Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File picker has stopped working #262

Open
TheCodeLamp opened this issue Mar 10, 2025 · 10 comments
Open

File picker has stopped working #262

TheCodeLamp opened this issue Mar 10, 2025 · 10 comments
Labels
bug Something isn't working

Comments

@TheCodeLamp
Copy link

Describe the bug

For some reason I can't export files in obsidian, or select files in protomail to add to an email. Obsidian is installed as a flatpak and protonmail is installed in a fedora distrobox.

I get the file picker popup, but when I click "Save" or "Open" it just closes, it's like the app doesn't get the result.

This happens both on my laptop, and my desktop (which runs bazzite). It started like a week ago or so. I have tried rolling back to a version a couple of weeks ago, but the problem persists.

I have tried running this script, but it didn't solve it:

#!/bin/bash
cd ~/
rm -rf .kde
rm -rf .cache/plasmashell*
rm -rf .cache/org.kde.dirmodel-qml.kcache
rm -rf .cache/kioexec/ .cache/krunner/ .cache/ksycoca5*
rm -rf .cache/krunnerbookmarkrunnerfirefoxdbfile.sqlite
rm -rf .config/plasma*
rm -rf .config/kde*

I don't know where to find log files for the file picker.

Also, when I select items in protonmail it also prepends the filename with "file:" and if I try to select that I get the error `The file "file:" could not be found", and sometimes the first letter gets removed. This only happens in protonmail, not Obsidian.

I have no idea how to even get log files. If I run the programs from the terminal, no output is registered, this is where my theory that the file picker is just exiting.

What did you expect to happen?

I expect obsidian to be able to export and protomail to be able to add attachments.

Output of bootc status

apiVersion: org.containers.bootc/v1
kind: BootcHost
metadata:
  name: host
spec:
  image: null
  bootOrder: default
status:
  staged: null
  booted:
    image: null
    cachedUpdate: null
    incompatible: true
    pinned: false
    store: null
    ostree:
      checksum: 0ffdd6432a8ca594b0d9dd1bd098d95663e1afe61fc3f28196b83d80d9401313
      deploySerial: 0
  rollback:
    image: null
    cachedUpdate: null
    incompatible: true
    pinned: false
    store: null
    ostree:
      checksum: af186f670bf8e1c342099837a5156578fc9e5d7a9d06fc978b8e2becbec9ee51
      deploySerial: 0
  rollbackQueued: false
  type: null

Output of groups

simonp wheel plugdev

Extra information or context

No response

@dosubot dosubot bot added the bug Something isn't working label Mar 10, 2025
@TheCodeLamp
Copy link
Author

TheCodeLamp commented Mar 10, 2025

Looking a little closer, this error pops up for both the programs when I start them from the terminal:

[14:0310/220558.686889:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

I managed to remove this error by giving the flatpak access to the system bus, however, this has not fixed the issue, the file picker is still useless.

@TheCodeLamp
Copy link
Author

I have tried the Obsidian appimage, and it doesn't work in that either.

@inffy
Copy link
Collaborator

inffy commented Mar 10, 2025

Have you installed something through brew that could have pulled in something like dbus?

@ledif
Copy link
Member

ledif commented Mar 11, 2025

From what I gather, the file picker is broken for you with Flatpaks, AppImages and distrobox-launched applications. Does the file picker work for native KDE apps?

Could you temporarily create a new test user and see if it's broken for that user as well? We can try to narrow it down to a user config file.

@TheCodeLamp
Copy link
Author

I haven't interacted with brew at all.

I think this might be two different bugs with the apps instead with the desktop environment, maybe. I made a new user and made a new vault using obsidian. I then tried to export a file to a PDF, and it failed like in my normal user account. However, when I installed the ProtonMail app it worked normally, I could add attachments through the file picker and there was no "file:" prefix.

I've also tried another flatpak app, LibreWolf. I tried uploading a file to virustotal, something that uses the file picker, and it worked both on the new account and my normal account.

This has made me believe that:

  1. The issue with Obsidian is tied to the obsidian app itself and not Aurora.
  2. The issue with the ProtonMail app is something tied to my user account.

I think I need to make sure that the issue with the obsidian app is reproducible so that I can submit an issue to their bug portal.

I'll try to remove the configurations for ProtonMail and reinstall it again to see if that fixes the attachment issues.

@TheCodeLamp
Copy link
Author

I have tried earlier obsidian versions and this issue is only present on the 1.8.9 version making the obsidian issue unrelated.
Here is the link to the obsidian bug report:
https://forum.obsidian.md/t/export-to-pdf-broken-on-kde-linux/98005?u=plywood5408

The issue with ProtonMail still persist, however.

@inffy
Copy link
Collaborator

inffy commented Mar 11, 2025

Tried to reproduce the ProtonMail issue

  1. create a Fedora 41 distrobox
  2. install the protonmail.rpm from proton.me
  3. launch protonmail

I then tested creating a new email and added a file as an attachment.

Couldn't reproduce the file picker issue. The app opens the KDE file picker and I can add file as an attachment.

Might be somekind of config corruption but I don't know which config/app handles the file picker.

@TheCodeLamp
Copy link
Author

Thank you for trying it out. I've seen that it's tied to my user account.

Right now I'm struggling to figure out how I'll handle the removal of the surface kernel, so I can't do any more trials right now.

@inffy
Copy link
Collaborator

inffy commented Mar 11, 2025

Thank you for trying it out. I've seen that it's tied to my user account.

Right now I'm struggling to figure out how I'll handle the removal of the surface kernel, so I can't do any more trials right now.

Is this your own custom image or what image are you running?

@TheCodeLamp
Copy link
Author

I'm running aurora-surface 41, but I've recently been made aware that the surface branch will be removed soon. I am currently trying to reinstall the OS with little success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants