codywd / WiFiz-Deprecated

A NetCTL GUI Frontend. Deprecated, please start using NetGUI, as it is better all around. Beta, however.
7 stars 2 forks source link

wx._core.PyAssertionError #11

Closed dbrgn closed 10 years ago

dbrgn commented 10 years ago

I'm getting the following error when starting WiFiz 0.9.2.3.

Arch Linux with dwm window manager.

$ sudo wifiz 
Starting WiFiz
Starting Tray
Traceback (most recent call last):
  File "/usr/share/wifiz/main.py", line 755, in <module>
    start()
  File "/usr/share/wifiz/main.py", line 749, in start
    WiFiz(None, title="WiFiz")
  File "/usr/share/wifiz/main.py", line 127, in __init__
    self.APList.SetStringItem(0, 0, 'scanning...')
  File "/usr/lib/python2.7/site-packages/wx-3.0-gtk2/wx/_controls.py", line 4521, in SetStringItem
    return _controls_.ListCtrl_SetStringItem(*args, **kwargs)
wx._core.PyAssertionError: C++ assertion "id >= 0 && (size_t)id < GetItemCount()" failed at ./src/generic/listctrl.cpp(3283) in SetItem(): invalid item index in SetItem

(main.py:29169): GLib-GObject-WARNING **: gsignal.c:2593: instance '0x4e890f0' has no handler with id '287'

(main.py:29169): GLib-GObject-WARNING **: gsignal.c:2593: instance '0x4f44830' has no handler with id '448'

(main.py:29169): GLib-GObject-WARNING **: gsignal.c:2593: instance '0x4f4d1f0' has no handler with id '527'

(main.py:29169): GLib-GObject-WARNING **: gsignal.c:2593: instance '0x4ed2940' has no handler with id '391'

(main.py:29169): GLib-GObject-WARNING **: gsignal.c:2593: instance '0x37cdb90' has no handler with id '56'
swig/python detected a memory leak of type 'wxPyXmlSubclassFactory *', no destructor found.
Child died here

swig/python detected a memory leak of type 'wxPyXmlSubclassFactory *', no destructor found.
agboom commented 10 years ago

+1 for this error. I'm using the same version (0.9.2.3-r4) in Arch Linux and i3-wm 4.7 as window manager.

beatgammit commented 10 years ago

+1 as well. I'm using the same version (0.9.2.3-r4) in Arch Linux with GNOME Shell. Ran as root: sudo wifiz.

I'm using NetworkManager right now, but I'd like to switch back to netctl.

codywd commented 10 years ago

Sorry for no response guys. I just got a new laptop after my last one broke. I bought a new Lenovo y410p. I will be installing sexy linux on it after I figure out how to use Windows 8 UEFI and Arch together. Hopefully will have a fix this week. :)

codywd commented 10 years ago

Oh Lord. Stupid autocorrect. Arch Linux. Although it is sexy.

dbrgn commented 10 years ago

Haha, sexy linux. Best autocorrect ever :)

I just did the same (UEFI + Win8 + Arch) a few weeks ago. Make sure to create a recovery USB stick of your Windows install before starting to mess with the bootloader. Oh, and I'd recommend the Gummiboot bootloader over Grub2.

codywd commented 10 years ago

Alright, I have Arch now. Time to start on fixing this bug!

codywd commented 10 years ago

Did not mean to click "Close and Comment." Oops.

quizzmaster commented 10 years ago

I also got this message with the addition of:

swig/python detected a memory leak of type 'wxPyXmlSubclassFactory *', no destructor found.
codywd commented 10 years ago

So I found out why the issue was caused: wxPython 3.0 must have changed the way something is required to be coded, now I just need to find out what the new way is. Hopefully have a fix out tomorrow, maybe later tonight?

Oddly, my error is slightly different, talking about one of the toolbar buttons, and not the adding of networks...

*EDIT: Alright, fixed that error. Time to move on to this one (Thankfully, it is 100% reproducible, so I should be able to fix it soon.

codywd commented 10 years ago

For a note, after I fix this error, I am going to move back into working on NetGUI and hopefully get that version up and running, since it is written in a much better way. The only issue with that is it runs off of GTK3, and I'm not sure how that will work with non-GTK based wm/de, like KDE or dwm (if that isn't based off of GTK.)

codywd commented 10 years ago

Alright, this issue seems to be fixed in 0.9.2.4. I updated the PKGBUILD as well, so this should work fine now. If there are any more issues, please feel free to reopen this issue, or open a new one.

I am aware of the following issue: swig/python detected a memory leak of type 'wxPyXmlSubclassFactory *', no destructor found.

I am trying to figure out a fix, so hopefully I will get it soon :)

codywd commented 10 years ago

According to my research the following error is part of wxPython, and not specifically my program: "swig/python detected a memory leak of type 'wxPyXmlSubclassFactory *', no destructor found."

If you get this error, it is safe to ignore, according to the developers of wxPython. Hopefully, a new version will fix it.

Thanks for reporting the issues guys! Keep them coming :)