Unlock dialog never shows (gnome-screensaver-dialog crashed with SIGSEGV)

StacktraceTop:gkbd_indicator_fill (gki=0x9927848) at gkbd-indicator.c:279
gkbd_indicator_init (gki=0x9927848) at gkbd-indicator.c:623
IA__g_type_create_instance (type=159503072) at /build/buildd/glib2.0-2.18.1/gobject/gtype.c:1674
g_object_constructor (type=159503072, n_construct_properties=0, construct_params=0x0)
IA__g_object_newv (object_type=159503072, n_parameters=0, parameters=0x0)

The same happened to me. I just locked the screen (Ctrl+Alt+L) and then I wasn't able to enter my session. gnome-screensaver didn't show me the lock screen whit password field.
When I click with the mouse, the screensaver disappears and the mouse appears above the black screen for about one second and then the screensaver reappears.
I had to go to one console (Ctrl Alt F1) to kill gnome-screensaver and reenter my session. Then I can launch gnome-screensaver again.

The crash of gnome-screensaver-dialog don't occured all the time but I get a new line like the following one in dmesg each time I click on type on keyboard :
[ 3718.938629] gnome-screensav[1233]: segfault at 51 ip b7eb4fa6 sp bfe7e620 error 4 in libgnomekbdui.so.3.0.0[b7eae000+f000]

Hi,

I have the same problem:
[ 3123.437075] gnome-screensav[9168]: segfault at 51 ip b7f36fa6 sp bf8ff890 error 4 in libgnomekbdui.so.3.0.0[b7f30000+f000]

When I want to unlock the screensaver.

This is linked to the keyboard choice...

To fix it (on both my workstations) I opened my keyboard preferences, clicked "+" to select a new layout, selected the SAME layout I used to have. Then it appears twice on the list. Select the newly-added one as default and make it the system default. You can get rid of the old one.

I guess there must have been some broken layouts at some point in alphas and upgrades retained them ?

Let me know if this fixes it for you too !

> Let me know if this fixes it for you too !
Works for me, thanks !

> Let me know if this fixes it for you too !
Works for me too.
Going to update the upstream bug I filed...
Thanks guys!

I'm pretty sure this issue is related to having an invalid keyboard layout
state. I haven't seen this issue in a while, but I have a separate one about
the keyboard layout indicator applet -- the whole X keyboard layout system
gets confused sometimes when I plug in an external (Apple USB) keyboard...
to the point that my laptop keyboard types Dvorak (as usual) and the
external keyboard types QWERTY! ... no wonder things start crashing.

On Mon, Oct 20, 2008 at 1:06 PM, Ronan Jouchet <email address hidden> wrote:

> > Let me know if this fixes it for you too !
> Works for me too.
> Going to update the upstream bug I filed...
> Thanks guys!
>
> --
> gnome-screensaver-dialog crashed with SIGSEGV in g_type_create_instance()
> https://bugs.launchpad.net/bugs/275957
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Hi!

I had the exact samse issue (no possibility to type password to unlock the screen) and redefining the keyboard layout fixed it! Thanks!

A clean install on an other laptop exhibits the same problem. Maybe this is due to the fact that I chose a french keyboard layout?

I'm using French alternative keyboard too...

Sébastien Valette wrote:
> A clean install on an other laptop exhibits the same problem. Maybe this
> is due to the fact that I chose a french keyboard layout?
>

I can reproduce it on a clean RC install too :
- Install Ubuntu, pick "France - France alternative" as the keyboard.
- When Ubuntu is installed, try "Lock screen" from FUSA
- Try to unlock...

Will see if I can reproduce on a default English install.

This seems to be specific to the "France - France alternative" keyboard, doe snot affect the default US keyboard or the "France - France" keyboard...

Unfortunately, the "France - France alternative" keyboard is the default for French users :)
People that are/were affected by this bug: please tell us which keyboard you used, espcially if it wasn't "France alternative".

The strange thing is that adding a "France alternative" layout (and removing the "France alternative" set by the installer) in the Preferences > Keyboard > Layouts workarounds the bug...

Should be fixed at the source of the crash (libgnomekbd).

the issue is similar to bug #273299 and http://bugzilla.gnome.org/show_bug.cgi?id=553915

Could users having this issue and not using a french keymap comment on the bug to say what layout they are using?

I've got the same issue but my layout is Canada multilingual (for both English and French...)

the xorg configuration is weird on configurations which trigger the crash but upstream workaround the crash, the change has been uploaded to intrepid now but will likely need to be uploaded as a stable update rather since the intrepid candidate images have already been rolled now

opening an xorg bug since the xorg configuration has several groups which have no title, running setxkbmap to set the same configuration workaround the issue, upstream thinkgs that's an xorg bug

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

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.
>

I have opened Bug 306319 to track the defect reported by myself, iram and others related to gnome-screensaver-dialog not coming back after a resume, even after this particular defect was fixed.

[This is an automated message]

Hi kenneth-arnold,

Please attach the output of `lspci -vvnn` too.

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.