gdmsetup crashed with SIGSEGV in strcmp()

Bug #410475 reported by Into the Pit
816
This bug affects 163 people
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gdm

gdmsetup crashes at start.

ProblemType: Crash
Architecture: i386
Date: Fri Aug 7 22:55:17 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gdmsetup
Package: gdm 2.27.4-0ubuntu9
ProcCmdline: gdmsetup
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0xc47a98 <strcmp+8>: mov (%ecx),%al
 PC (0x00c47a98) ok
 source "(%ecx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gdm
StacktraceTop:
 strcmp () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: gdmsetup crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Revision history for this message
Into the Pit (frickelpit) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:strcmp () at ../sysdeps/i386/i686/strcmp.S:39
?? ()
IA__g_cclosure_marshal_VOID__VOID (closure=0x951aa00,
IA__g_closure_invoke (closure=0x951aa00, return_value=0x0,
signal_emit_unlocked_R (node=<value optimized out>,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gdm (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
tr33m4n (tr33m4n) wrote :

Effects 64-bit also

Revision history for this message
Daniel Santibáñez Polanco (dansanti) wrote :

when i click on unlock..

Revision history for this message
Rubén Parra (rubenxparra) wrote :

I reply the bug when click in System>Adminitration>Login Screen

Revision history for this message
Kåre Birger Lapstuen (lapstue) wrote :

Happend for me on 64-bit version of ubuntu 9.10. Crashes when I click unlock.

Revision history for this message
Tom Pino (metalsmith-rangeweb) wrote :

I am on 64bit and it crashes just about when you have time to read the window to find unlock but to fast to actually click anything.

Revision history for this message
Tom Pino (metalsmith-rangeweb) wrote :

I thought I would try to bypass the sign-in for the gdm by "sudo gdm" in terminal;

ken@ken-desktop:~$ sudo gdm
[sudo] password for ken:

** (gdm-binary:3835): WARNING **: Failed to acquire org.gnome.DisplayManager

** (gdm-binary:3835): WARNING **: Could not acquire name; bailing out
ken@ken-desktop:~$

Revision history for this message
FrozenFish (frozenfish91) wrote :

Crashes few seconds or almost immediately after launch when launched normally but when I start it in sudo it stays up and don't crashes.
When I then click the unlock button blanks out and nothing happens (not even in the terminal).

Revision history for this message
Hellsgator (hellsgate) wrote :

same issue here. crashed when opening it in control center.

Revision history for this message
fastfret79 (markfoxwell) wrote :

Same as...

mark@karmic:~$ sudo gdm
[sudo] password for mark:

** (gdm-binary:3552): WARNING **: Failed to acquire org.gnome.DisplayManager

** (gdm-binary:3552): WARNING **: Could not acquire name; bailing out

Revision history for this message
fastfret79 (markfoxwell) wrote :
Download full text (3.9 KiB)

Although, running a gdmsetup produces the following:

mark@karmic:~$ gdmsetup

** (gdmsetup:3604): WARNING **: Error calling GetValue('daemon/TimedLoginEnable'): Key not found

** (gdmsetup:3604): WARNING **: Error calling GetValue('daemon/TimedLoginDelay'): Key not found
** (gdmsetup:3604): DEBUG: init delay=30
** (gdmsetup:3604): DEBUG: GdmUserManager: Found current seat: /org/freedesktop/ConsoleKit/Seat1
** (gdmsetup:3604): DEBUG: GdmUserManager: running 'ck-history --frequent --seat='Seat1' --session-type='''
** (gdmsetup:3604): DEBUG: GdmUserManager: explicitly skipping user: nobody
** (gdmsetup:3604): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:3604): DEBUG: adding monitor for '/home/mark/.face'
** (gdmsetup:3604): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:3604): DEBUG: adding monitor for '/var/run/vboxadd/.face'
** (gdmsetup:3604): DEBUG: Getting list of sessions for user 999
** (gdmsetup:3604): DEBUG: Found 0 sessions for user vboxadd
** (gdmsetup:3604): DEBUG: Getting list of sessions for user 1000
** (gdmsetup:3604): DEBUG: Found 1 sessions for user mark
** (gdmsetup:3604): DEBUG: GdmUser: adding session /org/freedesktop/ConsoleKit/Session2
** (gdmsetup:3604): DEBUG: GdmUserManager: sessions changed user=mark num=1
** (gdmsetup:3604): DEBUG: GdmUserManager: added session for user: mark
** (gdmsetup:3604): DEBUG: GdmUserManager: history output: mark 11

** (gdmsetup:3604): DEBUG: GdmUserManager: history output: root 4

** (gdmsetup:3604): DEBUG: GdmUserManager: excluding user 'root'
** (gdmsetup:3604): DEBUG: Login freq 1=0 2=11

** (gdmsetup:3604): WARNING **: Error calling GetValue('daemon/AutomaticLoginEnable'): Key not found

** (gdmsetup:3604): WARNING **: Error calling GetValue('daemon/TimedLoginEnable'): Key not found

** (gdmsetup:3604): WARNING **: Error calling GetValue('daemon/TimedLogin'): Key not found
** (gdmsetup:3604): DEBUG: init user='(null)' auto=False
Segmentation fault (core dumped)
mark@karmic:~$ cls
No command 'cls' found, but there are 22 similar ones
bash: cls: command not found
mark@karmic:~$ clear

mark@karmic:~$ gdmsetup

** (gdmsetup:3611): WARNING **: Error calling GetValue('daemon/TimedLoginEnable'): Key not found

** (gdmsetup:3611): WARNING **: Error calling GetValue('daemon/TimedLoginDelay'): Key not found
** (gdmsetup:3611): DEBUG: init delay=30
** (gdmsetup:3611): DEBUG: GdmUserManager: Found current seat: /org/freedesktop/ConsoleKit/Seat1
** (gdmsetup:3611): DEBUG: GdmUserManager: running 'ck-history --frequent --seat='Seat1' --session-type='''
** (gdmsetup:3611): DEBUG: GdmUserManager: explicitly skipping user: nobody
** (gdmsetup:3611): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:3611): DEBUG: adding monitor for '/home/mark/.face'
** (gdmsetup:3611): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:3611): DEBUG: adding monitor for '/var/run/vboxadd/.face'
** (gdmsetup:3611): DEBUG: Getting list of sessions for user 999
** (gdmsetup:3611): DEBUG: Found 0 sessions for user vboxadd
** (gdmsetup:3611): DEBUG: Getting list of sessions for user 1000
** (gdmsetup:3611): DEBUG: Found 1 sessions for user mark
** (gdmsetup:3611): DEBUG: GdmUser: adding session ...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote :

