FS#22849 - [rxvt-unicode] causing GNU screen segfault with awesomeWM
Attached to Project:
Arch Linux
Opened by Daniel Campbell (xelados) - Thursday, 10 February 2011, 23:29 GMT
Last edited by Angel Velasquez (angvp) - Tuesday, 03 May 2011, 14:37 GMT
Opened by Daniel Campbell (xelados) - Thursday, 10 February 2011, 23:29 GMT
Last edited by Angel Velasquez (angvp) - Tuesday, 03 May 2011, 14:37 GMT
|
Details
Description: When I use awesomewm's fullscreen or maximize
commands while running a screen session in urxvt, it closes
the session with the message: "[screen caught signal 11.]" I
tried the exact same scenario with xterm and everything
worked as expected. Someone suggested transparency as a
possible issue; I added transparency after this error
started occurring, so I'm certain it's not that.
The keybinds I have are Win+f for fullscreen and Win+m for maximize. I don't know if these keys are used for urxvt. Additional info: * package version(s) awesome 3.4.8-2 rxvt-unicode 9.10-1 screen 4.0.3-10 * config and/or log files etc. http://sprunge.us/PLGW?lua -- awesome's rc.lua http://sprunge.us/XJNc -- ~/.Xdefaults http://sprunge.us/PCYY -- ~/.screenrc Steps to reproduce: 1. Run urxvt in awesome, and at least one other window. Doesn't matter what it is. 2. Run screen in urxvt. 3. Make the urxvt window fullscreen or maximized through your preferred choice. |
This task depends upon
Closed by Angel Velasquez (angvp)
Tuesday, 03 May 2011, 14:37 GMT
Reason for closing: Not a bug
Additional comments about closing: This seems to be hold, and the failure is produced on a non-supported application (awesomewm)
Tuesday, 03 May 2011, 14:37 GMT
Reason for closing: Not a bug
Additional comments about closing: This seems to be hold, and the failure is produced on a non-supported application (awesomewm)
rxvt-unicode 9.10-1
screen 4.0.3-10
awesome 3.4.8-2