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#35732 - [wicd] systemd service no longer starts on boot, and wicd gtk client asks for a root password

Attached to Project: Arch Linux
Opened by Damjan Dimitrioski (gnu_D) - Sunday, 09 June 2013, 06:41 GMT
Last edited by Isenmann Daniel (ise) - Thursday, 08 January 2015, 10:58 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Isenmann Daniel (ise)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
This happen after I made the migration from bin/sbin to /usr/bin/.

When I boot my system and KDE start completely, the wicd gtk client start and open the gtsudo command to authorize the starting of the wicd service I guess, but that fails.

I tried manually to restart the wicd service via:
sudo service restart wicd
what happens is it sits there for several seconds and then the wicd gtk client sets to green, but the systemd command isn't complete, I mean I don't see a new line in bash.
After a while somehow the wicd crashes.
Looking at the logs I found this:

-- Logs begin at Tue 2013-02-12 13:54:20 CET, end at Sat 2013-06-08 23:31:35 CEST. --
Jun 08 23:31:15 freedom sudo[3588]: pam_unix(sudo:session): session closed for user root
Jun 08 23:31:19 freedom sudo[3591]: gnu_d : TTY=pts/1 ; PWD=/home/gnu_d ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Jun 08 23:31:19 freedom sudo[3591]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 08 23:31:19 freedom sudo[3591]: pam_unix(sudo:session): session closed for user root
Jun 08 23:31:20 freedom sudo[3597]: gnu_d : TTY=pts/1 ; PWD=/home/gnu_d ; USER=root ; COMMAND=/usr/bin/journalctl -xn
Jun 08 23:31:20 freedom sudo[3597]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 08 23:31:20 freedom sudo[3597]: pam_unix(sudo:session): session closed for user root
Jun 08 23:31:35 freedom systemd[1]: wicd.service operation timed out. Terminating.
Jun 08 23:31:35 freedom systemd[1]: Failed to start Wicd a wireless and wired network manager for Linux.
-- Subject: Unit wicd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit wicd.service has failed.
--
-- The result is failed.
Jun 08 23:31:35 freedom systemd[1]: Unit wicd.service entered failed state.

I believe this is related to the systemd-tmpfiles-setup.service, I looked at it's log and I sow:
Jun 09 08:26:21 freedom sudo[24585]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 09 08:26:21 freedom sudo[24585]: pam_unix(sudo:session): session closed for user root

Can this affect the wicd.service session too ?
Additional info:
* package version(s)
wicd 1.7.2.4-7
wicd-gtk 1.7.2.4-7
systemd 204-3

Steps to reproduce:
1) Have wicd and wicd-gtk installed. Update the system https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/
2) Reboot
3) When KDE starts the wicd gtk client will asks for password, enter the password, error raises.
4) Try to restart the wicd service via systemd, result:
the systemd command sits there and doesn't exit, but we can see a connection and after a minute I guess:
*) the connection is dropped.
This task depends upon

Closed by  Isenmann Daniel (ise)
Thursday, 08 January 2015, 10:58 GMT
Reason for closing:  Works for me
Additional comments about closing:  Can't reproduced it and this bug is a way too old now.
Comment by Isenmann Daniel (ise) - Monday, 10 June 2013, 16:08 GMT
Can't reproduced it here. wicd and wicd-gtk is running fine here under GNOME. Can't test it with KDE, can you test it with GNOME and tell me if the error still exists?
Comment by Damjan Dimitrioski (gnu_D) - Tuesday, 11 June 2013, 05:00 GMT
Not at the moment, I haven't got any disk space left for Gnome.

Loading...