Bug 316741 - Docking the toolbars to a different location results in floating toolbars and is difficult to use
Summary: Docking the toolbars to a different location results in floating toolbars and...
Status: RESOLVED DUPLICATE of bug 300896
Alias: None
Product: amarok
Classification: Applications
Component: Toolbar (show other bugs)
Version: 2.8-git
Platform: Slackware Linux
: NOR major
Target Milestone: 2.9
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-14 22:54 UTC by Woodsman
Modified: 2013-12-05 10:05 UTC (History)
3 users (show)

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


Attachments
Attempt at fixing the bug (2.66 KB, patch)
2013-04-26 16:57 UTC, Anmol Ahuja
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Woodsman 2013-03-14 22:54:02 UTC
Amarok is designed to support moving panes and toolbars but the docking mechanism will frustrate almost any user. Users will discover that docking does not work. Every time Amarok is started the docked toolbar is floating rather than docked.

I am posting a work-around at the end of this report.

Reproducible: Always

Steps to Reproduce:
All of the following was performed on KDE 4.10.1 with Amarok 2.7.0. I am providing three examples to illustrate how new users could try to fix the problem on their own.

Usability note: Docking is not intuitive for new Amarok users. When not performed correctly the toolbar remains in a float position. Docking requires a very slow movement such that the layout interface suddenly creates a gap or opening. Then the trick is not to force the docking handle exactly next to the left window border but instead to simply release the toolbar anywhere in the newly created gap opening.

Try this:

* In a test environment, delete all Amarok config files and data files such that Amarok starts clean.
* For testing purposes, cancel any possible dialogs about finding local music files.
* Unlock the layout.
* Drag the Main toolbar docking handle to the bottom of the Amarok window layout.
* After docking the Main toolbar, do not lock the layout.
* Quit Amarok.
* Start Amarok.
* Notice the toolbar will be floating.
* Again dock the Main toolbar to the bottom of the layout.
* Lock the layout.
* Quit Amarok.
* Start Amarok.
* Notice the toolbar will be floating.

Try this:

* In a test environment, delete all Amarok config files and data files such that Amarok starts clean.
* For testing purposes, cancel any possible dialogs about finding local music files.
* Unlock the layout.
* Close all three panes, leaving only the Main toolbar.
* Quit Amarok.
* Start Amarok.
* Notice the toolbar is docked at the top.
* With all three panes still removed, dock the Main toolbar to the bottom of the layout.
* Quit Amarok.
* Start Amarok.
* Notice the toolbar is docked at the top.
* With all three panes still removed, dock the Main toolbar to the bottom of the layout.
* Lock the layout.
* Quit Amarok.
* Start Amarok.
* Notice the toolbar is docked at the top.
* Enable the Playlist pane.
* Dock the Main toolbar to the bottom of the layout.
* Quit Amarok.
* Start Amarok.
* Notice the toolbar is floating at the top.

Try this:

* In a test environment, delete all Amarok config files and data files such that Amarok starts clean.
* For testing purposes, cancel any possible dialogs about finding local music files.
* Unlock the layout.
* Quit Amarok.
* Start Amarok.
* Notice everything looks fine.
* Dock the Main toolbar to the bottom of the layout.
* Quit Amarok.
* Start Amarok.
* Notice the toolbar is floating at the bottom.
* Dock the Main toolbar to the top of the layout.
* Toggle to the Slim toolbar.
* Quit Amarok.
* Start Amarok.
* Notice everything looks fine.
* Dock the Slim toolbar to the bottom of the layout.
* Quit Amarok.
* Start Amarok.
* Notice the Slim toolbar is floating at the bottom.

Actual Results:  
The toolbars do not remain docked after a restart.

Expected Results:  
The docked toolbars should remain docked after a restart.

A work-around:

Note: I believe the secret of preventing the toolbars from floating after the first docking is to quit Amarok with the opposite toolbar being displayed rather the one desired. That is, dock the desired toolbar, toggle to the other toolbar, quit and start Amarok, then toggle to the desired toolbar. Zany but works and I have repeated the solution several times. This is a work-around and I discovered this work-around only through much trial and error.

* In a test environment, delete all Amarok config files and data files such that Amarok starts clean.
* For testing purposes, cancel any possible dialogs about finding local music files.
* Unlock the layout.
* Dock the Main toolbar to the bottom of the layout.
* Toggle to the Slim toolbar, which will be docked at the top.
* Quit Amarok.
* Start Amarok.
* Dock the Slim toolbar to the bottom of the layout.
* Toggle to the Main toolbar.
* Quit Amarok.
* Start Amarok.
* Toggle to the Slim toolbar, which is docked at the bottom.
* Quit and start Amarok as many times as desired with either toolbar selected and the toolbar remains docked at the bottom.

I hope this helps!
Comment 1 Thomas Lübking 2013-03-14 23:08:25 UTC
sounds rather like there's an invalid layout dump in ~/.kde/share/apps/amarok/layout when the toolbar is docked in the bottom area or the layout is restored wrongly (bottom -> floating)
Comment 2 Myriam Schweingruber 2013-03-14 23:13:15 UTC
Confirmed, it is annoying.
Comment 3 Anmol Ahuja 2013-04-26 10:36:13 UTC
I'm working on this bug.
Comment 4 Anmol Ahuja 2013-04-26 16:56:04 UTC
I've encountered this bug several times myself, I'm unable to reliably reproduce it! It seems to occur at seemingly random instances.

Can you still reliably reproduce it? If so, could you try this patch I'm attaching and see if it works? Just seeing if saving the geometry somehow helps.

I've also added shortcuts for the save state (Control+S) and restore state (Control+R) functions. If you manage to reproduce it, can you try causing it with these shortcuts instead of restarts?
Comment 5 Anmol Ahuja 2013-04-26 16:57:27 UTC
Created attachment 79470 [details]
Attempt at fixing the bug
Comment 6 Myriam Schweingruber 2013-04-27 09:27:13 UTC
(In reply to comment #5)
> Created attachment 79470 [details]
> Attempt at fixing the bug

Don't forget to send this to reviewboard.kde.org, please :)
Comment 7 Anmol Ahuja 2013-04-27 11:41:17 UTC
I'd like to wait until I can get some confirmation from the OP, because I'm not really certain if this fixes the bug.
Or maybe I should leave it for somebody who can reliably reproduce it.
Comment 8 Mikhail Ivchenko 2013-12-04 11:10:43 UTC
Still not fixed in v2.8.0
Comment 9 Myriam Schweingruber 2013-12-05 10:05:40 UTC

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