Thx for the effort so far, but the bug still happens on my system. I am running Intrepid (KDE4+compiz) on an Asus V2s laptop.
Architecture: amd64
Version: 0.2.10-1ubuntu9
Now that I read the above reproduction-recipe, I am fairly sure I am experiencing a similar bug.
The crash happens to me (up to once every hour) when I am using eclipse and close a dialog window (by pressing ESC), e.g. the file-search dialog or team>commit-dialog. I do not know how to reproduce this 100%, because it doesn't always happen, but that is definitely the trigger for the crash.
I do not find segfaults in my logs, but i do always have entries in my syslog before X crashes, indicating console-kit-daemon is the culprit:
Thx for the effort so far, but the bug still happens on my system. I am running Intrepid (KDE4+compiz) on an Asus V2s laptop.
Architecture: amd64
Version: 0.2.10-1ubuntu9
Now that I read the above reproduction-recipe, I am fairly sure I am experiencing a similar bug.
The crash happens (sometimes) when I am using eclipse and close a dialog window (by pressing ESC), not the parent window, e.g. the file-search dialog or team>commit-dialog. I do not know how to reproduce this 100%, because it doesn't always happen, but that is definitely a trigger for the crash.
I do not find segfaults in my logs, but i do always have an entry in my syslog right before X crashes, indicating console-kit-daemon is probably to blame:
Apr 1 11:02:11 nesus console-kit-daemon[5749]: WARNING: Unable to activate console: No such device or address
Apr 1 11:17:47 nesus console-kit-daemon[5749]: WARNING: Unable to activate console: No such device or address
Apr 1 13:22:27 nesus console-kit-daemon[5749]: WARNING: Unable to activate console: No such device or address
Apr 1 16:31:12 nesus console-kit-daemon[5749]: WARNING: Unable to activate console: No such device or address
Apr 1 16:47:35 nesus console-kit-daemon[5749]: WARNING: Unable to activate console: No such device or address
Apr 2 01:27:20 nesus console-kit-daemon[5763]: WARNING: Unable to activate console: No such device or address
Apr 2 11:56:54 nesus console-kit-daemon[5696]: WARNING: Unable to activate console: No such device or address
Apr 2 12:17:06 nesus console-kit-daemon[5696]: WARNING: Unable to activate console: No such device or address
Apr 2 12:17:06 nesus console-kit-daemon[5696]: GLib-GObject-WARNING: instance of invalid non-instantiatable type `(null)'
Apr 2 12:17:06 nesus console-kit-daemon[5696]: GLib-GObject-CRITICAL: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Apr 2 12:17:06 nesus console-kit-daemon[5696]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Every 'Unable to activate console'-line is a crash. The Glib-lines only appeared on the last crash.
As you can see I had a pretty disruptive April Fools day. :)
If you need more details, I'll be happy to provide them.
Thx for the effort so far, but the bug still happens on my system. I am running Intrepid (KDE4+compiz) on an Asus V2s laptop.
Architecture: amd64
Version: 0.2.10-1ubuntu9
Now that I read the above reproduction- recipe, I am fairly sure I am experiencing a similar bug.
The crash happens to me (up to once every hour) when I am using eclipse and close a dialog window (by pressing ESC), e.g. the file-search dialog or team>commit-dialog. I do not know how to reproduce this 100%, because it doesn't always happen, but that is definitely the trigger for the crash.
I do not find segfaults in my logs, but i do always have entries in my syslog before X crashes, indicating console-kit-daemon is the culprit:
Thx for the effort so far, but the bug still happens on my system. I am running Intrepid (KDE4+compiz) on an Asus V2s laptop.
Architecture: amd64
Version: 0.2.10-1ubuntu9
Now that I read the above reproduction- recipe, I am fairly sure I am experiencing a similar bug.
The crash happens (sometimes) when I am using eclipse and close a dialog window (by pressing ESC), not the parent window, e.g. the file-search dialog or team>commit-dialog. I do not know how to reproduce this 100%, because it doesn't always happen, but that is definitely a trigger for the crash.
I do not find segfaults in my logs, but i do always have an entry in my syslog right before X crashes, indicating console-kit-daemon is probably to blame:
Apr 1 11:02:11 nesus console- kit-daemon[ 5749]: WARNING: Unable to activate console: No such device or address kit-daemon[ 5749]: WARNING: Unable to activate console: No such device or address kit-daemon[ 5749]: WARNING: Unable to activate console: No such device or address kit-daemon[ 5749]: WARNING: Unable to activate console: No such device or address kit-daemon[ 5749]: WARNING: Unable to activate console: No such device or address kit-daemon[ 5763]: WARNING: Unable to activate console: No such device or address kit-daemon[ 5696]: WARNING: Unable to activate console: No such device or address kit-daemon[ 5696]: WARNING: Unable to activate console: No such device or address kit-daemon[ 5696]: GLib-GObject- WARNING: instance of invalid non-instantiatable type `(null)' kit-daemon[ 5696]: GLib-GObject- CRITICAL: g_signal_ emit_valist: assertion `G_TYPE_ CHECK_INSTANCE (instance)' failed kit-daemon[ 5696]: GLib-GObject- CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Apr 1 11:17:47 nesus console-
Apr 1 13:22:27 nesus console-
Apr 1 16:31:12 nesus console-
Apr 1 16:47:35 nesus console-
Apr 2 01:27:20 nesus console-
Apr 2 11:56:54 nesus console-
Apr 2 12:17:06 nesus console-
Apr 2 12:17:06 nesus console-
Apr 2 12:17:06 nesus console-
Apr 2 12:17:06 nesus console-
Every 'Unable to activate console'-line is a crash. The Glib-lines only appeared on the last crash.
As you can see I had a pretty disruptive April Fools day. :)
If you need more details, I'll be happy to provide them.