You are not logged in.

#1 2009-10-03 09:35:05

moljac024
Member
From: Serbia
Registered: 2008-01-29
Posts: 2,676

wicd and networkmanager stopped working

I know the subject doesn't say much, but I can't explain it. Wicd just decided to stop working this morning. It can't connect to the daemon, this is the output:

~ $  wicd-client 
Has notifications support True
Loading...
Connecting to daemon...
Can't connect to the daemon, trying to start it automatically...

(gksudo:3915): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:3915): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:3915): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:3915): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
Can't connect to the daemon, trying to start it automatically...

(gksudo:3919): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:3919): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:3919): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:3919): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
/usr/lib/python2.6/site-packages/wicd/gui.py:151: GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size != GTK_ICON_SIZE_INVALID' failed
  self.wTree = gtk.glade.XML(gladefile)
Traceback (most recent call last):
  File "/usr/lib/wicd/wicd-client.py", line 827, in <module>
    main(sys.argv)
  File "/usr/lib/wicd/wicd-client.py", line 88, in wrapper
    return func(*args, **kwargs)
  File "/usr/lib/wicd/wicd-client.py", line 793, in main
    the_gui = gui.appGui(standalone=True)
  File "/usr/lib/python2.6/site-packages/wicd/gui.py", line 154, in __init__
    size = daemon.ReadWindowSize("main")
AttributeError: 'NoneType' object has no attribute 'ReadWindowSize'

I then tried starting the networkmanager daemon and the applet, check it out:

~ $  nm-applet 

** (nm-applet:4280): WARNING **: <WARN>  applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service.
  Message: 'Connection ":1.31" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file'

So, this looks like a dbus issue, but I always start a dbus session with my window manager with "dbus-launch --sh-syntax --exit-with-session". The system side daemon of Dbus should be started with hal.
NOTE: I see that it mentions some configuration file but I wouldn't know what file it is, so I couldn't have changed it

I looked in the pacman.log to see if it was a recent update and I can't see anything (yes, notice that I'm a -Syu junkie):

