Yes, you are right; I installed chromium-common-dbgsym alone, without chromium-dbgsym… My bad. Here are the new log extract (one ?? () did remain, yet):
Thread 1 "chromium" received signal SIGSEGV, Segmentation fault. 0x00005555576fa56b in base::ObserverList<base::RunLoop::NestingObserver, false, true, base::internal::UncheckedObserverAdapter>::AddObserver(base::RunLoop::NestingObserver*) () [?2004h[?2004l [?2004h(gdb) backtrace [?2004l #0 0x00005555576fa56b in base::ObserverList<base::RunLoop::NestingObserver, false, true, base::internal::UncheckedObserverAdapter>::AddObserver(base::RunLoop::NestingObserver*) () #1 0x0000555561094d3f in AvatarMenu::AvatarMenu(ProfileAttributesStorage*, AvatarMenuObserver*, Browser*) () #2 0x000055556109152c in DbusAppmenu::Initialize(base::OnceCallback<void (bool)>) () #3 0x000055556109410a in DbusAppmenuRegistrar::InitializeMenu(DbusAppmenu*) () #4 0x00005555610947c7 in DbusAppmenuRegistrar::OnNameOwnerChanged(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () #5 0x0000555557e90d5f in base::internal::Invoker<base::internal::BindState<base::RepeatingCallback<void (std::map<base::FilePath, base::FilePath, std::less<base::FilePath>, std::allocator<std::pair<base::FilePath const, base::FilePath> > > const&)>, std::map<base::FilePath, base::FilePath, std::less<base::FilePath>, std::allocator<std::pair<base::FilePath const, base::FilePath> > > >, void ()>::RunOnce(base::internal::BindStateBase*) () #6 0x000055555b89e998 in base::TaskAnnotator::RunTaskImpl(base::PendingTask&) () #7 0x000055555b8b83c3 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::LazyNow*) () #8 0x000055555b8b7e66 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() () #9 0x000055555b8b88a5 in non-virtual thunk to base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() () #10 0x000055555b91d70e in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) () #11 0x000055555b8b8c23 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run(bool, base::TimeDelta) () #12 0x000055555b87d74d in base::RunLoop::Run(base::Location const&) () #13 0x000055555987c997 in content::BrowserMainLoop::RunMainMessageLoop() () #14 0x000055555987e692 in content::BrowserMainRunnerImpl::Run() () #15 0x000055555987a1c4 in content::BrowserMain(content::MainFunctionParams) () #16 0x000055555ad4f2d2 in content::RunBrowserProcessMain(content::MainFunctionParams, content::ContentMainDelegate*) () #17 0x000055555ad509c6 in content::ContentMainRunnerImpl::RunBrowser(content::MainFunctionParams, bool) () #18 0x000055555ad50811 in content::ContentMainRunnerImpl::Run() () #19 0x000055555ad4dfa8 in content::RunContentProcess(content::ContentMainParams, content::ContentMainRunner*) () #20 0x000055555ad4e471 in content::ContentMain(content::ContentMainParams) () #21 0x000055555755b2f5 in ChromeMain () #22 0x00007ffff62461ca in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #23 0x00007ffff6246285 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #24 0x000055555755b021 in _start () [?2004h(gdb) thread apply all backtrace [?2004l ------- Original Message ------- Le lundi 21 août 2023 à 21:20, Andres Salomon <dilin...@queued.net> a écrit : > Looks like you're missing function names from that backtrace - do you have > chromium-dbgsym installed? > > https://wiki.debian.org/AutomaticDebugPackages > > If you're running debian stable, you'd want to add "deb > http://deb.debian.org/debian-debug/ proposed-updates-debug main" to your > /etc/apt/sources.list, and then run 'apt install chromium-dbgsym > chromium-common-dbgsym' > > And if you need to temporarily downgrade chromium because the version in > proposed-updates-debug isn't new enough, you can do something like 'apt > install chromium=115.0.5790.170-1~deb12u1 > chromium-common=115.0.5790.170-1~deb12u1' to downgrade. > > Once you have the debugging symbol packages installed, if you grab that > backtrace again it should be useable.
