[MCL-11237] "Browse" button doesn't work on Linux (Kubuntu)

Equipment used :

My computer running on Linux - Kubuntu 18.04.2 (with KDE)

Minecraft Launcher (official .deb) version 2.1.5410

The bug :

When you want to create/edit a profile, the browse button in the profile settings doesn't work. It simply change color, but it does nothing else (as shown in the screenshot above).

[media]

What is expected :

Open the file directory, I guess.

How to reproduce :

Start the launcher on a computer that runs Kubuntu
Create a profile
Try to use the "Browse" button

Linked issues

relates to 1

MCL-11593 "Browse" button not working Resolved

Attachments

Comments 2

migrated 2019-06-28T13:52:10Z

I have also observed this problem on the current release of Ubuntu. I could fill in the text field manually, but the Browse button did not work at all. Neither did the one for Java version.

Doing a bit of research, I get these error messages when I launch from a gterm and press the 'Browse' button:

[0628/094825.714664:ERROR:sandbox_linux.cc(346)] InitializeSandbox() called with multiple threads in process gpu-process.
[0628/094825.720596:ERROR:cache_util.cc(134)] Unable to move cache folder GPUCache to old_GPUCache_000
[0628/094825.720611:ERROR:disk_cache.cc(172)] Unable to create cache
[0628/094825.720616:ERROR:shader_disk_cache.cc(601)] Shader Cache Creation failed: -2
[0628/094834.677028:WARNING:file_dialog_manager.cc(317)] No file dialog runner available for this platform
[0628/094838.769184:WARNING:x11_util.cc(1349)] X error received: serial 1189, error_code 9 (BadDrawable (invalid Pixmap or Window parameter)), request_code 155, minor_code 7 (DRI2GetBuffersWithFormat	)
[0628/094838.772231:WARNING:x11_util.cc(1349)] X error received: serial 1221, error_code 185 (GLXBadWindow), request_code 156, minor_code 32 (X_GLXDestroyWindow)
[0628/094838.772279:WARNING:x11_util.cc(1349)] X error received: serial 1224, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)

migrated 2019-10-29T10:32:08Z

Should be fixed in the current beta