could you try if that's still an issue in hardy?
--
gnome-panel crashed with SIGSEGV in gdk_x11_xatom_to_atom_for_display()
https://bugs.launchpad.net/bugs/148358
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
On Thu, May 8, 2008 at 7:32 AM, Sebastien Bacher [EMAIL PROTECTED]
wrote:
could you try if that's still an issue in hardy?
In the update of Gusty to Hardy, I dont have this problem
--
gnome-panel crashed with SIGSEGV in gdk_x11_xatom_to_atom_for_display()
closing the bug then, feel free to reopen if you get the issue again
** Changed in: gnome-panel (Ubuntu)
Status: Incomplete = Invalid
--
gnome-panel crashed with SIGSEGV in gdk_x11_xatom_to_atom_for_display()
https://bugs.launchpad.net/bugs/148358
You received this bug notification
Thanks for your report, may you tell us a few steps to trigger the
crash?
** Changed in: gnome-panel (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New = Incomplete
** Visibility changed to: Public
--
gnome-panel crashed with SIGSEGV in
On Nov 19, 2007 9:13 AM, Pedro Villavicencio [EMAIL PROTECTED] wrote:
Thanks for your report, may you tell us a few steps to trigger the
crash?
I think that these two bugs have in common the Ubuntu updating, and I think
it is problem of the gconf-editor configuration files from one version to
