Arch Linux

2501

Member

Registered: 2008-05-17

Posts: 15

problem with last wicd upgrade

I can't connect wirelessly using wicd after upgrading it to the last version. Am I the only one????
-2501

hw-tph

Member

Registered: 2006-11-01

Posts: 149

Re: problem with last wicd upgrade

While I am pretty sure this is not the best solution, I managed to solve it with an ugly hack until I find a better solution.

I got this error:

2009/09/17 08:11:28 :: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.25" is not allowed to own the service "org.wicd.daemon" due to security policies in the configuration file

I am member of the network group so I added this to /etc/dbus-1/system.d/wicd.conf:

        <policy group="network">
            <allow own="org.wicd.daemon"/>
        </policy>

...just before the </busconfig> line.

If somebody has a better solution, please let us know.

Last edited by hw-tph (2009-09-17 10:30:23)

ralle

Member

From: Hannover

Registered: 2009-04-25

Posts: 20

Re: problem with last wicd upgrade

...originally I thought I got around this problem but today it appeared again. Same stuff as 2501 postet... From my understanding the problem is the following: If you install the wicd from pacman, configure it and start adding networks all works fine. If then you run an update, like we all did yesterday, the s..t begins. If you then try to add networks this phenomenon apears. The networks you added before the update all work fine. Just when you try to add new ones...

Don't quite know the solution to this...

Greets

jimbok

Member

Registered: 2009-09-17

Posts: 51

Re: problem with last wicd upgrade

After rebooting my wireless router, the new wicd update seems to work properly.

I had unhidden my SSID about 2 weeks ago (so I could use wicd easier).  Worked fine until the update last night.  After a reboot, the SSID showed up as hidden again..... Hmm.  I found a couple of wicd's conf files and the SSID was listed as hidden there.  I manually replaced <hidden> with my SSID but to no avail (didn't think it would work anyway).  So I powered down the laptop, and double checked my wireless router to make sure I'm broadcasting SSID and forced a reboot. Rebooted the laptop, and so far so good.

---

Registered Linux User #402088

thefatprecious

Member

From: Austin, TX

Registered: 2009-02-13

Posts: 98

Re: problem with last wicd upgrade

I had an issue as well after the update. The first thing I tried was to make a backup of the old one and delete the /etc/wicd/wireless-settings.conf  file. Restarted /etc/rc.d/wicd and let it create a new file. After that I setup my network profile again and haven't had an issue. You may want to give that a shot if you haven't tried that already...

---

ILoveCandy

arnfred

Member

Registered: 2009-03-27

Posts: 8

Re: problem with last wicd upgrade

thefatprecious,

I just wanted to say thanks. I've been trying to connect to the network for a couple of hours, and your solution worked perfectly. Virtual beer for you.

muramasa

Member

From: Vancouver, Canada

Registered: 2007-01-08

Posts: 16

Website

Re: problem with last wicd upgrade

That's odd. I haven't had any issues since I upgraded yesterday.

thefatprecious

Member

From: Austin, TX

Registered: 2009-02-13

Posts: 98

Re: problem with last wicd upgrade

thefatprecious,

I just wanted to say thanks. I've been trying to connect to the network for a couple of hours, and your solution worked perfectly. Virtual beer for you.

Cheers!

---

ILoveCandy

arnfred

Member

Registered: 2009-03-27

Posts: 8

Re: problem with last wicd upgrade

I was probably a little early out with my virtual beer (nawh, you can have it anyway ). For some reason, every time I reboot wicd can't connect to my home network. If I delete /etc/wicd/wireless-settings.conf  wicd will work untill next reboot.

does anybody know how I might fix this?

I'm using an intel 5000 wifi driver btw. If anybody else has the same problem and the same card there might be a connection.

Last edited by arnfred (2009-09-21 17:43:16)

R00KIE

Forum Fellow

From: Between a computer and a chair

Registered: 2008-09-14

Posts: 4,734

Re: problem with last wicd upgrade