[2009-10-01 10:16] synchronizing package lists
[2009-10-01 10:16] starting full system upgrade
[2009-10-01 10:17] upgraded device-mapper (1.02.33-1 -> 2.02.53-1)
[2009-10-01 10:17] warning: /etc/conf.d/gpm installed as /etc/conf.d/gpm.pacnew
[2009-10-01 10:17] upgraded gpm (1.20.6-1 -> 1.20.6-3)
[2009-10-01 10:17] upgraded lvm2 (2.02.48-1 -> 2.02.53-1)
[2009-10-01 10:23] synchronizing package lists
[2009-10-01 10:23] starting full system upgrade
[2009-10-01 10:45] installed hibernate-script (1.99-1)
[2009-10-01 15:24] ==> If suspend to ram doesn't work, edit the whitelist.c.diff
[2009-10-01 15:24] ==> file to add your machine to the s2ram whitelist with the 
[2009-10-01 15:24] ==> appropriate methods, then uncomment
[2009-10-01 15:24] ==> the line in the PKGBUILD where the patch is applied, eventually
[2009-10-01 15:24] ==> add the md5sum of the resulting patch and finally rebuild the package.  
[2009-10-01 15:24] ==> Use 's2ram --identify' to identify your machine.
[2009-10-01 15:24] ==> Be sure to let the suspend-devel list know!
[2009-10-01 15:24] 
[2009-10-01 15:24] ==> The new Software Suspend does not use kernel parameters
[2009-10-01 15:24] ==> to determine the suspend partition, instead it consults the
[2009-10-01 15:24] ==> /etc/suspend.conf file when booting.
[2009-10-01 15:24] ==> You MUST edit this file before you update your initrd.
[2009-10-01 15:24] 
[2009-10-01 15:24] ==> You will need to update your mkinitcpio.conf file to
[2009-10-01 15:24] ==> include the hook uresume.  Replace your 'resume' hook
[2009-10-01 15:24] ==> with 'uresume'.  If you do not have a resume hook the
[2009-10-01 15:24] ==> uresume hook must go before filesystems but after ide,
[2009-10-01 15:24] ==> sata, and/or scsi.
[2009-10-01 15:24] ==> Do not get this wrong.  Then rebuild the ramdisk with
[2009-10-01 15:24] ==> 'mkinitcpio -p kernel26' (or what else needed for the kernel you use)
[2009-10-01 15:24] installed uswsusp (0.8-5)
[2009-10-02 00:36] synchronizing package lists
[2009-10-02 00:37] starting full system upgrade
[2009-10-02 01:31] synchronizing package lists
[2009-10-02 01:31] starting full system upgrade
[2009-10-02 01:32] >>> texlive: updating the filename database...
[2009-10-02 01:32] removed texlive-humanities (2009.15113-1)
[2009-10-02 01:32] >>> texlive: updating the filename database...
[2009-10-02 01:32] >>> texlive: updating the fontmap files with updmap...
[2009-10-02 01:32]  done.
[2009-10-02 01:32] removed texlive-latexextra (2009.15178-1)
[2009-10-02 01:32] >>> texlive: updating the filename database...
[2009-10-02 01:32] removed texlive-bibtexextra (2009.15177-1)
[2009-10-02 01:32] synchronizing package lists
[2009-10-02 01:32] starting full system upgrade
[2009-10-02 01:32]   -->
[2009-10-02 01:32]   -->  Please remember to add 'fuse' to your MODULES array in /etc/rc.conf
[2009-10-02 01:32]   -->
[2009-10-02 01:32] upgraded acetoneiso2 (2.1-1 -> 2.1.1-1)
[2009-10-02 01:32] upgraded texlive-bin (2009.2-2 -> 2009.4-1)
[2009-10-02 01:33] >>> texlive: updating the filename database...
[2009-10-02 01:33] >>> texlive: updating the fontmap files with updmap...
[2009-10-02 01:33]  done.
[2009-10-02 01:34] recreating all formats... done.
[2009-10-02 01:34]  (logs are under /usr/share/texmf-var/web2c/<engine>/<formatname>.log)
[2009-10-02 01:34] upgraded texlive-core (2009.15216-1 -> 2009.15537-1)
[2009-10-02 01:34] >>> texlive: updating the filename database...
[2009-10-02 01:34] upgraded texlive-latex3 (2009.15164-1 -> 2009.15493-1)
[2009-10-02 01:34] >>> texlive: updating the filename database...
[2009-10-02 01:34] >>> texlive: updating the fontmap files with updmap...
[2009-10-02 01:34]  done.
[2009-10-02 01:34] upgraded texlive-pictures (2009.15144-1 -> 2009.15544-1)
[2009-10-02 01:34] upgraded thunderbird (2.0.0.22-1 -> 2.0.0.23-1)
[2009-10-02 01:55] synchronizing package lists
[2009-10-02 01:56] starting full system upgrade
[2009-10-02 01:57] >>> texlive: updating the filename database...
[2009-10-02 01:57] installed texlive-bibtexextra (2009.15542-1)
[2009-10-02 01:57] >>> texlive: updating the filename database...
[2009-10-02 01:57] >>> texlive: updating the fontmap files with updmap...
[2009-10-02 01:57]  done.
[2009-10-02 01:57] installed texlive-latexextra (2009.15540-1)
[2009-10-02 01:58] >>> texlive: updating the filename database...
[2009-10-02 01:58] >>> texlive: updating the fontmap files with updmap...
[2009-10-02 01:58]  done.
[2009-10-02 01:59] recreating all formats... done.
[2009-10-02 01:59]  (logs are under /usr/share/texmf-var/web2c/<engine>/<formatname>.log)
[2009-10-02 01:59] upgraded texlive-core (2009.15537-1 -> 2009.15537-1)
[2009-10-02 02:16] >>> texlive: updating the filename database...
[2009-10-02 02:16] >>> texlive: updating the fontmap files with updmap...
[2009-10-02 02:16]  done.
[2009-10-02 02:17] recreating all formats... done.
[2009-10-02 02:17]  (logs are under /usr/share/texmf-var/web2c/<engine>/<formatname>.log)
[2009-10-02 02:17] upgraded texlive-core (2009.15537-1 -> 2009.15537-1)
[2009-10-02 02:24] synchronizing package lists
[2009-10-02 02:24] starting full system upgrade
[2009-10-02 09:49] synchronizing package lists
[2009-10-02 09:49] starting full system upgrade
[2009-10-02 10:01] upgraded opera-snapshot (4609-1 -> 4644-1)
[2009-10-02 10:01] >>> texlive: updating the filename database...
[2009-10-02 10:02] >>> texlive: updating the fontmap files with updmap...
[2009-10-02 10:02]  done.
[2009-10-02 10:03] recreating all formats... done.
[2009-10-02 10:03]  (logs are under /usr/share/texmf-var/web2c/<engine>/<formatname>.log)
[2009-10-02 10:03] upgraded texlive-core (2009.15537-1 -> 2009.15574-1)
[2009-10-02 10:03] >>> texlive: updating the filename database...
[2009-10-02 10:03] >>> texlive: updating the fontmap files with updmap...
[2009-10-02 10:03]  done.
[2009-10-02 10:03] upgraded texlive-latexextra (2009.15540-1 -> 2009.15565-1)
[2009-10-02 10:07] synchronizing package lists
[2009-10-02 10:07] starting full system upgrade
[2009-10-02 10:09] synchronizing package lists
[2009-10-02 10:09] starting full system upgrade
[2009-10-02 13:43] synchronizing package lists
[2009-10-02 13:43] starting full system upgrade
[2009-10-02 13:44] upgraded griffith (0.9.10-1 -> 0.10-1)
[2009-10-02 13:44] upgraded gsl (1.12-2 -> 1.13-1)
[2009-10-02 13:44] upgraded pstoedit (3.45-3 -> 3.50-1)
[2009-10-02 15:28] synchronizing package lists
[2009-10-02 15:28] starting full system upgrade
[2009-10-02 18:37] installed meld (1.3.1-1)
[2009-10-03 11:00] synchronizing package lists
[2009-10-03 11:01] starting full system upgrade
[2009-10-03 11:06] upgraded apr (1.3.8-2 -> 1.3.9-1)
[2009-10-03 11:06] upgraded libical (0.43-1 -> 0.44-1)
[2009-10-03 11:06] upgraded mpd (0.15.2-1 -> 0.15.3-1)
[2009-10-03 11:06] upgraded qt (4.5.2-7 -> 4.5.3-1)
[2009-10-03 11:06] upgraded sshfs (2.2-1 -> 2.2-2)

