Thanks for the detailed report, Franziska. I tried to reproduce it but Chromium worked alright.
In your test, did you try to open the instances of Chromium to launch at the same time or at different times? The most conspicuous error there is ---> [33865:33865:0305/102017.483089:VERBOSE1:va_stubs.cc(734)] dlopen(libva-x11.so.2) failed. [33865:33865:0305/102017.483466:VERBOSE1:va_stubs.cc(736)] dlerror() says: libva-x11.so.2: cannot open shared object file: No such file or directory <--- Does the error persist with --disable-gpu? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2009285 Title: Chromium does not start in other user account Status in chromium-browser package in Ubuntu: New Bug description: Chromium does not start for other users. I have two admin user accounts on my Ubuntu. Chromium works as expected for the "first" user, but does not start in the second user account. [Expected behavior] Chromium to start/work for all users. [What is happening] Chromium does not start for "second" user. [Steps to reproduce] * Start condition: Only one user account present on the system. * Create a second admin user account * Login as second user. * Start Chromium (doesn't matter whether from dock or terminal) * It does not start. For testing purpose I created a third user account -> same behavior. [Attachments] * syslog * snap info chromium * log from: chromium --enable-logging=stderr --v=1 lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2009285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
