[Wayland-bugs] [Bug 67837] New: [weston-launch] default pam configuration breaks on fedora 19
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Aug 6 10:47:41 PDT 2013
https://bugs.freedesktop.org/show_bug.cgi?id=67837
Priority: medium
Bug ID: 67837
Assignee: wayland-bugs at lists.freedesktop.org
Summary: [weston-launch] default pam configuration breaks on
fedora 19
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: joe.konno at linux.intel.com
Hardware: All
Status: NEW
Version: unspecified
Component: weston
Product: Wayland
After building wayland and weston 1.2.0, weston-launch does not work "out of
the box" on a (fairly) pristine Fedora 19 installation. "Fairly" because I
disabled selinux shortly after installation.
The first error encountered (stdout/stderr weston-launch):
failed to open pam session: 14: Cannot make/remove an entry for the specified
session
And /var/log/secure:
Aug 6 10:18:30 $host weston-launch: pam_loginuid(login:session):
set_loginuid failed
Aug 6 10:18:30 $host weston-launch: pam_unix(login:session): session opened
for user $user by (uid=1000)
I did a web search, found a cheap work-around for the pam issue here:
https://ask.fedoraproject.org/question/25453/weston-launch-start-problem/
Which entails commenting out a line in the default pam configuration file:
# #weston-launch# session required pam_loginuid.so
--
The expectation is that weston-launch "just works" with sufficient permissions
(all documented) are granted. However, that is not the case on Fedora 19.
--
# yum list installed | grep -e "xkbcommon" -e "pam"
libxkbcommon.x86_64 0.3.0-1.fc19 @fedora
libxkbfile.x86_64 1.0.8-3.fc19 @fedora
pam.x86_64 1.1.6-12.fc19 @updates
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20130806/003f8570/attachment.html>
More information about the Wayland-bugs
mailing list