Bug 121532 - "su -l" produces munged warning message on exit
"su -l" produces munged warning message on exit
Product: Fedora
Classification: Fedora
Component: pam (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 2004-04-22 10:37 EDT by Tom London
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-13 20:39:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tom London 2004-04-22 10:37:14 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312

Description of problem:
From gnome-terminal, "su -l" on exit sometimes produces the following
type of messages in /var/log/messages:

Apr 21 20:00:48 fedora su(pam_unix)[7438]: session closed for user root
Apr 21 20:00:48 fedora su[7438]: Warning!  Could not relabel \2302^Q
with user_u:object_r:user_devpts_t, not relabeling.

(I have many of this type of message in the log. \230 is constant.
Next characters vary.....).  Rest of message constant.

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

How reproducible:

Steps to Reproduce:
1. gnome-terminal, su -l
2. exit

Additional info:
Comment 1 Tim Waugh 2004-04-22 11:42:06 EDT
This message comes from pam.
Comment 2 Tom London 2004-04-22 13:25:53 EDT
The bug occurs when you kill the window without exiting first from "su

So, here's how to reproduce it:
 1. as non-root user, within a gnome-terminal window, do "su -l" and
enter correct password.
 2. close the window without exiting from su shell.
 3. examine /var/log/messages.  You'll see warning message with
corrupted text.

Is this a NULL/dangling pointer?
Comment 3 Tomas Mraz 2004-09-13 08:07:16 EDT
Can't reproduce on pam-0.77-55.

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