Skip to content
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

swayfire_deco causes Wayfire to crush #46

Open
struthio opened this issue Feb 28, 2022 · 1 comment
Open

swayfire_deco causes Wayfire to crush #46

struthio opened this issue Feb 28, 2022 · 1 comment

Comments

@struthio
Copy link

hi,

I tried swayfire as a possible replacement for sway. I tries to load both modules, but when I add swayfire_deco in wayfire.ini, wayfire does not start.
I tried to load it dynamically from wcm and while wayfire session crushed.

DD 28-02-22 08:13:07.126 - [src/output/plugin-loader.cpp:135] Loaded plugin /usr/lib/wayfire/libswayfire-deco.so DD 28-02-22 08:13:07.126 - [src/deco/deco.cpp:529] === deco init === DD 28-02-22 08:13:07.126 - [src/output/output.cpp:432] output DP-1: activate plugin swayfire-deco DD 28-02-22 08:13:07.126 - [src/deco/deco.cpp:417] Decorating split-node-9 EE 28-02-22 08:13:07.126 - [src/main.cpp:132] Fatal error: Segmentation fault EE 28-02-22 08:13:07.144 - #1 wf::print_trace(bool) ??:? EE 28-02-22 08:13:07.158 - #2 __restore_rt libc_sigaction.c:? EE 28-02-22 08:13:07.170 - #3 set_outer_corners(nonstd::observer_ptr<INode>, unsigned char) ??:? EE 28-02-22 08:13:07.181 - #4 set_outer_corners(nonstd::observer_ptr<INode>, unsigned char) ??:? EE 28-02-22 08:13:07.195 - #5 wf::signal_connection_t::emit(wf::signal_data_t*) ??:? EE 28-02-22 08:13:07.210 - #6 wf::compositor_core_impl_t::add_view(std::unique_ptr<wf::view_interface_t, std::default_delete<wf::view_interface_t> >) ??:? EE 28-02-22 08:13:07.221 - #7 SwayfireDeco::decorate_node(nonstd::observer_ptr<INode>) ??:? EE 28-02-22 08:13:07.232 - #8 SplitNode::for_each_node(std::function<void (nonstd::observer_ptr<INode>)> const&) ??:? EE 28-02-22 08:13:07.244 - #9 non-virtual thunk to DecorationSurface::get_offset() ??:? EE 28-02-22 08:13:07.256 - #10 Workspaces::for_each(std::function<void (nonstd::observer_ptr<Workspace>)> const&) ??:? EE 28-02-22 08:13:07.267 - #11 SwayfireDeco::swf_init() ??:? EE 28-02-22 08:13:07.281 - #12 wf::signal_connection_t::emit(wf::signal_data_t*) ??:? EE 28-02-22 08:13:07.294 - #13 SwayfirePlugin::init() ??:? EE 28-02-22 08:13:07.309 - #14 plugin_manager::reload_dynamic_plugins() ??:? EE 28-02-22 08:13:07.320 - #15 wl_event_loop_dispatch_idle ??:? EE 28-02-22 08:13:07.332 - #16 wl_event_loop_dispatch ??:? EE 28-02-22 08:13:07.343 - #17 wl_display_run ??:? EE 28-02-22 08:13:07.359 - #18 main ??:? EE 28-02-22 08:13:07.373 - #19 __libc_start_call_main libc-start.c:? EE 28-02-22 08:13:07.386 - #20 __libc_start_main_alias_2 :? EE 28-02-22 08:13:07.401 - #21 _start ??:?

Swayfire package is built from https://aur.archlinux.org/packages/swayfire-git so it should be rather fresh,

@Javyre
Copy link
Owner

Javyre commented Mar 9, 2022

A good first step would be for you to clone+compile swayfire manually with debug symbols on and reproduce the bug. (see readme + --buildtype=debug)
That way the error message could point to specific lines in code instead of ??.

I haven't been very active on swayfire in a while but as far as I know there shouldn't be any breaking changes in wayfire master since my last commit here so everything should work and initialize fine.

Also make sure that you are using wayfire master as that is what swayfire targets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants