Bug 9204

Summary:	mkxauth doesn't setup the group correctly when using with -c
Product:	Mageia	Reporter:	Bruno Cornec <bruno>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	stormi-mageia, thierry.vignaud
Version:	2	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	mkxauth-1.7-19.mga1.src.rpm	CVE:
Status comment:

Description Bruno Cornec 2013-02-28 13:22:03 CET

Description of problem:

I'm trying to get rid of a message similar to the one mentioned on the bug #3714 on my Mageia 2. So I used the suggested tip:

mkxauth -c

First this doesn't seem to fix the issue I had (but that's anothier pb !), but it doesn't correctly setup the group for the file:

mkxauth -c
adding key for victoria2.home.musique-ancienne.org to /users/bruno/.Xauthority ... done
chown: utilisateur non valide: Â«Â bruno.brunoÂ Â»

This is normal as the function givusr() does chown $usrnam.$usrnam $dstfil which is wrong if your user doesn't have a group with the same name (my case).


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

1.7-19.mga1

How reproducible:

everytime

Steps to Reproduce:
1. Create a user and have its group name with another name
2. do mkxauth -c
3. enjoy !


Reproducible: 

Steps to Reproduce:

Manuel Hiebel 2013-03-02 00:39:09 CET

CC: (none) => thierry.vignaud

Comment 1 Samuel Verschelde 2013-09-05 12:40:47 CEST

Hi, sorry nobody answered nor triaged this bug yet. I guess it's still valid?

Also, is it valid in Mageia 3 and cauldron?

Keywords: (none) => NEEDINFO
CC: (none) => stormi

Comment 2 Manuel Hiebel 2013-10-22 12:19:07 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is 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.

-- 
The Mageia Bugsquad

Comment 3 Manuel Hiebel 2013-11-23 16:15:46 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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