-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Segfault on running dev panel manager branch on Magpie #23
Comments
Can you |
Never mind, saw the problem almost immediately. Try latest |
Updated builds have been published in COPR. |
Progress! I saw budgie-panel for a second before getting kicked back to SDDM. If you have any recommendations on the best way to debug it while under a Wayland compositor that'd be appreciated as using
Attached is the output from journalctl: magpie-wm-9af5081-journalctl.log Linked via Proton Drive is the output file of |
It seems to be segfaulting within Server::focus_view based on the journald log, though I can't see any obvious place where a segfault would be happening. I also can't check the coredump you linked directly, as I'm not on Fedora. Does running |
Here's the
|
Description
When running budgie-desktop branch 473-implement-wayland-support-in-panel-manager, with @Conan-Kudo's budgie-wayland-session file for magpie, upon login through SDDM it will black screen and kick me back to SDDM.
I am not 100% convinced that the budgie-wm code to effectively no-op and clean exit on detecting Wayland works under magpie v1 (under kwin, libxfce4windowing does detect the windowing system as Wayland), so may be worth taking a look at too, but would be good to start getting everything else to run.
Ties into #13 with missing Wayland protocol support too.
magpie-wlr provided via Neal's copr against f0fcf8e
Magpie version
1.0~git20240413.f0fcf8e-1
Operating System
Fedora 40
Steps to reproduce the issue
Actual result
Expected result
A very broken but visible Budgie.
Additional information
No response
The text was updated successfully, but these errors were encountered: