[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 128529] New: GstEngine plugin floods .xsession-errors with
From:       Jens Zurheide <jens.zurheide () gmx ! de>
Date:       2006-06-02 21:36:17
Message-ID: 20060602233615.128529.jens.zurheide () gmx ! de
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=128529         
           Summary: GstEngine plugin floods .xsession-errors with "QObject:
                    30 timers now exist for object GstEngine::unnamed" if
                    display power management was triggered
           Product: amarok
           Version: 1.4-SVN
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: amarok-bugs-dist lists sourceforge net
        ReportedBy: jens.zurheide gmx de


Version:           1.4-SVN (using KDE 3.5.2, compiled sources)
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.13-15-smp

I have observed that amarok when running with the GstEngine plugin and alsasink seems \
to have severe problems with either the screensaver or the power-saving feature.  \
This problem is reproducible on my machine if I start amarok and let it play a couple \
of mp3 files and do other things for a longer time so that the monitor is switched \
off by the power management of KDE. After that the problems occurs. I receive \
literally millions of entries of the form

QObject: 21 timers now exist for object GstEngine::unnamed
QObject: 20 timers now exist for object GstEngine::unnamed
QObject: 19 timers now exist for object GstEngine::unnamed
QObject: 18 timers now exist for object GstEngine::unnamed
QObject: 17 timers now exist for object GstEngine::unnamed
QObject: 36 timers now exist for object GstEngine::unnamed
QObject: 35 timers now exist for object GstEngine::unnamed
QObject: 34 timers now exist for object GstEngine::unnamed
QObject: 33 timers now exist for object GstEngine::unnamed
QObject: 32 timers now exist for object GstEngine::unnamed
QObject: 31 timers now exist for object GstEngine::unnamed
QObject: 30 timers now exist for object GstEngine::unnamed
QObject: 29 timers now exist for object GstEngine::unnamed
QObject: 28 timers now exist for object GstEngine::unnamed
QObject: 27 timers now exist for object GstEngine::unnamed

in my .xsession-errors file leading to an increase of 10 MB/5 min. Letting the \
computer run over night without logging off I found a file in the size of 1 GB.

If you need parts of the .xsession-errors file please let me know.

Regards,
Jens


[prev in list] [next in list] [prev in thread] [next in thread]