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.

Sign up for GitHub

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

Jump to bottom

Waybar is crashing when disabling one of the outputs #970

Closed
MaxVerevkin opened this issue Jan 9, 2021 · 11 comments
Closed

Waybar is crashing when disabling one of the outputs #970

MaxVerevkin opened this issue Jan 9, 2021 · 11 comments
Labels
question Further information is requested

Comments

@MaxVerevkin
Copy link

MaxVerevkin commented Jan 9, 2021 •
edited
Loading

Since version 0.9.5 waybar crashes when I disable my laptop screen via swaymsg output eDP-1 toggle

Info:
Os: Void linux - musl
Wm: sway v1.5.1
@l3nkz
Copy link
Contributor

l3nkz commented Jan 13, 2021

Might be related to #969. Can you check whether master is still affected? If yes, can you share some debugging output?

@MaxVerevkin
Copy link
Author

@l3nkz Yes, master is still affected. Here is the output:

Waybar ❯❯❯ build/waybar -l trace                                                                                                                                                                    (master|✔)
[2021-01-13 17:50:15.766] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:15.767] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:15.767] [info] Resources files: /home/max/.config/waybar/config, /home/max/.config/waybar/style.css
[2021-01-13 17:50:15.778] [debug] Output detection done: HDMI-A-1 (Samsung Electric Company LF27T35 H4ZN900483)
[2021-01-13 17:50:15.778] [debug] Output detection done: eDP-1 (Unknown 0x0354 0x00000000)
[2021-01-13 17:50:15.817] [warning] module network: Unknown module: network
[2021-01-13 17:50:15.818] [warning] module tray: Unknown module: tray
[2021-01-13 17:50:15.824] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:15.824] [debug] Cmd exited with code 0
[2021-01-13 17:50:15.853] [debug] GTK widget tree:
window#waybar.background.eDP-1.:dir(ltr)
  decoration:dir(ltr)
  box.horizontal:dir(ltr)
    box.horizontal.modules-left:dir(ltr)
      widget:dir(ltr)
        box#workspaces.horizontal:dir(ltr)
      widget:dir(ltr)
        label#mode:dir(ltr)
    box.horizontal.modules-center:dir(ltr)
      widget:dir(ltr)
        label#window:dir(ltr)
    box.horizontal.modules-right:dir(ltr)
      widget:dir(ltr)
        label#pulseaudio:dir(ltr)
      widget:dir(ltr)
        label#temperature:dir(ltr)
      widget:dir(ltr)
        label#backlight:dir(ltr)
      widget:dir(ltr)
        label#battery:dir(ltr)
      widget:dir(ltr)
        label#custom-key_layout:dir(ltr)
      widget:dir(ltr)
        label#custom-clock:dir(ltr)

[2021-01-13 17:50:15.858] [warning] module network: Unknown module: network
[2021-01-13 17:50:15.859] [warning] module tray: Unknown module: tray
[2021-01-13 17:50:15.867] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:15.867] [debug] Cmd exited with code 0
[2021-01-13 17:50:15.887] [debug] Cmd exited with code 0
[2021-01-13 17:50:15.887] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:15.925] [debug] GTK widget tree:
window#waybar.background..HDMI-A-1:dir(ltr)
  decoration:dir(ltr)
  box.horizontal:dir(ltr)
    box.horizontal.modules-left:dir(ltr)
      widget:dir(ltr)
        box#workspaces.horizontal:dir(ltr)
      widget:dir(ltr)
        label#mode:dir(ltr)
    box.horizontal.modules-center:dir(ltr)
      widget:dir(ltr)
        label#window:dir(ltr)
    box.horizontal.modules-right:dir(ltr)
      widget:dir(ltr)
        label#pulseaudio:dir(ltr)
      widget:dir(ltr)
        label#temperature:dir(ltr)
      widget:dir(ltr)
        label#backlight:dir(ltr)
      widget:dir(ltr)
        label#battery:dir(ltr)
      widget:dir(ltr)
        label#custom-key_layout:dir(ltr)
      widget:dir(ltr)
        label#custom-clock:dir(ltr)

