Arch Linux

Cew27

Member

Registered: 2008-06-16

Posts: 197

[solved] nm-applet causing hassle

when i run it i get
** (nm-applet:3820): WARNING **: <WARN>  nma_dbus_init(): org.freedesktop.DBus.Error.FileNotFound raised:
Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
any help

p.s sorry for all these posts but once i am done i will donte to make up for all my annoyances

Last edited by Cew27 (2009-01-07 22:12:57)

Cew27

Member

Registered: 2008-06-16

Posts: 197

Re: [solved] nm-applet causing hassle

also when i try shutdown it does nothing (using gnome shutdown) and wicd doesnt even start.
im assuming this is a dbus error not nm-applet

R00KIE

Forum Fellow

From: Between a computer and a chair

Registered: 2008-09-14

Posts: 4,734

Re: [solved] nm-applet causing hassle

Make sure dbus is started before you start wicd or nm-applet.
I start hal (which requires dbus) before I start wicd, never had any problems.

DAEMONS=(syslog-ng !network hal @oss @fam @wicd @crond @smartd @openntpd @cpufreq)

---

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Cew27

Member

Registered: 2008-06-16

Posts: 197

Re: [solved] nm-applet causing hassle

hall is going before nm-applet

Cew27

Member

Registered: 2008-06-16

Posts: 197

Re: [solved] nm-applet causing hassle

anyone else know what could be casuging it

Kirurgs

Member

Registered: 2008-10-20

Posts: 144

Re: [solved] nm-applet causing hassle

Have You added Yourself to approriate groups as installation guide suggests? Like network, dbus, hal... For shutdown You have to have to add yourself to power group... Please restart or at least log out and in afterwards.
Please check these and report back...

Cew27

Member

Registered: 2008-06-16

Posts: 197

Re: [solved] nm-applet causing hassle

didnt work, doesnt run as root either still get the error
i would pay for a fix for this, its so irritating

Cew27

Member

Registered: 2008-06-16

Posts: 197

Re: [solved] nm-applet causing hassle

solved
the problem was my NetworkManager.conf was blank for some strange reason meaning no hal or dus
pacman -Rns gnome-network-manager
then pacman -S gnome-network-manager