From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Peter Weilbacher <newsspam@weilbacher.org>
Subject: Re: [gentoo-user] wicd fails to set wireless connection
Date: Tue, 05 Jul 2011 11:00:57 +0200 [thread overview]
Message-ID: <1733345.vhZsb7yjbB@nazgul> (raw)
In-Reply-To: <iuui7k$paa$1@dough.gmane.org>
On Tuesday 05 July 2011 10:32:44 Peter Weilbacher did opine thusly:
> Since yesterday I cannot use wicd any more to get a wireless
> connection (wired still works fine). I think this has to do with a
> dbus update, but I'm not sure. I have done several restarts,
> re-emerged all relevant packages (dbus, dbus-python, wicd) but
> still it stops shortly after clicking the connect button in the GUI
> window, saying "Disconnecting active connections..." in the status
> bar (even though no connections were active).
>
> If I start wicd-gtk from the command line I sometimes get the errors
> below, but often it just "hangs". wicd-curses always fails reliably
> with the output below. Does that ring a bell with someone?
Is dbus actually running?
/etc/init.d/dbus status
ps axu | grep dbus
I had an issue recently where the init script claimed dbus was running
but ps proved it had died
>
> Cheers,
> Peter.
>
> $ wicd-gtk
> Has notifications support True
> Loading...
> Connecting to daemon...
> Connected.
> displaytray True
> Done loading.
> Traceback (most recent call last):
> File "/usr/share/wicd/gtk/wicd-client.py", line 645, in
> network_selected wireless.ConnectWireless(net_id)
> File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line
> 140, in __call__ **keywords)
> File "/usr/lib64/python2.7/site-packages/dbus/connection.py",
> line 630, in call_blocking message, timeout)
> dbus.exceptions.DBusException:
> org.freedesktop.DBus.Python.MemoryError: Traceback (most recent
> call last): File
> "/usr/lib64/python2.7/site-packages/dbus/service.py", line 702, in
> _message_cb retval = candidate_method(self, *args, **keywords)
> File "/usr/share/wicd/daemon/wicd-daemon.py", line 1168, in
> ConnectWireless self.SaveWirelessNetworkProfile(id)
> File "/usr/share/wicd/daemon/wicd-daemon.py", line 1278, in
> SaveWirelessNetworkProfile self.config.write()
> File "/usr/lib64/python2.7/site-packages/wicd/configmanager.py",
> line 218, in write p.set(sname, iname, value)
> File "/usr/lib64/python2.7/site-packages/wicd/configmanager.py",
> line 87, in set self.set_option(*args, **kargs)
> File "/usr/lib64/python2.7/site-packages/wicd/configmanager.py",
> line 77, in set_option value = to_unicode(value)
> File "/usr/lib64/python2.7/site-packages/wicd/misc.py", line 390,
> in to_unicode ret = x.decode(encoding).encode('utf-8')
> MemoryError
>
>
> $ wicd-curses
>
>
> 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 905, in
> call_update_ui self.update_ui(True)
> File "/usr/share/wicd/curses/wicd-curses.py", line 89, in wrapper
> return func(*args, **kargs)
> File "/usr/share/wicd/curses/wicd-curses.py", line 916, in
> update_ui self.handle_keys(input_data[1])
> File "/usr/share/wicd/curses/wicd-curses.py", line 837, in
> handle_keys self.connect("wireless",pos)
> File "/usr/share/wicd/curses/wicd-curses.py", line 930, in
> connect wireless.ConnectWireless(networkid)
> File "/usr/lib64/python2.7/site-packages/dbus/proxies.py", line
> 140, in __call__ **keywords)
> File "/usr/lib64/python2.7/site-packages/dbus/connection.py",
> line 630, in call_blocking message, timeout)
> dbus.exceptions.DBusException:
> org.freedesktop.DBus.Python.MemoryError: Traceback (most recent
> call last): File
> "/usr/lib64/python2.7/site-packages/dbus/service.py", line 702, in
> _message_cb retval = candidate_method(self, *args, **keywords)
> File "/usr/share/wicd/daemon/wicd-daemon.py", line 1168, in
> ConnectWireless self.SaveWirelessNetworkProfile(id)
> File "/usr/share/wicd/daemon/wicd-daemon.py", line 1278, in
> SaveWirelessNetworkProfile self.config.write()
> File "/usr/lib64/python2.7/site-packages/wicd/configmanager.py",
> line 218, in write p.set(sname, iname, value)
> File "/usr/lib64/python2.7/site-packages/wicd/configmanager.py",
> line 87, in set self.set_option(*args, **kargs)
> File "/usr/lib64/python2.7/site-packages/wicd/configmanager.py",
> line 77, in set_option value = to_unicode(value)
> File "/usr/lib64/python2.7/site-packages/wicd/misc.py", line 390,
> in to_unicode ret = x.decode(encoding).encode('utf-8')
> MemoryError
>
>
> $ emerge -vp wicd dbus dbus-python
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild R ] sys-apps/dbus-1.4.12 USE="X -debug -doc (-selinux)
> -static-libs -test" 0 kB [ebuild R ]
> dev-python/dbus-python-0.83.2 USE="-doc -examples -test" 0 kB
> [ebuild R ] net-misc/wicd-1.7.1_beta2-r4 USE="X gtk libnotify
> ncurses nls pm-utils (-ioctl)" 0 kB
>
> Total: 3 packages (3 reinstalls), Size of downloads: 0 kB
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-07-05 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 8:32 [gentoo-user] wicd fails to set wireless connection Peter Weilbacher
2011-07-05 9:00 ` Alan McKinnon [this message]
2011-07-05 13:22 ` Mick
2011-07-05 22:13 ` [gentoo-user] " Peter Weilbacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1733345.vhZsb7yjbB@nazgul \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=newsspam@weilbacher.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox