Re: [dev] [dwm] new release - transition from Openbox
Not all keyboards have a logo key, most of them have an alt key though. My keyboard doesn't have a win key. I believe that. :) But it's not an argument. I have one that even doesn't have some letters, but that doesn't mean it has to be supported. :) https://duckduckgo.com/?iax=images&ia=images&q=tracer+avenger I understand that proper keyboard support is necessary to start using system in the first place. But, still, I believe that nowadays keyboard without logo key is a marginal case (probably even in suckless community) - so it's not really important. Different matter is that "typical" keyboard has already at least 8 modifiers key (2 x shift, 2 x alt, 2 x ctrl, logo, CapsLock). Which is madness on its own. :) And "suckless philosophy" doesn't really state what has to be supported and what hasn't (which is actually good), apart from: "focus on simplicity, clarity and frugality. Our philosophy is about keeping things simple, minimal and usable." So I guess "we" have to stick with our intuition and make some arbitrary decisions. :) Alt is fine. ;-) Cheers s/
Re: [dev] [dwm] new release - transition from Openbox
And laptops has extra fn key :D I totally agree with you >Different matter is that "typical" keyboard has already at least 8 >modifiers key (2 x shift, 2 x alt, 2 x ctrl, logo, CapsLock). Which is >madness on its own. :) -- DG
Re: [dev] [dmenu] 4.9 segfault on input
Hi there, can you be a bit more elaborate how to run into this bug? How does it occure in your setup? Is config.h modified? What are the inputs (from stdin), what do you enter? Thanks, Anselm On Thu, 7 Feb 2019 at 18:35, Jordan Timmerman wrote: > > First bug report -- also only an amateur at debugging C. Please be patient. :) > > Originally reported to the package maintainer for Arch linux, who > tells me he's fairly certain it's an upstream bug. > > Per the hacking page, I have attached the output of the gdb backtrace. > I also attached strace output and the coredump file. > > Thanks for dmenu! Let me know if there's anything else I can do.
Re: [dev] [dmenu] 4.9 segfault on input
Hi Anselm, I run the following script: echo 'a\nb\nc' | dmenu I then press Enter. The program segaults. config.h is not modified (to the very best of my knowledge). I am using the dmenu package from the Arch Linux community packages database, which is packaged using the script you can see here: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/dmenu >From skimming that script, I am fairly of the opinion that the config.h is not being modified. I am running the command using st 0.8.1 running xserver 1.20.3. I don't know if any of that is helpful. Downgrading the package to 4.8 manually solves this issue. On Thu, Feb 7, 2019 at 8:53 PM Anselm Garbe wrote: > > Hi there, > > can you be a bit more elaborate how to run into this bug? How does it > occure in your setup? > > Is config.h modified? What are the inputs (from stdin), what do you enter? > > Thanks, > Anselm > > On Thu, 7 Feb 2019 at 18:35, Jordan Timmerman wrote: > > > > First bug report -- also only an amateur at debugging C. Please be patient. > > :) > > > > Originally reported to the package maintainer for Arch linux, who > > tells me he's fairly certain it's an upstream bug. > > > > Per the hacking page, I have attached the output of the gdb backtrace. > > I also attached strace output and the coredump file. > > > > Thanks for dmenu! Let me know if there's anything else I can do. >
Re: [dev] [dmenu] 4.9 segfault on input
On Thu, 7 Feb 2019 at 22:58, Jordan Timmerman wrote: > > Hi Anselm, > > I run the following script: > > echo 'a\nb\nc' | dmenu > > I then press Enter. The program segaults. I just did this on an up-to-date Arch Linux system with dmenu 4.9 installed and it does not seg-fault on my system. dca@franz:/tmp$ echo 'a\nb\nc' | dmenu a\nb\nc dca@franz:/tmp$
Re: [dev] [dmenu] 4.9 segfault on input
Well shucks. Okay. Thanks for trying! Must be something on my end. Perhaps the version of a dynamically linked library could be affecting it? On Thu, Feb 7, 2019 at 10:13 PM Donald Allen wrote: > > On Thu, 7 Feb 2019 at 22:58, Jordan Timmerman wrote: > > > > Hi Anselm, > > > > I run the following script: > > > > echo 'a\nb\nc' | dmenu > > > > I then press Enter. The program segaults. > > I just did this on an up-to-date Arch Linux system with dmenu 4.9 > installed and it does not seg-fault on my system. > > dca@franz:/tmp$ echo 'a\nb\nc' | dmenu > a\nb\nc > dca@franz:/tmp$ >
Re: [dev] [dmenu] 4.9 segfault on input
Doing a print-based line-by-line binary search indicates the segfault occurs during a call to XmbLookupString. Does that ring any alarm bells for anyone? Seems to imply there's some kind of problem in my version of that X library, whichever one it is. Will keep looking. On Thu, Feb 7, 2019 at 10:19 PM Jordan Timmerman wrote: > > Well shucks. Okay. Thanks for trying! Must be something on my end. > Perhaps the version of a dynamically linked library could be affecting > it? > > On Thu, Feb 7, 2019 at 10:13 PM Donald Allen wrote: > > > > On Thu, 7 Feb 2019 at 22:58, Jordan Timmerman wrote: > > > > > > Hi Anselm, > > > > > > I run the following script: > > > > > > echo 'a\nb\nc' | dmenu > > > > > > I then press Enter. The program segaults. > > > > I just did this on an up-to-date Arch Linux system with dmenu 4.9 > > installed and it does not seg-fault on my system. > > > > dca@franz:/tmp$ echo 'a\nb\nc' | dmenu > > a\nb\nc > > dca@franz:/tmp$ > >
Re: [dev] [dmenu] 4.9 segfault on input
On Thu, 7 Feb 2019 at 23:33, Jordan Timmerman wrote: > > Doing a print-based line-by-line binary search indicates the segfault > occurs during a call to XmbLookupString. > > Does that ring any alarm bells for anyone? > > Seems to imply there's some kind of problem in my version of that X > library, whichever one it is. Will keep looking. Here's the output of ldd for dmenu on my system, showing all library dependencies: dca@franz:~$ ldd `which dmenu` linux-vdso.so.1 (0x7fff933d) libX11.so.6 => /usr/lib/libX11.so.6 (0x7f2042e7d000) libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x7f2042c7a000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x7f2042c33000) libXft.so.2 => /usr/lib/libXft.so.2 (0x7f2042a1d000) libc.so.6 => /usr/lib/libc.so.6 (0x7f2042859000) libxcb.so.1 => /usr/lib/libxcb.so.1 (0x7f204282f000) libdl.so.2 => /usr/lib/libdl.so.2 (0x7f2042828000) libXext.so.6 => /usr/lib/libXext.so.6 (0x7f2042616000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x7f204234d000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0x7f2042311000) libuuid.so.1 => /usr/lib/libuuid.so.1 (0x7f2042308000) libpthread.so.0 => /usr/lib/libpthread.so.0 (0x7f20422e7000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0x7f20422d8000) /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x7f2042ff5000) libXau.so.6 => /usr/lib/libXau.so.6 (0x7f20420d4000) libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x7f2041ece000) libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x7f2041ebb000) libpng16.so.16 => /usr/lib/libpng16.so.16 (0x7f2041e83000) libz.so.1 => /usr/lib/libz.so.1 (0x7f2041c6c000) libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x7f2041b6e000) libm.so.6 => /usr/lib/libm.so.6 (0x7f20419e9000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x7f20418c6000) libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x7f20418a1000) libpcre.so.1 => /usr/lib/libpcre.so.1 (0x7f204182e000) You might want to compare with the output of ldd `which dmenu` on your system. > > On Thu, Feb 7, 2019 at 10:19 PM Jordan Timmerman wrote: > > > > Well shucks. Okay. Thanks for trying! Must be something on my end. > > Perhaps the version of a dynamically linked library could be affecting > > it? > > > > On Thu, Feb 7, 2019 at 10:13 PM Donald Allen wrote: > > > > > > On Thu, 7 Feb 2019 at 22:58, Jordan Timmerman wrote: > > > > > > > > Hi Anselm, > > > > > > > > I run the following script: > > > > > > > > echo 'a\nb\nc' | dmenu > > > > > > > > I then press Enter. The program segaults. > > > > > > I just did this on an up-to-date Arch Linux system with dmenu 4.9 > > > installed and it does not seg-fault on my system. > > > > > > dca@franz:/tmp$ echo 'a\nb\nc' | dmenu > > > a\nb\nc > > > dca@franz:/tmp$ > > > >
Re: [dev] [dmenu] 4.9 segfault on input
Thanks, Donald. My `ldd` output includes all the same libraries as yours, although the addresses of the libraries of course differ. I'm pretty confident at this point that the segfault occurs during the call to libx11 XmbLookupString. I've attempted downgrading libx11 from 1.6.7 to 1.6.6 and rebuilding, but this makes no difference. For whatever reason, dmenu 4.8 works, and dmenu 4.9 segfaults on keypress. I might look into it again later, but for now I'll downgrade back to dmenu 4.8 and get on with life. :) On Thu, Feb 7, 2019 at 10:37 PM Donald Allen wrote: > > On Thu, 7 Feb 2019 at 23:33, Jordan Timmerman wrote: > > > > Doing a print-based line-by-line binary search indicates the segfault > > occurs during a call to XmbLookupString. > > > > Does that ring any alarm bells for anyone? > > > > Seems to imply there's some kind of problem in my version of that X > > library, whichever one it is. Will keep looking. > > Here's the output of ldd for dmenu on my system, showing all library > dependencies: > > dca@franz:~$ ldd `which dmenu` > linux-vdso.so.1 (0x7fff933d) > libX11.so.6 => /usr/lib/libX11.so.6 (0x7f2042e7d000) > libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x7f2042c7a000) > libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x7f2042c33000) > libXft.so.2 => /usr/lib/libXft.so.2 (0x7f2042a1d000) > libc.so.6 => /usr/lib/libc.so.6 (0x7f2042859000) > libxcb.so.1 => /usr/lib/libxcb.so.1 (0x7f204282f000) > libdl.so.2 => /usr/lib/libdl.so.2 (0x7f2042828000) > libXext.so.6 => /usr/lib/libXext.so.6 (0x7f2042616000) > libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x7f204234d000) > libexpat.so.1 => /usr/lib/libexpat.so.1 (0x7f2042311000) > libuuid.so.1 => /usr/lib/libuuid.so.1 (0x7f2042308000) > libpthread.so.0 => /usr/lib/libpthread.so.0 (0x7f20422e7000) > libXrender.so.1 => /usr/lib/libXrender.so.1 (0x7f20422d8000) > /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 > (0x7f2042ff5000) > libXau.so.6 => /usr/lib/libXau.so.6 (0x7f20420d4000) > libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x7f2041ece000) > libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x7f2041ebb000) > libpng16.so.16 => /usr/lib/libpng16.so.16 (0x7f2041e83000) > libz.so.1 => /usr/lib/libz.so.1 (0x7f2041c6c000) > libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x7f2041b6e000) > libm.so.6 => /usr/lib/libm.so.6 (0x7f20419e9000) > libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x7f20418c6000) > libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x7f20418a1000) > libpcre.so.1 => /usr/lib/libpcre.so.1 (0x7f204182e000) > > You might want to compare with the output of ldd `which dmenu` on your system. > > > > > On Thu, Feb 7, 2019 at 10:19 PM Jordan Timmerman wrote: > > > > > > Well shucks. Okay. Thanks for trying! Must be something on my end. > > > Perhaps the version of a dynamically linked library could be affecting > > > it? > > > > > > On Thu, Feb 7, 2019 at 10:13 PM Donald Allen > > > wrote: > > > > > > > > On Thu, 7 Feb 2019 at 22:58, Jordan Timmerman wrote: > > > > > > > > > > Hi Anselm, > > > > > > > > > > I run the following script: > > > > > > > > > > echo 'a\nb\nc' | dmenu > > > > > > > > > > I then press Enter. The program segaults. > > > > > > > > I just did this on an up-to-date Arch Linux system with dmenu 4.9 > > > > installed and it does not seg-fault on my system. > > > > > > > > dca@franz:/tmp$ echo 'a\nb\nc' | dmenu > > > > a\nb\nc > > > > dca@franz:/tmp$ > > > > > > >
