You are not logged in.
Since recent updates, chromium crashes with SIGILL when I try to share my screen or a tab:
Program terminated with signal SIGILL, Illegal instruction.
#0 0x00005d9a0f7f0fac in webrtc::SharedScreenCastStreamPrivate::StartScreenCastStream(unsigned int, int, unsigned int, unsigned int, bool, webrtc::DesktopCapturer::Callback*) ()
[Current thread is 1 (Thread 0x76c77b20c400 (LWP 4270))]
(gdb) bt
#0 0x00005d9a0f7f0fac in webrtc::SharedScreenCastStreamPrivate::StartScreenCastStream(unsigned int, int, unsigned int, unsigned int, bool, webrtc::DesktopCapturer::Callback*) ()
#1 0x00005d9a0f7eb274 in webrtc::BaseCapturerPipeWire::OnScreenCastRequestResult(webrtc::xdg_portal::RequestResponse, unsigned int, int) ()
#2 0x00005d9a0f7ec3dc in webrtc::ScreenCastPortal::OnPortalDone(webrtc::xdg_portal::RequestResponse) ()
#3 0x00005d9a0f7ed0ac in webrtc::ScreenCastPortal::OnOpenPipeWireRemoteRequested(_GDBusProxy*, _GAsyncResult*, void*) [clone .cfi] ()
#4 0x000076c77cfa9cec in g_task_return_now (task=0x226) at ../glib/gio/gtask.c:1363
#5 0x000076c77cfadfd5 in g_task_return (type=<optimized out>, task=0x1f840b0afe40) at ../glib/gio/gtask.c:1432
#6 g_task_return (task=0x1f840b0afe40, type=<optimized out>) at ../glib/gio/gtask.c:1389
#7 0x000076c77d01b15d in reply_cb (connection=<optimized out>, res=<optimized out>, user_data=0x1f840b0afe40) at ../glib/gio/gdbusproxy.c:2557
#8 0x000076c77cfa9cec in g_task_return_now (task=0x1f840b0aea00) at ../glib/gio/gtask.c:1363
#9 0x000076c77cfadfd5 in g_task_return (type=<optimized out>, task=0x1f840b0aea00) at ../glib/gio/gtask.c:1432
#10 g_task_return (task=0x1f840b0aea00, type=<optimized out>) at ../glib/gio/gtask.c:1389
#11 0x000076c77d009de3 in g_dbus_connection_call_done (source=<optimized out>, result=<optimized out>, user_data=0x1f840b0aea00) at ../glib/gio/gdbusconnection.c:6489
#12 0x000076c77cfa9cec in g_task_return_now (task=0x1f8408eac240) at ../glib/gio/gtask.c:1363
#13 0x000076c77cfa9d35 in complete_in_idle_cb (task=0x1f8408eac240) at ../glib/gio/gtask.c:1377
#14 0x000076c77d444104 in g_main_dispatch (context=0x1f80000d0380) at ../glib/glib/gmain.c:3398
#15 0x000076c77d4a7d57 in g_main_context_dispatch_unlocked (context=0x1f80000d0380) at ../glib/glib/gmain.c:4249
#16 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x1f80000d0380, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4314
#17 0x000076c77d443535 in g_main_context_iteration (context=0x1f80000d0380, may_block=1) at ../glib/glib/gmain.c:4379
#18 0x00005d9a0ea9e062 in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) ()
#19 0x00005d9a08b0fffe in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run(bool, base::TimeDelta) ()
#20 0x00005d9a08d07d5d in base::RunLoop::Run(base::Location const&) ()
#21 0x00005d9a08d0a170 in content::BrowserMainLoop::RunMainMessageLoop() ()
#22 0x00005d9a08d0a0a3 in content::BrowserMainRunnerImpl::Run() ()
#23 0x00005d9a0c8dc288 in content::BrowserMain(content::MainFunctionParams) ()
#24 0x00005d9a0dee04d2 in content::ContentMainRunnerImpl::Run() ()
#25 0x00005d9a07a03703 in content::ContentMain(content::ContentMainParams) ()
#26 0x00005d9a07a043d3 in ChromeMain ()
#27 0x000076c77ba81488 in __libc_start_call_main (main=main@entry=0x5d9a07a04180 <main>, argc=argc@entry=2, argv=argv@entry=0x7fffdf6ea9b8) at ../sysdeps/nptl/libc_start_call_main.h:58
#28 0x000076c77ba8154c in __libc_start_main_impl (main=0x5d9a07a04180 <main>, argc=2, argv=0x7fffdf6ea9b8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffdf6ea9a8)
at ../csu/libc-start.c:360
#29 0x00005d9a0a958305 in _start ()
Does anyone encounter a similar issue? Is it a bug in chromium or could it be a configuration / environment issue. I am on KDE.
Offline
If anything a bug in the new pipewire/chromium release. Did you reboot "since update"? otherwise you might still have stale pipewire libs around. But generally speaking sigill usually means some newer cpu instruction getting compiled in that your CPU can't handle, what's your CPU?
Last edited by V1del (2025-03-13 10:36:54)
Offline
Yes, I rebooted several times. CPU is Intel Core i7-8750H.
Offline
I can confirm the same behavior on my side. After downgrading from 134.0.6998.88-1 to 134.0.6998.35-2 screen share works again.
AMD Ryzen 7 PRO 6850U with Radeon 680M
Offline
I can also confirm
extra/chromium 134.0.6998.88-1 [installed]
AMD Ryzen 5 5625U with Radeon Graphics
Last edited by simonelbaz (2025-03-13 14:54:37)
Offline
Mhm, mhm... potentially an actual chromium bug in that case? Didn't get to test yet might do so tonight after work.
Offline
Same SIGILL error here, on a laptop with Intel i7-1165g7 CPU
Downgrading Arch package from 134.0.6998.88-1 to 134.0.6998.35-2 works
Flatpak package with version 134.0.6998.88 also works without trouble
Offline
Same here - I downloaded the arch package using https://wiki.archlinux.org/title/Downgrading_packages and https://github.com/archlinux-downgrade/downgrade (first time I have ever done that - worked quite smoothly.
Wondering how niche this is, if it has been reported somewhere (or maybe that needs to happen) and if there is anything else to do apart from wait for a fix? My quick look (e.g. https://gitlab.archlinux.org/archlinux/ … e_size=20) didn't turn anything up apart from this thread.
Offline
Same problem. Downgrading also worked as a temp fix for me.
Offline
if it has been reported somewhere
I found:
- https://github.com/ungoogled-software/u … ssues/3245
- https://github.com/NixOS/nixpkgs/issues/390975
So nixos seems affected as well.
Downgrading solved the issue for me as well.
Offline
I can also confirm
extra/chromium 134.0.6998.88-1 [installed]
AMD Ryzen 5 5625U with Radeon Graphics
Hi,
Issue still present for me with: extra/chromium 134.0.6998.117-1 [installed]
Offline
I have also faced this problem. Downgrading helps.
Offline
The problem persists even with today's update 134.0.6998.165-1 and Wayland. Downgrading is still the solution.
Offline
Downgrading also works here.
Offline
Same for me on an up-to-date Arch system with Chromium v132.0.6834.159. I keep recompiling this version due to the Wayland+fractional scale blurriness regression introduced in v133, so I'm recompiling unchanged sources with new updates, and it's crashing. A few days ago (literally 2-3-5 days ago), it was fine.
Operating System: Arch Linux
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.3
Kernel Version: 6.13.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 9950X 16-Core Processor
Memory: 94.0 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 XT
Manufacturer: ASUS
Offline
It started after PipeWire was upgraded and Chromium was rebuilt using the new library headers. Downgrading PipeWire to 1:1.2.7 and rebuilding Chromium helps.
See my comment here: https://github.com/ungoogled-software/u … 2762561120
Offline