Here the same. The fix works as expected.
regards
--
gnome-screensaver crashed with SIGSEGV in gs_manager_set_active()
https://bugs.launchpad.net/bugs/558721
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
Ok. let me know if you have some intermediate debug version I could test and
see if the issue is fixed. Would love to test that here.
Thanks
--
gnome-screensaver crashed with SIGSEGV in gs_manager_set_active()
https://bugs.launchpad.net/bugs/558721
You received this bug notification because you
Thanks for you fast reply. Please find attached the cathed debug log
when gnome-screensaver crashes when issuing a "gnome-screensaver-command
-a". Would be great to get that fixed ASAP as this seems to be the only
issue that is currently holding back us from deploying ubuntu 10.04 to
our main serve
I also get the same kind of crashes of gnome-screenaver daemon as soon
as "gnome-screensaver-command -a" is used. Please note, however, that
this happens with a remote X connection to a Sunray. But the stacktrace
looks quite similar. I Have started "/usr/bin/gnome-screenaver" with the
option "--no-
Let me add that I see the very same problem here with our SunRay Server
System which we have running under Ubuntu 9.04 (Jaunty). Since we have
installed updates and rebooted all SunRay sessions can't be locked
anymore. After some short investigation we see that "gnome-screensaver"
isn't automatical
Public bug reported:
Binary package hint: gdm
The logic in gdm-xdmcp-manager.c that calls the
gdm_xdmcp_recount_sessions() function seems to be broken. Here we do
have a system running as a terminal server with SunRays connected to an
intrepid system. We noticed that XDMCP sessions are declined i
