Notification-daemon Crashed (Check crashreport for BACKTRACE)

Bug #62488 reported by Petr Tomeš
34
This bug affects 1 person
Affects Status Importance Assigned to Milestone
notification-daemon (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Crash on current edgy.

Revision history for this message
Petr Tomeš (ptomes) wrote :
Revision history for this message
John Leach (johnleach) wrote :

Crash here too. I don't think I did anything noteworthy to cause it.

Additionally, as I was reading over the crash report another 10 crash reports popped up for the same program.

Changed in notification-daemon:
status: Unconfirmed → Confirmed
Michael Vogt (mvo)
Changed in notification-daemon:
importance: Undecided → Medium
Revision history for this message
Tom Veens (tomveens) wrote : Re: Notification-daemon Crashed

I did not notice anything but then there was a message that said that the notification deamon crashed.
Here is the crash report:

Revision history for this message
_SpYkE_ (spyke248-gmail) wrote :

Noticiation-Daemon se cierra inesperadamente.... y no da fallo aparente

Changed in notification-daemon:
assignee: nobody → spyke248-gmail
Revision history for this message
Adrian Macneil (amacneil) wrote :

Is this a dupe of bug #58445?

Revision history for this message
ranespa (felici-alex) wrote : Crash on crash. Domino effect?

I don't know if this is a duplicate of bug #58445 or if it is related to bug #64329 reported by me. I may just say that I closed session in a clean way after a Gaim crash. I leave you an attachment.

Revision history for this message
Peter Levi (peterlevi) wrote : Re: Notification-daemon Crashed

Crash happened once here too, on XFCE startup

Revision history for this message
Daniel Holbach (dholbach) wrote :

Please don't assign bugs to you unless you intend to work on them. I'm sorry to say it, but all the crash reports are useless. We need on containing a backtrace.

Changed in notification-daemon:
assignee: spyke248-gmail → nobody
Revision history for this message
Daniel Holbach (dholbach) wrote :

Without having a backtrace, it's hard to say if bug 58445 is a duplicate or not.

Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in notification-daemon:
status: Confirmed → Incomplete
Revision history for this message
Ralph Janke (txwikinger) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in notification-daemon (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. My apologies as I should not have marked this Invalid. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Changed in notification-daemon (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for notification-daemon (Ubuntu) because there has been no activity for 60 days.]

Changed in notification-daemon (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.