Bug 408483 - "Open containing folder" button does not work as expected
Summary: "Open containing folder" button does not work as expected
Status: RESOLVED DUPLICATE of bug 408244
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Neon Linux
: HI grave
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-09 15:29 UTC by Patrick Silva
Modified: 2019-06-13 04:11 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2019-06-09 15:29:37 UTC 
STEPS TO REPRODUCE
1. press printscreen key to open Spectacle
2. make sure "Quit after Save or Copy" is unchecked
3. click on "Save" or "Save as" buttons to save the screenshot (a green bar shows up after you save the screenshot)
4. click "Open containing foder" button

OBSERVED RESULT
An empty Dolphin window opens, its location bar shows ">path>name-of-the-screenshot"
and the screenshot opens in the default image viewer.

EXPECTED RESULT
Spectacle opens the containing folder.

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.16.80
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3
Comment 1 Nate Graham 2019-06-10 20:31:04 UTC 
Hmm, actually for me nothing happens at all when I click the button. :/ Something funny is printed to the console though:

kf5.kio.widgets: No node found for item that was just removed: QUrl("file:///home/dev/Pictures/IMG_0713.JPG")

David, would you mind taking a look?
Comment 2 David Redondo 2019-06-12 09:08:16 UTC 
Sorry works for me :/ .
We just do KIO::highlightInFileManager. Does  Tools>Open Screenshot Folder work? It uses the same method.
Comment 3 Nate Graham 2019-06-13 04:11:02 UTC 
Ah OK, this is actually the Dolphin bug.

Thankfully the bug has not been released to users yet; it's only in Dolphin from git master.

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