kicker crashes after upgrading to KDE 3.5.10

Bug #261694 reported by Montblanc on 2008-08-27
Affects Status Importance Assigned to Milestone
kicker-taskbar-compiz (Ubuntu)

Bug Description

Binary package hint: kicker

Few minutes ago I did a dist-upgrade and noticed that KDE was updated to 3.5.10. When I restarted the session/rebooted I got this error message "The application KDE panel (kicker) crashed and caused the signal 11 (SIGSEGV)". It also happens if I try to run it from shell, in that case I get this output:

kicker: crashHandler called
KCrash: Application 'kicker' crashing...

This is the backtrace:
[KCrash handler]
#6 0xb6fd9c25 in QApplication::internalNotify () from /usr/lib/
#7 0xb6fdba5f in QApplication::notify () from /usr/lib/
#8 0xb779b9b2 in KApplication::notify () from /usr/lib/
#9 0xb6f6a28d in QApplication::sendEvent () from /usr/lib/
#10 0xb6fccb19 in QEventLoop::activateTimers () from /usr/lib/
#11 0xb6f7f64b in QEventLoop::processEvents () from /usr/lib/
#12 0xb6ff4f90 in QEventLoop::enterLoop () from /usr/lib/
#13 0xb6ff4c8e in QEventLoop::exec () from /usr/lib/
#14 0xb6fdb7df in QApplication::exec () from /usr/lib/
#15 0xb7ed91a7 in kdemain () from /usr/lib/
#16 0x080484b2 in ?? ()
#17 0xb7c04450 in __libc_start_main () from /lib/tls/i686/cmov/
#18 0x08048421 in ?? ()

kicker starts for a few seconds, and when it tries to load tray icons (or simultaneously, I don't know if tray icons are the real problem) it suddenly crashes. I don't know if this could help: I once edited one line from /usr/share/autostart/panel.desktop from




But I'm sure it isn't compiz fault. Everything else works just fine, but KDE without kicker is not KDE...

[lsb_release -rd]
Description: Ubuntu 8.04.1
Release: 8.04

[apt-cache policy kicker]
  Installato: 4:3.5.10-0ubuntu1~hardy1
  Candidato: 4:3.5.10-0ubuntu1~hardy1
  Tabella versione:
 *** 4:3.5.10-0ubuntu1~hardy1 0
        500 hardy-backports/main Packages
        100 /var/lib/dpkg/status
     4:3.5.9-0ubuntu7.3 0
        500 hardy-updates/main Packages
     4:3.5.9-0ubuntu7 0
        500 hardy/main Packages

scido (domi-mailing-list) wrote :

I got the same problem after upgrading. It seems to be related to the taskbar-compiz. After deleting taskbar-compiz from my panel, I don't have any crash. If I try to insert taskbar-compiz in my panel, it crashes.


Montblanc (montblanc) wrote :

Thank you, scido.

sudo apt-get remove --purge kicker-taskbar-compiz

solved the problem. I'll wait until they'll fix this package before reinstalling it.


Scott Kitterman (kitterman) wrote :

Looks like it needs to be rebuilt to use the new kdelibs version.

Scott Kitterman (kitterman) wrote :

I rebuilt it and I've got an i386 test .deb here:

The md5sum is:

c4dba17aa3d27e15f9906d546726ceee kicker-taskbar-compiz_0.1-0ubuntu2~hardy1~test1_i386.deb

Please verify this before installing by running:

md5sum kicker-taskbar-compiz_0.1-0ubuntu2~hardy1~test1_i386.deb and seeing that you get the same result.

If you are on i386 and you've had this problem, please give it a try and report back.

Montblanc (montblanc) wrote :

Hi Scott, thank you for your efforts. I installed your deb and tried to integrate the applet into kicker: kicker crashed immediately, but restarted again without compiz-taskbar.

Scott Kitterman (kitterman) wrote :

OK. So much for that theory then.

Scott Kitterman (kitterman) wrote :

Would you please install kdebase-dbg (the debug package) and then make it crash again. Maybe we can get a better backtrace.

jrtokarz (jrtokarz1) wrote :
Download full text (10.9 KiB)

As requested (with kdebase-dbg) backtrace:

[Thread debugging using libthread_db enabled]
[New Thread 0xb67fd6c0 (LWP 7713)]
[KCrash handler]
#6 0x081b675a in ?? ()
#7 0xb71a1a5f in QApplication::notify (this=0x808cc70, receiver=0x81b0000,
    e=0xbfdaa4f8) at kernel/qapplication.cpp:2361
