baobab is not able to read a mounted encrypted home directory

Bug #1184283 reported by Michael Basse
56
This bug affects 12 people
Affects Status Importance Assigned to Milestone
baobab (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

i was trying to find out what is using a lot of space on my system.

Its using the default home-encryption from ubuntu.
The home belongs to "michael". The home is mounted (see screenshot attached) but baobab is only showing the .Private part. baobab was started as "michael"

Its not showing ~/Documents and so on, just the encrypted files.

It would be great if baobab could read the mounted part which contains ~/Documents and so on

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: baobab 3.6.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
Uname: Linux 3.8.0-22-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Sun May 26 10:00:00 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-07-09 (321 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: baobab
UpgradeStatus: Upgraded to raring on 2013-05-06 (19 days ago)

Revision history for this message
Michael Basse (michael-alpha-unix) wrote :
Revision history for this message
Michael Basse (michael-alpha-unix) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in baobab (Ubuntu):
status: New → Confirmed
Revision history for this message
Jared Silva (jayrod) wrote :

You can work around this issue by selecting Home folder, or by selecting Scan Folder and then selecting a folder in your home directory.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Am I correct to assume this only happens when

1) you have an encrypted home file system
2) you start the search at either / or /home but not at ~, for example

Both conditions need to be fulfilled?

tags: added: precise
Revision history for this message
Michael Basse (michael-alpha-unix) wrote :

Hi Rolf,
yes that is correct.

Revision history for this message
Tronde (tronde) wrote :

Hi,
I would like to confirm that this bug affects Xenial, too. Both conditions from #5 are fulfilled, too. To work around I follow the suggestion from #4.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.