Try using the ioctl backend, today I was testdriving the 2.6.31 and testing the newly added support for a usb wireless adapter of mine and it was behaving erratically with the external backend, using ioctl seems to be working just fine (don't forget to install the optdepends to fully take advantage of it).

---

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

ralle

Member

From: Hannover

Registered: 2009-04-25

Posts: 20

Re: problem with last wicd upgrade

Try using the ioctl backend, today I was testdriving the 2.6.31 and testing the newly added support for a usb wireless adapter of mine and it was behaving erratically with the external backend, using ioctl seems to be working just fine (don't forget to install the optdepends to fully take advantage of it).

...funny, I was just about to post that using the "experimental" ioctl backend seems to be involved in the trouble I had, as I read R00KIE's message. Deleting the wireless-settings.conf didn't work for me.
My situation in some quick words...
Had some "root password trouble" with Wicd 1.5 and ignored it for some time. Upgraded to 1.6 when it came out, trouble still there. Started to annoy me so I decided to completely get rid of Wicd and install it again. Turned out to work fine 'till I was back in my university trying to hook up to the last WLAN I was missing, the EDUROAM on campus. And there it happened again, enter root password blabla...
So yesterday I deleted Wicd AGAIN, reinstalled it ---> connection worked! Switched then to ioctl (yes, I got all optional dependencies installed) and there it was again asking for root password. Switched back to external backend and it worked again...

I mean it could be a combination of the EDUROAM setup with ioctl or a hidden network wich causes it. Those were the factors which turned out to cause some headache in the past, though I read that these bugs were squashed...

Maybe some of you can reproduce this behaviour. Maybe I'm able to narrow it down some more, so check back from time to time...

Greets ralle

ise

Developer

From: Karlsruhe / Germany

Registered: 2005-10-06

Posts: 404

Website

Re: problem with last wicd upgrade

Everytime I push a new version of wicd to the repos, some people have trouble with it. I know that this is annyoing sometimes for those who can't connect anymore to their WLAN (internet most of the time).

The thing about the dbus interface and wicd: a bug report and solution was posted here

My advice to all wicd users here, post things which are clearly bugs of wicd to their bugtracker on launchpad. I test each release and I hadn't any problems so far, but I only have my own WLAN and from time to time some other WLANs. Maybe I change the way I release wicd, maybe it should be in [testing] first, but then some people (especially YOU (wicd users)) must test it before I move it to [extra].

Daniel

---

23 page
My blog

ChemBro

Member

Registered: 2008-10-22

Posts: 703

Re: problem with last wicd upgrade

Everytime I push a new version of wicd to the repos, some people have trouble with it.

He, he. I have to reinstall wicd after every update. Dunno why. Maybe I look deeper in it the next time.

And I think, the problem only appear, when I'm not typing in my WPA2-passkey in wicd, so maybe the wicd-update doesn't accept the saved WPA2-passkey? Only a guess, though.

R00KIE

Forum Fellow

From: Between a computer and a chair

Registered: 2008-09-14

Posts: 4,734

Re: problem with last wicd upgrade

@ise
The thing is that wicd works just fine with both backends for me if I use the internal wireless card of my notebook.
Like I said, while testing (with the kernel still in testing) I found that the usb adapter wasn't playing well with wicd.

I'm not having the problem some people have of not being able to connect at all and there was nothing in the logs that could point to wicd having trouble doing something. At first I even thought it was some powersave feature that was causing trouble.

Here goes an excerpt of what is in /var/log/everything.log concerning the problem (maybe you can make some sense of it), with the external backend + usb adapter it goes on and on like this:

Sep 23 18:53:18 arch64 kernel: wlan0: authenticate with AP 02:24:01:55:41:e5
Sep 23 18:53:18 arch64 kernel: wlan0: authenticated
Sep 23 18:53:18 arch64 kernel: wlan0: associate with AP 02:24:01:55:41:e5
Sep 23 18:53:18 arch64 kernel: wlan0: RX AssocResp from 02:24:01:55:41:e5 (capab=0x431 status=0 aid=1)
Sep 23 18:53:18 arch64 kernel: wlan0: associated
Sep 23 18:53:18 arch64 dhcpcd: wlan0: broadcasting for a lease
Sep 23 18:53:18 arch64 dhcpcd: wlan0: offered 192.168.1.102 from 192.168.1.1
Sep 23 18:53:18 arch64 dhcpcd: wlan0: acknowledged 192.168.1.102 from 192.168.1.1
Sep 23 18:53:18 arch64 dhcpcd: wlan0: checking for 192.168.1.102
Sep 23 18:53:23 arch64 dhcpcd: wlan0: leased 192.168.1.102 for 235926997 seconds
Sep 23 18:53:25 arch64 dhcpcd: wlan0: releasing lease of 192.168.1.102
Sep 23 18:53:25 arch64 dhcpcd: wlan0: removing interface
Sep 23 18:53:26 arch64 kernel: wlan0: deauthenticating by local choice (reason=3)
Sep 23 18:53:26 arch64 kernel: wlan0: deauthenticating by local choice (reason=3)
Sep 23 18:53:27 arch64 kernel: wlan0: deauthenticating by local choice (reason=3)

And at the same time here's what is in the wicd log, nothing seems wrong here to me and no dbus related problems, just with this I wouldn't call it a wicd bug right away

2009/09/23 18:53:16 :: Autoconnecting...
2009/09/23 18:53:16 :: No wired connection present, attempting to autoconnect to wireless network
2009/09/23 18:53:17 :: trying to automatically connect to...RKSDlink
2009/09/23 18:53:17 :: Connecting to wireless network RKSDlink
2009/09/23 18:53:17 :: Putting interface down
2009/09/23 18:53:17 :: Releasing DHCP leases...
2009/09/23 18:53:17 :: Setting false IP...
2009/09/23 18:53:17 :: Stopping wpa_supplicant
2009/09/23 18:53:17 :: Flushing the routing table...
2009/09/23 18:53:17 :: Putting interface up...
2009/09/23 18:53:17 :: Generating psk...
2009/09/23 18:53:17 :: Attempting to authenticate...
2009/09/23 18:53:18 :: Running DHCP
2009/09/23 18:53:18 :: dhcpcd: version 5.1.0 starting
2009/09/23 18:53:18 :: 
2009/09/23 18:53:18 :: dhcpcd: wlan0: broadcasting for a lease
2009/09/23 18:53:18 :: 
2009/09/23 18:53:18 :: dhcpcd: wlan0: offered 192.168.1.102 from 192.168.1.1
2009/09/23 18:53:18 :: 
2009/09/23 18:53:18 :: dhcpcd: wlan0: acknowledged 192.168.1.102 from 192.168.1.1
2009/09/23 18:53:18 :: 
2009/09/23 18:53:18 :: dhcpcd: wlan0: checking for 192.168.1.102
2009/09/23 18:53:18 :: 
2009/09/23 18:53:23 :: dhcpcd: wlan0: leased 192.168.1.102 for 235926997 seconds
2009/09/23 18:53:23 :: 
2009/09/23 18:53:23 :: dhcpcd: forking to background
2009/09/23 18:53:23 :: 
2009/09/23 18:53:23 :: 
2009/09/23 18:53:23 :: DHCP connection successful
2009/09/23 18:53:23 :: Connecting thread exiting.
2009/09/23 18:53:25 :: Sending connection attempt result Success
2009/09/23 18:53:30 :: Connecting to wireless network RKSDlink
2009/09/23 18:53:30 :: Putting interface down
2009/09/23 18:53:30 :: Releasing DHCP leases...
2009/09/23 18:53:30 :: Setting false IP...
2009/09/23 18:53:30 :: Stopping wpa_supplicant
2009/09/23 18:53:30 :: Flushing the routing table...
2009/09/23 18:53:30 :: Putting interface up...
2009/09/23 18:53:30 :: Generating psk...
2009/09/23 18:53:30 :: Attempting to authenticate...
2009/09/23 18:53:31 :: Running DHCP
2009/09/23 18:53:31 :: dhcpcd: version 5.1.0 starting
2009/09/23 18:53:31 :: 
2009/09/23 18:53:31 :: dhcpcd: wlan0: broadcasting for a lease
2009/09/23 18:53:31 :: 
2009/09/23 18:53:31 :: dhcpcd: wlan0: offered 192.168.1.102 from 192.168.1.1
2009/09/23 18:53:31 :: 
2009/09/23 18:53:31 :: dhcpcd: wlan0: acknowledged 192.168.1.102 from 192.168.1.1
2009/09/23 18:53:31 :: 
2009/09/23 18:53:31 :: dhcpcd: wlan0: checking for 192.168.1.102
2009/09/23 18:53:31 :: 
2009/09/23 18:53:36 :: dhcpcd: wlan0: leased 192.168.1.102 for 235926997 seconds
2009/09/23 18:53:36 :: 
2009/09/23 18:53:36 :: dhcpcd: forking to background
2009/09/23 18:53:36 :: 
2009/09/23 18:53:36 :: 
2009/09/23 18:53:36 :: DHCP connection successful
2009/09/23 18:53:36 :: Connecting thread exiting.
2009/09/23 18:53:36 :: Sending connection attempt result Success

---

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

kgas

Member

From: Qatar

Registered: 2008-11-08

Posts: 718

Re: problem with last wicd upgrade

In one of the laptops wicd gave the problem. A solution is found in the forum and worked.

pacman -Rd wicd
rm -rf /etc/wicd /var/log/wicd /etc/dbus-1/system.d/wicd
pacman -S wicd