Bug#969372: uwsgi-emperor: SysV init script does nothing
Package: uwsgi-emperor Version: 2.0.19.1-3+b1 Followup-For: Bug #969372 Hi Thomas, indeed, I have a number of vassals configured, actually I use emperor for web development for several years now. At first, I noticed that the emperor haven't start after reboot. I have tried to start it with systemd, but with no success. Systemd only reports the process as "started" but it's not running (`ps -ef | grep uwsgi`). Here's a relevant output of terminal commands: $ sudo service uwsgi-emperor start $ sudo service uwsgi-emperor status ● uwsgi-emperor.service - LSB: Start/stop uWSGI server instance(s) Loaded: loaded (/etc/init.d/uwsgi-emperor; generated) Active: active (exited) since Fri 2020-11-06 09:23:17 CET; 1s ago Docs: man:systemd-sysv-generator(8) Process: 889151 ExecStart=/etc/init.d/uwsgi-emperor start (code=exited, status=0/SUCCESS) Nov 06 09:23:17 queeg-500 systemd[1]: Starting LSB: Start/stop uWSGI server instance(s)... Nov 06 09:23:17 queeg-500 systemd[1]: Started LSB: Start/stop uWSGI server instance(s). $ ps -ef | grep uwsgi vzima 889177 887414 0 09:23 pts/500:00:00 grep uwsgi Despite this, I can start the emperor manually using command composed on /etc/init.d/uwsgi-emperor: $ sudo /usr/bin/uwsgi --ini /etc/uwsgi-emperor/emperor.ini --die-on-term --pidfile /run/uwsgi-emperor.pid --daemonize /var/log/uwsgi/emperor.log I also encounter the PID file bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934731, so I need to delete PID file manually. Regards, Vlastimil Zíma -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages uwsgi-emperor depends on: ii uwsgi-core 2.0.19.1-3+b1 uwsgi-emperor recommends no packages. uwsgi-emperor suggests no packages. -- Configuration Files: /etc/uwsgi-emperor/emperor.ini changed: [uwsgi] master = true workers = 2 no-orphans = true log-date = true uid = www-data gid = www-data emperor = /etc/uwsgi-emperor/vassals emperor-tyrant = true cap = setgid,setuid -- no debconf information
Bug#969372: uwsgi-emperor: SysV init script does nothing
Package: uwsgi-emperor Version: 2.0.19.1-3 Followup-For: Bug #969372 Dear Maintainer, it seems this bug still exists in 2.0.19.1-3. I've upgraded from 2.0.19.1-1 this morning and since then the uwsgi-emperor can't be started using systemd or /etc/init.d/uwsgi-emperor script. I tried to purge and install the uwsgi-emperor package. The /etc/init.d/uwsgi-emperor still seems to be broken. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages uwsgi-emperor depends on: ii uwsgi-core 2.0.19.1-3 uwsgi-emperor recommends no packages. uwsgi-emperor suggests no packages. -- no debconf information
Bug#944056: i3-wm: i3 ignores system keyboard layouts
Package: i3-wm Version: 4.17.1-1 Severity: normal Tags: l10n Dear Maintainer, I'm trying to setup a i3, but I encountered a problem with keyboard layout setup. Multiple layouts set up in /etc/default/keyboard are ignored by i3 and only 'us' layout is available. On the other hand, keyboard options are respected. I have in /etc/default/keyboard XKBLAYOUT="us,cz" XKBVARIANT=",qwerty" BACKSPACE="guess" XKBMODEL="pc105" XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll,caps:none" but after i3 is started, 'setxkbmap -query' returns rules: evdev model: pc105 layout: us options:grp:alt_shift_toggle,grp_led:scroll,caps:none I'd expect the layouts from the keyborad setup would be used as well. I wasn't able to find another location which would override the keyboard layout. Regards, Vlastimil Zíma -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages i3-wm depends on: ii libc6 2.29-2 ii libcairo2 1.16.0-4 ii libev41:4.27-1 ii libglib2.0-0 2.62.2-1 ii libpango-1.0-01.42.4-7 ii libpangocairo-1.0-0 1.42.4-7 ii libpcre3 2:8.39-12+b1 ii libstartup-notification0 0.12-6 ii libxcb-cursor00.1.1-4 ii libxcb-icccm4 0.4.1-1.1 ii libxcb-keysyms1 0.4.0-1+b2 ii libxcb-randr0 1.13.1-2 ii libxcb-shape0 1.13.1-2 ii libxcb-util0 0.3.8-3+b2 ii libxcb-xinerama0 1.13.1-2 ii libxcb-xkb1 1.13.1-2 ii libxcb-xrm0 1.0-3 ii libxcb1 1.13.1-2 ii libxkbcommon-x11-00.8.4-1 ii libxkbcommon0 0.8.4-1 ii libyajl2 2.1.0-3 ii perl 5.30.0-9 Versions of packages i3-wm recommends: ii fonts-dejavu-core 2.37-1 ii gnome-terminal [x-terminal-emulator] 3.34.2-1 ii libanyevent-i3-perl 0.17-1 ii libjson-xs-perl 4.020-1+b1 ii xfonts-base 1:1.0.5 ii xterm [x-terminal-emulator] 349-1 i3-wm suggests no packages. -- no debconf information
Bug#920900: libicu-dev: Command icu-config disappeared from libicu-dev
Package: libicu-dev Version: 63.1-6 Severity: grave Justification: renders package unusable Dear Maintainer, after upgrading libicu-dev, I can't install PyICU using pip, due to an error: FileNotFoundError: [Errno 2] No such file or directory: 'icu-config': 'icu-config' I found no replacement of the icu-config, hence I assume the file disappeared by an accident. When I downgrade libicu-dev back to 60.2-6, it works. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libicu-dev depends on: ii icu-devtools 63.1-6 ii libc6-dev [libc-dev] 2.28-5 ii libicu63 63.1-6 libicu-dev recommends no packages. Versions of packages libicu-dev suggests: pn icu-doc -- no debconf information
Bug#918624: openvpn: No password prompt under systemd
Package: openvpn Version: 2.4.6-1 Severity: important Dear Maintainer, I have troubles using openvpn. I use private key protected by password, but when I start openvpn through systemd: sudo systemctl start openvpn@work.service no password prompt is requested. When I start openvpn directly using sudo openvpn --config /etc/openvpn/work.conf everything works fine. I'd expect the systemd to ask for password when I start the openvpn service. It used to work for me before reinstall of computer some time ago, but I'm not sure which version of openvpn I had. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openvpn depends on: ii debconf [debconf-2.0] 1.5.69 ii iproute2 4.19.0-2 ii libc6 2.28-2 ii liblz4-1 1.8.2-1 ii liblzo2-2 2.10-0.1 ii libpam0g 1.1.8-3.8 ii libpkcs11-helper1 1.25.1-1 ii libssl1.1 1.1.1a-1 ii libsystemd0240-2 ii lsb-base 10.2018112800 Versions of packages openvpn recommends: ii easy-rsa 3.0.5-1 Versions of packages openvpn suggests: ii openssl 1.1.1a-1 ii resolvconf 1.79 -- Configuration Files: /etc/default/openvpn changed [not included] -- debconf information excluded
Bug#839155: bash: $HOME/.local/bin missing from $PATH again
Package: bash Version: 4.4-1 Severity: normal Dear Maintainer, $HOME/.local/bin is lost from the $PATH again. Bug was previously reported as #820856 and fixed in version 4.3-15, but it is missing again from /etc/skel/.profile. -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bash depends on: ii base-files 9.6 ii dash 0.5.8-2.3 ii debianutils 4.8 ii libc62.23-5 ii libtinfo56.0+20160625-1 Versions of packages bash recommends: ii bash-completion 1:2.1-4.3 Versions of packages bash suggests: pn bash-doc -- no debconf information
