Bug 472630 - Can't import from Dolphin to Itinerary
Summary: Can't import from Dolphin to Itinerary
Status: REPORTED
Alias: None
Product: KDE Itinerary
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-25 20:21 UTC by aronkvh
Modified: 2023-07-27 18:23 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description aronkvh 2023-07-25 20:21:35 UTC
Opening any file from the Dolphin "open with..." menu results in 
 org.kde.itinerary: Failed to open "/home/aronkvh/Downloads/boarding-pass (2).pdf" "No such file or directory"

When opening the same file from Itinerary it imports fine.
Comment 1 Volker Krause 2023-07-27 15:23:01 UTC
Strange, that works here without problems. Does this affect all files or just some with certain problematic file names? Does the file printed there actually exist or is it getting the wrong path from Dolphin do begin with?
Comment 2 aronkvh 2023-07-27 15:29:27 UTC
(In reply to Volker Krause from comment #1)
> Strange, that works here without problems. Does this affect all files or
> just some with certain problematic file names? Does the file printed there
> actually exist or is it getting the wrong path from Dolphin do begin with?

The path works and the error happens with any file. I think it's a problem with Flatpak, because Itinerary doesn't get filesystem=home access by default, but after setting it up can import from Dolphin
Comment 3 Volker Krause 2023-07-27 18:23:46 UTC
Ah, Flatpak is the important thing I was missing here! I need to check if there's a better way to enable this without having to give apps full file system access.