Segfault on access to user data passed to action callback

As a workaround instead of:

  notification.add_action(id, name, callback, data)

use:

  notification.add_action(id, name, lambda n, id: callback(n, id, data))

Fixed package is uploaded to my PPA: https://launchpad.net/~kriomant/+archive

Thank you for taking time to report this. Unfortunately I can not reproduce this with the test file you provided (It just shows a little notification "Matt is online" and thats it. No segfault (I run Intrepid).

Can you try it with a new user created on your system and maybe a clean install (dual boot or virtualbox should be enough). Thanks in advance.

Did you click notification? It is needed to reproduce segfault.

If you did and got no segfault, I'll try to reproduce bug on clean installation.

I forgot to klick it, thanks for reminding me, but I still get no segfault. Here is the terminal output:

1) Left click on the notification
martin@martin-laptop:~/Desktop$ python test-default-action.py
You clicked the default action
User data: <__main__.A instance at 0x1e82bd8>

2) Left click on the "x" (close) button (I had to press [ctrl] + [c] because the python script didn't quit itself):
martin@martin-laptop:~/Desktop$ python test-default-action.py
^CTraceback (most recent call last):
  File "test-default-action.py", line 29, in <module>
    gtk.main()
KeyboardInterrupt

3) Right click on the notification:
martin@martin-laptop:~/Desktop$ python test-default-action.py
You clicked the default action
User data: <__main__.A instance at 0x1ed6bd8>

Seems like the problem is actually related to your configuration. Maybe a new user is enough do avoid the segfault. Thanks for trying.

Just tried it on Ubuntu Intrepid Live CD. I don't even have to install pynotify, it is installed by default.

ubuntu@ubuntu:~$ python test.py
You clicked the default action
Segmentation fault (core dumped)
ubuntu@ubuntu:~$ python --version
Python 2.5.2
ubuntu@ubuntu:~$ dpkg-query -W python-notify
python-notify 0.1.1-2build1

Please try modified version of test with forced garbage collection. It is the only thing (which I know about) that may affect segfaulting, since reference is definitely isn't hold in code and object must be freed.

I am sorry, but still no segfault :)

martin@martin-laptop:~/Desktop$ python test-default-action-gc.py
You clicked the default action
User data: <__main__.A instance at 0x27496c8>
martin@martin-laptop:~/Desktop$ python --version
Python 2.5.2
martin@martin-laptop:~/Desktop$ dpkg-query -W python-notify
python-notify 0.1.1-2build1

Hm...this is interesting. I have two computers here and the one is segfaulting with your examples but the other is not segfaulting. The only remarkable difference is that the segfaulting computer runs Ubuntu 32-bit and the non segfaulting computer runs Ubuntu 64-bit

In response to comment #10, I can't get this to segfault on 64bit Maverick alpha 1. I don't have any 32bit computers to test it on, but if someone could test the attached test-script on a 32bit install, that would be greatly helpful.

Thanks!

Reproduced on Lucid 32bit.
Interesting that it segfaults if you click button using mouse, but it hangs if you press button using keyboard.