Closed GoogleCodeExporter closed 8 years ago
I am getting the same error, Kubuntu 12.04 as well.
Original comment by love.br...@gmail.com
on 1 May 2012 at 3:53
Same here, 12.04 desktop.
Original comment by explodin...@gmail.com
on 1 May 2012 at 5:23
Yes, the segfault is solved:
http://code.google.com/p/touchegg/issues/detail?id=148
Anyway, after some uTouch-GEIS API changes looks like Touchégg doesn't works
fine in Precise.
Original comment by jose.exposito89@gmail.com
on 3 May 2012 at 10:59
I still have the same problem and I don't understand the solution provided
above...
Any help?
shing@ubuntu:~$ touchegg
Reading config from "/home/shing/.config/touchegg/touchegg.conf"
Segmentation fault (core dumped)
Original comment by LauShing...@gmail.com
on 25 May 2012 at 9:39
Check the issue #148 please. The segfault is solved but the Precise
compatibility not.
Original comment by jose.exposito89@gmail.com
on 25 May 2012 at 11:23
i have got the exact same error in ubuntu 12.04 which clearly indicates ubuntu
12.04 is far the most unstable software in ubuntu history, it kinda sucks in
all ways
http://forumtest17.blogspot.se/2012/05/not-be-in-hurry-to-install-ubuntu-12.html
ubuntu:~$ touchegg
Reading config from "/home/test/.config/touchegg/touchegg.conf"
Segmentation fault (core dumped)
Original comment by forum.te...@gmail.com
on 27 Jun 2012 at 1:05
I've got this same problem. If someone could point us to the problem (and
maybe show us how to get started editing the code) we could track this down
fairly quickly. What is making it incompatible with Presice?
Original comment by Gregory....@gmail.com
on 30 Jun 2012 at 5:03
Any update on this? I'm using 12.04.1, which is hopefully a bit more stable,
and I'm getting the same segfault. Has it been revisited since the .1 update?
Original comment by joslin.g...@gmail.com
on 20 Oct 2012 at 8:37
Download and compile the source code from the SVN please:
http://code.google.com/p/touchegg/wiki/CompileSourceCode
Original comment by jose.exposito89@gmail.com
on 21 Oct 2012 at 11:40
Original issue reported on code.google.com by
r.c.bruno.andre@gmail.com
on 1 May 2012 at 11:00