Same here.

Alberto

Reassigning to Mike Wolf, as he took care of the original bug with GSynaptics.  Mike, is this enough info to proceed, or do you need something else?

I have been reading this bug, and #402536 and also the bug I posted as #402447.  These seem to be different descriptions of the same problem.  What do you guys think?

#402447 sounds similar, this one is caused by gsynaptics also. Looking at your bug report it sounds like you may have the same problem. GSynaptics didn't output sensitivity settings so your mouse stopped working. Easiest way of fixing it as a workaround which worked for me was to run gsynaptics set the sensitivity and acceleration settings (The min and max in your case also are zero and sensitivity is zero). When you login again your mouse should work again.

Looking at the output of gsynaptics, there is nothing really wrong with it.  It all depends on what the programmer intended.

If you delete the parameter file completely, the touchpad works with default settings.  In my case, "tap to click" is on (which I do not like) and "auto-scrolling" is on, (which I also do not like) and a bit of "acceleration" is on (which I do not mind).

If gsynaptics is only supposed to output the changes from the default, then it is working correctly.  In that case, the problem is that the program that reads the parameter file is mistakenly losing settings that it should keep.

The only way to know for sure is to open up the source code and read any comments made by the programmers -- which is what I was hoping I would not have to do.  I was hoping that someone would recognize what was going on and say "gee, I guess I forgot to set a variable here" and then a simple change would be made and we would all be happy.

Life is never that simple is it? :-)

Deleting the settings is a temporary fix on the next login the values will be seen as zero for acceleration and sensitivity (after you run gsynaptics) which dont seem to be written on the first login at least for me they aren't (unless you adjust them on the first login, using the sliders stops it from happening forcing it to write the settings).

I've having a problem like this too.  Once I put my laptop into sleep mode, and then restore it, the touchpad no longer works.  My trackpoint mouse does though.

I am deciding whether to remove 11.0 and load 10.3.  So if anyone wants me to upload something like a "conf" file or "log" file, now is the time to ask.

Since I'm basically having the same issue as you, I can cover any sort of log / configuration files anyone may need.  So... Feel free to revert to 10.3 if you wish.  :-)

Thankfully, my laptop has the Trackpoint built into it, which I use more anyway.

I replaced 11.0 with 10.3 yesterday.  Best of luck!

Actually, I prefer the "trackpoint" if I have it available.  Unfortunately, this computer did not come with one. :-)

Same issue on a Dell d820, trackpoint works but touchpad is about as useful as an ashtray on a motorbike for controlling the pointer.  The scroll functions on the touchpad function correctly.

I see this bug as well. I can repro using the following steps:

1) Unset all your touchpad settings in gconf /desktop/peripherals/touchpad
2) SaX2 -r
3) Restart X
4) Run GSynaptics (Touchpad settings in Control Center)
5) Change e.g. Acceleration
6) Restart X

Touchpad no longer working due to wrong settings in GSynpatics, such as 0 acceleration.

When can we expect a fix for this in Update?

Same problem here. I have HP 530 laptop running Gnome. The problem occured when I changed touchpad sensitivity level (Touchpad settings in Control Panel).

Deleting ~/.gconf/desktop/gnome/peripherals/%gconf.xml helped.

It seems like any change of touchpad settings in Control Panel zeroes settings in the /desktop/peripherals/touchpad/%gconf.xlm file.

Please let me know if you need any logs or testing.

The same issue again when I enabled external mouse in Yast. No response from my touchpad after logging out and in. 

My ~/.gconf/desktop/gnome/peripherals/touchpad/%gconf.xml now looks like that:

<?xml version="1.0"?>
<gconf>
        <entry name="sensitivity" mtime="1217534609" type="int" value="2">
        </entry>
        <entry name="vert_scroll_delta" mtime="1217534599" type="int" value="100">
        </entry>
        <entry name="max_tap_time" mtime="1217534599" type="int" value="180">
        </entry>
        <entry name="off" mtime="1217534599" type="bool" value="false">
        </entry>
</gconf>

I solved the problem by deleting ~/.gconf/desktop/gnome/peripherals/%gconf.xml again.

Can anyone of openSUSE development team take a look at this issue once more, please?

***

Update: The problem reoccurs almost each time the system is rebooted. 
Michael, do you have any idea to get rid of this bug?

It looks like I happened to find a workaround of the issue. 

[Control Centre] > [System] > [Sessions] > [Startup programs]
Edit [Touchpad]. 
Replace: gsynaptics-init --sm-disable 
with: gsynaptics-init on

