Red Hat Bugzilla – Bug 459818
SHMConfig should be enabled by default
Last modified: 2013-04-02 00:22:14 EDT
Created attachment 314821 [details]
Modified FDI to enable SHMConfig
SHMConfig should be enabled by default until input properties are merged.
reassigning to correct component (synaptic != synaptics :)
But let me add my 0.02: /usr/share/doc/synaptics-0.14.6/INSTALL says about
Note! This is not secure if you are in an untrusted multiuser
environment. All local users can change the parameters at any
So I'd recommend to keep things as they currently are.
(In reply to comment #1)
> Note! This is not secure if you are in an untrusted multiuser
> environment. All local users can change the parameters at any
> So I'd recommend to keep things as they currently are.
Enabling SHMConfig for the average user is quite difficult especially now that F10 ha no xorg.conf by default.
Moreover Synaptics touchpads are installed on laptops which are hardly "multiuser systems".
Even if so, I don't see how messing with the touchpad configuration may be a security hazard. The worst possibile outcame is a non-working touchpad.
I think I'd agree with comment #2. If the worst issue is somebody screwing with my touchpad settings, I think it's worth the risk. But, that being said, do we know when input properties can be expected to be available on Fedora? If I'm not mistaken, input properties will be merged into xserver-1.6. Will this be incorporated in F10 or held off to F11?
For the records, I made gsynaptics work on my laptop (which is Fedora 9,
though) by adding the line:
<merge key="input.x11_options.SHMConfig" type="string">true</merge>
in the file
just after the line:
<match key="info.capabilities" contains="input.touchpad">
A restart of hald and X (or a reboot) is needed after the change
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
*** Bug 475949 has been marked as a duplicate of this bug. ***
I agree with #2.. I still don't have my touchpad working.. Do I have to restart to make it take effect?
yes, a restart of the system (or at least for the hal daemon and Xorg) is needed
Man, I just had this all working and today it's reverted to the way it was before.. What the !@#$
OK, I still have the change from comment #4, but my touchpad scrolling isn't working anymore.. GSynaptics says I have to set SHMconfig to true, but I didn't change it since I had it working.. What's going on?
The file we modified is probably not marked as "%config" in the RPM so it will get overwritten each time there is an update to the package owning it.
(In reply to comment #11)
> The file we modified is probably not marked as "%config" in the RPM so it will
> get overwritten each time there is an update to the package owning it.
That wasn't it.. I have made the change listed here but every once in a while my system comes up with the touchpad not working, and says I need to set SHMConfig to true.. Rebooting generally brings it back so there's something else at play here.
To the ridiculously intelligent developers out there... When does this feature become enabled by default???
In particular, why can't this just be included in the standard Redhat Mouse Configuration Utility? I just want to be able to disable tapping without going through hours of stupid restarting, etc.
BTW in case you guys didn't know, it's called a mouse, and it's part of the primary interface to the computer for 99.9% of the people who use a computer and DONT WANT TO USE THE COMMAND LINE TO SET A SIMPLE PREFERENCE WHICH IS ALREADY INCLUDED WITH EVERY OTHER OPERATING SYSTEM.
(In reply to comment #13)
> To the ridiculously intelligent developers out there... When does this feature
> become enabled by default???
Never. As has been said in the past, SHMConfig is both potentially insecure and a hack of a solution.
> In particular, why can't this just be included in the standard Redhat Mouse
> Configuration Utility? I just want to be able to disable tapping without going
> through hours of stupid restarting, etc.
You are free to enable SHMConfig on your own machine if you desire
However, the real point to be made here is that full xinput properties support is now included in the synaptics driver. I've been running happily with it for several weeks now (I run xorg from git). Not only does it not require SHM ugliness, but it presents a nice uniform interface to configure all input devices. Now someone just needs to write a GUI for it (a task I might take up soon). This should be integrated in F11.
(In reply to comment #14)
> You are free to enable SHMConfig on your own machine if you desire
I had this enabled before but now it's reverted to whatever default settings are.. I certainly think configuring my laptop touchpad should be a whole heck of a lot simpler than it is right now.
I Ben's fix gets into F11 then I agree that would be the best solution. All I want to do is disable tapping -- feel like that was on Ubuntu's mouse preference already but can't remember.
I agree that SHMConfig is a bad program and should be unnecessary, but it is just difficult to see all this "dwell click" stuff in the standard Fedora mouse preference dialog, but still no "disable tapping" box.
(In reply to comment #16)
> I Ben's fix gets into F11 then I agree that would be the best solution. All I
> want to do is disable tapping -- feel like that was on Ubuntu's mouse
> preference already but can't remember.
It's already in Rawhide although I don't believe there's a UI for it yet.
> I agree that SHMConfig is a bad program and should be unnecessary, but it is
> just difficult to see all this "dwell click" stuff in the standard Fedora mouse
> preference dialog, but still no "disable tapping" box.
Understandable, F11 will be released soon enough.
Every time I think I've figured out which updates mess this up, some new thing messes with it. Right now I am typing this and not only is my scroll not working, but I have to press hard on the touch pad every few seconds to unfreeze the computer! This is CRAZY!!! AAND WHHHHHHHHHHHHHHHHHHHH WHY is the touchpad causing keys to repeaaaaaat?????
I'm seeing weird behaviours in the latest version.. Tapping enables itself, and then the system will freeze for brief periods, and unfreeze when I press hard on the touchpad.. I'm not even rebooting; I'll turn off tapping and the freezing goes away but a while later tapping turns back on apparently on it's own.
In fedora 11 on KDE4, I have Gsynaptics that is now enabled (had to manually "yum" it!), i can get the tapping (which i want to use) activated so that it works perfectly, however when i log out and in / restart the workstation the settings resort back to default. Also it is not included in the KDE4 menu so i have to run it manually.
so, it seems the way to go is not gsynaptics anymore, but the gpointing-device-settings project.
I submitted a package in bug 509310 if anyone wants to help with the review it will be surely appreciated by a lot of users ;)
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.