#8 0xb78a59b2 in KApplication::notify (this=0x808cc70, receiver=0x81b0000,
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#9 0xb713028d in QApplication::sendEvent (receiver=0x81b0000,
    event=0xbfdaa4f8) at ../include/qapplication.h:523
#10 0xb7192b19 in QEventLoop::activateTimers (this=0x80d67e0)
    at kernel/qeventloop_unix.cpp:559
#11 0xb714564b in QEventLoop::processEvents (this=0x80d67e0, flags=0)
    at kernel/qeventloop_x11.cpp:392
#12 0xb71baf02 in QEventLoop::processEvents (this=0x80d67e0, flags=0,
    maxTime=3000) at kernel/qeventloop.cpp:261
#13 0xb71a184a in QApplication::processEvents (this=0x808cc70, maxtime=3000)
    at kernel/qapplication.cpp:2696
#14 0xb71a1875 in QApplication::processEvents (this=0x808cc70)
    at kernel/qapplication.cpp:2680
#15 0xb6621abc in ExtensionContainer::autoHide (this=0x822abf8, hide=true)
    at /build/buildd/kdebase-3.5.10/./kicker/kicker/core/container_extension.cpp:840
#16 0xb6621ca4 in ExtensionContainer::autoHideTimeout (this=0x822abf8)
    at /build/buildd/kdebase-3.5.10/./kicker/kicker/core/container_extension.cpp:737
#17 0xb6628e44 in ExtensionContainer::qt_invoke (this=0x822abf8, _id=53,
    _o=0xbfdaa908) at ./container_extension.moc:170
#18 0xb720b704 in QObject::activate_signal (this=0x823ec20, clist=0x823e808,
    o=0xbfdaa908) at kernel/qobject.cpp:2359
#19 0xb720c1e9 in QObject::activate_signal (this=0x823ec20, signal=2)
    at kernel/qobject.cpp:2328
#20 0xb759d320 in QTimer::timeout (this=0x823ec20)
    at .moc/debug-shared-mt/moc_qtimer.cpp:82
#21 0xb7232d0e in QTimer::event (this=0x823ec20, e=0xbfdaac08)
    at kernel/qtimer.cpp:222
#22 0xb719fc36 in QApplication::internalNotify (this=0x808cc70,
    receiver=0x823ec20, e=0xbfdaac08) at kernel/qapplication.cpp:2638
#23 0xb71a1a5f in QApplication::notify (this=0x808cc70, receiver=0x823ec20,
    e=0xbfdaac08) at kernel/qapplication.cpp:2361
#24 0xb78a59b2 in KApplication::notify (this=0x808cc70, receiver=0x823ec20,
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#25 0xb713028d in QApplication::sendEvent (receiver=0x823ec20,
    event=0xbfdaac08) at ../include/qapplication.h:523
#26 0xb7192b19 in QEventLoop::activateTimers (this=0x80d67e0)
    at kernel/qeventloop_unix.cpp:559
#27 0xb714564b in QEventLoop::processEvents (this=0x80d67e0, flags=0)
    at kernel/qeventloop_x11.cpp:392
#28 0xb71baf02 in QEventLoop::processEvents (this=0x80d67e0, flags=0,
    maxTime=3000) at kernel/qeventloop.cpp:261
#29 0xb71a184a in QApplication::processEvents (this=0x808cc70, maxtime=3000)
    at kernel/qapplication.cpp:2696
#30 0xb71a1875 in QApplication::processEvents (this=0x808cc70)
    at kernel/qapplication.cpp:2680
#31 0xb6621abc in ExtensionContainer::autoHide (this=0x8141d88, hide=true)
    at /build/buildd/kdebase-3.5.10/./kicker/kicker/core/container_exte...

jrtokarz (jrtokarz1) wrote :

additional note, this debug trace is with the 'patched' version of 'kicker-taskbar-compiz' as supplied by Mr Kitterman.

Montblanc (montblanc) wrote :
Download full text (3.5 KiB)

Scott, I installed kdebase-dbg as you said. Here are the results:

[apt-cache policy kicker-taskbar-compiz]
  Installato: 0.1-0ubuntu1
  Candidato: 0.1-0ubuntu1
  Tabella versione:
 *** 0.1-0ubuntu1 0
        500 hardy/universe Packages
        100 /var/lib/dpkg/status
[Thread debugging using libthread_db enabled]
[New Thread 0xb661a6c0 (LWP 11861)]
[New Thread 0xb4671b90 (LWP 11869)]
[New Thread 0xb4e72b90 (LWP 11868)]
[New Thread 0xb5673b90 (LWP 11867)]
[New Thread 0xb5e74b90 (LWP 11866)]
[KCrash handler]
#6 0xb6fc2c25 in QApplication::internalNotify (this=0x80575e0,
    receiver=0x81d0100, e=0xbf90c238) at kernel/qapplication.cpp:2638
