anodynos / touchegg

Automatically exported from code.google.com/p/touchegg
4 stars 1 forks source link

Segfault on Ubuntu Oneiric Alpha #81

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hi,

sometimes, after running for a longer time, touchegg crashes with a segfault. I 
could not reproduce the problem for a specific situation.

This is the output:

[+] New gesture: 
    Type      ->  "TAP" 
    Fingers   ->  2 
    Direction ->  "NO_DIRECTION" 
    Action    ->  "SEND_KEYS" 
    App Class ->  "Anjuta" 
    Gesture Start 
    Gesture Update 
    Gesture Finish 
[+] New gesture: 
    Type      ->  "" 
    Fingers   ->  0 
    Direction ->  "" 
    Action    ->  "NO_ACTION" 
    App Class ->  "Anjuta" 
    Gesture Start 
Speicherzugriffsfehler (Speicherabzug geschrieben) (<- that's a german segfault 
;) )

My touchegg.conf file appears to be correct, so that's probably not where this 
"typeless" gesture comes from.

Original issue reported on code.google.com by Linus.Seelinger on 15 Jul 2011 at 6:14

GoogleCodeExporter commented 8 years ago
Wooha - I just got this in the output:

X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x0

However, that did not crash anything. Looks funny though ;)

Original comment by Linus.Seelinger on 15 Jul 2011 at 6:16

GoogleCodeExporter commented 8 years ago
Hi, thank you very much for report!

Please, could you test this with the new SVN code? I think that the lastest 
changes can (or not) solve the problem... And, could you attach your 
touchegg.conf please?

Anyway this SVN code is not definitively, I'm waiting for this bug: 
https://bugs.launchpad.net/utouch-geis/+bug/810637
To make the 1.0 version.

Note that some stuff have change in the current SVN code, like the path of the 
configuration file (now ~/.config/touchegg/touchegg.conf) and some stuffs like 
the send keys action (now looks like Control+A for example) check the wiki 
please:
http://code.google.com/p/touchegg/wiki/AllActions

Thank you very much!

Original comment by jose.exposito89@gmail.com on 16 Jul 2011 at 3:15

GoogleCodeExporter commented 8 years ago
Hi, thank you very much for report!

Please, could you test this with the new SVN code? I think that the lastest 
changes can (or not) solve the problem... And, could you attach your 
touchegg.conf please?

Anyway this SVN code is not definitively, I'm waiting for this bug: 
https://bugs.launchpad.net/utouch-geis/+bug/810637
To make the 1.0 version.

Note that some stuff have change in the current SVN code, like the path of the 
configuration file (now ~/.config/touchegg/touchegg.conf) and some stuffs like 
the send keys action (now looks like Control+A for example) check the wiki 
please:
http://code.google.com/p/touchegg/wiki/AllActions

Thank you very much!

Original comment by jose.exposito89@gmail.com on 16 Jul 2011 at 3:15

GoogleCodeExporter commented 8 years ago
The current SVN code looks good so far! Still, I will have to test it for a 
while, as these X errors occurred only sometimes.

By the way, do composed gestures already work? I'm really looking forward to 
that as both my touchpad and my touchscreen only support 2 fingers ;)

This is my current touchegg.conf (I already changed it to the new key names, 
but could not test the SEND_KEYS actions yet):

<touchégg>

    <settings>
        <property name="composed_gestures_time">0</property>
    </settings>

    <application name="All">        

        <gesture type="TAP" fingers="2" direction="">
            <action type="SEND_KEYS">Alt+F11</action>
        </gesture>

        <gesture type="DRAG" fingers="2" direction="DOWN">
            <action type="MINIMIZE_WINDOW"></action>
        </gesture>

        <gesture type="DRAG" fingers="2" direction="UP">
            <action type="MAXIMIZE_RESTORE_WINDOW"></action>
        </gesture>

        <gesture type="DRAG" fingers="2" direction="LEFT">
            <action type="CLOSE_WINDOW"></action>
        </gesture>

        <gesture type="DRAG" fingers="2" direction="RIGHT">
            <action type="SEND_KEYS">Alt+F12</action>            
        </gesture>

    </application>
    <application name="Gmpc">
        <gesture type="DRAG" fingers="2" direction="DOWN">
            <action type="SEND_KEYS">Ctrl+Right</action>            
        </gesture>
    </application>
</touchégg>

Original comment by Linus.Seelinger on 21 Jul 2011 at 2:56

GoogleCodeExporter commented 8 years ago
Hi!

The X errors are not problem, are errors of Xlib, not Touchégg. If you test 
some applicatios that uses Xlib (like KWin or Compiz) you will probably get the 
same errors.
I think that the segfault will be solved, anyway, if you find any problem 
please, report!

> By the way, do composed gestures already work?

Yes, you only need to adjust the "composed_gestures_time" property, for example:

    <settings>
        <property name="composed_gestures_time">135</property>
    </settings>

This "135" are the miliseconds between the tap and the other composed gesture, 
remember that now you can use TAP_AND_HOLD and DOUBLE_TAP.

Thanks for your report. I'll mark the problem as solved for the moment, but 
I'll reopen the issue if you found any problem
Greetings!

Original comment by jose.exposito89@gmail.com on 21 Jul 2011 at 3:06