FS#29709 - [wicd-curses] crashes when trying to save network properties

Attached to Project: Arch Linux
Opened by halfie (halfie) - Wednesday, 02 May 2012, 15:04 GMT
Last edited by Isenmann Daniel (ise) - Sunday, 06 May 2012, 20:26 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Isenmann Daniel (ise)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description:

wicd-curses crashes when trying to save network properties

DBus failure! This is most likely caused by the wicd daemon stopping while wicd-curses is running. Please restart the daemon, and then restart wicd-curses.
Traceback (most recent call last):
File "/usr/share/wicd/curses/wicd-curses.py", line 921, in call_update_ui
self.update_ui(True)
File "/usr/share/wicd/curses/wicd-curses.py", line 88, in wrapper
return func(*args, **kargs)
File "/usr/share/wicd/curses/wicd-curses.py", line 932, in update_ui
self.handle_keys(input_data[1])
File "/usr/share/wicd/curses/wicd-curses.py", line 913, in handle_keys
self.diag.save_settings()
File "/usr/share/wicd/curses/netentry_curses.py", line 481, in save_settin
self.set_net_prop("enctype", "None")
File "/usr/share/wicd/curses/netentry_curses.py", line 448, in set_net_pro
wireless.SetWirelessProperty(self.networkid, option, value)
File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __ca
**keywords)
File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in cblocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Python.TypeError: Traceb(most recent call last):
File "/usr/lib/python2.7/site-packages/dbus/service.py", line 707, in _mes_cb
retval = candidate_method(self, *args, **keywords)
File "/usr/share/wicd/daemon/wicd-daemon.py", line 1067, in SetWirelessProy
prop = misc.sanitize_config(prop)
File "/usr/lib/python2.7/site-packages/wicd/misc.py", line 433, in sanitiznfig
return s.translate(None, table)
TypeError: translate() takes exactly one argument (2 given)

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:

1) Configure ("C") an network and then try to save it (F10).
This task depends upon

Closed by  Isenmann Daniel (ise)
Sunday, 06 May 2012, 20:26 GMT
Reason for closing:  Fixed
Additional comments about closing:  New package release -2. Don't forget to restart the daemon after update that the changes take effect.
Comment by stardogg champ (stardoggchamp) - Wednesday, 02 May 2012, 20:49 GMT
The following will hopefully fix the problem:

sudo rc.d stop wicd

/user/share/wicd/daemon/wicd-daemon.py:1067
change:
prop = misc.sanitize_config(prop)
to:
prop = misc.sanitize_config(str(prop))

sudo rc.d start wicd
Comment by pluto9 (pluto9) - Thursday, 03 May 2012, 01:36 GMT
I'm experiencing the same problem when I use wicd-gtk 1.7.2.4-1. I can't save the properties and it shows the similar error messages. Stardoggchamp's method solves the problem.
Comment by Willie (bananabrain) - Thursday, 03 May 2012, 10:13 GMT
1.7.2.4-1 doesn't pull any different dependencies.
A simple reversion back to 1.7.2.3-1 fixes everything for me.
Comment by Isenmann Daniel (ise) - Thursday, 03 May 2012, 11:28 GMT
I have reported it upstream, looks like a problem upstream:
https://bugs.launchpad.net/wicd/+bug/993912
Comment by Willie (bananabrain) - Thursday, 03 May 2012, 17:44 GMT
Comment by james bos (jampola) - Friday, 04 May 2012, 15:44 GMT
stardoggchamp, doing that solved the issue for me.

Had the same problem here using both gtk and curses clients.

Thanks,
James
Comment by Christian Hesse (eworm) - Sunday, 06 May 2012, 04:59 GMT
I am suffering this as well. Here is the official upstream fix: http://bazaar.launchpad.net/~wicd-devel/wicd/experimental/revision/770

Do we wait for next release or can we push 1.7.2.4-2?
Comment by pluto9 (pluto9) - Sunday, 06 May 2012, 06:20 GMT
I tried upstream fix eworm mentioned but it didn't solve the problem.
Comment by Christian Hesse (eworm) - Sunday, 06 May 2012, 07:26 GMT
Mh, it did fix it for me... Anybody else?
Comment by Isenmann Daniel (ise) - Sunday, 06 May 2012, 20:22 GMT
Patch does work for me, I will release a new package release...

Loading...