Whenever I try to update or even install a package through the terminal, I keep getting this message: (I will download the java-plugin to show as example)
linux-0go3:/home/jonathan # zypper install java-plugin
Retrieving repository 'PK_TMP_DIR' metadata [done]
**
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...
'java-plugin' not found in package names. Trying capabilities.
Resolving package dependencies...
Blah blah blah...the rest of the install process :3
alot of folks are having this issue including me, it’s already a filed bug, i’m pretty sure it’s isolated to the gnome enviroment, i switched from KDE becuase of ubsurd/unecessary CPU consumption, only to be greated with more bugs including this and a ‘confused kernel’, are you using a strange power scheme?’ terminal message, which is just highly aggrovating. all of these problems are out of the box never have occured before on any distro i’ve used at least. Below is a google of the (GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed: (connection->initialization_error == NULL)) issue, some people only recive it from a certian task, like running yast from a terminal (if that’s your case they have a work around) but if your like me i get it when i try to do any type of zypper command and they dont have a ‘work around’ or ‘fix’ for it.
Below that is the bug reported on novell, it is also reported at (https://bugzilla.gnome.org/show_bug.cgi?id=635694)
"When DBUS_SESSION_BUS_ADDRESS is set to the valid socket of another user glib
will abort due to an assertion failure when more than one connection attempt
via gdbus is made. In practice this often happens when users try to execute GTK
applications which use GConf through su/sudo without properly clearing the
environment (e.g. starting YaST with xdg-su xterm+su).
A minimal example which triggers the problem is attached.
This bug affects glib2 verion 2.27.x in Factory, openSUSE 11.3 is not affected
since it uses an older glib version without GDBus. The bug has been reported
upstream: https://bugzilla.gnome.org/show_bug.cgi?id=635694" ~https://bugzilla.novell.com/show_bug.cgi?id=655751
When DBUS_SESSION_BUS_ADDRESS is set to the valid socket of another user glib
will abort due to an assertion failure when more than one connection attempt
via gdbus is made. In practice this often happens when users try to execute GTK
applications which use GConf through su/sudo without properly clearing the
environment. glib should handle invalid environment variables gracefully rather
than crashing.
A minimal example which triggers the problem is attached (note that in order to
reproduce DBUS_SESSION_BUS_ADDRESS must be set to a valid socket of another
user, bogus values will be handled correctly by returning an error) ~(https://bugzilla.gnome.org/show_bug.cgi?id=635694)
this probably wont help but hopefully it will shine some light on the subject
