Bug 753278 - Log into KDE desktop fails (btrfs filesystem)
Summary: Log into KDE desktop fails (btrfs filesystem)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-workspace
Version: 16
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-11 18:46 UTC by Singer Michael
Modified: 2013-02-13 23:19 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 23:19:14 UTC
Type: ---


Attachments (Terms of Use)

Description Singer Michael 2011-11-11 18:46:38 UTC
Description of problem:

OS Version: Fedora 16
Installation Medium: netinst ISO x86_64 KDE-spin

Problem Description:
I've chosen for installation in the root "/" (/ dev/sda3) file system btrfs. I have to subvolume with the name VOL-ROOT created.

# btrfs subvolume list /
ID 256 top level 5 path VOL-ROOT

After installation, I was able to register without problems to the KDE desktop. Now I have created another subvolume for the home directory (VOL-HOME). That mount point, I'm in the /etc/fstab.

# btrfs subvolume list /
ID 256 top level 5 path VOL-ROOT
ID 257 top level 5 path VOL-HOME

# cat /etc/fstab
UUID=5d1fb49b-758a-4cfe-aa56-ba4f9707ddf6 / btrfs   defaults,subvolid=256    1 1
UUID=5d1fb49b-758a-4cfe-aa56-ba4f9707ddf6 /home  btrfs defaults,subvolid=257 1 1
UUID=ab7e61f3-2a73-43d4-98f3-75126c0e90f6 /boot  ext4    defaults    1 2
UUID=f6a58a92-9b3f-4502-a3b0-6260b0013e9c swap   swap    defaults    0 0

The user directories from the original /home I moved into the new /home in the subvolume HOME-VOL.

After a reboot I could not log me KDE desktop. The following error message was displayed on the screen:

First dialog box: Can not enter home directory. Using /.
Second dialog box: No write access to $ HOME directory (/). KDE is unable to start.
Third dialog: Could not start ksmserver.

In the file /var/log/messages contains the following error message:
Nov 13:38:11 fedorabox kdm:  :0 '[898]: Cannot chdir to michael's home /home/michael: Permission denied


The file permissions on /home but are correct:
# ls -l /home
drwxr-xr-x. 1  root root          82   11. Nov 12:49  /home
drwx------. 1  michael michael   554   11. Nov 13:19  michael

Why can I not log on KDE desktop?

How reproducible: any time

If I were doing anything in the home directory irreversibly, ie the /home directory from the subvolume subvolume VOL-VOL-HOME back to ROOT move I can log back on KDE.

Incidentally, a login to the text console (tty) is always possible.

My guess is that if the problem is handling the subvolume btrfs or on KDE itself.

Regards
Michael Singer

Comment 1 Singer Michael 2011-11-12 09:43:52 UTC
Adjustment because of spelling errors (third from last paragraph):
[...]
If I do the whole reverse, ie the / home (from subvolume VOL-HOME) back into the subvolume VOL ROOT move me I can log into the KDE desktop.
[...]

Comment 2 Fedora End Of Life 2013-01-16 19:31:53 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 Fedora version prior to Fedora 16'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 Fedora 16 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 Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 23:19:18 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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 
Fedora please feel free to reopen this bug against that version.

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


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