Bug#874385: Debian Bug report logs - #874385,debian 9.1.0 fails to install
I have encountered the same failure reusing a partition scheme to (re)install Debian 9.5.0 from either USB or netboot. The file that tar "can't open" is different on each attempt, and ensuring that partman erases the partitions does not seem to help.
Bug#890968: network-manager-openvpn: does not save private key
Package: network-manager-openvpn Version: 1.8.0-2 Followup-For: Bug #890968 I'm finding the same behavior, but additionally the "User certificate" field is overwritten withe value from the "CA certificate" field. This is happening with multiple VPN defintions, and happens whether they were created before upgrading packages, newly imported from a .ovpn file, or defined manually through the UI. The issues recurs if I delete the definition and recreate it. Openvpn on the command line is working fine, but network-manager-openvpn is currently unuseable for me. -- System Information: Debian Release: kali-rolling APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-kali3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager-openvpn depends on: ii adduser 3.117 ii libc62.26-6 ii libglib2.0-0 2.54.3-2 ii libnm0 1.10.4-1+b1 ii network-manager 1.10.4-1+b1 ii openvpn 2.4.4-2 network-manager-openvpn recommends no packages. network-manager-openvpn suggests no packages. -- no debconf information
Bug#736243: network-manager-openvpn-gnome: Can not set certificates properly
Package: network-manager-openvpn Version: 1.8.0-2 Followup-For: Bug #736243 Dear Maintainer, I'm seeing the same behavior in kali-rolling (based on stretch). Whether I import the config from an .ovpn file or enter it by hand, every time I save it with network-manager-ovpn it appears to save as: CA certficate: ca.crt User certificate: ca.crt User private key: (None) This is of course unusable. The same config (with the correct user certificate and private key) works with openvpn on the command line. -- System Information: Debian Release: kali-rolling APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-kali3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager-openvpn depends on: ii adduser 3.117 ii libc62.26-6 ii libglib2.0-0 2.54.3-2 ii libnm0 1.10.4-1 ii network-manager 1.10.4-1 ii openvpn 2.4.4-2 network-manager-openvpn recommends no packages. network-manager-openvpn suggests no packages. -- no debconf information
Bug#837637: Audio settings often reset to 100% Volume
On Wed, 18 Jan 2017 14:10:49 -0300 Felipe Sateler wrote: > > The volume is reset by applications that try to set the master volume > to 100%. Most applications don't try doing that anymore. How can this be prevented? It seems like a health and safety issue, since sounds played at 100% volume can damage audio equipment or even cause hearing loss. In my experience there is no indication of what application is changing the master volume or why it is permitted to do so without user intervention.
