Bug 508241 - Spectacle does not use user's default file manager for "open containing folder" after saving a file.
Summary: Spectacle does not use user's default file manager for "open containing folde...
Status: RESOLVED DUPLICATE of bug 397953
Alias: None
Product: Spectacle
Classification: Applications
Component: General (other bugs)
Version First Reported In: 6.3.5
Platform: Debian stable Linux
: NOR minor
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-14 12:48 UTC by nazo
Modified: 2025-08-14 14:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nazo 2025-08-14 12:48:29 UTC
SUMMARY
Spectacle does not use the system setting for default file manager.

STEPS TO REPRODUCE
1. Set a different file manager as your default.
2. Save a screenshot via Spectacle.
3. Click the open containing folder button

OBSERVED RESULT
Spectacle opens Dolphin if it is installed, otherwise it may produce an error saying "Dolphin not found" or open something else such as Thunar depending on system configuration.

EXPECTED RESULT
Spectacle should open whatever the user has set as their default file manager.

SOFTWARE/OS VERSIONS
Linux Distro: Debian Trixie (13)
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
Initially I had Dolphin installed and it was calling that every time.  When I uninstalled Dolphin, Spectacle produced an error saying Dolphin was not found.  After a reboot since then it now opens Thunar, so I guess it must load the list of available options itself on initial startup or something.  pcmanfm-qt was set as my preferred file manager in the KDE settings the entire time, so in each case it has failed to use my setting.  (I can say that xdg-open with a folder location opens my preferred file manager, so KDE has presumably set it correctly.)
Comment 1 Nate Graham 2025-08-14 14:54:00 UTC

*** This bug has been marked as a duplicate of bug 397953 ***