Bug#965164: policykit-1: fails to install
Package: policykit-1 Version: 0.105-27 Followup-For: Bug #965164 I confirm the bug. I did a dist-up anyway. Now, no sound via pulseaudio, mocp in/decreasing volume not working, cmus won't play audio files... Not sure what kind of info i can provide :) Cheers " apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up policykit-1 (0.105-27) ... chown: cannot access '/usr/lib/policykit-1/polkit-agent-helper-1': No such file or directory dpkg: error processing package policykit-1 (--configure): installed policykit-1 package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: policykit-1 Error: Timeout was reached E: Sub-process /usr/bin/dpkg returned an error code (1) " -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES:es Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages policykit-1 depends on: ii dbus 1.12.20-1 ii libc62.31-1 ii libexpat12.2.9-1 ii libglib2.0-0 2.64.4-1 ii libpam-systemd [logind] 245.6-3 ii libpam0g 1.3.1-5 ii libpolkit-agent-1-0 0.105-27 ii libpolkit-gobject-1-00.105-27 ii libsystemd0 245.6-3 policykit-1 recommends no packages. policykit-1 suggests no packages. Versions of packages policykit-1 is related to: pn elogind pn libpam-elogind ii libpam-systemd 245.6-3 ii systemd 245.6-3 -- no debconf information
Bug#889028: minissdpd: Fails to install on Debian unstable
Package: minissdpd Version: 1.5.20161216-1 Followup-For: Bug #889028 Dear Maintainer, I just wanted to confirm the bug. So, upgrading from minissdpd:amd64 1.2.20130907-4.1 to 1.5.20161216-1 I got "Error: Sub-process /usr/bin/dpkg returned an error code (1)". Same error after purging the buggy pkg and reinstalling it. systemctl status minissdpd "Loaded: loaded (/lib/systemd/system/minissdpd.service; disabled; vendor preset: enabled)Active: inactive (dead)" Cheers, Awtul *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES:es (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages minissdpd depends on: ii libc6 2.26-6 ii libnfnetlink0 1.0.1-3+b1 ii lsb-base 9.20170808 minissdpd recommends no packages. minissdpd suggests no packages. -- no debconf information
Bug#886743: virtualbox-dkms now requires package libelf-dev to work
Package: linux-headers-4.14.0-3-amd64 Version: 4.14.12-2 Followup-For: Bug #886743 Dear Maintainer(s), I just wanted to confirm this bug and say that when I execute "VBoxManage clonehd --format RAW Debian-Sid-amd64-2.vdi Debian-Sid-amd64-2.raw" I get the following: "WARNING: The character device /dev/vboxdrv does not exist. Please install the virtualbox-dkms package and the appropriate headers, most likely linux-headers-amd64. You will not be able to start VMs until this problem is fixed. VBoxManage: error: Could not find file for the medium '/home/my-user/Debian-Sid-amd64-2.vdi' (VERR_FILE_NOT_FOUND) VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component MediumWrap, interface IMedium, callee nsISupports VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 179 of file VBoxManageDisk.cpp". "apt-get install --reinstall virtualbox virtualbox-dkms virtualbox-qt" fails and in /var/lib/dkms/virtualbox/5.2.4/build/make.log I see "DKMS make.log for virtualbox-5.2.4 for kernel 4.14.0-3-amd64 (x86_64) jue ene 11 00:11:10 EST 2018 make: se entra en el directorio '/usr/src/linux-headers-4.14.0-3-amd64' /usr/src/linux-headers-4.14.0-3-common/Makefile:947: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel". Alto. Makefile:146: fallo en las instrucciones para el objetivo 'sub-make' make[1]: *** [sub-make] Error 2 Makefile:8: fallo en las instrucciones para el objetivo 'all' make: *** [all] Error 2 make: se sale del directorio '/usr/src/linux-headers-4.14.0-3-amd64'" Cheers, Awtul -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES:es (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-headers-4.14.0-3-amd64 depends on: ii linux-compiler-gcc-7-x86 4.14.12-2 ii linux-headers-4.14.0-3-common 4.14.12-2 ii linux-kbuild-4.14 4.14.12-2 linux-headers-4.14.0-3-amd64 recommends no packages. linux-headers-4.14.0-3-amd64 suggests no packages. -- no debconf information
Bug#855168: olvwm crashes traying to log in X
Package: olvwm Version: 4.4.3.2p1.4-28.2 Severity: grave Justification: renders package unusable Dear Maintainer, Olvwm crashes trying to log in X, using startx or wdm. No trace of it in xsession-errors/Xorg logs. I only found the following in /var/log/syslog and journalctl: - syslog: kernel: [ 151.441615] olvwm[1112]: segfault at 44c51dd0 ip 55634411d3ed sp 7ffc19538b50 error 6 in olvwm[556344107000+62000] - journalctl: kernel: olvwm[1112]: segfault at 44c51dd0 ip 55634411d3ed sp 7ffc19538b50 error 6 in olvwm[556344107000+62000] Note that I'm not an olwm user; no clue on how to debug it. Cheers, Awtul -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores) 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 olvwm depends on: ii libc6 2.24-9 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1 ii libxpm4 1:3.5.12-1 olvwm recommends no packages. Versions of packages olvwm suggests: ii menu 2.1.47 ii olwm 3.2p1.4-28.2 pn xview-clients -- no debconf information
Bug#855167: olwm crashes trying to log in X
Package: olwm Version: 3.2p1.4-28.2 Severity: grave Justification: renders package unusable Dear Maintainer, Olwm crashes trying to log in X, using startx or wdm. No trace of it in xsession-errors/Xorg logs. I only found the following in /var/log/syslog and journalctl: - syslog: kernel: [ 1548.393919] olwm[7906]: segfault at 1fe16138 ip 7f1e6f4234c7 sp 7fff3bf47f10 error 4 in libX11.so.6.3.0[7f1e6f394000+13a000] - journalctl: kernel: olwm[983]: segfault at 82233138 ip 7f64327a84c7 sp 7ffe9cd18a80 error 4 in libX11.so.6.3.0[7f6432719000+13a000] Note that I'm not an olwm user; no clue on how to debug it. Cheers, Awtul -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores) 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 olwm depends on: ii libc6 2.24-9 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1 ii xviewg3.2p1.4-28.2 olwm recommends no packages. Versions of packages olwm suggests: ii menu 2.1.47 pn xview-clients -- no debconf information
Bug#833643: update-pepperflashplugin-nonfree --install fails
I confirm the bug. Same error, here: "update-pepperflashplugin-nonfree --verbose --install options : --verbose --install -- temporary directory: /tmp/pepperflashplugin-nonfree.pdrBjpz0EQ doing apt-get update on google repository cleaning up temporary directory /tmp/pepperflashplugin-nonfree.pdrBjpz0EQ ... ERROR: failed to retrieve status information from google : E: flAbsPath on ./var/lib/dpkg/status failed - realpath (2: No existe el fichero o el directorio) E: No pude abrir el fichero - open (2: No existe el fichero o el directorio) E: Problem opening E: No se pudieron analizar o abrir las listas de paquetes o el archivo de estado. More information might be available at: http://wiki.debian.org/PepperFlashPlayer; -- apt-cache policy pepperflashplugin-nonfree pepperflashplugin-nonfree: Instalados: 1.8.2+nmu1 Candidato: 1.8.2+nmu1 Tabla de versión: *** 1.8.2+nmu1 500 500 http://ftp.ca.debian.org/debian unstable/contrib amd64 Packages 100 /var/lib/dpkg/status Cheers, Awtul
