Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] Chromium and chromium based browsers crash at start (Read 669 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

[SOLVED] Chromium and chromium based browsers crash at start

Hi all and thanks for this great distro!  Bear with me as I am not very tech savvy  :D 
As said in the title, chromium and brave always crash a second after starting.When I start chromium from the terminal I get this message:

~$ chromium
[8029:8050:0818/174148.458939:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: Interfaccia «org.freedesktop.portal.FileChooser» inesistente
[8029:8050:0818/174148.459018:ERROR:select_file_dialog_linux_portal.cc(285)] Failed to read portal version property
Errore di segmentazione

Re: Chromium and chromium based browsers crash at start

Reply #1 –
Sounds like a dbus issue, which I know very little about.
Might want to review this thread.
Supercalifragilisticexpialidocious

Re: Chromium and chromium based browsers crash at start

Reply #2 –
Thanks for the reply, I already found that thread, unfortunately it doesn't seem to be the same problem. To be sure I checked that discussion (about a notification daemon issue)  and it was already setup correctly in my case.
I think it has something to do with the way I start dbus, as I run artix with dinit,  I am not really sure...
From my understanding I need to run dbus as a system service (done with dinitctl as root) and as a user service, which I had some trouble setting up but I thought it worked fine in the end.  To run dbus as user I did the following steps:

1. install dbus dbus-dinit dbus-dinit-user
2. install turnstile turnstile-dinit
3. follow these steps https://github.com/davmac314/dinit/blob/master/doc/getting_started.md
4. enable turnstiled as a system service with root

Right now I have these user services running and working:

 dinitctl list
[
  •      ] boot
    • [{+}     ] system
    [{+}     ] dbus (pid: 1364)
    [{+}     ] wireplumber (pid: 1370)
    [{+}     ] pipewire (pid: 1368)
    [{+}     ] pipewire-pulse (pid: 1369)

     ps aux | grep dbus
    dbus      1016  0.0  0.0   4984  3428 ?        Ss   00:20   0:00 /usr/bin/dbus-daemon --system --nofork --nopidfile --print-address=4
    root      1030  0.0  0.3 414372 13124 ?        Ssl  00:20   0:00 /usr/bin/thermald --no-daemon --dbus-enable
    sddm      1285  0.0  0.0   5356  1792 ?        S    00:21   0:00 dbus-launch --autolaunch 69d3c7c82df64c52a4761c638b5a4025 --binary-syntax --close-stderr
    sddm      1286  0.0  0.0   4376  1804 ?        Ss   00:21   0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session
    prova     1364  0.1  0.0   5248  3892 ?        Ss   00:21   0:04 dbus-daemon --session --address=unix:path=/run/user/1001/bus --print-address=4
    prova     1577  0.0  0.0   4504  3328 ?        S    00:21   0:00 /bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/1001/at-spi/bus_0
    prova     3886  0.0  0.0   7460  2176 pts/0    S+   01:20   0:00 grep --color dbus

Re: Chromium and chromium based browsers crash at start

Reply #3 –
The error is misleading, as it can be shown on instances where chromium starts and works normally.

Do you perhaps have any of these env vars set?
QT_QPA_PLATFORMTHEME
QT_PLATFORM_PLUGIN
If so, unset them and test again.

artist

Re: Chromium and chromium based browsers crash at start

Reply #4 –
I made sure to unset those vars but I still get this message and chromium crashes almost immediately

[4628:4647:0819/153502.067340:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: Interfaccia «org.freedesktop.portal.FileChooser» inesistente
[4628:4647:0819/153502.068208:ERROR:select_file_dialog_linux_portal.cc(285)] Failed to read portal version property
Errore di segmentazione

[prova ~]$ env | grep QT
QT_IM_MODULE=fcitx

I get the same error both in XFCE and LXQT.  As the error mentions desktop portals I checked and have these one installed:

xdg-desktop-portal
xdg-desktop-portal-gtk
xdg-desktop-portal-lxqt
xdg-desktop-portal-xapp



Re: Chromium and chromium based browsers crash at start

Reply #5 –
This is the only relevant part of the error you get:

 segmentation fault

Please try with a different user, or at least a new chromium profile

artist

Re: Chromium and chromium based browsers crash at start

Reply #6 –
I tried with a new user and while I get some error, chromium seems to work fine.
About creating a new chromium profile, I deleted  ".config/chromium" and ".cache/chromium", but it didn't work. Maybe there's something else  in my home folder that causes the problem, as also brave browser behaves in the same way.

Re: Chromium and chromium based browsers crash at start

Reply #7 –
Make sure to check theming; often the cause can be found there.

artist

Re: Chromium and chromium based browsers crash at start

Reply #8 –
Thanks for the reply, I will check themes, but frankly I can't remember I did apply any theme... I tried to delete some gtk config files in my home directory and  testing on i3wm, no idea where else to look,   I think I'll make a new user.

Re: Chromium and chromium based browsers crash at start

Reply #9 –
The mesa shader cache in .cache has caused a problem in the past after mesa version updates, there's a qt shader cache in there too, being graphics related stuff it might cause a crash.

Re: Chromium and chromium based browsers crash at start

Reply #10 –
Actually I managed to solve this without having to create a new user!  :) 
The culprit was probably the '.local/share/icons' folder, I don't really get how it had anything to do with btw, now chromium works again, thanks for the help.