LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Debian (https://www.linuxquestions.org/questions/debian-26/)
-   -   wicd xfce4 dbus notification-icon problem (https://www.linuxquestions.org/questions/debian-26/wicd-xfce4-dbus-notification-icon-problem-929099/)

radiodee1 02-13-2012 07:45 AM

wicd xfce4 dbus notification-icon problem
 
My problem, as you will see if you read below, is with the wicd notification icon.

I'm currently using testing on a laptop, updated every day, in the xfce4 d.e. environment. A couple of days ago, after an update, wicd started acting funny. There is a dialog box that pops up when the laptop is turned on that says that wicd is having some kind of problem. It suggests that I check the logs. In '/var/log/wicd/' there are some logs but they seem to report everything is working as normal. Running dmesg shows everything normal too, and lo and behold, if I try to use the internet it works.

Still if I click on the message bar icon I don't get the wicd gtk program. I can go to the 'Applications Menu' under 'Internet' and select wicd and get the gtk program, though. Under those circumstances it works as it should. As soon as I type 'wicd-gtk' from the command line the notification icon starts to work correctly (until I ctrl-C to stop it). What also works is if I type 'wicd' at a root terminal. If I do this as root, the notification icon works and there's nothing to ctrl-C as I suspect I am restarting the service.

Finally, something makes me think this all has to do with a change in the sysvinit package, but that's just a guess. I believe that the wicd package was updated today, and all my descriptions above were tested on the new version. Any help would be appreciated.

EDIT: this is the error message

Quote:

Could not connect to wicd's D-Bus interface. Check the wicd log for error messages.

rokytnji 02-13-2012 11:23 AM

Quote:

Could not connect to wicd's D-Bus interface. Check the wicd log for error messages.
http://wiki.debian.org/WiFi/HowToUse

Section Wicd

Quote:

If not already performed, add your regular user account to the netdev group and reload DBus:
Then I would try steps 3 through 5.

In Antix running Debian testing. During dist-upgrades. I had to add a user named demo. For some reason there was a wicd bug related to this though I have not searched for it in a while.

Quote:

Per a user suggestion on the AntiX forum I created a user called demo and
then was able to get the daemon to install. As this was a live-cd user it
gets removed after an install of distro AntiX and the previous install of
wicd had had this user. Thought purging the packages removed all references
to users but I guess its stored somewhere else.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634051

radiodee1 02-13-2012 12:20 PM

I don't have an entry in /etc/rcS.d for starting the wicd service. I should, right? I put the line below in the /etc/gdm3/PostLogin/ directory and everything worked.

Quote:

/etc/init.d/wicd restart
I'm guessing a link in the rcS.d directory would do it. It should be named 'S###wicd' where ### is a number, what number should it be? What is that program called that edits the rc#.d directories? update-rc.d ? can I use that here? What should that ### number be?

I've googled a little, and I have this link:

http://www.debuntu.org/how-to-manage...th-update-rc.d

I'm still not sure what number to give wicd.

radiodee1 02-13-2012 12:42 PM

So, what I started with was typing
Quote:

# update-rc.d wicd defaults
but an entry for wicd didn't show up in /etc/rcS.d/ so I typed the following:
Quote:

# cd /etc/rcS.d
# ln -s /etc/init.d/wicd S20wicd
# update-rc.d wicd defaults
This had the effect of placing an S24wicd entry in the rcS.d directory, along with S and K entries in other rc#.d directories. Then I rebooted. It's worked for one reboot. I need to try to reboot it again and test further.

EDIT: that seems to work.


All times are GMT -5. The time now is 05:54 AM.