Linux Brave desktop client not working correctly with Kubuntu Dolphin file manager after last updates. Function "open file in folder/see file in folder" not working for downloaded files

Linux Brave desktop client not working correctly with Dolphin file manager after update. Function open in folder/see in folder not working.


Description of the issue: File manager closes when you trying to open downloaded file and it’s location
How can this issue be reproduced?

  1. Download any file from any site (for example some mp3 file).
  2. Click on Down-Arrow button
    image
    in the top right corner to see last downloads
  3. There will be your downloaded file with a two buttons - to open it or to see file in the downloaded folder/location (literally to see where file was downloaded/ to show him in the some folder).
  4. The Dolphin File Manager starts and immedeately closes. The issues was not shown in the previous Brave versions.

Expected result: Dolphin correctly shows file’s location/folder where it placed

Brave Version( check About Brave):
Version 1.68.134 Chromium: 127.0.6533.88 (Official), (64 bit)

Additional Information: OS Kubuntu 20.04, also issue was spotted on Ubuntu 22.04.3

1 Like

Bump. Issue doesnt exists in Linux Firefox for example or some other browsers. It is should be some settings issue or update issue

1 Like

Updated Brave to v1.69.162

Issue is still exists.

I also found this https/github.com/brave/brave-browser/issues/33028
So, i believe this is not first issue connected to “show in the folder”. It is not as my issue but very similar

My Dolphin Manager just opens and immedeately closed. I didnt change anything in the settings of Brave or System. Only thing i was doing is installing updates for Brave

Any ideas / suggestions?

Sorry for the delay @BravBugRep. I don’t recall seeing your topic to this point and I’m guessing it just somehow slid under the radar in general. Let me tag in @Mattches and @steeven to see if either can try to look into this.

In the meanwhile, I am wondering if you can also just check out some of the more common troubleshooting steps and make sure none of them make a difference. More particularly new profile and testing on other release channels.

@BravBugRep,
Thank you for reporting. The issue you linked does seem like the same one you’re experiencing. I’m going to go ahead and add this report to the Github thread and ping a couple of folks internally to see if we can get eyes on it.

Thanks. Yeah i was linking issue that have same subject i was talking about, but still it’s kinda different. Thank you for reply!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.