Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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#70952 - urxvt will not open and uses 100% cpu after update to 9.26-1
Attached to Project:
Community Packages
Opened by John Henderson (jwhendy) - Wednesday, 19 May 2021, 22:27 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 22 May 2021, 20:20 GMT
Opened by John Henderson (jwhendy) - Wednesday, 19 May 2021, 22:27 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 22 May 2021, 20:20 GMT
|
DetailsDescription: I updated with pacman -Syu before my last shutdown. Upon boot, rxvt-unicode (urxvt) would not start for me. Using top showed 95-100% cpu utilization, requiring me to kill it. Downgrading to 9.22-10 works fine.
Additional info: * package version(s): 9.22-10 works, 9.26-1 does not * config and/or log files etc. I exited i3 to a new tty and tried starting urxvt and got no output. My journalctl just has lines like so: $ journalctl -b | grep rxvt May 19 14:33:20 voltaur systemd-coredump[6825]: Process 4199 (urxvt) of user 1000 dumped core. May 19 14:33:53 voltaur systemd-coredump[7543]: Process 6765 (urxvt) of user 1000 dumped core. $ sudo journalctl | grep -i error May 19 14:33:15 voltaur kernel: urxvt[4199]: segfault at 7ffc1231fe78 ip 00007f862da3f481 sp 00007ffc1231fe20 error 6 in libX11.so.6.4.0[7f862da15000+8a000] May 19 14:33:48 voltaur kernel: urxvt[6765]: segfault at 7ffde2d86ff8 ip 00007fe1a5dd8a99 sp 00007ffde2d86fb0 error 6 in libc-2.33.so[7fe1a5d75000+14c000] May 19 14:34:11 voltaur kernel: urxvt[6806]: segfault at 7ffd9c83efb8 ip 00007f61e75cd481 sp 00007ffd9c83ef60 error 6 in libX11.so.6.4.0[7f61e75a3000+8a000] May 19 14:34:46 voltaur kernel: urxvt[7550]: segfault at 7ffc27b70eb8 ip 00007f231a162481 sp 00007ffc27b70e60 error 6 in libX11.so.6.4.0[7f231a138000+8a000] May 19 15:47:07 voltaur kernel: urxvt[9855]: segfault at 7fffb4e55e68 ip 00007f8adbebe481 sp 00007fffb4e55e10 error 6 in libX11.so.6.4.0[7f8adbe94000+8a000] May 19 15:47:44 voltaur kernel: urxvt[9911]: segfault at 7ffe96945ff8 ip 00007f8190041d96 sp 00007ffe96945ff0 error 6 in libc-2.33.so[7f818ffde000+14c000] May 19 15:47:47 voltaur kernel: urxvt[9919]: segfault at 7fff5537bff0 ip 00007f44f76eaa75 sp 00007fff5537bf90 error 6 in libc-2.33.so[7f44f7687000+14c000] May 19 15:54:29 voltaur kernel: urxvt[9938]: segfault at 7ffd93cf4ff8 ip 00007f81139da6b5 sp 00007ffd93cf5000 error 6 in libX11.so.6.4.0[7f8113967000+8a000] * misc info $ uname -a Linux voltaur 5.12.3-arch1-1 #1 SMP PREEMPT Wed, 12 May 2021 17:54:18 +0000 x86_64 GNU/Linux As mentioned, running i3 (i3-gaps 4.19.1-1). If relevant, using nvidia dedicated graphics on nvidia-465.27-6. If relevant to the X11 errors: $ pacman -Q | grep xorg xorg-fonts-encodings 1.0.5-2 xorg-mkfontscale 1.2.1-2 xorg-server 1.20.11-1 xorg-server-common 1.20.11-1 xorg-setxkbmap 1.3.2-2 xorg-xauth 1.1-2 xorg-xbacklight 1.2.3-2 xorg-xinit 1.4.1-3 xorg-xinput 1.6.3-2 xorg-xkbcomp 1.4.5-1 xorg-xkill 1.0.5-2 xorg-xmodmap 1.0.10-2 xorg-xprop 1.2.5-1 xorg-xrandr 1.5.1-2 xorg-xrdb 1.2.0-2 xorg-xset 1.2.4-2 xorgproto 2021.4-1 * steps to reproduce: - update rxvt-unicode from 9.22-1 to 9.26-10 - try to run rxvt-unicode Given the segfaults, this is potentially look like a urxvt and xorg interaction issue? I don't see anything other than misc mouse/keyboard lag errors from libinput in my Xorg.0.log, but if that's relevant (or any other information), kindly let me know and I can post whatever is helpful. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Saturday, 22 May 2021, 20:20 GMT
Reason for closing: None
Additional comments about closing: user comment: This appears due to my .Xdefaults config and should either go upstream to Xorg or urxvt (or is expected, in which case... lesson learned on my end and I appreciate the replication attempt).
Saturday, 22 May 2021, 20:20 GMT
Reason for closing: None
Additional comments about closing: user comment: This appears due to my .Xdefaults config and should either go upstream to Xorg or urxvt (or is expected, in which case... lesson learned on my end and I appreciate the replication attempt).
```
$ xterm
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 1 (X_CreateWindow)
Serial number of failed request: 40
Current serial number in output stream: 48
```
I found that by removing .Xdefaults, things were working. Hmmm. I still have not figured out what, exactly, was going on. I did make this a while ago and it looks like i wasn't clear on * vs. . for the options. I noticed some wonky things upon inspection like `*.color1: foo` where I'd used both, for example. I *thought* I'd narrowed it down to depth: 32, but after my walk through it's working and I no longer get errors in urxvt (freeze/high cpu) or xterm. I posted the original (.Xdefaults) and the modified/working (.Xresources now per arch wiki) for reference.
If you know urxvt/X well... could you coach on continuing to post upstream? It might be X related, but in either case... I'm leaning toward thinking that a config file shouldn't break a system so easily! Thoughts?
I'll request closure here, but if you have a leaning on what might be up, I'm happy to take upstream. Otherwise... if this is an obvious goof on my part and such behavior is expected as a result, well, wouldn't be the first time :)
If you have any of the following in your .Xresources or .Xdefaults:
URxvt*tab-bg
URxvt*tab-fg
URxvt*tabbar-bg
URxvt*tabbar-fg
you will need to add in the 'tabbedex' prefix like so:
URxvt*tabbedex.tab-bg
I'd still count this as a bug, as with the wrong resources urxvt just hangs and needs a kill -9, instead of either ignoring the malformed resources or printing a warning.