I can't say for sure but it seems very likely that is the same issue.
It is occurring in XmbLookupString also and seems to have the same
behavior. Is there a fix in the works? It seems there was a bit of
disagreement as to whether XIM support was worth keeping, and people
weren't sure how to include XIM support without this segfault? I
personally have seen no need for non-ascii inputs but I'd imagine
there are many out there who like to name their scripts etc. using
their non-latin native writing system, which is the vast majority of
languages on this planet. From a international accessibility
perspective it makes perfect sense. Just one person's thoughts. But
the segfault is no fun either.
On Sat, Mar 23, 2019 at 8:42 PM congdanhqx <congdanhqx_AT_gmail.com> wrote:
>
> Hi Josh,
>
> On March 23, 2019 7:27:20 PM UTC, Josh Hansen <hansen.joshuaa_AT_gmail.com> wrote:
> >Hi,
> >I'm relaying a common bug report from i3wm that appears to be a dmenu
> >issue involving a segmentation fault upon any user input. You can see
> >the reports here: https://github.com/i3/i3/issues/3619
> >
> >This occurs in dmenu 4.9. It seems that at least for some users, this
> >version gives a segmentation fault when entering any text input into
> >the dmenu input box. This impairs essentially all use of dmenu.
> >
> >Here is how I can bring about the bug:
> >
> >1. Invoke dmenu using the i3 shortcut
> >2. Type any text input key
> >3. dmenu exits immediately
> >
> >Upon further inspection, this can be shown to be a segmentation fault.
> >From the command line:
> >
> >$ gdb dmenu
> >$ (gdb) run < /dev/null
> >...
> >Program received signal SIGSEGV, Segmentation fault.
> >XmbLookupString (ic=0x0, ev=0x7fffffffcf50, buffer=0x7fffffffd010
> ><incomplete sequence \302>, nbytes=32, keysym=0x7fffffffcec0,
> >status=0x7fffffffcdc0) at ICWrap.c:403
> >403 if (ic->core.im)
> >
> >This appears to be a dmenu-specific issue as it can be reproduced
> >similarly from within a non-i3 window manager.
> >
> >My system is Fedora 29, dmenu 4.9. The error appears to have been
> >introduced upon upgrading from dmenu 4.8, before which dmenu
> >functioned properly.
>
> Is it duplicated with this report:
>
> https://lists.suckless.org/dev/1902/33245.html?
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
Received on Sun Mar 24 2019 - 07:55:29 CET