Bug 184937 - widgets not moving properly
Summary: widgets not moving properly
Status: RESOLVED DUPLICATE of bug 170588
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-19 14:07 UTC by chapinjeff
Modified: 2009-02-24 10:50 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 chapinjeff 2009-02-19 14:07:11 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Fedora RPMs

When placing a new widget (digital clock) on an otherwise empty panel, I was unable to move the widget. It decided it was going to live in the middle, whether I wanted that, or not. 

I added a system tray to try and alleviate this problem -- now I have a giant system tray taking up 75% of my space -- and a giant clock taking up 25% -- rather than the respective 10% and 10% that is appropriate.
Comment 1 Dario Andres 2009-02-20 00:00:47 UTC
As a workaround you can use the "Panel Spacer" plasmoid (it should be on kdebase-plasma-addons)
Comment 2 chapinjeff 2009-02-21 02:44:50 UTC
I guess that is a fedora bug then, since it is not in kdeplasma-addons.

Well, thanks for the help.
Comment 3 chapinjeff 2009-02-21 04:06:10 UTC
Fedora claims it is your problem: https://bugzilla.redhat.com/show_bug.cgi?id=486690.

I have the package kdeplasma-addons (closest equivalent package name) installed, and this plasma widget does not seem to exist. If you could point me at the package name, or kde component a little more definitely, I could continue to pursue it with them.
Comment 4 Kevin Kofler 2009-02-21 06:03:41 UTC
We didn't claim it's an upstream problem, all we said is that it's not actually part of kdeplasma-addons.
Comment 5 chapinjeff 2009-02-21 11:34:29 UTC
Kevin, 
The claim was made that 'upstream is wrong', so I asked upstream for clarification. I don't care *whose* bug it is, it is a huge usability bug that needs fixed, so I am trying to get it tracked down and resolved.
Comment 6 Aaron J. Seigo 2009-02-24 10:50:41 UTC

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