[SOLVED] DWM logs showing errors in browser

Succulent of your garden · 2025-01-14 14:14:36

Hi

I was cheking my DWM logs and see these errors in brave browser:

Child process initialized in 67.77 ms
[6:25:0114/110444.906183:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/firejail/mnt/dbus/system: Permission denied
[6:31:0114/110444.934881:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/firejail/mnt/dbus/system: Permission denied
[6:31:0114/110444.934915:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/firejail/mnt/dbus/system: Permission denied
[6:6:0114/110444.947814:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[6:6:0114/110444.947827:ERROR:kwallet_dbus.cc(117)] Error contacting kwalletd6 (isEnabled)
[6:6:0114/110444.947855:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[6:6:0114/110444.947857:ERROR:kwallet_dbus.cc(86)] Error contacting klauncher to start kwalletd6
[6:6:0114/110444.947879:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[6:6:0114/110444.947881:ERROR:kwallet_dbus.cc(412)] Error contacting kwalletd6 (close)
[6:6:0114/110444.947980:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[6:6:0114/110444.947982:ERROR:kwallet_dbus.cc(117)] Error contacting kwalletd5 (isEnabled)
[6:6:0114/110444.948009:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[6:6:0114/110444.948011:ERROR:kwallet_dbus.cc(86)] Error contacting klauncher to start kwalletd5
[6:6:0114/110444.948029:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[6:6:0114/110444.948031:ERROR:kwallet_dbus.cc(412)] Error contacting kwalletd5 (close)
[6:6:0114/110444.948111:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[6:6:0114/110444.948113:ERROR:kwallet_dbus.cc(117)] Error contacting kwalletd (isEnabled)
[6:6:0114/110444.948135:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[6:6:0114/110444.948137:ERROR:kwallet_dbus.cc(86)] Error contacting klauncher to start kwalletd
[6:6:0114/110444.948155:ERROR:object_proxy.cc(576)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[6:6:0114/110444.948157:ERROR:kwallet_dbus.cc(412)] Error contacting kwalletd (close)
[6:115:0114/110445.016977:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/firejail/mnt/dbus/system: Permission denied
[6:115:0114/110445.017011:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/firejail/mnt/dbus/system: Permission denied
[6:115:0114/110445.017043:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/firejail/mnt/dbus/system: Permission denied
[6:115:0114/110445.017060:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/firejail/mnt/dbus/system: Permission denied
[6:115:0114/110445.017085:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/firejail/mnt/dbus/system: Permission denied

I'm worried about the dbus errors, I'm using the application with firejail. Since the browser shows this error, maybe I need to fix it. Can anyone help me in understand what's going on ? Brave launch and works well in gui.

Also the Kwallet error is wierd, since I launch the application with the flag --store-password=basic , so I'm not sure why brave is complaining with it.

EDIT: BTW, here is my .xinitrc file https://paste.ofcode.org/zrRnFXfwZPMmbAeiEsThVq

Last edited by Succulent of your garden (2025-01-19 17:57:30)

seth · 2025-01-15 14:56:22

kwallet looks like it's trying to activate via a dbu trigger and other than that brave deosn't seem to have access to the system bus, that's not a problem per se and proably due to the firejail profile.
Google has "Failed to connect to socket /run/firejail/mnt/dbus/system: Permission denied" for firejail and various chromium/electron based applications.

If you start to contain processes, certain things will "unexpectedly" not work (that's the whole point of containing them) and as long as they take that gracefully and function properly regardless, there isn't much to see there.

Why the browser would try to access kwallet despite the explicitly password storage mechanism is hard to tell but might be a chromium/brave bug (blatantly ignoring the switch and see what's available regardless)

Succulent of your garden · 2025-01-16 11:58:01

Hey Seth many thanks for your information.

If you delete the flag --store-password brave will start to complain to make a password storage for your crypto wallets and balblabla, but if you put the flag then brave will not comply with that. but it seems that the backend does try anyways to start the operation and fails. So I also think is a bug.

So I should not be worried for the error of the failed connection of dbus ? Since the sandboxing is happening, I also think that nothing bad could happend with that ? The application works well in any sense btw.

seth · 2025-01-16 15:52:34

So I should not be worried for the error of the failed connection of dbus ?

No, since you know where this is coming from - you could check that it's not there w/o firejail but otherwise only would have to deal w/ the firejail profile (to allow access) if and when the lack of dbus access causes any actual problems w/ the browser.

Succulent of your garden · 2025-01-18 14:03:07

Many thanks Seth for helping me. Now I'm having another error which maybe it is related to this post. Can you help me here ? https://bbs.archlinux.org/viewtopic.php … 1#p2221091

Arch Linux

#1 2025-01-14 14:14:36

[SOLVED] DWM logs showing errors in browser

#2 2025-01-15 14:56:22

Re: [SOLVED] DWM logs showing errors in browser

#3 2025-01-16 11:58:01

Re: [SOLVED] DWM logs showing errors in browser

#4 2025-01-16 15:52:34

Re: [SOLVED] DWM logs showing errors in browser

#5 2025-01-18 14:03:07

Re: [SOLVED] DWM logs showing errors in browser

Board footer