FS#49436 - [leafpad] Blank screen (hang/crash) when starting from rofi

Attached to Project: Arch Linux
Opened by Luca Weiss (z3ntu) - Sunday, 22 May 2016, 18:10 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 04 May 2021, 12:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Christian Hesse (eworm)
Anatol Pomozov (anatolik)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When I launch leafpad from rofi (mostly only the first time after a reboot or something like that), leafpad hangs with just a white screen.

Additional info:
* Leafpad 0.8.18.1-5
* I didn't change anything configuration wise & I don't know where or even if there are log files for leafpad


Steps to reproduce:
I launch rofi from i3wm with $mod+d:
i3-dmenu-desktop --entry-type=name --dmenu='rofi -i -opacity \"50\" -dmenu -p "run:"'
and then leafpad hangs/crashes.
gdb ("sudo gdb /usr/bin/leafpad" -> "attach <procnr>" -> "frame") tells me "#0 0x00007f1369b586ed in read () from /usr/lib/libc.so.6"
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 04 May 2021, 12:44 GMT
Reason for closing:  None
Additional comments about closing:  Works for ithers, very old report with no further response from the op.
Comment by Luca Weiss (z3ntu) - Sunday, 22 May 2016, 18:37 GMT
I forgot to add, that leafpad starts normally when I launch it from the terminal.
Comment by Doug Newgard (Scimmia) - Saturday, 28 May 2016, 14:18 GMT
Also pulling in the rofi maintainer, because this doesn't make sense to me.
Comment by Luca Weiss (z3ntu) - Wednesday, 01 June 2016, 08:33 GMT
I found out, that you can get more information with the gdb command "bt":

(gdb) bt
#0 0x00007fe58ff6a6ed in read () from /usr/lib/libc.so.6
#1 0x00007fe58ff01508 in __GI__IO_file_underflow ()
from /usr/lib/libc.so.6
#2 0x00007fe58ff00798 in __GI__IO_file_xsgetn ()
from /usr/lib/libc.so.6
#3 0x00007fe58fef6289 in fread () from /usr/lib/libc.so.6
#4 0x0000000000410191 in ?? ()
#5 0x0000000000407dfb in ?? ()
#6 0x00007fe58feb0741 in __libc_start_main ()
from /usr/lib/libc.so.6
#7 0x0000000000407f89 in ?? ()
Comment by Christian Hesse (eworm) - Wednesday, 01 June 2016, 18:56 GMT
Just tried to reproduce this...

* installed i3-wm, rofi and leafpad
* started an i3 session
* opened a terminal (Win+Enter)
* pasted your command (i3-dmenu-desktop --entry-type=name --dmenu='rofi -i -opacity \"50\" -dmenu -p "run:"')
* selected leafpad
* edited a file
* saved file
* exited leafpad

No issues found... Any more details about how to reproduce?
Comment by Luca Weiss (z3ntu) - Wednesday, 01 June 2016, 20:24 GMT
That's really weird because I can reproduce it all the time... The first time you start leafpad through rofi in (maybe a boot or suspend cycle?) it does that. When I then "pkill -e -9 leafpad" (normal SIGTERM/15 won't work) and start it again through rofi it does work :/
My installed packages: http://pastebin.com/4TUKr7Sr
My i3 config is here: https://github.com/z3ntu/dotfiles/blob/master/i3/.config/i3/config
Comment by Alad Wenter (Alad) - Wednesday, 20 July 2016, 11:57 GMT
The gdb output above is useless without debug symbols. Rebuild the relevant packages <https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces>, and send the traces to leafpad upstream.
Comment by mattia (nTia89) - Saturday, 12 December 2020, 13:38 GMT
I cannot reproduce the issue.

Loading...