notification-daemon crashed with signal 5 in g_logv()

[Roberto Gradini]

Binary package hint: notification-daemon

It crashed when i run rhythmbox

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Jun 29 10:26:14 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/notification-daemon/notification-daemon
NonfreeKernelModules: cdrom
Package: notification-daemon 0.3.7-1ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/lib/notification-daemon/notification-daemon
ProcCwd: /
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: notification-daemon
StacktraceTop:
 g_logv () from /usr/lib/libglib-2.0.so.0
 g_log () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? ()
Title: notification-daemon crashed with signal 5 in g_logv()
Uname: Linux pearljam 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:IA__g_logv (log_domain=<value optimized out>, log_level=G_LOG_LEVEL_ERROR, format=0xb7ae95a0 "%s", args1=0xbfc686ec "8NG\b�")
IA__g_log (log_domain=0xb7acd0a3 "Gdk", log_level=G_LOG_LEVEL_ERROR, format=0xb7ae95a0 "%s") at /build/buildd/glib2.0-2.13.5/glib/gmessages.c:517
gdk_x_error (display=0x8064000, error=0xbfc68798) at /build/buildd/gtk+2.0-2.11.4/gdk/x11/gdkmain-x11.c:641
_XError (dpy=0x8064000, rep=0xbfc6888c) at ../../src/XlibInt.c:2907
_XReply (dpy=0x8064000, rep=0xbfc6888c, extra=0, discard=0) at ../../src/XlibInt.c:1833

[Martin Ahnelöv (gasten)]

Can recreate the behaviour? Is it the first time? Did you do anything out of the ordinary?

[Paul Hannah (pkhannah)]

Martin,

It's happened a number of times, on startup. The window that shows up
when gnome is started (with the services showing as they're loaded)
seems to stall, then this error shows.

Is there anything I can check to give you and more of an idea?

Paul.

Martin Ahnelöv wrote:
> *** This bug is a duplicate of bug 122637 ***
> https://bugs.launchpad.net/bugs/122637
>
> Can recreate the behaviour? Is it the first time? Did you do anything
> out of the ordinary?
>

[Martin Ahnelöv (gasten)]

Are you able to start programs before the crash occures? if that is the case, please follow these instructions and include the logfiles as an attatchment. https://wiki.ubuntu.com/Valgrind

Also, please watch bug #122637 and do whatever they ask the initial bug reporter to do. This will greatly help us to see similarities.

Thank you.

[Paul Hannah (pkhannah)]

Sorry to be a pain, but this is a program being run I think from the
gnome start-up. how do I make that program run under valgrind? Do I
need to edit the gnome startup and replace the call to
notification-daemon with a valgrinded version?

Paul.

Martin Ahnelöv wrote:
> *** This bug is a duplicate of bug 122637 ***
> https://bugs.launchpad.net/bugs/122637
>
> Are you able to start programs before the crash occures? if that is the
> case, please follow these instructions and include the logfiles as an
> attatchment. https://wiki.ubuntu.com/Valgrind
>
> Also, please watch bug #122637 and do whatever they ask the initial bug
> reporter to do. This will greatly help us to see similarities.
>
> Thank you.
>

[Martin Ahnelöv (gasten)]

open the program-menu --> Accesoaries --> Terminal (this may differ depending on what language you are using). That will open the Terminal, or Console. That's where you type the command.

Actually, I don't think you have the same error as the original reporter RobertoGradini, so can I please beg you to file another bug-report, so we can have a clearer view of what's going on?

Thank you.

[Paul Hannah (pkhannah)]

MY problem was knowing what app to run under valgrind...

I'll fire off another report any time it happens.

Paul.

Martin Ahnelöv wrote:
> *** This bug is a duplicate of bug 122637 ***
> https://bugs.launchpad.net/bugs/122637
>
> open the program-menu --> Accesoaries --> Terminal (this may differ
> depending on what language you are using). That will open the Terminal,
> or Console. That's where you type the command.
>
> Actually, I don't think you have the same error as the original
> reporter RobertoGradini, so can I please beg you to file another bug-
> report, so we can have a clearer view of what's going on?
>
> Thank you.
>

[Thomas Hotz (thotz-deactivatedaccount)]

Confirming this bug because it has several duplicates.

[Mörgæs (moergaes)]

Closing this group of reports from 2007.
If a similar bug appears in 14.04 please create a new one.