Bug#850511: cpu: 10_support-inetOrgPerson-Schema.patch broken if -C is used for external config file
Package: cpu Version: 1.4.3-12 Severity: important Dear Maintainer, Bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397882 introduced a new configuration option "cn_value" for useradd / usermod / userdel. This enhancement is provided in the 10_support-inetOrgPerson-Schema.patch in Debian. Unfortunately, the short option name used for this option is "C" which is already used to specify a non-default configuration file. As a result, if using a non-default configuration file specified on command line, the CN will be erroneously set to the name of the configuration file. This of course leads to bogus entries being created in LDAP and the inability to create, modify, or delete proper users. As an example, the following command: cpu -C /etc/cpu/cpu-computers.conf useradd -o -d /nonexistent -g computers -s /bin/false pc1$ will result in adding a new user in LDAP whose CN is "/etc/cpu/cpu-computers.conf" instead of "pc1$". The same would be true for usermod and userdel operations. The fix is in fact trivial - a different short option name must be used in the source code. These are the letters that are still available: i, I, j, J, K, O, q, Q, T, W, Y (case sensitive) The change would involve src/plugins/ldap/commandline.c. Many thanks! Best regards, Peter -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages cpu depends on: ii debconf [debconf-2.0] 1.5.59 ii libc6 2.24-8 ii libcrack2 2.9.2-3 ii libldap-2.4-2 2.4.44+dfsg-2 ii ucf3.0036 cpu recommends no packages. cpu suggests no packages. -- debconf information excluded
Bug#850516: gvrng: Permission denied when attempting to run gvrng
Package: gvrng Version: 4.4-2 Severity: normal Dear Maintainer, When attempting to run gvrng, it fails due to permission issues: $ gvrng /usr/games/gvrng: 2: exec: /usr/share/GvRng/gvrng.py: Permission denied It looks like the underlying issue is that the Python script being called is not marked as executable. debian@debian:~$ ls -la /usr/share/GvRng/gvrng.py -rw-r--r-- 1 root root 4749 Jul 24 10:47 /usr/share/GvRng/gvrng.py See also https://bugs.launchpad.net/ubuntu/+source/gvrng/+bug/1027869 for a corresponding bug report in Ubuntu. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gvrng depends on: ii python-glade2 2.24.0-5.1 ii python-gtksourceview2 2.10.1-2 gvrng recommends no packages. gvrng suggests no packages. -- no debconf information -- mvh / best regards Hans Joachim Desserud http://desserud.org
Processed: Re: Processed: light-locker: screen remains black after unlock
Processing control commands: > reassign -1 systemd-shim Bug #846661 [systemd] light-locker: screen remains black after unlock Bug reassigned from package 'systemd' to 'systemd-shim'. No longer marked as found in versions systemd/232-1. Ignoring request to alter fixed versions of bug #846661 to the same values previously set -- 846661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#846661: Processed: light-locker: screen remains black after unlock
On 01/07/2017 06:47 PM, Gedalya wrote: > On the other hand, this did work well in all versions of systemd prior to > 232-1 Misspoke: it came and went several times.
Bug#846661: Processed: light-locker: screen remains black after unlock
On 01/07/2017 06:43 PM, Michael Biebl wrote: >> As stated in the last few messages in this bug report, the problem appears >> exclusively when not using systemd as init. >> At Yves-Alexis's request I confirmed the symptoms do not occur when booting >> with systemd as init. >> >> This is the n'th recurrence of, basically, the same problem, just the added >> issue with light-locker is new. >> In previous times as well, things did work when using systemd as init. > Since the reassign message did not include this information, this was > not clear. > > Thanks for confirming this works with systemd as PID 1. > So this seems to be a problem in the SysV - systemd shim layer, i.e. > systemd-shim. > Reassigning accordingly. > > Word of warning: systemd-shim is orphaned and currently has no > maintainer. So my recommendation would be to stick with systemd-sysv. > On the other hand, this did work well in all versions of systemd prior to 232-1, confirmed specifically with 231-10. Would there be a way, and particularly due to systemd-shim being orphaned, to identify the problem and possibly fix it with systemd? It should go without saying that people who are avoiding systemd (well, trying hard to avoid it, but not being allowed to), are more than aware of systemd's existence, and are consciously choosing to avoid it.
Bug#846661: Processed: light-locker: screen remains black after unlock
Am 08.01.2017 um 00:47 schrieb Gedalya: > On 01/07/2017 06:43 PM, Michael Biebl wrote: >>> As stated in the last few messages in this bug report, the problem appears >>> exclusively when not using systemd as init. >>> At Yves-Alexis's request I confirmed the symptoms do not occur when booting >>> with systemd as init. >>> >>> This is the n'th recurrence of, basically, the same problem, just the added >>> issue with light-locker is new. >>> In previous times as well, things did work when using systemd as init. >> Since the reassign message did not include this information, this was >> not clear. >> >> Thanks for confirming this works with systemd as PID 1. >> So this seems to be a problem in the SysV - systemd shim layer, i.e. >> systemd-shim. >> Reassigning accordingly. >> >> Word of warning: systemd-shim is orphaned and currently has no >> maintainer. So my recommendation would be to stick with systemd-sysv. >> > > On the other hand, this did work well in all versions of systemd prior to > 232-1, confirmed specifically with 231-10. > Would there be a way, and particularly due to systemd-shim being orphaned, to > identify the problem and possibly fix it with systemd? You are asking the wrong audience here, you should ask people using sysvinit as PID 1. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: tagging 846661
Processing commands for cont...@bugs.debian.org: > tags 846661 - moreinfo Bug #846661 [systemd-shim] light-locker: screen remains black after unlock Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 846661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#850577: grub-choose-default does not starts due to python error
Package: grub-choose-default Version: 0.2-6 Severity: important Dear Maintainer, grub-choose-default does not starts errors: root@sinamaica:~# grub-choose-default Using /boot/grub/menu.lst and /boot/grub/default Getting entries Getting default Creating window, might take a second No protocol specified No protocol specified Traceback (most recent call last): File "/usr/sbin/grub-choose-default", line 325, in tk_root = Tk() File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1813, in __init__ self.tk = _tkinter.create(screenName, baseName, className, interactive, wantobjects, useTk, sync, use) _tkinter.TclError: couldn't connect to display ":0" root@sinamaica:~# -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages grub-choose-default depends on: ii grub-legacy [grub] 0.97-70 ii menu2.1.47 ii python 2.7.9-1 ii python-tk 2.7.8-2+b1 grub-choose-default recommends no packages. grub-choose-default suggests no packages. -- no debconf information
