KNotify crashed while instantiating KNotify

Bug #21095 reported by Ron Strenger
30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdelibs (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

During the previous startup, KNotify crashed while instantiating KNotify. Do you
want to try again or disable aRts sound output?
If you choose to disable aRts output now, you can re-enable it later or select
an alternate sound player in the System Notifications control panel.

### I was running KolourPaint and then tried closing it without saving after
scribbling in it and this prompt above in the process.

Revision history for this message
Jonathan Riddell (jr) wrote :

Do you still have this problem in breezy final?

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Does this still happen with dapper? If you can reproduce it, try obtaining a backtrace following the instructions here. https://wiki.ubuntu.com/DebuggingProgramCrash Thanks.

Revision history for this message
Loïc Martin (loic-martin3) wrote :

I have the same problem here with Feisty Beta (it happenned before, but I didn't file a bug) when starting amarok for the first time. Then it propose me to disable arts output, and if I agree it seems ok afterwards.

Revision history for this message
Sir Nikon (omnineko) wrote :

I saw this thread earlier today while trying to figure out why this KNotify window kept popping up. I couldn't get it to reproduce itself because it seemed totally random. I noticed that it popped up after clicking the Close icon in the top right corner of the window (clicking it to close the window and leave Amarok in the tray). It happens every time I click that and it also seems to happen at random.

Revision history for this message
libertyernie (libertyernie) wrote :

Workaround: Tell it to disable arts and check the "don't ask again" box. Still seems to work fine on Ubuntu feisty.

Revision history for this message
Guillaume Martres (smarter) wrote :

Do you still have this problem with gutsy?

Revision history for this message
notman (notman05) wrote :

I've still experienced it in Gutsy... quite often actually. It's typically whenever I get a messagebox, like 'Do you want to save before closing?' in kMyMoney or when Evolution wants to tell me that I have a new message.

Revision history for this message
schumifer (schumifer2121) wrote :

Got here searching for a solution to the same problem. I had no sound and i got the message about knotifier each time i control+alt+backspaced.
Finally i reboot later it was all back to normal. At the time i acquired the problem i was merely browsing...... During, the issue i had no sound , in any application....

Revision history for this message
schumifer (schumifer2121) wrote :

Got here searching for a solution to the same problem. I had no sound and i got the message about knotifier each time i control+alt+backspaced.
Finally i reboot later it was all back to normal. At the time i acquired the problem i was merely browsing...... During, the issue i had no sound , in any application....gutsy amd64 kubuntu

Revision history for this message
hornetster (hornetster) wrote :

Have just installed 8.04 (32bit?) on Core2Duo and have been getting this error intermittently. Not sure what is causing it. Will try and take note next time around. Sound still seems fine.

Revision history for this message
Revup (revups) wrote :

I'm getting this problem in 8.10 Intrepid. the exact same report. However, I have no idea where the "system notifications panel" is.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Closing because:
-A proper backtrace was never made.
-The most likely cause of the crash was aRts, which is unmaintained upstream.

Any further knotify crashes are probably unrelated to this one and should get their own reports, along with a backtrace from a system with kdelibs5-dbg installed. Thank you.

Changed in kdelibs:
assignee: jr → nobody
status: Confirmed → Invalid
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.