#7 0xb6fc4a5f in QApplication::notify (this=0x80575e0, receiver=0x81d0100,
    e=0xbf90c238) at kernel/qapplication.cpp:2361
#8 0xb77849b2 in KApplication::notify (this=0x80575e0, receiver=0x81d0100,
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#9 0xb6f5328d in QApplication::sendEvent (receiver=0x81d0100,
    event=0xbf90c238) at ../include/qapplication.h:523
#10 0xb6fb5b19 in QEventLoop::activateTimers (this=0x805c990)
    at kernel/qeventloop_unix.cpp:559
#11 0xb6f6864b in QEventLoop::processEvents (this=0x805c990, flags=4)
    at kernel/qeventloop_x11.cpp:392
#12 0xb6fddf90 in QEventLoop::enterLoop (this=0x805c990)
    at kernel/qeventloop.cpp:201
#13 0xb6fddc8e in QEventLoop::exec (this=0x805c990)
    at kernel/qeventloop.cpp:148
#14 0xb6fc47df in QApplication::exec (this=0x80575e0)
    at kernel/qapplication.cpp:2761
#15 0xb7ec21a7 in kdemain (argc=1, argv=0xbf90c6a4)
    at /build/buildd/kdebase-3.5.10/./kicker/kicker/core/main.cpp:150
#16 0x080484b2 in main (argc=-1219641536, argv=0x1) at

[apt-cache policy kicker-taskbar-compiz]
  Installato: 0.1-0ubuntu2~hardy1~test1
  Candidato: 0.1-0ubuntu2~hardy1~test1
  Tabella versione:
 *** 0.1-0ubuntu2~hardy1~test1 0
        100 /var/lib/dpkg/status
     0.1-0ubuntu1 0
        500 hardy/universe Packages

[Thread debugging using libthread_db enabled]
[New Thread 0xb664d6c0 (LWP 12866)]
[New Thread 0xb46a4b90 (LWP 12874)]
[New Thread 0xb4ea5b90 (LWP 12873)]
[New Thread 0xb56a6b90 (LWP 12872)]
[New Thread 0xb5ea7b90 (LWP 12871)]
[KCrash handler]
#6 0xb6ff5c25 in QApplication::internalNotify (this=0x80575e0,
    receiver=0x8310100, e=0xbfdb26e8) at kernel/qapplication.cpp:2638
#7 0xb6ff7a5f in QApplication::notify (this=0x80575e0, receiver=0x8310100,
    e=0xbfdb26e8) at kernel/qapplication.cpp:2361
#8 0xb77b79b2 in KApplication::notify (this=0x80575e0, receiver=0x8310100,
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#9 0xb6f8628d in QApplication::sendEvent (receiver=0x8310100,
    event=0xbfdb26e8) at ../include/qapplication.h:523
#10 0xb6fe8b19 in QEventLoop::activateTimers (this=0x805c990)
    at kernel/qeventloop_unix.cpp:559
#11 0xb6f9b64b in QEventLoop::processEvents (this=0x805c990, flags=4)
    at kernel/qeventloop_x11.cpp:392
#12 0xb7010f90 in QEventLoop::enterLoop (this=0x805c990)
    at kernel/qeventloop.cpp:20...


Scott asked me to look at the backtraces. It LOOKS like this is two separate regressions vs. one nice one, given the difference in back traces.

