Bug 183122 - Activity Bar plasmoid freezes up Plasma when clicked
Summary: Activity Bar plasmoid freezes up Plasma when clicked
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-04 02:30 UTC by Stephan Sokolow
Modified: 2010-05-13 19:28 UTC (History)
6 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 Stephan Sokolow 2009-02-04 02:30:33 UTC
Version:           unknown (using 4.2.00 (KDE 4.2.0), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.25-gentoo-r7-20080501

The Activity Bar plasmoid freezes up Plasma if I click it.

I'm not sure, but it may have something to do with my using a dual-head nVidia TwinView setup.
Comment 1 Michal 2009-02-21 10:15:50 UTC
I can confirm this bug with intel GMA950. I have the same problem when I try to switch activity using activity bar, it freezes the plasma.  It happens only when I use dualhead because I can switch to activity which is already displayed on the second monitor. 
The activity bar should do nothing (or swap the activities) when I try to switch to already shown activity instead of freezing plasma.

I have this problem with
Qt: 4.4.2
KDE: 4.2.00 (KDE 4.2.0) 

and also with 
Qt: 4.5.0-rc1
KDE: 4.2.64 (KDE 4.2.64 (KDE 4.3 >= 20090218))
Comment 2 daboo 2009-06-11 21:20:57 UTC
I can confirm this. Still freezing on KDE 4.3 beta 2 with Qt 4.5.1. Curiously, I'm also running a dual monitor setup.
Comment 3 Michal 2009-07-02 20:41:31 UTC
The problem is also in KDE 4.3 RC1. Can you please fix it?
Comment 4 Aaron J. Seigo 2009-07-03 00:38:01 UTC
does it happen no matter what activity you click on?
or does it only happen when you click on the activity that is active on the other screen?

when it freezes, i assume it starts consuming 100% cpu? if so, can you attach gdb to the running process and get a backtrace of where it is spinning?
Comment 5 Michal 2009-07-03 13:24:45 UTC
The problem appears only when I click on activity already shown on the other screen then it starts to use 100% cpu.
Here is the backtrace. This part was repeating there.

#43 0xb6852121 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/qt4/libQtCore.so.4
#44 0xb685267d in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/qt4/libQtCore.so.4
#45 0xb6e3761a in QTabBar::currentChanged(int) () from /usr/lib/qt4/libQtGui.so.4
#46 0xb6e3d2d4 in QTabBar::setCurrentIndex(int) () from /usr/lib/qt4/libQtGui.so.4
#47 0xb7e5679c in Plasma::TabBar::setCurrentIndex (this=0x89a9650, index=0) at /home/kde-devel/kde/src/kdelibs/plasma/widgets/tabbar.cpp:351
#48 0xb7e56ce7 in Plasma::TabBar::qt_metacall (this=0x89a9650, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbf7afd0c)
    at /home/kde-devel/kde/build/kdelibs/plasma/tabbar.moc:84

I hope that this is the what did you need
Comment 6 Dario Andres 2009-09-27 17:17:57 UTC
- Is this still happening on an updated KDE and Qt? Thanks
Comment 7 Michal 2009-09-28 20:38:59 UTC
Yes still the same problem. I tried it with Qt 4.5 and Qt 4.6 and KDE 4.3.1 and 4.3.69 both with clean configuration of plasma.
Comment 8 Victor Hahn 2009-10-03 05:16:34 UTC
Confirming this as well. I use a manual dual monitor setup using xrandr (because of bug #180437 ;-) )
Comment 9 David Palacio 2010-01-04 20:38:50 UTC
On KDE 4.4 clicking on an activity displayed on the other screen will swap both activities.
Comment 10 Michal 2010-01-05 11:52:56 UTC
Yes, it looks that in the KDE4.4 beta 2 it is finally fixed.
Comment 11 Dario Andres 2010-01-05 12:02:02 UTC
- Can anyone else confirm that it is working on 4.4beta2 ? Thanks