As far as i am concerned the bug is not fixed with this version of the kbd package.
I still have to kill screensaver via console to come back to my x session.
Regards,
> ----- Original Message ----- > From: Launchpad Bug Tracker > Sent: 10/28/08 10:40 am > To: <email address hidden> > Subject: [Bug 275957] Re: Unlock dialog never shows > (gnome-screensaver-dialog crashed with SIGSEGV) > > This bug was fixed in the package libgnomekbd - 2.24.0-0ubuntu2 > > --------------- > libgnomekbd (2.24.0-0ubuntu2) intrepid; urgency=low > > * > debian/patches/90_upstream_dont_crash_on_incorrect_xorg_configuration.patch: > - upstream change to not crash on incorrect xorg configuration > (lp: #275957) > > -- Sebastien Bacher <email address hidden> Mon, 27 Oct 2008 16:14:29 > +0100 > > ** Changed in: libgnomekbd (Ubuntu) > Status: Fix Committed => Fix Released > > -- > Unlock dialog never shows (gnome-screensaver-dialog crashed with SIGSEGV) > https://bugs.launchpad.net/bugs/275957 > You received this bug notification because you are a direct subscriber > of the bug. >
As far as i am concerned the bug is not fixed with this version of the kbd
package.
I still have to kill screensaver via console to come back to my x session.
Regards,
> ----- Original Message ----- screensaver- dialog crashed with SIGSEGV) patches/ 90_upstream_ dont_crash_ on_incorrect_ xorg_configurat ion.patch: screensaver- dialog crashed with SIGSEGV) /bugs.launchpad .net/bugs/ 275957
> From: Launchpad Bug Tracker
> Sent: 10/28/08 10:40 am
> To: <email address hidden>
> Subject: [Bug 275957] Re: Unlock dialog never shows
> (gnome-
>
> This bug was fixed in the package libgnomekbd - 2.24.0-0ubuntu2
>
> ---------------
> libgnomekbd (2.24.0-0ubuntu2) intrepid; urgency=low
>
> *
> debian/
> - upstream change to not crash on incorrect xorg configuration
> (lp: #275957)
>
> -- Sebastien Bacher <email address hidden> Mon, 27 Oct 2008 16:14:29
> +0100
>
> ** Changed in: libgnomekbd (Ubuntu)
> Status: Fix Committed => Fix Released
>
> --
> Unlock dialog never shows (gnome-
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>