Is this happening to just me ? If so, Allan, how did you manage to break just my pc ? tongue

EDIT: Ok, that is interesting: even though I had "ck-launch-session" in my .xinitrc, when I ran it manually nm-applet started working...but wicd still won't play ball

Last edited by moljac024 (2009-10-03 10:08:24)


The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...

Offline

#2 2009-10-03 10:25:38

moljac024
Member
From: Serbia
Registered: 2008-01-29
Posts: 2,676

Re: wicd and networkmanager stopped working

Removing wicd, purging all it's configuration files and installing it again "fixed" it, although I wouldn't call it that way....must have been bitten by a bug


The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...

Offline

#3 2009-10-12 13:46:45

pendor
Member
From: Tucumán - Argentina
Registered: 2008-09-24
Posts: 130

Re: wicd and networkmanager stopped working

Same weird wicd problem here. Your solution did not work for me.
Too bad, wicd was always (before this event) rock solid, and the best in its field.
Wifi-radar, wlassistant and the rest just don't cut.
The problem arised, it seems, from a yaourt -Syu five days ago, IIRC. Maybe "fakeroot" related? I'm clueless.

Offline

#4 2009-10-12 13:54:31

ise
Developer
From: Karlsruhe / Germany
Registered: 2005-10-06
Posts: 404
Website

Re: wicd and networkmanager stopped working

pendor wrote:

Maybe "fakeroot" related? I'm clueless.

Why should it be fakeroot related? The last update I pushed to the repo was on September, 20th. Let me check wicd this evening on my laptop after work, maybe I can find something. Haven't turned on my laptop since last wicd update and it worked there.

Offline

#5 2009-10-12 20:07:20

pendor
Member
From: Tucumán - Argentina
Registered: 2008-09-24
Posts: 130

Re: wicd and networkmanager stopped working

The "fakeroot" comment was a very loonnggg shot. Because that's the last package (IIRC) updated BEFORE wicd stopped working... But, as I said, I can't trust my memory here. I think I noticed this problem (I'm on ethernet right now) one week ago, give or take 2 days...

Offline

#6 2009-10-12 20:09:47

pendor
Member
From: Tucumán - Argentina
Registered: 2008-09-24
Posts: 130

Re: wicd and networkmanager stopped working

Just after posting I finally managed to remember. Last time I used wireless without problem (on a public access point I use when not at home) was last Friday (october 9th). Hope this helps.

Offline

#7 2009-10-13 21:14:48

soupcan
Member
From: ?
Registered: 2008-10-25
Posts: 268

Re: wicd and networkmanager stopped working

Is it possible that the networkmanager errors have something to do with PolicyKit/ConsoleKit? I get a similar "org.freedesktop.foo" error when I try to eject a CD.

Offline

#8 2009-10-26 13:31:25

pendor
Member
From: Tucumán - Argentina
Registered: 2008-09-24
Posts: 130

Re: wicd and networkmanager stopped working

For me it´s finalley solved. Silly me, I´ve forgotten erasing /etc/wicd. The wicd log clearly stated parse problem. If I had read that, it would have been another different story.
So, summarizing, pacman -R wicd, erase all configuration files (esentially /etc/wicd), pacman -S wicd, nd there we go again!
Moral of story: obey wicd and read the log!!!!

Offline

Board footer

Powered by FluxBB