Bug 555813 - sshd[8190]: pam_env(sshd:setcred): non-alphanumeric key 'alias aumix=padsp aumix' in /etc/environment', ignoring
Summary: sshd[8190]: pam_env(sshd:setcred): non-alphanumeric key 'alias aumix=padsp au...
Status: RESOLVED DUPLICATE of bug 547384
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: i686 openSUSE 11.2
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Scott Reeves
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-16 13:31 UTC by Ulrich Windl
Modified: 2009-12-01 23:36 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Windl 2009-11-16 13:31:06 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090410 SUSE/1.1.18-0.1.1 SeaMonkey/1.1.18

For a 11.2 new install there are too many messages in /var/log/messages from sshd and pam_env. Examples are:
sshd[8190]: pam_env(sshd:setcred): non-alphanumeric key 'alias aumix=padsp aumix' in /etc/environment', ignoring
sshd[8190]: pam_env(sshd:setcred): non-alphanumeric key 'alias sox=padsp sox' in /etc/environment', ignoring
sshd[8190]: pam_env(sshd:setcred): non-alphanumeric key 'alias timidity=timidity -Oe' in /etc/environment', ignoring


Reproducible: Always

Steps to Reproduce:
1. Run SSH daemon, log in from remote

Actual Results:  
Suspect syslog messages

Expected Results:  
These messages shouldn't be there
Comment 1 Marcus Meissner 2009-11-17 08:11:48 UTC
i think ludwig fixed this, its caused by pulseaudio
Comment 2 Ludwig Nussel 2009-11-17 08:28:05 UTC
Great. It got checked into Factory but not 11.2
Comment 3 Ulrich Windl 2009-12-01 09:14:18 UTC
Should the bug be assigned to anybody? It seems the bug won't fix itself.
Comment 4 Scott Reeves 2009-12-01 23:36:18 UTC
Duplicate of 547384

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