Bug 270033 - Device notifier window appears at the wrong place when the first device is connected
Summary: Device notifier window appears at the wrong place when the first device is co...
Status: RESOLVED DUPLICATE of bug 267795
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-devicenotifier (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-03 22:12 UTC by David Nemeskey
Modified: 2011-04-04 08:53 UTC (History)
2 users (show)

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

Attachments
Popup with hidden panel (705.75 KB, image/png)
2011-04-03 22:12 UTC, David Nemeskey 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description David Nemeskey 2011-04-03 22:12:09 UTC 
Created attachment 58550 [details]
Popup with hidden panel

Version:           unspecified (using KDE 4.6.1) 
OS:                Linux

The device notifier popup window appears at the wrong place when the first device is connected. More specifically: if a device is connected, and the "storage Volume" list contains only one item, -- namely, the device just connected, -- then the window is placed around the middle of the screen vertically. If a second device is connected, the popup appears at the correct spot. However, if now both devices are removed, and one is connected again, the popup window shows up at the wrong place again.

This issue is for automatic popup only. If I click on the systray icon, the window appears where it should.

I have a hidden panel, and at first I thought that may be the cause of the issue, but apparently the problem manifests itself even when the panel is set to be always visible.

Reproducible: Always
Comment 1 Lamarque V. Souza 2011-04-04 01:04:38 UTC 

*** This bug has been marked as a duplicate of bug 268073 ***
Comment 2 David Nemeskey 2011-04-04 07:44:33 UTC 
> *** This bug has been marked as a duplicate of bug 268073 ***

Actually, shouldn't it be a duplicate of 267795 instead? 268073 has also been marked as a duplicate of that bug.
Comment 3 Lamarque V. Souza 2011-04-04 08:53:58 UTC 

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