[SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

PyroDevil · 2012-06-25 09:37:17

I am using Systemd as init-system and since an upgrade I have trouble loging on (with GDM, Console works but I have no network connection, so no fun).
Here are the messages I found in /var/log/everything.log:
http://pastebin.com/L2KY1VMy
From these messages I found that this problems may be related to the dbus 1.4 -> 1.6 upgrade.

Systemd could not start the systemd-logind.service, the NetworkManager.service and the bluetooth.service.
(The syslog.socket fails for some time already, but I have had no problems with this.)

Thanks for your help

---

A list of the Packages needed for downgrading so that it works again:

dbus-core-1.4.20-2-x86_64.pkg.tar.xz
dbus-1.4.20-1-x86_64.pkg.tar.xz
python-dbus-1.1.0-2-x86_64.pkg.tar.xz
python2-dbus-1.1.0-2-x86_64.pkg.tar.xz
lib32-dbus-core-1.4.20-1-x86_64.pkg.tar.xz

---

I added a bugreport to this case:
https://bugs.archlinux.org/task/30468

Last edited by PyroDevil (2012-07-01 07:10:17)

PyroDevil · 2012-06-25 12:09:51

I now tried the testing repository, but no success so far.

PyroDevil · 2012-06-25 12:32:58

With downgrading dbus and dbus-core to 1.4 everything works again.
Could this be a bug in dbus 1.6?
Anyone other than me has this problem?

~~Or maybe dbus-glib should be updated too?~~
dbus-glib is up to date, maybe incompatibilities?

Last edited by PyroDevil (2012-06-25 12:54:23)

aduser · 2012-06-25 14:41:16

same here

ahioros · 2012-06-27 00:16:03

I have the same problem here :-O

PyroDevil · 2012-06-27 05:28:26

No change with the newest update:
dbus-core 1.6.0-5
dbus-glib 0.100-1

Reverting only dbus and dbus-core to 1.4.20 works
Additional info, I am using the x86_64 architecture.

Last edited by PyroDevil (2012-06-27 05:30:37)

PyroDevil · 2012-06-27 16:02:41

I found that the new python2-dbus and python-dbus packages (1.1.1-1) are not kompatible with the old 1.4 dbus.
So they have to be downgraded to.

eyemonen · 2012-06-28 11:32:11

I did a fresh net install yesterday and could not start gnome shell. Also gdm was not starting. For me downgrading dbus-core to 1.6.0-4 helped.

Mr Green · 2012-06-28 17:13:54

Having problems with nm-applet after recent update..read bug report but downgrading is only a short term solution.

Does NetworkManager package need rebuilding?

Only thing I could find in logs was...

Jun 28 13:01:05 localhost NetworkManager[316]: <warn> Failed to open plugin directory /usr/lib/NetworkManager: Error opening directory '/usr/lib/NetworkManager': No such file or directory

Last edited by Mr Green (2012-06-28 17:28:27)

wonder · 2012-06-28 17:33:22

Mr Green wrote:

Having problems with nm-applet after recent update..read bug report but downgrading is only a short term solution.
Does NetworkManager package need rebuilding?
Only thing I could find in logs was...
Jun 28 13:01:05 localhost NetworkManager[316]: <warn> Failed to open plugin directory /usr/lib/NetworkManager: Error opening directory '/usr/lib/NetworkManager': No such file or directory

not related.

what version of dbus-core do you have?

Mr Green · 2012-06-28 17:57:47

 dbus-core 1.6.0-5

Last edited by Mr Green (2012-06-29 05:40:40)

Mr Green · 2012-06-28 18:29:23

Wondering if testing version will solve the problem....

Have tried testing and is does seem to solve my problem

Last edited by Mr Green (2012-06-29 05:42:34)

Mr Green · 2012-06-29 16:32:04

Trying dbus-core from testing

Can only access nm-applet if run via sudo now get

** (nm-applet:706): WARNING **: Failed to register as an agent: (32) No session found for uid 0
** Message: Starting applet secret agent because GNOME Shell disappeared

This under Openbox WM

As normal user

** (nm-applet:717): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Rejected send message, 2 matched rules; type="method_call", sender=":1.19" (uid=1000 pid=717 comm="nm-applet ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=314 comm="/usr/sbin/NetworkManager ")
** Message: applet now removed from the notification area

** (nm-applet:717): WARNING **: Failed to register as an agent: (32) No session found for uid 1000
** Message: applet now embedded in the notification area
** Message: applet now removed from the notification area
** Message: Starting applet secret agent because GNOME Shell disappeared

** (nm-applet:717): WARNING **: Failed to register as an agent: (32) No session found for uid 1000

wonder · 2012-06-29 16:33:03

can you paste ls /run/console ?

Mr Green · 2012-06-29 16:38:47

No output, so I am guessing its /var related?

wonder · 2012-06-29 16:41:21

then that's the problem. dbus should create a file having your username name that contains the session.

cat /run/console/ioni
/org/freedesktop/ConsoleKit/Session2

Mr Green · 2012-06-29 17:20:26

Live session was fine up until about a week ago, latest dbus stop nm-applet working. Been trying to figure out problem ever since.

My desktop and laptop are running fine without a problem.

Thinking I may have a package missing after recent systemd changes.

Back to the terminal

Thank you for your help

PyroDevil · 2012-07-01 07:09:35

Yury Afanasyev (on the bugtracker) found a solution that works for me.
It was related to the filesystem update. (I updated the filesystem package with the force option, but that may not be enougth on my system)
After executing `rm -rf /var/run /var/lock`, reinstalling the filesystem and dbus 1.6 package, gdm and nm are working flawless after a reboot.

So I mark this topic as solved.

Thanks for all you help!

hexchain · 2012-07-04 08:23:40

I think it's a dbus configuration related issue.

I just installed NetworkManager on my new laptop and nm-applet doesn't work.

Changing "deny" to "allow" on /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf solved this problem.

Mr Green · 2012-07-04 11:07:27

Can you explain a little more on what you changed?

I found linking /var/run to /run worked for me

quan2m · 2012-07-23 23:45:15

Not to be dense but did you mean "ln -s /var/run /run" or "ln -s /run /var/run".

I am suffering similar issues, but it seems that there is a file that nm-applet is looking for that is missing. /run/dbus/system_bus_socket (No such file or directory)

Also tail -f /var/log/messages.log. Also the /usr/lib/NetworkManager directory seems not to have made it through the /lib usr/lib merger. The error is: <warn> Failed to open plugin directory /usr/lib/NetworkManager: Error opening directory '/usr/lib/NetworkManager': No such file or directory

I get the machine online now using netcfg tools (wifi-menu) so I can paste more data if you need it.

quan2m · 2012-07-23 23:46:30

dbus is running at this point

Mocco · 2012-07-28 17:59:20

I think I have the same problem, I was experiencing problems with dbus and was not able to start gdm. After linking /run/dbus to /var/run/dbus gdm worked fine but I'm not able to run Networkmanager and upgrading filesystem package doesn't work, it says that's impossible to overwrite the directory with the file /var/run (???). Should I move all the files from /var/run to /run and then linking the two?

doctorzeus · 2012-11-02 10:15:12

I am having a similar problem, except I can login fine with GDM. The thing that isnt working is the KDE networkmanager client applet which appears to not have the permissions after a recent update to interface with the NetworkManager daemon.

I have a similar situation with mounting external devices in dolphin which is now not authorized to mount devices, wicd and mounting devices manually via the console works fine however this is obviously not suitable for everyday use..

Tried the various solutions however creating a symlink has no effect and starting KDE through .xinitrc means that the KDE NMApplet can interface with NetworkMangerD but cannot setup connections or influence the daemon..

Arch Linux

#1 2012-06-25 09:37:17

[SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#2 2012-06-25 12:09:51

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#3 2012-06-25 12:32:58

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#4 2012-06-25 14:41:16

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#5 2012-06-27 00:16:03

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#6 2012-06-27 05:28:26

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#7 2012-06-27 16:02:41

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#8 2012-06-28 11:32:11

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#9 2012-06-28 17:13:54

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#10 2012-06-28 17:33:22

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#11 2012-06-28 17:57:47

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#12 2012-06-28 18:29:23

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#13 2012-06-29 16:32:04

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#14 2012-06-29 16:33:03

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#15 2012-06-29 16:38:47

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#16 2012-06-29 16:41:21

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#17 2012-06-29 17:20:26

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#18 2012-07-01 07:09:35

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#19 2012-07-04 08:23:40

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#20 2012-07-04 11:07:27

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#21 2012-07-23 23:45:15

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#22 2012-07-23 23:46:30

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#23 2012-07-28 17:59:20

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

#24 2012-11-02 10:15:12

Re: [SOLVED] GDM, NM problems since upgrade (related to dbus 1.6)

Board footer