** Also affects: notify-osd
Importance: Undecided
Status: New
--
notify-osd (alsdorf) crashed with signal 5 in main()
https://bugs.launchpad.net/bugs/331150
You received this bug notification because you are a member of Notify
OSD Developers, which is subscribed to Notify OSD.
Status in Notify OSD: New
Status in “notify-osd” source package in Ubuntu: Triaged
Bug description:
Binary package hint: alsdorf
No idea what happened - just rebooted and logged into the session - first start
of alsdorf.
ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/alsdorf/alsdorf
Package: alsdorf 0.8-0ubuntu1
ProcCmdline: /usr/lib/alsdorf/alsdorf
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=de_DE.UTF-8
Signal: 5
SourcePackage: alsdorf
Stacktrace:
#0 0xb78a6b0f in g_logv () from /usr/lib/libglib-2.0.so.0
#1 0xb78a6e96 in g_log () from /usr/lib/libglib-2.0.so.0
#2 0x0805ad1c in main ()
StacktraceTop: main ()
ThreadStacktrace:
.
Thread 1 (process 28392):
#0 0xb78a6b0f in g_logv () from /usr/lib/libglib-2.0.so.0
#1 0xb78a6e96 in g_log () from /usr/lib/libglib-2.0.so.0
#2 0x0805ad1c in main ()
Title: alsdorf crashed with signal 5 in main()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
_______________________________________________
Mailing list: https://launchpad.net/~dx-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~dx-team
More help : https://help.launchpad.net/ListHelp
