Description of problem: Snapd’s fish configuration (/usr/share/fish/vendor_conf.d/snapd.fish) adds its own data directory (/var/lib/snapd/desktop) to the end of $XDG_DATA_DIRS using space as a separator, which makes most (all?) application using this variable not work. Version-Release number of selected component (if applicable): snapd-2.54.3-1.fc35.x86_64 How reproducible: Install the snapd package and (re)start the fish shell. Steps to Reproduce: 1. Install the snapd package 2. (re)start the fish shell Actual results: The value of XDG_DATA_DIRS is "ORIGINAL_VALUE /var/lib/snapd/desktop" Expected results: The value of XDG_DATA_DIRS is "ORIGINAL_VALUE:/var/lib/snapd/desktop" Additional info: Although fish indeed uses space as a separator in the PATH environment variable, XDG_DATA_DIRS should not be extended like this, but using the colon.
Seems to be already fixed by upstream (see https://launchpad.net/snapd/+bug/1957155 which i can’t link as bugzilla says it’s unknown to it).
I am confused. AFAICT Fedora 35 has fish 3.3, which was supposed to treat XDG_DATA_DIRS as path like thing already (actually even since fish 3.1 release). I haven't backported the patches, as Ubuntu has an old version of fish. Though looking at the upstream code https://github.com/fish-shell/fish-shell/blob/c6166f8cedf768e5ca2373ed13ab64c6681a34b2/share/config.fish the vendor config files are applied at the very end. So for XDG_DATA_DIRS to not be configured like a path it must have been set already when it reached this: https://github.com/fish-shell/fish-shell/blob/c6166f8cedf768e5ca2373ed13ab64c6681a34b2/share/config.fish#L56 (why?). I'm guessing something else, which runs before fish, must have set this variable, so it never gets switched to the 'path' mode and thus `set` no longer works in a predictable way.
FEDORA-2022-a1ee445f2b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a1ee445f2b
FEDORA-2022-a1ee445f2b has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-3f5d692439 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3f5d692439
FEDORA-2022-fa0fd2e5f0 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-fa0fd2e5f0
FEDORA-2022-9c42c03669 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9c42c03669
FEDORA-EPEL-2022-1850977bce has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-1850977bce
FEDORA-EPEL-2022-6e723fda27 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6e723fda27
FEDORA-EPEL-2022-a7681d7e28 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-a7681d7e28
FEDORA-EPEL-2022-6e723fda27 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6e723fda27 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-1850977bce has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-1850977bce See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-fa0fd2e5f0 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-fa0fd2e5f0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-fa0fd2e5f0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-9c42c03669 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-9c42c03669` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9c42c03669 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-a7681d7e28 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-a7681d7e28 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-3f5d692439 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-3f5d692439` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3f5d692439 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-6e723fda27 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-1850977bce has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-9c42c03669 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-fa0fd2e5f0 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-a7681d7e28 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-3f5d692439 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.