Wicd unable to connect to DBus for non-admin user

Bug #479922 reported by Anders on 2009-11-10
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
wicd
Undecided
Unassigned
wicd (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: wicd

I'm setting up a "granny phone" laptop where as little user action as possible is desired (hence my choice of xicd over NetworkManager, which requires the Gnome keyring unlocked every time). However, this morning, the default user was asked for a password (in a non-localized textbox: question was in English on an all-French laptop), and after entering, got a bunch of error messages.

/var/log/wicd/wicd.log shows:

2009/11/10 11:56:26 :: ---------------------------
2009/11/10 11:56:26 :: wicd initializing...
2009/11/10 11:56:26 :: ---------------------------
2009/11/10 11:56:26 :: wicd is version 1.6.1 426
2009/11/10 11:56:28 :: Traceback (most recent call last):
2009/11/10 11:56:28 :: File "/usr/share/wicd/wicd-daemon.py", line 1747, in <module>
2009/11/10 11:56:28 :: main(sys.argv)
2009/11/10 11:56:28 :: File "/usr/share/wicd/wicd-daemon.py", line 1709, in main
2009/11/10 11:56:28 :: bus = dbus.SystemBus()
2009/11/10 11:56:28 :: File "/usr/lib/pymodules/python2.6/dbus/_dbus.py", line 202, in __new__
2009/11/10 11:56:28 :: private=private)
2009/11/10 11:56:28 :: File "/usr/lib/pymodules/python2.6/dbus/_dbus.py", line 108, in __new__
2009/11/10 11:56:28 :: bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
2009/11/10 11:56:28 :: File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 125, in __new__
2009/11/10 11:56:28 :: bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
2009/11/10 11:56:28 :: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

ProblemType: Bug
Architecture: i386
Date: Tue Nov 10 12:00:05 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
Package: wicd 1.6.1-3ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: wicd
Uname: Linux 2.6.31-14-generic i686

Anders (andersja+launchpad-net) wrote :
tags: added: regression-update wicd
Anders (andersja+launchpad-net) wrote :

To "override", the workaround was to log in as an "admin user" and give password to wicd when asked for it.

Anders (andersja+launchpad-net) wrote :

Problem has not reoccurred on subsequent reboots, so considering it a low priority / one off issue. The laptop in question boots straight into a user = possible race condition (wicd trying to access a part of the system not yet available so soon after boot?)

Conner Lee (connerleecml) wrote :

i cant explain really but i messed around with sysv-rc-conf. before wireless would on light up on my gateway after login causing the dbus error. now everyone works fine. go into sysv-rc-conf and change the wicd settings. but find someone who knows more about sysv-rc-conf

to install sudo apt-get install sysv-rc-conf

then run sudo sysv-rc-conf

Changed in wicd (Ubuntu):
status: New → Confirmed
David Paleino (dpaleino) on 2012-02-05
Changed in wicd:
status: New → Invalid
Rob (ubuntu-clearblueskies) wrote :

I found a kludgy workaround, which I'll attach here as a patch. I just commented out the lines where wicd-daemon.py tries to backup resolv.conf. This fixes the dbus errors and lets wicd startup normally.

The attachment "wicd-daemon.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers