[Touch-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen flashes
*** This bug is a duplicate of bug 1826125 *** https://bugs.launchpad.net/bugs/1826125 I have some doubt that this is a duplicate of bug 1826125, though I see how they are similar. I'm experiencing the same issue described in this bug, and the visual effect is quite different than the photos and videos attached to the other bug. In the other one, the issue appears to involve different parts of the display flickering around, or different parts of the screen getting "out of sync" so it looks like there are horizontal bands. The problem in the other bug is also described as quite frequent/constant. I'm not experiencing any of that, but I am experiencing what Daniel C describes in this bug: my entire screen flashes quite brightly for a split second, then calms back down. The effect is uniform across the screen, there's no banding or shifting that I can see. It only happens once every few minutes, not constantly as described in the other bug. The flashing is most noticeable when the "Night Light" effect is active in the evening, though I believe I've also seen it happen during the day. One other important distinction: like Daniel C, I have an XPS 9380 with the non-touch 1080p display, and I wiped Dell's pre-installed 18.04 and installed 19.04 instead. The other bug has several references in the comments to it affecting the XPS 9380 with the "4k" display. So I believe the flashing described in this bug is a different problem with a different panel. -- 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/1827790 Title: Dell XPS 13 9380 - Screen flashes Status in xorg package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827790/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1833801] [NEW] initctl: invalid command: rotate
Public bug reported: rsyslog 8.16.0-1ubuntu3.1 , Ubuntu 16.04.6 LTS the logrotate for rsyslog is a bit awry. The /etc/logrotate.d/rsyslog has this in the postrotate block: /usr/lib/rsyslog/rsyslog-rotate But when invoked (either by logrotate or manually) I get: initctl: invalid command: rotate Try `initctl --help' for more information. invoke-rc.d: initscript rsyslog, action "rotate" failed. The workaround is to change the postrotate block to what I saw in a much earlier version: postrotate service rsyslog rotate > /dev/null endscript ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsyslog 8.16.0-1ubuntu3.1 Uname: Linux 2.6.32-042stab127.2 x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Jun 22 00:24:52 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: Upgraded to xenial on 2016-06-15 (1101 days ago) mtime.conffile..etc.logrotate.d.rsyslog: 2019-06-22T00:24:05.675752 ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1833801 Title: initctl: invalid command: rotate Status in rsyslog package in Ubuntu: New Bug description: rsyslog 8.16.0-1ubuntu3.1 , Ubuntu 16.04.6 LTS the logrotate for rsyslog is a bit awry. The /etc/logrotate.d/rsyslog has this in the postrotate block: /usr/lib/rsyslog/rsyslog-rotate But when invoked (either by logrotate or manually) I get: initctl: invalid command: rotate Try `initctl --help' for more information. invoke-rc.d: initscript rsyslog, action "rotate" failed. The workaround is to change the postrotate block to what I saw in a much earlier version: postrotate service rsyslog rotate > /dev/null endscript ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rsyslog 8.16.0-1ubuntu3.1 Uname: Linux 2.6.32-042stab127.2 x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Jun 22 00:24:52 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: Upgraded to xenial on 2016-06-15 (1101 days ago) mtime.conffile..etc.logrotate.d.rsyslog: 2019-06-22T00:24:05.675752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1833801/+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 1811706] Re: eval: en: not found
[Expired for console-setup (Ubuntu) because there has been no activity for 60 days.] ** Changed in: console-setup (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1811706 Title: eval: en: not found Status in console-setup package in Ubuntu: Expired Bug description: I tried to create a minimal Ubuntu bionic arm64 installation using debootstrap that I would use to create a bootable Kubuntu 18.04 image for the Pi 3, but debootstrap seems to fail to configure keyboard- configuration, and therefore fails to install the Ubuntu base. Looking into the debootstrap logs, I get the error "eval: en: not found". I've searched Google for solutions but found nothing relevant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1811706/+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 1825739] Re: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1825739 Title: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: I can hear songs okay with my speaker in laptop, but when i connect headphone in to 3.5mm jack in laptop I hear songs with crackling sound. I'm dual booting with windows. My headphones works fine in windows 10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: devin 1493 F pulseaudio /dev/snd/controlC1: devin 1493 F pulseaudio /dev/snd/pcmC1D0c: devin 1493 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 23:45:51 2019 InstallationDate: Installed on 2019-04-21 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LJ.602 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LJ.602:bd05/06/2016:svnASUSTeKCOMPUTERINC.:pnX555LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LJ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1825739/+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 1825739] Re: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1825739 Title: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: I can hear songs okay with my speaker in laptop, but when i connect headphone in to 3.5mm jack in laptop I hear songs with crackling sound. I'm dual booting with windows. My headphones works fine in windows 10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: devin 1493 F pulseaudio /dev/snd/controlC1: devin 1493 F pulseaudio /dev/snd/pcmC1D0c: devin 1493 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 23:45:51 2019 InstallationDate: Installed on 2019-04-21 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [X555LJ, Realtek ALC3236, Black Headphone Out, Right] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LJ.602 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LJ.602:bd05/06/2016:svnASUSTeKCOMPUTERINC.:pnX555LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LJ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1825739/+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 1825761] Re: package systemd:i386 229-4ubuntu21.21 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1825761 Title: package systemd:i386 229-4ubuntu21.21 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 Status in systemd package in Ubuntu: Expired Bug description: Crossgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd:i386 229-4ubuntu21.21 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 21 05:37:04 2019 DpkgTerminalLog: Desinstalando systemd:i386 (229-4ubuntu21.21) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error al procesar el paquete systemd:i386 (--remove): el subproceso instalado el script pre-removal devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 InstallationDate: Installed on 2015-03-04 (1509 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: systemd Title: package systemd:i386 229-4ubuntu21.21 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825761/+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 1833652] Re: [SB-XFi - Creative X-Fi, playback] No sound at all
Made sure everything is on/not muted and still no sound. Also tried under a live session of Ubuntu 16.04 which detected the card, but still came up with no sound. -- 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/1833652 Title: [SB-XFi - Creative X-Fi, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Installed a new X-Fi sound card, but no audio is being heard during playback on Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/controlC1: jfilingeri 1723 F pulseaudio CurrentDesktop: MATE Date: Thu Jun 20 23:32:37 2019 InstallationDate: Installed on 2019-06-18 (3 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed Symptom_Card: Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] - HDA ATI HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/pcmC0D0p: jfilingeri 1723 F...m pulseaudio /dev/snd/controlC1: jfilingeri 1723 F pulseaudio Symptom_Type: No sound at all Title: [SB-XFi - Creative X-Fi, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170M-D3H-CF 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: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd09/08/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170M-D3H-CF:rvrx.x: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.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833652/+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 1833793] Re: Updating to 19.04 audio keeps clicking when it should be silent
** Package changed: ubuntu => alsa-driver (Ubuntu) ** Summary changed: - Updating to 19.04 audio keeps clicking when it should be silent + Updating to 19.04 audio keeps clicking when nothing is playing audio ** Description changed: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: - Audio output starts clicking every second incredibly annoyingly and loud. + Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: - I heard the click twice during boot and then it worked properly (without clicking all the time) + I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent the time) ** Description changed: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: - I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent the time) + I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in alsa-driver package in Ubuntu: New Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833793/+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 1833793] [NEW] Updating to 19.04 audio keeps clicking when it should be silent
You have been subscribed to a public bug: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking all the time) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: audio bot-comment -- Updating to 19.04 audio keeps clicking when it should be silent https://bugs.launchpad.net/bugs/1833793 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 1833795] [NEW] unable to report an 18.04 crash from a 19.04 system
Public bug reported: I had a distribution upgrade crash when I was trying to upgrade from 18.04 to 19.10 and a .crash was generated. I didn't want to report it from the system which crashed so I ran apport (to do the data collection) and saved the information in the report. I then copied it over to another system which is running Ubuntu 19.04 and I could not report the crash as I received the following crash. $ ubuntu-bug tmp/_usr_bin_do-release-upgrade.0.crash Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 597, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 704, in run_argv self.run_crash(self.options.crash_file, False) File "/usr/lib/python3/dist-packages/apport/ui.py", line 291, in run_crash if not self.report and not self.load_report(report_file): File "/usr/lib/python3/dist-packages/apport/ui.py", line 1375, in load_report self.report.load(f, binary='compressed') File "/usr/lib/python3/dist-packages/problem_report.py", line 144, in load block = base64.b64decode(line) File "/usr/lib/python3.7/base64.py", line 87, in b64decode return binascii.a2b_base64(s) binascii.Error: Incorrect padding I've attached the problematic crash file, although I don't really think it is the crash file that is the issue. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: disco ** Attachment added: "_usr_bin_do-release-upgrade.0.crash" https://bugs.launchpad.net/bugs/1833795/+attachment/5272236/+files/_usr_bin_do-release-upgrade.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1833795 Title: unable to report an 18.04 crash from a 19.04 system Status in apport package in Ubuntu: New Bug description: I had a distribution upgrade crash when I was trying to upgrade from 18.04 to 19.10 and a .crash was generated. I didn't want to report it from the system which crashed so I ran apport (to do the data collection) and saved the information in the report. I then copied it over to another system which is running Ubuntu 19.04 and I could not report the crash as I received the following crash. $ ubuntu-bug tmp/_usr_bin_do-release-upgrade.0.crash Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 597, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 704, in run_argv self.run_crash(self.options.crash_file, False) File "/usr/lib/python3/dist-packages/apport/ui.py", line 291, in run_crash if not self.report and not self.load_report(report_file): File "/usr/lib/python3/dist-packages/apport/ui.py", line 1375, in load_report self.report.load(f, binary='compressed') File "/usr/lib/python3/dist-packages/problem_report.py", line 144, in load block = base64.b64decode(line) File "/usr/lib/python3.7/base64.py", line 87, in b64decode return binascii.a2b_base64(s) binascii.Error: Incorrect padding I've attached the problematic crash file, although I don't really think it is the crash file that is the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1833795/+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 1833795] Re: unable to report an 18.04 crash from a 19.04 system
I was able to workaround the issue by modifying problem_report.py: --- problem_report.py 2018-09-17 01:06:20.394711000 -0700 +++ /usr/lib/python3/dist-packages/problem_report.py2019-06-21 11:40:49.235500124 -0700 @@ -140,7 +140,7 @@ class ProblemReport(UserDict): continue assert (key is not None and value is not None) if b64_block: -block = base64.b64decode(line) +block = base64.b64decode(line + b"===") if bd: value += bd.decompress(block) else: ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1833795 Title: unable to report an 18.04 crash from a 19.04 system Status in apport package in Ubuntu: New Bug description: I had a distribution upgrade crash when I was trying to upgrade from 18.04 to 19.10 and a .crash was generated. I didn't want to report it from the system which crashed so I ran apport (to do the data collection) and saved the information in the report. I then copied it over to another system which is running Ubuntu 19.04 and I could not report the crash as I received the following crash. $ ubuntu-bug tmp/_usr_bin_do-release-upgrade.0.crash Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 597, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 704, in run_argv self.run_crash(self.options.crash_file, False) File "/usr/lib/python3/dist-packages/apport/ui.py", line 291, in run_crash if not self.report and not self.load_report(report_file): File "/usr/lib/python3/dist-packages/apport/ui.py", line 1375, in load_report self.report.load(f, binary='compressed') File "/usr/lib/python3/dist-packages/problem_report.py", line 144, in load block = base64.b64decode(line) File "/usr/lib/python3.7/base64.py", line 87, in b64decode return binascii.a2b_base64(s) binascii.Error: Incorrect padding I've attached the problematic crash file, although I don't really think it is the crash file that is the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1833795/+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 1831296] Re: __main__.SeccompTest is failing on Ubuntu CI
** Tags added: ddstreet-next systemd -- 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/1831296 Title: __main__.SeccompTest is failing on Ubuntu CI Status in systemd package in Ubuntu: In Progress Status in systemd source package in Eoan: In Progress Bug description: Since https://github.com/systemd/systemd/pull/12430 was merged and libsecomp was updated the test has been failing on Ubuntu CI: https://github.com/systemd/systemd/issues/12709. By analogy with https://github.com/systemd/systemd/pull/12430/commits/c3ab2c389ee60d92fb8d7fe779ae9c4e3c092e4c, the test should look for either "killed" or "dumped". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/+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 1831296] Re: __main__.SeccompTest is failing on Ubuntu CI
https://salsa.debian.org/systemd-team/systemd/merge_requests/33 ** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Eoan) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Eoan) Status: New => In Progress -- 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/1831296 Title: __main__.SeccompTest is failing on Ubuntu CI Status in systemd package in Ubuntu: In Progress Status in systemd source package in Eoan: In Progress Bug description: Since https://github.com/systemd/systemd/pull/12430 was merged and libsecomp was updated the test has been failing on Ubuntu CI: https://github.com/systemd/systemd/issues/12709. By analogy with https://github.com/systemd/systemd/pull/12430/commits/c3ab2c389ee60d92fb8d7fe779ae9c4e3c092e4c, the test should look for either "killed" or "dumped". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/+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 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
manpage patches for SRU releases are in git here: https://code.launchpad.net/~ddstreet/ubuntu/+source/sudo/+git/sudo and builds here: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1556302 As this is a manpage-only SRU, it's likely to be rejected if uploaded by itself; if anyone has any bugfix to apply to sudo in the future, please consider including the manpage patches from this bug as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: In Progress Status in sudo source package in Bionic: In Progress Status in sudo source package in Cosmic: In Progress Status in sudo source package in Disco: In Progress Status in sudo source package in Eoan: Fix Released Bug description: [impact] sudo does not set HOME to the target user's HOME [test case] ddstreet@thorin:~$ sudo printenv | grep HOME HOME=/home/ddstreet [regression potential] this is a significant behavior change. As mentioned in comment 11 (and later, and other bugs duped to this, and the mailing list discussion, etc) users of Ubuntu so far have been used to running sudo with their own HOME set, not root's HOME. Therefore, it's inappropriate to change this behavior for existing releases; this should be changed starting in Eoan, and only the sudo and sudoers man pages changed in previous releases to indicate the actual behavior of sudo in those releases. [other info] Shortly after upstream changed the behavior, the patch to keep HOME as the calling (instead of target) user was added in bug 760140. For quick reference to anyone coming to this bug, the pre-19.10 behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home or, run sudo with the -H param. -- original description: -- I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+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 1833758] [NEW] lvm2: vgcfgbackup in postinst takes several minutes
Public bug reported: The postinst for lvm2 includes a call to vgcfgbackup; in the version included in eoan 2.03.02-2ubuntu4 (and 2.03.02-2ubuntu3 before it), this command takes several minutes to run when invoked in an schroot as happens when a building a package with sbuild that ends up pulling lvm2 as part of its build dependency chain. An example package with lvm2 in its build depends is rsnapshot, but this behavior was seen with a build of glibc. Some notes: - this behavior is NOT seen with the version of lvm2 in disco. - this happens in bionic with a 4.15 kernel and disco with a 5.0 kernel (different hosts, so different sets of block devices) - this happens regardless of whether the host is currently using logical volumes or not Here's the time difference between running the disco version and the eoan version: (disco-amd64)root@HOSTNAME:~# time vgcfgbackup WARNING: Failed to connect to lvmetad. Falling back to device scanning. real0m0.204s user0m0.014s sys 0m0.010s (eoan-amd64)root@HOSTNAME:~# time vgcfgbackup WARNING: Device /dev/sda not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sda3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb2 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdb3 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdc1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sdd1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde1 not initialized in udev database even after waiting 1000 microseconds. WARNING: Device /dev/sde2 not initialized in udev database even after waiting 1000 microseconds. real4m11.405s user0m0.470s sys 0m0.576s /proc/mounts in the schroot: (eoan-amd64)root@HOSTNAME:~# cat /proc/mounts eoan-amd64 / overlay rw,relatime,lowerdir=/var/lib/schroot/union/underlay/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34,upperdir=/srv/devel/schroot-overlays/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34/upper,workdir=/srv/devel/schroot-overlays/eoan-amd64-29c7f791-9409-4505-9192-7c4685b8be34/work 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,nosuid,relatime,size=10197712k,nr_inodes=2549428,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 /dev/sda2 /home ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 /dev/sda2 /tmp ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 tmpfs /run/shm tmpfs rw,relatime 0 0 /dev/sda2 /scratch ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 /dev/sdc1 /srv/work ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 strace of vgcfgbackup is attached ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: eoan ** Attachment added: "strace of running vgcfgbackup in an eoan schroot" https://bugs.launchpad.net/bugs/1833758/+attachment/5272220/+files/vgcfgbackup-eoan.strace -- You received this
[Touch-packages] [Bug 1833757] [NEW] PCI/internal sound card not detected
Public bug reported: no audio ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-151.178-generic 4.4.179 Uname: Linux 4.4.0-151-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Jun 22 01:16:52 2019 InstallationDate: Installed on 2019-05-25 (27 days ago) InstallationMedia: It PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to xenial on 2019-05-30 (22 days ago) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 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 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1833757 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: no audio ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-151.178-generic 4.4.179 Uname: Linux 4.4.0-151-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Jun 22 01:16:52 2019 InstallationDate: Installed on 2019-05-25 (27 days ago) InstallationMedia: It PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to xenial on 2019-05-30 (22 days ago) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 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 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833757/+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 1782535] Re: cifs - poor upload speed with nautilus compared to rsync
** Changed in: glib Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1782535 Title: cifs - poor upload speed with nautilus compared to rsync Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Bug description: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1782535/+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 1579978] Re: upgrade to 1:7.2p2-4ubuntu1 fails on ubuntu server
For me, the root cause of this was systemd's inability to create temporary files. I would get a ton of messages similar to "Unsafe symlinks encountered in /var/run/sshd, refusing." in the systemd log, By changing my system root directory (i.e. /) to be owned by root, it fixed all these problems, included the resultant sshd problem. Previously / was owned by my user and group somehow. -- 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/1579978 Title: upgrade to 1:7.2p2-4ubuntu1 fails on ubuntu server Status in openssh package in Ubuntu: Confirmed Bug description: This package upgrade failure has occurred on multiple machines, with the same error on each machine. All affected machines are running Upstart (upstart-sysv) as /sbin/init. The package installed/updated successfully on a machine running Systemd (systemd-sysv) as /sbin/init. $ sudo apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-image-4.2.0-35-generic linux-image-extra-4.2.0-35-generic Use 'sudo apt autoremove' to remove them. 0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up openssh-server (1:7.2p2-4ubuntu1) ... start: Job failed to start invoke-rc.d: initscript ssh, action "restart" failed. dpkg: error processing package openssh-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue May 10 11:51:58 2016 InstallationDate: Installed on 2015-09-04 (249 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: openssh UpgradeStatus: Upgraded to xenial on 2016-05-04 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1579978/+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 1833749] [NEW] unfocused terminal window blinking because of transparency unreasonably changing
Public bug reported: unfocused terminal window blinking because of transparency unreasonably changing without any action on keyboard nor mouse ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-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-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 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: Fri Jun 21 20:01:45 2019 DistUpgraded: 2019-04-19 17:34:11,213 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-16-generic, x86_64: installed nvidia, 418.56, 5.0.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-17-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230] InstallationDate: Installed on 2018-04-27 (420 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20EN0008XS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic root=UUID=9ba5bcf6-c098-48cd-b443-cbb9ab3b0f03 ro quiet splash acpi_sleep=nonvs vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-19 (63 days ago) dmi.bios.date: 02/21/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET83W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN0008XS dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EN0008XS:pvrThinkPadP50:rvnLENOVO:rn20EN0008XS:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EN0008XS dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ubuntu ** Attachment added: "terminal-transparency-unreasonably-changing" https://bugs.launchpad.net/bugs/1833749/+attachment/5272172/+files/terminal-transparency-unreasonably-changing.mp4 -- 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/1833749 Title: unfocused terminal window blinking because of transparency unreasonably changing Status in xorg package in Ubuntu: New Bug description: unfocused terminal window blinking because of transparency unreasonably changing without any action on keyboard nor mouse ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-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-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 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: Fri Jun 21 20:01:45 2019
[Touch-packages] [Bug 1833476] Re: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests
Another thing to mention is that the new failures are all due to the same error as in the previous comment. It seems like the failing tests all expect the session to be reused, and fails. -- 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/1833476 Title: libssl1.1 version 1.1.1-1ubuntu2.1~18.04.2 breaks nginx ssl tests Status in nginx package in Ubuntu: Incomplete Status in openssl package in Ubuntu: New Bug description: Many nginx ssl tests pass with libssl1.1 version 1.1.0g-2ubuntu4.3 but fail when libssl1.1 is updated to version 1.1.1-1ubuntu2.1~18.04.2. Repro steps: 1. Create control Dockerfile: == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.0g-2ubuntu4.3 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 2. Run the command in a directory with only the Dockerfile: docker build -t nginx_image . && docker run --rm -it nginx_image 3. See output: == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=346, Tests=3782, 317 wallclock secs ( 1.87 usr 0.78 sys + 35.84 cusr 16.99 csys = 55.48 CPU) Result: FAIL == 4. Create new Dockerfile (only difference is updating libssl1.1): == FROM ubuntu:18.04 RUN apt-get update -y && \ apt-get upgrade -y && \ apt-get install -y git nginx-core xdg-utils openssl=1.1.0g-2ubuntu4.3 libnet-ssleay-perl=1.84-1build1 libio-socket-ssl-perl=2.056-1 libssl1.1=1.1.1-1ubuntu2.1~18.04.2 RUN git clone https://github.com/nginx/nginx-tests.git WORKDIR /nginx-tests ENV TEST_NGINX_BINARY=/usr/sbin/nginx ENV TEST_NGINX_MODULES=/usr/lib/nginx/modules USER www-data ENTRYPOINT ["prove", "."] == 5. See output == Test Summary Report --- ./grpc_request_buffering.t (Wstat: 512 Tests: 14 Failed: 2) Failed tests: 11-12 Non-zero exit status: 2 ./h2_server_tokens.t (Wstat: 1536 Tests: 14 Failed: 6) Failed tests: 1-2, 7-8, 10-11 Non-zero exit status: 6 ./mail_ssl.t (Wstat: 768 Tests: 22 Failed: 3) Failed tests: 3, 5-6 Non-zero exit status: 3 ./proxy_ssl.t(Wstat: 512 Tests: 9 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_proxy_ssl.t (Wstat: 512 Tests: 8 Failed: 2) Failed tests: 4-5 Non-zero exit status: 2 ./stream_ssl.t (Wstat: 768 Tests: 9 Failed: 3) Failed tests: 2, 4-5 Non-zero exit status: 3 ./stream_upstream_zone_ssl.t (Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 ./upstream_ip_hash_ipv6.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output ./upstream_zone_ssl.t(Wstat: 768 Tests: 11 Failed: 3) Failed tests: 4-5, 9 Non-zero exit status: 3 Files=346, Tests=3764, 317 wallclock secs ( 2.00 usr 0.73 sys + 36.49 cusr 16.91 csys = 56.13 CPU) Result: FAIL == New failures: mail_ssl.t, proxy_ssl.t, stream_proxy_ssl.t, stream_ssl.t, stream_upstream_zone_ssl.t, upstream_zone_ssl.t. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1833476/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
On 2019-06-21 15:59, Mathieu Trudel-Lapierre wrote: > Looks like noto sources now have the right glyphs (since their April > 9 release, actually). Right. There are 2 months old merge requests in Debian to get them in: https://salsa.debian.org/fonts-team/fonts-noto-cjk/merge_requests But nobody has reacted to those requests yet AFAIK. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in Poppler: New Status in fonts-noto-cjk package in Ubuntu: New Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: Fix Released Status in libreoffice-l10n source package in Xenial: Fix Released Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Released Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a
[Touch-packages] [Bug 1833742] Re: package linux-image-4.18.0-22-generic 4.18.0-22.23 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- 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/1833742 Title: package linux-image-4.18.0-22-generic 4.18.0-22.23 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I don't know much ProblemType: Package DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mohitatray 3547 F pulseaudio Date: Fri Jun 21 22:20:32 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2 InstallationDate: Installed on 2018-08-16 (309 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 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-br0xx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=0dc8b444-0cea-4736-8ec3-6fb7b8a78437 ro resume=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2 quiet splash resume=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2 vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3 RelatedPackageVersions: grub-pc 2.02+dfsg1-5ubuntu8.3 SourcePackage: initramfs-tools Title: package linux-image-4.18.0-22-generic 4.18.0-22.23 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.37 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd07/04/2017:svnHP:pnHPLaptop15g-br0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.37:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15g-br0xx dmi.product.sku: 2JR17PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1833742/+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 1833536] Re: QuiteRSS crashes intermittently
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1833536 Title: QuiteRSS crashes intermittently Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in qtbase-opensource-src source package in Bionic: Confirmed Bug description: [Impact] This bug affects QuiteRSS and other Qt applications, like plasma-discover (see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 1814375). All they crash with similar stack traces. [Test Case] 1. Open QuiteRSS. 2. Leave it running for several hours. 3. It should not crash. [Proposed Fix] The proposed fix is a backport of the following commit from upstream 5.12 branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db [Regression Potential] This patch adds an additional check before re-sending the request. Regressions chance is minimal, but the potential regressions may be that the request is not re-sent where it was re-sent with the previous code. [Original Description] After opening QuiteRSS it will run until crash happens. This happens intermittently within the hour usually. (gdb) bt #0 QHttpNetworkConnectionChannel::sendRequest (this=) at access/qhttpnetworkconnectionchannel.cpp:238 #1 0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest ( this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015 #2 0x72736122 in QObject::event (this=0x7fff48da89b0, e=) at kernel/qobject.cpp:1247 #3 0x76f2482c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x727069a8 in QCoreApplication::notifyInternal2 ( receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0) at kernel/qcoreapplication.cpp:1024 #6 0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #7 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x7fff60008e90) at kernel/qcoreapplication.cpp:1699 #8 0x727096a8 in QCoreApplication::sendPostedEvents ( receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1553 #9 0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10) at kernel/qeventdispatcher_glib.cpp:276 #10 0x7fffece96317 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fffece96550 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fffece965dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7275f8ef in QEventDispatcherGlib::processEvents ( this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7252322a in QThread::exec (this=) at thread/qthread.cpp:515 #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20) at thread/qthread_unix.cpp:368 #17 0x722646db in start_thread (arg=0x7fff4700) at pthread_create.c:463 #18 0x719ec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1833742] [NEW] package linux-image-4.18.0-22-generic 4.18.0-22.23 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: I don't know much ProblemType: Package DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mohitatray 3547 F pulseaudio Date: Fri Jun 21 22:20:32 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2 InstallationDate: Installed on 2018-08-16 (309 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 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-br0xx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=0dc8b444-0cea-4736-8ec3-6fb7b8a78437 ro resume=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2 quiet splash resume=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2 vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3 RelatedPackageVersions: grub-pc 2.02+dfsg1-5ubuntu8.3 SourcePackage: initramfs-tools Title: package linux-image-4.18.0-22-generic 4.18.0-22.23 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.37 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd07/04/2017:svnHP:pnHPLaptop15g-br0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.37:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15g-br0xx dmi.product.sku: 2JR17PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1833742 Title: package linux-image-4.18.0-22-generic 4.18.0-22.23 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I don't know much ProblemType: Package DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-22-generic 4.18.0-22.23 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mohitatray 3547 F pulseaudio Date: Fri Jun 21 22:20:32 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2 InstallationDate: Installed on 2018-08-16 (309 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 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-br0xx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=0dc8b444-0cea-4736-8ec3-6fb7b8a78437 ro resume=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2 quiet splash resume=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2 vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3 RelatedPackageVersions: grub-pc 2.02+dfsg1-5ubuntu8.3 SourcePackage: initramfs-tools Title: package linux-image-4.18.0-22-generic 4.18.0-22.23 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Touch-packages] [Bug 1630137] Re: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive
Could either of you please run `sudo apt update` and attach the output from `apt show gstreamer1.0-vaapi` afterwards? It is hard to tell, but based on the screenshot it seems to consider an older version of gstreamer1.0-vaapi as the latest which cause problems when the dependencies find the newer versions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1630137 Title: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive Status in gstreamer1.0 package in Ubuntu: Expired Bug description: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive, so the consequence is that nobody can install package `gstreamer1.0-vaapi` now: $ sudo apt install gstreamer1.0-vaapi Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gstreamer1.0-vaapi : Depends: libgstreamer-plugins-bad1.0-0 (< 1.8.1) but 1.8.2-1ubuntu0.1 is to be installed E: Unable to correct problems, you have held broken packages. Tested in recently installed Ubuntu 16.04.1. The culprit seems to be in: $ apt-cache show gstreamer1.0-vaapi Package: gstreamer1.0-vaapi Priority: optional Section: universe/libs Installed-Size: 714 Maintainer: Ubuntu Developers Original-Maintainer: Maintainers of GStreamer packages Architecture: amd64 Source: gstreamer-vaapi Version: 1.8.0-1 Depends: libc6 (>= 2.14), libdrm2 (>= 2.3.1), libegl1-mesa (>= 7.8.1) | libegl1-x11, libgl1-mesa-glx | libgl1, libglib2.0-0 (>= 2.37.3), libgstreamer-plugins-bad1.0-0 (>= 1.8.0), libgstreamer-plugins-bad1.0-0 (<< 1.8.1), libgstreamer-plugins-base1.0-0 (>= 1.6.0), libgstreamer1.0-0 (>= 1.6.0), libudev1 (>= 183), libva-drm1 (>= 1.1.0), libva-wayland1 (>= 1.3.0), libva-x11-1 (>= 1.0.3), libva1 (>= 1.4.0), libwayland-client0 (>= 1.3.92), libx11-6, libxrandr2, libxrender1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1630137/+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 1630137] Re: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive
...oh, and the output from `apt policy gstreamer1.0-vaapi` as well? :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1630137 Title: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive Status in gstreamer1.0 package in Ubuntu: Expired Bug description: gstreamer1.0-vaapi depends on libgstreamer-plugins-bad1.0-0 (<< 1.8.1) but 1.8.2 is in the archive, so the consequence is that nobody can install package `gstreamer1.0-vaapi` now: $ sudo apt install gstreamer1.0-vaapi Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gstreamer1.0-vaapi : Depends: libgstreamer-plugins-bad1.0-0 (< 1.8.1) but 1.8.2-1ubuntu0.1 is to be installed E: Unable to correct problems, you have held broken packages. Tested in recently installed Ubuntu 16.04.1. The culprit seems to be in: $ apt-cache show gstreamer1.0-vaapi Package: gstreamer1.0-vaapi Priority: optional Section: universe/libs Installed-Size: 714 Maintainer: Ubuntu Developers Original-Maintainer: Maintainers of GStreamer packages Architecture: amd64 Source: gstreamer-vaapi Version: 1.8.0-1 Depends: libc6 (>= 2.14), libdrm2 (>= 2.3.1), libegl1-mesa (>= 7.8.1) | libegl1-x11, libgl1-mesa-glx | libgl1, libglib2.0-0 (>= 2.37.3), libgstreamer-plugins-bad1.0-0 (>= 1.8.0), libgstreamer-plugins-bad1.0-0 (<< 1.8.1), libgstreamer-plugins-base1.0-0 (>= 1.6.0), libgstreamer1.0-0 (>= 1.6.0), libudev1 (>= 183), libva-drm1 (>= 1.1.0), libva-wayland1 (>= 1.3.0), libva-x11-1 (>= 1.0.3), libva1 (>= 1.4.0), libwayland-client0 (>= 1.3.92), libx11-6, libxrandr2, libxrender1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1630137/+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 1833536] Re: QuiteRSS crashes intermittently
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtbase-opensource-src (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1833536 Title: QuiteRSS crashes intermittently Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in qtbase-opensource-src source package in Bionic: Confirmed Bug description: [Impact] This bug affects QuiteRSS and other Qt applications, like plasma-discover (see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 1814375). All they crash with similar stack traces. [Test Case] 1. Open QuiteRSS. 2. Leave it running for several hours. 3. It should not crash. [Proposed Fix] The proposed fix is a backport of the following commit from upstream 5.12 branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db [Regression Potential] This patch adds an additional check before re-sending the request. Regressions chance is minimal, but the potential regressions may be that the request is not re-sent where it was re-sent with the previous code. [Original Description] After opening QuiteRSS it will run until crash happens. This happens intermittently within the hour usually. (gdb) bt #0 QHttpNetworkConnectionChannel::sendRequest (this=) at access/qhttpnetworkconnectionchannel.cpp:238 #1 0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest ( this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015 #2 0x72736122 in QObject::event (this=0x7fff48da89b0, e=) at kernel/qobject.cpp:1247 #3 0x76f2482c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x727069a8 in QCoreApplication::notifyInternal2 ( receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0) at kernel/qcoreapplication.cpp:1024 #6 0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #7 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x7fff60008e90) at kernel/qcoreapplication.cpp:1699 #8 0x727096a8 in QCoreApplication::sendPostedEvents ( receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1553 #9 0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10) at kernel/qeventdispatcher_glib.cpp:276 #10 0x7fffece96317 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fffece96550 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fffece965dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7275f8ef in QEventDispatcherGlib::processEvents ( this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7252322a in QThread::exec (this=) at thread/qthread.cpp:515 #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20) at thread/qthread_unix.cpp:368 #17 0x722646db in start_thread (arg=0x7fff4700) at pthread_create.c:463 #18 0x719ec88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1833536/+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 1833536] Re: QuiteRSS crashes intermittently
** Description changed: - After opening QuiteRSS it will run until crash happens. This happens - intermittently within the hour usually. + [Impact] + This bug affects QuiteRSS and other Qt applications, like plasma-discover (see https://bugs.kde.org/show_bug.cgi?id=402848) and qbittorrent (see bug 1814375). All they crash with similar stack traces. + + [Test Case] + 1. Open QuiteRSS. + 2. Leave it running for several hours. + 3. It should not crash. + + [Proposed Fix] + The proposed fix is a backport of the following commit from upstream 5.12 branch: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=e431a3ac027915db + + [Regression Potential] + This patch adds an additional check before re-sending the request. Regressions chance is minimal, but the potential regressions may be that the request is not re-sent where it was re-sent with the previous code. + + [Original Description] + After opening QuiteRSS it will run until crash happens. This happens intermittently within the hour usually. (gdb) bt #0 QHttpNetworkConnectionChannel::sendRequest (this=) - at access/qhttpnetworkconnectionchannel.cpp:238 + at access/qhttpnetworkconnectionchannel.cpp:238 #1 0x730deca2 in QHttpNetworkConnectionPrivate::_q_startNextRequest ( - this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015 - #2 0x72736122 in QObject::event (this=0x7fff48da89b0, - e=) at kernel/qobject.cpp:1247 + this=0x7fff480d4a20) at access/qhttpnetworkconnection.cpp:1015 + #2 0x72736122 in QObject::event (this=0x7fff48da89b0, + e=) at kernel/qobject.cpp:1247 #3 0x76f2482c in QApplicationPrivate::notify_helper(QObject*, QEvent*) - () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 + () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x76f2c0f4 in QApplication::notify(QObject*, QEvent*) () -from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 + from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x727069a8 in QCoreApplication::notifyInternal2 ( - receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0) - at kernel/qcoreapplication.cpp:1024 - #6 0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0, - receiver=) - at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 - #7 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, - event_type=event_type@entry=0, data=0x7fff60008e90) - at kernel/qcoreapplication.cpp:1699 + receiver=0x7fff48da89b0, event=event@entry=0x7fff494233b0) + at kernel/qcoreapplication.cpp:1024 + #6 0x7270911d in QCoreApplication::sendEvent (event=0x7fff494233b0, + receiver=) + at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 + #7 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, + event_type=event_type@entry=0, data=0x7fff60008e90) + at kernel/qcoreapplication.cpp:1699 #8 0x727096a8 in QCoreApplication::sendPostedEvents ( - receiver=receiver@entry=0x0, event_type=event_type@entry=0) - at kernel/qcoreapplication.cpp:1553 + receiver=receiver@entry=0x0, event_type=event_type@entry=0) + at kernel/qcoreapplication.cpp:1553 #9 0x727602c3 in postEventSourceDispatch (s=0x7fff48003f10) - ---Type to continue, or q to quit--- - at kernel/qeventdispatcher_glib.cpp:276 + at kernel/qeventdispatcher_glib.cpp:276 #10 0x7fffece96317 in g_main_context_dispatch () -from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fffece96550 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fffece965dc in g_main_context_iteration () -from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7275f8ef in QEventDispatcherGlib::processEvents ( - this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 - #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60, - flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 + this=0x7fff48000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 + #14 0x727049ea in QEventLoop::exec (this=this@entry=0x7fff4fffec60, + flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7252322a in QThread::exec (this=) - at thread/qthread.cpp:515 + at thread/qthread.cpp:515 #16 0x7252816d in QThreadPrivate::start (arg=0x7fff60008a20) - at thread/qthread_unix.cpp:368 + at thread/qthread_unix.cpp:368 #17 0x722646db in start_thread (arg=0x7fff4700) - at pthread_create.c:463 + at pthread_create.c:463 #18 0x719ec88f in clone () - at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 + at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 ** Also affects: qtbase-opensource-src (Ubuntu Bionic) Importance: Undecided
[Touch-packages] [Bug 1832414] Re: Removing document files spam from cups
Dariusz, Till, could you have a look? That's reported as a potential regression from the xenial SRU ** Changed in: cups (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1832414 Title: Removing document files spam from cups Status in cups package in Ubuntu: New Bug description: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832414/+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 1782535] Re: cifs - poor upload speed with nautilus compared to rsync
Would still be good to backport to the LTS if we know what changed resolved the issue ** Changed in: glib2.0 (Ubuntu) Status: Triaged => Fix Released ** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #1688 https://gitlab.gnome.org/GNOME/glib/issues/1688 ** Also affects: glib via https://gitlab.gnome.org/GNOME/glib/issues/1688 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1782535 Title: cifs - poor upload speed with nautilus compared to rsync Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Fix Released Bug description: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1782535/+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 1832754] Re: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs.
Upstream discussion points to https://github.com/systemd/systemd/pull/8429 ** Summary changed: - ubuntu-bug systemd + "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. -- 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/1832754 Title: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. Status in systemd package in Ubuntu: New Bug description: I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. systemd: 237-3ubuntu10.22 It's this issue: https://github.com/systemd/systemd/issues/8155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1832754/+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 1832801] Re: disco: curl error while loading shared libraries: libssl.so.1.0.0
Thank you for your bug report, what's the output of $ ldd -r /usr/bin/curl ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832801 Title: disco: curl error while loading shared libraries: libssl.so.1.0.0 Status in curl package in Ubuntu: New Bug description: Linux 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:52:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux DISTRIB_RELEASE=19.04 DISTRIB_DESCRIPTION="Ubuntu 19.04" curl: Installed: 7.64.0-2ubuntu1.1 Candidate: 7.64.0-2ubuntu1.1 Version table: *** 7.64.0-2ubuntu1.1 1001 1001 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 1001 http://mirror.aarnet.edu.au/pub/ubuntu/archive disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.64.0-2ubuntu1 1001 1001 http://mirror.aarnet.edu.au/pub/ubuntu/archive disco/main amd64 Packages When I run curl, I get the following error: curl: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory On other disco machines I'm not experiencing this issue. I apt purged openssl/libssl/curl and re-installed, but the error persists. I'm sure my system has some issue, but I'm unable to figure it out, and this felt like a bug as curl was working before upgrade to disco. I tried proposed packages to see if openssl 1.1.1b-1ubuntu2.2 instead of 1.1.1b-1ubuntu2 would make any difference, but the error persists. me@mbp:/usr/lib/x86_64-linux-gnu$ curl curl: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory me@mbp:/usr/lib/x86_64-linux-gnu$ which curl /usr/bin/curl me@mbp:/usr/lib/x86_64-linux-gnu$ sudo dpkg -l | grep curl ii curl 7.64.0-2ubuntu1.1 amd64command line tool for transferring data with URL syntax ii libcurl3-gnutls:amd64 7.64.0-2ubuntu1.1 amd64easy-to-use client-side URL transfer library (GnuTLS flavour) ii libcurl4:amd64 7.64.0-2ubuntu1.1 amd64easy-to-use client-side URL transfer library (OpenSSL flavour) ii python3-pycurl 7.43.0.2-0.1 amd64Python bindings to libcurl (Python 3) me@mbp:/usr/lib/x86_64-linux-gnu$ sudo dpkg -l | grep ssl ii android-libboringssl8.1.0+r23-2 amd64Google's internal fork of OpenSSL for the Android SDK rc docbook-dsssl 1.79-9.1 all modular DocBook DSSSL stylesheets, for print and HTML ii libflac++6v5:amd64 1.3.2-3 amd64Free Lossless Audio Codec - C++ runtime library ii libflac8:amd64 1.3.2-3 amd64Free Lossless Audio Codec - runtime C library ii libflac8:i386 1.3.2-3 i386 Free Lossless Audio Codec - runtime C library ii libio-socket-ssl-perl 2.060-3 all Perl module implementing object oriented interface to SSL sockets ii libnet-smtp-ssl-perl1.04-1 all Perl module providing SSL support to Net::SMTP ii libnet-ssleay-perl 1.85-2ubuntu3 amd64Perl module for Secure Sockets Layer (SSL) ii libssl-dev:amd64 1.1.1b-1ubuntu2.2 amd64Secure Sockets Layer toolkit - development files ii libssl1.1:amd64 1.1.1b-1ubuntu2.2 amd64Secure Sockets Layer toolkit - shared libraries ii libssl1.1:i386 1.1.1b-1ubuntu2.2 i386 Secure Sockets Layer toolkit - shared libraries ii libwavpack1:amd64 5.1.0-5ubuntu0.1amd64audio codec (lossy and lossless) - library ii libwavpack1:i386 5.1.0-5ubuntu0.1i386 audio codec (lossy and lossless) - library ii libzstd1:amd64
[Touch-packages] [Bug 1832787] Re: fontconfig 2.12 in 18.04 causes firefox to freeze when launching chrome
Thank you for your bug report. The issue seems similar to https://bugzilla.mozilla.org/show_bug.cgi?id=1495900 ** Bug watch added: Mozilla Bugzilla #1495900 https://bugzilla.mozilla.org/show_bug.cgi?id=1495900 ** Changed in: fontconfig (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1832787 Title: fontconfig 2.12 in 18.04 causes firefox to freeze when launching chrome Status in fontconfig package in Ubuntu: New Bug description: fontconfig version: 2.12.6-0ubuntu2 Related: https://askubuntu.com/questions/1076412/firefox-freezing-with-100-cpu- usage-for-30-seconds-when-launching-chromium https://bugzilla.mozilla.org/show_bug.cgi?id=1495900 https://bugzilla.mozilla.org/show_bug.cgi?id=1411338 Steps to reproduce: 1) Launch firefox, open a few tabs 2) Launch chrome 3) Go back to firefox, and notice it starts being very slow, switching tabs do nothing (the content area remains blank). 4) Backport fontconfig 2.13 from cosmic to bionic 5) Try to reproduce 1-3, be happy because it is now working fine! I backported 2.13.0-5ubuntu3 from cosmic to bionic, if that helps. I don't have the right setup right now to do a bisect from upstream or from debian patches sadly. ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1832787/+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 1833231] Re: cups ftbfs in eoan (amd64 only)
Till, can you have a look to this one? ** Changed in: cups (Ubuntu) Importance: Undecided => High ** Changed in: cups (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1833231 Title: cups ftbfs in eoan (amd64 only) Status in cups package in Ubuntu: New Bug description: cups ftbfs in eoan (amd64 only) in a test rebuild: https://launchpadlibrarian.net/428250411/buildlog_ubuntu-eoan- amd64.cups_2.2.10-6ubuntu1_BUILDING.txt.gz E [14/Jun/2019:14:46:57.037970 +] Unknown default SystemGroup "lpadmin". PASS: 8 warning messages. PASS: 0 notice messages. PASS: 760 info messages. PASS: 24065 debug messages. PASS: 25573 debug2 messages. Copied log file "access_log-2019-06-14-buildd" to test directory. Copied log file "debug_log-2019-06-14-buildd" to test directory. Copied log file "error_log-2019-06-14-buildd" to test directory. Copied log file "page_log-2019-06-14-buildd" to test directory. Copied report file "cups-str-2019-06-14-buildd.html" to test directory. 1 tests failed. make[2]: *** [Makefile:257: check] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:201: override_dh_auto_test] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:17: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1833231/+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 1833440] Re: My University disabled NTLMv1 and Evolution won't let me authenticate to Exchange
*** This bug is a duplicate of bug 1817537 *** https://bugs.launchpad.net/bugs/1817537 ** This bug has been marked a duplicate of bug 1817537 libsoup should support ntlmv2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1833440 Title: My University disabled NTLMv1 and Evolution won't let me authenticate to Exchange Status in libsoup2.4 package in Ubuntu: New Bug description: There is a newer version of libsoup that allows NTLMv2 authentication that resolves this issue. Here is a bug from the Gnome libsoup bug report: https://gitlab.gnome.org/GNOME/libsoup/issues/114 In this bug report for Evolution: https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 someone mentions "the change landed after 2.64.0 and before 2.65.1 and seems to be part of 2.65.1+ only" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1833440/+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 1832882] Re: libcurl-gnutls segfaults spotify client
The spotify community post suggest using the snap as a workaround (which is a good idea since the snap is maintained by upstream directly and those are less likely to be impact by OS issues like that one) ** Changed in: curl (Ubuntu) Importance: Undecided => High ** Changed in: curl (Ubuntu Disco) Importance: Undecided => High ** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client Status in curl package in Ubuntu: Confirmed Status in curl source package in Disco: Confirmed Bug description: The latest release of Spotify client segfaults in libcurl-gnutls as can be read in this thread on spotify support forum: https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479 According to one participant the work-around is to install debian packages libgnutls30_3.6.8-1_amd64.deb and libcurl3-gnutls_7.64.0-3_amd64.deb Ubuntu 19.04 version of the packages: libgnutls30 3.6.5-2ubuntu1.1 libcurl3-gnutls 7.64.0-2ubuntu1.1 As the bug can be resolved by installing debian packages, I assume Ubuntu's version of the packages is at fault and should be upgraded to match debian's level as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+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 1832882] Re: libcurl-gnutls segfaults spotify client
There is no stacktrace there but that new Debian revision fixes a segfault, so it's probably worth SRU that change https://packages.qa.debian.org/c/curl/news/20190512T204836Z.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832882 Title: libcurl-gnutls segfaults spotify client Status in curl package in Ubuntu: Confirmed Status in curl source package in Disco: Confirmed Bug description: The latest release of Spotify client segfaults in libcurl-gnutls as can be read in this thread on spotify support forum: https://community.spotify.com/t5/Desktop-Linux/Ubuntu-19-04-deb-package-segfault/td-p/4761479 According to one participant the work-around is to install debian packages libgnutls30_3.6.8-1_amd64.deb and libcurl3-gnutls_7.64.0-3_amd64.deb Ubuntu 19.04 version of the packages: libgnutls30 3.6.5-2ubuntu1.1 libcurl3-gnutls 7.64.0-2ubuntu1.1 As the bug can be resolved by installing debian packages, I assume Ubuntu's version of the packages is at fault and should be upgraded to match debian's level as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1832882/+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 1833470] Re: ca0132 audio in Ubuntu 19.04 only after Windows 10 started
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- 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/1833470 Title: ca0132 audio in Ubuntu 19.04 only after Windows 10 started Status in linux package in Ubuntu: Incomplete Bug description: Motherboard: Gigabyte GA-Z170X-Gaming GT (rev. 1.0) Description: Ubuntu 19.04 Release: 19.04 Expected behavior: Audio playback via headphones Actual behavior: No audio playback heard If I start Ubuntu 19.04 directly after booting my PC, there is no sound from the front or rear outputs. Everything seems configured correctly in Alsamixer, etc. If I boot into Windows 10, then restart and enter Ubuntu, the sound works as expected. I suspect something is being set properly by the Windows driver that is missed in the native Linux driver. The fact that it survives a (soft) reboot is interesting. I know this is at the ALSA level or below, because if I stop pulseaudio, `aplay music.wav` produces no output before starting Windows, and works after starting Windows. output of `lspci | grep -i audio` 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 02:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) output of `aplay -lL` default Playback/recording through the PulseAudio sound server null Discard all samples (playback) or generate zero samples (capture) jack JACK Audio Connection Kit pulse PulseAudio Sound Server sysdefault:CARD=PCH HDA Intel PCH, CA0132 Analog Default Audio Device front:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Front speakers surround21:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Digital IEC958 (S/PDIF) Digital Audio Output dmix:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct sample mixing device dmix:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct sample mixing device dsnoop:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct sample snooping device dsnoop:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct sample snooping device hw:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Direct hardware device without any conversions hw:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Direct hardware device without any conversions plughw:CARD=PCH,DEV=0 HDA Intel PCH, CA0132 Analog Hardware device with all software conversions plughw:CARD=PCH,DEV=1 HDA Intel PCH, CA0132 Digital Hardware device with all software conversions usbstream:CARD=PCH HDA Intel PCH USB Stream Output hdmi:CARD=NVidia,DEV=0 HDA NVidia, HDMI 0 HDMI Audio Output hdmi:CARD=NVidia,DEV=1 HDA NVidia, HDMI 1 HDMI Audio Output hdmi:CARD=NVidia,DEV=2 HDA NVidia, HDMI 2 HDMI Audio Output hdmi:CARD=NVidia,DEV=3 HDA NVidia, HDMI 3 HDMI Audio Output dmix:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct sample mixing device dmix:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct sample mixing device dmix:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct sample mixing device dmix:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Direct sample mixing device dsnoop:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct sample snooping device dsnoop:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct sample snooping device dsnoop:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct sample snooping device dsnoop:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Direct sample snooping device hw:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 Direct hardware device without any conversions hw:CARD=NVidia,DEV=7 HDA NVidia, HDMI 1 Direct hardware device without any conversions hw:CARD=NVidia,DEV=8 HDA NVidia, HDMI 2 Direct hardware device without any conversions hw:CARD=NVidia,DEV=9 HDA NVidia, HDMI 3 Direct hardware device without any conversions plughw:CARD=NVidia,DEV=3
[Touch-packages] [Bug 1833508] Re: the system woke up and has not proper desktop image
Thank you for your bug report, could you run that command $ apport-collect 1833508 What video card/driver are you using? Could you add your journalctl log to the bug after getting the issue? ** Package changed: systemd (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1833508 Title: the system woke up and has not proper desktop image Status in gnome-shell package in Ubuntu: Incomplete Bug description: i have ubuntu 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+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 1833512] Re: Wifi password dialog popup don't take more the 20 ASCII-encoded characters
Thank you for your bug report. Could you take a screenshot of the dialog you are talking about? How do you try to connect? What happens when you type more than 20 chars? ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1833512 Title: Wifi password dialog popup don't take more the 20 ASCII-encoded characters Status in network-manager package in Ubuntu: Incomplete Bug description: The max pass-phrase length for a WPA2-PSK, has a limit of 63 ASCII- encoded characters The password fields, in the dialog to write the pass-phrase for the Wifi network you are connecting to, is limiting this to 20 characters. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 09:59:57 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-06-19 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev enp0s25 proto dhcp metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.169 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 cb8f8bbb-c98f-3fcd-8212-fdf5d6425ab1 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0 wifi disconnected limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 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/1833512/+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 1833116] Re: chtmax98090 not working out of the box
** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1833116 Title: chtmax98090 not working out of the box Status in alsa-driver package in Ubuntu: Confirmed Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+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 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell
Could you provide the details asked in the previous comment? -- 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/1827842 Title: pulseaudio should not load module-x11-bell in gnome-shell Status in pulseaudio package in Ubuntu: Triaged Bug description: The package `pulseaudio` installs a startup script in `/etc/xdg/autostart/pulseaudio.desktop`, which itself runs `/usr/bin/start-pulseaudio-x11`, which loads a number of x11 related modules in `pulseaudio`. One of these modules is `module-x11-bell`, which makes `pulseaudio` play a sound each time a system bell is emitted (usually by terminal applications, such as bash or vim). This is redundant with gnome-shell, which is also able to handle the system bell (through the gsetting key `org.gnome.desktop.sound event-sounds`). The gnome system bell is directly configurable by the user (Settings > Sound), so it should be preferred over pulseaudio's own system bell. I suggest to patch the `/usr/bin/start-pulseaudio-x11`, to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome Shell (e.g. if GNOME_SHELL_SESSION_MODE is set). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1833719] Re: UFW 2nd interface incorrectly working
Thank you for using ufw and filing a bug. Please keep in mind that the firewall is sensitive to rule order. What is the output of 'sudo ufw show numbered'? ** Changed in: ufw (Ubuntu) Status: New => Incomplete -- 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/1833719 Title: UFW 2nd interface incorrectly working Status in ufw package in Ubuntu: Incomplete Bug description: ufw --version = ufw 0.36 Server has two interfaces ens160 and ens192 looking at the logs to understand why ufw is blocking requests from an interface, the log show the correct ip address and the incorrect interface. ip address 192.168.1.4 is on ens160 ip address 192.168.1.46 is on ens192 Correct when visiting address 192.168.1.4 i am blocked an logs correctly identify that i am using IN=ens160 Incorrect when visiting address 192.168.1.46 i am also blocked even though rule has been added "sudo ufw allow in on ens192 to any from 192.168.0.0/16" Logs from /var/log/ufw.log show that DST=192.168.1.46 is blocked witn IN=ens160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1833719/+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 1776752] Re: package console-setup-linux 1.108ubuntu16.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Which BTW, is a dup of #1068222 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1776752 Title: package console-setup-linux 1.108ubuntu16.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in console-setup package in Ubuntu: Confirmed Bug description: Setting up console-setup-linux (1.108ubuntu15.4) ... update-alternatives: error: alternative path /etc/console-setup/vtrgb doesn't exist dpkg: error processing package console-setup-linux (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of console-setup: console-setup depends on console-setup-linux; however: Package console-setup-linux is not configured yet. dpkg: error processing package console-setup (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: console-setup-linux console-setup E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: console-setup-linux 1.108ubuntu15.4 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jun 13 22:21:27 2018 DuplicateSignature: package:console-setup-linux:1.108ubuntu15.4 Installing new version of config file /etc/console-setup/compose.ISO-8859-9.inc ... update-alternatives: error: alternative path /etc/console-setup/vtrgb doesn't exist dpkg: error processing package console-setup-linux (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2018-04-13 (61 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: console-setup Title: package console-setup-linux 1.108ubuntu15.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.console-setup.compose.ARMSCII-8.inc: [deleted] modified.conffile..etc.console-setup.compose.CP1251.inc: [deleted] modified.conffile..etc.console-setup.compose.CP1255.inc: [deleted] modified.conffile..etc.console-setup.compose.CP1256.inc: [deleted] modified.conffile..etc.console-setup.compose.GEORGIAN-ACADEMY.inc: [deleted] modified.conffile..etc.console-setup.compose.GEORGIAN-PS.inc: [deleted] modified.conffile..etc.console-setup.compose.IBM1133.inc: [deleted] modified.conffile..etc.console-setup.compose.ISIRI-3342.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-10.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-11.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-16.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-5.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-6.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-8.inc: [deleted] modified.conffile..etc.console-setup.compose.KOI8-R.inc: [deleted] modified.conffile..etc.console-setup.compose.KOI8-U.inc: [deleted] modified.conffile..etc.console-setup.compose.TIS-620.inc: [deleted] modified.conffile..etc.console-setup.compose.VISCII.inc: [deleted] modified.conffile..etc.console-setup.remap.inc: [deleted] modified.conffile..etc.console-setup.vtrgb: [deleted] modified.conffile..etc.console-setup.vtrgb.vga: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1776752/+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 1776752] Re: package console-setup-linux 1.108ubuntu16.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Same problem. On 19.04. console-setup-linux 1.178ubuntu12.1. And there no issues with my hardware. ** Changed in: console-setup (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1776752 Title: package console-setup-linux 1.108ubuntu16.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in console-setup package in Ubuntu: Confirmed Bug description: Setting up console-setup-linux (1.108ubuntu15.4) ... update-alternatives: error: alternative path /etc/console-setup/vtrgb doesn't exist dpkg: error processing package console-setup-linux (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of console-setup: console-setup depends on console-setup-linux; however: Package console-setup-linux is not configured yet. dpkg: error processing package console-setup (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: console-setup-linux console-setup E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: console-setup-linux 1.108ubuntu15.4 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jun 13 22:21:27 2018 DuplicateSignature: package:console-setup-linux:1.108ubuntu15.4 Installing new version of config file /etc/console-setup/compose.ISO-8859-9.inc ... update-alternatives: error: alternative path /etc/console-setup/vtrgb doesn't exist dpkg: error processing package console-setup-linux (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2018-04-13 (61 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: console-setup Title: package console-setup-linux 1.108ubuntu15.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.console-setup.compose.ARMSCII-8.inc: [deleted] modified.conffile..etc.console-setup.compose.CP1251.inc: [deleted] modified.conffile..etc.console-setup.compose.CP1255.inc: [deleted] modified.conffile..etc.console-setup.compose.CP1256.inc: [deleted] modified.conffile..etc.console-setup.compose.GEORGIAN-ACADEMY.inc: [deleted] modified.conffile..etc.console-setup.compose.GEORGIAN-PS.inc: [deleted] modified.conffile..etc.console-setup.compose.IBM1133.inc: [deleted] modified.conffile..etc.console-setup.compose.ISIRI-3342.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-10.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-11.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-16.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-5.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-6.inc: [deleted] modified.conffile..etc.console-setup.compose.ISO-8859-8.inc: [deleted] modified.conffile..etc.console-setup.compose.KOI8-R.inc: [deleted] modified.conffile..etc.console-setup.compose.KOI8-U.inc: [deleted] modified.conffile..etc.console-setup.compose.TIS-620.inc: [deleted] modified.conffile..etc.console-setup.compose.VISCII.inc: [deleted] modified.conffile..etc.console-setup.remap.inc: [deleted] modified.conffile..etc.console-setup.vtrgb: [deleted] modified.conffile..etc.console-setup.vtrgb.vga: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1776752/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
Looks like noto sources now have the right glyphs (since their April 9 release, actually). It will need an update both in Debian and Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in Poppler: New Status in fonts-noto-cjk package in Ubuntu: New Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: Fix Released Status in libreoffice-l10n source package in Xenial: Fix Released Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Released Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. == Typing / input methods ==
[Touch-packages] [Bug 1833719] Re: UFW 2nd interface incorrectly working
** Attachment added: "Logs from /var/log/ufw.log" https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1833719/+attachment/5272094/+files/firewallBug.png -- 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/1833719 Title: UFW 2nd interface incorrectly working Status in ufw package in Ubuntu: New Bug description: ufw --version = ufw 0.36 Server has two interfaces ens160 and ens192 looking at the logs to understand why ufw is blocking requests from an interface, the log show the correct ip address and the incorrect interface. ip address 192.168.1.4 is on ens160 ip address 192.168.1.46 is on ens192 Correct when visiting address 192.168.1.4 i am blocked an logs correctly identify that i am using IN=ens160 Incorrect when visiting address 192.168.1.46 i am also blocked even though rule has been added "sudo ufw allow in on ens192 to any from 192.168.0.0/16" Logs from /var/log/ufw.log show that DST=192.168.1.46 is blocked witn IN=ens160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1833719/+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 1833671] Re: bond interfaces stop working after restart of systemd-networkd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd package in Ubuntu: Confirmed Bug description: Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833671/+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 1833719] [NEW] UFW 2nd interface incorrectly working
Public bug reported: ufw --version = ufw 0.36 Server has two interfaces ens160 and ens192 looking at the logs to understand why ufw is blocking requests from an interface, the log show the correct ip address and the incorrect interface. ip address 192.168.1.4 is on ens160 ip address 192.168.1.46 is on ens192 Correct when visiting address 192.168.1.4 i am blocked an logs correctly identify that i am using IN=ens160 Incorrect when visiting address 192.168.1.46 i am also blocked even though rule has been added "sudo ufw allow in on ens192 to any from 192.168.0.0/16" Logs from /var/log/ufw.log show that DST=192.168.1.46 is blocked witn IN=ens160 ** Affects: ufw (Ubuntu) Importance: Undecided Status: New -- 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/1833719 Title: UFW 2nd interface incorrectly working Status in ufw package in Ubuntu: New Bug description: ufw --version = ufw 0.36 Server has two interfaces ens160 and ens192 looking at the logs to understand why ufw is blocking requests from an interface, the log show the correct ip address and the incorrect interface. ip address 192.168.1.4 is on ens160 ip address 192.168.1.46 is on ens192 Correct when visiting address 192.168.1.4 i am blocked an logs correctly identify that i am using IN=ens160 Incorrect when visiting address 192.168.1.46 i am also blocked even though rule has been added "sudo ufw allow in on ens192 to any from 192.168.0.0/16" Logs from /var/log/ufw.log show that DST=192.168.1.46 is blocked witn IN=ens160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1833719/+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 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
Get:1 http://ppa.launchpad.net/ansible/ansible/ubuntu bionic/main amd64 ansible all 2.8.1-1ppa~bionic [5,140 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libssl-dev amd64 1.1.1-1ubuntu2.1~18.04.4 [1,566 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libssl1.1 amd64 1.1.1-1ubuntu2.1~18.04.4 [1,300 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-markupsafe amd64 1.0-1build1 [13.0 kB] Get:5 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 python-jinja2 all 2.10-1ubuntu0.18.04.1 [94.8 kB] Get:6 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-yaml amd64 3.12-1build2 [115 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-asn1crypto all 0.24.0-1 [72.7 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-cffi-backend amd64 1.11.5-1 [63.4 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-enum34 all 1.1.6-2 [34.8 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-idna all 2.6-1 [32.4 kB] Get:11 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-ipaddress all 1.0.17-1 [18.2 kB] Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-six all 1.11.0-2 [11.3 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 python-cryptography amd64 2.1.4-1ubuntu1.3 [221 kB] Get:14 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-pyasn1 all 0.4.2-3 [46.7 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 python-paramiko all 2.0.0-1ubuntu1.2 [110 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 python-httplib2 all 0.9.2+dfsg-1ubuntu0.1 [34.7 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-pkg-resources all 39.0.1-2 [128 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-setuptools all 39.0.1-2 [329 kB] Get:19 http://archive.ubuntu.com/ubuntu bionic/universe amd64 sshpass amd64 1.06-1 [10.5 kB] Fetched 9,342 kB in 5s (1,812 kB/s) Preconfiguring packages ... (Reading database ... 42089 files and directories currently installed.) Preparing to unpack .../00-libssl-dev_1.1.1-1ubuntu2.1~18.04.4_amd64.deb ... Unpacking libssl-dev:amd64 (1.1.1-1ubuntu2.1~18.04.4) over (1.1.0g-2ubuntu4.3) ... Preparing to unpack .../01-libssl1.1_1.1.1-1ubuntu2.1~18.04.4_amd64.deb ... Unpacking libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.4) over (1.1.0g-2ubuntu4.3) ... . . Setting up libssl1.1:amd64 (1.1.1-1ubuntu2.1~18.04.4) ... Checking for services that may need to be restarted...done. Checking for services that may need to be restarted...done. Checking init scripts... Restarting services possibly affected by the upgrade: Services restarted successfully. Setting up python-enum34 (1.1.6-2) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Setting up python-ipaddress (1.0.17-1) ... Setting up python-setuptools (39.0.1-2) ... Setting up python-jinja2 (2.10-1ubuntu0.18.04.1) ... Setting up libssl-dev:amd64 (1.1.1-1ubuntu2.1~18.04.4) ... Fix confirmed. (Ubuntu Bionic): tags: verification-done-bionic -- 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/1832919 Title: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Cosmic: Fix Committed Status in openssl source package in Disco: Fix Committed Status in openssl source package in Eoan: Fix Released Bug description: [Impact] * Systems that have in error removed debconf database fail to upgrade libssl1.1 (as e.g. is known to be done in some vagrant boxes) * libssl1.1 tries to use debconf template from libc6 package, but doesn't ship one by itself as it should for shared templates. As it is not guaranteed that template will be available. [TestCase] # DO NOT DO THIS ON PRODUCTION MACHINES # # echo PURGE | debconf-communicate libpam0g:amd64 0 # echo PURGE | debconf-communicate libpam0g 0 # echo PURGE | debconf-communicate libc6:amd64 0 # echo PURGE | debconf-communicate libc6 0 Then upgrade from bionic-release to the -proposed package and it should work. It should not fail with exit code 10. [Regression Potential] * A new template is added, an identical import from glibc without any further changes. This registers the template in debconf, for this package, preventing the above describe error. This has no codechanges, only metadata. [Other Info] * Original bug report The error happens when trying to configure libssl1.1:amd64 (dpkg --configure -D 2 libssl1.1) dpkg: error processing package
[Touch-packages] [Bug 1833715] Re: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1832054 *** https://bugs.launchpad.net/bugs/1832054 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1832054, so 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. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1832054 package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- 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/1833715 Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: ao tentar atualizar ubuntu 14.04 para 16.04 apresenta erro ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.21 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 21 09:45:23 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-02 (111 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.21 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/initramfs-tools/+bug/1833715/+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 1833715] [NEW] package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1832054 *** https://bugs.launchpad.net/bugs/1832054 Public bug reported: ao tentar atualizar ubuntu 14.04 para 16.04 apresenta erro ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.21 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 21 09:45:23 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-02 (111 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1833715 Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: ao tentar atualizar ubuntu 14.04 para 16.04 apresenta erro ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.21 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 21 09:45:23 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-02 (111 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.21 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/initramfs-tools/+bug/1833715/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
** Tags added: id-5d0bec28939a024305398e2a -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
** Tags added: id-5d0ba914f340e31a8e9f2cf1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in lvm2 source package in Bionic: New Status in linux source package in Cosmic: New Status in lvm2 source package in Cosmic: New Status in linux source package in Disco: New Status in lvm2 source package in Disco: New Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: In Progress Status in lvm2 package in Debian: Unknown Bug description: After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1832651] Re: jackdbus fails to start: cannot allocate memory
** Tags added: id-5d0babe141a9fa1a8a1210f7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Fix Released Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Status in jackd2 source package in Eoan: Invalid Status in systemd source package in Eoan: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+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 1833236] Re: whoopsie ftbfs in eoan
** Tags added: id-5d0ba7e6aecdb9565b8ad098 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1833236 Title: whoopsie ftbfs in eoan Status in whoopsie package in Ubuntu: New Status in whoopsie source package in Eoan: New Bug description: whoopsie ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17048048/+files/buildlog_ubuntu-eoan- amd64.whoopsie_0.2.64_BUILDING.txt.gz dh_auto_build make -j1 make[1]: Entering directory '/<>' Package NetworkManager was not found in the pkg-config search path. Perhaps you should add the directory containing `NetworkManager.pc' to the PKG_CONFIG_PATH environment variable No package 'NetworkManager' found cc -std=c99 -c -g -Ilib -Wall -Werror -Os -DVERSION=\"0.2.64\" -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o src/whoopsie.o src/whoopsie.c src/whoopsie.c:26:10: fatal error: glib.h: No such file or directory #include ^~~~ compilation terminated. make[1]: *** [Makefile:58: src/whoopsie.o] Error 1 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 returned exit code 2 make: *** [debian/rules:17: build] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1833236/+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 1833237] Re: skiboot ftbfs in eoan
** Tags added: id-5d0ba2fcdd3f47767d5ae86d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1833237 Title: skiboot ftbfs in eoan Status in binutils: In Progress Status in binutils package in Ubuntu: Confirmed Status in skiboot package in Ubuntu: Confirmed Status in binutils source package in Eoan: Confirmed Status in skiboot source package in Eoan: Confirmed Bug description: skiboot ftbfs in eoan https://launchpad.net/ubuntu/+archive/test- rebuild-20190614/+build/17038512/+files/buildlog_ubuntu-eoan- amd64.skiboot_6.2-1_BUILDING.txt.gz powerpc64-linux-gnu-gcc-I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -D__ASSEMBLY__ -mbig-endian -m64 -mabi=elfv1 -c asm/dummy_map.S -o asm/dummy_map.o powerpc64-linux-gnu-gcc -I/<>/include -Iinclude -MMD -include /<>/include/config.h -I/<>/libfdt -I/<>/libflash -I/<>/libxz -I/<>/libc/include -I/<> -I/<>/libpore -D__SKIBOOT__ -nostdinc -isystem /usr/lib/gcc-cross/powerpc64-linux-gnu/8/include -DBITS_PER_LONG=64 -DHAVE_BIG_ENDIAN -ffreestanding -DHAS_STACK_PROT -P -E skiboot.lds.S -o skiboot.lds powerpc64-linux-gnu-ld -EB -m elf64ppc --no-multi-toc -N --build-id=none --whole-archive -static -nostdlib -pie -Ttext-segment=0x0 --oformat=elf64-powerpc -o skiboot.tmp.elf -T skiboot.lds skiboot.tmp.a asm/dummy_map.o powerpc64-linux-gnu-ld: BFD (GNU Binutils for Ubuntu) 2.32.51.20190614 internal error, aborting at ../../bfd/elf64-ppc.c:15381 in ppc64_elf_relocate_section powerpc64-linux-gnu-ld: Please report this bug. make[2]: *** [/<>/Makefile.main:262: skiboot.tmp.elf] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:19: override_dh_auto_build-indep] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1833237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659534] Re: userdel doesn't supports extrausers
@mvo This fix raised bionic-update's shadow version above cosmic's. Do you plan fixing that or just wait for Cosmic's EOL? ** Also affects: shadow (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: shadow (Ubuntu Cosmic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1659534 Title: userdel doesn't supports extrausers Status in Snappy: In Progress Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Fix Released Status in shadow source package in Bionic: Fix Released Status in shadow source package in Cosmic: Confirmed Bug description: TEST CASE: - run userdel --extrausers foo on a ubuntu core system REGRESSION POTENTIAL: - low, this option will only take effect when "userdel --extrauser" is used. On an Ubuntu Core system is impossible to delete an user from the extrausers db: root@localhost:/# userdel --extrausers alice userdel: unrecognized option '--extrausers' To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832919] Re: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10
This bug was fixed in the package openssl - 1.1.1c-1ubuntu3 --- openssl (1.1.1c-1ubuntu3) eoan; urgency=medium * Import libraries/restart-without-asking as used in postinst, to prevent failure to configure the package without debconf database. LP: #1832919 -- Dimitri John Ledkov Thu, 20 Jun 2019 17:59:55 +0100 ** Changed in: openssl (Ubuntu Eoan) Status: Fix Committed => Fix Released -- 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/1832919 Title: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: Fix Committed Status in openssl source package in Cosmic: Fix Committed Status in openssl source package in Disco: Fix Committed Status in openssl source package in Eoan: Fix Released Bug description: [Impact] * Systems that have in error removed debconf database fail to upgrade libssl1.1 (as e.g. is known to be done in some vagrant boxes) * libssl1.1 tries to use debconf template from libc6 package, but doesn't ship one by itself as it should for shared templates. As it is not guaranteed that template will be available. [TestCase] # DO NOT DO THIS ON PRODUCTION MACHINES # # echo PURGE | debconf-communicate libpam0g:amd64 0 # echo PURGE | debconf-communicate libpam0g 0 # echo PURGE | debconf-communicate libc6:amd64 0 # echo PURGE | debconf-communicate libc6 0 Then upgrade from bionic-release to the -proposed package and it should work. It should not fail with exit code 10. [Regression Potential] * A new template is added, an identical import from glibc without any further changes. This registers the template in debconf, for this package, preventing the above describe error. This has no codechanges, only metadata. [Other Info] * Original bug report The error happens when trying to configure libssl1.1:amd64 (dpkg --configure -D 2 libssl1.1) dpkg: error processing package libssl1.1:amd64 (--configure): installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 10 D02: post_script_tasks - ensure_diversions D02: post_script_tasks - trig_incorporate D02: check_triggers_cycle pnow=libc-bin:amd64 first Processing triggers for libc-bin (2.27-3ubuntu1) ... D02: post_postinst_tasks - trig_incorporate Errors were encountered while processing: libssl1.1:amd64 [ WORKAROUND TO RECOVER YOUR SYSTEM ] $ sudo dpkg-reconfigure libc6 $ sudo dpkg --configure libssl1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832919/+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 1830146] Re: Checkbox detect an extra webcam "video1"
** Changed in: checkbox-support Status: In Progress => Fix Committed -- 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/1830146 Title: Checkbox detect an extra webcam "video1" Status in Checkbox Support Library: Fix Committed Status in systemd package in Ubuntu: New Bug description: Summary: System only have 1 webcam (video0) but checkbox detect an extra webcam "video1" - system-product-name: Latitude 5501 GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b (rev 02) CPU: Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz (12x) bios-version: 1.0.0 system-manufacturer: Dell Inc. Image: somerville-bionic-amd64-iso-hybrid-20180608-47 To manage notifications about this bug go to: https://bugs.launchpad.net/checkbox-support/+bug/1830146/+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 1832859] Re: during shutdown libvirt-guests gets stopped after file system unmount
It seems - somewhat expected - that the solution needs to be a bit bigger due to further service dependencies that might create a loop. Until that solution is sorted out upstream we should not implement another custom emergency fix that might cause more trouble. Instead while we wait on the final solution by upstream I'd recommend that everybody affected needs to evaluate his own system if the modification suggested in comment #8 would suffice as a workaround for you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1832859 Title: during shutdown libvirt-guests gets stopped after file system unmount Status in lvm2: New Status in libvirt package in Ubuntu: Incomplete Status in lvm2 package in Ubuntu: New Status in lvm2 package in Fedora: Unknown Bug description: When using automatic suspend at reboot/shutdown, it makes sense to store the suspend data on a separate partition to ensure there is always enough available space. However this does not work, as the partition gets unmounted before or during libvirt suspend. Steps to reproduce: 1. Use Ubuntu 18.04.02 LTS 2. Install libvirt + qemu-kvm 3. Start a guest 4. Set libvirt-guests to suspend at shutdown/reboot by editing /etc/default/libvirt-guests 5. Create a fstab entry to mount a separate partition to mount point /var/lib/libvirt/qemu/save. Then run sudo mount /var/lib/libvirt/qemu/save to mount the partition. 6. Reboot Expected result: The guest suspend data would be written to the /var/lib/libvirt/qemu/save, resulting in the data being stored at the partition specified in fstab. At boot, this partition would be mounted as specified in fstab and libvirt-guest would be able to read the data and restore the guests. Actual result: The partition gets unmounted before libvirt-guests suspends the guests, resulting in the data being stored on the partition containing the root file system. During boot, the empty partition gets mounted over the non-empty /var/lib/libvirt/qemu/save directory, resulting in libvirt-guests being unable to read the saved data. As a side effect, the saved data is using up space on the root partition even if the directory appears empty. Here is some of the relevant lines from the journal: Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: Deactivating block devices: Jun 14 00:00:04 libvirt-host systemd[1]: Unmounted /var/lib/libvirt/qemu/save. Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: [UMOUNT]: unmounting libvirt_lvm-suspenddata (dm-3) mounted on /var/lib/libvirt/qemu/save... done Jun 14 00:00:04 libvirt-host libvirt-guests.sh[4349]: Running guests on default URI: vps1, vps2, vps3 Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: [MD]: deactivating raid1 device md1... done Jun 14 00:00:05 libvirt-host libvirt-guests.sh[4349]: Suspending guests on default URI... Jun 14 00:00:05 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... Jun 14 00:00:05 libvirt-host blkdeactivate[4343]: [LVM]: deactivating Volume Group libvirt_lvm... skipping Jun 14 00:00:10 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: 5.989 GiB Jun 14 00:00:15 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... Jun 14 00:00:20 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/1832859/+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 1832859] Re: during shutdown libvirt-guests gets stopped after file system unmount
Linked the related RH bug that was mentioned upstream https://bugzilla.redhat.com/show_bug.cgi?id=1701234 ** Bug watch added: Red Hat Bugzilla #1701234 https://bugzilla.redhat.com/show_bug.cgi?id=1701234 ** Also affects: lvm2 (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1701234 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1832859 Title: during shutdown libvirt-guests gets stopped after file system unmount Status in lvm2: New Status in libvirt package in Ubuntu: Incomplete Status in lvm2 package in Ubuntu: New Status in lvm2 package in Fedora: Unknown Bug description: When using automatic suspend at reboot/shutdown, it makes sense to store the suspend data on a separate partition to ensure there is always enough available space. However this does not work, as the partition gets unmounted before or during libvirt suspend. Steps to reproduce: 1. Use Ubuntu 18.04.02 LTS 2. Install libvirt + qemu-kvm 3. Start a guest 4. Set libvirt-guests to suspend at shutdown/reboot by editing /etc/default/libvirt-guests 5. Create a fstab entry to mount a separate partition to mount point /var/lib/libvirt/qemu/save. Then run sudo mount /var/lib/libvirt/qemu/save to mount the partition. 6. Reboot Expected result: The guest suspend data would be written to the /var/lib/libvirt/qemu/save, resulting in the data being stored at the partition specified in fstab. At boot, this partition would be mounted as specified in fstab and libvirt-guest would be able to read the data and restore the guests. Actual result: The partition gets unmounted before libvirt-guests suspends the guests, resulting in the data being stored on the partition containing the root file system. During boot, the empty partition gets mounted over the non-empty /var/lib/libvirt/qemu/save directory, resulting in libvirt-guests being unable to read the saved data. As a side effect, the saved data is using up space on the root partition even if the directory appears empty. Here is some of the relevant lines from the journal: Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: Deactivating block devices: Jun 14 00:00:04 libvirt-host systemd[1]: Unmounted /var/lib/libvirt/qemu/save. Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: [UMOUNT]: unmounting libvirt_lvm-suspenddata (dm-3) mounted on /var/lib/libvirt/qemu/save... done Jun 14 00:00:04 libvirt-host libvirt-guests.sh[4349]: Running guests on default URI: vps1, vps2, vps3 Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: [MD]: deactivating raid1 device md1... done Jun 14 00:00:05 libvirt-host libvirt-guests.sh[4349]: Suspending guests on default URI... Jun 14 00:00:05 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... Jun 14 00:00:05 libvirt-host blkdeactivate[4343]: [LVM]: deactivating Volume Group libvirt_lvm... skipping Jun 14 00:00:10 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: 5.989 GiB Jun 14 00:00:15 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... Jun 14 00:00:20 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/1832859/+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 1833671] [NEW] bond interfaces stop working after restart of systemd-networkd
Public bug reported: Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd package in Ubuntu: New Bug description: Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833671/+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 1831775] Re: ss seems broken when using multiple filters in the same cmdline
** Merge proposal linked: https://code.launchpad.net/~smb/ubuntu/+source/iproute2/+git/iproute2/+merge/369140 -- 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/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: In Progress Status in iproute2 source package in Disco: In Progress Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+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
