Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#19443 - [wicd] wicd-client silently fails

Attached to Project: Arch Linux
Opened by Jesse (gnos) - Thursday, 13 May 2010, 04:29 GMT
Last edited by Isenmann Daniel (ise) - Tuesday, 15 June 2010, 15:42 GMT
Task Type Bug Report
Category Packages: Extra
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 0
Private No

Details

Description:
Right after installing Arch linux from a non-network install cd, I installed wicd (from the network, and after updating the package database first). After fixing a bug where a broken (empty) wicd config file was preventing dbus from running, and making sure that that config file now contained all the proper stuff (I just took the wicd.conf from wicd's bz2 and placed it in /etc/dbus-l/system.d), I made sure dbus and wicd were running and then tried wicd-client -n from a terminal in xorg. Wicd-client failed silently without any error message. This leads me to believe there is something wrong with the wicd package, likely a missing dependency. See https://bugs.launchpad.net/wicd/+bug/579740

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


Steps to reproduce:
This task depends upon

Closed by  Isenmann Daniel (ise)
Tuesday, 15 June 2010, 15:42 GMT
Reason for closing:  Fixed
Additional comments about closing:  This shouldn't happen anymore with the new package in [extra]. wicd runs fine on my computers.
Comment by Arin Lares (arinlares) - Monday, 31 May 2010, 07:16 GMT
Bug also appears in 1.7.0-2, I downgraded to try to fix it.

I noticed that when I scan for wireless networks with wicd-client, my Conky RAM readout skyrockets, and then starts swapping every bit as fast as RAM. This doesn't happen in 1.7.0-2 or 1.7.0-3 when scanning/connecting using wicd-curses, however.
Comment by Isenmann Daniel (ise) - Sunday, 06 June 2010, 15:19 GMT
Sorry for the long delay. I will have enough time next week and will have a look into it.
Comment by Isenmann Daniel (ise) - Tuesday, 15 June 2010, 15:21 GMT
Have you installed "consolekit"? Another user mentioned, that wicd doesn't run without consolekit.

Loading...