Bug 186124 - plasma crashes on startup with different resolution
Summary: plasma crashes on startup with different resolution
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-04 15:52 UTC by Michal Witkowski
Modified: 2009-03-11 22:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Plasma resolution change crash (3.39 KB, text/plain)
2009-03-04 15:53 UTC, Michal Witkowski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Witkowski 2009-03-04 15:52:44 UTC
Version:           unknown (using 4.2.1 (KDE 4.2.1), Arch Linux)
Compiler:          gcc
OS:                Linux (i686) release 2.6.28-ARCH

Hi

I'm using ArchLinux KDEmod packages latest 4.2.1 with xorg 1.5.6 and fglrx/catalyst version 9.2. I've got a Lenovo U330 laptop with Radeon HD3450 graphics, an LCD output (1280x800) and I plug in my DFP1 output (1920x1200) when I'm at home. I run a special xrandr script in KDM's Xsetup which detects the external display, switches it to auto and turns off the laptop's LCD.

Before todays update from 4.2.0 to 4.2.1 I had no problems. The xrandr script would kick in KDM and change the resolution. Then plasma would detect my configuration and load my previous settings. 

Right now, whenever I switch resolutions on startup (for example use only the LCD display after the previous session was using the DFP1), plasma crashes on startup with provided below output.

I then have to run nutcracker and create a default plasma config (ugh), which will in turn once again fail when I switch to the different resolution on startup (this time for example by using only the DFP display)

Crash log with debugging symbols attached below.
Comment 1 Michal Witkowski 2009-03-04 15:53:44 UTC
Created attachment 31766 [details]
Plasma resolution change crash
Comment 2 Pino Toscano 2009-03-04 15:58:30 UTC
Pasting the backtrace inline, so it is easier to look for duplicates:

Application: Plasma Workspace (plasma), signal SIGSEGV
[Current thread is 0 (LWP 3486)]

Thread 2 (Thread 0xa9f64b90 (LWP 3487)):
#0  0xb803b424 in __kernel_vsyscall ()
#1  0xb6857c55 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb68d46a2 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#3  0xb7a4ba0a in ?? () from /usr/lib/libQtNetwork.so.4
#4  0x098bc460 in ?? ()
#5  0x098bc45c in ?? ()
#6  0xffffffff in ?? ()
#7  0xb6a4c000 in ?? ()
#8  0xa9f64310 in ?? ()
#9  0xb804a41b in _dl_fixup () from /lib/ld-linux.so.2
#10 0xb68d3910 in ?? () from /usr/lib/libQtCore.so.4
#11 0x098bc450 in ?? ()
#12 0x00000000 in ?? ()

Thread 1 (Thread 0xb5673710 (LWP 3486)):
[KCrash Handler]
#6  0xb69c657a in QTimer::stop () from /usr/lib/libQtCore.so.4
#7  0xb8003100 in PanelView::updatePanelGeometry (this=0x9a1ebe0)
    at /home/jan/ScratchPad/kdemod-new-makepkg/work/core/kdebase-workspace/src/kdebase-workspace-4.2.1/plasma/shells/desktop/panelview.cpp:543
#8  0xb8004308 in PanelView::pinchContainment (this=0x9a1ebe0, screenGeom=@0xbfe55e70)
    at /home/jan/ScratchPad/kdemod-new-makepkg/work/core/kdebase-workspace/src/kdebase-workspace-4.2.1/plasma/shells/desktop/panelview.cpp:689
#9  0xb8005ebf in PanelView (this=0x9a1ebe0, panel=0x934f3a0, id=2, parent=0x0)
    at /home/jan/ScratchPad/kdemod-new-makepkg/work/core/kdebase-workspace/src/kdebase-workspace-4.2.1/plasma/shells/desktop/panelview.cpp:243
#10 0xb800fba6 in PlasmaApp::createView (this=0x9228840, containment=0x934f3a0)
    at /home/jan/ScratchPad/kdemod-new-makepkg/work/core/kdebase-workspace/src/kdebase-workspace-4.2.1/plasma/shells/desktop/plasmaapp.cpp:619
#11 0xb80102c6 in PlasmaApp::containmentAdded (this=0x9228840, containment=0x934f3a0)
    at /home/jan/ScratchPad/kdemod-new-makepkg/work/core/kdebase-workspace/src/kdebase-workspace-4.2.1/plasma/shells/desktop/plasmaapp.cpp:663
#12 0xb801053c in PlasmaApp::qt_metacall (this=0x9228840, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfe5617c)
    at /home/jan/ScratchPad/kdemod-new-makepkg/work/core/kdebase-workspace/src/kdebase-workspace-4.2.1/plasma/shells/desktop/plasmaapp.moc:96
#13 0xb69bf77b in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb69bfcd2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb7ed09d3 in Plasma::Corona::containmentAdded () from /usr/lib/libplasma.so.3
#16 0xb7ed2088 in Plasma::Corona::loadLayout () from /usr/lib/libplasma.so.3
#17 0xb7ed38a1 in Plasma::Corona::initializeLayout () from /usr/lib/libplasma.so.3
#18 0xb800d1ed in PlasmaApp::corona (this=0x9228840) at /home/jan/ScratchPad/kdemod-new-makepkg/work/core/kdebase-workspace/src/kdebase-workspace-4.2.1/plasma/shells/desktop/plasmaapp.cpp:517
#19 0xb800d385 in PlasmaApp::setupDesktop (this=0x9228840) at /home/jan/ScratchPad/kdemod-new-makepkg/work/core/kdebase-workspace/src/kdebase-workspace-4.2.1/plasma/shells/desktop/plasmaapp.cpp:255
#20 0xb801056b in PlasmaApp::qt_metacall (this=0x9228840, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfe56478)
    at /home/jan/ScratchPad/kdemod-new-makepkg/work/core/kdebase-workspace/src/kdebase-workspace-4.2.1/plasma/shells/desktop/plasmaapp.moc:94
#21 0xb69bf77b in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#22 0xb69bfcd2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb69c6777 in ?? () from /usr/lib/libQtCore.so.4
#24 0x09298af0 in ?? ()
#25 0xb6a49448 in ?? () from /usr/lib/libQtCore.so.4
#26 0x00000000 in ?? ()
Comment 3 Michal Witkowski 2009-03-04 23:04:21 UTC
Hi. I've found a temporary workaround. It seems the problem is related to the drawing of a maximized panels.

Since I've got two resolutions: 1280x800 and 1920x1200 I thought that I'd just make the panel circa 1100px in width and centered. Plasma no longer crashes when I change the resolution

However, the problem still exists with a maximized panel. Any ideas? Any chances of fixing this soon?
Comment 4 Aaron J. Seigo 2009-03-05 01:26:43 UTC
already fix in trunk and the 4.2 branch a couple day ago.
Comment 5 Michal Witkowski 2009-03-11 22:03:02 UTC
Could you please point me to the revision in which this was fixed? The packagers in my distro can't seem to find a suitable patch.

Thanks