Some detective work tells me that kicker ( got a rather massive change in it .9 to .10, so it probably broke compiz.

Some futher investigation relieves its likely kicker/core/containerarea.cpp that contains the change that broke compiz and kdelib due to it being one of the changed files in kicker 3.5.10, and one of the last files it leaves before Qt goes and cries in the corner.

Montblanc (montblanc) wrote :

Understood. Moral: I'll keep the original taskbar till some work on kicker-taskbar-compiz will be done. Shouldn't be that big problem since kicker runs and stays up.

Scott Kitterman (kitterman) wrote :
description: updated
jay armstrong (jayarmstrong) wrote :
Download full text (5.0 KiB)

I'm in the same boat but so far I can't stop it from crashing.

Initially, I uninstalled fusion-icon to no avail. Then "sudo apt-get remove --purge kicker-taskbar-compiz" seemed to work, as it stopped crashing for a few hours.

I removed the trash icon from kicker because I was getting multiple dialog boxes regarding the trash whenever it crashed.

Next, I noticed it happened sometimes right when I switched desktops, so I removed the desktop preview & pager.

It crashed every couple of hours today and at the moment, it won't run at all -- just crashes immediately after starting.
Okay, just found some consistency. I have eight desktops, and dual monitors, and use transparency in kicker. It's crashing as soon as I start it on desktop 4, and crashes anytime I switch to desktop 4. It seems stable switching between the other desktops, at least for the last 20 seconds. Desktop 4 uses a gradient background (kdesktop > options > colors > horizontal gradient) across both screens while all the other desktops use images for their wallpaper, some across both screens and some not. I also noticed the background of Tasty menu flickering for a second after changing desktops and sometimes retaining artifacts, like incorrect renders of the background. It didn't used to do that.

I'm going to change desktop 4 to an image background and see if I can keep kicker running. I'll report back if things get stable again. Also, for anyone in a pinch like me, you can try using fbpanel (in repos) as a replacement bar.

Hope this helps:
[Thread debugging using libthread_db enabled]
[New Thread 0xb66c06c0 (LWP 10332)]
[KCrash handler]
#6 0xb709c190 in QImage::pixel (this=0xbfe28298, x=1, y=1)
    at kernel/qimage.cpp:2270
#7 0xb60264d3 in TastyButton::drawButton ()
   from /usr/lib/kde3/
#8 0xb71712dc in QButton::paintEvent (this=0x8187958)
    at widgets/qbutton.cpp:890
#9 0xb710b22b in QWidget::event (this=0x8187958, e=0xbfe28620)
    at kernel/qwidget.cpp:4808
#10 0xb7068c36 in QApplication::internalNotify (this=0x8056a28,
    receiver=0x8187958, e=0xbfe28620) at kernel/qapplication.cpp:2638
#11 0xb706b564 in QApplication::notify (this=0x8056a28, receiver=0x8187958,
    e=0xbfe28620) at kernel/qapplication.cpp:2526
#12 0xb782a9b2 in KApplication::notify (this=0x8056a28, receiver=0x8187958,
    at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#13 0xb6ff928d in QApplication::sendEvent (receiver=0x8187958,
    event=0xbfe28620) at ../include/qapplication.h:523
#14 0xb70341e3 in QWidget::repaint (this=0x8187958, reg=@0x818784c,
    erase=true) at kernel/qwidget_x11.cpp:1627
#15 0xb7069c56 in QApplication::sendPostedEvents (receiver=0x0, event_type=0)
    at kernel/qapplication.cpp:3299
#16 0xb7069d76 in QApplication::sendPostedEvents ()
    at kernel/qapplication.cpp:3213
#17 0xb700d8a3 in QEventLoop::processEvents (this=0x80865c8, flags=0)
    at kernel/qeventloop_x11.cpp:147
#18 0xb7083f02 in QEventLoop::processEvents (this=0x80865c8, flags=0,
    maxTime=3000) at kernel/qeventloop.cpp:261
#19 0xb706a84a in QApplication::processEvents (this=0x8056a28, maxtime=3000)
    at kernel/qapplication.cpp:26...


Montblanc (montblanc) wrote :

Jay, which applets are you using other than those? You could try removing applets one by one and see if it keeps crashing (yeah, I'm wondering why i didn't do that, before...), just to make sure your dual monitor setup is not the problem. If it keeps crashing, try disabling compiz: open a terminal and type

kwin --replace &

I put this bug to affect kicker at the beginning, but as soon as I removed the compiz kicker taskbar it stopped crashing. If you realize what's the cause of the crash let us know.

jay armstrong (jayarmstrong) wrote :

I should have mentioned I'm only using kwin, though I have compiz installed and have used it before.

Applets: tasty menu, system menu, a couple of quick menus, recent docs, quick launch, taskbar, system guard, the tray and the clock.

Still no crashes since I last posted but I've only been actively using it for about four hours. I'll post again with an update, either way, around sunday. Thx.

jay armstrong (jayarmstrong) wrote :

Ok, it has remained stable, though the tasty menu background is still quirky. I've added back in the applets I had removed *other than fusion-icon* and have even set one of my desktops back to a gradient.

Overall, the only differences are:
- I've rebooted *again* after purging the kicker-taskbar-compiz package
- that the gradient background is on a different desktop now.

This is solved for me. Thanks for the help :)

Montblanc (montblanc) on 2008-09-05
Changed in kicker-taskbar-compiz:
status: New → Confirmed
Square Bottle (squarebottle) wrote :

Removing taskbar-compiz also solved it for me, but here's the backport anyway in case it helps:

