Bug 15617 - xguest not working with lxdm, homedirectory owned by root
Summary: xguest not working with lxdm, homedirectory owned by root
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Salguero
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-01 23:16 CEST by Marc Krämer
Modified: 2023-04-28 14:04 CEST (History)
0 users

See Also:
Source RPM: lxdm-0.5.0-3.mga5
CVE:
Status comment:


Attachments

Description Marc Krämer 2015-04-01 23:16:19 CEST
if you login as xguest, you get a user directory, which should contain /etc/skel and should be writeable by the user xguest.

My terminal is executed as rbash - but as far as "ls -la" tells the home-directory is owned by root and creating a file fails. Even no skel files exist. In lxde the menu is empty, and most programs complain they can't write files to the home-directory.

Reproducible: 

Steps to Reproduce:
Comment 1 Jani Välimaa 2015-04-02 09:52:30 CEST
Looks similar to bug 5980.

Which display manager are you using? Can't reproduce the issue with lightdm (+MATE/Xfce).

Source RPM: http://pkgs.fedoraproject.org/repo/pkgs/xguest/ => xguest-1.0.10-12.mga5

Comment 2 Marc Krämer 2015-04-02 10:54:53 CEST
tested with lxdm, lxde & mate as desktops.

I didn't know this depends on the display manager...
Jani Välimaa 2015-04-02 14:46:14 CEST

Summary: xguest not working anymore, homedirectory owned by root => xguest not working with lxdm, homedirectory owned by root

Jani Välimaa 2015-04-02 15:59:05 CEST

Source RPM: xguest-1.0.10-12.mga5 => lxdm-0.5.0-3.mga5

Comment 3 Samuel Verschelde 2015-06-06 01:12:23 CEST
Assigning to lxdm maintainer.

Assignee: bugsquad => nicolas.salguero
Whiteboard: (none) => MGA5TOO

Nicolas Salguero 2015-06-21 15:03:57 CEST

Status: NEW => ASSIGNED

Comment 4 Marc Krämer 2023-04-28 14:04:25 CEST
old

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


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