Mon 13 Feb 2012 08:18:13 AM UTC, comment #3:
another observation:
the problem with the resize arrow only seems to happen in the GWorkspace File viewer. On the weekend I recognized, that I also have such a resize bar in MPDCon Collection browser. When the MPDCon window is active, and I hover over the resize line, then the problem doesn't occur. So seems to be only bound to GWorkspace.
|
Fri 10 Feb 2012 06:11:20 PM UTC, comment #2:
I now can always reproduce the following:
After login in GWorkspace, I have a File Viewer open.
Viewer behaviour is set to browsing.
There, between the top, where I can drag 'n drop my bookmarks, and where the icons are, there is this thing that I can move up and down, i.e. to hide the bookmarks, or to enlarge that space. When I hover my mouse arrow over this line, then it changes to the horizontal resize arrow, this arrow with pointers up and down.
I don't need to click or anything, afterwards it just stays this way. The File Viewer window needs to be the active window to trigger this change.
A second thing I observed reproducibly:
when I try dragging an application from the file viewer to the dock, hover it over the dock, the arrow gets green, and this forbidden sign (the circle with the line from lower left to top right). When I release the mouse cursor when the arrow is this forbidden sign then it stays this way.
When I release the application, while the icon is green, then afterwards the icon stays green.
The icons still change, when I hover it over another application. It doesn't matter whether its green, thsi forbiddne sign, or the resize arrow, but when I move it for example over GNUmail window, or a different App, then the icon changes back to normal, when I move the cursor further, over the desktop again, or the file viewer, then its back to its wrong icon.
Hope my descriptions were clear enough to be able to reproduce things.
Sebastian
|
Thu 02 Feb 2012 10:09:03 PM UTC, comment #1:
I just wanted to add a few links to older bugs that deal with similar problems: bug #5871, bug #6213, bug #6214 and #bug #24886.
We resolved all of them, but there seem to be a few cases where our current solution isn't good enough. The problem here has been that it turned out hard to reprocude these problems on purpose.
|