Segmentation fault (core dumped)

Bug #196431 reported by kporter
4
Affects Status Importance Assigned to Milestone
gestikk
High
Friedrich Weber

Bug Description

Possible bug found on line 220 in start_config.py on main brach located at https://code.launchpad.net/gestikk bzr branch lp:gestikk.

Line 220 in start_config.py gives Causes above error, If I comment all lines pertaining to about button, gestikk works as expected.

Thanks,
Kporter

Revision history for this message
Friedrich Weber (fredreichbier) wrote :

Hello,

first, thanks for your bug report. I don't have this problems, so could you please post some details of your system, which distribution do you use, the version of Python and the wxPython version?

Thank you,

Fred

Changed in gestikk:
importance: Undecided → High
Revision history for this message
kporter (kportertx-yahoo) wrote :

hp-pavilion ze2315us

$ uname -srvm
Linux 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686

$ cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"

$ python --version
Python 2.5.1

Kubuntu-desktop 1.59
python-wxgtk2.8 2.8.4.0

Revision history for this message
kporter (kportertx-yahoo) wrote :

Took another look at this error, if I change wx.ID_ABOUT to another ID it works fine. So it is specifically ID_ABOUT on this program. Are these IDs part of wxPython?

Basically if I;
CHANGE
btnabout = wx.Button(pbuttons, id=wx.ID_ABOUT)
TO
btnabout = wx.Button(pbuttons, id=wx.ID_APPLY)
IT WORKS

Except after doing this, clicking that button gives an error :).

Revision history for this message
Friedrich Weber (fredreichbier) wrote :

I have no idea why this crashs. Maybe you have compiled GTK+ oder wxGTK on your own?
That values are just Stock IDs, which cause wxPython to display a yellow star on the 'About'-Button. You could also change this line to

btnabout = wx.Button(pbuttons)

Maybe I will remove the button in the gestikk-0.4 branch.

What error? :)

Changed in gestikk:
assignee: nobody → fredreichbier
Revision history for this message
kporter (kportertx-yahoo) wrote :

The error is the same non descriptive segmentation fault (core dumped).
I tried just pbuttons, while that button can load now, clicking it gives the error now.
I tested the 0.4.1 and it works. Very strange.

Revision history for this message
kporter (kportertx-yahoo) wrote :

Later today I'll try reinstalling anything having to do w/ python.

Revision history for this message
Friedrich Weber (fredreichbier) wrote :

Very strange. I don't get any errors with that button.
However, Gestikk 0.5 will (hopefully) be fully ported to GTK, so that problems won't exist anymore.
What about
> Maybe you have compiled GTK+ oder wxGTK on your own?

Thanks for your work!

Revision history for this message
kporter (kportertx-yahoo) wrote :

> Maybe you have compiled GTK+ oder wxGTK on your own?
No, this would not be the case.

Revision history for this message
kporter (kportertx-yahoo) wrote :

OK reinstalling wxPython fixed the issue. Everything seems to work now, really like the project hope to see more, thanks!

Revision history for this message
Friedrich Weber (fredreichbier) wrote :

Thanks for the bug report!

Changed in gestikk:
status: New → Invalid
Changed in gestikk:
status: Invalid → Won't Fix
Revision history for this message
iomicifikko (iomicifikko) wrote :

Hi, i have the same problem here. When the program recognize a gesture (i tryed using different buttons for the gesture) gestikk exit with the error "segmentation fault".( "core dumped" doesn't appear)
If i set the debug mode, this is what appears:

DEBUG: Condition: True (then the usual error)

I'm on Ubuntu Hardy using gestikk 0.5.1, compiz enabled (same thing if disabled) no strange apps running in the background.

A few Info:

Linux 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686

Python 2.5.2

no Python-wxgtk2.8 installed

Bye

Revision history for this message
Friedrich Weber (fredreichbier) wrote :

Hello,

sorry for the late answer, I am not subscribed to this bug :/

That's strange. gestikk normally doesn't produce segmentation faults, because it is written in Python. Does that happen for every gesture, for keypress and command actions?

Greetings,

Fred

Changed in gestikk:
status: Won't Fix → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers