| Summary: | dbus access from root user after remote login fails | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Frank Griffin <ftg> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11, pernel |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Frank Griffin
2017-10-28 17:26:24 CEST
It's too late for me to understand this bug. Is it a duplicate of bug 21920 ? If so, that one can be set to Cauldron and "MGA6TOO" on the whiteboard, and this one closed. CC:
(none) =>
marja11 bug#21920 is similar, but that OP doesn't report the error messages I do (connection refused, unauthorized). He just says nothing happens. (In reply to Frank Griffin from comment #2) > bug#21920 is similar, but that OP doesn't report the error messages I do > (connection refused, unauthorized). He just says nothing happens. Ok. I'll assign this report to our openssh maintainer, maybe he can shed some light :-) Assignee:
bugsquad =>
guillomovitch The dbus connection error suggest either than dbus is not running, or that it is running, but some kind of access control prevents you to access this. A local session initiated through a desktop manager is likely to have far more process running in the background than a remote one, which may explain the difference. Anyway, such kind of issue would have a better eye coverage on the cauldron mailing list. Tested on new Mageia 6 installation. The original bug 13834 is still valid. In comment 1 in that bug report a solution was suggested that works also for Mageia 6 CC:
(none) =>
pernel The original problem is still happening in current cauldron.
Guillaume Rousse
2019-02-19 19:03:36 CET
Summary:
Running root commands from terminal window in ssh fails =>
dbus access from root user after remote login fails The problems comes from dbus service initialisation, not from ssh. Source RPM:
openssh =>
(none)
Guillaume Rousse
2019-02-20 22:28:17 CET
Assignee:
guillomovitch =>
bugsquad Ping ? Still happening in current cauldron. Current stdout/stderr is: [root@ftgme2 ~]# mcc Too late to run INIT block at /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm line 257. (mcc:16210): dbind-WARNING **: 12:27:30.117: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-E0JEi0nQgR: Connection refused Ignore the following Glib::Object::Introspection & Gtk3 warnings (drakconf:16214): dbind-WARNING **: 12:27:30.676: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-E0JEi0nQgR: Connection refused Subroutine Gtk3::main redefined at /usr/share/perl5/vendor_perl/Gtk3.pm line 539. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. GLib-GObject-CRITICAL **: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed at /usr/lib64/perl5/DynaLoader.pm line 210. "cannot run /usr/sbin/isodumper" since it is not installed [Writing ISO] at /usr/libexec/drakconf line 833. GLib-LOG **: posix_spawn avoided (fd close requested) at /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm line 67. GLib-LOG **: posix_spawn avoided (child_setup specified) at /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm line 67. GLib-LOG **: posix_spawn avoided (child_setup specified) at /usr/lib64/perl5/vendor_perl/Glib/Object/Introspection.pm line 67. Oops, secure memory pool already initialized Oops, secure memory pool already initialized (WebKitWebProcess:16242): dbind-WARNING **: 12:27:34.639: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-E0JEi0nQgR: Connection refused [root@ftgme2 ~]# As before, mcc does open successfully. No longer happening in current cauldron. Status:
NEW =>
RESOLVED |