Bug 343393

Summary: kmix volume control is show in a wierd location on dual monitor configuration
Product: [Applications] kmix Reporter: Rogério Pereira Araújo <rogerio.araujo>
Component: Visual: Layout and GUIAssignee: Christian Esken <esken>
Status: RESOLVED DUPLICATE    
Severity: normal CC: cfeck
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Rogério Pereira Araújo 2015-01-27 19:33:27 UTC 
I have a kmix notification icon in a panel at the top of my laptop screen, if I attached another monitor and start to use the desktop in a dual monitor configuration and click on kmix notification icon to change the volume, the volume popup window is show in the other screen instead of laptop screen, if there's no external monitor attached then the kmix popup is shown on its correct place.

Reproducible: Always

Steps to Reproduce:
1. Create a panel at the top center of laptop screen
2. Add kmix notification icon to this panel
3. Attach an external monitor
4. Click on kmix notification icon to change volume settings

Actual Results:  
A click on kmix icon is showing a volume control in another monitor

Expected Results:  
A click on kmix icon should show the volume control on same monitor as the notification icon is.
Comment 1 Christoph Feck 2015-01-27 21:19:31 UTC 
Which version of kmix are you using? This should be fixed since the 14.12 release.
Comment 2 Rogério Pereira Araújo 2015-01-27 21:25:27 UTC 
kmix (4:4.13.3-0ubuntu0.1) trusty

Not sure if this is means kmix version 13.3, if yes, I believe I'm using an outdated version.
Comment 3 Christoph Feck 2015-01-27 21:41:21 UTC 
The KDE Applications releases changed version numbering since the last month to match the YY.MM (year/month) numbering many other projects used. The last 4.x release was 4.14.x, so 4.13.x is indeed two major releases outdated, now that we have 14.12.x since December.

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