I hope it works for you guys as well.

When I switched back to 10.3 (64-bit) I hoped that this bug would be resolved.  Unfortunately, in the original 10.3 distribution, "gsynaptics" was not included at all.  At a later date, someone asked for it to be included (because as you all know, these touchpads often need the adjustments badly).  So the "gsynaptics" from 11.0 was brought down to 10.3, along with its bugs.

I tried it out and yes, the bug still exists.  I opened a bug report (bug 408611) of the chance that it might be a different bug, and I had a particular thought in mind about the fact that mine is in 64-bit, and have not been looking into it since.

The above work around ("gsynaptics-init on") does not work on my system.

Recently, the bug was closed, however, when this was done the person who closed it identified another bug like this, which had been resolved prior to 11.0 final.  I downloaded the sources for "gsynaptics" and the latest version (that we are currently using) has changed since then.

Unfortunately this affects my EEE PC 1000 also.

I deleted ~/.gconf/desktop/gnome/peripherals/%gconf.xml, but that has not fixed it for me yet.  I dropped down to init 1 to make sure nothing was holding the values in the memory, and then I loaded up init 5 again.  I yet can not use my mouse.

Before I removed it, I did take a look at the contents, and it was blank.  I'll post anything I figure out...

Alright.  So if I remove that file, and then restart the system, it works as it should.  init 1 is not enough apparently.

Before I restarted, I tried running sax2, and the mouse would not function in there either.  It's almost like it just somehow just turns it off.

Now that EeePC has been mentioned, I have been using one of the earlier EeePC 701 computers since around spring, and the touchpad setting *does* work on it.  So you are saying that it has broken for them too now?  I am posting this message right now using the 701, and my preferred touchpad settings have been stable, I think, at least as far back as April or May.

Interesting.

The EEE PC has only done that to me once.  My Thinkpad (T43p) on the other hand I've had more mouse issues with.  I've had that much longer though.

This issue only affects 11.0, it wasn't present in 10.3 and isn't present in 11.1Beta1. 11.1 shows normal and expected behaviour.

That is not quite correct.  I opened a bug for 10.3 64-bit and somebody else closed it, claiming it was fixed.  It might have been fixed in 32-bit, but the bug is definitely still there in 64-bit.  I have not re-opened that bug because, I think that if it gets fixed "here" then it should be possible to back-port it later.  But no, the bug is NOT fixed in 10.3 -- at least not completely.

This bug I think may be still present in OpenSUSE 11.1 Beta 2.  Before I restarted, I was unable to use my touchpad, and after looking in ~/.gconf/desktop/gnome/peripherals/, there was a blank %gconf.xml.

However, a reboot fixed the problem, where a restart of xdm would not.  So maybe the issue I just had was a variant of this issue.  It happened to be once before actually, now that I think about it.  I was using OpenSUSE 11.1 Beta 1 then.

Yeah, the issue still exists in OpenSUSE 11.1 Beta 2.  The touchpad will not start working again until I get rid of the blank %gconf.xml file.  After I do that, and then restart, it works fine.

FWIW, I see this issue on my Dell D620 as well - "circular scrolling" is turned on by default which makes the touchpad nearly unusable for me, and if I go into the touchpad settings and turn that setting off and restart X, the touchpad works until gsynaptics-init runs - then it dies.

If I run gsynaptics-init from a terminal window, I get the following message:

[jhenderson@jshlaptop-dell ~]$ gsynaptics-init --sm-disable

** (gsynaptics-init:24087): WARNING **: Using synclient
Unknown parameter CoastingSpeedThreshold

I've grepped through the gconf files and am not able to find this particular parameter.  Hopefully this will be of help to someone.

This laptop does have a trackpoint, but I hate using that even more than using a regular mouse.

