Bugzilla – Bug 121861
ksynaptics seems not to be gcc4 patched and therefore it doesn't work
Last modified: 2005-11-16 10:51:23 UTC
ksynaptics is not working and the source packages are not gcc4 patched. I had the problem with Fedora Core 4 some weeks ago, and contacted the maintainer, Stefan Kombrink. He aa nswered (translated into english): > Okay, ich had a second look into the sources: > > in touchpad.h: > ============== > Delete the line > static const double coastingSpeedThreshold = 38 > > > in touchpad.cpp: > =============== > > void TouchPad::setCoastingEnabled( bool enable ) > { > if ( !isValid() ) > return; > > if ( enable ) > SYNSHM->coasting_speed = coastingSpeedThreshold; // set to reasonable > speed > else > SYNSHM->coasting_speed = 0.0; // disable it completely > } > > exchange with > > void TouchPad::setCoastingEnabled( bool enable ) > { > if ( !isValid() ) > return; > > if ( enable ) > SYNSHM->coasting_speed = 38; > else > SYNSHM->coasting_speed = 0.0; // disable it completely > } This solved the problem with Fedora Core 4. You can contact the author by yourself, he is very friendly, but very busy abousynaptics at the moment because they try to integrate it into KDE 3.5. Roland
*** Bug 121862 has been marked as a duplicate of this bug. ***
Hm, sorry, for bringing back to topic, but: This bug is now almost a month old, the description is clear, and it comes with a solution (!) - why isn't this fixed? What did I do wrong? I mean, I was easily able to fix it by myself, so that can't be the big deal for other people. I don't get it why now one cares or does anything even if there is a fix included in the bug report. What else do I have to do until someone cares and compiles new packages?
because we can only work as hard as we do. If Stefan finishes his code in kdereview, he will release a new version and then the bug will be fixed too. For this reason there is little reason to act on this right now
The problem with this bugreport is that you basically posted the diff between ksynaptics 0.2.0 and 0.2.1, which in the changelog reads as this: " Just a compilation fix on GCC4 and AMD64 machines. More to come, stay tuned! " And it indeed is just that - a compilation fix. if you notice that we ship binary packages compiled with GCC 4 - you must have come to the conclusion that we already ship this patch. And indeed we do, otherwise the stuff plain does not compile. So we already fixed the report in the final 10.0 packages you have installed. you can see so in the changelog of the binary package: === Cut === Tue Apr 19 2005 - ro@suse.de - fix build with gcc-4 === Cut === however, what is "broken" about them remains a mystery. Please consider explaining what problems you have with the existing package, then we might be able to help and debug or fix the problem. Otherwise this will be closed as FIXED in a few days.
Ok, here a detailled description: When I try to deactivate the touchpad, the kcontrol-plugin accepts this, and there is not failure message in the shell. But the behaviour of the touchpad does not changes, the touchpad is still activated. In the other way, when the touchpad is deactivated, and I try to activate it with the kcontrol plugin, the plugin accepts the change without any error message (not even in shell). It works when I use the shell commands: 'synclient TouchpadOff=1' turns it off, wiht a 0 it turns it on.
ok, the patch you posted has nothing to do with that problem. do you see one of these messages when opening the config dialog? "Access denied to driver shared memory" "Shared memory segment size mismatch" "Error attaching to shared memory segment" they should appear on the console. I'm not 100% sure if they can at all given that we (unfortunately) compile without debug. are you sure that the synaptics daemon is running at all? can you please run this command: strace -o /tmp/something -v kcmshell ksynaptics and then toggle the driver to "off" and then bzip2 /tmp/something and attach it to this bugreport?
> ok, the patch you posted has nothing to do with that problem. Hm, sorry than, I thought because whne I once had this problem, it was solved by this. > do you see one of these messages when opening the config dialog? Nothing. But something more: when I deactivate the touchpad with 'synclient TouchpadOff=1' and then switch in kcmshell ksynaptics the mode to activate or deactivate (it doesn't matter), it is activated again. So there happens something at least, when the Touchpad is deactivated. > are you sure that the synaptics daemon is running at all? Well, 'synclinet' works great, what else should I check? > can you please run this command: did it...
Created attachment 56145 [details] strace kcmshell ksynaptics output
Packman released a 0.2.3 package, I tested it, it worked properly for me. So from my point of view this bug can be closed with "Later" or something.
SUSE also has ksynpatics 0.2.3 package (should be available in supplementary/KDE too tomorrow), so unless otherwise stated let's consider it as it.