Open
Bug 721318
Opened 12 years ago
Updated 2 years ago
“Unknown location” after the Profile Directory path in Troubleshooting Information (encfs; unclear message)
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: Aleksej, Unassigned)
References
Details
1. Help → Troubleshooting Information 2. Look at end of the “Profile Directory” line: If the “Include account names” checkbox is unchecked: Profile Directory | [Open Containing Folder] (Unknown location) If the checkbox is checked: Profile Directory | /home/(…username…)/.thunderbird/fugg69vt.(…profilename…) (Unknown location) What is that “Unknown location”? It knows, at least, where the profile is.
Comment 1•12 years ago
|
||
It means that we couldn't figure out whether the profile directory was local or on the network.
Reporter | ||
Comment 2•12 years ago
|
||
(reproduced with versions 10.0b4 for Linux-i686 and Linux-x86_64, 10.0b5 and the current Daily for Linux-x86_64)
Reporter | ||
Comment 3•12 years ago
|
||
> /home/(…username…)/.thunderbird/fugg69vt.
Actually, it’s not exactly like that, because the user’s home directory is not /home/(…username…), but /home/(…a hidden (dot) directory with encfs…)/(…username…)
The filesystem is mounted like this:
encfs on /home/.(…skipped…) type fuse.encfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
Comment 4•12 years ago
|
||
Yes, in general I don't think we can tell whether an encfs is local or on the network.
Reporter | ||
Comment 5•12 years ago
|
||
OK. The message is very unclear for me, because I almost never use network file systems like that.
Summary: “Unknown location” after the Profile Directory path in Troubleshooting Information → “Unknown location” after the Profile Directory path in Troubleshooting Information (encfs; unclear message)
Updated•12 years ago
|
Comment 6•12 years ago
|
||
I see the same "(Unknown location)" for my NFS-mounted homedir (so the location is "filername:/some/path")
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•