[Touch-packages] [Bug 1825485] [NEW] It requires two dependencies that are in conflict (libqt5core5a and qtbase-abi)
Public bug reported: It requires two dependencies that are in conflict (libqt5core5a and qtbase-abi-5-2-1) and according to I saw at https://pkgs.org/download /qtbase-abi-5-2-1 it is included in libqt5core5a. And I can not install (libqt5multimedia5) because it requires qtbase-abi-5-2-1 but I already have libqt5core5a installed. Description:Ubuntu 14.04.6 LTS Release:14.04 jorge@jorge-Inspiron-3558:~$ apt-cache policy libqt5multimedia5 libqt5multimedia5: Instalados: (ninguno) Candidato: 5.2.1-0ubuntu5 Tabla de versión: 5.2.1-0ubuntu5 0 500 http://hn.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status jorge@jorge-Inspiron-3558:~$ apt-get -s install libqt5multimedia5 NOTA: ¡Esto es sólo una simulación! apt-get necesita privilegios de administrador para la ejecución real. Tenga también en cuenta que se han desactivado los bloqueos, ¡no dependa la situación real actual de la relevancia de esto! Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho No se pudieron instalar algunos paquetes. Esto puede significar que usted pidió una situación imposible o, si está usando la distribución inestable, que algunos paquetes necesarios aún no se han creado o se han sacado de «Incoming». La siguiente información puede ayudar a resolver la situación: Los siguientes paquetes tienen dependencias incumplidas: libqt5multimedia5 : Depende: qtbase-abi-5-2-1 E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libqt5multimedia5 (not installed) ProcVersionSignature: Ubuntu 3.13.0-168.218-generic 3.13.11-ckt39 Uname: Linux 3.13.0-168-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 19 02:01:48 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2017-10-22 (543 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: qtmultimedia-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtmultimedia-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "Captura de pantalla de 2019-04-19 02:35:13.png" https://bugs.launchpad.net/bugs/1825485/+attachment/5256938/+files/Captura%20de%20pantalla%20de%202019-04-19%2002%3A35%3A13.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtmultimedia-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1825485 Title: It requires two dependencies that are in conflict (libqt5core5a and qtbase-abi) Status in qtmultimedia-opensource-src package in Ubuntu: New Bug description: It requires two dependencies that are in conflict (libqt5core5a and qtbase-abi-5-2-1) and according to I saw at https://pkgs.org/download /qtbase-abi-5-2-1 it is included in libqt5core5a. And I can not install (libqt5multimedia5) because it requires qtbase-abi-5-2-1 but I already have libqt5core5a installed. Description: Ubuntu 14.04.6 LTS Release: 14.04 jorge@jorge-Inspiron-3558:~$ apt-cache policy libqt5multimedia5 libqt5multimedia5: Instalados: (ninguno) Candidato: 5.2.1-0ubuntu5 Tabla de versión: 5.2.1-0ubuntu5 0 500 http://hn.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status jorge@jorge-Inspiron-3558:~$ apt-get -s install libqt5multimedia5 NOTA: ¡Esto es sólo una simulación! apt-get necesita privilegios de administrador para la ejecución real. Tenga también en cuenta que se han desactivado los bloqueos, ¡no dependa la situación real actual de la relevancia de esto! Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho No se pudieron instalar algunos paquetes. Esto puede significar que usted pidió una situación imposible o, si está usando la distribución inestable, que algunos paquetes necesarios aún no se han creado o se han sacado de «Incoming». La siguiente información puede ayudar a resolver la situación: Los siguientes paquetes tienen dependencias incumplidas: libqt5multimedia5 : Depende: qtbase-abi-5-2-1 E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libqt5multimedia5 (not installed) ProcVersionSignature: Ubuntu 3.13.0-168.218-generic 3.13.11-ckt39 Uname: Linux 3.13.0-168-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 19 02:01:48 2019 Distri
[Touch-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
Also affected: Ubuntu MATE 18.10 -> 19.04 Upgrade. Normal system (not VM). 18.10 was a hardly used clean install of Ubuntu MATE, up-to-date patch status before update. Install appears complete and OK ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825155] Re: lxc-start crashed with SIGSEGV in cgfsng_payload_create()
** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1825155 Title: lxc-start crashed with SIGSEGV in cgfsng_payload_create() Status in lxc package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/8e0f1b9682f08bab5dedd4100e42f59cfe2cc004 Steps to reproduce: 1) Prepare creating unprivileged containers as described here: https://linuxcontainers.org/lxc/getting-started/ 2) Create a new container (e.g. "lxc-create -n container -t download" and then "debian", "stretch" and "amd64"). 3) Start the created container in foreground using "lxc-start -n container -F" ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: lxc-utils 3.0.3-0ubuntu1~18.10.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: KDE Date: Wed Apr 17 12:03:37 2019 ExecutablePath: /usr/bin/lxc-start InstallationDate: Installed on 2019-04-15 (1 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=UUID=0739f905-33c9-4de3-9ba9-a63b8d69e5e5 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x7f6292c5dbbd:mov(%rax),%r15 PC (0x7f6292c5dbbd) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%r15" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: lxc StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 __lxc_start () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 lxc_start () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 Title: lxc-start crashed with SIGSEGV in __lxc_start() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx mtime.conffile..etc.apport.crashdb.conf: 2019-04-17T11:58:15.556166 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1825155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Experiencing the same thing lately on Ubuntu 18.04.2 LTS ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: New Status in linux source package in Bionic: New Status in xorg-server source package in Bionic: New Status in console-setup source package in Cosmic: New Status in linux source package in Cosmic: New Status in xorg-server source package in Cosmic: New Status in console-setup source package in Disco: In Progress Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: New Status in linux source package in Eoan: New Status in xorg-server source package in Eoan: New Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1749562] Re: openvpn tls-crypt not working
http://www.pivpn.io/ is using tls-crypt by default, so ubuntu is not even capable connecting to this popular and easy to setup vpn solution. could you please fix network manager? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1749562 Title: openvpn tls-crypt not working Status in network-manager package in Ubuntu: Confirmed Bug description: Hi, if i try to connect to my openvpn 2.4 server i got this error on serverside: Feb 14 18:42:22 fenrir openvpn[58665]: tls-crypt unwrap error: packet too short Feb 14 18:42:22 fenrir openvpn[58665]: TLS Error: tls-crypt unwrapping failed from [AF_INET6]:::91.33.41.15:51754 (via :::192.168.2.2%igb0) my server conf: dev ovpns1 verb 1 dev-type tun dev-node /dev/tun1 writepid /var/run/openvpn_server1.pid #user nobody #group nobody script-security 3 daemon keepalive 10 60 ping-timer-rem persist-tun persist-key proto udp cipher AES-256-CBC auth SHA512 up /usr/local/sbin/ovpn-linkup down /usr/local/sbin/ovpn-linkdown client-connect /usr/local/sbin/openvpn.attributes.sh client-disconnect /usr/local/sbin/openvpn.attributes.sh multihome engine cryptodev tls-server server 10.4.0.0 255.255.0.0 client-config-dir /var/etc/openvpn-csc/server1 username-as-common-name auth-user-pass-verify "/usr/local/sbin/ovpn_auth_verify user ZmVucmly false server1 1194" via-env tls-verify "/usr/local/sbin/ovpn_auth_verify tls 'domain.local' 1" lport 1194 management /var/etc/openvpn/server1.sock unix ca /var/etc/openvpn/server1.ca cert /var/etc/openvpn/server1.cert key /var/etc/openvpn/server1.key dh /etc/dh-parameters.4096 tls-crypt /var/etc/openvpn/server1.tls-crypt ncp-ciphers AES-256-CBC persist-remote-ip float topology subnet my client config: dev tun persist-tun persist-key cipher AES-256-CBC ncp-ciphers AES-256-CBC auth SHA512 tls-client client resolv-retry infinite remote tuxist.ddns.net 1194 udp verify-x509-name "domain.local" name auth-user-pass remote-cert-tls server ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.8.4-1ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Feb 14 18:46:29 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-13 (550 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 10.3.0.1 dev wlp3s0 proto static metric 600 10.3.0.0/16 dev wlp3s0 proto kernel scope link src 10.3.141.174 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-02-12 (1 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 gameofgods 404f7dfd-a05c-4271-9a7f-6e18bc31e0cf /org/freedesktop/NetworkManager/ActiveConnection/2 eno1ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1749562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825402] Re: Regression. Recent updates to cosmic broke hybrid-sleep
Trying to downgrade systemd seems to be impossible. As soon as I try an apt install --reinstall systemd= apt tries to remove half of the system... I have noticed the issue in the past 15 days, I think, but only had time to look at it more closely right now. Some notes: - Trying to upgrade the kernel to latest 5.0.x via the mainline ppa seems to make no difference. - Issue is somehow erratic. Happens like 70% of the time. In some rare occasions the systems seems to save state and then suspend correctly. - When the issue occurs, the beginning of the hybrid sleep seems OK: big activity on disk to save the state, then the disk is powered down. However at this point, rather than suspending the system re-spins up the disk a couple of times and then halts. System logs show a HuHu unexpected nmi, dazed and confused, but it is unclear to me if it is related to the broken suspend - Plain suspend and plain hybernate seem to work. - Hybrid suspend has worked for years on this 2013 Haswell laptop, which is a Shenker, in fact a Clevo, substantially identical to the System 76 Galago UltraPro. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825402 Title: Regression. Recent updates to cosmic broke hybrid-sleep Status in systemd package in Ubuntu: Incomplete Bug description: Recently, hybrid-sleep has been broken on cosmic. Calling systemctl hybrid-sleep used to work perfectly on my system. Now, after having saved the state to disk, it switches off the machine rather than suspending it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.13 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 18 19:25:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1952 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2019-01-18 (90 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825402] Re: Regression. Recent updates to cosmic broke hybrid-sleep
Please attack `journalctl -k -b -1` after the issue occurs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825402 Title: Regression. Recent updates to cosmic broke hybrid-sleep Status in systemd package in Ubuntu: Incomplete Bug description: Recently, hybrid-sleep has been broken on cosmic. Calling systemctl hybrid-sleep used to work perfectly on my system. Now, after having saved the state to disk, it switches off the machine rather than suspending it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.13 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 18 19:25:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1952 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2019-01-18 (90 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825402] Re: Regression. Recent updates to cosmic broke hybrid-sleep
s/attack/attach -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825402 Title: Regression. Recent updates to cosmic broke hybrid-sleep Status in systemd package in Ubuntu: Incomplete Bug description: Recently, hybrid-sleep has been broken on cosmic. Calling systemctl hybrid-sleep used to work perfectly on my system. Now, after having saved the state to disk, it switches off the machine rather than suspending it. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.13 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 18 19:25:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1952 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2019-01-18 (90 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641236] Re: Confined processes inside container cannot fully access host pty device passed in by lxc exec
This affects Ubuntu 18.04 LXD containers as well. As per previous mentions for tcpdump: a) using script does not change anything b) connecting via ssh and not lxc exec has no effect c) disabling apparmour for tcpdump does work: i.e. /bin/ln -s /etc/apparmor.d/usr.sbin.tcpdump /etc/apparmor.d/disable/ /sbin/apparmor_parser -R /etc/apparmor.d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1641236 Title: Confined processes inside container cannot fully access host pty device passed in by lxc exec Status in apparmor package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Invalid Bug description: Now that AppArmor policy namespaces and profile stacking is in place, I noticed odd stdout buffering behavior when running confined processes via lxc exec. Much more data stdout data is buffered before getting flushed when the program is confined by an AppArmor profile inside of the container. I see that lxd is calling openpty(3) in the host environment, using the returned fd as stdout, and then executing the command inside of the container. This results in an AppArmor denial because the file descriptor returned by openpty(3) originates outside of the namespace used by the container. The denial is likely from glibc calling fstat(), from inside the container, on the file descriptor associated with stdout to make a decision on how much buffering to use. The fstat() is denied by AppArmor and glibc ends up handling the buffering differently than it would if the fstat() would have been successful. Steps to reproduce (using an up-to-date 16.04 amd64 VM): Create a 16.04 container $ lxc launch ubuntu-daily:16.04 x Run tcpdump in one terminal and generate traffic in another terminal (wget google.com) $ lxc exec x -- tcpdump -i eth0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 47 packets captured 48 packets received by filter 1 packet dropped by kernel Note that everything above was printed immediately because it was printed to stderr. , which is printed to stdout, was not printed until you pressed ctrl-c and the buffers were flushed thanks to the program terminating. Also, this AppArmor denial shows up in the logs: audit: type=1400 audit(1478902710.025:440): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-x_" profile="/usr/sbin/tcpdump" name="dev/pts/12" pid=15530 comm="tcpdump" requested_mask="r" denied_mask="r" fsuid=165536 ouid=165536 Now run tcpdump unconfined and take note that is printed immediately, before you terminate tcpdump. Also, there are no AppArmor denials. $ lxc exec x -- aa-exec -p unconfined -- tcpdump -i eth0 ... Now run tcpdump confined but in lxc exec's non-interactive mode and note that is printed immediately and no AppArmor denials are present. (Looking at the lxd code in lxd/container_exec.go, openpty(3) is only called in interactive mode) $ lxc exec x --mode=non-interactive -- tcpdump -i eth0 ... Applications that manually call fflush(stdout) are not affected by this as manually flushing stdout works fine. The problem seems to be caused by glibc not being able to fstat() the /dev/pts/12 fd from the host's namespace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1641236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825515] [NEW] Looping login cycle when trying to login to Ubuntu-Gnome (both X and Wayland). But logs in to Ubuntu with Budgie desktop okay.
Public bug reported: Bug started immediately after upgrading to Ubuntu 19.04. Have tried all the suggested work-arounds I can find on the web but none of them has any effect on the problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: login 1:4.5-1.1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Apr 19 22:39:45 2019 InstallationDate: Installed on 2018-10-22 (179 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: shadow UpgradeStatus: Upgraded to disco on 2019-04-18 (1 days ago) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1825515 Title: Looping login cycle when trying to login to Ubuntu-Gnome (both X and Wayland). But logs in to Ubuntu with Budgie desktop okay. Status in shadow package in Ubuntu: New Bug description: Bug started immediately after upgrading to Ubuntu 19.04. Have tried all the suggested work-arounds I can find on the web but none of them has any effect on the problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: login 1:4.5-1.1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Apr 19 22:39:45 2019 InstallationDate: Installed on 2018-10-22 (179 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: shadow UpgradeStatus: Upgraded to disco on 2019-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1825515/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
root@ubuntu1604:~# dpkg --list | grep iproute2
ii iproute2 4.3.0-1ubuntu3.16.04.4
amd64networking and traffic control tools
root@ubuntu1604:~# apt-get install iproute2/xenial-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '4.3.0-1ubuntu3.16.04.5' (Ubuntu:16.04/xenial-proposed
[amd64]) for 'iproute2'
Suggested packages:
iproute2-doc
The following packages will be upgraded:
iproute2
1 upgraded, 0 newly installed, 0 to remove and 38 not upgraded.
Need to get 523 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 iproute2
amd64 4.3.0-1ubuntu3.16.04.5 [523 kB]
Fetched 523 kB in 0s (6,782 kB/s)
(Reading database ... 85262 files and directories currently installed.)
Preparing to unpack .../iproute2_4.3.0-1ubuntu3.16.04.5_amd64.deb ...
Unpacking iproute2 (4.3.0-1ubuntu3.16.04.5) over (4.3.0-1ubuntu3.16.04.4) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up iproute2 (4.3.0-1ubuntu3.16.04.5) ...
root@ubuntu1604:~# dpkg --list | grep iproute2
ii iproute2 4.3.0-1ubuntu3.16.04.5
amd64networking and traffic control tools
root@ubuntu1604:~# ip link add dev dummy0 type dummy
RTNETLINK answers: File exists
root@ubuntu1604:~# ip link add dev dummy1 type dummy
root@ubuntu1604:~# ip link set dev dummy0 up
root@ubuntu1604:~# ip link set dev dummy1 up
root@ubuntu1604:~# tc qdisc add dev dummy0 handle 1: root prio
root@ubuntu1604:~# tc filter add dev dummy0 parent 1: matchall skip_hw action
mirred egress mirror dev dummy1
root@ubuntu1604:~# tc filter show dev dummy0
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1
root@ubuntu1604:~#
=> test is OK.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
[SRU Justification]
== Impact ==
The Xenial 4.4 kernel already has a patch applied which implements the
matchall filter. But in order to actually use it, iproute2 needs to pick up the
user-space
side of the implementation.
== Fix ==
Backported a patch from iproute2 upstream which adds the missing support.
Tested against the standard 4.4 and the HWE kernel in 16.04 (see testcase).
== Risk of Regression ==
This adds a new filter type which has to be actively selected. This should
not impact existing uses. So low.
== Testcase ==
ip link add dev dummy0 type dummy
ip link add dev dummy1 type dummy
ip link set dev dummy0 up
ip link set dev dummy1 up
tc qdisc add dev dummy0 handle 1: root prio
tc filter add dev dummy0 parent 1: matchall skip_hw action mirred egress
mirror dev dummy1
at this point, "tc filter show dev dummy0" should spit out something
like:
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1
and the functionality can be tested via
tcpdump -n -i dummy1 &
ping -I dummy0 1.2.3.4
---
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
See with just running ldapsearch after upgrade to 16.04: ``` # repeat 10 ldapsearch -x > /dev/null # tail /var/log/auth.log Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: New Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Trusty: Triaged Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811248] Re: systemd--networkd mounts denied for lxc guest
After having upgraded the host to: unbuntu disco (19.04) | kernel 5.0.0-13 | aa 2.13.2-9 | systemd 240-6 the issue is still present -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1811248 Title: systemd--networkd mounts denied for lxc guest Status in apparmor package in Ubuntu: New Bug description: Host unbuntu cosmic | lxc 3.0.3 | aa 2.12 | systemd 239-7 Guest Arch Linux | systemd 240.0 After having upgraded in the guest systemd from 239.370 to 240.0 the host's AA is exhibiting > audit: type=1400 audit(1547125168.853:722): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc- container-default-cgns" name="/" pid=8426 comm="(networkd)" flags="rw, rslave" and the guest > systemd-networkd.service: Failed to set up mount namespacing: Permission denied > systemd-networkd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-networkd: Permission denied According to lxc bug tracker https://github.com/lxc/lxc/issues/2778 > While we'd like to allow such mounts we cannot do so until the apparmor_parser is fixed to handle them correctly. other cross references https://github.com/systemd/systemd/issues/11371 https://bugs.archlinux.org/task/61313 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810129] Re: blake2b512 / sha3-512 invalid digest type
> did you try to use sha3-512 and did that work? please see the initial report: > or 'default_md = sha3-512' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1810129 Title: blake2b512 / sha3-512 invalid digest type Status in openssl package in Ubuntu: Incomplete Bug description: cosmic | openssl 1.1.1-1 Since 1.1.1.a-1 provides support for blake2b512 / sha3-512 it would be expected such to work when generating certificates which however does not. OpenSSL> list -digest-commands blake2b512 blake2s256 gost md4 md5 mdc2 rmd160 sha1 sha224 sha256 sha3-224 sha3-256 sha3-384 sha3-512 sha384 sha512 sha512-224 sha512-256 shake128 shake256 sm3 OpenSSL> list -digest-algorithms ... BLAKE2b512 ... SHA3-512 ... Steps to reproduce: in openssl_ca.conf set 'default_md = blake2b512' or 'default_md = sha3-512' generating a certificate ends with 'error:100C508A:elliptic curve routines:pkey_ec_ctrl:invalid digest type:crypto/ec/ec_pmeth.c:327:' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1810129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449250] Re: Keyboard Layout "Portuguese (Brazil, nativo for US keyboards)" doesn't respect US keyboard layout.
Ubuntu 18.04.2 LTS and the problem still persist. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1449250 Title: Keyboard Layout "Portuguese (Brazil, nativo for US keyboards)" doesn't respect US keyboard layout. Status in ibus package in Ubuntu: Confirmed Bug description: When setting up the keyboard layout to my bluetooth keyboard on my machine I saw the option to add a layout specific to Portuguese with the promise it would work with USA keyboards. But many letters are assigned to the wrong codes. 1. I'm using Ubuntu 14.04 2. I don't know the package responsible for this behaviour 3. I expected a behaviour similar to English USA International layout, but with cedilla when you press ' + C instead of the "ć" it currently generates. Pressing all characters keys on a USA keyboard should give the following result(with spaces between them and enter after each row of keys): ` 1 2 3 4 5 6 7 8 9 0 - = q w e r t y u i o p [ ] \ a s d f g h j k l ; ' z x c v b n m , . / 4. While using "Portuguese (Brazil, nativo for USA keyboards)" layout it gives = 1 2 3 4 5 6 7 8 9 0 [ ] / , . h x w l t c p ~ - ' i e a o u m d s r n ' y ; j b k q v g f z If you look at the keyboard layout chart, you'll see it has nothing to do with USA keyboards and specially nothing like to what is sold here in Brazil. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1449250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1825021] Re: apt's dpkgpm.cc WriteApportReport function should gather more data
On Tue, Apr 16, 2019 at 04:36:04PM -, Julian Andres Klode wrote:
> FWIW, apt actually overrides PATH since bionic or cosmic or something
> like that.
If that is the case then how could have the original bug been an issue?
--
Brian Murray
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1825021
Title:
apt's dpkgpm.cc WriteApportReport function should gather more data
Status in apt package in Ubuntu:
New
Bug description:
While fixing bug 1813464 it occurred to me that it is not obvious that
the dist-upgrader tarball includes its own copy of invoke-rc.d and
that this has been complicated to debug more than once. The apport
information in that report was gathered by apt's dpkgpm.cc code and I
think we should extend that to gather additional information from the
environment at the time that the package installation failed. For
example the dist-upgrader sets the following:
os.environ["PATH"] = "%s:%s" % (os.getcwd()+"/imported",
os.environ["PATH"])
Gathering path from the environment would have made diagnosing bug
1813464 a lot easier. I tested modifying dpkgpm.cc with the following:
if(const char* env_p = std::getenv("PATH"))
fprintf(report, "EnvPATH: %s\n", env_p);
I then installed the crash-in-postinst package from the daisy-plucker-
seeds PPA and received a crash report with the EnvPATH key and value.
Its worth noting that when apport gathers environment information only
a white listed set of keys is gathered to prevent disclosing
potentially sensitive information. So we should look at what
environment variables the dist-upgrader sets and gather those at a
minimum.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825021/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825545] [NEW] video memory leak leak in steamplay games
Public bug reported: the failure occurs when going through the options menu of f1 2018 is loading and after some time appears error message in the neon error saying that is missing video memory and my hardware meets the specifications where on windows can run the game. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 12:52:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050] [1043:85d7] InstallationDate: Installed on 2019-04-18 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=c81d4a6c-0a07-4434-a01f-d18e087bdeac ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1825545 Title: video memory leak leak in steamplay games Status in xorg package in Ubuntu: New Bug description: the failure occurs when going through the options menu of f1 2018 is loading and after some time appears error message in the neon error saying that is missing video memory and my hardware meets the specifications where on windows can run the game. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 12:52:54 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050] [1043:85d7] InstallationDate: Installed on 2019-04-18 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUI
[Touch-packages] [Bug 1825021] Re: apt's dpkgpm.cc WriteApportReport function should gather more data
No idea about Ubuntu specifically, but it should be in upstream since apt
1.8.0~alpha3 release on Tue, 18 Dec 2018 15:02:11 +0100.
See also: https://salsa.debian.org/apt-team/apt/merge_requests/38
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1825021
Title:
apt's dpkgpm.cc WriteApportReport function should gather more data
Status in apt package in Ubuntu:
New
Bug description:
While fixing bug 1813464 it occurred to me that it is not obvious that
the dist-upgrader tarball includes its own copy of invoke-rc.d and
that this has been complicated to debug more than once. The apport
information in that report was gathered by apt's dpkgpm.cc code and I
think we should extend that to gather additional information from the
environment at the time that the package installation failed. For
example the dist-upgrader sets the following:
os.environ["PATH"] = "%s:%s" % (os.getcwd()+"/imported",
os.environ["PATH"])
Gathering path from the environment would have made diagnosing bug
1813464 a lot easier. I tested modifying dpkgpm.cc with the following:
if(const char* env_p = std::getenv("PATH"))
fprintf(report, "EnvPATH: %s\n", env_p);
I then installed the crash-in-postinst package from the daisy-plucker-
seeds PPA and received a crash report with the EnvPATH key and value.
Its worth noting that when apport gathers environment information only
a white listed set of keys is gathered to prevent disclosing
potentially sensitive information. So we should look at what
environment variables the dist-upgrader sets and gather those at a
minimum.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825021/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825556] [NEW] freetype-config command not installed
Public bug reported: libfreetype6-dev does not include the freetype-config utility, which is used by applications to determine the location of include- and library- files. This was included in the previous version (2.8.1-2ubuntu2 from Cosmic), but disappeared when upgrading to 2.9.1-3. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libfreetype6 2.9.1-3 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 19:03:53 2019 InstallationDate: Installed on 2018-12-08 (132 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: freetype UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) ** Affects: freetype (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1825556 Title: freetype-config command not installed Status in freetype package in Ubuntu: New Bug description: libfreetype6-dev does not include the freetype-config utility, which is used by applications to determine the location of include- and library-files. This was included in the previous version (2.8.1-2ubuntu2 from Cosmic), but disappeared when upgrading to 2.9.1-3. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libfreetype6 2.9.1-3 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 19:03:53 2019 InstallationDate: Installed on 2018-12-08 (132 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: freetype UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1825556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
** Package changed: systemd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: New Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1688018 *** https://bugs.launchpad.net/bugs/1688018 Please fix this. This is a serious security problem for someone like myself trying to use Linux for work and needing to connect to a VPN on public networks. I have yet to find a workaround that lets me connect to the VPN once I've disconnected from the VPN (for example, moving from one location/public wifi to another, putting my laptop to sleep in between - when I connect to the new wifi network, I cannot connect to VPN). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825556] Re: freetype-config command not installed
freetype-config is superseded by pkg-config integration, which unlike the old freetype-config is multiarch-compatible. Projects should use pkg-config, which at this point has been supported by freetype for 16 years. ** Changed in: freetype (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1825556 Title: freetype-config command not installed Status in freetype package in Ubuntu: Won't Fix Bug description: libfreetype6-dev does not include the freetype-config utility, which is used by applications to determine the location of include- and library-files. This was included in the previous version (2.8.1-2ubuntu2 from Cosmic), but disappeared when upgrading to 2.9.1-3. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libfreetype6 2.9.1-3 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 19:03:53 2019 InstallationDate: Installed on 2018-12-08 (132 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: freetype UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1825556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824806] Re: Network stops working after systemd update
So I tested... $ sudo systemctl restart systemd-networkd ... and got the same results - the "speed changed to 0 for port" messages and loss of connectivity requiring a reboot. Afterwards, however, I noticed that I was not completely up to date so I ran an `apt full-upgrade` which brought in the latest systemd packages (237-3ubuntu10.20). During the upgrade I again saw the "speed changed to 0 for port" message and I had to reboot in order to restore connectivity. Now when I run either test (`systemctl restart systemd-networkd` or `systemctl stop systemd-networkd`), the message does not appear and I do not lose connectivity. To rule out that it only appears to occur during an upgrade, I noticed that systemd has an update in proposed (237-3ubuntu10.21), so I enabled that repository, did an `apt update` followed by an `apt full-upgrade` and the install went perfectly. So this may very well have been fixed by 237-3ubuntu10.20, but I don't want to speak for the original reporter. Side note: after running `systemctl stop systemd-networkd` the systemd- networkd process disappears from my process list, but the network does not get brought down. I don't know if that is intended behavior, but in either case it is not directly related to this report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824806 Title: Network stops working after systemd update Status in systemd package in Ubuntu: Confirmed Bug description: I have four 18.04 servers that are regularly updated and have a bond/bridge configured via netplan. Every so often the interfaces themselves will have "speed changed to 0" and the server will be unresponsive over network. The servers are still usable via the console, though. I think I can confidently associate it with systemd updates. If I'm manually updating the servers, e.g., `apt dist- upgrade`, and there's a system update... the ssh session becomes unresponsive when updating systemd, timing of automatic security updates seems to coincide with it happening as well. Rebooting fixes the issue until the next systemd update. I've included some log excerpts and one of my netplan configs below. Thanks! syslog: `Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53 Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: Lost carrier Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: IPv6 successfully disabled Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53 Apr 9 06:39:01 stn-vm-host kernel: [1058497.661292] igb :04:00.3 enp4s0f3: speed changed to 0 for port enp4s0f3 Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: Lost carrier Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: IPv6 successfully disabled Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf Apr 9 06:39:01 stn-vm-host systemd[1]: Started Network Time Synchronization. Apr 9 06:39:01 stn-vm-host systemd[1]: Stopped Flush Journal to Persistent Storage. Apr 9 06:39:01 stn-vm-host systemd[1]: Stopping Flush Journal to Persistent Storage... Apr 9 06:39:01 stn-vm-host kernel: [1058497.732487] systemd[1]: Stopping Journal Service... Apr 9 06:39:01 stn-vm-host kernel: [1058497.732903] systemd-journald[672]: Received SIGTERM from PID 1 (systemd). Apr 9 06:39:01 stn-vm-host kernel: [1058497.823634] igb :04:00.2 enp4s0f2: speed changed to 0 for port enp4s0f2 Apr 9 06:39:01 stn-vm-host kernel: [1058497.833718] systemd[1]: Stopped Journal Service. Apr 9 06:39:01 stn-vm-host kernel: [1058497.837652] systemd[1]: Starting Journal Service... Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: Lost carrier Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53 Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: IPv6 successfully disabled Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53 Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf Apr 9 06:39:01 stn-vm-host systemd[1]: Starting Flush Journal to Persistent Storage... Apr 9 06:39:01 stn-vm-host kernel: [1058497.912976] systemd[1]: Started Journal Service. Apr 9 06:39:01 stn-vm-host systemd[1]: Started Flush Journal to Persistent Storage. Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53 Apr 9 06:39:01 stn-vm-host kernel: [1058497.971223] igb :04:00.1 enp4s0f1: speed changed to 0 for port enp4s0f1 Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: Lost carrier Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: IPv6 successfully disabled Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf Apr 9 06:39
[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 Have the same problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in console-setup package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Have the same problem. Ubuntu 18.04 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: New Status in linux source package in Bionic: New Status in xorg-server source package in Bionic: New Status in console-setup source package in Cosmic: New Status in linux source package in Cosmic: New Status in xorg-server source package in Cosmic: New Status in console-setup source package in Disco: In Progress Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: New Status in linux source package in Eoan: New Status in xorg-server source package in Eoan: New Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825580] [NEW] Gnome Online Accounts fails to sign in Exchange emails
Public bug reported: After upgrading from 18.10 and/or on fresh install, a known-working Exchange email setup fails to sign in, giving "Error 7: Unexpected response from server". Tested the same settings and credentials on a new install of 18.10 and it worked. I have Evolution and Evolution-ews installed on all instances, working in 18.10, not in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 16:38:32 2019 InstallationDate: Installed on 2018-03-24 (391 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails Status in gnome-online-accounts package in Ubuntu: New Bug description: After upgrading from 18.10 and/or on fresh install, a known-working Exchange email setup fails to sign in, giving "Error 7: Unexpected response from server". Tested the same settings and credentials on a new install of 18.10 and it worked. I have Evolution and Evolution-ews installed on all instances, working in 18.10, not in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 16:38:32 2019 InstallationDate: Installed on 2018-03-24 (391 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825590] [NEW] "software & updates" freezes after selecting "canonical partners¨
Public bug reported: On a fresh install of 19.04, in "Software & Updates" when I select "Canonical Partners" the window "Authentication Required" pops up. After typing the password the mouse freezes, and can be unfrozen with CTRL+ALT+DEL. But the "Canonical Partners" cannot be selected, check box stays empty, mouse freezes again. Even after cold restart. WORKAROUND Select "Canonical Partners Sources" instead. After authorizing I can now also select "Canonical Partners". This was impossible before. After this I can select and deselect Canonical Partner in "Software & Updates". The previous authorization window, which opened first, and when the mouse froze, stays open and cannot be closed with CANCEL or ALT+F4. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: software-properties-gtk 0.97.11 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 00:17:33 2019 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-04-19 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1825590 Title: "software & updates" freezes after selecting "canonical partners¨ Status in software-properties package in Ubuntu: New Bug description: On a fresh install of 19.04, in "Software & Updates" when I select "Canonical Partners" the window "Authentication Required" pops up. After typing the password the mouse freezes, and can be unfrozen with CTRL+ALT+DEL. But the "Canonical Partners" cannot be selected, check box stays empty, mouse freezes again. Even after cold restart. WORKAROUND Select "Canonical Partners Sources" instead. After authorizing I can now also select "Canonical Partners". This was impossible before. After this I can select and deselect Canonical Partner in "Software & Updates". The previous authorization window, which opened first, and when the mouse froze, stays open and cannot be closed with CANCEL or ALT+F4. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: software-properties-gtk 0.97.11 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 00:17:33 2019 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-04-19 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1825590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825591] [NEW] Ubuntu 18.04 LTS (WSL) fails to launch in Windows 10 1903
Public bug reported: Ubuntu 18.04 LTS for WSL, official Microsoft Store package by Canonical, fails to open at all on Windows 10 May 2019 Feature Update. Link to issue in Microsoft Feedback Hub: https://aka.ms/AA4ubdp ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: package store windows10 wsl ** Summary changed: - Ubuntu 18.04 LTS (WSL) fails to launch + Ubuntu 18.04 LTS (WSL) fails to launch in Windows 10 1903 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825591 Title: Ubuntu 18.04 LTS (WSL) fails to launch in Windows 10 1903 Status in systemd package in Ubuntu: New Bug description: Ubuntu 18.04 LTS for WSL, official Microsoft Store package by Canonical, fails to open at all on Windows 10 May 2019 Feature Update. Link to issue in Microsoft Feedback Hub: https://aka.ms/AA4ubdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816237] Re: There is no lightdm in ubuntu
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1816237 Title: There is no lightdm in ubuntu Status in lightdm package in Ubuntu: Expired Bug description: The LightDM configuration files are empty ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 15:46:34 2019 InstallationDate: Installed on 2019-02-05 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1816237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814440] Re: [QCA9565 / AR9565] Bluetooth switches off automatically
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1814440 Title: [QCA9565 / AR9565] Bluetooth switches off automatically Status in bluez package in Ubuntu: Expired Bug description: Buetooth will switch automatically when i try to connect to my speaker. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 3 14:13:24 2019 InstallationDate: Installed on 2019-01-09 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80J2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=215a5782-5ca0-46f3-9fcf-f3a8c1e344db ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: A8CN54WW(V3.07) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo E50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900056 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E50-80 dmi.modalias: dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80J2:pvrLenovoE50-80:rvnLENOVO:rnLenovoE50-80:rvr31900056WIN:cvnLENOVO:ct10:cvrLenovoE50-80: dmi.product.family: IDEAPAD dmi.product.name: 80J2 dmi.product.version: Lenovo E50-80 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: B8:86:87:44:55:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:748 acl:0 sco:0 events:59 errors:0 TX bytes:4892 acl:0 sco:0 commands:59 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1814440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814554] Re: son
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1814554 Title: son Status in pulseaudio package in Ubuntu: Expired Bug description: le son ne fonctionne pas je ne peux pas écouter une vidéo ou un live ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-1028.31-oem 4.13.16 Uname: Linux 4.13.0-1028-oem x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 4 16:48:16 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0885] InstallationDate: Installed on 2019-01-21 (14 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 MachineType: Dell Inc. G3 3579 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-1028-oem.efi.signed root=UUID=20a56de0-6162-4a7f-b0ba-a98f17fcec10 ro acpi_osi=Linux-Dell-Video quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 00FK8Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd11/01/2018:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn00FK8Y:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1814554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814933] Re: Ambiance/Radiance: path-bar is broken with nautilus > 3.30
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1814933 Title: Ambiance/Radiance: path-bar is broken with nautilus > 3.30 Status in ubuntu-themes package in Ubuntu: Expired Bug description: Nautilus 3.30 has new path-bar. And hence it doesn't look good with current design. I had several ideas to solve the problem. Hence opened a discussion thread in community hub [1] to get opinions from developers and users. See: I will open a merge once this gets finalized. [1]: https://discourse.ubuntu.com/t/ambiance-radiance-path-bar- redesign-for-nautilus-3-30/9706 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1814933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
Same error message for me. Unable to boot into the 4 kernel backup as well. Repeatedly boots to the login screen, which shows my name but refuses to accept my password. Attempted installation with the beta and now the released version with same result. Running standard Ubuntu 18.10 - at least I was until the new upgrade failed... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360488] Re: software-properties-gtk does not request root permission when choosing repositories in "Other Software" tab
*** This bug is a duplicate of bug 1424362 *** https://bugs.launchpad.net/bugs/1424362 I have this behaviour on Ubuntu 19.04 (upgraded from 18.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1360488 Title: software-properties-gtk does not request root permission when choosing repositories in "Other Software" tab Status in software-properties package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu 14.04.1 LTS (Ubuntu-GNOME) Release: 14.04 amd64 2) software-properties-gtk: Installed: 0.92.37.1 Candidate: 0.92.37.1 Version table: *** 0.92.37.1 0 500 http://www.lug.bu.edu/mirror/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.92.36 0 500 http://www.lug.bu.edu/mirror/ubuntu/ trusty/main amd64 Packages 3) When checking/unchecking repositories under the "Other Software" tab of software-properties-gtk I expect it to prompt me for root/sudo password, and once accepted I can check and uncheck my repositories. 4) The title may not explain issue good enough so forgive me for being long winded just want to make sure issue is understood. This is what I experience when opening Software & Updates (software-properties-gtk) from app menu, and go to the "Other Software" tab. If you go to check or uncheck any of the repositories listed it does not let you because you don't have sudo/root privileges, that makes sense, but under regular Ubuntu 14.04.1 (I am currently running Ubuntu-GNOME 14.04.1) and you went ahead to check or uncheck a repository it would request root privileges at that moment by asking for the password. As long as the password was excepted you could then go ahead check/uncheck the repositories you want. In Ubuntu-GNOME it does not try and gain privilege it just darkens the list. If you open software-properties-gtk via terminal when you go to check/uncheck any repository it returns this error in terminal window: "ERROR:root:Authentication canceled, changes have not been saved" The only way you can get it to request root privileges is to hit one of the buttons below (Add, Edit, Remove, Add Volume). So it does not cause an issue you can not get around, it was just something that I noticed that happened with Ubuntu 14.04.1 that does not with Ubuntu-GNOME 14.04.1 and probably should. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: rr272x_1x ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 22 19:48:49 2014 InstallationDate: Installed on 2014-08-20 (2 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1360488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
