registry team mailing list archive

[Didier Roche <didrocks@xxxxxxxxxx>]

@Mark: I think there are two bugs there seeting the stacktrace of
people. That's why I tried to create this on titling ("gnome panel
conflict"). The other bug is the VBlank one and driver/graphical card
not supporting it.

I think for this one, unity should kill gnome-panel at start, this will handle as well:
- people saving their session in the GNOME session and switching then to the unity session (gnome-panel is saved in the registered session)
- people starting unity in their GNOME session to have a try.

or either, unity don't crash in the old-system-tray code.

** Summary changed:

- gnome panel conflict: Unity keeps reloading on my system and get white background...
+ Existing systray causes unity to crash (gnome panel conflict): Unity keeps reloading on my system and get white background...

-- 
Existing systray causes unity to crash (gnome panel conflict): Unity keeps reloading on my system and get white background...
https://bugs.launchpad.net/bugs/578585
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for NULL Project.