Bug 15280

Summary:	systemd and LDAP: impossible to mount a external disk drive or a USB key from the desktop
Product:	Mageia	Reporter:	Olivier Hoarau <olivier.hoarau>
Component:	RPM Packages	Assignee:	Colin Guthrie <mageia>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	Keywords:	NEEDINFO
Version:	4
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	systemd	CVE:
Status comment:

Description Olivier Hoarau 2015-02-13 17:40:51 CET

Description of problem:

It's impossible to mount a external disk drive or a USB key from the desktop. The mageia control center can't be launched from the desktop. I use KDE and a user authentication with a LDAP server, this problem appears with mageia3 and systemd, I have to mount manually all external storage devices from a shell. And I launch all draktools also from a shell.

And the solution

I have just find the solution of my problem which is very simple, I added this line in my /etc/pam.d/system.auth file

session     required      pam_systemd.so

here is my complete file

[olivier@rangiroa ~]$ more /etc/pam.d/system-auth 
#%PAM-1.0

auth        required      pam_env.so
auth        sufficient    pam_tcb.so shadow nullok prefix=$2a$ count=8
auth        required      pam_deny.so
auth        sufficient    pam_ldap.so

account     sufficient    pam_tcb.so shadow
account     required      pam_deny.so
account     sufficient    pam_ldap.so

password    required      pam_cracklib.so try_first_pass retry=3 minlen=4  dcredit=0  ucredit=0
password    sufficient    pam_tcb.so use_authtok shadow write_to=shadow nullok prefix=$2a$ count=8
password    required      pam_deny.so
password    sufficient    pam_ldap.so

session     optional      pam_keyinit.so revoke
session     required      pam_limits.so
session     [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
session     required      pam_tcb.so
session     required      pam_systemd.so
session     sufficient    pam_ldap.so

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

from Mageia 3, still present with mageia 4 and 4.1

How reproducible:

Always

Steps to Reproduce:
1.use a ldap authentication  
2. start KDE and plug a USB key
3. try to mount it from the desktop and you get the message like that "impossible to mount"

steps to solve
1. modify the system-auth file
2. exit the KDE session and log in back
3. try to mount, it works !
 


Reproducible: 

Steps to Reproduce:

Comment 1 Marja Van Waes 2015-09-21 10:51:29 CEST

Installer and Release bugs should always be set to cauldron, because once the isos for a stable version have been created, they cannot be changed.

This bug was filed very long ago, for Mageia 4. Was this bug still valid for Mageia 5?

(If so, please do _not_ set the version to "5". Only asking because if it was still valid for Mageia 5, that then we'll know we'll have to pay attention to this issue when testing the 6 alpha's and later).

Please close this bug report if the problem was solved in Mageia 5hhhh

Keywords: (none) => NEEDINFO
Version: 4 => Cauldron

Comment 2 Rémi Verschelde 2015-09-21 11:22:17 CEST

Not a release media bug, more likely systemd. Assigning to maintainer.

If the issue still happens with Mageia 5 or Cauldron, please update the version field accordingly.

CC: sysadmin-bugs => (none)
Component: Release (media or process) => RPM Packages
Hardware: i586 => All
Version: Cauldron => 4
Assignee: bugsquad => mageia
Source RPM: (none) => systemd

Rémi Verschelde 2015-09-21 11:22:38 CEST

Summary: systemd and LDAP => systemd and LDAP: impossible to mount a external disk drive or a USB key from the desktop

Comment 3 Samuel Verschelde 2015-09-21 13:18:46 CEST

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

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.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you 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. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

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.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Comment 4 Marja Van Waes 2015-10-27 06:56:14 CET

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too).

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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