[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#310048: marked as done (kicker: sometimes eats 100% CPU after logout from KDE)

Your message dated Thu, 11 Jan 2007 09:20:06 +0100
with message-id <20070111082006.GA9520@pryan.sytes.net>
and subject line Bug#310048: About your bug: "kicker: sometimes eats 100% CPU after logout from KDE" on the Debian BTS
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kicker
Version: 4:3.3.2-1
Severity: important

Sometimes after I log out from KDE, the kicker remains hanging and
starts eating 100% CPU. It doesn't die off even when I log in again,
so I have to kill it with SIGKILL. This happens or not happens without
obvious reasons, and the probability of hanging seems to be about 50%.

I've tried attaching to the hanging kicker process to find out what's
it busy with. Using strace has shown that it's not doing any syscalls.
Here is what I found out with gdb:

0x4b7b8332 in mallopt () from /lib/tls/i686/cmov/libc.so.6
(gdb) up
#1  0x4b7b817e in mallopt () from /lib/tls/i686/cmov/libc.so.6
(gdb) up
#2  0x4b7b6ffb in free () from /lib/tls/i686/cmov/libc.so.6
(gdb) up
#3  0x45c7eed8 in QImage::freeBits () from /usr/lib/libqt-mt.so.3
(gdb) up
#4  0x45c7e6aa in QImage::reset () from /usr/lib/libqt-mt.so.3
(gdb) up
#5  0x45c7dfeb in QImage::~QImage () from /usr/lib/libqt-mt.so.3
(gdb) up
#6  0xb7b42da2 in TaskBarContainer::sizeHint () from /usr/lib/libtaskbar.so.1
(gdb) up
#7  0x4b7701d2 in exit () from /lib/tls/i686/cmov/libc.so.6
(gdb) up
#8  0x463b3203 in _kde_IceDefaultIOErrorHandler () from /usr/lib/libDCOP.so.4
(gdb) up
#9  0x463b4822 in _kde_IceWrite () from /usr/lib/libDCOP.so.4
(gdb) up
#10 0x463b4355 in KDE_IceFlush () from /usr/lib/libDCOP.so.4
(gdb) up
#11 0x463ab35c in DCOPClient::callInternal () from /usr/lib/libDCOP.so.4
(gdb) up
#12 0x463aaafc in DCOPClient::callInternal () from /usr/lib/libDCOP.so.4
(gdb) up
#13 0x463aa5c5 in DCOPClient::call () from /usr/lib/libDCOP.so.4
(gdb) up
#14 0x463aa3ea in DCOPClient::call () from /usr/lib/libDCOP.so.4
(gdb) up
#15 0x463ac222 in DCOPClient::disconnectDCOPSignal () from /usr/lib/libDCOP.so.4
(gdb) up
#16 0x463a008e in DCOPObject::~DCOPObject () from /usr/lib/libDCOP.so.4
(gdb) up
#17 0xb79333a6 in KMFactory::~KMFactory () from /usr/lib/libkdeprint.so.4
(gdb) up
#18 0xb793673f in KStaticDeleter<KMFactory>::destructObject () from /usr/lib/libkdeprint.so.4
(gdb) up
#19 0x46273825 in KGlobal::deleteStaticDeleters () from /usr/lib/libkdecore.so.4
(gdb) up
#20 0x461e13ac in KApplication::~KApplication () from /usr/lib/libkdecore.so.4
(gdb) up
#21 0x46282157 in KUniqueApplication::~KUniqueApplication () from /usr/lib/libkdecore.so.4
(gdb) up
#22 0x46b513e8 in Kicker::~Kicker () from /usr/lib/libkdeinit_kicker.so
(gdb) up
#23 0x46b4f441 in kdemain () from /usr/lib/libkdeinit_kicker.so
(gdb) up
#24 0xb7ff88a6 in kdeinitmain () from /usr/lib/kde3/kicker.so
(gdb) up
#25 0x0804cd30 in ?? ()

If you need more debugging information of some kind, or information
about my system configuration, just write what info you need, I'll try
to collect it.


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages kicker depends on:
ii  kdebase-data              4:3.3.2-1      KDE Base (shared data)
ii  kdelibs4                  4:3.3.2-5      KDE core libraries
ii  libart-2.0-2              2.3.17-1       Library of functions for 2D graphi
ii  libc6                     2.3.2.ds1-21   GNU C Library: Shared libraries an
ii  libfam0c102               2.7.0-6        client library to control the FAM 
ii  libgcc1                   1:3.4.3-12     GCC support library
ii  libice6                   6.8.2-5.1      Inter-Client Exchange library
ii  libidn11                  0.5.13-1.0     GNU libidn library, implementation
ii  libkonq4                  4:3.3.2-1      Core libraries for KDE's file mana
ii  libpng12-0                1.2.8rel-1     PNG library - runtime
ii  libqt3c102-mt             3:3.3.4-3      Qt GUI Library (Threaded runtime v
ii  libsm6                    6.8.2-5.1      X Window System Session Management
ii  libstdc++5                1:3.3.5-12     The GNU Standard C++ Library v3
ii  libx11-6                  6.8.2-5.1      X Window System protocol client li
ii  libxext6                  6.8.2-5.1      X Window System miscellaneous exte
ii  libxrender1               0.9.0-0ubuntu4 X Rendering Extension client libra
ii  libxtst6                  6.8.2-5.1      X Window System event recording an
ii  xlibs                     6.8.2-5.1      X Window System client libraries m
ii  zlib1g                    1:1.2.2-4      compression library - runtime

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 4:3.3.2-1

On Wed, Jan 10, 2007 at 02:50:31AM +0100, Alexey Feldgendler wrote:
> On Tue, 09 Jan 2007 19:27:45 +0100, Ana Guerrero <ana-bugkde@debian.org>  
> wrote:
> 
> >So please respond to this mail and tell us if:
> >
> >- you are still experiencing this bug (adding in what version)
> >- the bug was already fixed,
> >- or if you have extra information on how reproduce this bug.
> 
> I stopped using KDE about a year ago. Can't tell if the bug is still there.
> 

Ok, thanks for the answer anyway. I have not found any bug similar to
this on the kde bugzilla and nobody else has reported this bug in
Debian, so i'm closing it.

Ana

--- End Message ---
Reply to: