[Pkg-utopia-maintainers] Bug#558114: [hal] Console-kit-daemon segfault with error 4 on console-kit-daemon on hald start

Thu Nov 26 14:48:04 UTC 2009

waks wrote:
> Hi Micheal,
> 
> 
> gdb console-kit-daemon
> GNU gdb (GDB) 7.0-debian
> Copyright (C) 2009 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /usr/sbin/console-kit-daemon...(no debugging
> symbols found)...done.
> (gdb) set pagination 0
> (gdb) run --no-daemon --debug
> Starting program: /usr/sbin/console-kit-daemon --no-daemon --debug
> [Thread debugging using libthread_db enabled]
> console-kit-daemon[23779]: DEBUG: Debugging enabled
> console-kit-daemon[23779]: DEBUG: initializing console-kit-daemon 0.4.1
> console-kit-daemon[23779]: DEBUG: Cleaning up /var/run/console
> console-kit-daemon[23779]: DEBUG: Creating thread for log writing
> [New Thread 0x7ffff7ff7910 (LWP 23782)]
> console-kit-daemon[23779]: WARNING: Unable to load seats from file
> /etc/ConsoleKit/seats.d/.svn: Not a regular file

What is that .svn directory doing there?

> console-kit-daemon[23779]: GLib-GObject-WARNING: invalid (NULL) pointer
> instance
> console-kit-daemon[23779]: GLib-GObject-CRITICAL: g_signal_connect_data:
> assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> console-kit-daemon[23779]: GLib-GObject-WARNING: invalid (NULL) pointer
> instance
> console-kit-daemon[23779]: GLib-GObject-CRITICAL: g_signal_connect_data:
> assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> console-kit-daemon[23779]: GLib-GObject-WARNING: invalid (NULL) pointer
> instance
> console-kit-daemon[23779]: GLib-GObject-CRITICAL: g_signal_connect_data:
> assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> console-kit-daemon[23779]: GLib-GObject-WARNING: invalid (NULL) pointer
> instance
> console-kit-daemon[23779]: GLib-GObject-CRITICAL: g_signal_connect_data:
> assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> console-kit-daemon[23779]: GLib-GObject-WARNING: invalid (NULL) pointer
> instance
> console-kit-daemon[23779]: GLib-GObject-CRITICAL: g_signal_connect_data:
> assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000000040d319 in ?? ()
> (gdb) bt
> #0  0x000000000040d319 in ?? ()
> #1  0x000000000040a9ce in ?? ()
> #2  0x00007ffff6c75a35 in g_type_create_instance () from
> /usr/lib/libgobject-2.0.so.0
> #3  0x00007ffff6c5a70b in ?? () from /usr/lib/libgobject-2.0.so.0
> #4  0x00007ffff6c5b532 in g_object_newv () from /usr/lib/libgobject-2.0.so.0
> #5  0x00007ffff6c5c2b7 in g_object_new_valist () from
> /usr/lib/libgobject-2.0.so.0
> #6  0x00007ffff6c5c3fc in g_object_new () from /usr/lib/libgobject-2.0.so.0
> #7  0x000000000040a189 in ?? ()
> #8  0x00000000004072e8 in ?? ()
> #9  0x00007ffff644aabd in __libc_start_main (main=<value optimized out>,
> argc=<value optimized out>, ubp_av=<value optimized out>, init=<value
> optimized out>, fini=<value optimized out>, rtld_fini=<value optimized
> out>, stack_end=0x7fffffffe6c8) at libc-start.c:222
> #10 0x0000000000406c69 in ?? ()
> #11 0x00007fffffffe6c8 in ?? ()
> #12 0x000000000000001c in ?? ()
> #13 0x0000000000000003 in ?? ()
> #14 0x00007fffffffe917 in ?? ()
> #15 0x0000000000000000 in ?? ()
> 
> Hope it will help, I'm not familiar with bug-reporting, it's the first
> time to be honest...

For a really useful backtrace you need to recompile consolekit with debugging
symbols enabled. Could you follow the instructions on the wiki for that or
should i provide you with a dbg package?

> To answer your questions, yes it is totaly reproducible, at every boot,
> after hal start, I see lots of segfault from console-kit-daemon, and it
> never stop. I got this bug for few weeks now.

Do you mean, if hal is not running, you don't get any console-kit-daemon segfaults?

> [ 5455.935432] console-kit-dae[23707]: segfault at 18 ip
> 000000000040d319 sp 00007fff9e719a00 error 4 in
> console-kit-daemon[400000+21000]
> [ 5941.967387] console-kit-dae[23735]: segfault at 18 ip
> 000000000040d319 sp 00007fff39748d70 error 4 in
> console-kit-daemon[400000+21000]
> 
> I got to stop syslog-ng which fill up my /var with log messages

What messages? How often, in what time frame do they appear?

> I also notice that my CPU was used anormaly, and I found that in
> stopping hal, the cpu usage go back to normal.
> That's why I think Hal is a part of the problem, maybe I'm totally
> wrong. It's just based on the fact that segfault appear right after hal
> start, and the abnormal use of CPU
> To be really precise, it's not hal which use CPU it's dbus-messages, but
> stopping hal, make dbus CPU usage back to normal

Well, hal does no longer use consolekit, so I'm surprised that those two should
be connected somehow. Could you run dbus-monitor --system and check what is
going on on the system bus and see why it takes up that much CPU.

Do you have any messages from dbus or hal in the syslog?

> Sorry for my english
> 
> Best regards
> 
> WakS
> 
> Michael Biebl a écrit :
>> severity 558114 normal
>> thanks
>>
>> waks wrote:
>>> Package: hal
>>> Version: 0.5.13-6
>>> Severity: critical
>>>
>>> --- Please enter the report below this line. ---
>>>
>> Please describe in more detail, what you were doing that led to this segfault,
>> if it is reproducible (always) and how console-kit-daemon comes into play here.
>> Is it hal that segfaults or console-kit-daemon. If the latter, why did you file
>> it against hal?
>>
>> It would also help, if you could get a meaningful backtrace of the crashing
>> program [1]
>>
>> As I don't see a justification for a critical bug I'm downgrading it.
>>
>> Regards,
>> Michael
>>
>> [1] http://wiki.debian.org/HowToGetABacktrace
>>
>>
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-utopia-maintainers/attachments/20091126/977bbc30/attachment.pgp>