(In reply to comment #16 from Sebastian Barylski)
> It looks like I happened to find a workaround of the issue. 
> 
> [Control Centre] > [System] > [Sessions] > [Startup programs]
> Edit [Touchpad]. 
> Replace: gsynaptics-init --sm-disable 
> with: gsynaptics-init on
> 
> I hope it works for you guys as well.
> 
A similar workaround suggested in the forum (http://forums.opensuse.org/hardware/laptop/397482-touch-pad-problems.html#post1883302) by modulep worked so far for me that I could use my touch pad again after going to control panel>sessions, unchecking 'touchpad' and rebooting.
But I was still being unable to change the configuration of my synaptics touch pad by gsynaptics - gsynaptics did not start and opensuse 11.0 was saying: "GSynaptics couldn't initialize.
You have to set 'SHMConfig' 'true' in xorg.conf or XF86Config to use GSynaptics
"
But neither that suggested change in XF86Config did bring Gsynaptics to work nor did 'SHMConfig'='on'.
Instead after trying to change something (reconfigure in SaX2, uninstalling and reinstalling gsynaptics, ect.) the touch pad worked generally but it's virtual mouse wheel did not.

So I reconfigured my touch pad manually and changed boot options permanently like described in http://de.opensuse.org/SDB:Konfiguration_des_Synaptics-Touchpad_unter_SUSE_LINUX_9.1 .

Now my touch pad works with the virtual (vertical) mouse wheel.

P.S.: I would find this keywords useful but could not ad them (they seem to be not "legal" - maybe "illegally"???): mousepad, mouse, laptop, notebook, touchpad, touch pad, gsynaptics

This bug seems to be a duplicate to Bug 403727 - "Gnome break synaptics driver settings completely"
https://bugzilla.novell.com/show_bug.cgi?id=403727.
Maybe someone can put them together (I do not know how to do it and do not know for sure thats the same bug)?
P.S.: "synaptics" would be a possible keyword for this bug too but its also a trademark or something like it so there could be really legal difficulties. 

To answer your question, no, I do not think they "look" the same.  In that case, fixing one might or might not fix the other.  In any case, at this point, there is no point to combining them. since they have both been open for quite a while now.  One would hope that one or the other will be solved soon, and then we will know for sure whether the other can be closed too.

hmm ... no activity and i still see the bug in Beta 5.

let's make some fuss.

This actually happened to me yesterday.  Actually, something I think I've noticed...  It seems to mainly happen after the system crashes.  It has not been a very common bug for me, as it was before, but I think it's still lurking deep down.

After my EEE PC froze up yesterday (no idea why, but it's been happening), when I restarted it, I was unable to use the mouse at the GDM screen.  I had to navigate with the keyboard to select the shutdown option on the GDM screen.  After it shut down, when I turned it on again, and when GDM launched, it worked again.  So, I don't know...

Otherwise, I have not seen this issue in a while.

for me, it's actually quite different:
- touchpad works in the GDM screen
- turns off at certain point of time when starting GNOME
- i can reenable it by setting "min speed" to maximum, but then it's unusable
- when i log off, i can't use it even in GDM
- but while in GDM, the "enable/disable touchpad" button on my laptop works, so i can reenable touchpad this way

my machine is MSI PR200, that's 64bit centrino duo, touchpad is synaptic

Yeah, so what I had yesterday was probably unrelated and just kind of a random occurrence of something similar.

Re Comment #32 - this is very similar to the symptoms I have seen and reported under issue 403727.  I am sure that the two bugs should be handled together, even if they are not the same.

*** Bug 448284 has been marked as a duplicate of this bug. ***

*** Bug 403727 has been marked as a duplicate of this bug. ***

Submitted fix to oS:F: submission #4072.

Resolved?
what was the problem?
What is the fix?
I reported it for 11.0 (#403727). Is it fixed for 11.0?
How do I get the fix?

(In reply to comment #38 from Robert Harvey)
> Resolved?
> what was the problem?

gsynaptics doesn't support a partial configuration stored in gconf, but makes it possible to get this result.

> What is the fix?

A patch in the new package, taken from Debian.

> I reported it for 11.0 (#403727). Is it fixed for 11.0?
> How do I get the fix?

Unfortunately, an update for 11.0 won't be allowed for this (there's a really strict policy), so the fix will only be in 11.1.

Fortunately, we have the build service, so you can get a fixed package from the home:vuntz:11.0-testing project there. Or go directly to http://download.opensuse.org/repositories/home:/vuntz:/11.0-testing/openSUSE_11.0

Have we stopped updating 11.0?  I don't understand why a patch isn't officially available for 11.0.  It's broken in 11.0, and should be fixed in 11.0.

(In reply to comment #40 from Jim Henderson)
> Have we stopped updating 11.0?  I don't understand why a patch isn't officially
> available for 11.0.  It's broken in 11.0, and should be fixed in 11.0.

I got several updates (including fix for crashes) for packages in 11.0 rejected, so my understanding is that only really major fixes should go in. If you want to try to push for an update, go ahead.

Thanks, Vincent, how would one go about doing that?

It is working in 11.1 "RC2" in 32-bit.

Test unit is an HP-2133 Mini.

This is an autogenerated message for OBS integration:
This bug (402864) was mentioned in
https://build.opensuse.org/request/show/4072 Factory / gsynaptics