notification-daemon crashed with SIGSEGV in move_notification()

[Guybrush88]

Binary package hint: notification-daemon

i was only downloading my mail when it crashed

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Jul 24 13:52:17 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/notification-daemon/notification-daemon
NonfreeKernelModules: fglrx
Package: notification-daemon 0.3.7-1ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/lib/notification-daemon/notification-daemon
ProcCwd: /
ProcEnviron:
 LANGUAGE=it_IT.UTF-8
 PATH=/home/davide/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: notification-daemon
StacktraceTop:
 ?? ()
 move_notification ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: notification-daemon crashed with SIGSEGV in move_notification()
Uname: Linux Pizzo 2.6.22-8-generic #1 SMP Thu Jul 12 16:09:47 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Florin Samareanu (florin-samareanu-vectorsoftware)]

it also occures to me, after todays updates.also, something is broken in nautilus since refreshing a folder crashes the whole thing and reopens the folder.

[Apport retracing service (apport)]

StacktraceTop:move_notification (nw=<value optimized out>, x=<value optimized out>, y=<value optimized out>) at theme.c:746
notify_daemon_notify_handler (daemon=0x632190, app_name=<value optimized out>, id=0, icon=0x64c570 "stock_mail", summary=<value optimized out>,
dbus_glib_marshal_notification_daemon_VOID__STRING_UINT_STRING_STRING_STRING_BOXED_BOXED_INT_POINTER (closure=0x7fff27be3140,
gobject_message_function (connection=0x647d50, message=0x64c600, user_data=<value optimized out>) at dbus-gobject.c:1160
_dbus_object_tree_dispatch_and_unlock (tree=0x647b20, message=0x64c600) at dbus-object-tree.c:842

[Cristian Tala (naito-neko)]

Yea, same problem opening folders with nautilus.

[Sebastien Vajda (sebvajda)]

same thing happened here.

[grendelkhan (scottricketts)]

Same crash and respawn problem here. The only way to fix this is to shut down evolution, which really stinks.

[Jesse Haubrich (jhaubrich)]

I don't use evolution and so don't see the relation. Still, update notifier dies several times a day of its own volition. I've killed all of the evolution processes just in case. Will keep an eye on it.

[Juan Pablo Salazar Bertín (snifer)]

Confirmed. Backtrace attached.

[Paul Adams (psadams)]

Experienced this same problem while receiving emails in Evolution today.

[Rich (rincebrain)]

Experienced this problem while using Pidgin today.

[Rich (rincebrain)]

Oh.

Important note - experienced on i386, so not an amd64 exclusive issue.

[Martin Pitt (pitti)]

Confirmed here, too. Michael, can you please have a look?

[einfach (freu-dich)]

happened on amd64 during startup of gnome gui

[Guybrush88 (guybrush)]

i also got this crash today when i was installing some updates. fortunately i got nothing lost

[grendelkhan (scottricketts)]

I worked around this issue by doing a chmod 644 on /usr/lib/notification-daemon/notification-daemon

It's ugly but everything else works now, including Pidgin and Evolution.

[Daniel J Blueman (danielblueman)]

notification-daemon got hit by SIGSEGV while I was using rhythmbox on an x86-64:

 #0 0x00002b12bc47f2ff in ?? ()
    from /usr/lib/notification-daemon-1.0/engines/libubuntu.so
 #1 0x00002b12bc47f6e2 in move_notification ()
    from /usr/lib/notification-daemon-1.0/engines/libubuntu.so
 #2 0x0000000000403c7f in ?? ()
 #3 0x0000000000404d35 in ?? ()
 #4 0x00002b12b5d69144 in ?? () from /usr/lib/libdbus-glib-1.so.2
 #5 0x00002b12b5f97119 in ?? () from /usr/lib/libdbus-1.so.3
 #6 0x00002b12b5f8a9bb in dbus_connection_dispatch ()
    from /usr/lib/libdbus-1.so.3
 #7 0x00002b12b5d65f75 in ?? () from /usr/lib/libdbus-glib-1.so.2
 #8 0x00002b12b78940a3 in g_main_context_dispatch ()
    from /usr/lib/libglib-2.0.so.0
 #9 0x00002b12b78973ad in ?? () from /usr/lib/libglib-2.0.so.0
 #10 0x00002b12b78976ba in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
 #11 0x00002b12b6799983 in IA__gtk_main ()
     at /build/buildd/gtk+2.0-2.11.6/gtk/gtkmain.c:1144
        tmp_list = (GList *) 0x63cb98
        functions = (GList *) 0x0
        init = (GtkInitFunction *) 0x623990
        loop = (GMainLoop *) 0x63e4d0
 #12 0x0000000000404a3a in ?? ()
 #13 0x00002b12b7d65b24 in XHXX$X () from /lib/libc.so.6
 #14 0x0000000000403209 in ?? ()
 #15 0x00007ffff4f699b8 in ?? ()
 #16 0x0000000000000000 in ?? ()

[berg (berg-foss)]

something aobout ath_hal and notification

[Raúl Soriano (gatoloko)]

This is happening multiple times per day to me and is becoming very annoying.

 $ dmesg | grep notification-da | wc -l
134
 $ dmesg | tail -n2
[100009.325183] notification-da[26838]: segfault at 0000000000000058 rip 00002ad8f352d2ff rsp 00007fffbe4d9690 error 4
[100009.947193] notification-da[26853]: segfault at 0000000000000058 rip 00002af88cec52ff rsp 00007fff24b41cf0 error 4

[Sebastien Bacher (seb128)]

what is the use of such comments? You should use a stable distribution if avoid a crash every now and then is annoying to you

[Raúl Soriano (gatoloko)]

2007/7/28, Sebastien Bacher <email address hidden>:
>
> what is the use of such comments? You should use a stable distribution
> if avoid a crash every now and then is annoying to you
>

What is the use of a comment that only is questioning the use of another
comment? (like this line)

May be knowing that it happens frequently is of any use to somebody, may be
not, but since nobody said it I wanted to do so. You can ignore the rest of
the comment or even entirely if you want.

And for "annoying", i have used the wrong word, I forgot to check that the
meaning matched what i wanted to say, so don't get me wrong, Remember that
some of us don't have English as our mother language and this things happens
sometimes.

I now doubt how to say it when something is very repetitive, and I'm not
going to try because you can take it wrong.

Remember to take it easy guy and forgive me if I made another mistake in
this message.

--
Raúl Soriano (GatoLoko), SpainTeam Local Community Contact.
http://www.ubuntu-spain.org - http://wiki.ubuntu.com/GatoLoko

[Sebastien Bacher (seb128)]

The bug has 18 duplicates, is marked high importance and is milestone for next tribe, it's clear that the distribution teams knows about it. Extra comments to confirm the bug is happening or say it's an annoying one are of no real use in this context. No problem about your english and thank you for your in interest in Ubuntu!

[ChrisKelley (ckelley)]

fyi: i have amd_64 install on Dell D630 (intel core-duo), so isn't restricted to 32 bit. Further, the only action happening was i had the add/remove programs dialog open and this crash notifier came up (seeming unrelated to anything i was doing -- and no effect on add/remove programs). This is a clean install of ubuntu and the only mod was to remove the former video package and add video-xorg-intel for the 1440x900 screen resolution (which worked perfectly - will look for a bug to make good report on that). thanks chris

[Laurent Bigonville (bigon)]

Bug #128052 has a workaround which works for me

[Mikael Nilsson (mini)]

Workaround works for me too:

   After changing the theme using gconf-editor (/apps/notification-daemon/theme) from "ubuntu" to "Ubuntu", everything works again.
   Can someone check this behavior?

   Regards, Charles

[grendelkhan (scottricketts)]

Like a champ!
On Sun, 2007-07-29 at 15:56 +0000, Mikael Nilsson wrote:

> Workaround works for me too:
>
> After changing the theme using gconf-editor (/apps/notification-daemon/theme) from "ubuntu" to "Ubuntu", everything works again.
> Can someone check this behavior?
>
> Regards, Charles
>

[traherom (morehart)]

Fixes things here, thanks a ton!

Ryan

On 7/29/07, Mikael Nilsson <email address hidden> wrote:
>
> Workaround works for me too:
>
> After changing the theme using gconf-editor
> (/apps/notification-daemon/theme) from "ubuntu" to "Ubuntu", everything
> works again.
> Can someone check this behavior?
>
> Regards, Charles
>

[Laurent Bigonville (bigon)]

Actually setting the key to "Ubuntu" makes notification-daemon to defaulting the standard theme

[Mikael Nilsson (mini)]

mån 2007-07-30 klockan 11:03 +0000 skrev Laurent Bigonville:
> Actually setting the key to "Ubuntu" makes notification-daemon to
> defaulting the standard theme

Yes. I see only two themes installed: "ubuntu" and "standard". So It
should work to set that key to "standard" as well.

/Mikael

>
--
<email address hidden>

Plus ça change, plus c'est la même chose

[Gabriel Speckhahn (gabspeck)]

Rhythmbox is not showing any notifications when the song changes because of this...

[Michael Vogt (mvo)]

Thanks for your bugreport,

fixed in my local branch and will be part of the next upload.

Cheers,
 Michael

[Michael Vogt (mvo)]

notification-daemon (0.3.7-1ubuntu3) gutsy; urgency=low

  * fix crash in ubuntu theme (caused by gtk+ changes
    in the way tooltips are handled). Closes LP: #127925

 -- Michael Vogt <email address hidden> Tue, 31 Jul 2007 15:20:36 +0200