Bug#838610: lightdm-gtk-greeter: always uses the last session as default
X-Debbugs-Cc: kh...@wisc.edu Package: lightdm-gtk-greeter Version: 1.8.5-2 Severity: normal Tags: upstream Dear Maintainer, I run a number of computer labs, and use lightdm with the gtk greeter. I haven't had time to patch the code, but have looked through the code. Despite being able to configure a default session for ligthdm, once lightdm has entered and exited a session it stores that selection in its XDG_CACHE_HOME directory. It then uses that saved session as the default for the next time, overriding the default preference. I can see where this might be an ok behavior in a home environment, but in a lab environment it is problematic because users tend to expect the same defaults every time rather than based on the last user. (I've temporarily disabled this by making a link to /dev/null from $XDG_CACHE_HOME/lightdm-gtk-greeter, preventing lightdm-gtk-greeter from creating its state file.) -- System Information: Debian Release: 8.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages lightdm-gtk-greeter depends on: ii libc6 2.19-18+deb8u4 ii libcairo2 1.14.0-2.1+deb8u1 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u5 ii libglib2.0-02.42.1-1+b1 ii libgtk-3-0 3.14.5-1+deb8u1 ii liblightdm-gobject-1-0 1.10.3-3 ii libx11-62:1.6.2-3 Versions of packages lightdm-gtk-greeter recommends: ii desktop-base 8.0.2 ii gnome-icon-theme-symbolic 3.12.0-1 ii gnome-themes-standard 3.14.2.2-1 ii policykit-10.105-8 lightdm-gtk-greeter suggests no packages. -- Configuration Files: /etc/lightdm/lightdm-gtk-greeter.conf changed [not included]
Bug#710975: Acknowledgement (sudo, ldap regression in Debian 7.0 (Wheezy))
Hello, I haven't heard anything regarding the regression in this package in Debian (are regressions a priority?), but I wanted to note that this regression has made its way into squeeze backports. This week we had our FAI messed up for a bit and installed a version of squeeze that gave priority to squeeze-backports and it then had the same behavior delivered here. Is there a possibility of a fix coming in wheezy? Thanks, -Ken Hahn -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717684: Patch
Hi,
On 10/07/2013 02:19 PM, Thomas Lange wrote:
> Here's the patch, that adds support for LV Path in this library.
> Later I will also adjust setup-storage in FAI.
>
Not sure if applies, but be aware that the field LV Name changes
depending on the kernel underneath it.. the contents of LV Path used to
be in LV Name, with no equivalent of LV Name existing.
I'm not certain where the point of demarcation is when the switch
occurred. You may want to chase down that information and populate LV
Path with a copy of LV Name if kernel version is low enough.
That said, I'm not sure if this module should account for the switch, or
if one level up (in the caller) the change in field definition should be
detected and accounted for.
That said, you're doing the work that I don't have a chance to do :)
This is already better than what it was doing. Thanks!
Cheers,
-Ken Hahn
>
> --- LVM.pm2012-02-08 23:51:49.0 +0100
> +++ /home/lange/LVM.pm2013-10-07 21:15:10.935908675 +0200
> @@ -288,9 +288,14 @@
> $vghash{$vgn}->{uuid} = $1;
> next VGINF; }
>
> +# Parse the logical path name.
> +elsif( m/LV Path\s+(\S+)/ ) {
> +$lvn = $1;
> +$vghash{$vgn}->{lvols}->{$lvn}->{path} = $1;
> +next VGINF; }
> +
> # Parse the logical volume name.
> elsif( m/LV Name\s+(\S+)/ ) {
> -$lvn = $1;
> $vghash{$vgn}->{lvols}->{$lvn}->{name} = $1;
> next VGINF; }
>
>
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717691: fai-setup-storage fails when trying to preserve LVM partitions
Package: fai-setup-storage Version: 4.0.6 Severity: important fai-setup-storage fails when trying to do an install to a machine using lvm when a partition is requested to be preserved. This is a regression from fai-setup-storage 3.4.8 where this worked fine (i.e. in squeeze) I actually believe it has a problem any time the hard disk previously contains an lvm volumegroup, but I haven't got time to test this configuration. I've talked on the upstream users' mailing list a bit and there appears to be a number of issues. First, setup-storage depends on liblinux-lvm-perl While that library has been redone, both versions of it just seems to pass through the same problem. The ultimate problem is that logical volume information is derived from executing the "vgdisplay -v" command. The output from this command has changed between squeeze and wheezy. The older version of this command has fewer fields. snippet of older output: LV Name/dev/vg/var VG Namevg snippit of newer output: LV Path/dev/vg/var LV Namevar VG Namevg They've added a field, and changed what is contained in the old named field. I've filed a bug with liblinux-lvm-perl about the fact that they don't pass on LV Path. Even after fixing the problem with liblinux-lvm-perl, setup-storage has problems with wipefs. In my case I error out with: Executing: wipefs -a vg/fscache ... wipefs: error: vg/fscache: probing initialization failed I don't see how that code ever could have worked because I don't think that $vg/$lv could ever be a valid path for the wipefs command. This is clearly what the code is trying to do. Since the fai-setup-storage code appears to be in a bit of trouble (somebody made a bunch of commits back in 2011 and hasn't been back to clean it up), I have managed to kludge 3.4.8 fai-setup-storage to work with the 4.0.6 fai packages for my local needs. I've recommended the following on the fai-users mailing list: 1. liblinux-lvm-perl be changed to pass the new LV Path field. 2. downgrade fai-setup-storage back to a known working version (3.4.8?) 3. fix the logic in fai-setup-storage to deal with the multiple fields for the LV in the manner described by Thomas Neumann on the fai-users mailing list. I'm not sure how the Debian package should go forward, but I wanted to make you aware of the problem. Let me know if I can provide further information. -Ken Hahn -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717684: liblinux-lvm-storage doesn't pass the LV Path field
Package: liblinux-lvm-perl Version: 0.16-1 Severity: important Hello, I've been trying to debug issues in fai-setup-storage using lvm partitions, and in the process I found that they use your module. The ultimate problem is that logical volume information is derived from executing the "vgdisplay -v" command within your module. The output from this command has changed between squeeze and wheezy. The older version of this command has fewer fields. snippet of older output: LV Name/dev/vg/var VG Namevg snippit of newer output: LV Path/dev/vg/var LV Namevar VG Namevg Ultimately they have a logic problem because between squeeze and wheezy lvm apparently added a field and redefined the meaning for the old field. That said, your module needs to pass through the new field for any user of the module to get accurate information, and I don't believe that the code is there to do so. Thanks for supporting the module, and effort you put towards the fix, -Ken Hahn -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714869: /usr/sbin/fai incorrectly removes mapping lines from /etc/idmapd.conf from install root image.
Package: fai-client Version: 4.0.6 Severity: important Hello, When using fai-client, the file, /etc/idmapd.conf is incorrectly created/altered to exist without entries for Nobody-User, and Nobody-Group. (If the nfs root provides this file, the entries for these will be removed.) In particular the program /usr/sbin/fai contains the following code: [ "$FAI_ROOT" = '/' ] && ROOTCMD= target=$FAI_ROOT AINSL_TARGET=$FAI_ROOT ... # NFS v4 support sed -i -e '/Nobody-/d' /etc/idmapd.conf ainsl -v /etc/idmapd.conf 'Nobody-User = root' ainsl -v /etc/idmapd.conf 'Nobody-Group = root' At the point this is run, my understanding is that the AINSL_TARGET isn't set up properly. The effect is that the sed removes the lines from idmapd.con, and then the ainsl lines that should add it back in, instead indicate that the file to change doesn't exist. I don't believe ainsl should be used here (and even if it was right here, it then makes the sed incorrect, because the sed file name isn't prefixed with the target. In my case, I have a hook called confdir.DEFAULT that attempts to get idmapd going before I map the config space. basically containing the following: modprobe nfsd mount -t rpc_pipefs rpc_pipefs /var/lib/nfs/rpc_pipefs /usr/sbin/rpc.idmapd -v This, along with the breakage in the idmapd.conf file ends up with the following error in fai.log: Calling hook: confdir.DEFAULT rpc.idmapd: Could not find group "nobody" confdir.DEFAULT FAILED with exit code 1. Calling task_confdir -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#710975: sudo, ldap regression in Debian 7.0 (Wheezy)
Package: libpam-ldap Version: 184-8.6 |Severity: important| Hello, When I attempt to use libpam-ldap to authenticate sudo I get the following error: $sudo su - sudo: PERM_ROOT: setresuid(0, -1, -1): Operation not permitted sudo: account validation failure, is your account locked? I'm not able to use pam-ldapd because our setup uses pam-ldap's "config=" option to specify different configurations (pam_filter is being varied), in order to provide different semantics (e.g. authorization filters, different ou's for passwords, etc.) per service. I believe this is a regression because I was able to do this under Debian 6.0.7, but get this error under Debian 7.0. Here is a subset of the relevant configuration files (we do this for more than sudo, such as cron, dovecot, smtp, etc.) with some security related items removed (e.g. bindpw). libpam_ldap.conf: base o=ENGR uri ldaps://ldap.engr.wisc.edu ldap_version 3 timelimit 15 bind_timelimit 10 bind_policy hard pam_filter caeacl=unix-lab pam_password crypt nss_base_passwdou=People,o=ENGR?one nss_base_shadowou=People,o=ENGR?one nss_base_groupou=Group,o=ENGR?one nss_base_netgroupou=Netgroup,o=ENGR tls_checkpeer yes libpam_ldap.conf.sudo: base o=ENGR uri ldaps://ldap.engr.wisc.edu ldap_version 3 binddn cn=proxyagent,ou=profile,o=ENGR timelimit 15 bind_timelimit 10 bind_policy hard pam_filter caeacl=sudo pam_password crypt nss_base_passwdou=Sudo,o=ENGR?one nss_base_shadowou=Sudo,o=ENGR?one nss_base_groupou=Group,o=ENGR?one nss_base_netgroupou=Netgroup,o=ENGR ssl on tls_checkpeer yes /etc/pam.d/common-account: accountrequired pam_access.so account [success=1 default=ignore] pam_unix.so account required pam_ldap.so account required pam_permit.so /etc/pam.d/common-auth: auth required pam_group.so auth [success=1 default=ignore] pam_unix.so auth required pam_ldap.so use_first_pass auth required pam_permit.so /etc/pam.d/sudo: auth required pam_group.so auth [success=1 default=ignore] pam_unix.so auth required pam_ldap.so use_first_pass config=/etc/pam_ldap.conf.sudo auth required pam_permit.so account [success=1 default=ignore] pam_unix.so account required pam_ldap.so config=/etc/pam_ldap.conf.sudo account required pam_permit.so session required pam_permit.so session required pam_limits.so Relavent Package versions: ii ldap-utils 2.4.23-7.3 OpenLDAP utilities ii libauthen-pam-perl 0.16-2 Perl interface to PAM library ii libgksu2-0 2.0.13~pre1-3 library providing su and sudo functionality ii libkldap4 4:4.4.5-2 library for accessing LDAP ii libldap-2.4-2 2.4.23-7.3 OpenLDAP libraries ii libldap2-dev 2.4.23-7.3 OpenLDAP development libraries ii libnet-ldap-perl 1:0.4001-2 client interface to LDAP servers ii libnss-ldap 264-2.2NSS module for using LDAP as a naming service ii libpam-ck-connector 0.4.1-4ConsoleKit PAM module ii libpam-gnome-keyring 2.30.3-5 PAM module to unlock the GNOME keyring upon login ii libpam-krb5 4.3-1 PAM module for MIT Kerberos ii libpam-ldap 184-8.5Pluggable Authentication Module for LDAP ii libpam-modules 1.1.1-6.1+squeeze1 Pluggable Authentication Modules for PAM ii libpam-runtime 1.1.1-6.1+squeeze1 Runtime support for the PAM library ii libpam0g 1.1.1-6.1+squeeze1 Pluggable Authentication Modules library ii sudo 1.7.4p4-2.squeeze.4Provide limited super user privileges to specific users
Bug#691976: gnome-osd-event-bridge will use 100% of the cpu..
Subject: gnome-osd-event-bridge will use 100% of the cpu..
Package: gnome-osd
Version: 0.12.2-1
Severity: normal
*** Please type your report below this line ***
gnome-osd-event-bridge appeasr to go into a pool loop, when it exits
trys to read a unix domain socket nad gets a return indicating resource
temporarily unavailable.
poll([{fd=11, events=POLLIN}, {fd=13, events=POLLIN|POLLPRI}, {fd=15,
events=POLLIN}, {fd=6, events=POLLIN|POLLPRI}, {fd=16,
events=POLLIN|POLLPRI}, {fd=17, events=POLLIN|POLLPRI}, {fd=19,
events=POLLIN|POLLPRI}, {fd=18, events=POLLIN|P$
read(15, 0x14b85d4, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
poll([{fd=11, events=POLLIN}, {fd=13, events=POLLIN|POLLPRI}, {fd=15,
events=POLLIN}, {fd=6, events=POLLIN|POLLPRI}, {fd=16,
events=POLLIN|POLLPRI}, {fd=17, events=POLLIN|POLLPRI}, {fd=19,
events=POLLIN|POLLPRI}, {fd=18, events=POLLIN|P$
read(15, 0x14b85d4, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
poll([{fd=11, events=POLLIN}, {fd=13, events=POLLIN|POLLPRI}, {fd=15,
events=POLLIN}, {fd=6, events=POLLIN|POLLPRI}, {fd=16,
events=POLLIN|POLLPRI}, {fd=17, events=POLLIN|POLLPRI}, {fd=19,
events=POLLIN|POLLPRI}, {fd=18, events=POLLIN|P$
read(15, 0x14b85d4, 4096) = -1 EAGAIN (Resource
temporarily unavailable)
poll([{fd=11, events=POLLIN}, {fd=13, events=POLLIN|POLLPRI}, {fd=15,
events=POLLIN}, {fd=6, events=POLLIN|POLLPRI}, {fd=16,
events=POLLIN|POLLPRI}, {fd=17, events=POLLIN|POLLPRI}, {fd=19,
events=POLLIN|POLLPRI}, {fd=18, events=POLLIN|P$
-- System Information:
Debian Release: 6.0.6
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gnome-osd depends on:
ii gconf2 2.28.1-6 GNOME configuration
database syste
ii python 2.6.6-3+squeeze7 interactive high-level
object-orie
ii python-dbus 0.83.1-1 simple interprocess
messaging syst
ii python-gnome2 2.28.1-1 Python bindings for the
GNOME desk
ii python-gtk2 2.17.0-4 Python bindings for the
GTK+ widge
ii python-pyorbit 2.24.0-6 A Python language binding
for the
ii python-pyorbit-omg 2.24.0-6 PyORBit - Python CORBA OMG
standar
ii python-support 1.0.10 automated rebuilding
support for P
gnome-osd recommends no packages.
Versions of packages gnome-osd suggests:
ii evolution 2.30.3-5 groupware suite with mail
client a
pn muine(no description available)
ii pidgin 2.7.3-1+squeeze3 graphical multi-protocol
instant m
ii rhythmbox 0.12.8-3 music player and organizer
for GNO
ii xchat 2.8.8-3 IRC client for X similar to
AmIRC
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
