Created attachment 873808 [details] emerge --info Chrome was working fine until I did a routine system update a few days ago, now it barfs with: $ google-chrome-stable [18144:18144:1101/170842.161527:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying [18144:18144:1101/170842.161551:ERROR:kwallet_dbus.cc(112)] Error contacting kwalletd5 (isEnabled) [18144:18144:1101/170842.161726:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.klauncher was not provided by any .service files [18144:18144:1101/170842.161733:ERROR:kwallet_dbus.cc(81)] Error contacting klauncher to start kwalletd5 [18144:18144:1101/170842.319327:ERROR:object_proxy.cc(577)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying [18144:18144:1101/170842.319342:ERROR:kwallet_dbus.cc(503)] Error contacting kwalletd5 (close) [18144:18171:1101/170842.335229:ERROR:token_service_table.cc(135)] Failed to decrypt token for service AccountId-114006544968779005866 [18144:18144:1101/170842.472970:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=256 [18144:18144:1101/170842.696636:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=256 [18144:18144:1101/170842.870773:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=256 [18144:18144:1101/170842.989040:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=256 [18144:18144:1101/170843.109009:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=256 [18144:18144:1101/170843.228790:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=256 [18144:18144:1101/170843.333287:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=256 [18144:18144:1101/170843.439629:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=256 [18144:18144:1101/170843.526258:ERROR:gpu_process_host.cc(990)] GPU process exited unexpectedly: exit_code=256 [18144:18144:1101/170843.526271:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye. [1101/170843.531218:ERROR:elf_dynamic_array_reader.h(64)] tag not found [1101/170843.531290:ERROR:elf_dynamic_array_reader.h(64)] tag not found [1101/170843.531635:ERROR:elf_dynamic_array_reader.h(64)] tag not found [1101/170843.532014:ERROR:elf_dynamic_array_reader.h(64)] tag not found [1101/170843.532997:ERROR:elf_dynamic_array_reader.h(64)] tag not found [1101/170843.533022:ERROR:elf_dynamic_array_reader.h(64)] tag not found [1101/170843.533184:ERROR:elf_dynamic_array_reader.h(64)] tag not found [1101/170843.533282:ERROR:elf_dynamic_array_reader.h(64)] tag not found Trace/breakpoint trap Pretty sure the kwalletd stuff is irrelevant, it said that when it worked fine as well. Any hints on debugging why exactly it's choking would be much appreciated I didn't have much luck with gdb as it seemed to make chrome deadlock with a useless backtrace before even trying to show a window. I've tried googling around, but didn't find anything that matched this issue - although there were some vaguely similar ones for Wayland and Electron. I'm using Xorg on a RTX3070 with nvidia-drivers-535.113.01, and KDE desktop - and other GPU-using apps work just fine. $ emerge -pv1O google-chrome [ebuild R ] www-client/google-chrome-118.0.5993.117::gentoo USE="qt5 -qt6 (-selinux)" L10N="-af -am -ar -bg -bn -ca -cs -da -de -el en-GB -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -ur -vi zh-CN -zh-TW" 0 KiB
I don't really have any idea what the issue could be here, and google-chrome is pretty impossible to debug without access to the symbols that Google keeps. You might try running it with "strace -f" to see what it's doing at the time of the failure.
I put the zstd-compressed strace log on wetransfer because it was 42MB uncompressed and no pastebin would accept it; https://we.tl/t-YFyBYgRmzF I had a look myself, but nothing jumps out - only curiosity I can spot in that region is EPERM failures on /usr/lib64/gconv/gconv-modules despite the fact I can read this file just fine, some weird sandbox thing perhaps? The error comes from pid=4711 but before that it just tries to do some I/O on socket fd=10 and reads some stuff from /proc/4951/stat on fd=71 - but I can't find where in the log socket fd=10 is created, let alone what it connects to
After another routine system update which included google-chrome-119.0.6045.105, this issue no longer occurs. Guess that means it's time to close the bug even though none of us know what caused it
