[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1815509] Re: Shutdown hung by firmware update daemon
Can you please add the requested stuff from comment 2? -- 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/1815509 Title: Shutdown hung by firmware update daemon Status in fwupd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When rebooting my desktop, the shutdown sequence hangs for a long time on "Stopping firmware update daemon." It eventually will reboot but it hangs there for quite some time before doing so. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.12 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 11 13:39:51 2019 InstallationDate: Installed on 2018-07-24 (202 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+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 1815509] Re: Shutdown hung by firmware update daemon
I have this issue on Ubuntu 18.04 running on late 2009 iMac with Intel Core 2 Duo, 8G RAM. -- 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/1815509 Title: Shutdown hung by firmware update daemon Status in fwupd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When rebooting my desktop, the shutdown sequence hangs for a long time on "Stopping firmware update daemon." It eventually will reboot but it hangs there for quite some time before doing so. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.12 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 11 13:39:51 2019 InstallationDate: Installed on 2018-07-24 (202 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+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 1821763] Re: Xorg freeze
Thanks for the bug report. Next time the problem happens, please: 1. Reboot. 2. Run: journalctl -b-1 > prevboot.txt 3. Send us the file 'prevboot.txt'. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1821763 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: System froze completely, no mouse and keyboard, caps and num lock keys didn't even light up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 12:20:53 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39c5] InstallationDate: Installed on 2019-03-06 (19 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5a02 IMC Networks Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 413c:8505 Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80YH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=e7f345fa-d4fb-4bf9-a5bc-6788d80fdfba ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN41WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN41WW:bd07/23/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80YH dmi.product.sku: LENOVO_MT_80YH_BU_idea_FM_ideapad 320-15IKB dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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/+bug/1821763/+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 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco) [needed for graphics support on Intel Core 2 Duo systems]
** Summary changed: - intel video driver not installed by default in ubuntu 19.04 (Disco) + intel video driver not installed by default in ubuntu 19.04 (Disco) [needed for graphics support on Intel Core 2 Duo systems] -- 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/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) [needed for graphics support on Intel Core 2 Duo systems] Status in xorg package in Ubuntu: Fix Released Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1819943/+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 1821609] Re: lightdm login screen never appears when using kernel 5.0.0-7, but works with kernel 5.0.0-8
*** This bug is a duplicate of bug 1819943 *** https://bugs.launchpad.net/bugs/1819943 Oh. On second thoughts I think you might have made a mistake. I think more likely the fix came from the reintroduction of the Intel Xorg driver: Install: libxcb-randr0:amd64 (1.13.1-2, automatic), xserver-xorg- video-intel:amd64 (2:2.99.917+git20180925-2, automatic) which is needed by older GPUs, possibly like: Intel(R) Core(TM)2 Duo CPU T5870 @ 2.00GHz That would make this a duplicate of bug 1819943. ** Package changed: linux (Ubuntu) => xorg (Ubuntu) ** Summary changed: - lightdm login screen never appears when using kernel 5.0.0-7, but works with kernel 5.0.0-8 + lightdm login screen never appears on Intel(R) Core(TM)2 Duo CPU T5870 ** Changed in: xorg (Ubuntu) Status: Fix Committed => New ** This bug has been marked a duplicate of bug 1819943 intel video driver not installed by default in ubuntu 19.04 (Disco) -- 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/1821609 Title: lightdm login screen never appears on Intel(R) Core(TM)2 Duo CPU T5870 Status in xorg package in Ubuntu: New Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev:
[Touch-packages] [Bug 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily
Could you please try some older kernels (like 4.18) to see if the problem is caused by the new kernel in Ubuntu 19.04? https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Package changed: ubuntu => linux (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/1821641 Title: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily Status in linux package in Ubuntu: Incomplete Bug description: On the 19.04 daily image (2019-03-24), the screen on my laptop is completely upside down, from the moment the GUI loads. This does not happen on 18.04 and 18.10. It appears to be an accelerometer issue since holding the laptop upside down flips the image to its correct orientation - basically the functionality of the accelerometer is suddenly inverted. Please contact me if you want me to help testing the issue on my hardware. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821641/+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 1821609] [NEW] lightdm login screen never appears when using kernel 5.0.0-7, but works with kernel 5.0.0-8
You have been subscribed to a public bug: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: Fix Committed ** Tags: amd64 apport-bug disco freeze has-workaround regression reproducible ubuntu -- lightdm login screen never appears when using kernel 5.0.0-7, but works with kernel 5.0.0-8 https://bugs.launchpad.net/bugs/1821609 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved
Thanks for figuring that out. Kernel 5.0.0-8 is in disco-proposed right now, so we call that Fix Committed (but not yet released). ** No longer affects: kwallet-pam (Ubuntu) ** Summary changed: - Xorg freeze - fails to start or stay going screen blanks-grub seems involved + lightdm login screen never appears when using kernel 5.0.0.7, but works with kernel 5.0.0.8 ** Package changed: lightdm (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Summary changed: - lightdm login screen never appears when using kernel 5.0.0.7, but works with kernel 5.0.0.8 + lightdm login screen never appears when using kernel 5.0.0-7, but works with kernel 5.0.0-8 -- 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/1821609 Title: lightdm login screen never appears when using kernel 5.0.0-7, but works with kernel 5.0.0-8 Status in linux package in Ubuntu: Fix Committed Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau:
[Touch-packages] [Bug 1222356] Re: WARNING: Couldn't register with accessibility bus: Did not receive a reply.
I started receiving this warning when I installed HPLIP on my computer, and it appears to be preventing me from sending faxes. I also think it caused me to receive the 'hp-uiscan is not supported for this device'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1222356 Title: WARNING: Couldn't register with accessibility bus: Did not receive a reply. Status in at-spi2-core package in Ubuntu: Fix Released Status in at-spi2-core package in Debian: Fix Released Bug description: The following warnings/errors appear after calling ubuntu-bug ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport-gtk 2.12.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 10:54:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-01 (371 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1222356/+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 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
** No longer affects: xorg-server (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/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) Status in xorg package in Ubuntu: Fix Released Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1819943/+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 1821822] [NEW] Temporary failure in name resolution in Python 3.7.2
Public bug reported:
My Python application works in 18.10 fine, but when upgrading to 19.10
for development reasons the same script produces the errors reported
below. I have checked on the Python bug tracker and there are no related
bug reports.
Traceback (most recent call last):
File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open
encode_chunked=req.has_header('Transfer-encoding'))
File "/usr/lib/python3.7/http/client.py", line 1229, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output
self.send(msg)
File "/usr/lib/python3.7/http/client.py", line 956, in send
self.connect()
File "/usr/lib/python3.7/http/client.py", line 1384, in connect
super().connect()
File "/usr/lib/python3.7/http/client.py", line 928, in connect
(self.host,self.port), self.timeout, self.source_address)
File "/usr/lib/python3.7/socket.py", line 707, in create_connection
for res in getaddrinfo(host, port, 0, SOCK_STREAM):
File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/pihole-panel/main.py", line 312, in
win = GridWindow()
File "/usr/lib/pihole-panel/main.py", line 37, in __init__
self.updates_frame = self.draw_updates_frame()
File "/usr/lib/pihole-panel/main.py", line 132, in draw_updates_frame
if self.version_check() == True:
File "/usr/lib/pihole-panel/main.py", line 53, in version_check
get_version = urlopen('https://urlchanged.com').read()
File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.7/urllib/request.py", line 525, in open
response = self._open(req, data)
File "/usr/lib/python3.7/urllib/request.py", line 543, in _open
'_open', req)
File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/usr/lib/python3.7/urllib/request.py", line 1360, in https_open
context=self._context, check_hostname=self._check_hostname)
File "/usr/lib/python3.7/urllib/request.py", line 1319, in do_open
raise URLError(err)
urllib.error.URLError:
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
My Python application works in 18.10 fine, but when upgrading to 19.10
for development reasons the same script produces the errors reported
below. I have checked on the Python bug tracker and there are no related
bug reports.
Traceback (most recent call last):
- File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open
- encode_chunked=req.has_header('Transfer-encoding'))
- File "/usr/lib/python3.7/http/client.py", line 1229, in request
- self._send_request(method, url, body, headers, encode_chunked)
- File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request
- self.endheaders(body, encode_chunked=encode_chunked)
- File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders
- self._send_output(message_body, encode_chunked=encode_chunked)
- File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output
- self.send(msg)
- File "/usr/lib/python3.7/http/client.py", line 956, in send
- self.connect()
- File "/usr/lib/python3.7/http/client.py", line 1384, in connect
- super().connect()
- File "/usr/lib/python3.7/http/client.py", line 928, in connect
- (self.host,self.port), self.timeout, self.source_address)
- File "/usr/lib/python3.7/socket.py", line 707, in create_connection
- for res in getaddrinfo(host, port, 0, SOCK_STREAM):
- File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo
- for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
+ File "/usr/lib/python3.7/urllib/request.py", line 1317, in do_open
+ encode_chunked=req.has_header('Transfer-encoding'))
+ File "/usr/lib/python3.7/http/client.py", line 1229, in request
+ self._send_request(method, url, body, headers, encode_chunked)
+ File "/usr/lib/python3.7/http/client.py", line 1275, in _send_request
+ self.endheaders(body, encode_chunked=encode_chunked)
+ File "/usr/lib/python3.7/http/client.py", line 1224, in endheaders
+ self._send_output(message_body, encode_chunked=encode_chunked)
+ File "/usr/lib/python3.7/http/client.py", line 1016, in _send_output
+ self.send(msg)
+ File "/usr/lib/python3.7/http/client.py", line 956, in send
[Touch-packages] [Bug 1585886] Re: WiFi indicator icon disappears in Ubuntu 16.04
I am facing a similar issue in my HP Ubuntu 16.04 laptop... WiFi icon is grayed out, it doesn't show the active connection (though it is actually connected to my WiFi router!) and it shows other Wi-Fi networks. Sometimes, the whole icon disappears and I get the small icon of network (with the up-down arrows)! As reported by others, I suspect that it is caused due to laptop going to standby. The "service network-manager restart" command worked for me! Wish this bug could be fixed though! -- 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/1585886 Title: WiFi indicator icon disappears in Ubuntu 16.04 Status in indicator-applet package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Dear all, Can someone confirm an occasionally missing WiFi indicator tray icon? Sometimes it happens that the icon is not displayed although the WiFi connection is working. Please see also the attached screenshot. Warmly, ~Robert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1585886/+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 781154] Re: [nc] Wishlist: Figlet export ASCIIfied BFD to /usr/share/figlet*.flc
** Package changed: ubuntu-font-family-sources (Ubuntu) => fonts-ubuntu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/781154 Title: [nc] Wishlist: Figlet export ASCIIfied BFD to /usr/share/figlet*.flc Status in fonts-ubuntu package in Ubuntu: New Bug description: It would be nice to have a figlet'ised version of the Ubuntu font available in the figlet package. So when I do things like this:- alan@bishop:~$ figlet Moo! __ __ _ | \/ | ___ ___ | | | |\/| |/ _ \ / _ \| | | | | | (_) | (_) |_| |_| |_|\___/ \___/(_) It uses the Ubuntu font. Please make that happen. (note above wil need a fixed font to view properly) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/781154/+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 1204579] Re: ufw doesn't support concurrent updates
Hello Jeremy, or anyone else affected, Accepted ufw into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ufw (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: ufw (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1204579 Title: ufw doesn't support concurrent updates Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Status in ufw package in Debian: Fix Released Bug description: [Impact] ufw prior to 0.36 did not support locking or use xtables locking which can lead to problems when using ufw as a dynamic firewall. [Test Case] $ sudo apt-get install python-minimal # for the test script $ sudo ./test_ufw_threads.py # this runs for many seconds A patched ufw will complete with no errors. With an unpatched ufw, there will be many errors like: $ sudo ./test_ufw_threads.py ... ERROR: initcaps [Errno 2] iptables: Chain already exists. ERROR: initcaps [Errno 2] iptables: Chain already exists. [Regression Potential] ufw 0.36 implements a global exclusive lock before doing any kernel or file writes. Risk of regression includes the lock file not being released due to coding error. The locking is done via fcntl.lockf and ufw releases it in a finally clause that is careful to always release it. [Other Info] This locking code has been in production in the ufw snap for years and is known to work is static environments as well as in dynamic environments (IPS/fail2ban/etc). = Original description = On a server under Ubuntu 12.04 I automatically update firewall rules and I unfortunately noticed that if 2 rules are processed at the same time it leads to an inconsistent result between iptables and ufw status. In fact it can be reproduced using the python script in attachment. Before executing this script I didn't have any rules matching the ip 192.168.254.1 on my computer. After a launch iptables takes into acount 464 rules. sudo iptables -L -n | grep 192.168.254.1 | wc -l 464 It should be 500 rules but the script stressed a lot my system and all rules can't be processed by iptables sudo ./test_ufw_threads.py iptables: Resource temporarily unavailable. iptables: Resource temporarily unavailable. iptables: Resource temporarily unavailable. [...] Anyway, ufw stores only the last updates (in /lib/ufw/user.rules): sudo ufw status État : actif Vers Action Depuis -- -- 192.168.254.1 1234/tcp ALLOW 192.168.46.9 192.168.254.1 1234/tcp ALLOW 192.168.22.10 192.168.254.1 1234/tcp ALLOW 192.168.32.10 192.168.254.1 1234/tcp ALLOW 192.168.5.10 192.168.254.1 1234/tcp ALLOW 192.168.43.9 192.168.254.1 1234/tcp ALLOW 192.168.40.10 192.168.254.1 1234/tcp ALLOW 192.168.46.10 192.168.254.1 1234/tcp ALLOW 192.168.48.10 192.168.254.1 1234/tcp ALLOW 192.168.42.10 192.168.254.1 1234/tcp ALLOW 192.168.43.10 So I can't delete other rules using ufw, I had to directly use iptables. In this case I can only delete 10 rules using ufw. Could you please handle some kind of lock? To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1204579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1204579] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted ufw into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1204579 Title: ufw doesn't support concurrent updates Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Status in ufw package in Debian: Fix Released Bug description: [Impact] ufw prior to 0.36 did not support locking or use xtables locking which can lead to problems when using ufw as a dynamic firewall. [Test Case] $ sudo apt-get install python-minimal # for the test script $ sudo ./test_ufw_threads.py # this runs for many seconds A patched ufw will complete with no errors. With an unpatched ufw, there will be many errors like: $ sudo ./test_ufw_threads.py ... ERROR: initcaps [Errno 2] iptables: Chain already exists. ERROR: initcaps [Errno 2] iptables: Chain already exists. [Regression Potential] ufw 0.36 implements a global exclusive lock before doing any kernel or file writes. Risk of regression includes the lock file not being released due to coding error. The locking is done via fcntl.lockf and ufw releases it in a finally clause that is careful to always release it. [Other Info] This locking code has been in production in the ufw snap for years and is known to work is static environments as well as in dynamic environments (IPS/fail2ban/etc). = Original description = On a server under Ubuntu 12.04 I automatically update firewall rules and I unfortunately noticed that if 2 rules are processed at the same time it leads to an inconsistent result between iptables and ufw status. In fact it can be reproduced using the python script in attachment. Before executing this script I didn't have any rules matching the ip 192.168.254.1 on my computer. After a launch iptables takes into acount 464 rules. sudo iptables -L -n | grep 192.168.254.1 | wc -l 464 It should be 500 rules but the script stressed a lot my system and all rules can't be processed by iptables sudo ./test_ufw_threads.py iptables: Resource temporarily unavailable. iptables: Resource temporarily unavailable. iptables: Resource temporarily unavailable. [...] Anyway, ufw stores only the last updates (in /lib/ufw/user.rules): sudo ufw status État : actif Vers Action Depuis -- -- 192.168.254.1 1234/tcp ALLOW 192.168.46.9 192.168.254.1 1234/tcp ALLOW 192.168.22.10 192.168.254.1 1234/tcp ALLOW 192.168.32.10 192.168.254.1 1234/tcp ALLOW 192.168.5.10 192.168.254.1 1234/tcp ALLOW 192.168.43.9 192.168.254.1 1234/tcp ALLOW 192.168.40.10 192.168.254.1 1234/tcp ALLOW 192.168.46.10 192.168.254.1 1234/tcp ALLOW 192.168.48.10 192.168.254.1 1234/tcp ALLOW 192.168.42.10 192.168.254.1 1234/tcp ALLOW 192.168.43.10 So I can't delete other rules using ufw, I had to directly use iptables. In this case I can only delete 10 rules using ufw. Could you please handle some kind of lock? To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1204579/+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 1368411] Please test proposed package
Hello babipanghang, or anyone else affected, Accepted ufw into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1368411 Title: Cannot insert IPV6 rule before IPV4 rules Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Status in ufw package in Debian: Fix Released Bug description: [Impact] ufw's 'insert' command is designed to work with 'ufw status numbered' to insert rules in specific places in the ruleset. This makes it more difficult than it should be for using ufw as part of an IPS/dynamic firewall (eg, fail2ban) since if the firewall already has an IPv4 rule then the user/IPS must calculate the position of an IPv6-only rule before inserting it. From the git commit: " add 'prepend' command Introduce 'prepend' command to add rules to the top of the IPv4 and/or IPv6 chains. This is particularly useful for dynamic firewalls/IPS (eg, fail2ban). Unlike 'insert', 'prepend' does not require knowledge about the IPv6 rule number so integration into IPS is much easier. " [Test Case] $ sudo ufw allow 22/tcp $ sudo ufw allow from 1.2.3.4 $ sudo ufw allow from 2001:db8::/32 $ sudo ufw enable $ sudo ufw status numbered ... [ 1] 22/tcp ALLOW INAnywhere [ 2] Anywhere ALLOW IN1.2.3.4 [ 3] 22/tcp (v6)ALLOW INAnywhere (v6) [ 4] Anywhere (v6) ALLOW IN2001:db8::/32 # unchanged from 0.35 $ sudo ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 ERROR: Invalid position '1' # new in 0.36 $ sudo ufw prepend deny from 2a02:2210:12:a:b820:fff:fea2:25d1 $ sudo ufw prepend deny from 6.7.8.9 $ sudo ufw status numbered ... [ 1] Anywhere DENY IN 6.7.8.9 [ 2] 22/tcp ALLOW INAnywhere [ 3] Anywhere ALLOW IN1.2.3.4 [ 4] Anywhere (v6) DENY IN 2a02:2210:12:a:b820:fff:fea2:25d1 [ 5] 22/tcp (v6)ALLOW INAnywhere (v6) [ 6] Anywhere (v6) ALLOW IN2001:db8::/32 [Regression Potential] ufw has a clean methodology for adding new commands so while frontend.py necessarily has some logic changes to calculate where to insert the rule (ie, if IPv4 at the top, if IPv6 before other IPv6 rules and if both, both), the changes were minimal and only are used if 'prepend' is specified (so people only using the previous command set should be fine). [Other Info] The ufw prepend command is new in 0.36 and thus only available in Debian, Ubuntu disco and the ufw snap for a few weeks. The snap is known to work with fail2ban and the prepend command in production environments since it was available. = Original description = I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered 6 to 10, the following command: [code] ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] errors with "ERROR: Invalid position '1'". However, the command [code] ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] succeeds. In my case, this poses a problem, since I am trying to insert rules from a script against brute force attacks. The script needs to insert blocking rules before a number of other rules that open up some ports (since the order of rules is important in ufw). However since the number of IPV4 rules will be changing all the time, the position of the first available
[Touch-packages] [Bug 1368411] Re: Cannot insert IPV6 rule before IPV4 rules
Hello babipanghang, or anyone else affected, Accepted ufw into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ufw (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: ufw (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1368411 Title: Cannot insert IPV6 rule before IPV4 rules Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Status in ufw package in Debian: Fix Released Bug description: [Impact] ufw's 'insert' command is designed to work with 'ufw status numbered' to insert rules in specific places in the ruleset. This makes it more difficult than it should be for using ufw as part of an IPS/dynamic firewall (eg, fail2ban) since if the firewall already has an IPv4 rule then the user/IPS must calculate the position of an IPv6-only rule before inserting it. From the git commit: " add 'prepend' command Introduce 'prepend' command to add rules to the top of the IPv4 and/or IPv6 chains. This is particularly useful for dynamic firewalls/IPS (eg, fail2ban). Unlike 'insert', 'prepend' does not require knowledge about the IPv6 rule number so integration into IPS is much easier. " [Test Case] $ sudo ufw allow 22/tcp $ sudo ufw allow from 1.2.3.4 $ sudo ufw allow from 2001:db8::/32 $ sudo ufw enable $ sudo ufw status numbered ... [ 1] 22/tcp ALLOW INAnywhere [ 2] Anywhere ALLOW IN1.2.3.4 [ 3] 22/tcp (v6)ALLOW INAnywhere (v6) [ 4] Anywhere (v6) ALLOW IN2001:db8::/32 # unchanged from 0.35 $ sudo ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 ERROR: Invalid position '1' # new in 0.36 $ sudo ufw prepend deny from 2a02:2210:12:a:b820:fff:fea2:25d1 $ sudo ufw prepend deny from 6.7.8.9 $ sudo ufw status numbered ... [ 1] Anywhere DENY IN 6.7.8.9 [ 2] 22/tcp ALLOW INAnywhere [ 3] Anywhere ALLOW IN1.2.3.4 [ 4] Anywhere (v6) DENY IN 2a02:2210:12:a:b820:fff:fea2:25d1 [ 5] 22/tcp (v6)ALLOW INAnywhere (v6) [ 6] Anywhere (v6) ALLOW IN2001:db8::/32 [Regression Potential] ufw has a clean methodology for adding new commands so while frontend.py necessarily has some logic changes to calculate where to insert the rule (ie, if IPv4 at the top, if IPv6 before other IPv6 rules and if both, both), the changes were minimal and only are used if 'prepend' is specified (so people only using the previous command set should be fine). [Other Info] The ufw prepend command is new in 0.36 and thus only available in Debian, Ubuntu disco and the ufw snap for a few weeks. The snap is known to work with fail2ban and the prepend command in production environments since it was available. = Original description = I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered 6 to 10, the following command: [code] ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] errors with "ERROR: Invalid position '1'". However, the command [code] ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] succeeds. In my case, this poses a problem, since I am trying to insert rules from a script against brute force
[Touch-packages] [Bug 1664133] Please test proposed package
Hello Adam, or anyone else affected, Accepted ufw into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1664133 Title: ipv6 multicast pings don't return Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Bug description: [Impact] ping6 replies to multicast addresses are mistakenly blocked. ufw used to have correct ordering for these replies, but 0.34 reorganized the icmp rules and reintroduced LP: #720605 (this bug). multicast ping replies are part of the ok icmp codes for INPUT (rfc4890, 4.4.1 and 4.4.2) but don't have an associated connection and are marked INVALID, so move this rule above the INVALID rules. [Test Case] On an IPv6 enabled system, perform a multicast ping like so: $ sudo ufw enable $ sudo ping6 ff02::1%wlp58s0 # where 'wlp58s0' is your network iface PING ff02::1%wlp58s0(ff02::1%wlp58s0) 56 data bytes 64 bytes from ...addr1...: icmp_seq=1 ttl=64 time=0.081 ms 64 bytes from ...addr2...: icmp_seq=2 ttl=64 time=0.155 ms ^C $ Without this fix, only see responses from the ff80 address of the specified interface (ie, the 'wlp58s0' interface in the above example). With the fix, there should be a response from other IPv6 enabled hosts on the network. [Regression Potential] The regression potential is extremely low since we are simply moving a single rule above another rule. The worst that could happen is that the ping6 would continue to not work. = Original description = Hi, I have the default settings from Linux Mint 18 for ufw. When I "ping6 ff02::1%wlp3s0", I get only an answer from my own ip. Duplicates from other devices on the net get filtered. It works fine after "sudo ufw disable". ufw --version ufw 0.35 Copyright 2008-2015 Canonical Ltd. I've attached the output of ip6tables-save. There is a similar old and long fixed bug: https://bugs.launchpad.net/ufw/+bug/720605 To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1664133/+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 1664133] Re: ipv6 multicast pings don't return
Hello Adam, or anyone else affected, Accepted ufw into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ufw (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: ufw (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1664133 Title: ipv6 multicast pings don't return Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Bug description: [Impact] ping6 replies to multicast addresses are mistakenly blocked. ufw used to have correct ordering for these replies, but 0.34 reorganized the icmp rules and reintroduced LP: #720605 (this bug). multicast ping replies are part of the ok icmp codes for INPUT (rfc4890, 4.4.1 and 4.4.2) but don't have an associated connection and are marked INVALID, so move this rule above the INVALID rules. [Test Case] On an IPv6 enabled system, perform a multicast ping like so: $ sudo ufw enable $ sudo ping6 ff02::1%wlp58s0 # where 'wlp58s0' is your network iface PING ff02::1%wlp58s0(ff02::1%wlp58s0) 56 data bytes 64 bytes from ...addr1...: icmp_seq=1 ttl=64 time=0.081 ms 64 bytes from ...addr2...: icmp_seq=2 ttl=64 time=0.155 ms ^C $ Without this fix, only see responses from the ff80 address of the specified interface (ie, the 'wlp58s0' interface in the above example). With the fix, there should be a response from other IPv6 enabled hosts on the network. [Regression Potential] The regression potential is extremely low since we are simply moving a single rule above another rule. The worst that could happen is that the ping6 would continue to not work. = Original description = Hi, I have the default settings from Linux Mint 18 for ufw. When I "ping6 ff02::1%wlp3s0", I get only an answer from my own ip. Duplicates from other devices on the net get filtered. It works fine after "sudo ufw disable". ufw --version ufw 0.35 Copyright 2008-2015 Canonical Ltd. I've attached the output of ip6tables-save. There is a similar old and long fixed bug: https://bugs.launchpad.net/ufw/+bug/720605 To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1664133/+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 1775043] Please test proposed package
Hello Paulo, or anyone else affected, Accepted ufw into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1775043 Title: bash completion not working: uses deprecated have() Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Bug description: [Impact] Tab completion is currently broken. [Test Case] $ ufw allow delete --dry-run --help loggingreset status appdeny enable insert reject route version defaultdisable--forcelimit reload show With an unpatched ufw, tab completion only shows the files in the current directory, which is meaningless for ufw. [Regression Potential] Risk of regression is considered very low since tab completion is totally broken and correct functionality is easily tested. = Original description = bash completion, defined in /usr/share/bash- completion/completions/ufw, doesn't work: the completion is not dynamically loaded, because it uses deprecated helper function have(). According to /usr/share/bash-completions/bash_completion, which defines the helper functions: # Backwards compatibility for compat completions that use have(). # @deprecated should no longer be used; generally not needed with dynamically # loaded completions, and _have is suitable for runtime use. and at the end of the file: unset -f have unset have which means: function have() is not available for usage. The bash completion for ufw conditionally defines _ufw and the comspec: have ufw && _ufw() ... [ "$have" ] && complete -F _ufw ufw These should be changed to: _have ufw && _ufw() ... _have ufw && complete -F _ufw ufw ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ufw 0.35-5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jun 4 14:34:11 2018 InstallationDate: Installed on 2018-04-28 (37 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1775043/+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 1811129] Re: update ufw to 0.36
Hello Jamie, or anyone else affected, Accepted ufw into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ufw (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: ufw (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1811129 Title: update ufw to 0.36 Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Bug description: [Impact] This bug is the master bug for a one time SRU of ufw to the new 0.36 release. Typically patches would be individually backported like normal, but the new 'prepend' command feature is the impetus for this SRU and it contains most of the code changes. Other bugs fixed in the upstream release are either already included in the Ubuntu/Debian packaging or small enough to not pose a significant regression risk. 0.36 had various pyflakes/pep8/pylint cleanups over 0.35 so upgrading 18.04 to 0.36 will make maintaining ufw a bit easier for the duration of this LTS. [Test Case] In addition to the in-build tests, there is an extensive testsuite for running under root on the live system. The QRT tests for ufw (scripts /test-ufw.py) run these tests (and more). [Regression Potential] In terms of code changes, I've attached code-changes-bionic-to- disco.diff which is a diff of the source code in bionic's 0.35-5 with patches applied and disco's 0.36-1 with its patches applied. This shows that: * only comment changes to conf/sysctl.conf * only comment changes to conf/ufw.defaults * doc/systemd.example is updated (but unused in our packaging) * various man page updates * ufw.pot is refreshed * various Makefile updates related to snap packaging and coverage (the debian packaging only uses the 'clean' target) * src/applications.py has only whitespace and comment changes The remaining code changes in src/ are quite small and address the SRU bugs and the regression potential for these changes will be discussed in those bugs. In addition to the SRU bugs listed in the changelog, 0.36 also fixes the following upstream bugs not already in 0.35-5: * bug 1782384 - ufw-framework document error * bug 1695718 - UFW rule for Transmission only allows 51413/tcp while 51413/udp is used for DHT * bug 1377600 - ufw errors after ctr+c interupt * bug 1586258 - Rule insertion fails if ruleset is empty * bug 1558068 - remove extraneous source quench rule * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884932 - cannot preseed package configuration in debian-installer (other bugs in the 0.36-1 changelog are dupes of the above) [Other Info] Note that the 0.36 code base has been the basis for the snap for many months with the majority of the non-'prepend' changes in production during this time. 0.36-1 was uploaded to Debian in December (and it migrated automatically to disco shortly after) with no new ufw bug reports in either. Buster will release with 0.36-1. The snappy packaging, which is included upstream, underwent a lot of changes, but should not be considered as part of this SRU since it doesn't affect the deb builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1811129/+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 1775043] Re: bash completion not working: uses deprecated have()
Hello Paulo, or anyone else affected, Accepted ufw into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ufw (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: ufw (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1775043 Title: bash completion not working: uses deprecated have() Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Bug description: [Impact] Tab completion is currently broken. [Test Case] $ ufw allow delete --dry-run --help loggingreset status appdeny enable insert reject route version defaultdisable--forcelimit reload show With an unpatched ufw, tab completion only shows the files in the current directory, which is meaningless for ufw. [Regression Potential] Risk of regression is considered very low since tab completion is totally broken and correct functionality is easily tested. = Original description = bash completion, defined in /usr/share/bash- completion/completions/ufw, doesn't work: the completion is not dynamically loaded, because it uses deprecated helper function have(). According to /usr/share/bash-completions/bash_completion, which defines the helper functions: # Backwards compatibility for compat completions that use have(). # @deprecated should no longer be used; generally not needed with dynamically # loaded completions, and _have is suitable for runtime use. and at the end of the file: unset -f have unset have which means: function have() is not available for usage. The bash completion for ufw conditionally defines _ufw and the comspec: have ufw && _ufw() ... [ "$have" ] && complete -F _ufw ufw These should be changed to: _have ufw && _ufw() ... _have ufw && complete -F _ufw ufw ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ufw 0.35-5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jun 4 14:34:11 2018 InstallationDate: Installed on 2018-04-28 (37 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1775043/+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 1719211] Re: Bad interface name
Hello les, or anyone else affected, Accepted ufw into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ufw (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: ufw (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1719211 Title: Bad interface name Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Bug description: [Impact] ufw's interface name's or both too strict (this bug) and too loose (iptables has its own limits). Adjust the interface name checks to match those of the kernel. [Test Case] $ sudo ufw --dry-run allow in on i-1|grep i-1 ### tuple ### allow any any 0.0.0.0/0 any 0.0.0.0/0 in_i-1 -A ufw-user-input -i i-1 -j ACCEPT ### tuple ### allow any any ::/0 any ::/0 in_i-1 -A ufw6-user-input -i i-1 -j ACCEPT With an unpatched ufw, the above results in: $ sudo ufw --dry-run allow in on i-1|grep i-1 ERROR: Bad interface name [Regression Potential] Risk of regression is considered low since the updated allow more than what is currently allowed, but not more than what iptables allows. See: https://git.launchpad.net/ufw/tree/src/common.py?h=release/0.36#n295 = Original description = Is there a reason to restrict interface's name in ufw? Should ufw accept what iptables accept as iface name? I've a vpn with lot of nodes, its iface name contain a '-' so cannot use ufw on it. I've found the check here and cannot found a reason for it: http://bazaar.launchpad.net/~jdstrand/ufw/trunk/view/head:/src/common.py#L300 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1719211/+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 1719211] Please test proposed package
Hello les, or anyone else affected, Accepted ufw into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1719211 Title: Bad interface name Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Bug description: [Impact] ufw's interface name's or both too strict (this bug) and too loose (iptables has its own limits). Adjust the interface name checks to match those of the kernel. [Test Case] $ sudo ufw --dry-run allow in on i-1|grep i-1 ### tuple ### allow any any 0.0.0.0/0 any 0.0.0.0/0 in_i-1 -A ufw-user-input -i i-1 -j ACCEPT ### tuple ### allow any any ::/0 any ::/0 in_i-1 -A ufw6-user-input -i i-1 -j ACCEPT With an unpatched ufw, the above results in: $ sudo ufw --dry-run allow in on i-1|grep i-1 ERROR: Bad interface name [Regression Potential] Risk of regression is considered low since the updated allow more than what is currently allowed, but not more than what iptables allows. See: https://git.launchpad.net/ufw/tree/src/common.py?h=release/0.36#n295 = Original description = Is there a reason to restrict interface's name in ufw? Should ufw accept what iptables accept as iface name? I've a vpn with lot of nodes, its iface name contain a '-' so cannot use ufw on it. I've found the check here and cannot found a reason for it: http://bazaar.launchpad.net/~jdstrand/ufw/trunk/view/head:/src/common.py#L300 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1719211/+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 1811129] Please test proposed package
Hello Jamie, or anyone else affected, Accepted ufw into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ufw/0.36-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1811129 Title: update ufw to 0.36 Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Committed Status in ufw source package in Cosmic: Fix Committed Status in ufw source package in Disco: Fix Released Bug description: [Impact] This bug is the master bug for a one time SRU of ufw to the new 0.36 release. Typically patches would be individually backported like normal, but the new 'prepend' command feature is the impetus for this SRU and it contains most of the code changes. Other bugs fixed in the upstream release are either already included in the Ubuntu/Debian packaging or small enough to not pose a significant regression risk. 0.36 had various pyflakes/pep8/pylint cleanups over 0.35 so upgrading 18.04 to 0.36 will make maintaining ufw a bit easier for the duration of this LTS. [Test Case] In addition to the in-build tests, there is an extensive testsuite for running under root on the live system. The QRT tests for ufw (scripts /test-ufw.py) run these tests (and more). [Regression Potential] In terms of code changes, I've attached code-changes-bionic-to- disco.diff which is a diff of the source code in bionic's 0.35-5 with patches applied and disco's 0.36-1 with its patches applied. This shows that: * only comment changes to conf/sysctl.conf * only comment changes to conf/ufw.defaults * doc/systemd.example is updated (but unused in our packaging) * various man page updates * ufw.pot is refreshed * various Makefile updates related to snap packaging and coverage (the debian packaging only uses the 'clean' target) * src/applications.py has only whitespace and comment changes The remaining code changes in src/ are quite small and address the SRU bugs and the regression potential for these changes will be discussed in those bugs. In addition to the SRU bugs listed in the changelog, 0.36 also fixes the following upstream bugs not already in 0.35-5: * bug 1782384 - ufw-framework document error * bug 1695718 - UFW rule for Transmission only allows 51413/tcp while 51413/udp is used for DHT * bug 1377600 - ufw errors after ctr+c interupt * bug 1586258 - Rule insertion fails if ruleset is empty * bug 1558068 - remove extraneous source quench rule * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884932 - cannot preseed package configuration in debian-installer (other bugs in the 0.36-1 changelog are dupes of the above) [Other Info] Note that the 0.36 code base has been the basis for the snap for many months with the majority of the non-'prepend' changes in production during this time. 0.36-1 was uploaded to Debian in December (and it migrated automatically to disco shortly after) with no new ufw bug reports in either. Buster will release with 0.36-1. The snappy packaging, which is included upstream, underwent a lot of changes, but should not be considered as part of this SRU since it doesn't affect the deb builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1811129/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
@VanVan Just updated to kernel 5.0 and the sound on my model ( Asus Q325UAR / dual boot ) does NOT work. How/where can I submit a report so that the model is included in the list for the fix? As far as I am aware the Q325UAR hardware is exactly the same as UX391UA but the model was targeted at a different retailer. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved
okay did the same thing to my sda7 partition install the 5.0.0.8 kernel works lightdm is stable etc. but boot with the 5.0.0.7 kernel fails as per before .. so choice of kernel or it's corresponding initrd is the problem ..here a kernal upgrade fixes the issues -- 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/1821609 Title: Xorg freeze - fails to start or stay going screen blanks-grub seems involved Status in kwallet-pam package in Ubuntu: New Status in lightdm package in Ubuntu: New Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwallet-pam/+bug/1821609/+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 1821810] [NEW] gdebi crashes when trying to install packages
Public bug reported: When I try to install some deb packages gdebi disapears. It does not show me any error report. It will just disapear from my screen. Lubuntu 18.4 LTS gdebi 0.9.5.7+nmu2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdebi 0.9.5.7+nmu2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 26 23:30:04 2019 InstallationDate: Installed on 2019-03-18 (8 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdebi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1821810 Title: gdebi crashes when trying to install packages Status in gdebi package in Ubuntu: New Bug description: When I try to install some deb packages gdebi disapears. It does not show me any error report. It will just disapear from my screen. Lubuntu 18.4 LTS gdebi 0.9.5.7+nmu2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdebi 0.9.5.7+nmu2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 26 23:30:04 2019 InstallationDate: Installed on 2019-03-18 (8 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1821810/+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 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved
okay did something unusual .. i copyed my apt sources and trust files from the working version sda1 to the copy on sda6 the added a series of new proposed updates including a new kernel version on reboot the updated sda6 worked as expected: this was the upgrade package list: including a few earlier xorg/video driver upgrades from previous update for reference too! Install: libxcb-randr0:amd64 (1.13.1-2, automatic), xserver-xorg-video-intel:amd64 (2:2.99.917+git20180925-2, automatic), libxvmc1:amd64 (2:1.0.10-1, automatic), mesa-vulkan-drivers:amd64 (19.0.0-1ubuntu1, automatic) Upgrade: xserver-xorg-input-all:amd64 (1:7.7+19ubuntu11, 1:7.7+19ubuntu12), xserver-xorg:amd64 (1:7.7+19ubuntu11, 1:7.7+19ubuntu12), xserver-xorg-video-all:amd64 (1:7.7+19ubuntu11, 1:7.7+19ubuntu12), xorg:amd64 (1:7.7+19ubuntu11, 1:7.7+19ubuntu12), x11-common:amd64 (1:7.7+19ubuntu11, 1:7.7+19ubuntu12) End-Date: 2019-03-26 16:17:46 updated sources.list sources.d etc. Start-Date: 2019-03-26 17:16:25 Commandline: apt upgrade Requested-By: derk (1000) Install: libpath-tiny-perl:amd64 (0.108-1, automatic), linux-headers-5.0.0-8:amd64 (5.0.0-8.9, automatic), linux-headers-5.0.0-8-generic:amd64 (5.0.0-8.9, automatic), libxpresent1:amd64 (1.0.0-2, automatic), linux-image-5.0.0-8-generic:amd64 (5.0.0-8.9, automatic), linux-modules-5.0.0-8-generic:amd64 (5.0.0-8.9, automatic), libunicode-utf8-perl:amd64 (0.62-1, automatic), linux-modules-extra-5.0.0-8-generic:amd64 (5.0.0-8.9, automatic), libcapture-tiny-perl:amd64 (0.48-1, automatic) Upgrade: libpython3.7-minimal:amd64 (3.7.2-3, 3.7.3-1), perl-base:amd64 (5.28.1-4, 5.28.1-5), fuse:amd64 (2.9.8-1ubuntu1, 2.9.9-1ubuntu1), linux-headers-generic:amd64 (5.0.0.7.8, 5.0.0.8.9), linux-libc-dev:amd64 (5.0.0-7.8, 5.0.0-8.9), libcairo-gobject2:amd64 (1.16.0-3, 1.16.0-4), linux-image-generic:amd64 (5.0.0.7.8, 5.0.0.8.9), rtkit:amd64 (0.11-6, 0.12-4), libsqlite3-0:amd64 (3.27.2-1, 3.27.2-2), python3-gi-cairo:amd64 (3.30.4-1, 3.32.0-1), perl-modules-5.28:amd64 (5.28.1-4, 5.28.1-5), libpython3.7:amd64 (3.7.2-3, 3.7.3-1), python3.7:amd64 (3.7.2-3, 3.7.3-1), gdb:amd64 (8.2.90-0ubuntu1, 8.2.90.20190311-0ubuntu1), python3:amd64 (3.7.2-1, 3.7.3-1), libnm0:amd64 (1.15.2-0ubuntu2, 1.16.0-0ubuntu1), network-manager:amd64 (1.15.2-0ubuntu2, 1.16.0-0ubuntu1), xfwm4:amd64 (4.12.5-1ubuntu1, 4.13.1-3~19.04), libpython3.7-stdlib:amd64 (3.7.2-3, 3.7.3-1), libapparmor1:amd64 (2.12-4ubuntu10, 2.13.2-9ubuntu2), python3.7-minimal:amd64 (3.7.2-3, 3.7.3-1), libperl5.28:amd64 (5.28.1-4, 5.28.1-5), python3-minimal:amd64 (3.7.2-1, 3.7.3-1), libpython3-stdlib:amd64 (3.7.2-1, 3.7.3-1), libfuse2:amd64 (2.9.8-1ubuntu1, 2.9.9-1ubuntu1), lintian:amd64 (2.6.0, 2.11.0), libwebkit2gtk-4.0-37:amd64 (2.23.91-1, 2.24.0-1), python3-gi:amd64 (3.30.4-1, 3.32.0-1), gir1.2-webkit2-4.0:amd64 (2.23.91-1, 2.24.0-1), perl:amd64 (5.28.1-4, 5.28.1-5), rsync:amd64 (3.1.3-5, 3.1.3-6), apparmor:amd64 (2.12-4ubuntu10, 2.13.2-9ubuntu2), gdbserver:amd64 (8.2.90-0ubuntu1, 8.2.90.20190311-0ubuntu1), libcairo2:amd64 (1.16.0-3, 1.16.0-4), python3-gdbm:amd64 (3.7.2-3ubuntu1, 3.7.3-1ubuntu1), libjavascriptcoregtk-4.0-18:amd64 (2.23.91-1, 2.24.0-1), linux-generic:amd64 (5.0.0.7.8, 5.0.0.8.9), gir1.2-javascriptcoregtk-4.0:amd64 (2.23.91-1, 2.24.0-1) End-Date: 2019-03-26 17:18:12 -- 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/1821609 Title: Xorg freeze - fails to start or stay going screen blanks-grub seems involved Status in kwallet-pam package in Ubuntu: New Status in lightdm package in Ubuntu: New Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot
[Touch-packages] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved
okay determined all my installs of xubuntu including the one that works no matter what the others are doing .. do not have kwallet installed .. and the three /etc/pam.d lightdm? configs are all the same .. the missing modules are just ignored .. I tried commenting them out but this does not influence the screen behaviour the versions of lightdm are the same on all the instances: 1.28.0-0ubuntu1 libpam-systemd is the same as well: 240-6ubuntu3 -- 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/1821609 Title: Xorg freeze - fails to start or stay going screen blanks-grub seems involved Status in kwallet-pam package in Ubuntu: New Status in lightdm package in Ubuntu: New Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwallet-pam/+bug/1821609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1821768] Re: Java-gtk3 theming has many artefacts after updating to openjdk-11 in bionic-proposed
Yes, the screenshots are similar. ** Package changed: ubuntu-themes (Ubuntu) => openjdk-lts (Ubuntu) -- 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/1821768 Title: Java-gtk3 theming has many artefacts after updating to openjdk-11 in bionic-proposed Status in openjdk-lts package in Ubuntu: New Bug description: Openjdk-11 is now in bionic-proposed, and apparently it has switched to gtk3. The gtk3-java theming in Ambiance theme is very incomplete in Bionic. I can see a lot of theming artefacts in scilab (default look) and jabref (after switching to gtk look) from bionic-proposed. Steps to compare between java-gtk2 and java-gtk3 theming in Ambiance on Bionic: A. For java-gtk2: 1. Don't update to openjdk-11 in bionic-proposed 2. Install jabref 3.8.2+ds-3 3. Change the look in Preferences to Gtk 4. Notice that the app is properly themed B. For java-gtk3: 5. Install jabref 3.8.2+ds-12~18.04 from bionic-proposed 6. Change the look in Preferences to Gtk 5. Notice that the theming has many artefacts compared to the previous version The same steps can be followed to compare scilab before and after. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20181005-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 16:17:52 2019 InstallationDate: Installed on 2018-11-29 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1821768/+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 1803441] Re: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch)
I don't think they are the same issue. Or, at least, the first issue was only partially fixed. I can see both Fedora 29 and Ubuntu 18.10 being still affected by the issue outlined in https://lists.gnu.org/archive/html/bug-bash/2017-12/msg00065.html, though they are not affected by https://lists.gnu.org/archive/html/bug- bash/2017-03/msg00077.html. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1803441 Title: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch) Status in bash package in Ubuntu: New Bug description: In 14.04 LTS, the BASH_CMDS variable is writable in rbash. This allows a trivial escape from rbash to run arbitrary shell commands. This issue is fixed upstream: http://git.savannah.gnu.org/cgit/bash.git/tree/CHANGES?h=bash-4.4-testing#n65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1803441/+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 1803441] Re: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch)
I'm sorry Riccardo, I didn't notice the two separate BASH_CMDS issues when I filed the request. The only mention in the changelog is: > This document details the changes between this version, bash-4.4-beta2, > and the previous version, bash-4.4-rc1. >$ > [...] >$ > d. Fixed a bug that allowed assignments to BASH_CMDS when the shell was > in restricted mode. http://git.savannah.gnu.org/cgit/bash.git/tree/CHANGES?h=bash-4.4-testing#n65 I did not find a single well-defined patch or commit for this, so completely overlooked that there are multiple issues. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1803441 Title: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch) Status in bash package in Ubuntu: New Bug description: In 14.04 LTS, the BASH_CMDS variable is writable in rbash. This allows a trivial escape from rbash to run arbitrary shell commands. This issue is fixed upstream: http://git.savannah.gnu.org/cgit/bash.git/tree/CHANGES?h=bash-4.4-testing#n65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1803441/+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 1821768] Re: Java-gtk3 theming has many artefacts after updating to openjdk-11 in bionic-proposed
Could you please take a look at bug #1770278 and look if the screenshot with the artifacts is the same/similar to what you are seeing here? -- 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/1821768 Title: Java-gtk3 theming has many artefacts after updating to openjdk-11 in bionic-proposed Status in ubuntu-themes package in Ubuntu: New Bug description: Openjdk-11 is now in bionic-proposed, and apparently it has switched to gtk3. The gtk3-java theming in Ambiance theme is very incomplete in Bionic. I can see a lot of theming artefacts in scilab (default look) and jabref (after switching to gtk look) from bionic-proposed. Steps to compare between java-gtk2 and java-gtk3 theming in Ambiance on Bionic: A. For java-gtk2: 1. Don't update to openjdk-11 in bionic-proposed 2. Install jabref 3.8.2+ds-3 3. Change the look in Preferences to Gtk 4. Notice that the app is properly themed B. For java-gtk3: 5. Install jabref 3.8.2+ds-12~18.04 from bionic-proposed 6. Change the look in Preferences to Gtk 5. Notice that the theming has many artefacts compared to the previous version The same steps can be followed to compare scilab before and after. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20181005-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 16:17:52 2019 InstallationDate: Installed on 2018-11-29 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1821768/+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 984390] Re: $PATH is taken from login.defs not /etc/environment
Hello James, or anyone else affected, Accepted shadow into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shadow/1:4.2-3.1ubuntu5.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: shadow (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- 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/984390 Title: $PATH is taken from login.defs not /etc/environment Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Precise: Won't Fix Status in shadow source package in Xenial: Fix Committed Status in shadow source package in Bionic: Fix Committed Bug description: $PATH isn't sourced from /etc/environment, instead the version in /etc/login.defs is used. (The example below comes from a precise install.) | james@panlong:~$ echo $PATH | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games | james@panlong:~$ sudo su - buildd | buildd@panlong:~$ echo $PATH | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | buildd@panlong:~$ cat /etc/environment | PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" | buildd@panlong:~$ grep PATH /etc/login.defs | # Three items must be defined: MAIL_DIR, ENV_SUPATH, and ENV_PATH. | # *REQUIRED* The default PATH settings, for superuser and normal users. | ENV_SUPATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin | ENV_PATH PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | #CRACKLIB_DICTPATH | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" /etc/login.defs | buildd@panlong:~$ logout | james@panlong:~$ sudo su - buildd | buildd@panlong:~$ echo $PATH | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | buildd@panlong:~$ REGRESSION POTENTIAL: - medium: it changes (incorrect) existing behaviour so https://xkcd.com/1172/ may apply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/984390/+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 1495580] Re: chfn needs to learn about the --extrausers argument and use libnss-extrausers files when set
Hello Oliver, or anyone else affected, Accepted shadow into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shadow/1:4.2-3.1ubuntu5.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: shadow (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1495580 Title: chfn needs to learn about the --extrausers argument and use libnss- extrausers files when set Status in Snappy: Fix Released Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Fix Committed Status in shadow source package in Bionic: Fix Released Bug description: as seen in bug 1492327, adduser now works for creating users in the extrausers db but when it tries to update the GECOS field at the end of adding a user (interactively and noninteractively) chfn falls over ... chfn needs similar patches to the other shadow binaries that recently got extrausers support. TEST CASE: - create a user "foo" on an Ubuntu Core system - run "chfn --extrausers -f some-name foo" on an Ubuntu Core system REGRESSION POTENTIAL: - low: this requires the new (and optional) --extrausers switch to change anything. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1495580/+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 1659534] Re: userdel doesn't supports extrausers
Hello Matteo, or anyone else affected, Accepted shadow into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shadow/1:4.2-3.1ubuntu5.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: shadow (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- 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/1659534 Title: userdel doesn't supports extrausers Status in Snappy: In Progress Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Fix Committed Status in shadow source package in Bionic: Fix Committed Bug description: TEST CASE: - run userdel --extrausers foo on a ubuntu core system REGRESSION POTENTIAL: - low, this option will only take effect when "userdel --extrauser" is used. On an Ubuntu Core system is impossible to delete an user from the extrausers db: root@localhost:/# userdel --extrausers alice userdel: unrecognized option '--extrausers' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+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 1803441] Re: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch)
Yes, that's basically the same issue. It was patched upstream many years ago (2016 I recall) however as of last fall Ubuntu old-LTS had not backported the fix. I used this bug to escape from rbash during a security audit of a fully patched Ubuntu system in October. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1803441 Title: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch) Status in bash package in Ubuntu: New Bug description: In 14.04 LTS, the BASH_CMDS variable is writable in rbash. This allows a trivial escape from rbash to run arbitrary shell commands. This issue is fixed upstream: http://git.savannah.gnu.org/cgit/bash.git/tree/CHANGES?h=bash-4.4-testing#n65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1803441/+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 1759014] Re: Netplan has no way to control DHCP client
This means we'll need to identify what patches need to be applied on top
of v237 to make this work.
Is this crippling? Are we able to verify that dhcp customization work
despite anything missing in systemd? I think it's the case; but I'd like
a second opinion. To be clear: I think we can verify this SRU despite
any additional issues existing in systemd that also might need to be
fixed.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/1759014
Title:
Netplan has no way to control DHCP client
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
New
Status in netplan.io source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
New
Status in netplan.io source package in Cosmic:
Fix Committed
Status in systemd source package in Cosmic:
New
Status in netplan.io source package in Disco:
Fix Released
Status in systemd source package in Disco:
New
Bug description:
[Impact]
DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
[Test case]
1) Configure netplan for the particulars of the network by configuring an
appropriate dhcp{4,6}-override stanza:
network:
version: 2
ethernets:
engreen:
dhcp4: true
dhcp4-overrides:
use-dns: false
use-routes: false
route-metric:
Additionally, if so required, add a custom DNS / routes to the
configuration. e.g.
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
(See https://netplan.io/reference#dhcp-overrides for the available
options)
2) Run 'netplan apply' or reboot to have the configuration applied.
3) Validate that the routes / DNS are properly ignored and/or replaced by the
defined values.
[Regression potential]
Minimal; this adds new values to the configuration generated for networkd or
NetworkManager. Existing configurations will remain unchanged, but new
configurations using the dhcp{4,6}-overrides fields will benefit from
additional flexibility.
---
Currently DHCP appears to be an all or nothing boolean, which is insufficient
for many network configurations.
Ideally all of the DHCP configuration options supported by systemd would also
be supported in netplan:
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options
As an example, consider the following netplan configuration:
network:
version: 2
renderer: networkd
ethernets:
enp0s3:
dhcp4: yes
nameservers: [8.8.8.8,8.8.4.4]
After running netplan apply I check the nameservers with systemd-
resolve --status and it shows:
DNS Servers: 8.8.8.8
8.8.4.4
192.168.1.1
Here, "192.168.1.1" was provided by my DHCP server. On this
particular node, I only want the manually configured DNS servers, but
netplan has no way to indicate this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
This bug was fixed in the package xorg - 1:7.7+19ubuntu12 --- xorg (1:7.7+19ubuntu12) disco; urgency=medium * control: Restore -intel to x-x-video-all Recommends, glamor needs OpenGL 2.1 which i915_dri.so doesn't support. (LP: #1819943) * control: Add mesa-vulkan-drivers back to xserver-xorg recommends. -- Timo Aaltonen Tue, 26 Mar 2019 17:46:22 +0200 ** Changed in: xorg (Ubuntu) Status: In Progress => Fix Released -- 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/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) Status in xorg package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Incomplete Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1819943/+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 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem
Jamie, are you using an ISO install or a cloud image for your test? I was seeing this in a cloud image. (When we were debugging on IRC, I recall that being a difference that meant people couldn't reproduce.) ** Changed in: iptables (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1820114 Title: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Status in iptables package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I hit this error on disco: ``` $ free -h totalusedfree shared buff/cache available Mem: 478Mi98Mi 311Mi 0.0Ki68Mi 366Mi Swap:0B 0B 0B $ sudo iptables -S iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: iptables 1.6.1-2ubuntu3 ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Thu Mar 14 19:16:15 2019 SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 DistroRelease: Ubuntu 19.04 Package: linux PackageArchitecture: amd64 ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0 Tags: disco uec-images Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1820114/+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 1804280] Re: intermittent periods of packet loss and high latency
This could be the same issue as those other two. Similar hardware is involved. I haven't had time to test changing those settings on the NIC. On 2019-03-21 6:41 a.m., Kai-Heng Feng wrote: > Is this same as LP: #1785171 and #1802691? > -- 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/1804280 Title: intermittent periods of packet loss and high latency Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Intermittently and unpredictably, ping response times and packet loss will spike to unusable levels. Normal ping times are about .25 ms for other hosts on the local network, with essentially no packet loss. During the problematic periods (usually lasting 2-10 minutes), packet loss jumps to about 50% and ping response times on the packets that aren't dropped jump to between 250 and 750 ms. This behavior started when I upgraded from Kubuntu 16.04 to Kubuntu 18.04. Changing which host on the network I test this with has no effect (and during this, those other hosts are able to use the network without any problem). Replacing the cable changes nothing. Using a different Ethernet interface changes nothing. Replacing the switch changes nothing. This is almost certainly not a hardware problem. There is a chance that using wireless instead of Ethernet would fix the issue, but I have been avoiding that since the wired connection is much faster when Kubuntu is not malfunctioning. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 20 12:48:05 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-12-09 (711 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via [removed] dev enp0s31f6 proto dhcp metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 [removed]/24 dev enp0s31f6 proto kernel scope link src [removed] metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-08-19 (92 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s31f6 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 2e0d0ce3-8ee2-3c06-815d-eb9a42873b3b /org/freedesktop/NetworkManager/ActiveConnection/5 [removed] btdisconnected /org/freedesktop/NetworkManager/Devices/5 -- ---- wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/4 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2053 F pulseaudio /dev/snd/pcmC1D0c: dan2053 F...m pulseaudio /dev/snd/controlC1: dan2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4eadd7fe-e046-471d-b0ee-f1c85365411e IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-12-09 (712 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.4.1 dev enp0s31f6 proto dhcp metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.42 metric 100 MachineType: Dell Inc. Precision Tower 3420 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=89b1b98c-8c19-4200-966b-190a0ca0 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
[Touch-packages] [Bug 1817799] Re: [FFe] apparmor 2.13
Uploaded to disco-proposed. ** Changed in: apparmor (Ubuntu) Status: Triaged => Fix Committed -- 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/1817799 Title: [FFe] apparmor 2.13 Status in apparmor package in Ubuntu: Fix Committed Bug description: Feature Freeze exception for AppArmor 2.13.2 The security team is pushing to get AppArmor 2.13 into 19.04 since we want AppArmor 3 (or higher) in 20.04 and we'd like to update to 2.13.2 to have widespread use of its new features and make the overall experience to AppArmor 3 better tested and less disruptive. The 2.13.2 series over 2.12 is primarily incremental improvements in the parser, libapparmor, userspace tooling and policy; Debian started preparing 2.13 in experimental last June where the first upload to unstable was made in July. Since then, Debian has worked closely with upstream and Ubuntu devs to shake out bugs and improve the packaging. There are no new mediation rules so the chance of regression in terms of parser/kernel/policy updates is considered low. IME, the primary points of interest for the FFe surround the following: * apparmor_parser in 2.13 now creates subdirectories in the cache directory with the subdir name based on the kernel features. This improves the experience when booting between kernels with different feature sets * Debian moved /etc/apparmor.d/cache to /var/cache/apparmor (first upload with this change in August) * the init process now uses proper systemd unit instead of calling out to SysV init script. This and rc.apparmor.functions cleanups were done in coordination with Ubuntu devs (first upload in December) * due to bug #1820068, the 2.12 and earlier Ubuntu-distro patch to use -O no-expr-simplify (helps with policy compilation times on armhf) has been reverted. We'll get the bug fixed before disco release Debian has been very active in improving the packaging since the plan is to release with AppArmor by default in Buster (it has been on by default in Debian testing for a long time, before the 2.13 uploads). A version of 2.13.2 has been in Debian testing (Buster) since January with the 2.13.2-9 version that this FFe is based on migrating last week. Debian improved autopkgtests throughout Buster, worked with upstream and Ubuntu devs throughout. Because of the extensive baking in Debian, I think it is reasonable to consider granting the exception (indeed, part of why we missed Disco's freeze was because we were working with Debian on improving the package for Buster's freeze). While most software in Ubuntu doesn't care about the systemd or cache changes, it was known that snapd manages snap cache files on snap remove, and snapd needed to be changed to account for this[2]. This update is included in snapd 2.38 which is now in disco. Because of the change in the apparmor cache, I have introduced a Breaks: snapd (<< 2.38~) in the apparmor package since snaps cannot be removed (snapd aborts the removal when the cache file is not found; which is a little strict IMO, but I digress). In terms of testing, we exercised our test plan, like normal[1]. This includes upgrade testing, verifying profile load on boot, cache is used and software with apparmor integration continue to work (snapd, lxc, lxd, libvirt, docker, etc). Anecdotally I have been using 2.13.2 for some time without issue (and I have a lot of snap, distro and personal policy). The source tarball does not contain a changelog, instead the upstream release notes can be found here: * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.1 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.2 [1]https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [2]https://github.com/snapcore/snapd/pull/6549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+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 1804280] Re: intermittent periods of packet loss and high latency
I have been experiencing identical issues since around mid-January or so (though my latency sometimes reaches 3000/4000+ ms during these times). I am running a freshly installed and fully updated version of Ubuntu 18.04 Desktop. For the first couple of months after installing 18.04 I had none of these issues whatsoever, they seemed to materialize during a period when I was doing a lot of heavy software development which used a great deal of system resources (multiple VMs). Originally the workstation was wired directly to my router, but even after purchasing a wireless USB adapter I am still experiencing the issue. I typically use remote viewing software to work on the affected workstation (from another laptop in my home), and once I begin to notice moderate sluggishness in the response time of the system I can typically run "sudo systemctl restart network-manager" and I will usually not begin to experience the issue again until several hours later, typically. If I go too long without running that command the full 10-15 minute period of extreme latency will set in. It doesn't return fully to "normal" response times after that high period, but it is far lower than the most extreme patches. I hesitate to say that the issue is similar to other bug reports because of the "dropping of the connection" aspects of those. The connection never fully dies in this case, but just experiences periods of latency related unusability. Any logs or further info available upon request. -- 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/1804280 Title: intermittent periods of packet loss and high latency Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Intermittently and unpredictably, ping response times and packet loss will spike to unusable levels. Normal ping times are about .25 ms for other hosts on the local network, with essentially no packet loss. During the problematic periods (usually lasting 2-10 minutes), packet loss jumps to about 50% and ping response times on the packets that aren't dropped jump to between 250 and 750 ms. This behavior started when I upgraded from Kubuntu 16.04 to Kubuntu 18.04. Changing which host on the network I test this with has no effect (and during this, those other hosts are able to use the network without any problem). Replacing the cable changes nothing. Using a different Ethernet interface changes nothing. Replacing the switch changes nothing. This is almost certainly not a hardware problem. There is a chance that using wireless instead of Ethernet would fix the issue, but I have been avoiding that since the wired connection is much faster when Kubuntu is not malfunctioning. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 20 12:48:05 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-12-09 (711 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via [removed] dev enp0s31f6 proto dhcp metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 [removed]/24 dev enp0s31f6 proto kernel scope link src [removed] metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-08-19 (92 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s31f6 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 2e0d0ce3-8ee2-3c06-815d-eb9a42873b3b /org/freedesktop/NetworkManager/ActiveConnection/5 [removed] btdisconnected /org/freedesktop/NetworkManager/Devices/5 -- ---- wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/4 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse:
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
** Changed in: ubuntu-power-systems Status: Won't Fix => In Progress -- 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/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: In Progress Status in linux source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: In Progress Status in linux source package in Cosmic: Invalid Status in makedumpfile source package in Cosmic: Invalid Status in initramfs-tools source package in Disco: In Progress Status in linux source package in Disco: Invalid Status in makedumpfile source package in Disco: Invalid Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR:
[Touch-packages] [Bug 1817799] Re: [FFe] apparmor 2.13
I've confirmed that the "Could not open '/var/lib/snapd/apparmor/snap- confine'" is not present in standard install of disco. This was a local issue. I've also updated the packaging to remove the "dpkg: warning: unable to delete old directory '/etc/apparmor.d/cache': Directory not empty" message. postinst was doing the cleaning so the end result was ok, but we can be better. Thanks Adam for the review! -- 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/1817799 Title: [FFe] apparmor 2.13 Status in apparmor package in Ubuntu: Triaged Bug description: Feature Freeze exception for AppArmor 2.13.2 The security team is pushing to get AppArmor 2.13 into 19.04 since we want AppArmor 3 (or higher) in 20.04 and we'd like to update to 2.13.2 to have widespread use of its new features and make the overall experience to AppArmor 3 better tested and less disruptive. The 2.13.2 series over 2.12 is primarily incremental improvements in the parser, libapparmor, userspace tooling and policy; Debian started preparing 2.13 in experimental last June where the first upload to unstable was made in July. Since then, Debian has worked closely with upstream and Ubuntu devs to shake out bugs and improve the packaging. There are no new mediation rules so the chance of regression in terms of parser/kernel/policy updates is considered low. IME, the primary points of interest for the FFe surround the following: * apparmor_parser in 2.13 now creates subdirectories in the cache directory with the subdir name based on the kernel features. This improves the experience when booting between kernels with different feature sets * Debian moved /etc/apparmor.d/cache to /var/cache/apparmor (first upload with this change in August) * the init process now uses proper systemd unit instead of calling out to SysV init script. This and rc.apparmor.functions cleanups were done in coordination with Ubuntu devs (first upload in December) * due to bug #1820068, the 2.12 and earlier Ubuntu-distro patch to use -O no-expr-simplify (helps with policy compilation times on armhf) has been reverted. We'll get the bug fixed before disco release Debian has been very active in improving the packaging since the plan is to release with AppArmor by default in Buster (it has been on by default in Debian testing for a long time, before the 2.13 uploads). A version of 2.13.2 has been in Debian testing (Buster) since January with the 2.13.2-9 version that this FFe is based on migrating last week. Debian improved autopkgtests throughout Buster, worked with upstream and Ubuntu devs throughout. Because of the extensive baking in Debian, I think it is reasonable to consider granting the exception (indeed, part of why we missed Disco's freeze was because we were working with Debian on improving the package for Buster's freeze). While most software in Ubuntu doesn't care about the systemd or cache changes, it was known that snapd manages snap cache files on snap remove, and snapd needed to be changed to account for this[2]. This update is included in snapd 2.38 which is now in disco. Because of the change in the apparmor cache, I have introduced a Breaks: snapd (<< 2.38~) in the apparmor package since snaps cannot be removed (snapd aborts the removal when the cache file is not found; which is a little strict IMO, but I digress). In terms of testing, we exercised our test plan, like normal[1]. This includes upgrade testing, verifying profile load on boot, cache is used and software with apparmor integration continue to work (snapd, lxc, lxd, libvirt, docker, etc). Anecdotally I have been using 2.13.2 for some time without issue (and I have a lot of snap, distro and personal policy). The source tarball does not contain a changelog, instead the upstream release notes can be found here: * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.1 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.2 [1]https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [2]https://github.com/snapcore/snapd/pull/6549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+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 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove
Verified with 1.1ubuntu1.18.04.10 on Bionic: ... root@bb-uu-lp-1795696-verify:~# eatmydata apt install linux-image-unsigned-4.18.0-13-generic linux-image-unsigned-4.18.0-14-generic linux-image-unsigned-4.18.0-15-generic ... root@bb-uu-lp-1795696-verify:~# apt-mark auto linux-image-unsigned-4.18.0-13-generic linux-image-unsigned-4.18.0-14-generic linux-image-unsigned-4.18.0-15-generic linux-image-unsigned-4.18.0-13-generic set to automatically installed. linux-image-unsigned-4.18.0-14-generic set to automatically installed. linux-image-unsigned-4.18.0-15-generic set to automatically installed. root@bb-uu-lp-1795696-verify:~# /etc/kernel/postinst.d/apt-auto-removal root@bb-uu-lp-1795696-verify:~# apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common libfreetype6 linux-image-unsigned-4.18.0-13-generic linux-image-unsigned-4.18.0-14-generic linux-image-unsigned-4.18.0-15-generic linux-modules-4.18.0-13-generic linux-modules-4.18.0-14-generic linux-modules-4.18.0-15-generic os-prober 0 upgraded, 0 newly installed, 13 to remove and 7 not upgraded. After this operation, 239 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. root@bb-uu-lp-1795696-verify:~# vi /etc/apt/apt.conf.d/50unattended-upgrades root@bb-uu-lp-1795696-verify:~# grep Minimal /etc/apt/apt.conf.d/50unattended-upgrades Unattended-Upgrade::MinimalSteps "false"; root@bb-uu-lp-1795696-verify:~# unattended-upgrade --dry-run --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic Removing unused kernel packages: linux-modules-4.18.0-13-generic linux-modules-4.18.0-15-generic linux-modules-4.18.0-14-generic Keeping 3 auto-removable package(s) because it would also remove the following packages which should be kept in this step: libntfs-3g88 linux-image-unsigned-4.18.0-13-generic linux-image-unsigned-4.18.0-14-generic linux-image-unsigned-4.18.0-15-generic ntfs-3g snapd Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1798, in main options.verbose or options.debug, options.dry_run) File "/usr/bin/unattended-upgrade", line 1495, in do_auto_remove if res: UnboundLocalError: local variable 'res' referenced before assignment oot@bb-uu-lp-1795696-verify:~# echo "deb http://archive.ubuntu.com/ubuntu/ bionic-proposed restricted main multiverse universe" > /etc/apt/sources.list.d/proposed.list root@bb-uu-lp-1795696-verify:~# apt update -qq 33 packages can be upgraded. Run 'apt list --upgradable' to see them. root@bb-uu-lp-1795696-verify:~# apt install unattended-upgrades Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common libfreetype6 linux-image-unsigned-4.18.0-13-generic linux-image-unsigned-4.18.0-14-generic linux-image-unsigned-4.18.0-15-generic linux-modules-4.18.0-13-generic linux-modules-4.18.0-14-generic linux-modules-4.18.0-15-generic os-prober Use 'apt autoremove' to remove them. Suggested packages: bsd-mailx default-mta | mail-transport-agent needrestart The following packages will be upgraded: unattended-upgrades 1 upgraded, 0 newly installed, 0 to remove and 32 not upgraded. Need to get 40.4 kB of archives. After this operation, 4096 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 unattended-upgrades all 1.1ubuntu1.18.04.10 [40.4 kB] Fetched 40.4 kB in 0s (204 kB/s) N: Ignoring file 'proposed' in directory '/etc/apt/sources.list.d/' as it has no filename extension Preconfiguring packages ... (Reading database ... 32894 files and directories currently installed.) Preparing to unpack .../unattended-upgrades_1.1ubuntu1.18.04.10_all.deb ... Unpacking unattended-upgrades (1.1ubuntu1.18.04.10) over (1.1ubuntu1.18.04.9) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for systemd (237-3ubuntu10.15) ... Setting up unattended-upgrades (1.1ubuntu1.18.04.10) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... N: Ignoring file 'proposed' in directory '/etc/apt/sources.list.d/' as it has no filename extension root@bb-uu-lp-1795696-verify:~# unattended-upgrade --dry-run --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic Removing unused kernel packages: linux-modules-4.18.0-13-generic linux-modules-4.18.0-15-generic linux-modules-4.18.0-14-generic Keeping 3
[Touch-packages] [Bug 1817799] Re: [FFe] apparmor 2.13
As discussed on IRC, if the upgrade is clean, and you're committing to keeping a close eye on bugs/regressions and fixing ASAP, go for it. ** Changed in: apparmor (Ubuntu) Status: New => Triaged -- 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/1817799 Title: [FFe] apparmor 2.13 Status in apparmor package in Ubuntu: Triaged Bug description: Feature Freeze exception for AppArmor 2.13.2 The security team is pushing to get AppArmor 2.13 into 19.04 since we want AppArmor 3 (or higher) in 20.04 and we'd like to update to 2.13.2 to have widespread use of its new features and make the overall experience to AppArmor 3 better tested and less disruptive. The 2.13.2 series over 2.12 is primarily incremental improvements in the parser, libapparmor, userspace tooling and policy; Debian started preparing 2.13 in experimental last June where the first upload to unstable was made in July. Since then, Debian has worked closely with upstream and Ubuntu devs to shake out bugs and improve the packaging. There are no new mediation rules so the chance of regression in terms of parser/kernel/policy updates is considered low. IME, the primary points of interest for the FFe surround the following: * apparmor_parser in 2.13 now creates subdirectories in the cache directory with the subdir name based on the kernel features. This improves the experience when booting between kernels with different feature sets * Debian moved /etc/apparmor.d/cache to /var/cache/apparmor (first upload with this change in August) * the init process now uses proper systemd unit instead of calling out to SysV init script. This and rc.apparmor.functions cleanups were done in coordination with Ubuntu devs (first upload in December) * due to bug #1820068, the 2.12 and earlier Ubuntu-distro patch to use -O no-expr-simplify (helps with policy compilation times on armhf) has been reverted. We'll get the bug fixed before disco release Debian has been very active in improving the packaging since the plan is to release with AppArmor by default in Buster (it has been on by default in Debian testing for a long time, before the 2.13 uploads). A version of 2.13.2 has been in Debian testing (Buster) since January with the 2.13.2-9 version that this FFe is based on migrating last week. Debian improved autopkgtests throughout Buster, worked with upstream and Ubuntu devs throughout. Because of the extensive baking in Debian, I think it is reasonable to consider granting the exception (indeed, part of why we missed Disco's freeze was because we were working with Debian on improving the package for Buster's freeze). While most software in Ubuntu doesn't care about the systemd or cache changes, it was known that snapd manages snap cache files on snap remove, and snapd needed to be changed to account for this[2]. This update is included in snapd 2.38 which is now in disco. Because of the change in the apparmor cache, I have introduced a Breaks: snapd (<< 2.38~) in the apparmor package since snaps cannot be removed (snapd aborts the removal when the cache file is not found; which is a little strict IMO, but I digress). In terms of testing, we exercised our test plan, like normal[1]. This includes upgrade testing, verifying profile load on boot, cache is used and software with apparmor integration continue to work (snapd, lxc, lxd, libvirt, docker, etc). Anecdotally I have been using 2.13.2 for some time without issue (and I have a lot of snap, distro and personal policy). The source tarball does not contain a changelog, instead the upstream release notes can be found here: * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.1 * https://gitlab.com/apparmor/apparmor/wikis/Release_Notes_2.13.2 [1]https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [2]https://github.com/snapcore/snapd/pull/6549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1817799/+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 1778844] Re: nvme multipath does not report path relationships
** Patch added: "initramfs-tools_0.131ubuntu19.debdiff" https://bugs.launchpad.net/ubuntu-power-systems/+bug/1778844/+attachment/5249521/+files/initramfs-tools_0.131ubuntu19.debdiff ** Description changed: + [Impact] + initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. + + [Test case] + Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. + + [Regression potential] + A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. + + + - + + Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h - totalusedfree shared buff/cache available + totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: -/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic + /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: -/var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic + /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: - /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz + /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00
[Touch-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
Thanks, nice collection of crashes, but no NetworkManager. -- 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/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) Status in gnome-control-center: New Status in NetworkManager: New Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+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 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
** Attachment added: "$ ll /var/crash" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1810316/+attachment/5249520/+files/ll_var-crash.txt -- 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/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) Status in gnome-control-center: New Status in NetworkManager: New Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
The regression potential here in the description is incorrect "We are simply backporting the workaround we applied in Ubuntu 18.10." The fix in Ubuntu 18.10 for both packages was to add "--no-as-needed" to the build options which you now indicate is a worse solution. Please also upload the better fix to the cosmic SRU queue. ** Changed in: libidn (Ubuntu Bionic) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Incomplete Status in libunistring source package in Bionic: Fix Committed Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 18.10. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
To anyone who has observed this problem: Please check the contents of your /var/crash/ directory. Is there a file with the ".crash" extension and NetworkManager or networkmanager in its name and the day when you observed the problem as file date? In this case also NetworkManager has crashed. Then please call "apport-bug" with this file as command line argument: apport-bug /var/crash/... This will generate a new bug report with more info about your crash of NetworkManager. Add a link to this bug report here. Or tell here for the case that you do not get a crash file related to NetworkManager. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) Status in gnome-control-center: New Status in NetworkManager: New Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
Hello Matthias, or anyone else affected, Accepted libunistring into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libunistring/0.9.9-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libunistring (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Incomplete Status in libunistring source package in Bionic: Fix Committed Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 18.10. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 984390] Re: $PATH is taken from login.defs not /etc/environment
Hello James, or anyone else affected, Accepted shadow into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shadow/1:4.5-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: shadow (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/984390 Title: $PATH is taken from login.defs not /etc/environment Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Precise: Won't Fix Status in shadow source package in Xenial: New Status in shadow source package in Bionic: Fix Committed Bug description: $PATH isn't sourced from /etc/environment, instead the version in /etc/login.defs is used. (The example below comes from a precise install.) | james@panlong:~$ echo $PATH | /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games | james@panlong:~$ sudo su - buildd | buildd@panlong:~$ echo $PATH | /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | buildd@panlong:~$ cat /etc/environment | PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" | buildd@panlong:~$ grep PATH /etc/login.defs | # Three items must be defined: MAIL_DIR, ENV_SUPATH, and ENV_PATH. | # *REQUIRED* The default PATH settings, for superuser and normal users. | ENV_SUPATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin | ENV_PATH PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | #CRACKLIB_DICTPATH | buildd@panlong:~$ sudo sed -i -e "s#^ENV_PATH.*#ENV_PATH PATH=/wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games#" /etc/login.defs | buildd@panlong:~$ logout | james@panlong:~$ sudo su - buildd | buildd@panlong:~$ echo $PATH | /wtf:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games | buildd@panlong:~$ REGRESSION POTENTIAL: - medium: it changes (incorrect) existing behaviour so https://xkcd.com/1172/ may apply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/984390/+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 1659534] Re: userdel doesn't supports extrausers
Hello Matteo, or anyone else affected, Accepted shadow into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shadow/1:4.5-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: shadow (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1659534 Title: userdel doesn't supports extrausers Status in Snappy: In Progress Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: In Progress Status in shadow source package in Bionic: Fix Committed Bug description: TEST CASE: - run userdel --extrausers foo on a ubuntu core system REGRESSION POTENTIAL: - low, this option will only take effect when "userdel --extrauser" is used. On an Ubuntu Core system is impossible to delete an user from the extrausers db: root@localhost:/# userdel --extrausers alice userdel: unrecognized option '--extrausers' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+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 1821101] Re: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade
It was Bionic ^. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821101 Title: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the introduced fallbacks u-u could not upgrade particular package sets from -security. It could be observed in Cosmic with systemd security updates failing to install in: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to marking test2-package, then adjusting changes DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:falling back to marking test3-package, then adjusting changes WARNING:root:package test3-package upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) DEBUG:root:falling back to adjusting all packages DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-old-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 WARNING:root:package z-package upgradable but fails to be marked for upgrade () . -- Ran 1 test in 0.039s OK [Regression Potential] * When failing to mark a package to upgrade/install from the allowed origin holding the highest version the first fallback resets all already adjusted candidates to the highest available version irrespective to the origin of this version being allowed or not. This itself is not a risky operation and sanity checks later ensure that no package would be installed from not allowed origins but it can trigger code paths in apt that were not tried before and may crash. * In testing apt's resolver failed to find a solution for upgrading packages with the first fallback raising an error, but the second fallback handles the error and tries adjusting _all_ potentially upgradable/installable package at the expense of using much more CPU time. This second fallback is not expected to be reached often (it is not reached in autopkgtests either) and adjusting all of those packages matches an earlier behavior of u-u, thus the slow-down may not be considered a regression. [Other Info] * If the second fallback is found to be reached often a different fallback can be introduced before the first one, to adjust all packages from the same source package then try again: See: https://github.com/mvo5/unattended-upgrades/pull/175#discussion_r268226796 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821101/+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 1820888] Re: unattended-upgrades may hold back upgrades due to comparing package versions by their string representation
Tested with 1.5ubuntu3.18.10.3 on Cosmic: https://launchpadlibrarian.net/416582074/buildlog_ubuntu-cosmic-amd64.unattended-upgrades_1.5ubuntu3.18.10.3_BUILDING.txt.gz : ... OK Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 ... OK ... ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic ** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1820888 Title: unattended-upgrades may hold back upgrades due to comparing package versions by their string representation Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the fix u-u could not upgrade particular packages from -security. It could be observed in Cosmic with systemd security updates failing to install partly due to 239-7ubuntu10.10 being smaller than 239-7ubuntu10.8 when comparing them as strings: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: ... Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 ... With the unfixed version the test case fails here because u-u tries to upgrade test-package to version 12.0 because it does not find version 2.0 smaller. [Regression Potential] * The change is very small and isolated, but fixing it revealed the issue fixed in LP: #1821101. Since the found issue's fix introduces fallbacks when apt's resolver can't find a the solution it is unlikely that other failures are triggered by the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1820888/+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 1820888] Re: unattended-upgrades may hold back upgrades due to comparing package versions by their string representation
Tested with 1.1ubuntu1.18.04.10 on Bionic: https://launchpadlibrarian.net/416582722/buildlog_ubuntu-bionic-amd64.unattended-upgrades_1.1ubuntu1.18.04.10_BUILDING.txt.gz : ... Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 ... -- Ran 1 test in 0.051s OK ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1820888 Title: unattended-upgrades may hold back upgrades due to comparing package versions by their string representation Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the fix u-u could not upgrade particular packages from -security. It could be observed in Cosmic with systemd security updates failing to install partly due to 239-7ubuntu10.10 being smaller than 239-7ubuntu10.8 when comparing them as strings: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: ... Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 ... With the unfixed version the test case fails here because u-u tries to upgrade test-package to version 12.0 because it does not find version 2.0 smaller. [Regression Potential] * The change is very small and isolated, but fixing it revealed the issue fixed in LP: #1821101. Since the found issue's fix introduces fallbacks when apt's resolver can't find a the solution it is unlikely that other failures are triggered by the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1820888/+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 1821101] Re: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade
Tested with 1.5ubuntu3.18.10.3 on Cosmic: https://launchpadlibrarian.net/416582074/buildlog_ubuntu-cosmic-amd64.unattended-upgrades_1.5ubuntu3.18.10.3_BUILDING.txt.gz : ... OK Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to marking test2-package, then adjusting changes DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:falling back to marking test3-package, then adjusting changes WARNING:root:package test3-package upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) DEBUG:root:falling back to adjusting all packages DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-old-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 WARNING:root:package z-package upgradable but fails to be marked for upgrade () . -- Ran 1 test in 0.025s OK ... ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic ** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => In Progress ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821101 Title: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the introduced fallbacks u-u could not upgrade particular package sets from -security. It could be observed in Cosmic with systemd security updates failing to install in: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to marking test2-package, then adjusting changes DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:falling back to marking test3-package, then adjusting changes WARNING:root:package test3-package upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) DEBUG:root:falling back to adjusting all packages DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-old-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 WARNING:root:package z-package upgradable but fails to be marked for upgrade () . -- Ran 1 test in 0.039s OK [Regression Potential] * When failing to mark a package to upgrade/install from the allowed origin holding the highest version the first fallback resets all already adjusted candidates to the highest available version irrespective to the origin of this version being allowed or not. This itself is not a risky operation and sanity checks later ensure that no package would be installed from not allowed origins
[Touch-packages] [Bug 1821101] Re: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade
Tested with 1.1ubuntu1.18.04.10 on Cosmic: https://launchpadlibrarian.net/416582722/buildlog_ubuntu-bionic-amd64.unattended-upgrades_1.1ubuntu1.18.04.10_BUILDING.txt.gz : ... Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to marking test2-package, then adjusting changes DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:falling back to marking test3-package, then adjusting changes WARNING:root:package test3-package upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) DEBUG:root:falling back to adjusting all packages DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-old-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 WARNING:root:package z-package upgradable but fails to be marked for upgrade () . -- Ran 1 test in 0.051s OK -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821101 Title: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the introduced fallbacks u-u could not upgrade particular package sets from -security. It could be observed in Cosmic with systemd security updates failing to install in: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to marking test2-package, then adjusting changes DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:falling back to marking test3-package, then adjusting changes WARNING:root:package test3-package upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) DEBUG:root:falling back to adjusting all packages DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-old-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 WARNING:root:package z-package upgradable but fails to be marked for upgrade () . -- Ran 1 test in 0.039s OK [Regression Potential] * When failing to mark a package to upgrade/install from the allowed origin holding the highest version the first fallback resets all already adjusted candidates to the highest available version irrespective to the origin of this version being allowed or not. This itself is not a risky operation and sanity checks later ensure that no package would be installed from not allowed origins but it can trigger code paths in apt that were not tried before and may crash. * In testing apt's resolver failed to find a solution for upgrading packages with the first fallback raising an error, but the second fallback handles the error and tries adjusting _all_ potentially upgradable/installable package at the expense of using much more CPU time. This second fallback is not expected to be reached often (it is not reached in autopkgtests either) and adjusting all of those packages matches an earlier behavior of u-u, thus the slow-down may
[Touch-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
** Changed in: network-manager Status: Unknown => New -- 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/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) Status in gnome-control-center: New Status in NetworkManager: New Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+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 1820114] Re: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem
I get sometimes the memory allocation error and sometimes a "no chain by that name": root@ubu1904:/etc/ctdb# iptables -L iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. root@ubu1904:/etc/ctdb# iptables -L iptables: No chain/target/match by that name. root@ubu1904:/etc/ctdb# iptables -L iptables: No chain/target/match by that name. root@ubu1904:/etc/ctdb# iptables -L iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. root@ubu1904:/etc/ctdb# iptables -L INPUT iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. root@ubu1904:/etc/ctdb# iptables -L INPUT iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. root@ubu1904:/etc/ctdb# iptables -L INPUT iptables: No chain/target/match by that name. root@ubu1904:/etc/ctdb# iptables -L INPUT iptables: No chain/target/match by that name. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1820114 Title: iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Status in iptables package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Bug description: I hit this error on disco: ``` $ free -h totalusedfree shared buff/cache available Mem: 478Mi98Mi 311Mi 0.0Ki68Mi 366Mi Swap:0B 0B 0B $ sudo iptables -S iptables v1.6.1: can't initialize iptables table `filter': Memory allocation problem Perhaps iptables or your kernel needs to be upgraded. ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: iptables 1.6.1-2ubuntu3 ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 Date: Thu Mar 14 19:16:15 2019 SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 DistroRelease: Ubuntu 19.04 Package: linux PackageArchitecture: amd64 ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0 Tags: disco uec-images Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1820114/+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 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1795696 Title: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended- upgrade@1991:main:do_auto_remove Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: New Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Released Bug description: [Impact] * Unattended-upgrades crashes while auto-removing kernel packages. [Test Case] 1. Install kernel packages to be automatically removed: # eatmydata apt install linux-image-4.18.0-13-generic linux-image-4.18.0-14-generic linux-image-4.18.0-15-generic # apt-mark auto linux-image-4.18.0-13-generic linux-image-4.18.0-14-generic linux-image-4.18.0-15-generic # /etc/kernel/postinst.d/apt-auto-removal 2. Set up u-u to perform action in non-minimal steps: # grep Minimal /etc/apt/apt.conf.d/50unattended-upgrades Unattended-Upgrade::MinimalSteps "false"; 3. Run u-u in dry-run mode. Observe it failing with not fixed versions: # unattended-upgrade --dry-run Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1798, in main options.verbose or options.debug, options.dry_run) File "/usr/bin/unattended-upgrade", line 1495, in do_auto_remove if res: UnboundLocalError: local variable 'res' referenced before assignment Observe the fixed version running properly: # ./unattended-upgrade --dry-run # [Regression Potential] * The fix is very small and isolated, but a programming error could cause the misreporting of the success of auto-removals. Considering the size and simplicity of the change, regressions here seem unlikely. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1795696/+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 1772512] Re: Unable to install i386 and amd64 arch at the same time
Hi. It's probably me, but I can't find this proposed package. apt list --upgradeable lists only libxkbcommon0/bionic-proposed, but I can't install even that with apt install libxkbcommon0/bionic-proposed. It says the release 'bionic-proposed' doesn't exist for this package. The package libxkbcommon-dev is not visible at all. Anyway, the problem isn't as severe for me now as it seems libgl1-mesa- dev no longer depends on libxkbcommon-dev (in 18.04 at least) which was what I really wanted to get installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1772512 Title: Unable to install i386 and amd64 arch at the same time Status in libxkbcommon package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Committed Bug description: [Impact] libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the package isn't properly multi-archified in bionic [Test case] apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64 should succeed [Regression potential] not really -- Not sure if this is intended, but it's not possible to install two architectures of the libxkbcommon-dev at the same time. On Ubuntu 16.04 and 18.04 apt-get says that they are in conflict. The package is a dependency for libegl1-mesa-dev, which I need to have installed in 64 and 32-bit variants. Please see the example output below: $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic $ sudo apt-get install libxkbcommon-dev:* Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be installed libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/+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 1820888] Re: unattended-upgrades may hold back upgrades due to comparing package versions by their string representation
Hello Balint, or anyone else affected, Accepted unattended-upgrades into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.5ubuntu3.18.10.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: unattended-upgrades (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1820888 Title: unattended-upgrades may hold back upgrades due to comparing package versions by their string representation Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the fix u-u could not upgrade particular packages from -security. It could be observed in Cosmic with systemd security updates failing to install partly due to 239-7ubuntu10.10 being smaller than 239-7ubuntu10.8 when comparing them as strings: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: ... Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 ... With the unfixed version the test case fails here because u-u tries to upgrade test-package to version 12.0 because it does not find version 2.0 smaller. [Regression Potential] * The change is very small and isolated, but fixing it revealed the issue fixed in LP: #1821101. Since the found issue's fix introduces fallbacks when apt's resolver can't find a the solution it is unlikely that other failures are triggered by the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1820888/+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 1821101] Please test proposed package
Hello Balint, or anyone else affected, Accepted unattended-upgrades into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821101 Title: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the introduced fallbacks u-u could not upgrade particular package sets from -security. It could be observed in Cosmic with systemd security updates failing to install in: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to marking test2-package, then adjusting changes DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:falling back to marking test3-package, then adjusting changes WARNING:root:package test3-package upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) DEBUG:root:falling back to adjusting all packages DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-old-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 WARNING:root:package z-package upgradable but fails to be marked for upgrade () . -- Ran 1 test in 0.039s OK [Regression Potential] * When failing to mark a package to upgrade/install from the allowed origin holding the highest version the first fallback resets all already adjusted candidates to the highest available version irrespective to the origin of this version being allowed or not. This itself is not a risky operation and sanity checks later ensure that no package would be installed from not allowed origins but it can trigger code paths in apt that were not tried before and may crash. * In testing apt's resolver failed to find a solution for upgrading packages with the first fallback raising an error, but the second fallback handles the error and tries adjusting _all_ potentially upgradable/installable package at the expense of using much more CPU time. This second fallback is not expected to be reached often (it is not reached in autopkgtests either) and adjusting all of those packages matches an earlier behavior of u-u, thus the slow-down may not be considered a regression. [Other Info] * If the second fallback is found to be reached often a different fallback can be introduced before the first one, to adjust all packages from the same source package then try again: See: https://github.com/mvo5/unattended-upgrades/pull/175#discussion_r268226796
[Touch-packages] [Bug 1821101] Please test proposed package
Hello Balint, or anyone else affected, Accepted unattended-upgrades into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.5ubuntu3.18.10.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821101 Title: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the introduced fallbacks u-u could not upgrade particular package sets from -security. It could be observed in Cosmic with systemd security updates failing to install in: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to marking test2-package, then adjusting changes DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:falling back to marking test3-package, then adjusting changes WARNING:root:package test3-package upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) DEBUG:root:falling back to adjusting all packages DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-old-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 WARNING:root:package z-package upgradable but fails to be marked for upgrade () . -- Ran 1 test in 0.039s OK [Regression Potential] * When failing to mark a package to upgrade/install from the allowed origin holding the highest version the first fallback resets all already adjusted candidates to the highest available version irrespective to the origin of this version being allowed or not. This itself is not a risky operation and sanity checks later ensure that no package would be installed from not allowed origins but it can trigger code paths in apt that were not tried before and may crash. * In testing apt's resolver failed to find a solution for upgrading packages with the first fallback raising an error, but the second fallback handles the error and tries adjusting _all_ potentially upgradable/installable package at the expense of using much more CPU time. This second fallback is not expected to be reached often (it is not reached in autopkgtests either) and adjusting all of those packages matches an earlier behavior of u-u, thus the slow-down may not be considered a regression. [Other Info] * If the second fallback is found to be reached often a different fallback can be introduced before the first one, to adjust all packages
[Touch-packages] [Bug 1820888] Please test proposed package
Hello Balint, or anyone else affected, Accepted unattended-upgrades into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1820888 Title: unattended-upgrades may hold back upgrades due to comparing package versions by their string representation Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the fix u-u could not upgrade particular packages from -security. It could be observed in Cosmic with systemd security updates failing to install partly due to 239-7ubuntu10.10 being smaller than 239-7ubuntu10.8 when comparing them as strings: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: ... Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 ... With the unfixed version the test case fails here because u-u tries to upgrade test-package to version 12.0 because it does not find version 2.0 smaller. [Regression Potential] * The change is very small and isolated, but fixing it revealed the issue fixed in LP: #1821101. Since the found issue's fix introduces fallbacks when apt's resolver can't find a the solution it is unlikely that other failures are triggered by the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1820888/+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 1821101] Re: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade
Regarding "This second fallback is not expected to be reached often" - is there any logging of this fallback being reached done? It'd probably be useful to log that it is happening so we either end up getting the information in crash and bug reports. This isn't necessary for the SRU but is something to consider for the development release. ** Changed in: unattended-upgrades (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1821101 Title: unattended-upgrades: Fall back to adjusting more packages' candidates when a package from an allowed origin can't be marked to install/upgrade Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Without the introduced fallbacks u-u could not upgrade particular package sets from -security. It could be observed in Cosmic with systemd security updates failing to install in: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/u/unattended-upgrades/20190318_182031_fe4fe@/log.gz [Test Case] * The fix includes the extension of the build-time test cases to cover package sets with which u-u fails with without the fallback: Running ./test_rewind.py with python3 DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to marking test2-package, then adjusting changes DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:falling back to marking test3-package, then adjusting changes WARNING:root:package test3-package upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) DEBUG:root:falling back to adjusting all packages DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:adjusting candidate version: test2-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-old-package-dependency=2.0 DEBUG:root:adjusting candidate version: test3-package=2.0 WARNING:root:package z-package upgradable but fails to be marked for upgrade () . -- Ran 1 test in 0.039s OK [Regression Potential] * When failing to mark a package to upgrade/install from the allowed origin holding the highest version the first fallback resets all already adjusted candidates to the highest available version irrespective to the origin of this version being allowed or not. This itself is not a risky operation and sanity checks later ensure that no package would be installed from not allowed origins but it can trigger code paths in apt that were not tried before and may crash. * In testing apt's resolver failed to find a solution for upgrading packages with the first fallback raising an error, but the second fallback handles the error and tries adjusting _all_ potentially upgradable/installable package at the expense of using much more CPU time. This second fallback is not expected to be reached often (it is not reached in autopkgtests either) and adjusting all of those packages matches an earlier behavior of u-u, thus the slow-down may not be considered a regression. [Other Info] * If the second fallback is found to be reached often a different fallback can be introduced before the first one, to adjust all packages from the same source package then try again: See: https://github.com/mvo5/unattended-upgrades/pull/175#discussion_r268226796 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821101/+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 1821768] [NEW] Java-gtk3 theming has many artefacts after updating to openjdk-11 in bionic-proposed
Public bug reported: Openjdk-11 is now in bionic-proposed, and apparently it has switched to gtk3. The gtk3-java theming in Ambiance theme is very incomplete in Bionic. I can see a lot of theming artefacts in scilab (default look) and jabref (after switching to gtk look) from bionic-proposed. Steps to compare between java-gtk2 and java-gtk3 theming in Ambiance on Bionic: A. For java-gtk2: 1. Don't update to openjdk-11 in bionic-proposed 2. Install jabref 3.8.2+ds-3 3. Change the look in Preferences to Gtk 4. Notice that the app is properly themed B. For java-gtk3: 5. Install jabref 3.8.2+ds-12~18.04 from bionic-proposed 6. Change the look in Preferences to Gtk 5. Notice that the theming has many artefacts compared to the previous version The same steps can be followed to compare scilab before and after. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20181005-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 16:17:52 2019 InstallationDate: Installed on 2018-11-29 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1821768 Title: Java-gtk3 theming has many artefacts after updating to openjdk-11 in bionic-proposed Status in ubuntu-themes package in Ubuntu: New Bug description: Openjdk-11 is now in bionic-proposed, and apparently it has switched to gtk3. The gtk3-java theming in Ambiance theme is very incomplete in Bionic. I can see a lot of theming artefacts in scilab (default look) and jabref (after switching to gtk look) from bionic-proposed. Steps to compare between java-gtk2 and java-gtk3 theming in Ambiance on Bionic: A. For java-gtk2: 1. Don't update to openjdk-11 in bionic-proposed 2. Install jabref 3.8.2+ds-3 3. Change the look in Preferences to Gtk 4. Notice that the app is properly themed B. For java-gtk3: 5. Install jabref 3.8.2+ds-12~18.04 from bionic-proposed 6. Change the look in Preferences to Gtk 5. Notice that the theming has many artefacts compared to the previous version The same steps can be followed to compare scilab before and after. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20181005-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 16:17:52 2019 InstallationDate: Installed on 2018-11-29 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1821768/+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 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Description changed: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432 - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 (moved of freedesktop to GNOME) + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 ** Also affects: network-manager via https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 Importance: Unknown Status: Unknown -- 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/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) Status in gnome-control-center: New Status in NetworkManager: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1821763] [NEW] Xorg freeze
Public bug reported: System froze completely, no mouse and keyboard, caps and num lock keys didn't even light up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 12:20:53 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39c5] InstallationDate: Installed on 2019-03-06 (19 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5a02 IMC Networks Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 413c:8505 Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80YH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=e7f345fa-d4fb-4bf9-a5bc-6788d80fdfba ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN41WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN41WW:bd07/23/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80YH dmi.product.sku: LENOVO_MT_80YH_BU_idea_FM_ideapad 320-15IKB dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu wayland-session -- 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/1821763 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: System froze completely, no mouse and keyboard, caps and num lock keys didn't even light up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 12:20:53 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39c5] InstallationDate: Installed on 2019-03-06 (19 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5a02 IMC Networks Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 413c:8505 Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80YH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=e7f345fa-d4fb-4bf9-a5bc-6788d80fdfba ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN41WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO
[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
The solution by @robertjjoynt did *not* work for me. Also, is there a way to revert changes produced by @robertjjoynt? Not that it's any different now, but don't want to mess around with settings if it doesn't fix the issue. OS: Ubuntu 18.04 System: HP Elitebook 830 G5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1803441] Re: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch)
Is this about https://lists.gnu.org/archive/html/bug- bash/2017-03/msg00077.html ? Or about https://lists.gnu.org/archive/html /bug-bash/2017-12/msg00065.html ? Apparently, both are very old flaws. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1803441 Title: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch) Status in bash package in Ubuntu: New Bug description: In 14.04 LTS, the BASH_CMDS variable is writable in rbash. This allows a trivial escape from rbash to run arbitrary shell commands. This issue is fixed upstream: http://git.savannah.gnu.org/cgit/bash.git/tree/CHANGES?h=bash-4.4-testing#n65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1803441/+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 1821752] Re: libc6 version 2.19 breaks NSS loading for static binaries
** Changed in: eglibc (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1821752 Title: libc6 version 2.19 breaks NSS loading for static binaries Status in eglibc: Fix Released Status in eglibc package in Ubuntu: New Status in eglibc package in Debian: Fix Released Bug description: Rebuilding busybox on trusty breaks wget name resolution. Introduced by: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0d23a5c1b1908700d25b7e3c6cece148e19dded4 fixed by: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=93bad7c97c7047ecaf7664859e2b49c0fe995443 To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1821752/+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 1821653] Re: Gtk-WARNING **: 19:38:32.437: Theme parsing error:
*** This bug is a duplicate of bug 1805653 *** https://bugs.launchpad.net/bugs/1805653 ** This bug has been marked a duplicate of bug 1805653 launching firefox from terminal reveals Gtk-WARNING -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1821653 Title: Gtk-WARNING **: 19:38:32.437: Theme parsing error: Status in apport package in Ubuntu: New Bug description: When I report a bug in Ubuntu I get the following errors. (apport-gtk:16883): Gtk-WARNING **: 18:54:44.036: Theme parsing error: gtk-widgets.css:3135:13: 'max-width' is not a valid property name (apport-gtk:16883): Gtk-WARNING **: 18:54:44.037: Theme parsing error: gtk-widgets.css:3136:14: 'max-height' is not a valid property name I saw a response that said to examine the style sheets and remove the 'max-width' and 'max-height' properties. But I check with the CSS3 web-site and they are both valid property names. See https://www.w3schools.com/cssref/pr_dim_max-height.asp and https://www.w3schools.com/cssref/pr_dim_max-width.asp. Should the warning ge Gtk-WARNING **: Gtk does not yet support the 'max-width' and 'max-height' properties? I do know that many of the CSS3 properties (like the 'rotation' property) are not yet supported. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport-gtk 2.20.10-0ubuntu13.2 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: MATE Date: Mon Mar 25 19:38:32 2019 InstallationDate: Installed on 2018-12-16 (99 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1821653/+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 1733870] Re: [Ubuntu 19.10] Add GDB support to access/display POWER8 registers
Based comments #6, #7 and #8, closing this bug out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1733870 Title: [Ubuntu 19.10] Add GDB support to access/display POWER8 registers Status in The Ubuntu-power-systems project: Fix Released Status in gdb package in Ubuntu: Fix Released Bug description: This feature request is for GDB support for access to Power registers that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM registers. The feature is currently being worked on, so no upstream code is available yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733870/+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 1733870] Re: [Ubuntu 19.10] Add GDB support to access/display POWER8 registers
** Changed in: gdb (Ubuntu) Status: Incomplete => Fix Released ** Changed in: ubuntu-power-systems Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1733870 Title: [Ubuntu 19.10] Add GDB support to access/display POWER8 registers Status in The Ubuntu-power-systems project: Fix Released Status in gdb package in Ubuntu: Fix Released Bug description: This feature request is for GDB support for access to Power registers that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM registers. The feature is currently being worked on, so no upstream code is available yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733870/+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 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest
IBM, please can you provide us with a list of patches (probably from the delta between 2.27 and 2.31) that needs to be applied on top of 2.27 to get the situation solved? (For already released Ubuntu versions we cannot simply bump the version to 2.31 - the patches need to be cherry-picked ...) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1764628 Title: incorrect hypervisor and virtualization type reported in compat mode guest Status in The Ubuntu-power-systems project: Triaged Status in util-linux package in Ubuntu: New Bug description: ---uname output--- Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC: root@guest:/tmp# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Model: 2.2 (pvr 004e 1202) Model name:POWER8 (architected), altivec supported >> Hypervisor vendor: horizontal >> Virtualization type: full L1d cache: 32K L1i cache: 32K NUMA node0 CPU(s): 0,1 Stack trace output: no Oops output: no We test what is coming along with distro. If you are not able to see issue with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+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 1821415] Re: pkexec fails in a non-graphical environment
Marking as notfixing for release. This doesn't mean that it won't get worked on, and Andrea might have an idea what's going on here, but we won't block release on this bug. ** Tags removed: rls-dd-incoming ** Tags added: rls-dd-notfixing ** Tags added: desktop-trello-import -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in policykit-1 package in Ubuntu: New Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1821415] Automatically added comment
Added to Trello: https://trello.com/c/sTIx3fol/288-bug1821415-pkexec- fails-in-a-non-graphical-environment ** Tags removed: desktop-trello-import -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in policykit-1 package in Ubuntu: New Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1811129] Re: update ufw to 0.36
** Description changed: [Impact] This bug is the master bug for a one time SRU of ufw to the new 0.36 release. Typically patches would be individually backported like normal, but the new 'prepend' command feature is the impetus for this SRU and it - contains most of the code changes. Other bugs fixes in the upstream + contains most of the code changes. Other bugs fixed in the upstream release are either already included in the Ubuntu/Debian packaging or small enough to not pose a significant regression risk. 0.36 had various pyflakes/pep8/pylint cleanups over 0.35 so upgrading 18.04 to 0.36 will make maintaining ufw a bit easier for the duration of this LTS. [Test Case] In addition to the in-build tests, there is an extensive testsuite for running under root on the live system. The QRT tests for ufw (scripts /test-ufw.py) run these tests (and more). [Regression Potential] In terms of code changes, I've attached code-changes-bionic-to- disco.diff which is a diff of the source code in bionic's 0.35-5 with patches applied and disco's 0.36-1 with its patches applied. This shows that: * only comment changes to conf/sysctl.conf * only comment changes to conf/ufw.defaults * doc/systemd.example is updated (but unused in our packaging) * various man page updates * ufw.pot is refreshed * various Makefile updates related to snap packaging and coverage (the debian packaging only uses the 'clean' target) * src/applications.py has only whitespace and comment changes The remaining code changes in src/ are quite small and address the SRU bugs and the regression potential for these changes will be discussed in those bugs. In addition to the SRU bugs listed in the changelog, 0.36 also fixes the following upstream bugs not already in 0.35-5: * bug 1782384 - ufw-framework document error * bug 1695718 - UFW rule for Transmission only allows 51413/tcp while 51413/udp is used for DHT * bug 1377600 - ufw errors after ctr+c interupt * bug 1586258 - Rule insertion fails if ruleset is empty * bug 1558068 - remove extraneous source quench rule * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884932 - cannot preseed package configuration in debian-installer (other bugs in the 0.36-1 changelog are dupes of the above) [Other Info] Note that the 0.36 code base has been the basis for the snap for many months with the majority of the non-'prepend' changes in production during this time. 0.36-1 was uploaded to Debian last month (and it migrated automatically to disco shortly after) with no new bug reports in either. The snappy packaging, which is included upstream, underwent a lot of changes, but should not be considered as part of this SRU since it doesn't affect the deb builds. ** Description changed: [Impact] This bug is the master bug for a one time SRU of ufw to the new 0.36 release. Typically patches would be individually backported like normal, but the new 'prepend' command feature is the impetus for this SRU and it contains most of the code changes. Other bugs fixed in the upstream release are either already included in the Ubuntu/Debian packaging or small enough to not pose a significant regression risk. 0.36 had various pyflakes/pep8/pylint cleanups over 0.35 so upgrading 18.04 to 0.36 will make maintaining ufw a bit easier for the duration of this LTS. [Test Case] In addition to the in-build tests, there is an extensive testsuite for running under root on the live system. The QRT tests for ufw (scripts /test-ufw.py) run these tests (and more). [Regression Potential] In terms of code changes, I've attached code-changes-bionic-to- disco.diff which is a diff of the source code in bionic's 0.35-5 with patches applied and disco's 0.36-1 with its patches applied. This shows that: * only comment changes to conf/sysctl.conf * only comment changes to conf/ufw.defaults * doc/systemd.example is updated (but unused in our packaging) * various man page updates * ufw.pot is refreshed * various Makefile updates related to snap packaging and coverage (the debian packaging only uses the 'clean' target) * src/applications.py has only whitespace and comment changes The remaining code changes in src/ are quite small and address the SRU bugs and the regression potential for these changes will be discussed in those bugs. In addition to the SRU bugs listed in the changelog, 0.36 also fixes the following upstream bugs not already in 0.35-5: * bug 1782384 - ufw-framework document error * bug 1695718 - UFW rule for Transmission only allows 51413/tcp while 51413/udp is used for DHT * bug 1377600 - ufw errors after ctr+c interupt * bug 1586258 - Rule insertion fails if ruleset is empty * bug 1558068 - remove extraneous source quench rule * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884932 - cannot
[Touch-packages] [Bug 1821752] Re: libc6 version 2.19 breaks NSS loading for static binaries
Launchpad has imported 9 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=17250.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2014-08-10T12:35:26+00:00 Mike Frysinger wrote:
it looks like the change landed for bug 16046 broke static dlopening of
nss modules. if you try to use getaddrinfo/getpwnam/etc..., they just
return errors immediately.
example tests:
$ cat test.c
#include
#include
#include
int main() {
void *p = getpwnam("root");
printf("%p\n", p);
return p == NULL ? 1 : 0;
}
$ gcc test.c && ./a.out
0x7f6aec59a0e0
$ gcc -static test.c && ./a.out
(nil)
$ cat test.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
const char *host = argv[1];
int rc;
struct addrinfo *result = NULL;
struct addrinfo hint;
memset(, 0 , sizeof(hint));
hint.ai_family = AF_INET;
hint.ai_socktype = SOCK_STREAM;
hint.ai_flags = AF_UNSPEC;
rc = getaddrinfo(host, NULL, , );
if (rc || !result) {
printf("bad address '%s'\n", host);
return 1;
} else
return 0;
}
$ gcc test.c && ./a.out localhost
$ gcc -static test.c && ./a.out localhost
bad address 'localhost'
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1821752/comments/0
On 2014-08-10T13:13:55+00:00 Mike Frysinger wrote:
bisecting more, it looks like it's specifically the change to elf/dl-
iteratephdr.c that breaks things (where it changes from a custom
dl_iterate_phdr to a weak alias of __dl_iterate_phdr). if i revert that
change alone, the tests start working again.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1821752/comments/1
On 2014-10-21T08:50:31+00:00 Aurelien Jarno wrote:
I confirm that the breakage has been introduced by the following commit:
commit 0d23a5c1b1908700d25b7e3c6cece148e19dded4
Author: Maciej W. Rozycki
Date: Fri Jan 31 17:51:31 2014 +
[BZ #16046] Static dlopen correction fallout fixes.
Fixes to address issues from BZ #15022 resolution, as follows:
* TLS updates to csu/libc-tls.c -- we now have a proper main map, so
there's no longer a need to create a separate fake one to keep TLS
structures,
* random updates to elf/dl-close.c -- LM_ID_BASE is now a valid name
space ID for static executables as well, so assert that we don't
unload the main map. Similarly dl_nns isn't supposed to be 0 for
static executables anymore,
* actual BZ #16046 fix to elf/dl-iteratephdr.c -- the dl_iterate_phdr
special function for static executables isn't needed anymore, provided
that l_phdr and l_phnum members of the main map have been properly
initialized (done in _dl_non_dynamic_init in elf/dl-support.c now),
* ld.so.cache loader update to elf/dl-load.c --
GL(dl_ns)[LM_ID_BASE]._ns_loaded is now always initialized in static
executables so can become the fallback loader map to check for
DF_1_NODEFLIB, provided that the l_flags_1 member of the main map has
been properly initialized (done in elf/dl-support.c now); this also
ensures previous semantics elsewhere in elf/dl-load.c,
* matching updates to elf/dl-support.c -- to complement the two fixes
above.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1821752/comments/2
On 2014-10-21T08:57:23+00:00 Aurelien Jarno wrote:
The problem seems to be related to the trusted directories. As long as
the generated file elf/trusted-dirs.h contains a path matching the NSS
modules location, they are not even load. Changing these paths to not
match the NSS modules location make the NSS modules to work again.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1821752/comments/3
On 2014-10-22T10:58:54+00:00 Aurelien Jarno wrote:
Looking more at the code the new behaviour is actually wanted.
Statically linked binaries do not lookup in the default lib search patch
by default (DF_1_NODEFLIB is defined as "Ignore default lib search
path."):
--- a/elf/dl-support.c
+++ b/elf/dl-support.c
@@ -91,6 +91,7 @@ static struct link_map _dl_main_map =
.l_scope = _dl_main_map.l_scope_mem,
.l_local_scope = { &_dl_main_map.l_searchlist },
.l_used = 1,
+.l_flags_1 = DF_1_NODEFLIB,
.l_tls_offset = NO_TLS_OFFSET,
Re: [Touch-packages] [Bug 1821022] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
Should I try out One by One all these https://www.kernel.org/doc/html/v4.15/sound/hd-audio/models.html#alc66x-67x-892 options?Or wait for some fix? Il lunedì 25 marzo 2019, 02:40:52 CET, Daniel van Vugt ha scritto: Can you please run: dpkg -l > allpackages.txt and then attach 'allpackages.txt'? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1821022 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: he problem occurs even on live xubuntu 18.04 17.10 16.04 even modifying alsa-base in options snd-hda-intel model=auto or options snd-hda-intel model=asrock-mobo or options snd-hda-intel model=generic.; all on board audio port are shown as unplugged. Thus HDMI of the Nvidia GTX 1050ti seems to work perfectly when I connected to TV HDMI input (but could not steal TV 4 ever) https://forum.ubuntuusers.de/topic/alc662-kein-ton-von-asrock-fm2a75m-dgs/2/#post-9058858 https://streamable.com/5j96k BIOS setting in the video above ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: hp 1577 F pulseaudio /dev/snd/controlC0: hp 1577 F pulseaudio CurrentDesktop: XFCE Date: Wed Mar 20 15:42:37 2019 InstallationDate: Installed on 2016-09-07 (923 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_DevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: hp 1577 F pulseaudio /dev/snd/controlC0: hp 1577 F pulseaudio /dev/snd/seq: timidity 1083 F timidity Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.modprobe.d.alsa-base.conf: #options snd-hda-intel model=3stack-6ch mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-19T20:25:47.409210 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821022/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821022 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: he problem occurs even on live xubuntu 18.04 17.10 16.04 even modifying alsa-base in options snd-hda-intel model=auto or options snd-hda-intel model=asrock-mobo or options snd-hda-intel model=generic.; all on board audio port are shown as unplugged. Thus HDMI of the Nvidia GTX 1050ti seems to work perfectly when I connected to TV HDMI input (but could not steal TV 4 ever) https://forum.ubuntuusers.de/topic/alc662-kein-ton-von-asrock-fm2a75m-dgs/2/#post-9058858 https://streamable.com/5j96k BIOS setting in the video above ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1577 F pulseaudio /dev/snd/controlC0: hp 1577 F pulseaudio CurrentDesktop: XFCE Date: Wed Mar 20 15:42:37 2019
[Touch-packages] [Bug 1821641] Re: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily
** Tags added: disco iso-testing ** Package changed: ubuntu => xorg (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/1821641 Title: [HP Elitebook 840 G1] Screen is upside down on 19.04 daily Status in xorg package in Ubuntu: New Bug description: On the 19.04 daily image (2019-03-24), the screen on my laptop is completely upside down, from the moment the GUI loads. This does not happen on 18.04 and 18.10. It appears to be an accelerometer issue since holding the laptop upside down flips the image to its correct orientation - basically the functionality of the accelerometer is suddenly inverted. Please contact me if you want me to help testing the issue on my hardware. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821641/+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 1821752] [NEW] libc6 version 2.19 breaks NSS loading for static binaries
Public bug reported: Rebuilding busybox on trusty breaks wget name resolution. Introduced by: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0d23a5c1b1908700d25b7e3c6cece148e19dded4 fixed by: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=93bad7c97c7047ecaf7664859e2b49c0fe995443 ** Affects: eglibc Importance: Unknown Status: Unknown ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Affects: eglibc (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #754813 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754813 ** Also affects: eglibc (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754813 Importance: Unknown Status: Unknown ** Bug watch added: Sourceware.org Bugzilla #17250 https://sourceware.org/bugzilla/show_bug.cgi?id=17250 ** Also affects: eglibc via https://sourceware.org/bugzilla/show_bug.cgi?id=17250 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1821752 Title: libc6 version 2.19 breaks NSS loading for static binaries Status in eglibc: Unknown Status in eglibc package in Ubuntu: New Status in eglibc package in Debian: Unknown Bug description: Rebuilding busybox on trusty breaks wget name resolution. Introduced by: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0d23a5c1b1908700d25b7e3c6cece148e19dded4 fixed by: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=93bad7c97c7047ecaf7664859e2b49c0fe995443 To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1821752/+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 1821641] [NEW] [HP Elitebook 840 G1] Screen is upside down on 19.04 daily
You have been subscribed to a public bug: On the 19.04 daily image (2019-03-24), the screen on my laptop is completely upside down, from the moment the GUI loads. This does not happen on 18.04 and 18.10. It appears to be an accelerometer issue since holding the laptop upside down flips the image to its correct orientation - basically the functionality of the accelerometer is suddenly inverted. Please contact me if you want me to help testing the issue on my hardware. Thanks! ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment disco iso-testing -- [HP Elitebook 840 G1] Screen is upside down on 19.04 daily https://bugs.launchpad.net/bugs/1821641 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system
IMO adding two patterns than keeping the rule of not adding patterns that would only cover versioned kernel packages that could not be installed by installing meta packages from the archive is worth it due to the reduced complexity. Alternatively I can add exceptions for those patterns in the autopackagetest to ignore the covered packages. -- 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/1821640 Title: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system Status in apt package in Ubuntu: Triaged Bug description: Unattended-upgrades keeps versioned kernel packages because they don't match known kernel package patterns: ... Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it would also remove the following packages which should be kept in this step: linux-image-unsigned-4.18.0-14-generic ... For reproduction see LP: #1795696, but running u-u with --verbose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system
I agree that -unsigned- kernel packages are unlikely to pile up in /boot, but they are still versioned kernel packages and handling those uniformly helps in maintainence. I also added linux-buildinfo to the patterns and an autopkgtest to detect new kernel packages not covered by patterns, thus we can catch the next variant of LP: #1698159 earlier. -- 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/1821640 Title: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system Status in apt package in Ubuntu: Triaged Bug description: Unattended-upgrades keeps versioned kernel packages because they don't match known kernel package patterns: ... Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it would also remove the following packages which should be kept in this step: linux-image-unsigned-4.18.0-14-generic ... For reproduction see LP: #1795696, but running u-u with --verbose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove
** Description changed: [Impact] - * Unattended-upgrades crashes while auto-removing kernel packages. + * Unattended-upgrades crashes while auto-removing kernel packages. [Test Case] 1. Install kernel packages to be automatically removed: - # eatmydata apt install linux-image-unsigned-4.18.0-13-generic linux-image-unsigned-4.18.0-14-generic linux-image-unsigned-4.18.0-15-generic - # apt-mark auto linux-image-unsigned-4.18.0-13-generic linux-image-unsigned-4.18.0-14-generic linux-image-unsigned-4.18.0-15-generic - # /etc/kernel/postinst.d/apt-auto-removal + # eatmydata apt install linux-image-4.18.0-13-generic linux-image-4.18.0-14-generic linux-image-4.18.0-15-generic + # apt-mark auto linux-image-4.18.0-13-generic linux-image-4.18.0-14-generic linux-image-4.18.0-15-generic + # /etc/kernel/postinst.d/apt-auto-removal 2. Set up u-u to perform action in non-minimal steps: - # grep Minimal /etc/apt/apt.conf.d/50unattended-upgrades + # grep Minimal /etc/apt/apt.conf.d/50unattended-upgrades Unattended-Upgrade::MinimalSteps "false"; 3. Run u-u in dry-run mode. -Observe it failing with not fixed versions: - # unattended-upgrade --dry-run + Observe it failing with not fixed versions: + # unattended-upgrade --dry-run Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 1998, in - sys.exit(main(options)) - File "/usr/bin/unattended-upgrade", line 1798, in main - options.verbose or options.debug, options.dry_run) - File "/usr/bin/unattended-upgrade", line 1495, in do_auto_remove - if res: + File "/usr/bin/unattended-upgrade", line 1998, in + sys.exit(main(options)) + File "/usr/bin/unattended-upgrade", line 1798, in main + options.verbose or options.debug, options.dry_run) + File "/usr/bin/unattended-upgrade", line 1495, in do_auto_remove + if res: UnboundLocalError: local variable 'res' referenced before assignment - Observe the fixed version running properly: - # ./unattended-upgrade --dry-run - # + Observe the fixed version running properly: + # ./unattended-upgrade --dry-run + # + [Regression Potential] - [Regression Potential] - - * The fix is very small and isolated, but a programming error could + * The fix is very small and isolated, but a programming error could cause the misreporting of the success of auto-removals. Considering the size and simplicity of the change, regressions here seem unlikely. - [Original Bug Text] - The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1795696 Title: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended- upgrade@1991:main:do_auto_remove Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: New Status in unattended-upgrades source package in Bionic: Confirmed Status in unattended-upgrades source package in Cosmic: Fix Released Bug description: [Impact] * Unattended-upgrades crashes while auto-removing kernel packages. [Test Case] 1. Install kernel packages to be automatically removed: # eatmydata apt install linux-image-4.18.0-13-generic linux-image-4.18.0-14-generic linux-image-4.18.0-15-generic # apt-mark auto linux-image-4.18.0-13-generic linux-image-4.18.0-14-generic linux-image-4.18.0-15-generic # /etc/kernel/postinst.d/apt-auto-removal 2. Set up u-u to perform action in non-minimal steps: # grep Minimal /etc/apt/apt.conf.d/50unattended-upgrades Unattended-Upgrade::MinimalSteps "false"; 3. Run u-u in dry-run mode. Observe it failing with not fixed versions: # unattended-upgrade --dry-run Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1798, in main options.verbose or options.debug, options.dry_run) File "/usr/bin/unattended-upgrade", line 1495, in do_auto_remove if res: UnboundLocalError: local variable 'res' referenced before assignment Observe the fixed version running properly: # ./unattended-upgrade --dry-run # [Regression Potential] * The fix is very small and isolated, but a programming error could cause the misreporting of the success of auto-removals.
[Touch-packages] [Bug 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system
I mean, usually people should have linux-image- installed, not linux-image-unsigned - they are basically only artifacts used for building the signed kernel images that are installed by the metapackages. Since there is no metapackage that pulls in unsigned kernels, there is no reason to add unsigned kernels to that list, as they'll be manually installed anyway. -- 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/1821640 Title: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system Status in apt package in Ubuntu: Triaged Bug description: Unattended-upgrades keeps versioned kernel packages because they don't match known kernel package patterns: ... Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it would also remove the following packages which should be kept in this step: linux-image-unsigned-4.18.0-14-generic ... For reproduction see LP: #1795696, but running u-u with --verbose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system
Proposed fix on Salsa: https://salsa.debian.org/apt- team/apt/merge_requests/57 -- 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/1821640 Title: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system Status in apt package in Ubuntu: Triaged Bug description: Unattended-upgrades keeps versioned kernel packages because they don't match known kernel package patterns: ... Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it would also remove the following packages which should be kept in this step: linux-image-unsigned-4.18.0-14-generic ... For reproduction see LP: #1795696, but running u-u with --verbose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system
Why should not it be installed? -- 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/1821640 Title: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system Status in apt package in Ubuntu: Triaged Bug description: Unattended-upgrades keeps versioned kernel packages because they don't match known kernel package patterns: ... Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it would also remove the following packages which should be kept in this step: linux-image-unsigned-4.18.0-14-generic ... For reproduction see LP: #1795696, but running u-u with --verbose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1821091] Re: [FFe] Qt 5.12.2 update
> The most ironic part is that you can not update it independently without having Qt 5.12. In fact you can, at least that was the case with previous Qt WebEngine versions: https://doc.qt.io/qt-5/qtwebengine-platform-notes.html#using-earlier-qt- versions-to-build-qt-webengine But anyway, any version will be insecure at some point of time. I personally do not have time to backport security fixes to stable releases, and we have no other volunteers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1821091 Title: [FFe] Qt 5.12.2 update Status in qtbase-opensource-src package in Ubuntu: New Bug description: Dear Release Team, I would like to update Qt in disco from 5.11.3 to 5.12.2. The reasons are the following: 1) The 5.11 branch is EOL and no longer receiving any fixes. The 5.12 branch is LTS and will be supported for three years. 2) New versions of Plasma are going to require Qt 5.12, and the Kubuntu team would like to be able to package them in their backports PPA for disco. 3) In Qt 5.12, the memory usage of the QML Engine is reduced by up to 30 %. 4) Finally we will be able to sync all packages from Debian. I have managed to drop the delta in qtbase, qtmultimedia and qtwebkit. Why we haven’t packaged it early: we did not want to package 5.12.1 because it had some known bugs. And 5.12.2 was released upstream later than it was originally planned. Changelog: https://wiki.qt.io/New_Features_in_Qt_5.12 The packages are being prepared in https://launchpad.net/~ci-train- ppa-service/+archive/ubuntu/3680/+packages, but these will be replaced with syncs from Debian when qtbase and qtdeclarative get accepted from Debian’s NEW queue. This transition will require syncs of all Qt packages, and no-change rebuilds of packages that build-depend on qtbase5-private-dev or qtdeclarative5-private-dev. All Qt modules are in universe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1821091/+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 1821091] Re: [FFe] Qt 5.12.2 update
QtWebEngine from 5.11.3 is largely insecure and outdated at this point. Leaving it there is a crime. The most ironic part is that you can not update it independently without having Qt 5.12. So it's a tough situation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1821091 Title: [FFe] Qt 5.12.2 update Status in qtbase-opensource-src package in Ubuntu: New Bug description: Dear Release Team, I would like to update Qt in disco from 5.11.3 to 5.12.2. The reasons are the following: 1) The 5.11 branch is EOL and no longer receiving any fixes. The 5.12 branch is LTS and will be supported for three years. 2) New versions of Plasma are going to require Qt 5.12, and the Kubuntu team would like to be able to package them in their backports PPA for disco. 3) In Qt 5.12, the memory usage of the QML Engine is reduced by up to 30 %. 4) Finally we will be able to sync all packages from Debian. I have managed to drop the delta in qtbase, qtmultimedia and qtwebkit. Why we haven’t packaged it early: we did not want to package 5.12.1 because it had some known bugs. And 5.12.2 was released upstream later than it was originally planned. Changelog: https://wiki.qt.io/New_Features_in_Qt_5.12 The packages are being prepared in https://launchpad.net/~ci-train- ppa-service/+archive/ubuntu/3680/+packages, but these will be replaced with syncs from Debian when qtbase and qtdeclarative get accepted from Debian’s NEW queue. This transition will require syncs of all Qt packages, and no-change rebuilds of packages that build-depend on qtbase5-private-dev or qtdeclarative5-private-dev. All Qt modules are in universe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1821091/+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
