Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#61673 - [dmenu] 4.9-1 segfaults immediately on user input

Attached to Project: Community Packages
Opened by fwfull (fluffywaffles) - Friday, 08 February 2019, 01:39 GMT
Last edited by Jonas Witschel (diabonas) - Thursday, 11 November 2021, 10:36 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 8
Private No


dmenu 4.9-1 segfaults once I start typing in the popup. Kernel 4.20.6, running bspwm 0.9.5, st 0.8.1, X server 1.20.3, nothing else.

Downgrade to 4.8 fixes issue.
This task depends upon

Closed by  Jonas Witschel (diabonas)
Thursday, 11 November 2021, 10:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 5.0. (linked commit is included in that release).
Comment by Levente Polyak (anthraxx) - Friday, 08 February 2019, 01:47 GMT
would you maybe actually provide anything useful in this bugreport? like some strace, ltrace, ldd or coredump output?
Comment by fwfull (fluffywaffles) - Friday, 08 February 2019, 01:50 GMT
Apologies for slow uptake on the bug report - never used strace before. You must allow for some innocent ignorance on my part. :)


echo 'a\nb\nc' | strace dmenu > strace.out

dmenu popup opened. Pressed enter. Segfault. strace output attached. Indecipherable to one such as me - if there is anything else I can provide will happily comply. Thanks for your patience and for being a package maintainer.

EDIT: sorry captured stdin instead of stderr. Changed '>' to '&>' in test script. Fixing attachment.
Comment by Levente Polyak (anthraxx) - Friday, 08 February 2019, 01:51 GMT
the file is empty, it outputs to stderr not stdout
Comment by fwfull (fluffywaffles) - Friday, 08 February 2019, 01:52 GMT
Sorry, saw that 1s too late to fix it -- my bad. Fixed now.
Comment by Levente Polyak (anthraxx) - Friday, 08 February 2019, 01:59 GMT
you can get coredump information with 'coredumpctl' can you use the 'dump' command on the affected PID to get the stacktrace here?

However, this seems to be some kind of corruption issue in one or the other way, however it works perfectly fine over here.
I don't see this as a packaging issue but as an issue with the upstream software.

Please open a bug ticket at the dmenu bugtracker providing them strace and coredump output via coredumpctl PID dump.
I don't think this is a packaging issue
Comment by fwfull (fluffywaffles) - Friday, 08 February 2019, 02:10 GMT
Thanks for your help - will do!
Comment by Jochen (Alfe) - Wednesday, 13 February 2019, 11:30 GMT
Any updates on this? I have the same issue.
Comment by Brian (blamm9) - Thursday, 14 February 2019, 16:54 GMT
dmenu_run works for me, but I get this issue running i3-dmenu-desktop and j4-dmenu-desktop. Downgrade to 4.8 fixes this.
Comment by Levente Polyak (anthraxx) - Thursday, 14 February 2019, 17:15 GMT
Read the history here: Report upstream where people can fix it.
Comment by Jochen (Alfe) - Friday, 15 February 2019, 07:40 GMT
There seems to be a vivid discussion at the mailinglist of dmenu ( about this issue. It seems, that this commit ( introduced the broken stuff (from Seems that upstream is on a good way of fixing; thanks to @fwfull for reporting and investigating there!
Comment by Stefan (Faither) - Saturday, 16 February 2019, 14:47 GMT
Just FYI or if you want to replicate the crash - or make it go away. Here's a work-around:




I've bound this script in my ~/.i3/config
#bindsym $mod+d exec dmenu_run
bindsym $mod+d exec /opt/dmenu_fix

---- EDIT ----

Alternatively starting fcitx (the IME I use) also mitigated the crashes.
Comment by Jochen (Alfe) - Tuesday, 19 March 2019, 08:22 GMT
Since the issue is solved Upstream with the commit ( ) mentioned by one of the devs ( ) which was reported as working ( ), can we maybe get a new 4.9 build?
Comment by Jochen (Alfe) - Sunday, 26 May 2019, 15:52 GMT
Since this is now fixed for over two months (and everyone with this issue needs to work around that) can we finally get an updated 4.9-2 with the couple last commits?
Comment by Alex (Sinax) - Tuesday, 11 June 2019, 21:34 GMT
Requesting the same as user above, 4.9-2 would be nice