After I start MCC from a root terminal, and go to "Configure media sources", then after I enable an item from the sources by clicking the "Enabled" menu item, the scrollbar jumps to the currently enabled item. Instead, the scrollbar should stay at the current place to avoid unnecessary jumps and "WTF?" moments.
Wrong package. This is a side effect of the switch from gtk2 to gtk3
CC: (none) => thierry.vignaudBlocks: (none) => 11778Assignee: bugsquad => thierry.vignaudSummary: In MCC -> "Configure media sources" the scrollbar jumps when an item is ticked. => In "Configure media sources" the scrollbar jumps when an item is tickedSource RPM: drakconf-12.47-1.mga4.src.rpm => rpmdrake
*** Bug 13666 has been marked as a duplicate of this bug. ***
CC: (none) => zen25000
There's a chance Debian's equivalent of our drakrpm-edit-media has the same problem: One or two days ago, I saw someone who was configuring the Debian media sources for his new KNOPPIX 7.4.2, getting very annoyed by the jumps the selection screen made every time he deselected something. I didn't find a bug report (don't know how their tool is called), but mention it just in case it's the same problem with gtk+3 and they find a fix.
CC: (none) => marja11
This also affects mouse actions in the info pane in in rpmdrake. When trying to copy text from the changelog that is below the first full pane of text, clicking the start of the text to be copied, causes the text in the pane to scroll instantly back to the top.
Valid 5RC
Fixed in my git tree
Keywords: (none) => USABILITY
Whiteboard: (none) => MGA5TOO
commit 877f395a26ac1499a9e9354fd96e7b0648ae831e Author: Thierry Vignaud <thierry.vignaud@...> Date: Thu May 28 14:38:40 2015 -0400 fix list jumping when tickling an item (mga#12180) --- Commit Link: http://gitweb.mageia.org/software/rpmdrake/commit/?id=877f395a26ac1499a9e9354fd96e7b0648ae831e
Closing
Status: NEW => RESOLVEDResolution: (none) => FIXED
Thierry, don't you want to keep it open with Mageia 5 as the version, as a reminder to include it in an update to Mageia 5? This is how we do usually when a fix reached cauldron but not the stable release.
Actually, I've already pushed it for mga5 :-)