Confirming due to the number of duplicates, the dialog is working correctly there, could be similar to bug #410727

Changed in gdm (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Did you restart gdm after the upgrade? Is somebody having the issue on an intel installation?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could somebody get a debug stacktrace?

Revision history for this message
Sebastien Bacher (seb128) wrote :

The tool is not meant to be run using sudo since it use policykit, running it with sudo is an user error and not a bug

Revision history for this message
Crsim (crsim) wrote :

I did not try to run it using sudo.

Revision history for this message
Hippu (teemu-heinamaki) wrote :

Rebooting does not solve the bug. I attached the stacktrace from apport with the -dbg package installed.

Revision history for this message
Wayne Cat (exchange) wrote :

Sebastien,

the bug #410727 ( https://bugs.launchpad.net/bugs/410727 ) is not accessible

-------
Not allowed here

Sorry, you don't have permission to access this page.

You are logged in as Wayne Cat.
------

is there a solution in this bug report?

Revision history for this message
C de-Avillez (hggdh2) wrote :

@Wayne: The bug was still marked as private due to the stacktraces. I looked at them, and did not see anything warranting a Private status, so I reset it. You can now access it.

Sorry for that, but sometimes stacktraces do contain private data, and we try to be careful on them.

Revision history for this message
Bobby McGee (iaskedalice09) wrote :

Same bug on Dell Inspiron 1525n

Got this output when I try and run gdmsetup as root in Terminal

** (gdmsetup:16795): WARNING **: Error calling GetValue('daemon/TimedLoginEnable'): Key not found

** (gdmsetup:16795): WARNING **: Error calling GetValue('daemon/TimedLoginDelay'): Key not found
** (gdmsetup:16795): DEBUG: init delay=30
** (gdmsetup:16795): DEBUG: GdmUserManager: skipping shell /bin/false
** (gdmsetup:16795): DEBUG: GdmUserManager: Found current seat: /org/freedesktop/ConsoleKit/Seat1
** (gdmsetup:16795): DEBUG: GdmUserManager: running 'ck-history --frequent --seat='Seat1' --session-type='''
** (gdmsetup:16795): DEBUG: GdmUserManager: explicitly skipping user: nobody
** (gdmsetup:16795): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:16795): DEBUG: adding monitor for '/home/penguin/.face'
** (gdmsetup:16795): DEBUG: Getting list of sessions for user 1000
** (gdmsetup:16795): DEBUG: Found 1 sessions for user penguin
** (gdmsetup:16795): DEBUG: GdmUser: adding session /org/freedesktop/ConsoleKit/Session2
** (gdmsetup:16795): DEBUG: GdmUserManager: sessions changed user=penguin num=1
** (gdmsetup:16795): DEBUG: GdmUserManager: added session for user: penguin
** (gdmsetup:16795): DEBUG: GdmUserManager: history output: root 288

** (gdmsetup:16795): DEBUG: GdmUserManager: excluding user 'root'
** (gdmsetup:16795): DEBUG: GdmUserManager: history output: penguin 31

** (gdmsetup:16795): DEBUG: GdmUserManager: history output: (null) 2

** (gdmsetup:16795): WARNING **: Unable to parse history: (null) 2

** (gdmsetup:16795): WARNING **: Error calling GetValue('daemon/AutomaticLoginEnable'): Key not found

** (gdmsetup:16795): WARNING **: Error calling GetValue('daemon/TimedLoginEnable'): Key not found

** (gdmsetup:16795): WARNING **: Error calling GetValue('daemon/TimedLogin'): Key not found
** (gdmsetup:16795): DEBUG: init

Revision history for this message
bert07 (marien.bert) wrote :

Running Ubuntu 9.10 on a i386 desktop.

Ran "gdmsetup" in the root terminal.
Got these messages.

** (gdmsetup:3505): WARNING **: Error calling GetValue('daemon/TimedLoginEnable'): Key not found

** (gdmsetup:3505): WARNING **: Error calling GetValue('daemon/TimedLoginDelay'): Key not found
** (gdmsetup:3505): DEBUG: init delay=30
** (gdmsetup:3505): DEBUG: GdmUserManager: skipping shell /bin/false
** (gdmsetup:3505): DEBUG: Failed to identify the current session: Unable to lookup session information for process '3505'

** (gdmsetup:3505): WARNING **: Unable to find users: no seat-id found
** (gdmsetup:3505): DEBUG: GdmUserManager: explicitly skipping user: nobody
** (gdmsetup:3505): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:3505): DEBUG: adding monitor for '/home/bert/.face'
** (gdmsetup:3505): DEBUG: Getting list of sessions for user 1000
** (gdmsetup:3505): DEBUG: Found 1 sessions for user bert
** (gdmsetup:3505): DEBUG: GdmUserManager: not adding session on other seat: /org/freedesktop/ConsoleKit/Session2

A unlock window appears, but doesn't work.

Revision history for this message
bert07 (marien.bert) wrote :

I also found the following messages in /var/log/messages

Aug 10 17:34:34 bavo kernel: [ 42.469329] hda-intel: Too big adjustment 32
Aug 10 17:34:34 bavo kernel: [ 42.533457] hda-intel: Too big adjustment 32
Aug 10 17:34:34 bavo kernel: [ 42.549331] hda-intel: Too big adjustment 32
Aug 10 17:34:34 bavo kernel: [ 42.617465] hda-intel: Too big adjustment 32
Aug 10 17:34:34 bavo kernel: [ 42.640358] hda-intel: Too big adjustment 32
Aug 10 17:34:34 bavo kernel: [ 90.000025] Clocksource tsc unstable (delta = -151174583 ns)
Aug 10 17:34:34 bavo kernel: [ 109.204275] gdmsetup[3374]: segfault at 0 ip 00cf4a98 sp bfe8b04c error 4 in libc-2.10.1.so[c82000+151000]

Revision history for this message
bert07 (marien.bert) wrote :

I also found the following message in /var/log/auth.log

