[Bug 655751] New: gdbus aborting due to unauthorized socket in DBUS_SESSION_BUS_ADDRESS
https://bugzilla.novell.com/show_bug.cgi?id=655751 https://bugzilla.novell.com/show_bug.cgi?id=655751#c0 Summary: gdbus aborting due to unauthorized socket in DBUS_SESSION_BUS_ADDRESS Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: gber@opensuse.org QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=402008) --> (http://bugzilla.novell.com/attachment.cgi?id=402008) minimal example to trigger the bug User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 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 Backtrace: Starting program: /home/gber/gdbus-test [New Thread 0xb7b3bb70 (LWP 24927)] Program received signal SIGABRT, Aborted. 0xffffe430 in __kernel_vsyscall () #0 0xffffe430 in __kernel_vsyscall () #1 0xb7bf37cf in raise () from /lib/libc.so.6 #2 0xb7bf5110 in abort () from /lib/libc.so.6 #3 0xb7db8132 in g_assertion_message (domain=0xb7f7f1e1 "GLib-GIO", file=0xb7f96c19 "gdbusconnection.c", line=2152, func=0xb7f98c68 "initable_init", message=<value optimized out>) at gtestutils.c:1358 #4 0xb7db875f in g_assertion_message_expr (domain=0xb7f7f1e1 "GLib-GIO", file= 0xb7f96c19 "gdbusconnection.c", line=2152, func=0xb7f98c68 "initable_init", expr= 0xb7f98314 "connection->initialization_error == NULL") at gtestutils.c:1369 #5 0xb7f4f41b in initable_init (initable=0x8055000, cancellable=0x0, error=0xbffff278) at gdbusconnection.c:2152 #6 0xb7ef2822 in g_initable_init (initable=0x8055000, cancellable=0x0, error=0xbffff278) at ginitable.c:105 #7 0xb7f4fc65 in g_bus_get_sync (bus_type=G_BUS_TYPE_SESSION, cancellable=0x0, error=0xbffff278) at gdbusconnection.c:6121 #8 0x080486f8 in try_connect () at gdbus-test.c:14 #9 0x08048755 in main (argc=1, argv=0xbffff344) at gdbus-test.c:36 A debugging session is active. Inferior 1 [process 24924] will be killed. Quit anyway? (y or n) Reproducible: Always Steps to Reproduce: 1. point DBUS_SESSION_BUS_ADDRESS to the valid socket of another user 2. execute the attached example -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c1
Guido Berhörster
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c2
Vincent Untz
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c3
John Harmon
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c4
Jeremy Meldrum
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c5
Martin Seidler
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c6
--- Comment #6 from Ricardo Cruz
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c7
--- Comment #7 from Guido Berhörster
http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/... 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c8
--- Comment #8 from Guido Berhörster
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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c9
--- Comment #9 from John Harmon
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c10
--- Comment #10 from Guido Berhörster
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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
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
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c11
--- Comment #11 from Martin Seidler
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c12
--- Comment #12 from Martin Seidler
(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" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c13
Ryan Bach
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c14
Guido Berhörster
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c15
--- Comment #15 from Guido Berhörster
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". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c16
--- Comment #16 from Guido Berhörster
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c17
Duncan Mac-Vicar
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c18
Dirk Mueller
https://bugzilla.novell.com/show_bug.cgi?id=655751
https://bugzilla.novell.com/show_bug.cgi?id=655751#c19
Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com