[Touch-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
more or less, though AIUI the xserver changes aren't necessary if the kernel support is there -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
i915 is loaded just fine on your first journal log: Mar 25 23:26:06 zlink2 kernel: [drm] Initialized i915 1.6.0 20181204 for :00:02.0 on minor 0 but it's happening after lightdm is started, so I'd say it's lightdm which is just being too hasty ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- 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 briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid 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/lightdm/+bug/1821609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1297144] Re: [Lenovo ThinkPad X230] Invisible cursor after resume from suspend
*** This bug is a duplicate of bug 1568604 *** https://bugs.launchpad.net/bugs/1568604 ** This bug has been marked a duplicate of bug 1568604 Mouse cursor lost when unlocking with Intel graphics -- 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/1297144 Title: [Lenovo ThinkPad X230] Invisible cursor after resume from suspend Status in xorg package in Ubuntu: Expired Bug description: I am using the daily build of Xubuntu 14.04 x64 on a Lenovo Thinkpad x230. If I wake up the computer after it spending some time in the suspend state, the cursor will be invisible. The courser still works (I can click on stuff and hover the invisible cursor over stuff), but the little arrow is not visible. This bug showed up a few days ago after an update. Putting the computer back in suspend state and immediately waking it back up resolves the issue until the next time the computer is put in suspend state for an extended period of time. It is possible that this bug has something to do with Whisker Menu. Sometimes when the courser is invisible it will still show up over Whisker Menu. Most of the time it is invisible there too. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 xfdesktop version 4.11.4, running on Xfce 4.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1297144/+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 1821491] Re: DNS lookup fails for local hosts
Please show the complete output of systemd-resolve --status on this system. > I would expect that the nameserver set in network-manager would be used If it's not used, that can only be because you have some other nameservers defined that are taking precedence; but we would need to see the complete config to establish this. ** Changed in: resolvconf (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts Status in resolvconf package in Ubuntu: Incomplete Bug description: Mint 19 (Ubuntu Bionic) Laptop so Using NetworkManager, and connecting wirelessly to LAN Upgraded from Mint 18.3 so using resolvconf... Versions: network-manager: 1.10.6-2ubuntu1.1 resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2 systemd: 237-3ubuntu10.15 dns is specified in NetworkMananager as 192.168.2.1 the dns is a router, and has static ips assigned to certain hosts on my lan... $cat resolv.conf nameserver 127.0.0.53 search phs options edns0 $ nslookup phspi05 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find phspi05: SERVFAIL If I explicity specify the dns: $ nslookup phspi05 192.168.2.1 Server: 192.168.2.1 Address: 192.168.2.1#53 Non-authoritative answer: Name: phspi05 Address: 192.168.2.35 I get the correct ip address... Same with dig... I would expect that the nameserver set in network-manager would be used From tail of $ systemd-resolve --status Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.2.1 DNS Domain: phs So the dns address had been picked up from NetworkManager, but apparently is not being used... Thought it might be related to this bug: https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903 So installed the proposed fix, but no change. I also tried removing package resolvconf, again no change... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1821491/+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 briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
a little digging and plymouth is supposed to work with drm modesetting drivers which means i915 has to be loaded for it to work .. so not seeing it means ..some hardware detection has failed .. is that part of plymouth or something else? since it works on the upgraded install on sda1 I suspect a config file change relating to hardware detection and "autoload" by systemd .. i'm not familiar with that magic .. I only know that manual override via /etc/modules etc. is possible.. not required on sda1 I noticed that issues with xorg function started arround march 16, 2019 .. first bug report ..missing xorg-server install .. #1820430 .. march 8, 2019 iso was okay as far as i can remember .. unfortunately .. those dailys are bit vapor so no way to re test .. unless i can re-download .. is there an archive? I haven't looked. -- 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 briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in xorg-server 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
[Touch-packages] [Bug 1450838] Re: lightdm fails to unlock with serial console configured
[Expired for light-locker (Ubuntu) because there has been no activity for 60 days.] ** Changed in: light-locker (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1450838 Title: lightdm fails to unlock with serial console configured Status in light-locker package in Ubuntu: Expired Status in lightdm package in Ubuntu: Expired Bug description: With /etc/default/grub configured for serial console output as follows (seehttps://help.ubuntu.com/community/SerialConsoleHowto): GRUB_DEFAULT=0 GRUB_TIMEOUT=3 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600n8" #GRUB_TERMINAL=console GRUB_TERMINAL="serial console" GRUB_SERIAL_COMMAND="serial --speed=9600 --unit=0 --word=8 --parity=no --stop=1" Lightdm fails to unlock a locked screen. Initial login works fine. But, when the screen locks, the correct password is accepted, but the screen does not unlock. If I disable serial console with the default "GRUB_TERMINAL=console", lightdm screen unlock seems to work fine. I don't know if this is a problem with lightdm or light-locker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1450838/+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 1450838] Re: lightdm fails to unlock with serial console configured
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1450838 Title: lightdm fails to unlock with serial console configured Status in light-locker package in Ubuntu: Expired Status in lightdm package in Ubuntu: Expired Bug description: With /etc/default/grub configured for serial console output as follows (seehttps://help.ubuntu.com/community/SerialConsoleHowto): GRUB_DEFAULT=0 GRUB_TIMEOUT=3 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600n8" #GRUB_TERMINAL=console GRUB_TERMINAL="serial console" GRUB_SERIAL_COMMAND="serial --speed=9600 --unit=0 --word=8 --parity=no --stop=1" Lightdm fails to unlock a locked screen. Initial login works fine. But, when the screen locks, the correct password is accepted, but the screen does not unlock. If I disable serial console with the default "GRUB_TERMINAL=console", lightdm screen unlock seems to work fine. I don't know if this is a problem with lightdm or light-locker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1450838/+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 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
[Expired for wayland (Ubuntu) because there has been no activity for 60 days.] ** Changed in: wayland (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Expired Status in wayland package in Ubuntu: Expired Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+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 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Expired Status in wayland package in Ubuntu: Expired Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
Kernel module will load if added to /etc/ modules .. I have my sda1 partition running kernel 5.0.0-8.9 as are the iso's tested recently .. my sda1 partition loads i915 without using /etc/modules.. I notice that the recent isos do not show Plymouth progress screen at startup..is that relevant? On Wed, Apr 3, 2019, 10:15 PM Daniel van Vugt, < daniel.van.v...@canonical.com> wrote: > If you're sure that's the problem then we would need to figure out which > kernel version it started in. Please try some different kernel versions: > > https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D > > and see if you can find the two closest versions where one doesn't have > the bug and the other does. > > ** Also affects: linux (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: linux (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1821609 > > Title: > lightdm login screen briefly appears and then blanks out on Intel(R) > Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module > > Status in lightdm package in Ubuntu: > New > Status in linux package in Ubuntu: > Incomplete > Status in xorg-server 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:
[Touch-packages] [Bug 1438786] Re: package libc6:amd64 2.19-0ubuntu6.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: eglibc (Ubuntu) Status: New => Confirmed -- 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/1438786 Title: package libc6:amd64 2.19-0ubuntu6.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in eglibc package in Ubuntu: Confirmed Bug description: Just tried to do a routine update, got a fail to install problem ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libc6:amd64 2.19-0ubuntu6.6 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Mar 31 08:37:49 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.4 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-11-08 (142 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: eglibc Title: package libc6:amd64 2.19-0ubuntu6.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1438786/+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 1751963] Re: audio
Please provide more details about what kind of files don't play and in what app(s) you are trying to play them. ** 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/1751963 Title: audio Status in Ubuntu: Incomplete Bug description: some files do not play. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 27 07:53:01 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2017] InstallationDate: Installed on 2018-02-18 (8 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=5d1c7af4-92aa-40c5-9a1a-0d9b3a877e7c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BEH6110H.86A.0016.2011.0118.1128 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61WW dmi.board.vendor: Intel Corporation dmi.board.version: AAG23116-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0016.2011.0118.1128:bd01/18/2011:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-203:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Feb 27 07:51:40 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB OPTICAL MOUSEMOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1751963/+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 1754309] Re: 2 issues
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** 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/1754309 Title: 2 issues Status in Ubuntu: Incomplete Bug description: chack issues ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Mar 8 17:24:03 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:39b5] InstallationDate: Installed on 2018-03-08 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210f Acer, Inc Bus 001 Device 002: ID 0bda:c024 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=3b5ebb05-0cbe-4a1a-b1f1-3e3651a75837 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 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:bvr6JCN21WW:bd12/04/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 81BG dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Mar 8 17:02:43 2018 xserver.configfile: default xserver.devices: inputVideo BusKEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputEasyCamera: EasyCamera KEYBOARD, id 8 inputElan TouchpadTOUCHPAD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1754309/+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 1754628] Re: vaapi not working
** Package changed: xorg (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754628 Title: vaapi not working Status in mesa package in Ubuntu: New Bug description: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)" 04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 470/480/570/580] (Nitro+ Radeon RX 580 4GB) [1da2:e366] The graphics run by the amdgpu (not -pro) and is unable to address va- api acceleration. eric@athena:~$ vainfo libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so libva error: dlopen of /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so failed: /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so: undefined symbol: amdgpu_cs_syncobj_import_sync_file libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit While open GL software like the unigine heaven benchmark runs very well. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,gnomecompat,grid,imgpng,mousepoll,move,place,regex,resize,session,unitymtgrabhandles,wall,wobbly,animation,expo,ezoom,fade,scale,unityshell,workarounds] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 12:16:28 2018 DistUpgraded: 2018-03-09 11:15:52,669 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 17.50-511655, 4.13.0-36-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Ellesmere [Radeon RX 470/480/570/580] (Nitro+ Radeon RX 580 4GB) [1da2:e366] InstallationDate: Installed on 2018-01-04 (63 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=9782f23b-461f-4cf0-b7d4-9b4e2739964c ro iommu=soft quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-03-09 (0 days ago) dmi.bios.date: 10/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2g dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2g:bd10/07/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Jan 11 18:02:23 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1754628/+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 1823076] Re: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled
Also, are you able to change any settings in your BIOS to prevent wakeup from Bluetooth? ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1823076 Title: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Incomplete Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1823076] Re: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled
It sounds like you've found a good workaround but I am curious about the root cause here. It seems the Bluetooth mouse might be emitting events even when you don't touch it..? Are you able to try a different model of Bluetooth mouse? ** Summary changed: - Intel NUC (8I3BEH1) wakes up immediately after suspend after installing BlueZ + Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1823076 Title: Intel NUC (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Incomplete Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection
My Ubuntu 18.04 randomly drops ethernet connection once per hour while in use. Reboot clears this issue. *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 06 serial: 74:d4:35:b1:58:ff size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.045.08-NAPI duplex=full ip=192.168.1.50 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s resources: irq:25 ioport:de00(size=256) memory:fddff000-fddf memory:fddf8000-fddfbfff -- 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/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.15 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 1823052] Re: After a screen lock, the desktop wallpaper turns to pixel garbage
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 This sounds like it's going to be the same Nvidia backgrounds bug as 1809407. So let's wait till that is resolved before treating this separately. ** This bug has been marked a duplicate of bug 1809407 [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. -- 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/1823052 Title: After a screen lock, the desktop wallpaper turns to pixel garbage Status in xorg package in Ubuntu: New Bug description: As mentioned, after a lock-wake cycle, the wallpaper turns to pixel garbage as seen on the screenshot. Workaround: Setting the wallpaper from GNOME Tweaks, just not in the same adjustment mode as before. For example, if the adjustment was set to Zoom, now I must set it to something else to repair it. Setting it to Zoom again turns it once more into pixel garbage. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1) ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 3 19:22:13 2019 DistUpgraded: 2019-03-29 19:19:33,105 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 4.18.0-16-generic, x86_64: installed nvidia, 418.56, 5.0.0-7-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:380a] Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b] InstallationDate: Installed on 2018-12-31 (93 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 5986:0670 Acer, Inc Bus 001 Device 002: ID 17ef:60b2 Lenovo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=a2f33991-8e13-4dbe-bfae-4a0a1edd71b9 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-03-29 (4 days ago) XorgConf: Section "Extensions" Option "XVideo" "Disable" EndSection dmi.bios.date: 02/15/2017 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN58WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN58WW:bd02/15/2017:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK 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.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 2:2.99.917+git20180925-2 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/xorg/+bug/1823052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1820314] Re: [ASRock FM2A75M-DGS] No sound at all
** Changed in: alsa-driver (Ubuntu) Status: Incomplete => New -- 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/1820314 Title: [ASRock FM2A75M-DGS] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: cannot hear any sound even with headphones from any of 2 rear output port (green and blue) of my asrock fm2a75m-dgs or the front unique one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 15 17:32:51 2019 InstallationDate: Installed on 2016-09-07 (918 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_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.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=auto mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820314/+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 1823007] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
*** This bug is a duplicate of bug 1820314 *** https://bugs.launchpad.net/bugs/1820314 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1820314, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1820314 [ASRock FM2A75M-DGS] No sound at all -- 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/1823007 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: New Bug description: Please this is the same bug i reported before in the fresh install 18.04 lts xubuntu 18.04 partition, with internal gpu (apu a8 5500) enabled with hdmi audio but always analog output does not work. Attached to the previous. Does anyone fix this? 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 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 14:58:53 2019 InstallationDate: Installed on 2019-03-31 (3 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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_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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1823007/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
If I understand it correctly, to completely resolve this issue, we will need mesa + xserver + kernel fix, but currently only mesa fix is in place, right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1714178/+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 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Bump. -- 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/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
Please also try step 2 from comment #2. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
Separately, the "tick" and "thud" may be related to bug 1821663. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
Can you please try some older kernel versions and tell us if any of those avoid the bug? https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
Thanks. It looks like the audio driver in the kernel is broken/confused by suspend and resume: Apr 02 21:18:48 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x1f0500 Apr 02 21:18:48 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x470700 Apr 02 21:18:48 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x570700 Apr 02 21:18:48 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x670700 Apr 02 21:18:48 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x770700 Apr 02 21:18:48 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x470100 Apr 02 21:18:48 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x470881 Apr 02 21:18:48 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x570100 Apr 02 21:18:48 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x570882 Apr 02 21:18:48 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x670100 ... Apr 03 18:39:46 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x1f0500 Apr 03 18:39:46 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x470700 Apr 03 18:39:46 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x570700 Apr 03 18:39:46 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x670700 Apr 03 18:39:46 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x770700 Apr 03 18:39:46 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x470100 Apr 03 18:39:46 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x470881 Apr 03 18:39:46 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x570100 Apr 03 18:39:46 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x570882 Apr 03 18:39:46 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x670100 ... Apr 03 18:39:53 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x40:0x0, last cmd=0x470700 Apr 03 18:39:53 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x470700 Apr 03 18:39:55 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0xa2 Apr 03 18:39:55 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0xa2 Apr 03 18:39:55 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x0:0x0, last cmd=0x1f0500 Apr 03 18:39:55 Imagined kernel: snd_hda_intel :01:00.1: spurious response 0x233:0x0, last cmd=0x1f0500 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture
[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
If you're sure that's the problem then we would need to figure out which kernel version it started in. Please try some different kernel versions: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D and see if you can find the two closest versions where one doesn't have the bug and the other does. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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 briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in xorg-server 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:
[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
In 19.04 right now the bug appears with Adwaita but not with Yaru. That doesn't mean it's a theme bug though -- it might be a universal bug and something about the Yaru design is hiding it. ** Tags added: disco ** Changed in: gtk+3.0 (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1691678/+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
> What about Cosmic? Has anyone actually checked that > the packages still work on Cosmic? why should we? We cannot afford doing test rebuilds for every supported release at the same time. And this is such an issue found for the test rebuilds. -- 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: Fix Committed Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: 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 19.04. 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 1823098] Re: /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf
A hacky workaround is the constantly touch/update the timestamp of /etc/ntp.conf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1823098 Title: /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf Status in ntp package in Ubuntu: New Status in ntp source package in Xenial: New Bug description: Hi, On a few instances in a public cloud, mostly seen in GCE, ntp seems incorrectly set up with: | ubuntu@juju-453c71-0:~$ ntpq -pn | remote refid st t when poll reach delay offset jitter | == | *169.254.169.254 71.79.79.71 2 u 737 1024 3770.6570.136 0.147 We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool' host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version over our configured ntp.conf: | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp" | fi | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp I think this is wrong, if /etc/ntp.conf is configured, it should use that over what DHCP/dhclient provides. | ubuntu@juju-453c71-0:~$ cat /etc/*release | DISTRIB_RELEASE=16.04 | DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" | VERSION_ID="16.04" | ubuntu@juju-453c71-0:~$ dpkg-query -S /etc/init.d/ntp | ntp: /etc/init.d/ntp | ubuntu@juju-453c71-0:~$ apt-cache policy ntp | ntp: | Installed: 1:4.2.8p4+dfsg-3ubuntu5.9 | Candidate: 1:4.2.8p4+dfsg-3ubuntu5.9 | Version table: | *** 1:4.2.8p4+dfsg-3ubuntu5.9 500 | 500 http://us-central1.gce.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages | 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages Thanks, Haw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1823098/+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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
Journal file when sound failed after resume. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1822426/+attachment/5252628/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in pulseaudio package in Ubuntu: Incomplete Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1822426/+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 1823098] [NEW] /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf
Public bug reported: Hi, On a few instances in a public cloud, mostly seen in GCE, ntp seems incorrectly set up with: | ubuntu@juju-453c71-0:~$ ntpq -pn | remote refid st t when poll reach delay offset jitter | == | *169.254.169.254 71.79.79.71 2 u 737 1024 3770.6570.136 0.147 We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool' host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version over our configured ntp.conf: | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp" | fi | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp I think this is wrong, if /etc/ntp.conf is configured, it should use that over what DHCP/dhclient provides. | ubuntu@juju-453c71-0:~$ cat /etc/*release | DISTRIB_RELEASE=16.04 | DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" | VERSION_ID="16.04" | ubuntu@juju-453c71-0:~$ dpkg-query -S /etc/init.d/ntp | ntp: /etc/init.d/ntp | ubuntu@juju-453c71-0:~$ apt-cache policy ntp | ntp: | Installed: 1:4.2.8p4+dfsg-3ubuntu5.9 | Candidate: 1:4.2.8p4+dfsg-3ubuntu5.9 | Version table: | *** 1:4.2.8p4+dfsg-3ubuntu5.9 500 | 500 http://us-central1.gce.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages | 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages Thanks, Haw ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Affects: ntp (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: Hi, On a few instances in a public cloud, mostly seen in GCE, ntp seems incorrectly set up with: | ubuntu@juju-453c71-0:~$ ntpq -pn | remote refid st t when poll reach delay offset jitter | == | *169.254.169.254 71.79.79.71 2 u 737 1024 3770.6570.136 0.147 We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool' host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version over our configured ntp.conf: | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp" | fi | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp I think this is wrong, if /etc/ntp.conf is configured, it should use that over what DHCP/dhclient provides. + | ubuntu@juju-453c71-0:~$ cat /etc/*release + | DISTRIB_RELEASE=16.04 + | DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" + | VERSION_ID="16.04" + + | ubuntu@juju-453c71-0:~$ dpkg-query -S /etc/init.d/ntp + | ntp: /etc/init.d/ntp + + | ubuntu@juju-453c71-0:~$ apt-cache policy ntp + | ntp: + | Installed: 1:4.2.8p4+dfsg-3ubuntu5.9 + | Candidate: 1:4.2.8p4+dfsg-3ubuntu5.9 + | Version table: + | *** 1:4.2.8p4+dfsg-3ubuntu5.9 500 + | 500 http://us-central1.gce.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages + | 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages + Thanks, Haw ** Also affects: ntp (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1823098 Title: /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf Status in ntp package in Ubuntu: New Status in ntp source package in Xenial: New Bug description: Hi, On a few instances in a public cloud, mostly seen in GCE, ntp seems incorrectly set up with: | ubuntu@juju-453c71-0:~$ ntpq -pn | remote refid st t when poll reach delay offset jitter | == | *169.254.169.254 71.79.79.71 2 u 737 1024 3770.6570.136 0.147 We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool' host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version over our configured ntp.conf: | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp" | fi | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp I think this is wrong, if /etc/ntp.conf is configured, it should use that over what DHCP/dhclient provides. | ubuntu@juju-453c71-0:~$ cat /etc/*release |
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
** Description changed: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. * This update bundles python 3.6 and 3.7 point releases - * Following the change in Cosmic and up, this SRU also includes a - distro patch that lowers OPENSSL_TLS_SECURITY_LEVEL from 1 to 0, to - allow for establishing client->server server->client connections with - lower grade security settings (e.g. sub-80bits keys, MD5/SHA1 - certificate checksums, and other crap like that). This is to continue - allow bionic clients to connect to servers operating with older 1.0.x - based openssl, as typically clients are at no mercy to reject servers - that do not have any better certs/keys/signatures. Thus potentially - weak-security connections that previously would fail to establish - to/from bionic, may now be accepted. Some may view this as a regression. - In that case adjust openssl.cnf to a higher TLS_SECURITY_LEVEL, or use - the openssl ctx APIs to set a higher TLS security level. See further - comments in this bug report as to when we will be raising this LEVEL up - (currently timeline is to raise to 2, in 20.04 LTS). - [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via security updates * TLS v1.3 support in GnuTLS is expected to be available in 19.04 * Test OpenSSL is being prepared in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: In Progress Status in libio-socket-ssl-perl source package in Bionic: New Status in libnet-ssleay-perl source package in Bionic: New Status in nova source package in Bionic: New Status in openssl source package in Bionic: Fix Committed Status in python-cryptography source package in Bionic: New Status in python2.7 source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in r-cran-openssl source package in Bionic: Fix Committed Status in ruby-openssl source package in Bionic: Fix Committed Status in ruby2.5 source package in Bionic: New Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) *
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
Hello Dimitri, or anyone else affected, Accepted openssl into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~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. ** Changed in: openssl (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: In Progress Status in libio-socket-ssl-perl source package in Bionic: New Status in libnet-ssleay-perl source package in Bionic: New Status in nova source package in Bionic: New Status in openssl source package in Bionic: Fix Committed Status in python-cryptography source package in Bionic: New Status in python2.7 source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in r-cran-openssl source package in Bionic: Fix Committed Status in ruby-openssl source package in Bionic: Fix Committed Status in ruby2.5 source package in Bionic: New Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. * This update bundles python 3.6 and 3.7 point releases * Following the change in Cosmic and up, this SRU also includes a distro patch that lowers OPENSSL_TLS_SECURITY_LEVEL from 1 to 0, to allow for establishing client->server server->client connections with lower grade security settings (e.g. sub-80bits keys, MD5/SHA1 certificate checksums, and other crap like that). This is to continue allow bionic clients to connect to servers operating with older 1.0.x based openssl, as typically clients are at no mercy to reject servers that do not have any better certs/keys/signatures. Thus potentially weak-security connections that previously would fail to establish to/from bionic, may now be accepted. Some may view this as a regression. In that case adjust openssl.cnf to a higher TLS_SECURITY_LEVEL, or use the openssl ctx APIs to set a higher TLS security level. See further comments in this bug report as to when we will be raising this LEVEL up (currently
[Touch-packages] [Bug 1822544] Re: System clock miracoulously jumped ahead by one hour overnight
** Package changed: tzdata (Ubuntu) => ntp (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1822544 Title: System clock miracoulously jumped ahead by one hour overnight Status in ntp package in Ubuntu: New Bug description: The clock miraculously jumped one hour ahead on my system overnight. Two nights ago there was the switch to summer time. This went fine, i.e. the UTC system clock was not changed and the system just added another hour to interpret it as UTC+2 (CEST). However, this morning I found that over the next night the UTC system clock was incorrectly advanced by one hour. The system was suspended, but not rebooted, there is no Windows installation/virtual machine that could mess with the clock. ntpdate -q displays the error message "no servers can be used, exiting", but this cannot explain why the clock jumped ahead. The clock was reset correctly after I replaced ntp with chrony. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: tzdata 2018i-0ubuntu0.18.04 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 1 10:17:50 2019 InstallationDate: Installed on 2015-11-05 (1242 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: tzdata UpgradeStatus: Upgraded to bionic on 2018-05-24 (311 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1822544/+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 1823055] Re: krb5-user fails to install on 18.04 AMD64
This was an in-house template virtual machine with a base 18.04 server installer. I'm not 100% if it was from 18.04 or 18.04.1. I have since corrected the issue and generated a new template so we won't have to worry about it in the future :) On Wed, Apr 3, 2019 at 2:25 PM Andreas Hasenack wrote: > Correct, thanks for letting us known. This but in the 18.04 installer is > nowadays fixed. If you got it with the latest installer > (http://cdimage.ubuntu.com/releases/18.04.2/release/) then it's a > regression. Can you please verify which iso image you used? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1823055 > > Title: > krb5-user fails to install on 18.04 AMD64 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+subscriptions > -- Jamey Steinmann 407.697.0197 jameysteinm...@gmail.com -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1823055 Title: krb5-user fails to install on 18.04 AMD64 Status in krb5 package in Ubuntu: Invalid Bug description: When installing the package krb5-user(1.16-2build1) it fails due to dependency on libkrb5-3. Apt-Get is expecting 1.16-2build1 but only 1.16-ubuntu0.1 is available for the libkrb5-3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+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 1806012] Re: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server
@lathiat: > - Is there some specific hardware where scaling-driver=pcc-cpufreq > and scaling-governor=ondemand performs poorly. I have yet to run a > benchmark on my example hardware to find out. Yes, we first started seeing this when deploying new Ubuntu Archive servers where we had two servers in the same DC taking on the same amount of traffic/requests. One was showing much higher load and performing much worse than the other. We brought up others in another DC and saw the same. The internal ticket, RT#90571, has some details. The specs differ with the one without issues being: | economy - HP ProLiant DL380 G7 The ones that were showing issues are: | hanger - HP ProLiant DL360p Gen8 | steelix - ProLiant DL380 Gen9 | keeton - ProLiant DL380p Gen8 By default, they're using the pcc-cpufreq but we also tried acpi-cpufreq which didn't seem to have made any difference. This led to us filing LP: #1579278 and the change to a piece of software we use to deploy disabling the 'ondemand' CPU governor: | https://bazaar.launchpad.net/~canonical- sysadmins/basenode/trunk/revision/98 -- 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/1806012 Title: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: Whilst debugging 'slow instance performance' on a Ubuntu Bionic based cloud, I observed that the default cpu governor configuration was set to 'powersave'; toggling this to 'performance' (while in not anyway a particularly green thing todo) resulted in the instance slowness disappearing and the cloud performance being as expected (based on a prior version of the deploy on Ubuntu Xenial). AFAICT Xenial does the same thing albeit in a slight different way, but we definitely did not see the same performance laggy-ness under a Xenial based cloud. Raising against systemd (as this package sets the governor to 'powersave') - I feel that the switch to 'performance' although appropriate then obscures what might be a performance/behavioural difference in the underlying kernel when a machine is under load. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.9 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 Date: Fri Nov 30 10:05:46 2018 Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt intel_iommu=on SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012/+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 1821863] Re: Need to add Intel CML related pci-id's
** Changed in: linux (Ubuntu Disco) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Committed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Committed Status in mesa source package in Disco: New Status in xorg-server source package in Disco: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 294830] Re: libpcsclite.so versions >1.4.99 and <1.8.25 causes crash of firefox/chrome
#7 0x7fffdef0702e in MessageSend (buffer_void=buffer_void@entry=0x7fffd60030d0, buffer_size=buffer_size@entry=8, filedes=filedes@entry=1024) at winscard_msg.c:372 The file descriptor value is 1024. This is the default maximum number of opened file for a process. You can check that using "ulimit -n". The GNU libC then aborts the call, but your backtrace does not indicate the name of the function that is aborted. I guess it is send(2). Using more than 1024 opened files is NOT normal. I really suspect a bug in the proprietary PKCS#11 library /usr/local/AWP/lib/libOcsCryptoki.so You can increase the limit using "ulimit -n 2000" just to see what happens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/294830 Title: libpcsclite.so versions >1.4.99 and <1.8.25 causes crash of firefox/chrome Status in pcsc-lite package in Ubuntu: Fix Committed Bug description: pcscd with version after 1.4.99 causes crash of firefox if smart card reader is not inserted, and in result firefox can not start in Ubuntu 8.10 package pcscd 1.4.102-1u is not good, i recommend to rollback to 1.4.99 or older version of pcscd this issue is not only in Ubuntu, it persist in Slackware too configuration - reader Omnikey 6121 with smart card Siemens HiPath SIcurity card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/294830/+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 1823076] [NEW] Intel NUC (8I3BEH1) wakes up immediately after suspend after installing BlueZ
Public bug reported: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1823076 Title: Intel NUC (8I3BEH1) wakes up immediately after suspend after installing BlueZ Status in bluez package in Ubuntu: New Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:
[Touch-packages] [Bug 1823077] [NEW] Cannot upgrade libxkbcommon0 without removing half the operating system
Public bug reported: Attempting to upgrade the libxkbcommon0:i386 0.8.0-1ubuntu0.1 to 0.8.2-1~ubuntu18.04.1 will cause a large amount of packages central to the OS to be removed - basically more than a thousand packages. Never seen anything like this. Dependencies need to be fixed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxkbcommon0 0.8.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Apr 3 16:22:28 2019 Dependencies: gcc-8-base 8.3.0-5ubuntu1~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-5ubuntu1~18.04 xkb-data 2.23.1-1ubuntu1.18.04.1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-17-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (78 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_guc=-1 vt.handoff=1 SourcePackage: libxkbcommon UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp3-c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: galp3-c dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version: galp3-c dmi.sys.vendor: System76 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1ubuntu1~18.04~ppa1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1ubuntu1~18.04~ppa1 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: libxkbcommon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 ubuntu -- 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/1823077 Title: Cannot upgrade libxkbcommon0 without removing half the operating system Status in libxkbcommon package in Ubuntu: New Bug description: Attempting to upgrade the libxkbcommon0:i386 0.8.0-1ubuntu0.1 to 0.8.2-1~ubuntu18.04.1 will cause a large amount of packages central to the OS to be removed - basically more than a thousand packages. Never seen anything like this. Dependencies need to be fixed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxkbcommon0 0.8.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Apr 3 16:22:28 2019 Dependencies: gcc-8-base 8.3.0-5ubuntu1~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-5ubuntu1~18.04 xkb-data 2.23.1-1ubuntu1.18.04.1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-17-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (78 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago
[Touch-packages] [Bug 1823063] Re: package libtool 2.4.6-4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: fsys-tarfile-error ** Changed in: libtool (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtool in Ubuntu. https://bugs.launchpad.net/bugs/1823063 Title: package libtool 2.4.6-4 failed to install/upgrade: dpkg-deb --fsys- tarfile subprocess returned error exit status 2 Status in libtool package in Ubuntu: Invalid Bug description: Trying to rebuild modules for VMware workstation 15 Pro after kernel upgrade to 4.18.0-17-generic ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libtool 2.4.6-4 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Wed Apr 3 11:42:22 2019 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2019-03-20 (14 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: libtool Title: package libtool 2.4.6-4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1823063/+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 1822984] Re: revert tls security level back to 1
** Changed in: openssl (Ubuntu Cosmic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822984 Title: revert tls security level back to 1 Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Cosmic: In Progress Status in openssl source package in Disco: Fix Committed Bug description: [Impact] * increase minimum default tls security level from 0 to 1, as is the default upstream [Test Case] * generate 80bits TLS certificate and attempt to use it * with prior openssl it should work, but with this update it should fail [Regression Potential] * This increases the minimum required certificate/keys sizes and algorithms, back to what Bionic GA openssl 1.1.0 shipped as. It also now will match upstream default. It is still lower than Debian's default that raises it to 2 by default. * Cosmic GA shipped with TLS_SECURITY_LEVEL 0, meaning pretty much any weak keys were accepted. With this change keys lower than 112 will be rejected, which are considered to be too weak to be useful by most CAs out there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822984/+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 1822898] Re: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i
** Changed in: openssl (Ubuntu Cosmic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822898 Title: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Cosmic: In Progress Status in openssl source package in Disco: Fix Committed Status in openssl package in Debian: New Bug description: [Impact] * fetch-url cannot use https protocol (no https preseeds) [Test case] * in d-i, mini.iso, tty try wget https://geoip.ubuntu.com/lookup it should succeed. [Solution] The required openssl.cnf configuration file is missing, needs to simply exists, even if it is empty. [Regression Potential] well, if one cannot download over https / init ssl library in d-i, it's hard to get openssl busted more than that. No code changes on the .deb side of things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822898/+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 1823070] [NEW] unattended-upgrades should tell the user (via motd) when security updates are held back
Public bug reported: Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later: 1) unattended-upgrades automatically installs security updates daily by default 2) the motd reports the number of available updates, including security updates. A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about. However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system. In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*. Suggested wording: N security updates will not be automatically installed due to local changes. See /var/log/foo for details. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- 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/1823070 Title: unattended-upgrades should tell the user (via motd) when security updates are held back Status in unattended-upgrades package in Ubuntu: New Bug description: Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later: 1) unattended-upgrades automatically installs security updates daily by default 2) the motd reports the number of available updates, including security updates. A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about. However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system. In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*. Suggested wording: N security updates will not be automatically installed due to local changes. See /var/log/foo for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+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 1823063] [NEW] package libtool 2.4.6-4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: Trying to rebuild modules for VMware workstation 15 Pro after kernel upgrade to 4.18.0-17-generic ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libtool 2.4.6-4 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Wed Apr 3 11:42:22 2019 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2019-03-20 (14 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: libtool Title: package libtool 2.4.6-4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libtool (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtool in Ubuntu. https://bugs.launchpad.net/bugs/1823063 Title: package libtool 2.4.6-4 failed to install/upgrade: dpkg-deb --fsys- tarfile subprocess returned error exit status 2 Status in libtool package in Ubuntu: New Bug description: Trying to rebuild modules for VMware workstation 15 Pro after kernel upgrade to 4.18.0-17-generic ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libtool 2.4.6-4 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Wed Apr 3 11:42:22 2019 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2019-03-20 (14 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: libtool Title: package libtool 2.4.6-4 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1823063/+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 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package
This bug was fixed in the package ubuntu-meta - 1.431 --- ubuntu-meta (1.431) disco; urgency=medium * Refreshed dependencies * Added multipath-tools to server * Added thunderbird to desktop-recommends [s390x] * Added thunderbird-gnome-support to desktop-recommends [s390x] * Added ubuntu-wsl binary package depending on wslu (LP: #1822341) -- Balint Reczey Mon, 01 Apr 2019 12:38:30 +0200 ** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1822341 Title: [FFE][SRU] Please add ubuntu-wsl binary package Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: [Impact] * The newly added wsl seed includes the packages to be installed by default on Ubuntu running in the Windows Subsystem for Linux. In addition to the packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on utilities useful only in the WSL environment. [Test Case] * The package is a new metapackage, just try installing it [Fix] * The change add the new package and also adds the wsl seed to watch. [Regression potential] * Nothing, it is a new meta package, with no breaks, etc. [Other Info] * Please consider accepting this new binary package to Disco, because it needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will allow adding new packages for WSL installations only when more integration utilities become available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1822370] Re: 19.04 beta openssh-client broken pipe
@jsavanyo: Thanks for following up! The iptables-related part of the discussion may yet yield an openssh packaging change; we'll see. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1822370 Title: 19.04 beta openssh-client broken pipe Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: New Bug description: New versions of openssh (as in Ubuntu 19.04) are reported to trigger a connection issue: packet_write_wait: Connection to x.x.x.x port 22: Broken pipe In most of the cases this seems to affect VMWare based environments as there is a bug in their implementation in regard to the traffic shaping protocols. Until resolved by VMWare the workarounds for now are: Configure your client to use the old defaults permanently in => /etc/ssh/ssh_config Host * IPQoS lowdelay throughput # You might want to limit to your VMware based systems Or per command via: $ ssh IPQoS="latency throughput" user@host Two values as one is for interactive and one for non-interactive use cases. original report Upgrade to Xubuntu 19.04 beta from 18.10 openssh-client when trying to ssh into another system, following error: packet_write_wait: Connection to x.x.x.x port 22: Broken pipe Problem is consistent on trying to connect to various systems. Can confirm was able to ssh prior to upgrade and can ssh into these systems from other systems. Can use putty on this system to ssh into these boxes as well. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openssh-client 1:7.9p1-9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 29 13:36:38 2019 InstallationDate: Installed on 2018-11-14 (135 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b 26 Feb 2019 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1822370] Re: 19.04 beta openssh-client broken pipe
@paelzer: A day is a bit soon to be stressing about lack of feedback, I think. We have time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1822370 Title: 19.04 beta openssh-client broken pipe Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: New Bug description: New versions of openssh (as in Ubuntu 19.04) are reported to trigger a connection issue: packet_write_wait: Connection to x.x.x.x port 22: Broken pipe In most of the cases this seems to affect VMWare based environments as there is a bug in their implementation in regard to the traffic shaping protocols. Until resolved by VMWare the workarounds for now are: Configure your client to use the old defaults permanently in => /etc/ssh/ssh_config Host * IPQoS lowdelay throughput # You might want to limit to your VMware based systems Or per command via: $ ssh IPQoS="latency throughput" user@host Two values as one is for interactive and one for non-interactive use cases. original report Upgrade to Xubuntu 19.04 beta from 18.10 openssh-client when trying to ssh into another system, following error: packet_write_wait: Connection to x.x.x.x port 22: Broken pipe Problem is consistent on trying to connect to various systems. Can confirm was able to ssh prior to upgrade and can ssh into these systems from other systems. Can use putty on this system to ssh into these boxes as well. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openssh-client 1:7.9p1-9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 29 13:36:38 2019 InstallationDate: Installed on 2018-11-14 (135 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b 26 Feb 2019 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1823055] Re: krb5-user fails to install on 18.04 AMD64
Correct, thanks for letting us known. This but in the 18.04 installer is nowadays fixed. If you got it with the latest installer (http://cdimage.ubuntu.com/releases/18.04.2/release/) then it's a regression. Can you please verify which iso image you used? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1823055 Title: krb5-user fails to install on 18.04 AMD64 Status in krb5 package in Ubuntu: Invalid Bug description: When installing the package krb5-user(1.16-2build1) it fails due to dependency on libkrb5-3. Apt-Get is expecting 1.16-2build1 but only 1.16-ubuntu0.1 is available for the libkrb5-3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+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 294830] Re: libpcsclite.so versions >1.4.99 and <1.8.25 causes crash of firefox/chrome
Only version libpcsclite1-dbg_1.8.23-1_amd64.deb was available, but seems to be the same crash. Also got firefox-dbg. Backtrace added. ** Attachment added: "firefox crash backtrace debug (firefox, pcsc-lite)" https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/294830/+attachment/5252573/+files/firefox%20crash%20backtrace%20debug%20%28firefox%2C%20pcsc-lite%29 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/294830 Title: libpcsclite.so versions >1.4.99 and <1.8.25 causes crash of firefox/chrome Status in pcsc-lite package in Ubuntu: Fix Committed Bug description: pcscd with version after 1.4.99 causes crash of firefox if smart card reader is not inserted, and in result firefox can not start in Ubuntu 8.10 package pcscd 1.4.102-1u is not good, i recommend to rollback to 1.4.99 or older version of pcscd this issue is not only in Ubuntu, it persist in Slackware too configuration - reader Omnikey 6121 with smart card Siemens HiPath SIcurity card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/294830/+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 1823055] Re: krb5-user fails to install on 18.04 AMD64
current universe repo for 18.04.2 was missing causing the conflict. ** Changed in: krb5 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1823055 Title: krb5-user fails to install on 18.04 AMD64 Status in krb5 package in Ubuntu: Invalid Bug description: When installing the package krb5-user(1.16-2build1) it fails due to dependency on libkrb5-3. Apt-Get is expecting 1.16-2build1 but only 1.16-ubuntu0.1 is available for the libkrb5-3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+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 1823055] Re: krb5-user fails to install on 18.04 AMD64
I was missing the universe repo. I actually just resolved it and came here to say make sure the Universe repo is enabled. It appears to be a known issue with the Ubuntu 18.04.1 installer not enabling this repo by default -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1823055 Title: krb5-user fails to install on 18.04 AMD64 Status in krb5 package in Ubuntu: Invalid Bug description: When installing the package krb5-user(1.16-2build1) it fails due to dependency on libkrb5-3. Apt-Get is expecting 1.16-2build1 but only 1.16-ubuntu0.1 is available for the libkrb5-3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+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 1822370] Re: 19.04 beta openssh-client broken pipe
VMware bug 2319367 was closed as a duplicate of bug 2275007 which was closed as a duplicate of bug 2201049. Good news is that bug 2201049 is fixed in a future unreleased version of Workstation and Fusion. I'm not aware of a plan to back port fix to maintenance patch yet. I will ask. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1822370 Title: 19.04 beta openssh-client broken pipe Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: New Bug description: New versions of openssh (as in Ubuntu 19.04) are reported to trigger a connection issue: packet_write_wait: Connection to x.x.x.x port 22: Broken pipe In most of the cases this seems to affect VMWare based environments as there is a bug in their implementation in regard to the traffic shaping protocols. Until resolved by VMWare the workarounds for now are: Configure your client to use the old defaults permanently in => /etc/ssh/ssh_config Host * IPQoS lowdelay throughput # You might want to limit to your VMware based systems Or per command via: $ ssh IPQoS="latency throughput" user@host Two values as one is for interactive and one for non-interactive use cases. original report Upgrade to Xubuntu 19.04 beta from 18.10 openssh-client when trying to ssh into another system, following error: packet_write_wait: Connection to x.x.x.x port 22: Broken pipe Problem is consistent on trying to connect to various systems. Can confirm was able to ssh prior to upgrade and can ssh into these systems from other systems. Can use putty on this system to ssh into these boxes as well. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openssh-client 1:7.9p1-9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 29 13:36:38 2019 InstallationDate: Installed on 2018-11-14 (135 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b 26 Feb 2019 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1823055] Re: krb5-user fails to install on 18.04 AMD64
Can you check if you have all repositories enabled? main, restricted, universe, multiverse, and updates and security? Please show: apt-cache policy krb5-user libkrb5-3 ** Changed in: krb5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1823055 Title: krb5-user fails to install on 18.04 AMD64 Status in krb5 package in Ubuntu: Incomplete Bug description: When installing the package krb5-user(1.16-2build1) it fails due to dependency on libkrb5-3. Apt-Get is expecting 1.16-2build1 but only 1.16-ubuntu0.1 is available for the libkrb5-3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+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 1822118] Re: Kernel Panic while rebooting cloud instance
I modified your script to perform 5000 reboots. I'm up to 3508 reboots now without hitting the bug. I'll let it run for a while longer. I'll also compare our environments to see if there is a difference. -- 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/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+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 1823053] [NEW] wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco
Public bug reported: Ubuntu 18.10 "Cosmic" and 19.04 "Disco" currently ship with both wpasupplicant 2.6 and openssl/libssl 1.1.1, although upstream only supports OpenSSL 1.1.1 starting with wpasupplicant 2.7. OpenSSL 1.1.1 introduced support for TLS 1.3, and introduced new APIs to configure the parameters governing TLS connections using TLS >= 1.3. OpenSSL also decided that it would enable TLS 1.3 by default even for software that had only been built for libssl <= 1.1.0 and hence couldn't "know" about the new APIs. This leads to a situation where software that was designed/built for OpenSSL 1.1.0 and TLS 1.2 will also offer TLS 1.3, without any possibility for end users to disable such behavior. One case where this causes problems is wpasupplicant: wpasupplicant 2.7 officially introduced support for OpenSSL 1.1.1, which mainly consists of disabling TLS 1.3 by default and adding a configuration flag allowing end users to selectively enable it for connections when they see fit. wpasupplicant 2.6, however, as shipped with Ubuntu 18.10 and 19.04, does not offer such a possibility, and hence tries negotiating TLS 1.3 (alongside with older versions all the way down to TLS 1.0). Sadly, there are RADIUS servers which suffer from TLS version intolerance and will refuse authentication when the client offers TLS 1.3. I know of such a case with a German university's eduroam wifi, but I doubt this is the only case where this causes problems. As a dirty stopgap measure, I've installed the wpasupplicant 2.7 package from Debian Buster (https://packages.debian.org/buster/wpasupplicant), and I've asked the NOC at the affected university to upgrade/reconfigure their RADIUS server to make the version intolerance go away - but still, this is a bug that should be fixed in Ubuntu, preferably by backporting wpasupplicant 2.7. ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: eap eduroam libssl openssl peap tls1.3 tlsv1.3 ttls wpa wpa-enterprise wpasupplicant -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1823053 Title: wpasupplicant 2.6 w/ openssl 1.1.1 triggers TLSv1.3 version intolerance on WPA2-Enterprise networks on Cosmic and Disco Status in wpa package in Ubuntu: New Bug description: Ubuntu 18.10 "Cosmic" and 19.04 "Disco" currently ship with both wpasupplicant 2.6 and openssl/libssl 1.1.1, although upstream only supports OpenSSL 1.1.1 starting with wpasupplicant 2.7. OpenSSL 1.1.1 introduced support for TLS 1.3, and introduced new APIs to configure the parameters governing TLS connections using TLS >= 1.3. OpenSSL also decided that it would enable TLS 1.3 by default even for software that had only been built for libssl <= 1.1.0 and hence couldn't "know" about the new APIs. This leads to a situation where software that was designed/built for OpenSSL 1.1.0 and TLS 1.2 will also offer TLS 1.3, without any possibility for end users to disable such behavior. One case where this causes problems is wpasupplicant: wpasupplicant 2.7 officially introduced support for OpenSSL 1.1.1, which mainly consists of disabling TLS 1.3 by default and adding a configuration flag allowing end users to selectively enable it for connections when they see fit. wpasupplicant 2.6, however, as shipped with Ubuntu 18.10 and 19.04, does not offer such a possibility, and hence tries negotiating TLS 1.3 (alongside with older versions all the way down to TLS 1.0). Sadly, there are RADIUS servers which suffer from TLS version intolerance and will refuse authentication when the client offers TLS 1.3. I know of such a case with a German university's eduroam wifi, but I doubt this is the only case where this causes problems. As a dirty stopgap measure, I've installed the wpasupplicant 2.7 package from Debian Buster (https://packages.debian.org/buster/wpasupplicant), and I've asked the NOC at the affected university to upgrade/reconfigure their RADIUS server to make the version intolerance go away - but still, this is a bug that should be fixed in Ubuntu, preferably by backporting wpasupplicant 2.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1823053/+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 1823055] [NEW] krb5-user fails to install on 18.04 AMD64
Public bug reported: When installing the package krb5-user(1.16-2build1) it fails due to dependency on libkrb5-3. Apt-Get is expecting 1.16-2build1 but only 1.16-ubuntu0.1 is available for the libkrb5-3 package ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1823055 Title: krb5-user fails to install on 18.04 AMD64 Status in krb5 package in Ubuntu: New Bug description: When installing the package krb5-user(1.16-2build1) it fails due to dependency on libkrb5-3. Apt-Get is expecting 1.16-2build1 but only 1.16-ubuntu0.1 is available for the libkrb5-3 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1823055/+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 1823052] [NEW] After a screen lock, the desktop wallpaper turns to pixel garbage
Public bug reported: As mentioned, after a lock-wake cycle, the wallpaper turns to pixel garbage as seen on the screenshot. Workaround: Setting the wallpaper from GNOME Tweaks, just not in the same adjustment mode as before. For example, if the adjustment was set to Zoom, now I must set it to something else to repair it. Setting it to Zoom again turns it once more into pixel garbage. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1) ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 3 19:22:13 2019 DistUpgraded: 2019-03-29 19:19:33,105 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 4.18.0-16-generic, x86_64: installed nvidia, 418.56, 5.0.0-7-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:380a] Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b] InstallationDate: Installed on 2018-12-31 (93 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 5986:0670 Acer, Inc Bus 001 Device 002: ID 17ef:60b2 Lenovo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=a2f33991-8e13-4dbe-bfae-4a0a1edd71b9 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-03-29 (4 days ago) XorgConf: Section "Extensions" Option "XVideo" "Disable" EndSection dmi.bios.date: 02/15/2017 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN58WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN58WW:bd02/15/2017:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK 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.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption disco possible-manual-nvidia-install ubuntu ** Attachment added: "Screenshot from 2019-04-03 19-23-35.png" https://bugs.launchpad.net/bugs/1823052/+attachment/5252546/+files/Screenshot%20from%202019-04-03%2019-23-35.png -- 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/1823052 Title: After a screen lock, the desktop wallpaper turns to pixel garbage Status in xorg package in Ubuntu: New Bug description: As mentioned, after a lock-wake cycle, the wallpaper turns to pixel garbage as seen on the screenshot. Workaround: Setting the wallpaper from GNOME Tweaks, just not in the same adjustment mode as before. For example, if the adjustment was set to Zoom, now I must set it to something else to repair it. Setting it to Zoom again turns it once more into pixel garbage. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
Adwaita? What about Yaru? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1691678/+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 1822984] Re: revert tls security level back to 1
But equally, I would not want to keep cosmic more insecure than what bionic and disco will be. And currently, cosmic is a release regression w.r.t. bionic GA. Upgrading to newer releases, should not result in looser acceptance of insecure protocols. ** Description changed: [Impact] * increase minimum default tls security level from 0 to 1, as is the default upstream [Test Case] * generate 80bits TLS certificate and attempt to use it * with prior openssl it should work, but with this update it should fail [Regression Potential] * This increases the minimum required certificate/keys sizes and algorithms, back to what Bionic GA openssl 1.1.0 shipped as. It also now will match upstream default. It is still lower than Debian's default that raises it to 2 by default. + + * Cosmic GA shipped with TLS_SECURITY_LEVEL 0, meaning pretty much any + weak keys were accepted. With this change keys lower than 112 will be + rejected, which are considered to be too weak to be useful by most CAs + out there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822984 Title: revert tls security level back to 1 Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Cosmic: New Status in openssl source package in Disco: Fix Committed Bug description: [Impact] * increase minimum default tls security level from 0 to 1, as is the default upstream [Test Case] * generate 80bits TLS certificate and attempt to use it * with prior openssl it should work, but with this update it should fail [Regression Potential] * This increases the minimum required certificate/keys sizes and algorithms, back to what Bionic GA openssl 1.1.0 shipped as. It also now will match upstream default. It is still lower than Debian's default that raises it to 2 by default. * Cosmic GA shipped with TLS_SECURITY_LEVEL 0, meaning pretty much any weak keys were accepted. With this change keys lower than 112 will be rejected, which are considered to be too weak to be useful by most CAs out there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822984/+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 1822984] Re: revert tls security level back to 1
The patch was added by Dimitri in cosmic to restore compatibility with older and less secure TLS implementations using weak keys. However, bionic shipped without compatibility with those less secure keys, and we are unaware of any complaints about this change in bionic. This distro patch to lower the security baseline of openssl 1.1 was being introduced in SRU to bionic as part of the openssl 1.1.1 backport, and I rejected that upload after discussion with the security team, because it is not justifiable for the SRU to *lower* the security baseline in SRU without specific reports of breakage. And since the protocol baseline in bionic is incompatible with those servers, there is no reason for newer non-LTS releases to be compatible with them. Hence, dropping the patch for devel is, I believe, obviously correct. SRUing that same change to cosmic is not as obviously correct since it carries some risk of regression vs. the state of cosmic at time of release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822984 Title: revert tls security level back to 1 Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Cosmic: New Status in openssl source package in Disco: Fix Committed Bug description: [Impact] * increase minimum default tls security level from 0 to 1, as is the default upstream [Test Case] * generate 80bits TLS certificate and attempt to use it * with prior openssl it should work, but with this update it should fail [Regression Potential] * This increases the minimum required certificate/keys sizes and algorithms, back to what Bionic GA openssl 1.1.0 shipped as. It also now will match upstream default. It is still lower than Debian's default that raises it to 2 by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822984/+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 1796251] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from g
** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1796251 Title: gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv() Status in GNOME Shell: Fix Released Status in gdk-pixbuf package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/1473c291c70d181ad72605561ac28f3b860445d5 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/gnome-shell/+bug/1796251/+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 1822773] Re: Volume resets to 0 on startup
The sound should be restored at the system/alsa level ** Package changed: gnome-settings-daemon (Ubuntu) => alsa-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1822773 Title: Volume resets to 0 on startup Status in alsa-utils package in Ubuntu: New Bug description: Steps to reproduce the problem 1. Set the volume to some value like 100 or 80% 2. Shutdown and start the system 3. Volume is set to 0%. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1822773/+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 1822984] Re: revert tls security level back to 1
looks like someone else accepted with this question still pending... still would appreciate an answer -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822984 Title: revert tls security level back to 1 Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Cosmic: New Status in openssl source package in Disco: Fix Committed Bug description: [Impact] * increase minimum default tls security level from 0 to 1, as is the default upstream [Test Case] * generate 80bits TLS certificate and attempt to use it * with prior openssl it should work, but with this update it should fail [Regression Potential] * This increases the minimum required certificate/keys sizes and algorithms, back to what Bionic GA openssl 1.1.0 shipped as. It also now will match upstream default. It is still lower than Debian's default that raises it to 2 by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822984/+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 1822773] [NEW] Volume resets to 0 on startup
You have been subscribed to a public bug: Steps to reproduce the problem 1. Set the volume to some value like 100 or 80% 2. Shutdown and start the system 3. Volume is set to 0%. Ubuntu 18.10 ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New -- Volume resets to 0 on startup https://bugs.launchpad.net/bugs/1822773 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils 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 1815742] Re: latest network-manager segfaults in disco
Great, thanks for testing! -- 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/1815742 Title: latest network-manager segfaults in disco Status in network-manager package in Ubuntu: Fix Released Bug description: When I updated to the latest version of networkmanager in disco dingo (1.15.2-0ubuntu1), it started segfaulting. Reverting to the version in cosmic (1.12.4-1ubuntu1.2) solved the problem. Syslog shows the following (will attach a more complete log): feb 13 10:39:45 regan NetworkManager[2315]: NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added: assertion failed: __extension__ ({ GTypeInstance *__inst = (GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type ())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && __inst->g_class->g_type == __t) __r = (!(0)); else __r = g_type_check_instance_is_a (__inst, __t); __r; }) feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612] ifupdown: management mode: managed feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type '(null)' in cast to 'NMSettingsConnection' feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2016-12-22 (782 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.12.4-1ubuntu1.2 PackageArchitecture: amd64 Tags: disco Uname: Linux 4.19.0-1-amd64 x86_64 UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago) UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev sambashare scanner src sudo tss wireshark _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-06-01T16:38:44.962715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
This issue is still there in in the current beta of Ubuntu 19.04 (Gnome 3.32 with Adwaita). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1691678/+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 1815742] Re: latest network-manager segfaults in disco
Yes, this version works perfectly. Thanks! -- 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/1815742 Title: latest network-manager segfaults in disco Status in network-manager package in Ubuntu: Fix Released Bug description: When I updated to the latest version of networkmanager in disco dingo (1.15.2-0ubuntu1), it started segfaulting. Reverting to the version in cosmic (1.12.4-1ubuntu1.2) solved the problem. Syslog shows the following (will attach a more complete log): feb 13 10:39:45 regan NetworkManager[2315]: NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added: assertion failed: __extension__ ({ GTypeInstance *__inst = (GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type ())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && __inst->g_class->g_type == __t) __r = (!(0)); else __r = g_type_check_instance_is_a (__inst, __t); __r; }) feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612] ifupdown: management mode: managed feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type '(null)' in cast to 'NMSettingsConnection' feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2016-12-22 (782 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.12.4-1ubuntu1.2 PackageArchitecture: amd64 Tags: disco Uname: Linux 4.19.0-1-amd64 x86_64 UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago) UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev sambashare scanner src sudo tss wireshark _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-06-01T16:38:44.962715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1815742] Re: latest network-manager segfaults in disco
I've backported the patch upstream recommended, it would be nice if you could give it a try to see if it really resolves your issue -- 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/1815742 Title: latest network-manager segfaults in disco Status in network-manager package in Ubuntu: Fix Released Bug description: When I updated to the latest version of networkmanager in disco dingo (1.15.2-0ubuntu1), it started segfaulting. Reverting to the version in cosmic (1.12.4-1ubuntu1.2) solved the problem. Syslog shows the following (will attach a more complete log): feb 13 10:39:45 regan NetworkManager[2315]: NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added: assertion failed: __extension__ ({ GTypeInstance *__inst = (GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type ())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && __inst->g_class->g_type == __t) __r = (!(0)); else __r = g_type_check_instance_is_a (__inst, __t); __r; }) feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612] ifupdown: management mode: managed feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type '(null)' in cast to 'NMSettingsConnection' feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2016-12-22 (782 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.12.4-1ubuntu1.2 PackageArchitecture: amd64 Tags: disco Uname: Linux 4.19.0-1-amd64 x86_64 UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago) UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev sambashare scanner src sudo tss wireshark _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-06-01T16:38:44.962715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option
can't believe it was fixed in less than 3 short years -- 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/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: Fix Released Bug description: [Impact] initramfs-tools would always include all "framebuffer" drivers/firmware inside initramfs, which was making it ever more huge. In some systems with low memory, that would even prevent systems to boot. kdump, for example, had an impact. [Test case] Different systems on different arches were tested. When cryptsetup (or cryptsetup-initramfs) was installed, framebuffer drivers were included in the ramdisk. When not installed, the initramfs was smaller. Systems booted on both cases. Systems with encrypted disks were tested as well. [Regression Potential] Systems may not boot because of missing drivers. Users may have a different experience during boot because of missing "framebuffer" drivers. == initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+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 1822984] Re: revert tls security level back to 1
that regression potential doesn't really describe what might regress... I think it could be improved. since you asked me to review, can you give a bit more context for the change please? why did we have the patch before and why can it be removed now? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822984 Title: revert tls security level back to 1 Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Cosmic: New Status in openssl source package in Disco: Fix Committed Bug description: [Impact] * increase minimum default tls security level from 0 to 1, as is the default upstream [Test Case] * generate 80bits TLS certificate and attempt to use it * with prior openssl it should work, but with this update it should fail [Regression Potential] * This increases the minimum required certificate/keys sizes and algorithms, back to what Bionic GA openssl 1.1.0 shipped as. It also now will match upstream default. It is still lower than Debian's default that raises it to 2 by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822984/+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 1815742] Re: latest network-manager segfaults in disco
This bug was fixed in the package network-manager - 1.16.0-0ubuntu2 --- network-manager (1.16.0-0ubuntu2) disco; urgency=medium * debian/patches/git_ifupdown_iterator.patch: - ifupdown: fix connection iterator, should fix a segfault in the corresponding plugin (lp: #1815742) -- Sebastien Bacher Tue, 02 Apr 2019 17:53:26 +0200 ** Changed in: network-manager (Ubuntu) Status: Triaged => Fix Released -- 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/1815742 Title: latest network-manager segfaults in disco Status in network-manager package in Ubuntu: Fix Released Bug description: When I updated to the latest version of networkmanager in disco dingo (1.15.2-0ubuntu1), it started segfaulting. Reverting to the version in cosmic (1.12.4-1ubuntu1.2) solved the problem. Syslog shows the following (will attach a more complete log): feb 13 10:39:45 regan NetworkManager[2315]: NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added: assertion failed: __extension__ ({ GTypeInstance *__inst = (GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type ())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && __inst->g_class->g_type == __t) __r = (!(0)); else __r = g_type_check_instance_is_a (__inst, __t); __r; }) feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612] ifupdown: management mode: managed feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type '(null)' in cast to 'NMSettingsConnection' feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2016-12-22 (782 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.12.4-1ubuntu1.2 PackageArchitecture: amd64 Tags: disco Uname: Linux 4.19.0-1-amd64 x86_64 UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago) UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev sambashare scanner src sudo tss wireshark _MarkForUpload: True mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2018-06-01T16:38:44.962715 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1806012] Re: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server
TBH it was probably whatever the default mode was in the BIOS - we saw the same issue on Dell and HP servers. This one >> "You mean that you let systemd ondemand service do whatever it does by default" -- 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/1806012 Title: set-cpufreq: 'powersave' governor configuration sanity on ubuntu server Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: Whilst debugging 'slow instance performance' on a Ubuntu Bionic based cloud, I observed that the default cpu governor configuration was set to 'powersave'; toggling this to 'performance' (while in not anyway a particularly green thing todo) resulted in the instance slowness disappearing and the cloud performance being as expected (based on a prior version of the deploy on Ubuntu Xenial). AFAICT Xenial does the same thing albeit in a slight different way, but we definitely did not see the same performance laggy-ness under a Xenial based cloud. Raising against systemd (as this package sets the governor to 'powersave') - I feel that the switch to 'performance' although appropriate then obscures what might be a performance/behavioural difference in the underlying kernel when a machine is under load. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.9 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 Date: Fri Nov 30 10:05:46 2018 Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=a361a524-47eb-46c3-8a04-e5eaa65188c9 ro hugepages=103117 iommu=pt intel_iommu=on SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806012/+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] Update Released
The verification of the Stable Release Update for ufw has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Released Status in ufw source package in Cosmic: Fix Released 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] Re: Cannot insert IPV6 rule before IPV4 rules
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.10.1 --- ufw (0.36-0ubuntu0.18.10.1) cosmic-proposed; urgency=medium * Backport to cosmic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 20:46:10 + ** Changed in: ufw (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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 number for an IPV6 address is hard to determine. Proposed solution: either allow IPV6 rules to precede IPV4 rules, or implement a keyword defining the first available position; e.g. "ufw insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1". BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu 12.04.5 LTS, To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1368411] Update Released
The verification of the Stable Release Update for ufw has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Released Status in ufw source package in Cosmic: Fix Released 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 number for an IPV6 address is hard to determine. Proposed solution: either allow IPV6 rules to precede IPV4 rules, or implement a keyword defining the first available position; e.g. "ufw insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1". BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu 12.04.5 LTS, To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+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
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.10.1 --- ufw (0.36-0ubuntu0.18.10.1) cosmic-proposed; urgency=medium * Backport to cosmic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 20:46:10 + ** Changed in: ufw (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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 1204579] Re: ufw doesn't support concurrent updates
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.04.1 --- ufw (0.36-0ubuntu0.18.04.1) bionic-proposed; urgency=medium * Backport to bionic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 21:14:25 + ** Changed in: ufw (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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] Re: Cannot insert IPV6 rule before IPV4 rules
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.04.1 --- ufw (0.36-0ubuntu0.18.04.1) bionic-proposed; urgency=medium * Backport to bionic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 21:14:25 + ** Changed in: ufw (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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 number for an IPV6 address is hard to determine. Proposed solution: either allow IPV6 rules to precede IPV4 rules, or implement a keyword defining the first available position; e.g. "ufw insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1". BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu 12.04.5 LTS, To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1664133] Update Released
The verification of the Stable Release Update for ufw has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Released Status in ufw source package in Cosmic: Fix Released 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] Re: bash completion not working: uses deprecated have()
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.10.1 --- ufw (0.36-0ubuntu0.18.10.1) cosmic-proposed; urgency=medium * Backport to cosmic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 20:46:10 + ** Changed in: ufw (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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 1664133] Re: ipv6 multicast pings don't return
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.10.1 --- ufw (0.36-0ubuntu0.18.10.1) cosmic-proposed; urgency=medium * Backport to cosmic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 20:46:10 + ** Changed in: ufw (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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 1811129] Re: update ufw to 0.36
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.04.1 --- ufw (0.36-0ubuntu0.18.04.1) bionic-proposed; urgency=medium * Backport to bionic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 21:14:25 + ** Changed in: ufw (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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 1719211] Update Released
The verification of the Stable Release Update for ufw has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Released Status in ufw source package in Cosmic: Fix Released 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] Re: Bad interface name
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.10.1 --- ufw (0.36-0ubuntu0.18.10.1) cosmic-proposed; urgency=medium * Backport to cosmic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 20:46:10 + ** Changed in: ufw (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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] Re: Bad interface name
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.04.1 --- ufw (0.36-0ubuntu0.18.04.1) bionic-proposed; urgency=medium * Backport to bionic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 21:14:25 + ** Changed in: ufw (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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 1664133] Re: ipv6 multicast pings don't return
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.04.1 --- ufw (0.36-0ubuntu0.18.04.1) bionic-proposed; urgency=medium * Backport to bionic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 21:14:25 + ** Changed in: ufw (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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] Update Released
The verification of the Stable Release Update for ufw has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Released Status in ufw source package in Cosmic: Fix Released 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 1775043] Re: bash completion not working: uses deprecated have()
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.04.1 --- ufw (0.36-0ubuntu0.18.04.1) bionic-proposed; urgency=medium * Backport to bionic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 21:14:25 + ** Changed in: ufw (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.10.1 --- ufw (0.36-0ubuntu0.18.10.1) cosmic-proposed; urgency=medium * Backport to cosmic addressing the following SRU bugs: - LP: #1811129 - master SRU bug - LP: #1664133 - before6.rules: echo-reply needs to be before INVALID - LP: #1719211 - improve interface name checks - LP: #1775043 - shell-completion/bash: adjust for modern bash - LP: #1204579 - support concurrent updates - LP: #1368411 - add 'prepend' command -- Jamie Strandboge Mon, 25 Mar 2019 20:46:10 + ** Changed in: ufw (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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 Released Status in ufw source package in Cosmic: Fix Released 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 1811129] Update Released
The verification of the Stable Release Update for ufw has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 Released Status in ufw source package in Cosmic: Fix Released 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 1642514] Re: sched: Match-all classifier is missing in xenial
iproute2 is handled by the kernel team nowadays, due to its close ties with the kernel itself. Unsubscribing ubuntu-server for that reason. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1642514 Title: sched: Match-all classifier is missing in xenial Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: New Status in linux source package in Xenial: Fix Released Bug description: This is implemented in linux v4.8 by the following upstream patch: bf3994d2ed31 ("net/sched: introduce Match-all classifier") http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31 The backport is straightforward. It's useful in combination with clsact qdisc (see bug #1642510). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
What about Cosmic? Has anyone actually checked that the packages still work on Cosmic? -- 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: Fix Committed Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: 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 19.04. 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 1791405] Re: bluetooth always in discoverable mode (security issue)
@Daniel, the urls Bastien shared on the redhat bug are for bluez, he states on the gitlab bug that it's the proper fix where the gnome- bluetooth are improvements for new features to work better -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1791405 Title: bluetooth always in discoverable mode (security issue) Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: Fix Released Status in bluez source package in Bionic: New Status in gnome-bluetooth source package in Bionic: Fix Released Status in bluez source package in Cosmic: New Status in gnome-bluetooth source package in Cosmic: Fix Released Status in bluez source package in Disco: New Status in gnome-bluetooth source package in Disco: Fix Released Status in bluez source package in EE-Series: Fix Committed Status in gnome-bluetooth package in Fedora: Confirmed Bug description: Excerpt from a similar report (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) : Opening the Bluetooth settings will make the device discoverable again, but does not make the device undiscoverable after the settings are closed (this is not intended behavior; devices should only be discoverable when the bluetooth settings UI is open). There seem to be a merge request : https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1 Could you please merge it asap, it should be treated as a security issue IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1791405/+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 1823007] [NEW] [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all
Public bug reported: Please this is the same bug i reported before in the fresh install 18.04 lts xubuntu 18.04 partition, with internal gpu (apu a8 5500) enabled with hdmi audio but always analog output does not work. Attached to the previous. Does anyone fix this? 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 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 14:58:53 2019 InstallationDate: Installed on 2019-03-31 (3 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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_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. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1823007 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: New Bug description: Please this is the same bug i reported before in the fresh install 18.04 lts xubuntu 18.04 partition, with internal gpu (apu a8 5500) enabled with hdmi audio but always analog output does not work. Attached to the previous. Does anyone fix this? 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 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 14:58:53 2019 InstallationDate: Installed on 2019-03-31 (3 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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_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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1823007/+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 294830] Re: libpcsclite.so versions >1.4.99 and <1.8.25 causes crash of firefox/chrome
Jalakas, please install the package libpcsclite1-dbg and generate a new backtrace. I suspect a bug in the proprietary PKCS#11 library /usr/local/AWP/lib/libOcsCryptoki.so -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/294830 Title: libpcsclite.so versions >1.4.99 and <1.8.25 causes crash of firefox/chrome Status in pcsc-lite package in Ubuntu: Fix Committed Bug description: pcscd with version after 1.4.99 causes crash of firefox if smart card reader is not inserted, and in result firefox can not start in Ubuntu 8.10 package pcscd 1.4.102-1u is not good, i recommend to rollback to 1.4.99 or older version of pcscd this issue is not only in Ubuntu, it persist in Slackware too configuration - reader Omnikey 6121 with smart card Siemens HiPath SIcurity card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/294830/+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 1822898] Re: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i
** Changed in: openssl (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822898 Title: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i Status in openssl package in Ubuntu: Fix Committed Status in openssl source package in Cosmic: New Status in openssl source package in Disco: Fix Committed Status in openssl package in Debian: New Bug description: [Impact] * fetch-url cannot use https protocol (no https preseeds) [Test case] * in d-i, mini.iso, tty try wget https://geoip.ubuntu.com/lookup it should succeed. [Solution] The required openssl.cnf configuration file is missing, needs to simply exists, even if it is empty. [Regression Potential] well, if one cannot download over https / init ssl library in d-i, it's hard to get openssl busted more than that. No code changes on the .deb side of things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822898/+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
** Tags added: id-5ca3e96ad9917b50d663113d -- 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: In Progress Status in util-linux package in Ubuntu: In Progress Bug description: [IMPACT] In xenial lscpu prints the wrong "Hypervisor vendor" and "Virtualization type" on PowerVM or KVM systems. Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC. [TEST] Curent output: ubuntu@P8lpar3:~$ dpkg -l "*util-linux*" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii util-linux 2.31.1-0.4ub ppc64el miscellaneous system utilities un util-linux-loc (no description available) ubuntu@P8lpar3:~$ lscpu Architecture:ppc64le Byte Order: Little Endian CPU(s): 128 On-line CPU(s) list: 0-127 Thread(s) per core: 8 Core(s) per socket: 1 Socket(s): 16 NUMA node(s):2 Model: 2.1 (pvr 004b 0201) Model name: POWER8 (architected), altivec supported Hypervisor vendor: pHyp Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): NUMA node4 CPU(s): 0-127 ubuntu@P8lpar3:~$ Expected Output: $ lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):128 On-line CPU(s) list: 0-127 Thread(s) per core:8 Core(s) per socket:1 Socket(s): 16 NUMA node(s): 2 Model: 2.1 (pvr 004b 0201) Model name:POWER8 (architected), altivec supported Hypervisor vendor: pHyp Virtualization type: para L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): NUMA node4 CPU(s): 0-127 [Potential Regression] The fix changes the logic to how lscpu-dmi returns from read_hypervisor_dmi() this could introduce potential regression in platforms that has incorrect DMI information. [Other Info] ---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 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
Thank you Daniel, we will most likely keep Disco as-is for now and merge this in 19.10 where then mesa can drop the revert. I tagged it for 19.10 to be revisited. ** Tags added: qemu-19.10 ** Also affects: mesa (Ubuntu Ee-series) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Ee-series) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Ee-series) Status: New => Triaged ** Changed in: qemu (Ubuntu) Status: Triaged => Won't Fix ** Changed in: qemu (Ubuntu) Status: Won't Fix => Invalid ** Changed in: mesa (Ubuntu Ee-series) Status: New => Triaged ** Changed in: qemu (Ubuntu Ee-series) Assignee: (unassigned) => Christian Ehrhardt (paelzer) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Confirmed Status in QEMU: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Invalid Status in mesa source package in Disco: Fix Released Status in mesa source package in EE-Series: Triaged Status in qemu source package in EE-Series: Triaged Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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