Bug 1000018 - terminal emulators don't work after update to glibc-2.17-13.fc19
Summary: terminal emulators don't work after update to glibc-2.17-13.fc19
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-22 13:59 UTC by Dragos Tatulea
Modified: 2016-11-24 15:59 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-23 08:19:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
urxvt strace log (118.99 KB, text/x-log)
2013-08-22 13:59 UTC, Dragos Tatulea
no flags Details

Description Dragos Tatulea 2013-08-22 13:59:08 UTC
Created attachment 789211 [details]
urxvt strace log

Description of problem:
After doing a yum upgrade, most terminal emulators don't want to start (gnome-terminal, urxvt, tmux)

Version-Release number of selected component (if applicable):
glibc-2.17-13.fc19

How reproducible:
Just start urxvt, tmux, gnome-terminal.

Steps to Reproduce:
1. run urxvt

Actual results:
urxvt: can't initialize pseudo-tty, aborting.

Expected results:
urxvt starts without errors

Additional info:

* Narrowed it down to glibc. There's a pty chown CVE fix in there [1]

* After downgrading glibc, everything is back to normal.

* Here's how devpts is mounted:
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)

* Attached strace log. Check out the chown err on /dev/pts/1.

[1] - https://admin.fedoraproject.org/updates/FEDORA-2013-15053/glibc-2.17-13.fc19?_csrf_token=390be9769cd733681beb5e86c521ebc6eabb6de6

Comment 1 Siddhesh Poyarekar 2013-08-22 14:42:29 UTC
devpts is mounted by default as:

devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000)

Not having gid=5 in your mount options is wrong and should not occur in a default installation.  In fact, I had mentioned that in a note in the update link you posted.

Unless there is reason to believe that the default fedora install options resulted in gid=5 not being present, this is not a bug.  Do you know how your system ended up without gid=5 in the mount options?

Comment 2 Dragos Tatulea 2013-08-23 08:19:34 UTC
Ooops. PEBCAK. Found the issue: I deleted the devpts line in fstab and it was getting mounted with default arguments. After fixing that all works fine.


Note You need to log in before you can comment on or make changes to this bug.