THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#705 - Awesome freezes when switching from console -> back to X
User who did this - Jim Pryor (Profjim)

----------
I may have found a necessary condition for the bug. My laptop has a touchpad 
(AlpsPS/2 GlidePoint), and I use the synaptics driver for it, with hal/evdev 
input hotplugging. I have a custom  /etc/hal/fdi/policy/11-x11-synaptics.fdi 
file, to customize some of the settings for that driver.

Formerly, one needed to use have the SHMConfig set to a boolean true value in 
order to be able to dynamically change the driver settings from inside X. Some 
GUI tools for configuring the driver also required this.

In my fdi file, that looks like:

<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
 <device>
   <match key="info.capabilities" contains="input.touchpad">
     <match key="info.product" contains="AlpsPS/2 ALPS">
       <merge key="input.x11_driver" type="string">synaptics</merge>
     </match>
        ...
          <match key="input.x11_driver" contains="synaptics">
                <merge key="input.x11_options.SHMConfig" 
type="string">true</merge>
        ...
          </match>
   </match>
 </device>
</deviceinfo>


I shut that off several hours ago, and started X, and since then the bug has 
not appeared. Even starting gpm doesn't make it show up.

Now it turns out that this setting doesn't need to be on anymore: see 
<http://fedoraproject.org/wiki/Features/InputDeviceProperties>. That's why I 
turned it off. But even if that's true, it will take some time for users to learn 
this, and for GUI tools that now require SHMConfig to be true to be rewritten to use 
the new communication channel.

Until the use of SHMConfig has worked out of the userbase, this bug may bite 
anyone who uses the synpatics touchpad driver, and who ever switches between 
virtual consoles and X.



----------

More information can be found at the following URL:
http://awesome.naquadah.org/bugs/index.php?do=details&task_id=705#comment1706

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to [email protected].

Reply via email to