Bug 163429 - [kde4daily] kde4.1 don't save panel position
Summary: [kde4daily] kde4.1 don't save panel position
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 169218 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-06-07 10:59 UTC by Michał Kudła
Modified: 2008-08-16 13:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Kudła 2008-06-07 10:59:17 UTC 
Version:           unknown (using 4.00.81 (KDE 4.0.81 >= 20080527), compiled sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-16-generic

[Kde4Daily]
how to reproduce:
1. move panel to up of destop,
2. restart machine,
=> after restart panel placed bottom.

Screencast (h264)
http://michal.kudla.googlepages.com/kde4aily-konqueror.mp4
Comment 1 Simon St James 2008-06-07 11:29:26 UTC 
Might be a consequence of 

https://bugs.kde.org/show_bug.cgi?id=163112

which kills KDE prematurely when you try to logout.  I can't tell from your screencast if this is the case, as it seems to show something to do with Konqueror ;)

I'm going to try and get to the bottom of bug:163112 this weekend if I can ping ervin; otherwise I'll just have to patch around it, I guess :/
Comment 2 Michał Kudła 2008-06-07 11:59:26 UTC 
bad link, propper is
http://michal.kudla.googlepages.com/kde4aily-plasma.mp4
Comment 3 Simon St James 2008-06-07 12:02:38 UTC 
Yep, definitely bug:163112 (note how it dumps you straight back to kdm instead of restarting).  I'm trying to create a workaround as we speak, and will roll out an emergency update if I figure it out.  Stay tuned!
Comment 4 Simon St James 2008-06-07 17:39:13 UTC 
Please upgrade to the KDESVNTRUNKr818001 update and re-try (it now WORKSFORME, at least :)).
Comment 5 Aaron J. Seigo 2008-06-16 01:10:17 UTC 
yes, it has been since fixed.
Comment 6 lucas 2008-08-16 13:23:27 UTC 
*** Bug 169218 has been marked as a duplicate of this bug. ***