Bug 275034 - knotify spams .xsession-errors and thus causes KDE(-apps) to crash
Summary: knotify spams .xsession-errors and thus causes KDE(-apps) to crash
Status: RESOLVED DUPLICATE of bug 273529
Alias: None
Product: phonon-backend-gstreamer
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: Torrie Fischer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-06 10:06 UTC by S. Burmeister
Modified: 2012-02-15 09:46 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description S. Burmeister 2011-06-06 10:06:10 UTC 
Version:           unspecified (using KDE 4.6.3) 
OS:                Linux

While akonadi/kontact were trying to remove emails from my trash they issued a lot of notifications. Within minutes knotify filled-up .xsession-errors with GBs of the same notification until my /home was full and apps started to behave funny. the .xsession-errors grew to ~7 GB.

Having no space left on /home can lead to data-loss and writing the same notification into .xsession-errors is of no value.

The notification is:

(knotify4:2309): GStreamer-CRITICAL **: gst_poll_write_control: assertion `set != NULL' failed

(knotify4:2309): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again : 24:Zu viele offene Dateien

"Zu viele offene Dateien" means: too many open files.

Expected behaviour: for repeating messages, write to .xsession-errors only once every minute stating something like "the last message was repeated 200 times"

Reproducible: Always
Comment 1 Torrie Fischer 2011-09-19 12:31:15 UTC 
This actually looks like an upstream gstreamer bug. You shouldn't be getting so many asserts. I'm afraid there isn't much we can do about the logging, but think you could post a bigger sample of the logs?
Comment 2 Torrie Fischer 2011-09-19 13:25:38 UTC 
Adjusting the status, pardon the noise.
Comment 3 Blindauer Emmanuel 2012-02-15 06:18:31 UTC 
It's probably the same as bug 273529
Comment 4 Myriam Schweingruber 2012-02-15 09:46:15 UTC 
(In reply to comment #3)
> It's probably the same as bug 273529

Well spotted, thank you :)

*** This bug has been marked as a duplicate of bug 273529 ***