Description of problem: Boot to Mageia2 alpha2/Gnome, try to activate anything by clicking into the touchpad â nothing happens. You need to go to the Mouse settings and explicitly allow click via touchpad. Just do a google search and you'll find lots of questions regarding this questionable change in default. Those who disabled click in the past, will be able to still do so. But those having used Linux or Windows before, where clicking via the pad was default, will have a "wtf" moment or two, thinking their touchpad isn't properly supported.
why "Update breaks my touchpad" ?
Component: Installer => RPM Packages
Keywords: (none) => NEEDINFOSource RPM: (none) => gnome-control-center
because: clicking on the touchpad did execute a click before in windows, in $previous_distro, and when switching to Mageia alpha2 suddenly only the buttons work, and no longer the tap-to-click feature.
Keywords: NEEDINFO => (none)
Ah you have upgrade ok perfect :) Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedBlocks: (none) => 3342Assignee: bugsquad => olav
oh,m to be clear on that - I did not upgrade yet - it is still too alpha for me to really switch - this is while booting the Live iso - and I guess these are the settings that will be applied when installing the system. A windows user who is trying out Mageia will not be satisfied with the touchbad not responding on clicks anymore. On all machines/all drivers I have come across so far, disabling the tap-to-click requires user-interaction, but never the opposite. It simpler to understand that you can make the system ignore something than to understand that it is not broken, but not activated.
Blocks: 3342 => (none)Summary: GNOME - click via touchpad should be enabled by default - otherwise "Update breaks my touchpad" => Touchpad click should be enabled by default (default setting regression)
still the same in beta3 live iso. While booting up (i.e. when choosing the language, accepting the license, choosing the keyboard layout) the touchpad-click works, but when gnome is booted, it stops working and has to be manually enabled. This is bad usability and contrary to users' expectations. What is the rationale behind disabling this by default? If you cannot name any reason, please change the default.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
yes, still valid. comment #5 still holds true.
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Still valid? Keep open?
CC: (none) => nic
I'm not planning to do anything with this bug. I don't know how to judge what's better. I prefer following whatever upstream does. Removing me as assignee.
Assignee: olav => bugsquad
(In reply to Nic Baxter from comment #9) > Still valid? Keep open? (In reply to Olav Vitters from comment #10) > I'm not planning to do anything with this bug. I don't know how to judge > what's better. I prefer following whatever upstream does. Removing me as > assignee. Setting UPSTREAM keyword. @ Christian Please close as fixed, if it did/does get fixed. If not, it is better to file a bug here https://bugzilla.gnome.org/ (or add yourself to it if it already exists) In that case, please give a link to the report
Keywords: Triaged => UPSTREAMCC: (none) => marja11
reported https://bugzilla.gnome.org/show_bug.cgi?id=746189
Thanks, Nic Adding it to the "See Also" field (That is for links to bugs in other, so non-Mageia, Bugzillas and can be used for a link to the upstream bug report, but also for links to bug reports in other distros about the same issue as our bug report is about.)
See Also: (none) => https://bugzilla.gnome.org/show_bug.cgi?id=746189
*** Bug 13522 has been marked as a duplicate of this bug. ***
CC: (none) => tablackwell
Assigning to GNOME maintainer group but that doesn't mean anything will be done, since it seems to be an upstream decision...
Assignee: bugsquad => gnome