|
Bugzilla – Full Text Bug Listing |
| Summary: | gdbus aborting due to unauthorized socket in DBUS_SESSION_BUS_ADDRESS | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | Forgotten User cAXlJ_FoSf <forgotten_cAXlJ_FoSf> |
| Component: | GNOME | Assignee: | E-mail List <gnome-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | aj, arun, caf4926, cedric, fedev, forgotten_h13THG8RK1, jslaby, koenig, Martin.Seidler, terjejhanssen |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | maint:released:11.4:42528 | ||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | minimal example to trigger the bug | ||
|
Description
Forgotten User cAXlJ_FoSf
2010-11-24 14:39:12 UTC
*** Bug 648558 has been marked as a duplicate of this bug. *** *** Bug 672793 has been marked as a duplicate of this bug. *** Fresh install of 11.4, and I receive this error when trying to launch yast as root from a shell GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed: (connection->initialization_error == NULL) I can get you a supportconfig if desired. I also see the same issue and can get you whatever you need. Is the issue described in Thread: After zypper dup to 11.4 , most of the (graphical) YaST modules do not start via YaST http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/455279-after-zypper-dup-11-4-most-graphical-yast-modules-do-not-start-via-yast-post2306145.html#post2306145 a result of the issue of this bugreport? Should I open a new bugreport or do anything to give data to the bugreport 655751 here? If it would be only me and my former factory-tested installation I would just make a fresh reinstall. I the forums have tree other users written that they have the same issue. Regards Martin (pistazienfresser) Martin: please try if the other plugins (ncurses, qt) work for you. (In reply to comment #5) > http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/455279-after-zypper-dup-11-4-most-graphical-yast-modules-do-not-start-via-yast-post2306145.html#post2306145 > a result of the issue of this bugreport? That seems to be a separate bug in xdg-su (which like the other xdg-* stuff is total crap) triggering this one. It does some guesswork on what the current desktop is and falls back to calling an xterm with su, of course without properly requesting a login shell. (In reply to comment #3) > Fresh install of 11.4, and I receive this error when trying to launch yast as > root from a shell > > > GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed: > (connection->initialization_error == NULL) > > I can get you a supportconfig if desired. Anyone running into this is doing something wrong anyway, if you properly log in as root or request a login shell with su via "-" or "-l" you should not see this. No more data is needed, a backtrace is already on this and the upstream report. You are right. I wasn't using "-" before. I tested it and it worked. While I k now that is the standard way of doing things, previous versions of Suse didn't require it--made me lazy I guess. (In reply to comment #9) > You are right. I wasn't using "-" before. I tested it and it worked. While I > k now that is the standard way of doing things, previous versions of Suse > didn't require it--made me lazy I guess. You shouldn't do that, GNU coreutils su has in contrast to other implementations like Solaris su no security precautions at all and if you don't request a login shell, $PATH and any $LD_* variables are happily passed along. But this is getting offtopic, this bug is about glib not handling an invalid $DBUS_SESSION_BUS_ADDRESS gracefully. (In reply to comment #6) > Martin: please try if the other plugins (ncurses, qt) work for you. Thanks, Ricardo. Yes. they are working. Also are the YaST modules working properly if I start them individually and with gnomesu instead of Compare: Bug 681078 - xdg-utils: calling xdg-su inside "su -" fails formerly known as: Bug 681078 - yast2-control-center-gnome: After zypper dup to 11.4, most of the (graphical) YaST modules do not start via YaST on GNOME Regards Martin (pistazienfresser) (In reply to comment #10) > (In reply to comment #9) > > You are right. I wasn't using "-" before. I tested it and it worked. While I > > k now that is the standard way of doing things, previous versions of Suse > > didn't require it--made me lazy I guess. > > You shouldn't do that, GNU coreutils su has in contrast to other > implementations like Solaris su no security precautions at all and if you don't > request a login shell, $PATH and any $LD_* variables are happily passed along. > But this is getting offtopic, this bug is about glib not handling an invalid > $DBUS_SESSION_BUS_ADDRESS gracefully. Compare: Bug 682726 - Reference suggests only "su" instead of "su -"/su -l/su --login "make the shell a login shell" This should be added as a 11.4 patch update when fixed, because without this clicking any yast2 icon does nothing. That would be very problematic for new users that don't know the command line yet. Changing the priority. *** Bug 682563 has been marked as a duplicate of this bug. *** (In reply to comment #13) > This should be added as a 11.4 patch update when fixed, because without this > clicking any yast2 icon does nothing. That would be very problematic for new > users that don't know the command line yet. Changing the priority. This bug does not affect YaST when called via gnomesu or kdesu (which is what happens when you start it though the KDE/GNOME/LXDE/Xfce menu). It is only a problem with the YaST GTK frontend (and other GTK applications) when starting it from a root shell which has not had the environment properly cleared, i.e. mostly the usage of "su" instead of "su -/-l". BTW, this bug has been fixed upstream, see https://bugzilla.gnome.org/show_bug.cgi?id=635694 *** Bug 675053 has been marked as a duplicate of this bug. *** accepted as an update for 11.4 Update released for: glib2, glib2-branding-upstream, glib2-debugsource, glib2-devel, glib2-devel-debuginfo, glib2-devel-debuginfo-32bit, glib2-devel-debuginfo-x86, glib2-devel-static, glib2-lang, glib2-tools, glib2-tools-32bit, glib2-tools-debuginfo, glib2-tools-debuginfo-32bit, glib2-tools-debuginfo-x86, glib2-tools-x86, libgio-2_0-0, libgio-2_0-0-32bit, libgio-2_0-0-debuginfo, libgio-2_0-0-debuginfo-32bit, libgio-2_0-0-debuginfo-x86, libgio-2_0-0-x86, libgio-fam, libgio-fam-32bit, libgio-fam-debuginfo, libgio-fam-debuginfo-32bit, libgio-fam-debuginfo-x86, libgio-fam-x86, libglib-2_0-0, libglib-2_0-0-32bit, libglib-2_0-0-debuginfo, libglib-2_0-0-debuginfo-32bit, libglib-2_0-0-debuginfo-x86, libglib-2_0-0-x86, libgmodule-2_0-0, libgmodule-2_0-0-32bit, libgmodule-2_0-0-debuginfo, libgmodule-2_0-0-debuginfo-32bit, libgmodule-2_0-0-debuginfo-x86, libgmodule-2_0-0-x86, libgobject-2_0-0, libgobject-2_0-0-32bit, libgobject-2_0-0-debuginfo, libgobject-2_0-0-debuginfo-32bit, libgobject-2_0-0-debuginfo-x86, libgobject-2_0-0-x86, libgthread-2_0-0, libgthread-2_0-0-32bit, libgthread-2_0-0-debuginfo, libgthread-2_0-0-debuginfo-32bit, libgthread-2_0-0-debuginfo-x86, libgthread-2_0-0-x86 Products: openSUSE 11.4 (debug, i586, x86_64) |