No wireless connection after pacman update

Question

I dont get any connection whatsoever after a pacman -Syu . Im using wicd and iwconfig shows the device.
Im only using wicd and the service should start and connect after booting but it dosnt. If I start the wicd-gtk, it dosnt show the connections. I tried to use wifi-menu but it throws a connection error (gives me the journal -xn)
Any reason for whats causing this? Ill try to copy every command, but its hard since im posting from another pc.
Thanks

Answer 1

jasonwryan wrote:What error messages are in the journal? In wicd's log? What packages were in the upgrade?
You need to try an narrow down the fault...
For the packages, I did a full system upgrade. I cant remember how many or what packages were actually upgraded cause they were.. many.
Im sorry admin! Let me try to copy as much as I can : the journal after using wifi-menu:
Something interesting is that I see for a second that my wifi is on ( im usng xmonad and dzen ), then it goes off.
-- Logs begin at Fri 2013-08-23 23:37:07 ART, end at Wed 2013-11-13 22:26:33 ART. --
Nov 13 16:29:35 linx systemd[339]: Stopped target Default.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Documentation: [url]http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286[/url]
-- Unit UNIT has finished shutting down.
Nov 13 16:29:35 linx systemd[339]: Starting Shutdown.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit UNIT has begun starting up.
Nov 13 16:29:35 linx systemd[339]: Reached target Shutdown.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit UNIT has finished starting up.
-- The start-up result is done.
Nov 13 16:29:35 linx systemd[339]: Starting Exit the Session...
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit UNIT has begun starting up.
-- Reboot --
Nov 13 22:26:32 linx systemd[350]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
Nov 13 22:26:32 linx systemd[350]: Mounted /sys/kernel/config.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit UNIT has finished starting up.
-- The start-up result is done.
Nov 13 22:26:32 linx systemd[350]: Stopped target Sound Card.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Documentation: [url]http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286[/url]
-- Unit UNIT has finished shutting down.
Nov 13 22:26:32 linx systemd[350]: Starting Default.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit UNIT has begun starting up.
Nov 13 22:26:32 linx systemd[350]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- Unit UNIT has finished starting up.
-- The start-up result is done.
Nov 13 22:26:32 linx systemd[350]: Startup finished in 77ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- Kernel start-up required KERNEL_USEC microseconds.
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- Userspace start-up required 77128 microseconds.
Last edited by jasonwryan (2013-11-14 01:55:31)