Bug 1183652

Summary:	[Build 20210316] vim gets stuck when running in fbiterm
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Rodion Iafarov <riafarov>
Component:	Installation	Assignee:	Stanislav Brabec <sbrabec>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P3 - Medium	CC:	ancor, jreidinger
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST logs

Description Rodion Iafarov 2021-03-17 14:04:23 UTC

Created attachment 847338 [details]
YaST logs

Related to https://jira.suse.com/browse/SLE-16358

Steps to reproduce:
1. Run installer in text mode
2. Press Ctrl+D Shift+C 
3. Select Expert console
4. Run "shell" command
5. Type vim and press enter
6. System freezes with only cursor in the corner

It doesn't work only in TW (works fine in SLES) and only in Expert Console. Other ttys are fine, as well if run in qt. Hope it helps to bisect the issue a bit.

It's also not possible to recover from this error and after killing vim process, I could not get back to the installer.

Comment 1 Ancor Gonzalez Sosa 2021-03-18 08:35:03 UTC

Maybe this is mitigated by this fix for bug#1183648.
https://github.com/yast/yast-installation/pull/934/files

It uses dash instead of bash and it wouldn't be surprised if it has an impact in how vim runs.

We should likely re-test with an int-sys including yast2-installation > 4.3.35

Comment 2 Ladislav Slezák 2021-03-18 09:37:32 UTC

That "bash" job control issue happened only in Qt UI as we run xterm window there. In ncurses bash does not complain. This is a different problem.

I found out that "vim" works fine when the console is a plain text console without the "fbiterm" running. (I used the "nomodeset" boot option do disable KMS and force plain VGA text console.)

It works in SLE because it does not use KMS, at least in my VirtualBox VM it by default boots into a plain VGA console.

Comment 3 Ladislav Slezák 2021-03-18 09:44:08 UTC

OK, vim get's stuck even when simply running "fbiterm vim"...

Comment 4 Ladislav Slezák 2021-03-18 14:18:22 UTC

I found a workaround, running "TERM=vt100 vim" inside fbiterm works.

I'll add the workaround into YaST and some some more testing...

Comment 5 Josef Reidinger 2021-03-30 06:29:42 UTC

I think we should forward when we implement workaround to fbiterm/vim maintainer as it looks like bug in that tools.

Comment 7 Ladislav Slezák 2021-03-30 07:23:33 UTC

Workaround applied in yast2-installation-4.3.36 (https://github.com/yast/yast-installation/pull/936)

Reassigning to the fbiterm maintainer, see comment #3 and comment #4. (Maybe the problem is in the terminfo database or in the ncurses library, I do not know...)

Comment 10 Stanislav Brabec 2024-02-05 12:49:40 UTC

fbiterm (xiterm) is a dead project - the latest change is from 2004. It has a lot of bugs. Even worse, it does not work well on recent kernels with several drivers. Nobody is going to fix it, as it uses an obsolete kernel interface. We want to avoid its using and stop shipping it as soon as possible. We do not have resources to fix fbiterm bugs.

Related enterprise requests:
PED-3655
PED-7839