Closing as Invalid based on the reporter's last comment.
** Changed in: notification-daemon (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/58445
Title:
c
Just going through my old related bugs... I did not encounter this
problem for quite some time (possibly years). So for all I care, this
could be closed.
--
crashed after clicking on crash symbol
https://bugs.launchpad.net/bugs/58445
You received this bug notification because you are a member of
Adding debug backtrace:
--- stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Core was generated by `/usr/lib/notification-daemon/notification-daemon'.
Program terminated with signal 11, Segmentation fault.
#0 0xb7f0d6cc in dbus_g_method_return_error (context
"Me too." The attached crash report actually does seem to contain a
backtrace.
** Attachment added: "Crash report with backtrace"
http://librarian.launchpad.net/5581132/_usr_lib_notification-daemon_notification-daemon.1000.crash
--
crashed after clicking on crash symbol
https://launchpad.ne
apport stopped producing crash files for those at the moment. The issue
is that apport tries to write the coredump to the directory and in case
of such daemon the user has not the permission to write to the system
directory so there is no coredump available. You can open a wishlist on
apport about
Okay... I thought that they could be apport-retrace'd,
(
http://www.archivesat.com/Ubuntu_Linux_Developer_Discussion/thread1775644.htm
)
but it seems that these ones cannot be. Apparently they "don't contain
core dumps".
So hear's the next question - why don't they contain everything that is
nee
We need a backtrace for this kind of crash.
http://wiki.ubuntu.com/Backtrace
Unfortunately the crash reports are all useless. :-/
--
crashed after clicking on crash symbol
https://launchpad.net/bugs/58445
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
Same here. Happened today (6/10) after I rebooted the system from the
command line with CTRL+ALT+DEL while X was still running.
** Attachment added: "crash report"
http://librarian.launchpad.net/4684463/_usr_lib_notification-daemon_notification-daemon.1000.crash
--
crashed after clicking on
I had the same problem today (03/10) with a fully updated system. It was
also after doing a CTRL+ALT+BKSP.
** Attachment added: "Aaron's crash report"
http://librarian.launchpad.net/4605391/_usr_lib_notification-daemon_notification-daemon.1000.crash
--
crashed after clicking on crash symbol
I have the same problem with a fully updated system as of today (9/17).
This was after doing a CTRL+ALT+BKSP.
-Ben
--
crashed after clicking on crash symbol
https://launchpad.net/bugs/58445
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubun
Will do. (Weird feeling, actually _waiting_ for the next crash... :)
Ciao
Martin
--
crashed after clicking on crash symbol
https://launchpad.net/bugs/58445
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for your bugreport.
This problem should be fixed with the latest version of notification-
daemon. Can you please check that you run it and that you have rebootet
since the new notification-daemon was installed (so that the new code is
actually runing)?
Thanks,
Michael
** Changed in: noti
I see this too, on Edgy.
--
crashed after clicking on crash symbol
https://launchpad.net/bugs/58445
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
crashed after clicking on crash symbol
https://launchpad.net/bugs/58445
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
14 matches
Mail list logo
