[Snap] Downloads directory defaults inside of Snap directory for LDAP users
Categories
(Firefox Build System :: Third Party Packaging, defect)
Tracking
(Not tracked)
People
(Reporter: jesse.darnley, Unassigned, NeedInfo)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
(deleted),
text/plain
|
Details |
Steps to reproduce:
Run Snap version of Firefox for the first time as a new LDAP user.
Actual results:
Downloads directory defaults to /home/<LDAP USER>/snap/firefox/common/Downloads
Expected results:
Downloads directory should default to /home/<LDAP USER>/Downloads
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Downloads Panel' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
What's the significance of LDAP here?
On the whole this smells like a Snap issue.
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 3•2 years ago
|
||
(In reply to :Gijs (he/him) from comment #2)
What's the significance of LDAP here?
On the whole this smells like a Snap issue.
It works for local users but not LDAP users. Seems like it was fixed for local users here: https://bugzilla.mozilla.org/show_bug.cgi?id=1535785
But I can confirm that the issue still occurs when logging on to a computer with a LDAP account.
Comment 4•2 years ago
|
||
I will confirm this bug based on the previous comment of a secondary user that has reproduced this issue specifically on a LDAP user account.
To provide the status flags of the latest channels/branches, I will need a detailed tutorial on how to set up and use a LDAP account.
Comment 5•2 years ago
|
||
Would you be able to provide us with a tutorial on how to set up and use a LDAP account on a Ubuntu 22? Thank you!
Comment 6•2 years ago
|
||
(In reply to Daniel Bodea [:danibodea] from comment #5)
Would you be able to provide us with a tutorial on how to set up and use a LDAP account on a Ubuntu 22? Thank you!
I just tried in our lab with OpenLDAP and I wasn't able to reproduce the issue. So it doesn't seem related to LDAP per say. We run MS AD + SSSD in production so I will have to set that up in the LAB and from that test we should be able to determine if the issue is related to our config or a general issue.
Comment 7•2 years ago
|
||
I can now confirm that the issue occurs on a AD joined Ubuntu 22.04 client using SSSD. Here are the instructions on how to reproduce my environment: https://pastebin.ubuntu.com/p/v6SGxXgn2T/
Comment 8•2 years ago
|
||
(In reply to Martin Nyström from comment #7)
I can now confirm that the issue occurs on a AD joined Ubuntu 22.04 client using SSSD. Here are the instructions on how to reproduce my environment: https://pastebin.ubuntu.com/p/v6SGxXgn2T/
Can you attach those here? Pastebin content will be lost in a few hours at most.
Comment 9•2 years ago
|
||
Description
•