Bug 2069687

Summary: chrome based browsers cannot save images, crash in xdg-desktop-portal
Product: [Fedora] Fedora Reporter: Simon Putt <lemonzest>
Component: chromiumAssignee: Tom "spot" Callaway <spotrh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 36CC: sanjay.ankur, spotrh, tpopela, yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-31 08:42:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
crash from journal none

Description Simon Putt 2022-03-29 13:22:55 UTC
Created attachment 1868986 [details]
crash from journal

Description of problem:

Cannot save images from web pages in chromium based web browsers (Brave/Edge/Opera/Vivaldi) where I can save the same images with Firefox

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1. Loads a website with images
2. Attempt to right click save image
3. xdg-desktop-portal will coredump

Actual results:

xdg-desktop-portal coredumps

Expected results:

The image to be saved
Additional info:

Fedora 36 beta, GNOME Workstation Edition

Comment 1 Simon Putt 2022-03-29 13:36:21 UTC
I just attempted the same tests above in an x11 xorg session and I am able to save images fine, so must be a Wayland issue

Comment 2 Ankur Sinha (FranciscoD) 2022-03-31 08:42:33 UTC
Dup of https://bugzilla.redhat.com/show_bug.cgi?id=2036518 from the looks of it. In any case, it's likely a bug in xdg-desktop-portal, not in the Fedora Chromium package. I'll close this now, but please feel free to open it against xdg-desktop-portal if the bugfix that's been pushed does not fix your issue.

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