Waybar Crashing #101

Closed
opened 2022-02-21 21:08:09 +01:00 by frap129 · 8 comments

Waybar installed from ALHP's community-x86-64-v3 is crashing with the error:

** (waybar:41188): ERROR **: 15:09:48.700:
unhandled exception (type std::exception) in signal handler:
what: Type is not convertible to string

This crash doesn't seem to be ALHP related, as it also happens with waybar-git from the AUR and is reported in a couple issues upstream: https://github.com/Alexays/Waybar/issues?q=is%3Aissue+is%3Aopen+Type+is+not+convertible.

I'm hoping waybar can be removed from ALHP until this issue is resolved upstream, as the build in Arch's community repo does not exhibit the same crash.

Waybar installed from ALHP's community-x86-64-v3 is crashing with the error: ``` ** (waybar:41188): ERROR **: 15:09:48.700: unhandled exception (type std::exception) in signal handler: what: Type is not convertible to string ``` This crash doesn't seem to be ALHP related, as it also happens with waybar-git from the AUR and is reported in a couple issues upstream: https://github.com/Alexays/Waybar/issues?q=is%3Aissue+is%3Aopen+Type+is+not+convertible. I'm hoping waybar can be removed from ALHP until this issue is resolved upstream, as the build in Arch's community repo does not exhibit the same crash.
frap129 changed title from Waybar coredump to Waybar Crashing 2022-02-21 21:14:36 +01:00
frap129 reopened this issue 2022-02-21 21:17:20 +01:00
Owner

Are you sure this is not happening with the official build? In one of the issues you linked, someone seems to have it with the official build as well.

Are you sure this is not happening with the official build? In one of the issues you linked, someone seems to have it with the official build as well.
Author

Are you sure this is not happening with the official build? In one of the issues you linked, someone seems to have it with the official build as well.

The issues I linked (at least, the one that had multiple user reports) describe the issue as being intermitent and inconsistent, which I can confirm happens to me as well. However, the build on alhp (and selfbuilt waybar-git from aur) crash at start 100% of the time, regardless of the config given (tested my config and the default config).

I took a look at the source itself and it uses a compiler flag to enable experimental c++ features. The last time the official package was built was Jan 10th, so I'm wondering if this got broken with arch's recent toolchain updates.

> Are you sure this is not happening with the official build? In one of the issues you linked, someone seems to have it with the official build as well. The issues I linked (at least, the one that had multiple user reports) describe the issue as being intermitent and inconsistent, which I can confirm happens to me as well. However, the build on alhp (and selfbuilt waybar-git from aur) crash at start 100% of the time, regardless of the config given (tested my config and the default config). I took a look at the source itself and it uses a compiler flag to enable experimental c++ features. The last time the official package was built was Jan 10th, so I'm wondering if this got broken with arch's recent toolchain updates.
Owner

Fair enough, I have blacklisted it. I think we can leave this open until its resolved, then we can re-add waybar.

Fair enough, I have blacklisted it. I think we can leave this open until its resolved, then we can re-add waybar.
anonfunc added the
build-failure
label 2022-02-22 07:48:55 +01:00
Author

Fair enough. I have blacklisted it. I think we can leave this open until its resolved, then we can re-add waybar.

Awesome, thanks!

> Fair enough. I have blacklisted it. I think we can leave this open until its resolved, then we can re-add waybar. Awesome, thanks!
anonfunc added the
blocked upstream
label 2022-02-22 20:58:01 +01:00
Owner

Waybar just got bumped to waybar 0.9.9-2. If the problem really lies with newer gcc versions, the official version should show these problems now as well.

Waybar just got bumped to `waybar 0.9.9-2`. If the problem really lies with newer gcc versions, the official version should show these problems now as well.
Author

@anonfunc I noticed that and updated, and it worked fine without crashing. I found that odd, so I built waybar from source (again, waybar-git from AUR), and that also works now. Could have been another dependency that was broken, I'm not exactly sure. But since the source built version works now, building it in ALHP is proably fine as well.

@anonfunc I noticed that and updated, and it worked fine without crashing. I found that odd, so I built waybar from source (again, waybar-git from AUR), and that also works now. Could have been another dependency that was broken, I'm not exactly sure. But since the source built version works now, building it in ALHP is proably fine as well.
Owner

Please try waybar 0.9.9-2.1 if you find the time.

Please try `waybar 0.9.9-2.1` if you find the time.
anonfunc removed the
blocked upstream
label 2022-02-26 07:50:40 +01:00
Author

Please try waybar 0.9.9-2.1 if you find the time.

Been using it for about 6 hours now, no issues at all. Seems solved to me, thanks!

> Please try `waybar 0.9.9-2.1` if you find the time. Been using it for about 6 hours now, no issues at all. Seems solved to me, thanks!
Sign in to join this conversation.
No description provided.