Can anyone try to reproduce the crash with -dbgsym packages installed for both kicker and kicker-taskbar-compiz if they are avaible?

See for instructions.

mrvanes (mrvanes) wrote :
Montblanc (montblanc) wrote :


Changed in kicker-taskbar-compiz:
status: Confirmed → Fix Committed
Changed in kicker-taskbar-compiz:
assignee: nobody → andreas-wenning
status: Fix Committed → In Progress

I've packaged the fixed version. Please test:

Please confirm if it fixes the problem, so the fix can be committed!

Montblanc (montblanc) wrote :

Thank you very much, Andreas, and sorry for mistaking the status of this bug! :P Your package is fine, I had no problem. Except I had to put the ShowAllWindows option from ~/.kde/share/config/ktaskbarrc to true in order to show only the apps from the workspace I'm from, while I had to set it to false, before. This is clearly not related to your package, and is not a bad deal, after all.

$ apt-cache policy kicker-taskbar-compiz
  Installato: 0.1+3.5.10-0ubuntu1~test2
  Candidato: 0.1+3.5.10-0ubuntu1~test2
  Tabella versione:
 *** 0.1+3.5.10-0ubuntu1~test2 0
        100 /var/lib/dpkg/status
     0.1-0ubuntu1 0
        500 hardy/universe Packages

Gijs ter Beek (gijsterbeek) wrote :


I just installed the .deb package on my Kubuntu 3.5.10. It doesn't clutter the taskbar as much, but I do still see closed applications linger on the Compiz taskbar. Contrary to earlier, they do disappear, but it takes a minute or so. Right now I'm looking at Thunderbird and KTorrent icons which both are closed already. Did you implement a scheduled cleanup of the taskbar? Or is this strange behaviour you would like to look into?


I've simply updated the package with the code from here:

I've tried a quick look at the code changes to see if anythind looked to be related to what you experience, but didn't find anything. I don't use compiz myself (and can't due to my graphics adapter) so can't play around with the code that much and be sure that it works with compiz.

Gijs ter Beek (gijsterbeek) wrote :

I think the problem is strongly related to whether kicker autohides or not. I've just disabled autohide and until now, it works just like it should work. As soon as I enable autohide again, taskbar-compiz doesn't clean up all the old windows.

Can you try experimenting with the settings, and see which gives a problem; and post the settings (and values) from .kde/share/config/ktaskbarrc

If you change viewport/desktop does the closed programs then disappear?


I doesn't matter if I change viewports or not. They don't disappear.
Also, I've tried to change some settings in ktaskbarrc but it doesn't
change a lot (also, there aren't that much settings that can be changed.
See my ktaskbarrc below:





Even when ktaskbarrc doesn't contain anything, the problem persists.
Both kicker-taskbar-compiz and the regular kicker taskbar show this
behaviour. So maybe it's related to something else. There is two more

1. When I have Autohide disabled, the problem doesn't occur
2. When I lock and unlock the panel, the leftovers disappear, but it
start again after i close a window
3. It doesn't happen for all windows, but I couldn't find out any
predictability in which are and which are not influenced.

Thanks for helping out!


Andreas Wenning schreef:
> @Gijs
> Can you try experimenting with the settings, and see which gives a problem; and post the settings (and values) from .kde/share/config/ktaskbarrc
> If you change viewport/desktop does the closed programs then disappear?

It sounds like the issue is unrelated to kicker-taskbar-compiz if it happens in regular kicker as well.

I'd suggest reporting it as a seperate bug (don't know against which package thou). I don't see that behaviour on kde 3.5.10; might be worth testing it without using compiz before reporting the bug to see if it could be related to compiz.

Scott Kitterman (kitterman) wrote :

Fix uploaded for hardy-backports. Need wait for an archive admin to accept it.

Changed in kicker-taskbar-compiz:
assignee: andreas-wenning → nobody
importance: Undecided → Medium
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kicker-taskbar-compiz - 0.1+3.5.10-0ubuntu1

kicker-taskbar-compiz (0.1+3.5.10-0ubuntu1) hardy-backports; urgency=low

  * New upstream release that works with KDE 3.5.10. (LP: #261694)
  * debian/control: Added version requirement to kdelibs4-dev,
    kdebase-dev as it doesn't build with kde << 3.5.10.

 -- Andreas Wenning <email address hidden> Mon, 29 Sep 2008 22:20:09 +0200

Changed in kicker-taskbar-compiz:
status: Fix Committed → Fix Released
Gijs ter Beek (gijsterbeek) wrote :

I found another bug (239645) which I think reflects the problems a little better. Thanks for helping out, though!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers