git ver r1776.d014394 sfwbar core dump, When I emptied the pcmanfm-qt trash can

[knm100]

Sometimes, git ver r1776.d014394 sfwbar core dump, When I emptied the pcmanfm-qt trash can
please see the coredump file
coredump.txt

[knm100]

The steps to reproduce this issue are:

1. Reinstall or update the sfwbar (don't logout the session or restart the sfwbar)
2. empty the pcmanfm-qt trash can

[LBCrion]

Can you please check if this still happens in the latest git version?

[artix-arist]

On the latest commit I just had a crash while using the volume widget.
Also, since some commit early this week the volume widget shows a large number of audio devices, all in identical pairs of 2.
I'm not not sure this is related; if needed I can create a separate issue for this.

[LBCrion]

Can you get a backtrace of the crash by chance?

…

On Fri, 17 Jan 2025, 09:40 artix-arist, ***@***.***> wrote: On the latest commit I just had a crash while using the volume widget. Also, since some commit early this week the volume widget shows a large number of audio devices, all in identical pairs of 2. I'm not not sure this is related; if needed I can create a separate issue for this. — Reply to this email directly, view it on GitHub <#319 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHPFFE7WFXTD62BJD7XJ3D2LDF2BAVCNFSM6AAAAABVGVBHDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJXHAZDIMZZGM> . You are receiving this because you commented.Message ID: ***@***.***>

[artix-arist]

So far I have not been able to reprocude the crash.

[LBCrion]

Can you please try to update to the latest git? I think I found one bit of code that could trigger a segfault. If you go get a segfault, a backtrace would be very helpful. For the volume widget duplication - are you using pulse or alsa? I haven't seen this happen on my system (pipewire-pulse), so may need help tracking the issue down.

…

On Fri, Jan 17, 2025 at 3:48 PM artix-arist ***@***.***> wrote: So far I have not been able to reprocude the crash. — Reply to this email directly, view it on GitHub <#319 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHPFFCZ6UN4VITONCOF3KL2LEQ3LAVCNFSM6AAAAABVGVBHDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJYGY2TAMRXGI> . You are receiving this because you commented.Message ID: ***@***.***>

[artix-arist]

This is the way to reproduce the crash - it might be related to using pipewire AND the multiple abnormal sound devices shown in the volume widget :

• start a browser and play some media with audio
• open the sfwbar volume widget; and let its popup stay open
• close the browser that is playing audio

sfwbar then crashes with this being the last part of the debug output:

22:00:11.91 expr: '(null)' = 'audio-volume-muted', vstate: 1
22:00:11.91 scanner: $xvolumemutedicon = audio-volume-muted (vstate: 1)
22:00:11.91 expr: '(null)' = 'audio-volume-medium', vstate: 1
22:00:11.91 expr: '(null)' = 'Chromium', vstate: 1
22:00:11.91 expr: '(null)' = 'checkbox', vstate: 1
22:00:11.91 expr: '(null)' = 'hidden', vstate: 1
22:00:11.91 expr: '(null)' = 'volume_client_menu', vstate: 1
22:00:11.91 expr: '(null)' = '0.54998779296875', vstate: 1
22:00:11.91 expr: '(null)' = '0.54998779296875', vstate: 1
22:00:11.91 image: kitty @ 28 x 28
22:00:11.91 image: chromium @ 28 x 28
22:00:11.91 foreign toplevel state for 0x5a2c1d210b40: 
22:00:11.91 trigger: 'window_focus'
22:00:11.91 foreign toplevel state for 0x5a2c1cfb3b70: Activated, 
zsh: segmentation fault  sfwbar -d

About the multiple sound devices, which could very wel be related to the crashing issue; these are displayed after clicking on the right hand side hamburger menu for the clients part at the bottom.

Previously these were shown, exactly the same as in the pwvuvontrol program:
Plantronic Headset
Internal Audio

Currently these are shown:
PipeWire
PipeWire
@SINKDESC@
@SINKDESC@
@SINKDESC@
HDA Intel PCH
HDA Intel PCH
HDA Intel PCH
HDA Intel PCH
HDA Intel PCH
HDA Intel PCH
HDA Intel PCH
HDA Intel PCH
Plantronic Headset
Internal Audio

[LBCrion]

Ok. The multiple menu items should be fixed now. The crash I suspect may have been an issue mentioned in #314. It should also be fixed. Please let me know if you still see it.

…

On Fri, 17 Jan 2025, 21:20 artix-arist, ***@***.***> wrote: This is the way to reproduce the crash - it might be related to using pipewire AND the multiple abnormal sound devices shown in the volume widget : - start a browser and play some media with audio - open the sfwbar volume widget; and let its popup stay open - close the browser that is playing audio sfwbar then crashes with this being the last part of the debug output: 22:00:11.91 expr: '(null)' = 'audio-volume-muted', vstate: 1 22:00:11.91 scanner: $xvolumemutedicon = audio-volume-muted (vstate: 1) 22:00:11.91 expr: '(null)' = 'audio-volume-medium', vstate: 1 22:00:11.91 expr: '(null)' = 'Chromium', vstate: 1 22:00:11.91 expr: '(null)' = 'checkbox', vstate: 1 22:00:11.91 expr: '(null)' = 'hidden', vstate: 1 22:00:11.91 expr: '(null)' = 'volume_client_menu', vstate: 1 22:00:11.91 expr: '(null)' = '0.54998779296875', vstate: 1 22:00:11.91 expr: '(null)' = '0.54998779296875', vstate: 1 22:00:11.91 image: kitty @ 28 x 28 22:00:11.91 image: chromium @ 28 x 28 22:00:11.91 foreign toplevel state for 0x5a2c1d210b40: 22:00:11.91 trigger: 'window_focus' 22:00:11.91 foreign toplevel state for 0x5a2c1cfb3b70: Activated, zsh: segmentation fault sfwbar -d About the multiple sound devices, which could very wel be related to the crashing issue; these are displayed after clicking on the right hand side hamburger menu for the clients part at the bottom. Previously these were shown, exactly the same as in the pwvuvontrol program: Plantronic Headset Internal Audio Currently these are shown: PipeWire PipeWire @SINKDESC@ @SINKDESC@ @SINKDESC@ HDA Intel PCH HDA Intel PCH HDA Intel PCH HDA Intel PCH HDA Intel PCH HDA Intel PCH HDA Intel PCH HDA Intel PCH Plantronic Headset Internal Audio — Reply to this email directly, view it on GitHub <#319 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASHPFFG7X6GBOPQVC47Y6ID2LFX2PAVCNFSM6AAAAABVGVBHDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJZGIZTMMZUGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[artix-arist]

A build from the latest commit shows that both issues have been fixed:

• the sfwbar crash no longer reproduces
• the list of displayed audio devices is correct now

Thank you very much!

FYI, I have added sfwbar to the official package repository of Artix Linux a few weeks ago, so you might want to add this to the Installation section of Readme.md:

Artix Linux: sudo pacman -Sy sfwbar

artist