Bug 17838 - RpmDrake fails to start for a sudo-able user.`
Summary: RpmDrake fails to start for a sudo-able user.`
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-28 20:09 CET by Krzysztof Setlak
Modified: 2021-05-25 20:30 CEST (History)
4 users (show)

See Also:
Source RPM: drakxtools-17.19-1.mga6.x86_64
CVE:
Status comment:


Attachments
Last 100 lines of log (journalctl) immediately after trying to start drakrpm. (18.87 KB, text/x-log)
2016-03-02 06:46 CET, Krzysztof Setlak
Details

Description Krzysztof Setlak 2016-02-28 20:09:53 CET
Description of problem: RpmDrake fails to start. The user is capable of sudoing, the attempt to launch the program is made using a Gnome3 launcher. It's difficult for me to find out what's the problem as I can't run it using terminal. All hints I can provide is:
A) The program can be successfully ran as root (also logged in via Gnome3 shell).
B) When trying to reinstall the package it's possible to get this exact output from terminal:
[username@localhost ~]$ sudo rpm --erase ./*.rpm
error: package ./drakxtools-17.19-1.mga6.x86_64.rpm is not installed
[username@localhost ~]$ sudo rpm --install ./*.rpm
	package drakxtools-17.19-1.mga6.x86_64 is already installed
[username@localhost ~]$ 
(no lines removed!)


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


How reproducible:


Steps to Reproduce:
The descripion of the problem pretty much says it all, nevertheless:
1. Install Mageia 5 x86_64, upgrade to Caulron exactly as respective wiki article says how to do it.
2. After full update, attempt to run Mageia Control Center using mentioned activator.
Comment 1 Nic Baxter 2016-03-01 05:06:08 CET
I am trying to understand your report. rpmdrake and drakxtools are different packages. 

your issue erasing drakxtools can be easily explained. The erase option with rpm doesn't take a filename input but rather a package name input. rpm is trying to erase the package named drakxtools-17.19-1.mga6.x86_64.rpm and can't find it as the package name is drakxtools-17.19-1.mga6.x86_64

I am running mga6 in a vm upgraded from mga5. Both mcc and drakrpm work  whether through console or via gnome menu item. However to find the launcher you need to search for drakrpm

CC: (none) => nic

Comment 2 Nic Baxter 2016-03-01 05:12:46 CET
Please supply a few more details so I can exactly reproduce your report

Component: Installer => RPM Packages

Comment 3 Krzysztof Setlak 2016-03-01 07:55:29 CET
OK, I managed to find out that this problem is related to Gnome on this particular config. Maybe it will show that it's not even a bug in the OS, just a flaw of this particular instance.

1) The problem does not occur in Cinnamon, only Gnome.
2) The problem only occurs on this machine - I tested it on an old x86 laptop and MCC runs fine on Gnome there.

Could you please point me to a log file that could give more info on the issue? I can't seem to find the proper log anywhere...
Comment 4 Nic Baxter 2016-03-01 08:44:41 CET
Perhaps you could describe the issue in more depth. Are you having the problem with mcc or drakrpm? How are you trying to the start the program? What do you mean by a Gnome3 launcher?
Comment 5 Krzysztof Setlak 2016-03-01 23:05:33 CET
OK, I'll start with the launcher. What I mean is the icon on the side panel that is in the system by default:
http://s10.postimg.org/8zgu7jnnt/panel.png
4th icon from the top. When I click it, nothing happens.

Regarding the package, there is some confusion, I mean drakrpm (I thought it's mcc, but when I investigated the launcher using Alacarte, it showed that it points to drakrpm executable):
http://s27.postimg.org/eydsyusbn/alacarte.png
Comment 6 Nic Baxter 2016-03-02 00:27:04 CET
Thanks it is now clearer. Please click on the launcher and then open a terminal window and run 'sudo journalctl -n 100 > journal.log' . Then upload the log as an attachment.
Comment 7 Krzysztof Setlak 2016-03-02 06:45:48 CET
OK, did it, seems like the problem is described by these lines:

Mar 02 06:38:09 localhost polkitd[1106]: Operator of unix-session:c45 successfully authenticated as unix-user:amarok to gain TEMPORARY authorization for action org.mageia.drakconf.pkexec.run for unix-process:4687:12454 [/usr/bin/perl /usr/bin/drakconf] (owned by unix-user:amarok)
Mar 02 06:38:09 localhost pkexec[4692]: pam_systemd(polkit-1:session): Cannot create session: Already running in a session
Mar 02 06:38:09 localhost pkexec[4692]: pam_tcb(polkit-1:session): Session opened for root by (uid=1000)
Mar 02 06:38:09 localhost pkexec[4692]: amarok: Executing command [USER=root] [TTY=unknown] [CWD=/home/amarok] [COMMAND=/usr/libexec/drakconf]
Mar 02 06:38:09 localhost drakconf[4692]: ### Program is starting ###
Mar 02 06:38:09 localhost mageia-drakconf.desktop[4687]: No protocol specified
Mar 02 06:38:11 localhost sudo[4700]: pam_tcb(sudo:auth): Authentication passed for amarok from (uid=1000)


Full log in attachment.
Comment 8 Krzysztof Setlak 2016-03-02 06:46:42 CET
Created attachment 7507 [details]
Last 100 lines of log (journalctl) immediately after trying to start drakrpm.
Comment 9 Marja Van Waes 2016-04-28 20:56:57 CEST
(In reply to Krzysztof Setlak from comment #7)
> OK, did it, seems like the problem is described by these lines:
> 
> Mar 02 06:38:09 localhost polkitd[1106]: Operator of unix-session:c45
> successfully authenticated as unix-user:amarok to gain TEMPORARY
> authorization for action org.mageia.drakconf.pkexec.run for
> unix-process:4687:12454 [/usr/bin/perl /usr/bin/drakconf] (owned by
> unix-user:amarok)
> Mar 02 06:38:09 localhost pkexec[4692]: pam_systemd(polkit-1:session):
> Cannot create session: Already running in a session
> Mar 02 06:38:09 localhost pkexec[4692]: pam_tcb(polkit-1:session): Session
> opened for root by (uid=1000)
> Mar 02 06:38:09 localhost pkexec[4692]: amarok: Executing command
> [USER=root] [TTY=unknown] [CWD=/home/amarok] [COMMAND=/usr/libexec/drakconf]
> Mar 02 06:38:09 localhost drakconf[4692]: ### Program is starting ###
> Mar 02 06:38:09 localhost mageia-drakconf.desktop[4687]: No protocol
> specified
> Mar 02 06:38:11 localhost sudo[4700]: pam_tcb(sudo:auth): Authentication
> passed for amarok from (uid=1000)
> 
> 
> Full log in attachment.

@ Thierry

What can cause (assuming that's the problem) "mageia-drakconf.desktop[4687]: No protocol specified"?
Assigning to all packagers collectively, since

Assignee: bugsquad => thierry.vignaud
CC: (none) => marja11

Comment 10 Kristoffer Grundström 2021-05-25 14:03:11 CEST
Should this be closed?
This problem and its bugreport is way old and we've released a couple of Mageia versions since 2016.

Reporter, do you still experience this issue in the stable version of Mageia 8?

CC: (none) => lovaren

Comment 11 Krzysztof Setlak 2021-05-25 20:23:30 CEST
I don't use Mageia since a long time. This bug is over 5 years old - I think the only reasonable thing to do is to close it as expired...
Comment 12 Dave Hodgins 2021-05-25 20:30:32 CEST
Thanks. Closing as fixed since it's been working in Mageia for quite a few
releases.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
CC: (none) => davidwhodgins


Note You need to log in before you can comment on or make changes to this bug.