[2021-01-13 17:50:15.930] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:15.930] [debug] Cmd exited with code 0
[2021-01-13 17:50:16.006] [info] Bar configured (width: 1366, height: 27) for output: eDP-1
[2021-01-13 17:50:16.006] [info] Bar configured (width: 1920, height: 27) for output: HDMI-A-1
[2021-01-13 17:50:16.929] [debug] Cmd exited with code 0
[2021-01-13 17:50:16.929] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:16.973] [debug] Cmd exited with code 0
[2021-01-13 17:50:16.973] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:17.971] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:17.971] [debug] Cmd exited with code 0
[2021-01-13 17:50:18.016] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:18.016] [debug] Cmd exited with code 0
[2021-01-13 17:50:18.982] [debug] Output removed: Unknown 0x0354
[2021-01-13 17:50:19.129] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:19.189] [debug] Received SIGCHLD in signalThread
[2021-01-13 17:50:19.189] [debug] Cmd exited with code 0
terminate called after throwing an instance of 'std::invalid_argument'
  what():  stoi
zsh: abort      build/waybar -l trace
[134] Waybar ❯❯❯

@l3nkz
Copy link
Contributor

l3nkz commented Jan 14, 2021

Hm, this is an unrelated crash. Could you also recover a core dump? This would help debugging the problem further.

@MaxVerevkin
Copy link
Author

@l3nkz Sorry for the delay. How do I recover a core dump?

@l3nkz
Copy link
Contributor

l3nkz commented Jan 20, 2021

This depends a little bit on your distribution. If you have systemd running, there should be a binary like coredumpctl. With coredumpctl list you can view all saved coredumps. If you find the waybar binary that failed you can use coredumpctl dump -c out.core PID where PID is the showed pid of the failing process. If you don't have systemd with coredumpctl in your system. You might need to set the following before running the waybar: ulimit -c unlimited to allow an unlimited size for the core dumps and then you should find the core dump in your cwd.
You can find more informatition here.

@MaxVerevkin
Copy link
Author

Here it is: https://drive.google.com/file/d/1xLZigKmAKR2OFt-dNnNG2HxnaoZ0I8xH/view?usp=sharing

@baloo baloo mentioned this issue Feb 5, 2021
Closed
@Alexays
Copy link
Owner

Alexays commented Apr 16, 2021

@MaxVerevkin still crashing on latest version?

@Alexays Alexays added the question Further information is requested label Apr 16, 2021
@eulerfan271
Copy link

I am experiencing this same issue on the latest version (0.9.7 from the arch repos).

@MaxVerevkin
Copy link
Author

MaxVerevkin commented May 19, 2021 •
edited
Loading

@Alexays seems to work for me (Waybar v0.9.7 sway version 1.6). Oh, forgot it was crashing on void-musl. I'll update my comment when I'll be able to test it.

@minhduc0711
Copy link

I've got the same issue, but my log is a bit different (no active exception)

[2021-06-04 11:16:48.198] [info] Bar configured (width: 1920, height: 23) for output: HDMI-A-1
[2021-06-04 11:16:48.198] [info] Bar configured (width: 1536, height: 23) for output: eDP-1
[2021-06-04 11:16:48.205] [info] Bar configured (width: 1920, height: 23) for output: HDMI-A-1
[2021-06-04 11:16:54.234] [debug] Output removed: Dell Inc. DELL P2319H
[2021-06-04 11:16:54.338] [debug] Received SIGCHLD in signalThread
[2021-06-04 11:16:54.338] [debug] Received SIGCHLD in signalThread
[2021-06-04 11:16:54.338] [debug] Received SIGCHLD in signalThread
terminate called without an active exception
[1]    209358 abort (core dumped)  waybar --log-level debug

@Alexays
Copy link
Owner

Alexays commented Jun 4, 2021

Dups of #1065

@Alexays Alexays closed this as completed Jun 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@l3nkz @eulerfan271 @Alexays @minhduc0711 @MaxVerevkin