More elegant failures

[keshto]

More elegant failures

[keshto]

Note that the error is not the reason for the segfault.

@@ -1,6 +1,6 @@
-scanner {
-  SwayClient("") {}  # launch sway client to get "sway" trigger
-}
+#scanner {
+#  SwayClient("") {}  # launch sway client to get "sway" trigger
+#}
 
 # Window Placer
 placer {
@@ -45,7 +45,7 @@ layout ":start" {
 }
 
 layout ":end" {
-  include("wbar-mpd.widget")
+#  include("wbar-mpd.widget")
 #  include("wbar-bluetooth.widget")
   include("wbar-idleinhibit.widget")
   include("wbar-pulse.widget")
@@ -54,7 +54,7 @@ layout ":end" {
   include("wbar-memory.widget")
   include("wbar-temp.widget")
   include("wbar-backlight.widget")
-  include("wbar-sway-lang.widget")
+#  include("wbar-sway-lang.widget")

makes seg fault go away

[keshto]

backtrace:

Thread 1 "sfwbar" received signal SIGSEGV, Segmentation fault.
0x00007ffff73a6e10 in g_socket_connection_is_connected ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
(gdb) bt
#0  0x00007ffff73a6e10 in g_socket_connection_is_connected ()
    at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#1  0x000055555556d0e6 in client_socket_connect_cb
    (src=0x555555894d00, res=0x55555566f250, client=0x555555839d70)
    at ../src/client.c:102
#2  0x00007ffff73adc93 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#3  0x00007ffff73ae673 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007ffff73a4501 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x00007ffff73adc93 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x00007ffff73ae673 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7  0x00007ffff73933cc in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#8  0x00007ffff73adc93 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#9  0x00007ffff73adcc9 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#10 0x00007ffff71bb67f in g_main_context_dispatch ()
    at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffff71bba38 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffff71bbacc in g_main_context_iteration ()
    at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff78084e5 in gtk_main_iteration ()
    at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#14 0x00007ffff7973de5 in gtk_widget_show_now ()
    at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#15 0x000055555556a96f in css_custom_handle (widget=0x5555558a65a0)
--Type <RET> for more, q to quit, c to continue without paging--
    at ../src/css.c:40
#16 0x000055555556b195 in css_widget_cascade (widget=0x5555558a65a0, data=0x0)
    at ../src/css.c:171
#17 0x000055555556647a in activate (app=0x555555629210, data=0x0)
    at ../src/sfwbar.c:176
#18 0x00007ffff72b53b0 in g_closure_invoke ()
    at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x00007ffff72c8076 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x00007ffff72cebf5 in g_signal_emit_valist ()
    at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x00007ffff72cedbf in g_signal_emit ()
    at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x00007ffff73db438 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#23 0x00007ffff73db5c6 in g_application_run ()
    at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#24 0x0000555555566732 in main (argc=3, argv=0x7fffffffe2d8)
    at ../src/sfwbar.c:219

This is off master as of now.

[LBCrion]

Any chance you can get a backtrace of the segfault? I'll take a look at the hypr error. Is this with huprland?

…

On Mon, 8 May 2023, 14:11 Keshto, ***@***.***> wrote: Note that the error is not the reason for the segfault. @@ -1,6 +1,6 @@ -scanner { - SwayClient("") {} # launch sway client to get "sway" trigger -} +#scanner { +# SwayClient("") {} # launch sway client to get "sway" trigger +#} # Window Placer placer { @@ -45,7 +45,7 @@ layout ":start" { } layout ":end" { - include("wbar-mpd.widget") +# include("wbar-mpd.widget") # include("wbar-bluetooth.widget") include("wbar-idleinhibit.widget") include("wbar-pulse.widget") @@ -54,7 +54,7 @@ layout ":end" { include("wbar-memory.widget") include("wbar-temp.widget") include("wbar-backlight.widget") - include("wbar-sway-lang.widget") +# include("wbar-sway-lang.widget") makes seg fault go away — Reply to this email directly, view it on GitHub <#91 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHPFFHWUCKQZEOXH2FVK43XFDWJDANCNFSM6AAAAAAXZ5RZGI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[LBCrion]

Thank you! You're way ahead of me.

…

On Mon, 8 May 2023, 14:15 Keshto, ***@***.***> wrote: backtrace: Thread 1 "sfwbar" received signal SIGSEGV, Segmentation fault. 0x00007ffff73a6e10 in g_socket_connection_is_connected () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (gdb) bt #0 0x00007ffff73a6e10 in g_socket_connection_is_connected () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #1 0x000055555556d0e6 in client_socket_connect_cb (src=0x555555894d00, res=0x55555566f250, client=0x555555839d70) at ../src/client.c:102 #2 0x00007ffff73adc93 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #3 0x00007ffff73ae673 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x00007ffff73a4501 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x00007ffff73adc93 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x00007ffff73ae673 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #7 0x00007ffff73933cc in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #8 0x00007ffff73adc93 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #9 0x00007ffff73adcc9 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #10 0x00007ffff71bb67f in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x00007ffff71bba38 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x00007ffff71bbacc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x00007ffff78084e5 in gtk_main_iteration () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #14 0x00007ffff7973de5 in gtk_widget_show_now () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #15 0x000055555556a96f in css_custom_handle (widget=0x5555558a65a0) --Type <RET> for more, q to quit, c to continue without paging-- at ../src/css.c:40 #16 0x000055555556b195 in css_widget_cascade (widget=0x5555558a65a0, data=0x0) at ../src/css.c:171 #17 0x000055555556647a in activate (app=0x555555629210, data=0x0) at ../src/sfwbar.c:176 #18 0x00007ffff72b53b0 in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #19 0x00007ffff72c8076 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #20 0x00007ffff72cebf5 in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x00007ffff72cedbf in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x00007ffff73db438 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #23 0x00007ffff73db5c6 in g_application_run () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #24 0x0000555555566732 in main (argc=3, argv=0x7fffffffe2d8) at ../src/sfwbar.c:219 This is off master as of now. — Reply to this email directly, view it on GitHub <#91 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHPFFFK5KXCL25DGUE4ZFLXFDWVPANCNFSM6AAAAAAXZ5RZGI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[keshto]

backtrace already included :) no i am not running hyperland

[keshto]

I believe it has to do with include("wbar-mpd.widget")

[LBCrion]

Can you try with the latest git please? Hyprland message isn't fixed, but the segfault hopefully should be.

…

On Mon, 8 May 2023, 14:16 Keshto, ***@***.***> wrote: I believe it has to do with include("wbar-mpd.widget") — Reply to this email directly, view it on GitHub <#91 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHPFFAGZTHKAJQWMKSIIN3XFDW35ANCNFSM6AAAAAAXZ5RZGI> . You are receiving this because you commented.Message ID: ***@***.***>

[keshto]

Yay no more segfault! I think the hyper message is fine. Maybe make it more like a warning?

Closing as the segfault was the scary part (if a new user were to try to use sfwbar there should be no segfault no matter the config or their env)

[LBCrion]

Yes, it should have only reported these in debug mode. Should be fixed now.

…

On Mon, 8 May 2023, 14:45 Keshto, ***@***.***> wrote: Yay no more segfault! I think the hyper message is fine. Maybe make it more like a warning? Closing as the segfault was the scary part (if a new user were to try to use sfwbar there should be no segfault no matter the config or their env) — Reply to this email directly, view it on GitHub <#91 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHPFFCZIXWPRE2ZVEEZPVDXFD2IJANCNFSM6AAAAAAXZ5RZGI> . You are receiving this because you commented.Message ID: ***@***.***>