Bug#480056: gdm: Gets killed with signal 6 on first login after boot.
Le jeudi 08 mai 2008 à 00:23 +0200, Kurt Roeckx a écrit : Program received signal SIGABRT, Aborted. 0xb7f73424 in __kernel_vsyscall () (gdb) bt #0 0xb7f73424 in __kernel_vsyscall () #1 0xb76bbef5 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb76bd871 in abort () from /lib/i686/cmov/libc.so.6 #3 0xb78372c2 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x000a in ?? () #5 0xb77db580 in ?? () from /lib/i686/cmov/libc.so.6 #6 0xbf88cc24 in ?? () Someone can suggest how I can get something more useful out of this? Where should I add a breakpoint? First of all I think you should install libglib2.0-dbg, which will make the top of the backtrace readable. Your investigation is much appreciated, since no one has yet taken the time to do it :/ Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#480056: gdm: Gets killed with signal 6 on first login after boot.
On Wed, 2008-05-07 at 23:30 +0200, Kurt Roeckx wrote: A few days ago, gdm started to restart every time I log in for the first time after booting. It switched back to console and then restarts gdm. In the log file I see: May 7 22:46:28 pc2 gdm[2726]: WARNING: gdm_cleanup_children: child 2731 crashed of signal 6 May 7 22:46:28 pc2 gdm[2726]: WARNING: gdm_cleanup_children: Slave crashed, killing its children I seem to have this version installed since 2008-04-26, but probably didn't reboot then. It was an upgrade from 2.20.4-1. Hi, This has been reported previously, in 462942, but that bug has been closed. -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22 signature.asc Description: This is a digitally signed message part
Bug#480056: gdm: Gets killed with signal 6 on first login after boot.
On Thu, May 08, 2008 at 09:39:21PM +0200, Sven Arvidsson wrote: On Wed, 2008-05-07 at 23:30 +0200, Kurt Roeckx wrote: A few days ago, gdm started to restart every time I log in for the first time after booting. It switched back to console and then restarts gdm. In the log file I see: May 7 22:46:28 pc2 gdm[2726]: WARNING: gdm_cleanup_children: child 2731 crashed of signal 6 May 7 22:46:28 pc2 gdm[2726]: WARNING: gdm_cleanup_children: Slave crashed, killing its children I seem to have this version installed since 2008-04-26, but probably didn't reboot then. It was an upgrade from 2.20.4-1. Hi, This has been reported previously, in 462942, but that bug has been closed. Looks like nobody reopened while people still saw the problem and so it got archived. Anyway, I have x11-xkb-utils installed, and don't think it's related. I also don't have Composite enabled in my xorg.conf. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480056: gdm: Gets killed with signal 6 on first login after boot.
Package: gdm Version: 2.20.5-1 Severity: important Hi, A few days ago, gdm started to restart every time I log in for the first time after booting. It switched back to console and then restarts gdm. In the log file I see: May 7 22:46:28 pc2 gdm[2726]: WARNING: gdm_cleanup_children: child 2731 crashed of signal 6 May 7 22:46:28 pc2 gdm[2726]: WARNING: gdm_cleanup_children: Slave crashed, killing its children I seem to have this version installed since 2008-04-26, but probably didn't reboot then. It was an upgrade from 2.20.4-1. On the same day I also upgraded xserver-xorg-video-intel from 2:2.2.1-1 to 2:2.2.1-2, and it's changelog suggest not much changed. I upgraded alot of other packages that day, but they're probably not related. According to my log file, I first started seeing the error on the april 27. I also notice that gdm pid 2726 is still running, but there is now also one running with pid 2859, not sure if that's normal or not. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480056: gdm: Gets killed with signal 6 on first login after boot.
On Wed, May 07, 2008 at 11:30:32PM +0200, Kurt Roeckx wrote: Package: gdm Version: 2.20.5-1 Severity: important Hi, A few days ago, gdm started to restart every time I log in for the first time after booting. It switched back to console and then restarts gdm. In the log file I see: May 7 22:46:28 pc2 gdm[2726]: WARNING: gdm_cleanup_children: child 2731 crashed of signal 6 May 7 22:46:28 pc2 gdm[2726]: WARNING: gdm_cleanup_children: Slave crashed, killing its children I seem to have this version installed since 2008-04-26, but probably didn't reboot then. It was an upgrade from 2.20.4-1. I'm seeing the same problem with 2.20.4-1. It seems that gdm starts 2 processes, and it's the second of those that gets the sigabort. I attached gdb to it, and it first received a bunch of SIGUSR2, then an SIGABRT. The stack trace wasn't very useful without debug symbols. I'll build a version with debug info. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480056: gdm: Gets killed with signal 6 on first login after boot.
On Wed, May 07, 2008 at 11:56:39PM +0200, Kurt Roeckx wrote: On Wed, May 07, 2008 at 11:30:32PM +0200, Kurt Roeckx wrote: Package: gdm Version: 2.20.5-1 Severity: important Hi, A few days ago, gdm started to restart every time I log in for the first time after booting. It switched back to console and then restarts gdm. In the log file I see: May 7 22:46:28 pc2 gdm[2726]: WARNING: gdm_cleanup_children: child 2731 crashed of signal 6 May 7 22:46:28 pc2 gdm[2726]: WARNING: gdm_cleanup_children: Slave crashed, killing its children I seem to have this version installed since 2008-04-26, but probably didn't reboot then. It was an upgrade from 2.20.4-1. I'm seeing the same problem with 2.20.4-1. It seems that gdm starts 2 processes, and it's the second of those that gets the sigabort. I attached gdb to it, and it first received a bunch of SIGUSR2, then an SIGABRT. The stack trace wasn't very useful without debug symbols. I'll build a version with debug info. So, I've build with debug now. I first just started the new version which worked, and got: Program received signal SIGUSR2, User defined signal 2. [Switching to Thread 0xb744daa0 (LWP 22635)] 0xb7ef6424 in __kernel_vsyscall () (gdb) bt #0 0xb7ef6424 in __kernel_vsyscall () #1 0xb76cebec in sched_yield () from /lib/i686/cmov/libc.so.6 #2 0x0806673e in gdm_slave_send (str=0x98fe9b0 QUERYLOGIN 22635 kurt, wait_for_ack=1) at slave.c:2982 #3 0x08066c2b in gdm_slave_send_string (opcode=0x80994b4 QUERYLOGIN, str=0x98fe5c0 kurt) at slave.c:3096 #4 0x08061e57 in gdm_slave_check_user_wants_to_log_in (user=0x98fe5c0 kurt) at slave.c:1293 #5 0x0807c120 in gdm_verify_user (d=0x98f0a28, username=0x0, allow_retry=1) at verify-pam.c:1094 #6 0x080639f1 in gdm_slave_wait_for_login () at slave.c:2127 #7 0x08062918 in gdm_slave_run (display=0x98f0a28) at slave.c:1650 #8 0x08061592 in gdm_slave_start (display=0x98f0a28) at slave.c:932 #9 0x0805ecd3 in gdm_display_manage (d=0x98f0a28) at display.c:414 #10 0x08050146 in gdm_start_first_unborn_local (delay=0) at gdm.c:266 #11 0x08053049 in main (argc=1, argv=0xbff12554) at gdm.c:1776 (gdb) c Continuing. Program received signal SIGUSR2, User defined signal 2. 0xb7ef6424 in __kernel_vsyscall () (gdb) bt #0 0xb7ef6424 in __kernel_vsyscall () #1 0xb76db1d3 in write () from /lib/i686/cmov/libc.so.6 #2 0x080723ce in gdm_fdprintf (fd=5, format=0x809a4a5 \n%s\n) at misc.c:198 #3 0x080666fe in gdm_slave_send (str=0x98fed68 LOGGED_IN 22635 1, wait_for_ack=1) at slave.c:2973 #4 0x08066ae6 in gdm_slave_send_num (opcode=0x8099747 LOGGED_IN, num=1) at slave.c:3069 #5 0x08062938 in gdm_slave_run (display=0x98f0a28) at slave.c:1653 #6 0x08061592 in gdm_slave_start (display=0x98f0a28) at slave.c:932 #7 0x0805ecd3 in gdm_display_manage (d=0x98f0a28) at display.c:414 #8 0x08050146 in gdm_start_first_unborn_local (delay=0) at gdm.c:266 #9 0x08053049 in main (argc=1, argv=0xbff12554) at gdm.c:1776 (gdb) c Continuing. Program received signal SIGUSR2, User defined signal 2. 0xb7ef6424 in __kernel_vsyscall () (gdb) bt #0 0xb7ef6424 in __kernel_vsyscall () #1 0xb76e372d in select () from /lib/i686/cmov/libc.so.6 #2 0x0806698e in gdm_slave_send (str=0x98fcf60 LOGIN 22635 kurt, wait_for_ack=1) at slave.c:3032 #3 0x08066c2b in gdm_slave_send_string (opcode=0x8099751 LOGIN, str=0x98fe5c0 kurt) at slave.c:3096 #4 0x08062997 in gdm_slave_run (display=0x98f0a28) at slave.c:1664 #5 0x08061592 in gdm_slave_start (display=0x98f0a28) at slave.c:932 #6 0x0805ecd3 in gdm_display_manage (d=0x98f0a28) at display.c:414 #7 0x08050146 in gdm_start_first_unborn_local (delay=0) at gdm.c:266 #8 0x08053049 in main (argc=1, argv=0xbff12554) at gdm.c:1776 i(gdb) c Continuing. Program received signal SIGUSR2, User defined signal 2. 0xb7ef6424 in __kernel_vsyscall () (gdb) bt #0 0xb7ef6424 in __kernel_vsyscall () #1 0xb76cebec in sched_yield () from /lib/i686/cmov/libc.so.6 #2 0x0806673e in gdm_slave_send (str=0x98fed68 GREETPID 22635 0, wait_for_ack=1) at slave.c:2982 #3 0x08066ae6 in gdm_slave_send_num (opcode=0x80992a4 GREETPID, num=0) at slave.c:3069 #4 0x08061af8 in gdm_slave_whack_greeter () at slave.c:1170 #5 0x0806abbf in gdm_slave_session_start () at slave.c:4680 #6 0x0806299c in gdm_slave_run (display=0x98f0a28) at slave.c:1665 #7 0x08061592 in gdm_slave_start (display=0x98f0a28) at slave.c:932 #8 0x0805ecd3 in gdm_display_manage (d=0x98f0a28) at display.c:414 #9 0x08050146 in gdm_start_first_unborn_local (delay=0) at gdm.c:266 #10 0x08053049 in main (argc=1, argv=0xbff12554) at gdm.c:1776 (gdb) (gdb) c Continuing. Program received signal SIGUSR2, User defined signal 2. 0xb7ef6424 in __kernel_vsyscall () (gdb) bt #0 0xb7ef6424 in __kernel_vsyscall () #1 0xb76db1d3 in write () from /lib/i686/cmov/libc.so.6 #2 0x080723ce in gdm_fdprintf (fd=5, format=0x809a4a5 \n%s\n) at misc.c:198 #3 0x080666fe in gdm_slave_send (str=0x99018f0 WRITE_X_SERVERS 22635 0,
