console-kit-daemon crashed with SIGSEGV in g_str_hash()

[albert]

Binary package hint: consolekit

Automatic report, I don't know what happened

ProblemType: Crash
Architecture: amd64
Date: Wed Mar 26 09:59:09 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/sbin/console-kit-daemon
Package: consolekit 0.2.3-3ubuntu5
PackageArchitecture: amd64
ProcCmdline: /usr/sbin/console-kit-daemon
ProcEnviron:

Signal: 11
SourcePackage: consolekit
StacktraceTop:
 g_str_hash () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: console-kit-daemon crashed with SIGSEGV in g_str_hash()
Uname: Linux 2.6.24-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev scanner tape

[Qiubo Su (qiubosu)]

hi sir,

can you help to remove me from the bug email list?

thanks,
qiubo su

On Wed, Jun 10, 2009 at 9:57 AM, Apport retracing service <
<email address hidden>> wrote:

> *** This bug is a duplicate of bug 196724 ***
> https://bugs.launchpad.net/bugs/196724
>
> ** Attachment removed: "CoreDump.gz"
> http://launchpadlibrarian.net/12910381/CoreDump.gz
>
> --
> console-kit-daemon crashed with SIGSEGV in g_str_hash()
> https://bugs.launchpad.net/bugs/207460
> You received this bug notification because you are a direct subscriber
> of the bug (via bug 196724).
>
> Status in “consolekit” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: consolekit
>
> Automatic report, I don't know what happened
>
> ProblemType: Crash
> Architecture: amd64
> Date: Wed Mar 26 09:59:09 2008
> DistroRelease: Ubuntu 8.04
> ExecutablePath: /usr/sbin/console-kit-daemon
> Package: consolekit 0.2.3-3ubuntu5
> PackageArchitecture: amd64
> ProcCmdline: /usr/sbin/console-kit-daemon
> ProcEnviron:
>
> Signal: 11
> SourcePackage: consolekit
> StacktraceTop:
> g_str_hash () from /usr/lib/libglib-2.0.so.0
> ?? () from /usr/lib/libglib-2.0.so.0
> ?? ()
> ?? ()
> ?? ()
> Title: console-kit-daemon crashed with SIGSEGV in g_str_hash()
> Uname: Linux 2.6.24-12-generic x86_64
> UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin
> plugdev scanner tape
>

[Dobry (dobry-dobrev)]

I don’t know how either :(

--
Dobry Dobrev
Office: 1 703 636 7112
Mobile: [phone]

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Qiubo Su
Sent: Wednesday, June 10, 2009 2:30 AM
To: <email address hidden>
Subject: Re: [Bug 207460] Re: console-kit-daemon crashed with SIGSEGV in g_str_hash()

*** This bug is a duplicate of bug 196724 ***
    https://bugs.launchpad.net/bugs/196724

hi sir,

can you help to remove me from the bug email list?

thanks,
qiubo su

On Wed, Jun 10, 2009 at 9:57 AM, Apport retracing service <
<email address hidden>> wrote:

> *** This bug is a duplicate of bug 196724 ***
> https://bugs.launchpad.net/bugs/196724
>
> ** Attachment removed: "CoreDump.gz"
> http://launchpadlibrarian.net/12910381/CoreDump.gz
>
> --
> console-kit-daemon crashed with SIGSEGV in g_str_hash()
> https://bugs.launchpad.net/bugs/207460
> You received this bug notification because you are a direct subscriber
> of the bug (via bug 196724).
>
> Status in “consolekit” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: consolekit
>
> Automatic report, I don't know what happened
>
> ProblemType: Crash
> Architecture: amd64
> Date: Wed Mar 26 09:59:09 2008
> DistroRelease: Ubuntu 8.04
> ExecutablePath: /usr/sbin/console-kit-daemon
> Package: consolekit 0.2.3-3ubuntu5
> PackageArchitecture: amd64
> ProcCmdline: /usr/sbin/console-kit-daemon
> ProcEnviron:
>
> Signal: 11
> SourcePackage: consolekit
> StacktraceTop:
> g_str_hash () from /usr/lib/libglib-2.0.so.0
> ?? () from /usr/lib/libglib-2.0.so.0
> ?? ()
> ?? ()
> ?? ()
> Title: console-kit-daemon crashed with SIGSEGV in g_str_hash()
> Uname: Linux 2.6.24-12-generic x86_64
> UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin
> plugdev scanner tape
>

--
console-kit-daemon crashed with SIGSEGV in g_str_hash()
https://bugs.launchpad.net/bugs/207460
You received this bug notification because you are a direct subscriber
of the bug (via bug 196724).