Aug 10 17:34:34 bavo dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.50" (uid=1000 pid=3362 comm="/usr/bin/indicator-messages-service) interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination=":1.75" (uid=1000 pid=3630 comm="gdmsetup))

Revision history for this message
Alessandro Ranaldi (ciaolo) wrote :

In vb (with intel pentium host) it closes, in real installation (intel atom, a netbook) it works well.

Revision history for this message
Taralyn Darkchylde (hellion0) wrote :

Had the same thing just happen, message is pretty much the same as initial report.

From dmesg:

[ 7266.171776] gdmsetup[22938]: segfault at 0 ip 00d25a98 sp bfefeb2c error 4 in libc-2.10.1.so[cb3000+151000]
[ 8403.027299] gdmsetup[26134]: segfault at 0 ip 008d7a98 sp bfbc036c error 4 in libc-2.10.1.so[865000+151000]

Revision history for this message
Sebastien Bacher (seb128) wrote :

could people having the issue add their /etc/gdm/gconf.gdm and custom.conf there?

Revision history for this message
Fabian (fabian-h) wrote :

I'm experiencing this bug on a VM running the latest Karmic. I did not change any settings regarding gdm, they should all be default values. I don't even have any gdm.conf or custum.conf in /etc/gdm (There is ony a gdm.schemas).

Revision history for this message
Michał Mrówczyński (ups5) wrote :

For a true installation (clean install on Acer Aspire Ine 150 BB), is not working properly. This requires the use of from time to time command restart netbook-launcher

Revision history for this message
Michał Mrówczyński (ups5) wrote :

It's "netbook-launcher restart" command, of cors.

Revision history for this message
Hippu (teemu-heinamaki) wrote :

The gconf.gdm file doesn't exist, but the rather empty looking custom.conf is there.

Revision history for this message
Taralyn Darkchylde (hellion0) wrote :

@ #28: Neither file mentioned exists on my system.

Revision history for this message
Wayne Cat (exchange) wrote :

Sebastien,

the files also do not exist on my system

------------
root@macbook:~# ls /etc/gdm
gdm.schemas Init PostLogin PostSession PreSession Xsession

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue happen when there is no key in custom.conf yet, I've a fix locally now

Changed in gdm (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
manzur (sl-solaris) wrote :

we have too see that fix first, because a bad treatment brings more problems

Revision history for this message
bert07 (marien.bert) wrote :

The latest update with "gdm" in it, did not resolve anything here.

root@bavo:~# gdmsetup

** (gdmsetup:3851): WARNING **: Error calling GetValue('daemon/TimedLoginEnable'): Key not found

** (gdmsetup:3851): WARNING **: Error calling GetValue('daemon/TimedLoginDelay'): Key not found
** (gdmsetup:3851): DEBUG: init delay=30
** (gdmsetup:3851): DEBUG: GdmUserManager: skipping shell /bin/false
** (gdmsetup:3851): DEBUG: GdmUserManager: Found current seat: /org/freedesktop/ConsoleKit/Seat1
** (gdmsetup:3851): DEBUG: GdmUserManager: running 'ck-history --frequent --seat='Seat1' --session-type='''
** (gdmsetup:3851): DEBUG: GdmUserManager: explicitly skipping user: nobody
** (gdmsetup:3851): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:3851): DEBUG: adding monitor for '/home/bert/.face'
** (gdmsetup:3851): DEBUG: Getting list of sessions for user 1000
** (gdmsetup:3851): DEBUG: Found 0 sessions for user bert
** (gdmsetup:3851): DEBUG: GdmUserManager: history output: root 10

** (gdmsetup:3851): DEBUG: GdmUserManager: excluding user 'root'
** (gdmsetup:3851): DEBUG: GdmUserManager: history output: bert 9

** (gdmsetup:3851): WARNING **: Error calling GetValue('daemon/AutomaticLoginEnable'): Key not found

** (gdmsetup:3851): WARNING **: Error calling GetValue('daemon/TimedLoginEnable'): Key not found

** (gdmsetup:3851): WARNING **: Error calling GetValue('daemon/TimedLogin'): Key not found
** (gdmsetup:3851): DEBUG: init user='(null)' auto=False
Segmentation fault (core dumped)
root@bavo:~#

Revision history for this message
Andrew O'Brien (ar-obrien) wrote :

Hmm, I don't have any keys set in custom.conf, and I don't have a gdm.conf (at least not in /etc/gdm). I do have a gdm.conf.dpkg.bak, which I have attached, dated 2009-04-03.
Did a recent update of gdm remove this file by mistake?

Revision history for this message
Sebastien Bacher (seb128) wrote :

the update has not been uploaded due to the alpha freeze being in effect

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gdm - 2.27.4-0ubuntu11

---------------
gdm (2.27.4-0ubuntu11) karmic; urgency=low

  * debian/patches/09_gdmsetup.patch:
    - clean some unused variables there
    - don't crash if there is no autologin key in the configuration yet
      (lp: #410475)
    - don't specify encoding in desktop entry (lp: #410591)
  * debian/patches/11_crash_for_apport.patch:
    - don't catch crashes so apport can do its job

 -- Sebastien Bacher <email address hidden> Wed, 12 Aug 2009 16:17:23 +0200

Changed in gdm (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.