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 us
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-en
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
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
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
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
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 m
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 refer
... 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
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, an
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=6599
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
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'
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 resu
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
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?
--
Yo
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.launchp
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
Tit
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 notificat
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 20
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://
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 pac
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
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 recei
** 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:/
*** 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/
*** 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 Ubunt
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.launch
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:
ru
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 r
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 manag
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 Ubu
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 w
** 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
34 matches
Mail list logo
