[Bug 1655584] [NEW] systemd-udevd busyloops when nvidia kernel module fails to load
Public bug reported: On a machine where nvidia-367 is installed, but the driver won't attach (due to the nvidia card being older and requiring legacy drivers), systemd-udevd repeatedly attempts to load it anyway, causing high CPU and memory usage. I observed the systemd-udevd process at 98% CPU usage and 2.5G RSS reported by top(1); restarting the service reduces resource usage momentarily, but it appears to be climbing back up (I suspect the number of events is growing). Workaround is of course installing the correct driver package, but udevd really ought not behave like this if something fails to load. Some journal entries for systemd-udevd.service: Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' failed with exit code 9. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' failed with exit code 9. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. dmesg shows repeated failures for loading the nvidia module: [1675406.587926] NVRM: The NVIDIA GeForce 9300 GE GPU installed in this system is NVRM: supported through the NVIDIA 340.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM: information. The 367.57 NVIDIA driver will ignore NVRM: this GPU. Continuing probe... [1675406.587936] NVRM: No NVIDIA graphics adapter found! [1675406.588078] NVRM: NVIDIA init module failed! Release information: # lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 # apt policy systemd udev systemd: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu13 Version table: *** 229-4ubuntu13 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial/main amd64 Packages udev: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu13 Version table: *** 229-4ubuntu13 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial/main amd64 Packages ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655584 Title: systemd-udevd busyloops when nvidia kernel module fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1655584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584759 Title: masking NetworkManager ineffective without also masking network- manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1584759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584759] [NEW] masking NetworkManager ineffective without also masking network-manager
Public bug reported:
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.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584759
Title:
masking NetworkManager ineffective without also masking network-
manager
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1584759/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1275796] [NEW] dhcpd dies for unprivileged users
Public bug reported: dhcpd fails to run as an unprivileged user; this is particularly an issue when wanting to syntax-check the config file. Reproducing: $ dhcpd -t -cf /dev/null Expected results: dhcpd checks configuration file (/dev/null used here) and reports errors encountered. Actual results: dhcpd outputs: drop_privileges: could not set group id: Operation not permitted and exits with status 255. Ubuntu 12.04.4 isc-dhcp-server: Installed: 4.1.ESV-R4-0ubuntu5.9 ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275796 Title: dhcpd dies for unprivileged users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1275796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232473] Re: depmod fills disk to 100% with invisible modules.ccwmap
Unfortunately I could not reproduce this after building module-init- tools with debug symbols. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232473 Title: depmod fills disk to 100% with invisible modules.ccwmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232473] Re: depmod fills disk to 100% with invisible modules.ccwmap
We also ran into this on one of our machines. depmod seems to be writing to the file in question in a loop: # strace -s 100 -p $(pgrep depmod) write(3, "0x00\nnvidia_304 0x2887 0xfbad 0x00 0x 0x00\nnvidia_304 0x2887"..., 4096) = 4096 Attaching to process 17565 Reading symbols from /sbin/depmod...(no debugging symbols found)...done. Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...Reading symbols from /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.15.so...done. done. Loaded symbols for /lib/x86_64-linux-gnu/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.15.so...done. done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 0x7fed6ba89040 in __write_nocancel () at ../sysdeps/unix/syscall-template.S:82 82 ../sysdeps/unix/syscall-template.S: No such file or directory. (gdb) bt #0 0x7fed6ba89040 in __write_nocancel () at ../sysdeps/unix/syscall-template.S:82 #1 0x7fed6ba1b883 in _IO_new_file_write (f=0x18164b0, data=0x7fed621c2000, n=4096) at fileops.c:1289 #2 0x7fed6ba1b74a in new_do_write (fp=0x18164b0, data=0x7fed621c2000 "0x00\nnvidia_304", ' ' , "0x2887 0xfbad 0x00 0x 0x00\nnvidia_304", ' ' , "0x2887 0xfbad 0x00 0x 0x00\nnvidia_304", ' ' , "0x2887 0xfbad 0x00 0x 0x00\nnvi"..., to_do=4096) at fileops.c:543 #3 0x7fed6ba1ceb5 in _IO_new_do_write (fp=, data=, to_do=4096) at fileops.c:516 #4 0x7fed6ba1c025 in _IO_new_file_xsputn (n=4, data=, f=0x18164b0) at fileops.c:1371 #5 _IO_new_file_xsputn (f=0x18164b0, data=, n=4) at fileops.c:1305 #6 0x7fed6b9ec4a7 in _IO_vfprintf_internal (s=, format=, ap=) at vfprintf.c:1660 #7 0x7fed6baab80b in ___fprintf_chk (fp=0x18164b0, flag=1, format=) at fprintf_chk.c:37 #8 0x00405a24 in ?? () #9 0x004021a4 in ?? () #10 0x7fed6b9c376d in __libc_start_main (main=0x401770, argc=5, ubp_av=0x7fff69f88ea8, init=, fini=, rtld_fini=, stack_end=0x7fff69f88e98) at libc-start.c:226 #11 0x00402535 in ?? () #12 0x7fff69f88e98 in ?? () #13 0x001c in ?? () #14 0x0005 in ?? () #15 0x7fff69f8ae05 in ?? () #16 0x7fff69f8ae12 in ?? () #17 0x7fff69f8ae26 in ?? () #18 0x7fff69f8ae29 in ?? () #19 0x7fff69f8ae15 in ?? () #20 0x in ?? () I'll build module-init-tools with debug symbols and try to reproduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232473 Title: depmod fills disk to 100% with invisible modules.ccwmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1232473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027805 Title: logins are not recorded in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1027805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666565 Title: "utf8" charmap in locale name is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/666565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027805
Title:
logins are not recorded in wtmp
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1027805/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027805 Title: logins are not recorded in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1027805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in utmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027805 Title: logins are not recorded in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1027805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/870297
Title:
Lightdm logins not being logged in wtmp
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870297 Title: Lightdm logins not being logged in wtmp To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/870297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/960157 Title: lightdm exits on SIGHUP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/960157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792847] Re: run-parts does not seem to reap its children
Ok. I've already stated that the updated version fixes my issue (which I assume is the same as the original issue, not reported by me). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792847 Title: run-parts does not seem to reap its children To manage notifications about this bug go to: https://bugs.launchpad.net/debianutils/+bug/792847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792847] Re: run-parts does not seem to reap its children
So can we get this to oneiric or should I package it myself? In effect, this causes cron.daily not to run the next day if a daemon is restarted by unattended-upgrades. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792847 Title: run-parts does not seem to reap its children To manage notifications about this bug go to: https://bugs.launchpad.net/debianutils/+bug/792847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792847] Re: run-parts does not seem to reap its children
I think the original problem reported was caused by apt restarting a daemon after installing/upgrading a package -- at least I think that's what happened to me. Vladimir, check your apt logs if it upgraded a package when this problem occurred. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792847 Title: run-parts does not seem to reap its children To manage notifications about this bug go to: https://bugs.launchpad.net/debianutils/+bug/792847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792847] Re: run-parts does not seem to reap its children
Here's a test case: a program that forks a longer running process (could be a daemon) and exits. debianutils 4.0.2 is buggy, and waits until the forked program exits: % run-parts --report . & sleep 1 && ps xf [1] 2742 PID TTY STAT TIME COMMAND 28460 ?S 0:00 sshd: ltirkkon@pts/0 28461 pts/0Ss 0:00 \_ -zsh 2742 pts/0SN 0:00 \_ run-parts --report . 2744 pts/0ZN 0:00 | \_ [fork-sleeper] 2746 pts/0R+ 0:00 \_ ps xf 2745 pts/0SN 0:00 ./fork-sleeper 4.2.1ubuntu1 fixes this issue: % run-parts --report . & sleep 1 && ps xf [1] 1952 [1] + done run-parts --report . PID TTY STAT TIME COMMAND 28460 ?S 0:00 sshd: ltirkkon@pts/0 28461 pts/0Ss 0:00 \_ -zsh 1956 pts/0R+ 0:00 \_ ps xf 1955 pts/0SN 0:00 ./fork-sleeper ** Attachment added: "testcase program that forks a longer running process and exits" https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/792847/+attachment/2745918/+files/fork-sleeper.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792847 Title: run-parts does not seem to reap its children To manage notifications about this bug go to: https://bugs.launchpad.net/debianutils/+bug/792847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/885984 Title: Can not log in when homedir permissions are set `o-x` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/885984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/885984 Title: Can not log in when homedir permissions are set `o-x` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/885984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666565] Re: "utf8" charmap in locale name is wrong
Colin's right, of course -- my main issue with this isn't software running locally, but remote systems. That's not trivial though: ssh into some legacy machine, and they might not have compiled your locale at all, or perhaps it's different (such as the case with en_IN). Of course, that's not an Ubuntu bug, but rather a problem with POSIX not separating charmaps from locales. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/666565 Title: "utf8" charmap in locale name is wrong -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666565] Re: "utf8" charmap in locale name is wrong
** Patch added: "Replace '.utf8' with 'UTF-8' in generated locale strings." https://bugs.launchpad.net/bugs/666565/+attachment/1711201/+files/language-selector-localename.patch -- "utf8" charmap in locale name is wrong https://bugs.launchpad.net/bugs/666565 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666565] [NEW] "utf8" charmap in locale name is wrong
Public bug reported:
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
** Affects: language-selector (Ubuntu)
Importance: Undecided
Status: New
--
"utf8" charmap in locale name is wrong
https://bugs.launchpad.net/bugs/666565
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
