You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quickshell crashed with SIGSEGV immediately after being (re)launched to replace a running instance that was in the middle of teardown, following a plugin-directory reload storm.
Stack (symbolized, thread 1, only thread present): QQmlContextData::initPropertyNames() ← QV4::QQmlContextWrapper::getPropertyAndBase ← resolveQmlContextPropertyLookupGetter ← Runtime::CallQmlContextPropertyLookup::call, with JS JIT frames (Null pipewire default metadata property update causes crash #6) beneath, dispatched from QObject::event → sendPostedEvents → glib main loop. Crash during initial component/context setup, ~1s after start.
Trigger: the shell was relaunched while the previous process had not yet exited. The new instance's log shows it discovered ~17 existing instances for the same Shell ID, then created the PID symlink by-pid/151239 pointing at itself — i.e., it took over the identity of a still-live shell. The recorded signal is SI_TKILL: quickshell's own crash handler re-raised the SIGSEGV to produce the dump, so the original fault address is not in the core.
Attached: report.txt
Reproduction path (system-dependent): while the shell is running, rapidly rewrite/delete files in a watched plugin directory so the reload logic spawns a replacement Quickshell process before the old one finishes exiting. First occurrence observed; crash handler behaved correctly.
What caused the crash
Quickshell crashed with SIGSEGV immediately after being (re)launched to replace a running instance that was in the middle of teardown, following a plugin-directory reload storm.
Reproduction path (system-dependent): while the shell is running, rapidly rewrite/delete files in a watched plugin directory so the reload logic spawns a replacement Quickshell process before the old one finishes exiting. First occurrence observed; crash handler behaved correctly.
Report file
report.txt
Configuration
No response
Backtrace
No response