Bug 179602 - panel moved from bottom to top when adding a new screen and kwin crashed
Summary: panel moved from bottom to top when adding a new screen and kwin crashed
Status: RESOLVED DUPLICATE of bug 173017
Alias: None
Product: plasma4
Classification: Unmaintained
Component: containment-panel (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 179607 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-04 13:52 UTC by Andreas Pakulat
Modified: 2009-01-11 17:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Pakulat 2009-01-04 13:52:05 UTC
Adding a second monitor to my desktop via xrandr --output VGA --right-of LVDS --auto worked ok (except the desktop background, but thats a different bug). After creating a new konqueror window on the second screen and opening bko in it kwin crashed and at the same time the plasma panel moved from its bottom location on the first screen to the top of the first screen.

The panel was fine after adding another screen, it only happened once I interacted with the konqueror window on the second screen and kwin crashed.
Comment 1 Andreas Pakulat 2009-01-04 13:54:35 UTC
Just retried and its perfectly reproducable: 

Grab a window title, move the window into the second screen. This crashes kwin and it also makes the panel vanish. Not the desktop background though, so I assume not all of plasma is crashing at that point. 

When the panel and kwin come back, the panel is at the top of the first screen.
Comment 2 Andreas Pakulat 2009-01-04 14:22:39 UTC
And another note: Due to 179607 I can't really move the panel myself back to the bottom, but it seems when playing around with the size handles a bit it jumps back to the bottom itself.

I also just noticed (trying to move it back to the top via this bugreports steps) that it doesn't necessarily happen the first time kwin crashes. Might need a second try of moving the window on the second screen to move the panel...
Comment 3 Andreas Pakulat 2009-01-04 18:13:10 UTC
Captured plasma kdebug output while moving a window from screen 0 to screen 1 and the panel jumped to the top:

plasma(21082) PanelView::updateStruts: screen l/r/b/t offsets are: 0 1680 150 0 4
plasma(21082) TaskManager::AbstractGroupingStrategy::createGroup:
Object::connect: Attempt to bind non-signal TaskManager::TaskGroup::editRequest()
plasma(21082) TaskGroupItem::reload:
plasma(21082) TaskGroupItem::isActive: Not Implemented
Comment 4 Aaron J. Seigo 2009-01-04 18:57:40 UTC
*** Bug 179607 has been marked as a duplicate of this bug. ***
Comment 5 Aaron J. Seigo 2009-01-04 18:59:38 UTC
i doubt this has anything to do with plasma. the panel asks to move to a certain location on screen, but it's the window manager that actually allows it to do so. that it repositions properly as soon as you alter the settings says that plasma internally has the right bookkeeping, but that the window manager has moved the window elsewhere "behind its back".

let's get the window manager crash fixed, and then when that's done, revisit this bug. i trust you've filed a report with kwin with a backtrace? can you reference the bug # in a comment in this report, please? thanks.
Comment 6 Andreas Pakulat 2009-01-05 00:31:11 UTC
There's only one xrandr kwin bugreport: https://bugs.kde.org/show_bug.cgi?id=173017
Comment 7 Andreas Pakulat 2009-01-11 17:13:30 UTC
Ok, seems like the real issue for both plasma and kwin has been kephal. Luckily I've got help from one of the kephal devs and he was able to fix the problems I've seen (there's one remaining which happens with cloning/"un-cloning" screens ). So I'm closing this as duplicate of the xrandr bug in kwin.

Commit is pending, along with backporting to 4.2 and closing the bugreport.

*** This bug has been marked as a duplicate of bug 173017 ***