[Desktop-packages] [Bug 1584759] Re: masking NetworkManager ineffective without also masking network-manager
Sorry, perhaps I was unclear in my original description: For the masking
to be effective *both* network-manager and NetworkManager need to be
masked, or NetworkManager.service will start on boot. 'systemctl status
network-manager' will show information about NetworkManager.service so
it seems to be an alias that works for things other than masking, which
does not feel like it's intended, whatever the canonical name.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1584759
Title:
masking NetworkManager ineffective without also masking network-
manager
Status in network-manager package in Ubuntu:
Won't Fix
Bug description:
On xenial (systemd 229), 'systemctl mask NetworkManager' is
ineffective; I can still start the service (and in fact it starts on
boot). This may be due to an interaction with an init.d script with a
different name ("network-manager").
root@test-paniikki:~# systemctl is-enabled NetworkManager network-manager
enabled
enabled
root@test-paniikki:~# systemctl mask NetworkManager
Created symlink from /etc/systemd/system/NetworkManager.service to
/dev/null.
root@test-paniikki:~# systemctl is-enabled NetworkManager network-manager
masked
masked
root@test-paniikki:~# systemctl start NetworkManager; echo $?
0
root@test-paniikki:~# systemctl status --no-pager NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; masked;
vendor preset: enabled)
Active: active (running) since Mon 2016-05-23 15:39:09 EEST; 9s ago
Main PID: 6155 (NetworkManager)
Tasks: 6 (limit: 512)
CGroup: /system.slice/NetworkManager.service
├─6155 /usr/sbin/NetworkManager --no-daemon
├─6167 /sbin/dhclient -d -q -sf
/usr/lib/NetworkManager/nm-dhcp-helper -pf /va...
└─6182 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground
--no-hosts --bind-in...
Only if 'network-manager' is also masked will the service fail to start:
root@test-paniikki:~# systemctl mask network-manager
Created symlink from /etc/systemd/system/network-manager.service to
/dev/null.
root@test-paniikki:~# systemctl stop NetworkManager
root@test-paniikki:~# systemctl start NetworkManager
Failed to start NetworkManager.service: Unit NetworkManager.service is
masked.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1584759/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1027805] Re: logins are not recorded in wtmp
sessreg(1) could also be used for this (in retrospect, it would actually also work for #870297) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1027805 Title: logins are not recorded in wtmp Status in Light Display Manager: Triaged Status in “lightdm” package in Ubuntu: Triaged Bug description: After applying the fix for #870297, utmp records are updated correctly but wtmp is not: flashman ~ % ssh root@test-precise 'dpkg-query --show lightdm && last -n1' lightdm 1.2.1-0ubuntu1.1 root pts/0 flashman Tue Jul 17 10:32 - 10:32 (00:00) wtmp begins Fri Jul 13 19:23:13 2012 'last' output here should show my graphical session as 'still logged in'. This should probably be fixed by stacking pam_lastlog for user sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1027805/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 666565] Re: "utf8" charmap in locale name is wrong
This was fixed in language-selector, which is what I originally reported
it against. I'm not sure why it's marked as affecting ubuntu-
translations.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/666565
Title:
"utf8" charmap in locale name is wrong
Status in Ubuntu Translations:
Incomplete
Status in “eglibc” package in Ubuntu:
New
Status in “gdm” package in Ubuntu:
Fix Released
Status in “langpack-locales” package in Ubuntu:
Won't Fix
Status in “language-selector” package in Ubuntu:
Fix Released
Status in “vim” package in Ubuntu:
New
Bug description:
Binary package hint: language-selector
LanguageSelector/macros.py explicitly sets the charmap part of locale
strings to "utf8" - it should be set to "UTF-8" instead. This is
relevant because not all systems alias locale names with the former to
the latter, and compatibility with those systems is broken.
Rationale for this change is that the 'locales' package uses the uppercase
hyphenated format everywhere, even going as far as replacing '.utf8' with it in
one case:
% dpkg -L locales | xargs grep '\.utf8'
/usr/sbin/locale-gen:elif [ $IS_LANG = no ] && L=`grep
"^${1/%.utf8/.UTF-8} " /usr/share/i18n/SUPPORTED`; then
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/666565/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1027805] Re: logins are not recorded in wtmp
Paul: 'who', 'users' and 'top' all look at utmp. The utmp issue was
fixed already, this concerns wtmp and lastlog ('last' and 'lastlog'
utilities show those records).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1027805
Title:
logins are not recorded in wtmp
Status in Light Display Manager:
Triaged
Status in “lightdm” package in Ubuntu:
Triaged
Bug description:
After applying the fix for #870297, utmp records are updated correctly
but wtmp is not:
flashman ~ % ssh root@test-precise 'dpkg-query --show lightdm && last -n1'
lightdm 1.2.1-0ubuntu1.1
root pts/0 flashman Tue Jul 17 10:32 - 10:32 (00:00)
wtmp begins Fri Jul 13 19:23:13 2012
'last' output here should show my graphical session as 'still logged
in'.
This should probably be fixed by stacking pam_lastlog for user
sessions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1027805/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1027805] Re: logins are not recorded in wtmp
pam_lastlog updates both wtmp and /var/log/lastlog. I'm not sure whether anything else actually writes to lastlog; there is no library to do so (both pam_lastlog and login without PAM seem to handle the file directly, using the struct from lastlog.h; see eg. libmisc/log.c in the 'shadow' source package) That said, I haven't tested what GDM does, but grepping the gdm3 source tree for 'lastlog' finds nothing but a mention in the documentation: http://library.gnome.org/admin/gdm/stable/security.html.en#PAM (I don't know what to make of those docs; the mention is vague and they discuss PAM modules not even present on my system). Therefore I assume GDM doesn't update lastlog, but this should probably be double-checked. As for updating wtmp, once we have the utmpx struct it's just a matter of calling udpwtmpx. That's simpler than changing the pam configuration, at least. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1027805 Title: logins are not recorded in wtmp Status in Light Display Manager: Triaged Status in “lightdm” package in Ubuntu: Triaged Bug description: After applying the fix for #870297, utmp records are updated correctly but wtmp is not: flashman ~ % ssh root@test-precise 'dpkg-query --show lightdm && last -n1' lightdm 1.2.1-0ubuntu1.1 root pts/0 flashman Tue Jul 17 10:32 - 10:32 (00:00) wtmp begins Fri Jul 13 19:23:13 2012 'last' output here should show my graphical session as 'still logged in'. This should probably be fixed by stacking pam_lastlog for user sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1027805/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in utmp
Robert, ok: bug 1027805 is the wtmp issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in utmp Status in Light Display Manager: Fix Released Status in “lightdm” package in Ubuntu: Fix Committed Status in “lightdm” source package in Oneiric: Triaged Status in “lightdm” source package in Precise: Fix Committed Bug description: Impact: Systems using LightDM have no entries in the utmp record for logins, so tools like 'w' and 'who' do not show LightDM sessions. Testcase: 1. Start Ubuntu system 2. Log into session 3. Open gnome-terminal 4. Run 'who' command Expected result: You should see TWO entries (the first is from LightDM, the second is from gnome-terminal): tty7 -MM-DD HH:MM pts/0 -MM-DD HH:MM (:0) Observed result: You see only one entry: pts/0 -MM-DD HH:MM (:0) Regression potential: Bugs in utmp code cause cause issues logging in To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1027805] [NEW] logins are not recorded in wtmp
Public bug reported: After applying the fix for #870297, utmp records are updated correctly but wtmp is not: flashman ~ % ssh root@test-precise 'dpkg-query --show lightdm && last -n1' lightdm 1.2.1-0ubuntu1.1 root pts/0 flashman Tue Jul 17 10:32 - 10:32 (00:00) wtmp begins Fri Jul 13 19:23:13 2012 'last' output here should show my graphical session as 'still logged in'. This should probably be fixed by stacking pam_lastlog for user sessions. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1027805 Title: logins are not recorded in wtmp Status in “lightdm” package in Ubuntu: New Bug description: After applying the fix for #870297, utmp records are updated correctly but wtmp is not: flashman ~ % ssh root@test-precise 'dpkg-query --show lightdm && last -n1' lightdm 1.2.1-0ubuntu1.1 root pts/0 flashman Tue Jul 17 10:32 - 10:32 (00:00) wtmp begins Fri Jul 13 19:23:13 2012 'last' output here should show my graphical session as 'still logged in'. This should probably be fixed by stacking pam_lastlog for user sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1027805/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
Sorry, that should've been lp:~lotheac/lightdm/wtmp_precise -- I'm too tired. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in Light Display Manager: Fix Released Status in “lightdm” package in Ubuntu: Fix Committed Status in “lightdm” source package in Oneiric: Triaged Status in “lightdm” source package in Precise: Fix Committed Bug description: Impact: Systems using LightDM have no entries in the utmp record for logins, so tools like 'w' and 'who' do not show LightDM sessions. Testcase: 1. Start Ubuntu system 2. Log into session 3. Open gnome-terminal 4. Run 'who' command Expected result: You should see TWO entries (the first is from LightDM, the second is from gnome-terminal): tty7 -MM-DD HH:MM pts/0 -MM-DD HH:MM (:0) Observed result: You see only one entry: pts/0 -MM-DD HH:MM (:0) Regression potential: Bugs in utmp code cause cause issues logging in To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
The 'last' issue is simple to fix: lp:~lotheac/lightdm/utmpx Should I propose a merge to lp:ubuntu/precise-proposed/lightdm or somewhere else? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in Light Display Manager: Fix Released Status in “lightdm” package in Ubuntu: Fix Committed Status in “lightdm” source package in Oneiric: Triaged Status in “lightdm” source package in Precise: Fix Committed Bug description: Impact: Systems using LightDM have no entries in the utmp record for logins, so tools like 'w' and 'who' do not show LightDM sessions. Testcase: 1. Start Ubuntu system 2. Log into session 3. Open gnome-terminal 4. Run 'who' command Expected result: You should see TWO entries (the first is from LightDM, the second is from gnome-terminal): tty7 -MM-DD HH:MM pts/0 -MM-DD HH:MM (:0) Observed result: You see only one entry: pts/0 -MM-DD HH:MM (:0) Regression potential: Bugs in utmp code cause cause issues logging in To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
The package in precise-proposed works for me. lightdm 1.2.1-0ubuntu1.1 ltirkkon tty7 2012-07-17 10:33 10:34:34 up 37 min, 1 user, load average: 0.55, 0.53, 0.49 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT ltirkkon tty7 10:33 37:24 1.13s 0.09s /bin/sh /etc/xd However, the included pam config doesn't stack pam_lastlog, so wtmp is still not being updated (it should show my desktop session as 'still logged in'): flashman ~ % ssh root@test-precise 'dpkg-query --show lightdm && last -n1' lightdm 1.2.1-0ubuntu1.1 root pts/0flashman Tue Jul 17 10:32 - 10:32 (00:00) wtmp begins Fri Jul 13 19:23:13 2012 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in Light Display Manager: Fix Released Status in “lightdm” package in Ubuntu: Fix Committed Status in “lightdm” source package in Oneiric: Triaged Status in “lightdm” source package in Precise: Triaged Bug description: Impact: Systems using LightDM have no entries in the utmp record for logins, so tools like 'w' and 'who' do not show LightDM sessions. Testcase: 1. Start Ubuntu system 2. Log into session 3. Open gnome-terminal 4. Run 'who' command Expected result: You should see TWO entries (the first is from LightDM, the second is from gnome-terminal): tty7 -MM-DD HH:MM pts/0 -MM-DD HH:MM (:0) Observed result: You see only one entry: pts/0 -MM-DD HH:MM (:0) Regression potential: Bugs in utmp code cause cause issues logging in To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
** Branch linked: lp:~lotheac/lightdm/utmpx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Oneiric: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: When logged into a graphical session, I get no acknowledgement from who, w or last that I am logged in: $ who $ w 16:48:14 up 1 day, 1:08, 0 users, load average: 0.68, 0.83, 0.84 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT last only reports tty logins, not graphical logins. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Fri Oct 7 16:47:23 2011 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
Okay. I moved the branch based on ubuntu/precise/lightdm to lp:~lotheac/lightdm/utmpx_precise and the one based on upstream is lp:~lotheac/lightdm/utmpx. Upstream doesn't have debian/lightdm.pam though (since it's packaging stuff), so that should still be merged to the Ubuntu branch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Oneiric: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: When logged into a graphical session, I get no acknowledgement from who, w or last that I am logged in: $ who $ w 16:48:14 up 1 day, 1:08, 0 users, load average: 0.68, 0.83, 0.84 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT last only reports tty logins, not graphical logins. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Fri Oct 7 16:47:23 2011 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
Ok, now that I've finally figured out how exactly lightdm works in this
regard, I've pushed my changes to lp:~lotheac/lightdm/utmpx.
At first, I was trying to check for XDG_SESSION_CLASS_USER, but it seems
that is never set. The authentication session (which talks to the
greeter) has no class, and that same session is used to start the
user's process (hence it needs PAM very much). If authentication fails,
the authentication session is restarted. I just check if we're a greeter
after authentication, and if so, skip pam_{open,close}_session and write
the utmpx entry.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
Status in Light Display Manager:
Confirmed
Status in “lightdm” package in Ubuntu:
Triaged
Status in “lightdm” source package in Oneiric:
Confirmed
Status in “lightdm” source package in Precise:
Confirmed
Bug description:
When logged into a graphical session, I get no acknowledgement from
who, w or last that I am logged in:
$ who
$ w
16:48:14 up 1 day, 1:08, 0 users, load average: 0.68, 0.83, 0.84
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
last only reports tty logins, not graphical logins.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: lightdm 1.0.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Fri Oct 7 16:47:23 2011
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3)
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
Sebastien, yeah, that's the issue. I'm working on skipping PAM for user sessions right now, actually, but it's probably going to be a little ugly since I'm trying to keep the changes small. On a side note, does lightdm have an IRC channel this could be discussed in? I couldn't seem to find a reference to one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Oneiric: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: When logged into a graphical session, I get no acknowledgement from who, w or last that I am logged in: $ who $ w 16:48:14 up 1 day, 1:08, 0 users, load average: 0.68, 0.83, 0.84 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT last only reports tty logins, not graphical logins. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Fri Oct 7 16:47:23 2011 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
... sorry, that should be "skipping PAM for non-user sessions" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Oneiric: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: When logged into a graphical session, I get no acknowledgement from who, w or last that I am logged in: $ who $ w 16:48:14 up 1 day, 1:08, 0 users, load average: 0.68, 0.83, 0.84 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT last only reports tty logins, not graphical logins. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Fri Oct 7 16:47:23 2011 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
Ok, but what about PAM? Greeters should run as the same user lightdm does, so authentication is already skipped for them (do_authenticate is false), but do pam_open_session or pam_acct_mgmt make sense? If we skip pam_open_session for greeters, we can use pam_lastlog for actual user sessions, but I'm thinking we should skip PAM altogether if it's not an actual user session. That would require some refactoring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lightdm” source package in Oneiric: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: When logged into a graphical session, I get no acknowledgement from who, w or last that I am logged in: $ who $ w 16:48:14 up 1 day, 1:08, 0 users, load average: 0.68, 0.83, 0.84 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT last only reports tty logins, not graphical logins. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Fri Oct 7 16:47:23 2011 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
Robert, but that wouldn't help for wtmp/lastlog, since pam is still used. Is there a reason it is for greeters, though, and should greeters really have a consolekit session either? Couldn't we just simply fork without doing most of the stuff in session_child_run if we're starting a greeter? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lightdm” source package in Oneiric: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: When logged into a graphical session, I get no acknowledgement from who, w or last that I am logged in: $ who $ w 16:48:14 up 1 day, 1:08, 0 users, load average: 0.68, 0.83, 0.84 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT last only reports tty logins, not graphical logins. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Fri Oct 7 16:47:23 2011 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
I've written a patch that updates utmp and uses pam_lastlog for wtmp. It seems to work: root@test-precise:~# w 18:22:27 up 1:16, 2 users, load average: 2.44, 1.03, 0.68 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT root pts/0remotehost 17:060.00s 3.40s 0.01s w lotheac tty7 18:231:17m 1.07s 0.67s awesome But, there's a problem: since the greeter session is started the same way as the user session, we get unnecessary entries by the lightdm user when the login screen is visible: root@test-precise:~# who root pts/02012-04-19 17:06 (this is an ssh session) lightdm tty7 2012-04-19 18:05 root@test-precise:~# w 18:06:50 up 1:00, 2 users, load average: 0.59, 0.41, 0.42 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT root pts/0remotehost 17:060.00s 3.03s 0.01s w lightdm tty7 18:051:00m 0.36s 0.01s /bin/sh /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/lightdm-gtk-greeter root@test-precise:~# last -n3 lightdm :0Thu Apr 19 18:05 still logged in lotheac :0Thu Apr 19 17:56 - 18:05 (00:09) lightdm :0Thu Apr 19 17:56 - 17:56 (00:00) wtmp begins Mon Apr 16 14:40:28 2012 I don't think greeter sessions should be handled identically to user sessions; I'm not sure why it needs to go through the pam stack at all. Maybe someone more familiar with lightdm can shed some light on this? The attached patch isn't finished, since it introduces the issue described above. ** Patch added: "update utmp on session start and use pam_lastlog to record wtmp/lastlog" https://bugs.launchpad.net/ubuntu/oneiric/+source/lightdm/+bug/870297/+attachment/3094021/+files/utmp.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lightdm” source package in Oneiric: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: When logged into a graphical session, I get no acknowledgement from who, w or last that I am logged in: $ who $ w 16:48:14 up 1 day, 1:08, 0 users, load average: 0.68, 0.83, 0.84 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT last only reports tty logins, not graphical logins. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Fri Oct 7 16:47:23 2011 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870297] Re: Lightdm logins not being logged in wtmp
I looked into this a bit. There is a pam module that updates lastlog and wtmp (pam_lastlog(8)), which could be stacked in the lightdm pam config. It doesn't update utmp, however, and utmp is what w(1) and who(1) look at -- see the discussion at http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=659957. I guess as it stands, lightdm needs to write the utmp entry, like login(1), since nothing else does. I also propose to add the pam_lastlog module to lightdm's stack to keep lastlog and wtmp up to date. ** Bug watch added: Debian Bug tracker #659957 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659957 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lightdm” source package in Oneiric: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: When logged into a graphical session, I get no acknowledgement from who, w or last that I am logged in: $ who $ w 16:48:14 up 1 day, 1:08, 0 users, load average: 0.68, 0.83, 0.84 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT last only reports tty logins, not graphical logins. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Fri Oct 7 16:47:23 2011 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 960157] [NEW] lightdm exits on SIGHUP
Public bug reported: Steps to reproduce: service lightdm reload Expected: lightdm reloads configuration without exiting Actual: lightdm exits, taking the X server with it, killing any user session Even if config refresh isn't supported, lightdm should not quit when it receives SIGHUP, or reloading the service will have the same effect as stopping it -- definitely not optimal with remotely managed workstations. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/960157 Title: lightdm exits on SIGHUP Status in “lightdm” package in Ubuntu: New Bug description: Steps to reproduce: service lightdm reload Expected: lightdm reloads configuration without exiting Actual: lightdm exits, taking the X server with it, killing any user session Even if config refresh isn't supported, lightdm should not quit when it receives SIGHUP, or reloading the service will have the same effect as stopping it -- definitely not optimal with remotely managed workstations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/960157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885984] Re: Can not log in when homedir permissions are set `o-x`
*** This bug is a duplicate of bug 877766 *** https://bugs.launchpad.net/bugs/877766 Sorry, missed that this bug is a duplicate (and that the other bug already has a fix the comments). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/885984 Title: Can not log in when homedir permissions are set `o-x` Status in “lightdm” package in Ubuntu: New Bug description: When mounting home directories over NFS with root squashing, users with home directories with the execute bit unset for other (i.e. `chmod o-x $HOME`) will not be able to log in via lightdm. The log in appears to be successful, the screen blinks, and then the log in screen returns. Users should be able to log in via lightdm in a root- squashed environment without requiring the execute bit set for everyone on the home directory. $ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 $ apt-cache policy lightdm lightdm: Installed: 1.0.1-0ubuntu6 Candidate: 1.0.1-0ubuntu6 Version table: *** 1.0.1-0ubuntu6 0 500 http://mirrors.cat.pdx.edu/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status ==> /var/log/lightdm/lightdm.log <== [+4245.45s] DEBUG: Opened ConsoleKit session 45a196b38946d744fc2450aa038d-1320380637.865888-1199086430 [+4245.45s] DEBUG: Dropping privileges to uid 11248 [+4245.45s] DEBUG: Adding session authority to /u/jesusaur/.Xauthority [+4245.47s] DEBUG: Restoring privileges [+4245.47s] DEBUG: Launching process 10563: /usr/sbin/lightdm-session 'gnome-session --session=ubuntu' [+4245.47s] WARNING: Failed to change to home directory /u/jesusaur: Permission denied [+4245.48s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session11 [+4245.48s] DEBUG: Process 10563 exited with return value 1 ==> /var/log/auth.log <== Nov 3 21:23:57 sizeof lightdm: pam_unix(lightdm:session): session closed for user jesusaur To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/885984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885984] Re: Can not log in when homedir permissions are set `o-x`
*** This bug is a duplicate of bug 877766 *** https://bugs.launchpad.net/bugs/877766 Attached patch fixes this issue by changing directory after (not before) changing uid. ** Patch added: "chdir-after-setuid.patch" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/885984/+attachment/2723589/+files/chdir-after-setuid.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/885984 Title: Can not log in when homedir permissions are set `o-x` Status in “lightdm” package in Ubuntu: New Bug description: When mounting home directories over NFS with root squashing, users with home directories with the execute bit unset for other (i.e. `chmod o-x $HOME`) will not be able to log in via lightdm. The log in appears to be successful, the screen blinks, and then the log in screen returns. Users should be able to log in via lightdm in a root- squashed environment without requiring the execute bit set for everyone on the home directory. $ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 $ apt-cache policy lightdm lightdm: Installed: 1.0.1-0ubuntu6 Candidate: 1.0.1-0ubuntu6 Version table: *** 1.0.1-0ubuntu6 0 500 http://mirrors.cat.pdx.edu/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status ==> /var/log/lightdm/lightdm.log <== [+4245.45s] DEBUG: Opened ConsoleKit session 45a196b38946d744fc2450aa038d-1320380637.865888-1199086430 [+4245.45s] DEBUG: Dropping privileges to uid 11248 [+4245.45s] DEBUG: Adding session authority to /u/jesusaur/.Xauthority [+4245.47s] DEBUG: Restoring privileges [+4245.47s] DEBUG: Launching process 10563: /usr/sbin/lightdm-session 'gnome-session --session=ubuntu' [+4245.47s] WARNING: Failed to change to home directory /u/jesusaur: Permission denied [+4245.48s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session11 [+4245.48s] DEBUG: Process 10563 exited with return value 1 ==> /var/log/auth.log <== Nov 3 21:23:57 sizeof lightdm: pam_unix(lightdm:session): session closed for user jesusaur To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/885984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
