Bug 273529 - knotify4 random crashes and dumps following to console where startkde was run..
Summary: knotify4 random crashes and dumps following to console where startkde was run..
Status: RESOLVED DOWNSTREAM
Alias: None
Product: phonon-backend-gstreamer
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.5.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Harald Sitter
URL:
Keywords:
: 275034 (view as bug list)
Depends on: 216130
Blocks:
  Show dependency treegraph
 
Reported: 2011-05-18 02:48 UTC by onigino
Modified: 2012-02-15 09:46 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description onigino 2011-05-18 02:48:36 UTC
Version:           4.6 (using Devel) 
OS:                Linux


wn>:15310): GStreamer-CRITICAL **: gst_poll_write_control: assertion `set != NULL' failed

(<unknown>:15310): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again : 24:Too many open files


(<unknown>:15310): GStreamer-CRITICAL **: gst_poll_write_control: assertion `set != NULL' failed

(<unknown>:15310): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again : 24:Too many open files

seems to go on forever, had to kill knotify4 to resolve issue.

slackware64-current w/kde4.6.3 compiled from source.

Reproducible: Sometimes

Steps to Reproduce:
randomly happens, i'll be away from the computer, come back and see escalated cpu usage and this stream above dumped to my xterm where i spawned startkde


Actual Results:  
killing knotify4 seems to fix the issue.. if you can call that a fix
Comment 1 onigino 2011-05-18 02:49:26 UTC
15302 xxx      20   0  633m 111m  47m S   73  2.8 205:51.47 kwin -session 10c9dedade00013055404440
15140 xxx      20   0 59300 3940 2248 D   55  0.1 146:47.46 xterm -e startkde                     
15310 xxx      20   0 3962m 149m  29m S   29  3.8  90:13.21 /usr/bin/knotify4
Comment 2 Bartosz Brachaczek 2011-06-22 20:36:34 UTC
Might be related to bug 216130. See bug 216130 comment 17.
Comment 3 Myriam Schweingruber 2011-06-23 10:02:59 UTC
Setting dependency
Comment 4 Wolfgang Rohdewald 2011-10-09 08:45:20 UTC
this is still so with kubuntu oneiric, pre-kde4.7.2
the .xsession-errors file grows by about 1 GB per minute 
(using an SSD)

so at least throttling the output of identical messages should be fixed like

ERROR MESSAGE
...repeated 145235423 times

after the disk was full, kmail2/akonadi/whatever was corrupt, I had to clean and reinstall everything related to mail and akonadi. Just a few tens of thousands of mails...

So IMHO this is a very serious bug.
Comment 5 Stephane MANKOWSKI 2011-12-21 12:05:44 UTC
Problem reproduced 2 or 3 times per day on on kubuntu 11.10 (kde 4.7.3).

Here are the repeated traces in .xsession-errors:
(knotify4:15723): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again : 24:Trop de fichiers ouverts


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

(knotify4:15723): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again : 24:Trop de fichiers ouverts


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

(knotify4:15723): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again : 24:Trop de fichiers ouverts


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

(knotify4:15723): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again : 24:Trop de fichiers ouverts
Comment 6 Myriam Schweingruber 2011-12-21 17:55:49 UTC
Did you report this downstream to the distribution? Apparently this is a gstreamer problem and not a Phonon one.
I use the Phonon-backend-vlc and have never come accross that problem.
Comment 7 Torrie Fischer 2012-01-17 15:36:53 UTC
Yup, this is a gstreamer issue. Check with your packagers.
Comment 8 Myriam Schweingruber 2012-02-15 09:46:15 UTC
*** Bug 275034 has been marked as a duplicate of this bug. ***