Bugzilla – Bug 671355
OpenSuse 11.4 RC1 - zypper dup - GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed:
Last modified: 2011-03-07 12:14:20 UTC
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b10) Gecko/20110121 Firefox/4.0b10 Fresh installation of OpenSuse 11.4RC1 in VirtualBox 4.02 on Inter Quad Core PC. No problems or any errors durning installation - missing "Prompt for PC name" causing a "funny name" to be assigned - will log seprately. Doing a "zupper dup" is showing the follwing errors. inux-5thc:/home/netadm # zypper dup Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. ** GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed: (connection->initialization_error == NULL) ** GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed: (connection->initialization_error == NULL) ** GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed: (connection->initialization_error == NULL) Loading repository data... Reading installed packages... Computing distribution upgrade... Nothing to do. linux-5thc:/home/netadm # Reproducible: Always Steps to Reproduce: 1. As per above with fresh installation 2. 3.
Looks like this only happens when running as "gnome gui-user", terminal, su and then "zypper dup" - updates does work Looks like I have to be "root in GUI" - then no error.
Same problem on my machine - but only under GNOME.
Looks like bug 655751. Note that "su -" is much better than "su"... I'm not sure what tool zypper is calling that would cause this, though.
It calls dbus-send --system --dest=org.freedesktop.DBus --type=method_call \ --print-reply --reply-timeout=200 \ / org.freedesktop.DBus.NameHasOwner string:org.freedesktop.PackageKit
This is not what is creating those warnings, though (just checked).
Thanks, yes "su -" does work :-) As previous shared, testing is done on GNOME
. *** This bug has been marked as a duplicate of bug 672793 ***