Bug 21920

Summary: Cannot remotely run drakconf through ssh
Product: Mageia Reporter: Christian C <bugzzzz>
Component: RPM PackagesAssignee: Mageia tools maintainers <mageiatools>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: marja11, ouaurelien
Version: 6   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Christian C 2017-10-23 14:30:10 CEST
Description of problem:
When drakconf is run in a shell connected to a remote ssh server from a mageia-5.1 local client, an error message is displayed and and nothing displays on the client.

The remote ssh server is configured with the option :
X11Forwarding yes

The client is connected with the command :
$ ssh -X <server-IP> -l <username>
root is substituted :
$ su
password :

then drakconf is started :
# drakconf

then following message displays :
# Too late to run INIT block at /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/Glib/Object/Introspection.pm line 257.

This could be a regression for the same operation from a mageia-5.1 client to a mageia-6 ssh server works fine, even when the ssh connection is run without -X argument.

However, running a graphical program as pcmanfm as a common user works correctly.

I noticed some differences between the results in the execution of drakconf and pcmanfm in a mga-5.1 server and mga-6 server that might help :

On mga-5.1 server :
# ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
azor     10077  9704  0 23:09 pts/3    00:00:00 pcmanfm
root     10085  9754  0 23:09 pts/2    00:00:00 /usr/bin/perl /usr/sbin/drakconf
root     10089 10085  1 23:09 pts/2    00:00:01 /usr/bin/perl /usr/libexec/drakconf 
# netstat -taupe
Connexions Internet actives (serveurs et établies)
Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat        Utilisatr  Inode      PID/Program name    
tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN      root       17028      1750/sshd       
tcp        0      0 localhost:42452         localhost:6013          ESTABLISHED azor       3352145    10077/pcmanfm       
tcp        0      0 localhost:42152         localhost:6012          ESTABLISHED root       3352898    10089/perl

On mga-6 server :
# ps -ef
UID        PID  PPID  C STIME TTY          TIME CMD
azor      8579  7252  1 23:12 pts/3    00:00:01 pcmanfm
root      8586  7204  2 23:12 pts/2    00:00:02 /usr/bin/perl /usr/sbin/drakconf
# netstat -taupe
Connexions Internet actives (serveurs et établies)
Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat        Utilisatr  Inode      PID/Program name    
tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN      root       15090      1341/sshd 
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN      root       15099      1341/sshd        
tcp6       0      0 localhost:49424         localhost:6013          ESTABLISHED azor       1678690    8579/pcmanfm 
tcp6       0      0 localhost:49350         localhost:6012          ESTABLISHED root       1678777    8586/perl  

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. configure the sshd_config with "X11Forwarding yes" on the mga-6 server and start the daemon
2. connect to the ssh server
3. switch to root user
4. run drakconf command
Marja Van Waes 2017-10-24 10:26:54 CEST

CC: (none) => marja11
Assignee: bugsquad => mageiatools

Comment 1 Christian C 2017-10-24 10:46:43 CEST
Sorry, I made a mistake while writing the report. Replace the above paragraph by :
"This could be a regression for the same operation from a mageia-5.1 client to a _mageia-5.1_ ssh server works fine, even when the ssh connection is run without -X argument."
Comment 2 Marja Van Waes 2017-10-27 19:58:58 CEST
Mass-change status to NEW for all bugs that were filed as UNCONFIRMED between October 9 and now, and that still have that status now.

From now on all newly filed bugs will have the NEW status again, like before, regardless of who files the report.

Ever confirmed: 0 => 1
Status: UNCONFIRMED => NEW

Comment 3 Aurelien Oudelet 2020-08-05 16:35:14 CEST
This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Resolution: (none) => OLD
CC: (none) => ouaurelien
Status: NEW => RESOLVED