Bug 1048487

Summary:	Wrong trminal mode after install/uninstall packages with systemd services
Product:	[Fedora] Fedora	Reporter:	Jochen Schmitt <jochen>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	jochen, johannbg, lnykryn, msekleta, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-23 16:02:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jochen Schmitt 2014-01-04 16:01:55 UTC

Description of problem:

After install or uninstall of a package which contains a systemd
service ther console (text mode) is unusable. When I try to type
anything the input will not echoed on the console.

Version-Release number of selected component (if applicable):

systemd-208-9.fc20

How reproducible:

1.) Start system with systemd.unit=multi-user.target

2.) Login as root

3.) typ 'yum install and' to install a package which contains a systemd serivce.

4.) After yum is finisched try to type anything on the console.

Actual results:

INput will not echoed on the console.

Expected results:

User input should echoed on the console as usual.

Additional info:

Comment 1 Lennart Poettering 2014-01-23 13:30:18 UTC

Hmm? systemd has no business in interfering with the terminal setup of your running login session. 

Reassigning to "and", since that package supposedly resulted in the broken terminal settings when yum finished. Maybe "and" has some code in %postinst or so, which changes the tty settings? 

If "and" is not responsible, please reassign to yum, since that is then the only thing accessing the terminal.

Comment 2 Jochen Schmitt 2014-01-23 15:32:57 UTC

Sorry, but and was only an example of a package where the reported issue occured. the issue occures on all package which will install systemd unit. this was the reason why I have reported this bug agains systemd.

Comment 3 Lennart Poettering 2014-02-23 16:02:26 UTC

This sounds a lot like another effect of bug 1043212.

*** This bug has been marked as a duplicate of bug 1043212 ***