← Back to issue list

Incorrect Downloads directory for LDAP user in snapped firefox & chromium

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#2025447
Type
issue
State
open
Author
~dgadomski
Labels
se
Created
Updated
Closed

Current evaluation

Snapped Firefox/Chromium downloads to ~/snap/.../Downloads for LDAP users instead of ~/Downloads; untriaged, inactive 3+ years

Suggested action: needs triage

Reason: No maintainer comments or labels present; the issue has clear reproduction steps and expected vs actual results, but has been inactive for over 3 years without any triage. The issue is about snap package behavior (Firefox/Chromium) rather than snapcraft itself, which may require a different project to address.

Impact: 50 Quick Win: 30.0 Staleness: 85 Complexity: 40 Confidence: 45 Support Request: 10

Issue body

Test procedure: 1. Log in to Gnome as a Active Directory user. 2. Launch browser (firefox or chrome) - make sure there's no existing config (we are interested in the default Downloads location). 3. Download a file via the browser. 4. Check where it was downloaded. Expected result: The files are downloaded to ~/Downloads (or a translated equivalent). Actual result: The files are downloaded to: ~/snap/firefox/common/Downloads ~/snap/chromium/current/Downloads For local users the behavior is as expected (all files are downloaded to ~/Downloads). This is very inconvenient for enterprise environments where manual setting modification is needed on every host. This has been tested on 22.04 with the following versions: - firefox (116.0.3 Mozilla Firefox Snap for Ubuntu canonical-002 - 1.0) - chromium (Version 116.0.5845.110 (Official Build) snap (64-bit)) - snapd 2.58+22.04.1 [1] https://ubuntu.com/server/docs/service-sssd-ad

Evaluation history

Date Model Scores Action Summary
qwen3.6-35b-a3b-mtp-q6
Impact: 50
Quick Win: 30.0
Staleness: 85
Complexity: 40
Confidence: 45
Support Request: 10
needs triage Snapped Firefox/Chromium downloads to ~/snap/.../Downloads for LDAP users instead of ~/Downloads; untriaged, inactive 3+ years
qwen/qwen3.6-35b-a3b
Staleness: 92
Complexity: 60
Confidence: 85
Support Request: 5
close stale Snapped Firefox and Chromium route downloads to ~/snap/.../Downloads instead of ~/Downloads for LDAP users. Local users work correctly. Reported on Ubuntu 22.04 with no maintainer response in over 3 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 65
Confidence: 85
Support Request: 10
close stale Snap-packaged Firefox and Chromium download files to ~/snap/... instead of ~/Downloads for LDAP users. Issue is 3 years old with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 65
Confidence: 85
Support Request: 10
close stale Snapped Firefox and Chromium download files to ~/snap/... instead of ~/Downloads for LDAP/AD users on Ubuntu 22.04. No maintainer response or comments in over 2.5 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 92
Complexity: 45
Confidence: 75
Support Request: 5
needs triage LDAP/AD users experience incorrect default download paths in snapped Firefox and Chromium, saving to snap-specific directories instead of ~/Downloads. Untriaged, inactive for over two years.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.