Description of problem: cannot open attachment to database entry Version-Release number of selected component (if applicable): fully updated F32 using Gnome desktop How reproducible: try open attachment that was saved to database entry Steps to Reproduce: 1.try open from the main menu 2.or, alternatively through "edit" entry 3. Actual results: attachment will not open, instead error message is displayed "access denied". the usual message asking if the user wishes to save or discard any changes is correctly displayed Expected results: attachment will open (in the clipboard?) using the appropriate software and a message will be displayed if the user wishes to save or discard any changes Additional info: I tested the same in openSUSE Tumbleweed and Debian Buster. the issue is the same in Tumbleweed (does not work), but everything works correctly in Buster. this is why I suspect this could be a Wayland issue (Buster not on Wayland yet?) I am not knowledgeable enough to say for sure, but it seems to me there are related issues when using Keepass and Wayland together (autotype will not work in Firefox, clipboard does not always clear - security issue) that make me think this is one cluster of issues all having to do with functionality that was provided by xdotool before Wayland wish to refer to https://bugzilla.redhat.com/show_bug.cgi?id=1761153 because even when it is closed it is not solved thank you in advance for providing insight and getting this into the appropriate channel. Keepass (the original one by Dominik Reichl) is an important security application
I made comment 3 on https://bugzilla.redhat.com/show_bug.cgi?id=1843720 this is a different issue but maybe part of a cluster of issues with a single root cause (Wayland in combination with Clipboard?). it is already a while ago (F30?) that all these things just worked - so something has changed
Workaround: it's still possible to save attachments. This issue is also present on X11 so isn't related to Wayland. It isn't present in KeePass 2.45 on Fedora 31, suggesting that this has been caused by a change in Mono. Since both bugs involve xdg-open, it might turn out that this is related to bug #1839410.
*** This bug has been marked as a duplicate of bug 1839410 ***