[Touch-packages] [Bug 1759961] Re: Update to bluez 5.50
Hi all, I've encountered Heart rate profile connection error of bluez-5.48 in Bionic. It can be resolved in bluez 5.49 version from below commit. - Fix issue with Connect and ConnectProfile returning in progress. Do you have a plan to upgrade the bluez version to 5.50 for Bionic as well? If not, could you pick the patch for Ubuntu bionic's bluez version. If you want to create a ticket for this release, I can make it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759961 Title: Update to bluez 5.50 Status in bluez package in Ubuntu: Fix Released Bug description: From upstream: http://www.bluez.org/release-of-bluez-5-49/ Release of BlueZ 5.49 This is mostly a bug fix release, with fixes to features such as AVCTP, OBEX, GATT and Mesh. There are however some notable new features also, such as improved heartbeat management support in meshctl as well as a new experimental ConnectDevice D-Bus method on the Adapter interface, which can be used for quick device object creation for testing purpose or when information about the device has been received over some Out-of-Band channel. Upstream changelog: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog ver 5.49: Fix issue with configuring discoverable advertising flag. Fix issue with bearer selection and single mode controllers. Fix issue with Connect and ConnectProfile returning in progress. Fix issue with missing Paired property change when not bonded. Fix issue with storage for controllers without public address. Fix issue with handling AVCTP disconnecting the channel queue. Fix issue with not clearing connectable setting on power off. Fix issue with creating multiple mgmt socket instances. Fix issue with GATT server and BR/EDR only devices. Fix issue with InterfaceAdded event ordering. Add support for generic ConnectDevice method call. Add support for Mesh heartbeat client functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759961/+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 1767654] Re: Cursor gets stuck on left side of the screen
If you have any Gnome Shell extensions installed, please try disabling them and tell us if that fixes the problem. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** 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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: Cursor gets stuck on left side of the screen Status in gnome-shell package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+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 1767342] Re: Dosplay scale factor reset after changing screen size or reboot
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: hidpi -- 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/1767342 Title: Dosplay scale factor reset after changing screen size or reboot Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce 1. Take computer with HiDPI monitor 2. Install bionic in VM, install open-vm-tools && open-vm-tools-desktop and enable hi-dpi 3. Settings-Devices-Display-Scale to 200% and press apply 4. Drag VM window corner for changing VM screen size or simple reboot VM. Scale resets to 100% ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 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: Unity Date: Fri Apr 27 14:20:34 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=203b7377-6f0c-4d39-a33f-db18baece74c ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767342/+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 1038706] Re: "Testing download servers" hangs
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1038706 Title: "Testing download servers" hangs Status in software-properties package in Ubuntu: Expired Bug description: From Software Sources / Download from / other/ Select Best Server, the "Testing Download Servers" progress bar only gets halfway through and then hangs. Tried several times over many different days, and predictably hangs at the same spot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1038706/+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 1797302] [NEW] ubuntu-bug doesn't provide a way of just getting the URL to report a bug
Public bug reported: I use more than one browser profile, only one of which is logged in to Launchpad. When using ubuntu-bug to report a bug, it will open the page in whichever one happened to be focused last. If this browser profile isn't logged in to Launchpad, it will redirect me to a login page. It is impossible, as far as I can tell, to reconstruct the original URL in order to copy/paste it in to a browser profile which _is_ logged in to Launchpad. It would be good if ubuntu-bug could either display the URL it is opening before it opens it in the UI. (An acceptable workaround for me (as I generally launch ubuntu-bug from a terminal) would be to write the URL to stdout.) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 11 00:31:45 2018 InstallationDate: Installed on 2017-10-23 (352 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to cosmic on 2018-09-10 (30 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1797302 Title: ubuntu-bug doesn't provide a way of just getting the URL to report a bug Status in apport package in Ubuntu: New Bug description: I use more than one browser profile, only one of which is logged in to Launchpad. When using ubuntu-bug to report a bug, it will open the page in whichever one happened to be focused last. If this browser profile isn't logged in to Launchpad, it will redirect me to a login page. It is impossible, as far as I can tell, to reconstruct the original URL in order to copy/paste it in to a browser profile which _is_ logged in to Launchpad. It would be good if ubuntu-bug could either display the URL it is opening before it opens it in the UI. (An acceptable workaround for me (as I generally launch ubuntu-bug from a terminal) would be to write the URL to stdout.) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 11 00:31:45 2018 InstallationDate: Installed on 2017-10-23 (352 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to cosmic on 2018-09-10 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1797302/+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 973045] Re: Does not allow me to select 'sources'
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/973045 Title: Does not allow me to select 'sources' Status in software-properties package in Ubuntu: Expired Bug description: See video - the application was not allowing me to select 'sources', while failing to provide an explanation as to why as well. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: software-properties-gtk 0.81.13.3 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Wed Apr 4 13:07:52 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/973045/+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 1541207] Re: package python3-software-properties 0.92.37.6 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1541207 Title: package python3-software-properties 0.92.37.6 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück Status in software-properties package in Ubuntu: Expired Bug description: Software updater does not open either. Since 4 weeks there are very many system-errors ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python3-software-properties 0.92.37.6 ProcVersionSignature: Ubuntu 3.19.0-42.48~14.04.1-generic 3.19.8-ckt10 Uname: Linux 3.19.0-42-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Wed Feb 3 06:29:27 2016 DuplicateSignature: package:python3-software-properties:0.92.37.6:Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2015-08-28 (158 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: software-properties Title: package python3-software-properties 0.92.37.6 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1541207/+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 1797002] Re: all my bluetooth headsets skips terribly after todays update
The change could also be a coincidence and environmental, like: * a new 2.4GHz wifi network or device was recently introduced nearby, degrading Bluetooth signal quality. * a new Bluetooth device was introduced nearby, degrading the signal quality of audio. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work
I opened an issue upstream about this: https://gitlab.gnome.org/GNOME /gnome-control-center/issues/229 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1759300 Title: Gnome Shell: Touchpad right click (bottom right) area does not work Status in gsettings-desktop-schemas package in Ubuntu: Invalid Bug description: The right (second) touchpad click does not work. It ceased to work about three months ago. ubuntu 18,04 aser ex2519 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+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 1797002] Re: all my bluetooth headsets skips terribly after todays update
Thanks Ivan. It appears your bluez and pulseaudio packages last updated on 2018-07-25, so they won't be the cause of any recent regressions. I think this kernel upgrade on 2018-10-09 might be what changed: linux-generic:amd64 (4.15.0.29.31 --> 4.15.0.36.38) Please try downgrading your kernel, like to version 4.14: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1574746] Re: Enable support for libsoxr
The required change to libsoxr is now in 18.10 (and only in 18.10).
However 18.10 is about to be released so it's too late to change
pulseaudio there. We would be aiming for 19.04 and later now. Please
give me a reminder again in November if no further progress has been
made by then.
** Changed in: pulseaudio (Ubuntu)
Status: In Progress => Triaged
--
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/1574746
Title:
Enable support for libsoxr
Status in pulseaudio package in Ubuntu:
Triaged
Bug description:
I'd like to ask to enable support for libsoxr-based resamplers in the
official Ubuntu packages for pulseaudio. The upstream already supports libsoxr
and automatically detects its availability, so the only change really needed is
to add the build dependency to debian/control.
The resamplers based in libsoxr offer better quality and better performace
while introducing more delay compared to the speex resamplers that are used by
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu
16.04 but unfortunately are not enabled at build time ('pulseaudio
--dump-resample-methods' doesn't list them). I've built local packages with
libsoxr and verified that the resampler works as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574746/+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 1797002] Re: all my bluetooth headsets skips terribly after todays update
Here they are, bu today I've tried to update with check box pre-release updates ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+attachment/5199767/+files/history.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1797002] Re: all my bluetooth headsets skips terribly after todays update
and dpkg.log but again, it doesn't work even with fresh installation over formatted partition, can try it again tomorrow ** Attachment added: "dpkg.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+attachment/5199768/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1574746] Re: Enable support for libsoxr
It is 2018-10-11, and it hasn't been done since 2016-04-25
--
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/1574746
Title:
Enable support for libsoxr
Status in pulseaudio package in Ubuntu:
In Progress
Bug description:
I'd like to ask to enable support for libsoxr-based resamplers in the
official Ubuntu packages for pulseaudio. The upstream already supports libsoxr
and automatically detects its availability, so the only change really needed is
to add the build dependency to debian/control.
The resamplers based in libsoxr offer better quality and better performace
while introducing more delay compared to the speex resamplers that are used by
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu
16.04 but unfortunately are not enabled at build time ('pulseaudio
--dump-resample-methods' doesn't list them). I've built local packages with
libsoxr and verified that the resampler works as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574746/+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 1797002] Re: all my bluetooth headsets skips terribly after todays update
Ivan: Please attach a copy of your: /var/log/apt/history.log /var/log/dpkg.log So that we can see what packages changed around 10 October. -- anlag: Please open a new bug by running: ubuntu-bug pulseaudio and also attach the same files requested above to your new bug. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: bluez (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1797124] Re: Xorg crashes
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1797124 Title: Xorg crashes Status in Ubuntu: Incomplete Bug description: Frequent crashes when I; * unlock the screen * resume from suspend Usually, I see the login page, I put my password and then it's 50:50 chance that it will crash. If it crashes, there's a brief flash in screen and then it goes black. I cannot fire up tty with ctrl+alt+[1-7]. I had to reboot in that case (I use SysRq Magic+R,E,I,S,U,B) If it does not crash, then I can login to system, I can see the desktop but it stays unresponsive for 10-30 seconds and then gnome- shell restarts, and then I can start using the windows/programs. Not sure if this is Xorg or gnome-shell or gdm3 problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 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: GNOME Date: Wed Oct 10 16:31:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.15.0-34-generic, x86_64: installed nvidia, 390.87, 4.15.0-36-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-34-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:11cd] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 750M] [1043:11cd] InstallationDate: Installed on 2018-06-01 (131 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N550JV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=d62c0813-bece-408d-8a4c-773ce7fbe368 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
[Touch-packages] [Bug 1797257] Re: remove authentication keys from software-properties-gtk is not working
*** This bug is a duplicate of bug 1656100 *** https://bugs.launchpad.net/bugs/1656100 ** This bug has been marked a duplicate of bug 1656100 Unable to remove signing keys using gnome-software-properties -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1797257 Title: remove authentication keys from software-properties-gtk is not working Status in software-properties package in Ubuntu: New Bug description: Removing authentication keys from Software & Updates is not working. It asked for a password when trying to remove a key, then nothing happens. Tried this on both Ubuntu (gnome) and Ubuntu-Mate and its not working on both distros or DE. It however work from the terminal with "sudo apt-key del" without a problem. Its just that it doesn't work from the GUI. Details: Description: Ubuntu 18.04.1 LTS Release: 18.04 software-properties-gtk: Installed: 0.96.24.32.5 Candidate: 0.96.24.32.5 Version table: *** 0.96.24.32.5 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.96.24.32.1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.5 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 11 07:04:55 2018 InstallationDate: Installed on 2018-10-09 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797257/+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 1775432] Re: Stackswitcher buttons in gnome-software are not themed alike
No gnome-software, o tema dos botões stackswitcher no topo 'Installed' e 'Updates' é diferente de 'All'. O efeito 3D só é visível em 'All' quando selecionado. Os três botões devem ter o mesmo efeito. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1775432 Title: Stackswitcher buttons in gnome-software are not themed alike Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: In gnome-software, the theming of the stackswitcher buttons at the top 'Installed' and 'Updates' is different than 'All'. The 3D effect is only visible in 'All' when selected. The three buttons should have the same effect. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:38:01 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1775432/+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 1775432] Re: Stackswitcher buttons in gnome-software are not themed alike
No gnome-software, o tema dos botões stackswitcher no topo 'Installed' e 'Updates' é diferente de 'All'. O efeito 3D só é visível em 'All' quando selecionado. Os três botões devem ter o mesmo efeito. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1775432 Title: Stackswitcher buttons in gnome-software are not themed alike Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: In gnome-software, the theming of the stackswitcher buttons at the top 'Installed' and 'Updates' is different than 'All'. The 3D effect is only visible in 'All' when selected. The three buttons should have the same effect. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:38:01 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1775432/+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 1775432] Re: Stackswitcher buttons in gnome-software are not themed alike
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1775432 Title: Stackswitcher buttons in gnome-software are not themed alike Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: In gnome-software, the theming of the stackswitcher buttons at the top 'Installed' and 'Updates' is different than 'All'. The 3D effect is only visible in 'All' when selected. The three buttons should have the same effect. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:38:01 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1775432/+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 1797275] [NEW] libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent.
Public bug reported: The binary "gtk-query-immodules-3.0" is absent from package. The package DOES include the man-page for "gtk-query-immodules-3.0", but not the actual utility it documents. I downloaded the source tarball "gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz" and untar-ed it: |$ ls ./ |debian |gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz |$ ls ./debian/libgtk-3-bin* |debian/libgtk-3-bin.install |debian/libgtk-3-bin.links.in |$ cat ./debian/libgtk-3-bin.install |usr/bin/broadwayd |usr/bin/gtk-builder-tool |usr/bin/gtk-launch |usr/bin/gtk-query-settings |usr/share/gettext/its/gtkbuilder.its |usr/share/gettext/its/gtkbuilder.loc |usr/share/man/man1/broadwayd.1 |usr/share/man/man1/gtk-builder-tool.1 |usr/share/man/man1/gtk-launch.1 |usr/share/man/man1/gtk-query-immodules-3.0.1 |usr/share/man/man1/gtk-query-settings.1 Qualifiers: 1) |$ lsb_release -rd |Description: Linux Mint 19 Tara |Release: 19 2) |$ apt-cache policy libgtk-3-bin |libgtk-3-bin: | Installed: 3.22.30-1ubuntu1 | Candidate: 3.22.30-1ubuntu1 | Version table: | *** 3.22.30-1ubuntu1 500 |500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages |100 /var/lib/dpkg/status |$ ls /usr/share/man/man1/gtk-query* |/usr/share/man/man1/gtk-query-immodules-2.0.1.gz |/usr/share/man/man1/gtk-query-immodules-3.0.1.gz |/usr/share/man/man1/gtk-query-settings.1.gz |$ ls /usr/bin/gtk-query* |/usr/bin/gtk-query-settings 3) I am experimenting with development of specialized immodules for GtkEntry widget. I expect to be able to install these additional modules and for my application to access them per the instructions in the Gtk+3 documentation. 4) |$ whereis gtk-query-immodules-3.0 |gtk-query-immodules-3: Thank you! ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: gtk-query-immodules-3.0 immodule libgtk-3-bin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1797275 Title: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent. Status in gtk+3.0 package in Ubuntu: New Bug description: The binary "gtk-query-immodules-3.0" is absent from package. The package DOES include the man-page for "gtk-query-immodules-3.0", but not the actual utility it documents. I downloaded the source tarball "gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz" and untar-ed it: |$ ls ./ |debian |gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz |$ ls ./debian/libgtk-3-bin* |debian/libgtk-3-bin.install |debian/libgtk-3-bin.links.in |$ cat ./debian/libgtk-3-bin.install |usr/bin/broadwayd |usr/bin/gtk-builder-tool |usr/bin/gtk-launch |usr/bin/gtk-query-settings |usr/share/gettext/its/gtkbuilder.its |usr/share/gettext/its/gtkbuilder.loc |usr/share/man/man1/broadwayd.1 |usr/share/man/man1/gtk-builder-tool.1 |usr/share/man/man1/gtk-launch.1 |usr/share/man/man1/gtk-query-immodules-3.0.1 |usr/share/man/man1/gtk-query-settings.1 Qualifiers: 1) |$ lsb_release -rd |Description:Linux Mint 19 Tara |Release:19 2) |$ apt-cache policy libgtk-3-bin |libgtk-3-bin: | Installed: 3.22.30-1ubuntu1 | Candidate: 3.22.30-1ubuntu1 | Version table: | *** 3.22.30-1ubuntu1 500 |500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages |100 /var/lib/dpkg/status |$ ls /usr/share/man/man1/gtk-query* |/usr/share/man/man1/gtk-query-immodules-2.0.1.gz |/usr/share/man/man1/gtk-query-immodules-3.0.1.gz |/usr/share/man/man1/gtk-query-settings.1.gz |$ ls /usr/bin/gtk-query* |/usr/bin/gtk-query-settings 3) I am experimenting with development of specialized immodules for GtkEntry widget. I expect to be able to install these additional modules and for my application to access them per the instructions in the Gtk+3 documentation. 4) |$ whereis gtk-query-immodules-3.0 |gtk-query-immodules-3: Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1797275/+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 1797255] Re: Epson WF-2760 Not working properly
** Description changed: My Epson WF-2670 Network printer is having issues printing correctly on Ubuntu. It prints differently depending on what protocol i use, and what configuration i use. The only configuration that gets it right, is the Driverless IPP printing on Ubuntu 18.04. However using the same Driverless Printing option in Ubuntu 18.10 dose not work properly. When printing the text runs off the side of the page. The printer supports PPD, LDP, IPP, and DNS printing. There is no specific driver for this printer in the repos. There is an official driver on the Epson Website for this printer however it's unmaintained and out of date. As a result it doesn't work. Instead When choosing a setup option in Ubuntu (or any other distro) it automatically selects the generic epson-escpr inkjet Driver. This driver will print. But again, it prints incorrectly with the text going off the side of the page. The driverless IPP printing in Ubuntu 18.04 gets it right. But in 18.10 the same exact configuration prints incorrectly. All other protocols i mentioned all print the same on both versions of Ubuntu, all of which are equally incorrect. Driverless IPP printing in 18.04 is the only one that dose it correctly. This problem locks me to 18.04. Which isn't an immediate problem, But probably will be in the long term. I've included a picture of some test prints. Both are from Ubuntu 18.10. The one on the left is using the epson-escpr Driver using the LDP/passthru option. And the one on the right is using the Default Driverless Printing. You can see the text going off the side of the page on both, and off the bottom of the page on the one on the right. Whatever configuration/package version is being used in Ubuntu 18.04 for Driverless Printing works properly. But in - 18.10 it dose Not. Nor do any of the other configuration Options. + 18.10 it dose Not. Nor do any of the other configuration Options. I can + manually change the page margins in the settings, But this only changes + where the Black border is on those test prints, The text itself stills + runs outside of the margins. Trying to print an Office document or PDF + yields similar results. -- 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/1797255 Title: Epson WF-2760 Not working properly Status in cups package in Ubuntu: New Bug description: My Epson WF-2670 Network printer is having issues printing correctly on Ubuntu. It prints differently depending on what protocol i use, and what configuration i use. The only configuration that gets it right, is the Driverless IPP printing on Ubuntu 18.04. However using the same Driverless Printing option in Ubuntu 18.10 dose not work properly. When printing the text runs off the side of the page. The printer supports PPD, LDP, IPP, and DNS printing. There is no specific driver for this printer in the repos. There is an official driver on the Epson Website for this printer however it's unmaintained and out of date. As a result it doesn't work. Instead When choosing a setup option in Ubuntu (or any other distro) it automatically selects the generic epson-escpr inkjet Driver. This driver will print. But again, it prints incorrectly with the text going off the side of the page. The driverless IPP printing in Ubuntu 18.04 gets it right. But in 18.10 the same exact configuration prints incorrectly. All other protocols i mentioned all print the same on both versions of Ubuntu, all of which are equally incorrect. Driverless IPP printing in 18.04 is the only one that dose it correctly. This problem locks me to 18.04. Which isn't an immediate problem, But probably will be in the long term. I've included a picture of some test prints. Both are from Ubuntu 18.10. The one on the left is using the epson-escpr Driver using the LDP/passthru option. And the one on the right is using the Default Driverless Printing. You can see the text going off the side of the page on both, and off the bottom of the page on the one on the right. Whatever configuration/package version is being used in Ubuntu 18.04 for Driverless Printing works properly. But in 18.10 it dose Not. Nor do any of the other configuration Options. I can manually change the page margins in the settings, But this only changes where the Black border is on those test prints, The text itself stills runs outside of the margins. Trying to print an Office document or PDF yields similar results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1797255/+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 1797257] [NEW] remove authentication keys from software-properties-gtk is not working
Public bug reported: Removing authentication keys from Software & Updates is not working. It asked for a password when trying to remove a key, then nothing happens. Tried this on both Ubuntu (gnome) and Ubuntu-Mate and its not working on both distros or DE. It however work from the terminal with "sudo apt-key del" without a problem. Its just that it doesn't work from the GUI. Details: Description:Ubuntu 18.04.1 LTS Release:18.04 software-properties-gtk: Installed: 0.96.24.32.5 Candidate: 0.96.24.32.5 Version table: *** 0.96.24.32.5 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.96.24.32.1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.5 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 11 07:04:55 2018 InstallationDate: Installed on 2018-10-09 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1797257 Title: remove authentication keys from software-properties-gtk is not working Status in software-properties package in Ubuntu: New Bug description: Removing authentication keys from Software & Updates is not working. It asked for a password when trying to remove a key, then nothing happens. Tried this on both Ubuntu (gnome) and Ubuntu-Mate and its not working on both distros or DE. It however work from the terminal with "sudo apt-key del" without a problem. Its just that it doesn't work from the GUI. Details: Description: Ubuntu 18.04.1 LTS Release: 18.04 software-properties-gtk: Installed: 0.96.24.32.5 Candidate: 0.96.24.32.5 Version table: *** 0.96.24.32.5 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.96.24.32.1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.5 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 11 07:04:55 2018 InstallationDate: Installed on 2018-10-09 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797257/+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 1797255] [NEW] Epson WF-2760 Not working properly
Public bug reported: My Epson WF-2670 Network printer is having issues printing correctly on Ubuntu. It prints differently depending on what protocol i use, and what configuration i use. The only configuration that gets it right, is the Driverless IPP printing on Ubuntu 18.04. However using the same Driverless Printing option in Ubuntu 18.10 dose not work properly. When printing the text runs off the side of the page. The printer supports PPD, LDP, IPP, and DNS printing. There is no specific driver for this printer in the repos. There is an official driver on the Epson Website for this printer however it's unmaintained and out of date. As a result it doesn't work. Instead When choosing a setup option in Ubuntu (or any other distro) it automatically selects the generic epson-escpr inkjet Driver. This driver will print. But again, it prints incorrectly with the text going off the side of the page. The driverless IPP printing in Ubuntu 18.04 gets it right. But in 18.10 the same exact configuration prints incorrectly. All other protocols i mentioned all print the same on both versions of Ubuntu, all of which are equally incorrect. Driverless IPP printing in 18.04 is the only one that dose it correctly. This problem locks me to 18.04. Which isn't an immediate problem, But probably will be in the long term. I've included a picture of some test prints. Both are from Ubuntu 18.10. The one on the left is using the epson-escpr Driver using the LDP/passthru option. And the one on the right is using the Default Driverless Printing. You can see the text going off the side of the page on both, and off the bottom of the page on the one on the right. Whatever configuration/package version is being used in Ubuntu 18.04 for Driverless Printing works properly. But in 18.10 it dose Not. Nor do any of the other configuration Options. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: epson error margins printing setup ** Attachment added: "Test Prints" https://bugs.launchpad.net/bugs/1797255/+attachment/5199708/+files/P_20181008_004236.jpg -- 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/1797255 Title: Epson WF-2760 Not working properly Status in cups package in Ubuntu: New Bug description: My Epson WF-2670 Network printer is having issues printing correctly on Ubuntu. It prints differently depending on what protocol i use, and what configuration i use. The only configuration that gets it right, is the Driverless IPP printing on Ubuntu 18.04. However using the same Driverless Printing option in Ubuntu 18.10 dose not work properly. When printing the text runs off the side of the page. The printer supports PPD, LDP, IPP, and DNS printing. There is no specific driver for this printer in the repos. There is an official driver on the Epson Website for this printer however it's unmaintained and out of date. As a result it doesn't work. Instead When choosing a setup option in Ubuntu (or any other distro) it automatically selects the generic epson-escpr inkjet Driver. This driver will print. But again, it prints incorrectly with the text going off the side of the page. The driverless IPP printing in Ubuntu 18.04 gets it right. But in 18.10 the same exact configuration prints incorrectly. All other protocols i mentioned all print the same on both versions of Ubuntu, all of which are equally incorrect. Driverless IPP printing in 18.04 is the only one that dose it correctly. This problem locks me to 18.04. Which isn't an immediate problem, But probably will be in the long term. I've included a picture of some test prints. Both are from Ubuntu 18.10. The one on the left is using the epson-escpr Driver using the LDP/passthru option. And the one on the right is using the Default Driverless Printing. You can see the text going off the side of the page on both, and off the bottom of the page on the one on the right. Whatever configuration/package version is being used in Ubuntu 18.04 for Driverless Printing works properly. But in 18.10 it dose Not. Nor do any of the other configuration Options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1797255/+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 1419369] Re: Fingerprint reader doesn't work after suspend
I can confirm bug in Ubuntu 16.04 on Lenovo T420. Also fingeprint works after click Switch user on lock screen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1419369 Title: Fingerprint reader doesn't work after suspend Status in lightdm package in Ubuntu: Confirmed Bug description: My fingerprint reader does not work after "waking up" my laptop. This happens on both fingeprint GUI as well as fprint. There is a workaround for fprint, fingeprint GUI crashed everytime. Had to uninstall. Steps to reproduce when using fprint: - go into suspend mode - resume - lightdm greeter says "swipe your finger…" - nothing happens when swiping - Wait until time out - - lightdm asks for password - press enter (without entering any password) - lightdm says again "swipe your finger…" - now it works ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 7 23:54:05 2015 InstallationDate: Installed on 2015-02-03 (4 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1419369/+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 1797097] Re: Missaligned border wit ComboBox in Headerbar
I added a simple python app in the hope that is sufficient for reproducing it. https://github.com/pulseaudio-equalizer-ladspa/equalizer is the actual application i noticed it with. ** Attachment added: "app with combobox as custom headerbar title" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1797097/+attachment/5199704/+files/app.py -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1797097 Title: Missaligned border wit ComboBox in Headerbar Status in ubuntu-themes package in Ubuntu: New Bug description: Hi, with ubuntu-themes_16.10+18.10.20181005 the left border of a GtkComboBox with a GtkTextEntry in the GtkHeaderbar seems to be slightly misaligned leaving an additional white space to its left. The bug isn't visible once the GtkTextEntry gets the focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1797097/+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 1726803] Re: unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess insta
** Changed in: shim-signed (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1726803
Title:
unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-
signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to
install/upgrade: subprocess installed post-installation script
returned error exit status 1)
Status in shim-signed package in Ubuntu:
In Progress
Status in unattended-upgrades package in Ubuntu:
Incomplete
Status in shim-signed source package in Bionic:
Triaged
Status in unattended-upgrades source package in Bionic:
Incomplete
Bug description:
[Impact]
* When Secure Boot is enabled and a new dkms module is installed sim-
signed asks for a new Secure Boot key, or aborts package installation
in non-interactive mode. When unattended-upgrades performed the
upgrade the aborted installation leaves an unconfigured system behind
that may even fail to boot.
* The fix in u-u detects new dkms-related packages and holds them
back from installation.
[Test Case]
1. Set up a fully - or almost fully updated Bionic system.
2. Install packagages to trigger the block:
apt install dkms shim-signed r8168-dkms
3. Fake enabled secure boot:
echo "shim-signed shim/enable_secureboot boolean true" |
debconf-set-selections
4. Add and enable PPA hosting updated dkms package pulling in a new dkms-like
dependency:
add-apt-repository ppa:rbalint/scratch
echo 'Unattended-Upgrade::Allowed-Origins
{"LP-PPA-rbalint-scratch:${distro_codename}";}' >
/etc/apt/apt.conf.d/51unattended-upgrades-all
5. Observe u-u keeping back the new package:
unattended-upgrade --verbose --dry-run --debug
...
Checking: r8168-dkms ([])
pkg new-dkms-dep may trigger secure boot key prompt
sanity check failed
...
[Regression Potential]
* Since the fix is holding back packages from installation it is
expected that systems that would have otherwise broke during the
installation would not receive all updates. Since exact detection of
the installation failure reported here does not seem possible u-u
holds back more packages than it would be absolutely necessary.
* Administrators are expected to set up email notifications about the
updates performed by u-u and act on held back packages.
* Since updates pulling in new packages are fairly rare especially in
the -security pocket which u-u installs from by default unwanted
regressions are unlikely to show up.
[Original Bug Text]
Occurred a minute after logging in
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Oct 24 11:35:53 2017
EFITables:
Oct 24 11:33:04 paddy-laptop kernel: efi: EFI v2.40 by American Megatrends
Oct 24 11:33:04 paddy-laptop kernel: efi: ACPI=0x7866 ACPI
2.0=0x7866 SMBIOS=0xf SMBIOS 3.0=0xf0020 ESRT=0x79360598
Oct 24 11:33:04 paddy-laptop kernel: esrt: Reserving ESRT space from
0x79360598 to 0x793605d0.
Oct 24 11:33:04 paddy-laptop kernel: Secure boot enabled
ErrorMessage: subprocess installed post-installation script returned error
exit status 1
InstallationDate: Installed on 2017-09-11 (42 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.2
apt 1.2.24
SecureBoot: 6 0 0 0 1
SourcePackage: shim-signed
Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
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/shim-signed/+bug/1726803/+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 1797242] Re: apparmor package has inappropriate Breaks/Replaces
You can see the sad, sad, history, in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1756800 Thanks ** Attachment added: "apparmor.postinst" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1797242/+attachment/5199703/+files/apparmor.postinst -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1797242 Title: apparmor package has inappropriate Breaks/Replaces Status in apparmor package in Ubuntu: New Bug description: After the removal of the unity8 stack from the Ubuntu archive, it seems apparmor now has a set of Breaks/Replaces on various components used by unity8, and thus makes using the continued work of the UBports team to get Unity8 usable on PCs, difficult. It also seems quite inappropriate for something as low level as apparmor to have these Breaks/Replaces: Breaks: fcitx-data Breaks: Breaks: Breaks: Breaks: Replaces: fcitx-data It would be great if these could be removed from the package in an update for Ubuntu 18.04 (and preferably in newer versions of Ubuntu as well), so that low level packages in Ubuntu are not preventing downstreams from building upon the platform in such manner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1797242/+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 1726803] Re: unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess insta
** Merge proposal linked:
https://code.launchpad.net/~rbalint/shim/+git/shim-signed/+merge/356440
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1726803
Title:
unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-
signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to
install/upgrade: subprocess installed post-installation script
returned error exit status 1)
Status in shim-signed package in Ubuntu:
In Progress
Status in unattended-upgrades package in Ubuntu:
Incomplete
Status in shim-signed source package in Bionic:
Triaged
Status in unattended-upgrades source package in Bionic:
Incomplete
Bug description:
[Impact]
* When Secure Boot is enabled and a new dkms module is installed sim-
signed asks for a new Secure Boot key, or aborts package installation
in non-interactive mode. When unattended-upgrades performed the
upgrade the aborted installation leaves an unconfigured system behind
that may even fail to boot.
* The fix in u-u detects new dkms-related packages and holds them
back from installation.
[Test Case]
1. Set up a fully - or almost fully updated Bionic system.
2. Install packagages to trigger the block:
apt install dkms shim-signed r8168-dkms
3. Fake enabled secure boot:
echo "shim-signed shim/enable_secureboot boolean true" |
debconf-set-selections
4. Add and enable PPA hosting updated dkms package pulling in a new dkms-like
dependency:
add-apt-repository ppa:rbalint/scratch
echo 'Unattended-Upgrade::Allowed-Origins
{"LP-PPA-rbalint-scratch:${distro_codename}";}' >
/etc/apt/apt.conf.d/51unattended-upgrades-all
5. Observe u-u keeping back the new package:
unattended-upgrade --verbose --dry-run --debug
...
Checking: r8168-dkms ([])
pkg new-dkms-dep may trigger secure boot key prompt
sanity check failed
...
[Regression Potential]
* Since the fix is holding back packages from installation it is
expected that systems that would have otherwise broke during the
installation would not receive all updates. Since exact detection of
the installation failure reported here does not seem possible u-u
holds back more packages than it would be absolutely necessary.
* Administrators are expected to set up email notifications about the
updates performed by u-u and act on held back packages.
* Since updates pulling in new packages are fairly rare especially in
the -security pocket which u-u installs from by default unwanted
regressions are unlikely to show up.
[Original Bug Text]
Occurred a minute after logging in
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Oct 24 11:35:53 2017
EFITables:
Oct 24 11:33:04 paddy-laptop kernel: efi: EFI v2.40 by American Megatrends
Oct 24 11:33:04 paddy-laptop kernel: efi: ACPI=0x7866 ACPI
2.0=0x7866 SMBIOS=0xf SMBIOS 3.0=0xf0020 ESRT=0x79360598
Oct 24 11:33:04 paddy-laptop kernel: esrt: Reserving ESRT space from
0x79360598 to 0x793605d0.
Oct 24 11:33:04 paddy-laptop kernel: Secure boot enabled
ErrorMessage: subprocess installed post-installation script returned error
exit status 1
InstallationDate: Installed on 2017-09-11 (42 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.2
apt 1.2.24
SecureBoot: 6 0 0 0 1
SourcePackage: shim-signed
Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
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/shim-signed/+bug/1726803/+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 1797242] [NEW] apparmor package has inappropriate Breaks/Replaces
Public bug reported: After the removal of the unity8 stack from the Ubuntu archive, it seems apparmor now has a set of Breaks/Replaces on various components used by unity8, and thus makes using the continued work of the UBports team to get Unity8 usable on PCs, difficult. It also seems quite inappropriate for something as low level as apparmor to have these Breaks/Replaces: Breaks: fcitx-data Breaks: Breaks: Breaks: Breaks: Replaces: fcitx-data It would be great if these could be removed from the package in an update for Ubuntu 18.04 (and preferably in newer versions of Ubuntu as well), so that low level packages in Ubuntu are not preventing downstreams from building upon the platform in such manner. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1797242 Title: apparmor package has inappropriate Breaks/Replaces Status in apparmor package in Ubuntu: New Bug description: After the removal of the unity8 stack from the Ubuntu archive, it seems apparmor now has a set of Breaks/Replaces on various components used by unity8, and thus makes using the continued work of the UBports team to get Unity8 usable on PCs, difficult. It also seems quite inappropriate for something as low level as apparmor to have these Breaks/Replaces: Breaks: fcitx-data Breaks: Breaks: Breaks: Breaks: Replaces: fcitx-data It would be great if these could be removed from the package in an update for Ubuntu 18.04 (and preferably in newer versions of Ubuntu as well), so that low level packages in Ubuntu are not preventing downstreams from building upon the platform in such manner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1797242/+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 1797236] Re: network-manager openvpn settings not being saved
I'm unsure whether this is NM or n-m-openvpn. Looks more like NM, since downgrading n-m-openvpn alone didn't seem to change anything. -- 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/1797236 Title: network-manager openvpn settings not being saved Status in network-manager package in Ubuntu: New Status in network-manager-openvpn package in Ubuntu: New Bug description: I'm seeing some weird issue with the new NM + openvpn; if I create a new VPN connection, and add certificate options (verify name exactly, plus TLS auth), these options are not saved, leading to the connection failing. The following versions lead to an invalid connection: ii network-manager 1.12.4-1ubuntu1 amd64 network management framework (daemon and userspace tools) ii network-manager-openvpn 1.8.6-1 amd64 network management framework (OpenVPN plugin core) Reverting to the following versions, things work again: ii network-manager 1.12.2-0ubuntu4 amd64 network management framework (daemon and userspace tools) ii network-manager-openvpn 1.8.4-1 amd64 network management framework (OpenVPN plugin core) If I use an existing connection saved with a prior version of NM, the connection will be successful. If I go open the settings, hit Apply, all advanced TLS settings are wiped. The connection then fails: Oct 10 16:58:52 demeter nm-openvpn[6538]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Oct 10 16:58:52 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used remote address: [AF_INET]91.189.91.19:443 Oct 10 16:58:52 demeter nm-openvpn[6538]: Attempting to establish TCP connection with [AF_INET]91.189.91.19:443 [nonblock] Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP connection established with [AF_INET]91.189.91.19:443 Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link local: (not bound) Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link remote: [AF_INET]xx.xx.xx.xx:443 Oct 10 16:58:53 demeter nm-openvpn[6538]: Connection reset, restarting [0] Oct 10 16:58:53 demeter nm-openvpn[6538]: SIGUSR1[soft,connection-reset] received, process restarting Oct 10 16:58:58 demeter nm-openvpn[6538]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Oct 10 16:58:58 demeter nm-openvpn[6538]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Oct 10 16:58:58 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used remote address: [AF_INET6]2001:67c:1562:0:1::1:443 Oct 10 16:58:58 demeter nm-openvpn[6538]: Attempting to establish TCP connection with [AF_INET6]2001:67c:1562:0:1::1:443 [nonblock] Oct 10 16:58:59 demeter nm-openvpn[6538]: TCP: connect to [AF_INET6]:xxx:xx:xx::xx:443 failed: Network is unreachable Oct 10 16:58:59 demeter nm-openvpn[6538]: SIGUSR1[connection failed(soft),init_instance] received, process restarting Oct 10 16:59:04 demeter nm-openvpn[6538]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1797236/+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 1797236] [NEW] network-manager openvpn settings not being saved
Public bug reported: I'm seeing some weird issue with the new NM + openvpn; if I create a new VPN connection, and add certificate options (verify name exactly, plus TLS auth), these options are not saved, leading to the connection failing. The following versions lead to an invalid connection: ii network-manager 1.12.4-1ubuntu1 amd64 network management framework (daemon and userspace tools) ii network-manager-openvpn 1.8.6-1 amd64 network management framework (OpenVPN plugin core) Reverting to the following versions, things work again: ii network-manager 1.12.2-0ubuntu4 amd64 network management framework (daemon and userspace tools) ii network-manager-openvpn 1.8.4-1 amd64 network management framework (OpenVPN plugin core) If I use an existing connection saved with a prior version of NM, the connection will be successful. If I go open the settings, hit Apply, all advanced TLS settings are wiped. The connection then fails: Oct 10 16:58:52 demeter nm-openvpn[6538]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Oct 10 16:58:52 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used remote address: [AF_INET]91.189.91.19:443 Oct 10 16:58:52 demeter nm-openvpn[6538]: Attempting to establish TCP connection with [AF_INET]91.189.91.19:443 [nonblock] Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP connection established with [AF_INET]91.189.91.19:443 Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link local: (not bound) Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link remote: [AF_INET]xx.xx.xx.xx:443 Oct 10 16:58:53 demeter nm-openvpn[6538]: Connection reset, restarting [0] Oct 10 16:58:53 demeter nm-openvpn[6538]: SIGUSR1[soft,connection-reset] received, process restarting Oct 10 16:58:58 demeter nm-openvpn[6538]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Oct 10 16:58:58 demeter nm-openvpn[6538]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Oct 10 16:58:58 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used remote address: [AF_INET6]2001:67c:1562:0:1::1:443 Oct 10 16:58:58 demeter nm-openvpn[6538]: Attempting to establish TCP connection with [AF_INET6]2001:67c:1562:0:1::1:443 [nonblock] Oct 10 16:58:59 demeter nm-openvpn[6538]: TCP: connect to [AF_INET6]:xxx:xx:xx::xx:443 failed: Network is unreachable Oct 10 16:58:59 demeter nm-openvpn[6538]: SIGUSR1[connection failed(soft),init_instance] received, process restarting Oct 10 16:59:04 demeter nm-openvpn[6538]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1797236 Title: network-manager openvpn settings not being saved Status in network-manager package in Ubuntu: New Status in network-manager-openvpn package in Ubuntu: New Bug description: I'm seeing some weird issue with the new NM + openvpn; if I create a new VPN connection, and add certificate options (verify name exactly, plus TLS auth), these options are not saved, leading to the connection failing. The following versions lead to an invalid connection: ii network-manager 1.12.4-1ubuntu1 amd64 network management framework (daemon and userspace tools) ii network-manager-openvpn 1.8.6-1 amd64 network management framework (OpenVPN plugin core) Reverting to the following versions, things work again: ii network-manager 1.12.2-0ubuntu4 amd64 network management framework (daemon and userspace tools) ii network-manager-openvpn 1.8.4-1 amd64 network management framework (OpenVPN plugin core) If I use an existing connection saved with a prior version of NM, the connection will be successful. If I go open the settings, hit Apply, all advanced TLS settings are wiped. The connection then fails: Oct 10 16:58:52 demeter nm-openvpn[6538]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Oct 10 16:58:52 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used remote address: [AF_INET]91.189.91.19:443 Oct 10 16:58:52 demeter nm-openvpn[6538]: Attempting to establish TCP connection with
[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
So far I highly suspect this commit[1] to be the possible offending one and it would "fit" with the bionic systemd version in Ubuntu[2] vs upstream introduction of the change : $ git describe --contains 006aabbd05 v237~47^2~2 [1] 006aabbd0 mount: mountinfo event is supposed to always arrive before SIGCHLD [2] rmadison systemd | 237-3ubuntu10| bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x systemd | 237-3ubuntu10.3 | bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x -- 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/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Daemon' dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") fuse: device not found, try 'modprobe fuse' first dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Metadata' (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed A connection to the bus can't be made done. Begin: Setting up init... ... done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+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 1795658] Re: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently
Verification done on Xenial. Changing verification tags. -- Testcase) $ cat <" $ dpkg -s systemd | grep ^Version: Version: 229-4ubuntu21.5 $ sudo systemctl start fail-on-restart $ systemctl status -n0 fail-on-restart fail-on-restart.service Loaded: loaded (/etc/systemd/system/fail-on-restart.service; static; vendor preset: enabled) Active: failed (Result: start-limit-hit) since Wed 2018-10-10 20:53:17 UTC; 2min 34s ago Process: 1450 ExecStart=/bin/false (code=exited, status=1/FAILURE) Main PID: 1450 (code=exited, status=1/FAILURE) ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1795658 Title: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] * In case a service unit has repeatedly failed to restart, it should be reported as 'failed' permanently, but currently it's instead reported as 'inactive'. * System monitoring tools that evaluate the status of systemd service units and act upon it (for example: restart service, report permanent failure) are currently misled by information in 'systemctl status .service'. * System management tools based on such information may take wrong and/or sub-optimal actions in the managed systems regarding such service units. * This systemd patch [1] directly addresses this issue (see systemd github PR #3166 [2]), and its code is still effectice in upstream systemd today, without further fixes/changes (the only changes were in doc text and the busname files that were removed, but still without further fixes to this). [Test Case] * This is copied from systemd PR #3166 [2]. * This has been tested by a customer as well, and with its system monitoring and management solution, for interoperability verification. $ cat
[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
So far I highly suspect this commit[1] to be the possible offending one and it would with the bionic systemd version vs upstream introduction of the change : $ git describe --contains 006aabbd05 v237~47^2~2 [1] 006aabbd0 mount: mountinfo event is supposed to always arrive before SIGCHLD -- 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/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Daemon' dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") fuse: device not found, try 'modprobe fuse' first dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Metadata' (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed A connection to the bus can't be made done. Begin: Setting up init... ... done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
I started to look at this problem from scratch since it's been a while
since I have reported it
It seems to go into emergency mode due to a failed attempt to start unit
"tmp.mount" :
# /var/log/boot.log
65 emergency.target: Enqueued job emergency.target/start as 159
66 tmp.mount: Unit entered failed state.
Adding "systemd.mask=tmp.mount" in /tftpboot/pxelinux.cfg/default as a
parameter did the trick to workaround the behaviour :
APPEND initrd=bionic-desktop-amd64/initrd root=/dev/nfs boot=casper
netboot=nfs nfsroot=192.168.100.2:/bionic-desktop-amd64 splash
systemd.mask=tmp.mount systemd.debug-shell=1 systemd.log_level=debug
systemd.log_target=console console=ttyS0,38400 console=tty1 --
Note:
- I did the test by curiosity w/ Artful/17.10 (systemd-234) and it works, so
it's possibly something between v234 and v237 which introduced the behaviour
for tmp.mount, a change in mount, ...
- Problem is also reproducible in Cosmic, and journalctl was a little bit more
verbose in Cosmic than it was for Bionic in my testing :
$ journalctl -a -u tmp.mount
-- Logs begin at Wed 2018-10-10 20:15:36 UTC, end at Wed 2018-10-10 20:15:43
UTC. --
Oct 10 20:15:36 ubuntu systemd[1]: tmp.mount: Directory /tmp to mount over is
not empty, mounting anyway.
Oct 10 20:15:36 ubuntu systemd[1]: Mounting /tmp...
Oct 10 20:15:36 ubuntu systemd[1]: tmp.mount: Mount process finished, but there
is no mount.
Oct 10 20:15:36 ubuntu systemd[1]: tmp.mount: Failed with result 'protocol'.
Oct 10 20:15:36 ubuntu systemd[1]: Failed to mount /tmp.
# src/core/mount.c
802 static void mount_enter_dead(Mount *m, MountResult f) {
803 assert(m);
804
805 if (m->result == MOUNT_SUCCESS)
806 m->result = f;
807
808 if (m->result != MOUNT_SUCCESS)
809 log_unit_warning(UNIT(m), "Failed with result '%s'.",
mount_result_to_string(m->result));
...
1282 switch (m->state) {
1283
1284 case MOUNT_MOUNTING:
1285 /* Our mount point has not appeared in mountinfo. Something went wrong. */
1286
1287 if (f == MOUNT_SUCCESS) {
1288 /* Either /bin/mount has an unexpected definition of success,
1289 * or someone raced us and we lost. */
1290 log_unit_warning(UNIT(m), "Mount process finished, but there is no
mount.");
1291 f = MOUNT_FAILURE_PROTOCOL;
1292 }
and m->result is indeed equalt to "MOUNT_FAILURE_PROTOCOL" ^
1955 [MOUNT_FAILURE_PROTOCOL] = "protocol",
I'll try to instrument things and create a custom ISO for further
debugging/testing. This is where am at the moment.
- Eric
--
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/1755863
Title:
netbooting the bionic live CD over NFS goes straight to maintenance
mode :
Status in casper package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Bug description:
netbooting the bionic live CD[1] over NFS goes straight to maintenance
mode :
[1] http://cdimage.ubuntu.com/daily-live/current/
# casper.log
Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0'
(uid=999 pid=569 comm="" label="unconfined")
dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service
'org.gtk.vfs.Daemon'
dbus-daemon[568]: [session uid=999 pid=568] Activating service
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm=""
label="unconfined")
fuse: device not found, try 'modprobe fuse' first
dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service
'org.gtk.vfs.Metadata'
(gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
failed
(gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
A connection to the bus can't be made
done.
Begin: Setting up init... ... done.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+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 1797192] Re: package libapparmor-perl 2.12-4ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: fsys-tarfile-error ** Changed in: apparmor (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1797192 Title: package libapparmor-perl 2.12-4ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in apparmor package in Ubuntu: Invalid Bug description: no knowledge ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libapparmor-perl 2.12-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: libapparmor-perl:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 10 19:47:09 2018 DpkgTerminalLog: Gør klar til at udpakke .../libapparmor-perl_2.12-4ubuntu5.1_amd64.deb ... Udpakker libapparmor-perl (2.12-4ubuntu5.1) over (2.12-4ubuntu5) ... dpkg-deb: fejl: kunne ikke læse arkivet '/var/cache/apt/archives/libapparmor-perl_2.12-4ubuntu5.1_amd64.deb': Ingen sådan fil eller filkatalog dpkg: fejl under behandling af arkivet /var/cache/apt/archives/libapparmor-perl_2.12-4ubuntu5.1_amd64.deb (--unpack): dpkg-deb --fsys-tarfile subprocess returned error exit status 2 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-03-15 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=143ba28a-b1c2-455c-8a76-303a87108ad9 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apparmor Title: package libapparmor-perl 2.12-4ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-04-27 (166 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1797192/+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 1795305] Re: package base-files 10.1ubuntu2.2 [modified: usr/share/doc/base-files/changelog.gz] failed to install/upgrade: package base-files is not ready for configuration canno
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: base-files (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1795305 Title: package base-files 10.1ubuntu2.2 [modified: usr/share/doc/base- files/changelog.gz] failed to install/upgrade: package base-files is not ready for configuration cannot configure (current status 'half- installed') Status in base-files package in Ubuntu: Confirmed Bug description: i was trying to install gcc and I got this error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: base-files 10.1ubuntu2.2 [modified: usr/share/doc/base-files/changelog.gz] ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Oct 1 12:53:35 2018 Dependencies: DpkgHistoryLog: Start-Date: 2018-10-01 12:53:35 Commandline: apt install gcc Requested-By: pragati (1000) Install: libgcc-7-dev:amd64 (7.3.0-16ubuntu3, automatic), libmpx2:amd64 (8-20180414-1ubuntu2, automatic), linux-libc-dev:amd64 (4.15.0-34.37, automatic), libc6-dev:amd64 (2.27-3ubuntu1, automatic), libitm1:amd64 (8-20180414-1ubuntu2, automatic), gcc:amd64 (4:7.3.0-3ubuntu2), libcilkrts5:amd64 (7.3.0-16ubuntu3, automatic), libasan4:amd64 (7.3.0-16ubuntu3, automatic), libquadmath0:amd64 (8-20180414-1ubuntu2, automatic), libtsan0:amd64 (8-20180414-1ubuntu2, automatic), libubsan0:amd64 (7.3.0-16ubuntu3, automatic), gcc-7:amd64 (7.3.0-16ubuntu3, automatic), liblsan0:amd64 (8-20180414-1ubuntu2, automatic), manpages-dev:amd64 (4.15-1, automatic), libc-dev-bin:amd64 (2.27-3ubuntu1, automatic), libatomic1:amd64 (8-20180414-1ubuntu2, automatic) DpkgTerminalLog: [1mdpkg:[0m error processing package base-files (--configure): package base-files is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package base-files is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-09-17 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: base-files Title: package base-files 10.1ubuntu2.2 [modified: usr/share/doc/base-files/changelog.gz] failed to install/upgrade: package base-files is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1795305/+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 1797221] [NEW] Update to 2.13.1 on next cycle
Public bug reported: Updating is not risk free and there is no reason to do that now, that's for next cycle ** Affects: fontconfig (Ubuntu) Importance: Wishlist Status: Invalid ** Tags: upgrade-software-version version-blocked-ff ** Changed in: fontconfig (Ubuntu) Status: New => Invalid -- 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/1797221 Title: Update to 2.13.1 on next cycle Status in fontconfig package in Ubuntu: Invalid Bug description: Updating is not risk free and there is no reason to do that now, that's for next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1797221/+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 1797224] [NEW] Stay on 2.0 for cosmic, update next cycle
Public bug reported: The new version requires the MIR situation to be sorted out ** Affects: tracker (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: upgrade-software-version version-blocked-ff ** Changed in: tracker (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1797224 Title: Stay on 2.0 for cosmic, update next cycle Status in tracker package in Ubuntu: Triaged Bug description: The new version requires the MIR situation to be sorted out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1797224/+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 1797222] [NEW] Update to 2.13.1 on next cycle
Public bug reported: Updating is not risk free and there is no reason to do that now, that's for next cycle ** Affects: fontconfig (Ubuntu) Importance: Wishlist Status: New ** Tags: upgrade-software-version version-blocked-ff -- 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/1797222 Title: Update to 2.13.1 on next cycle Status in fontconfig package in Ubuntu: New Bug description: Updating is not risk free and there is no reason to do that now, that's for next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1797222/+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 1790613] Re: Regression: packagekit crashes updating itself to a new version
** Summary changed: - Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 + Regression: packagekit crashes updating itself to a new version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to a new version Status in packagekit package in Ubuntu: Triaged Status in plasma-discover package in Ubuntu: Confirmed Status in packagekit source package in Bionic: Triaged Status in plasma-discover source package in Bionic: Confirmed Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: Fix Released Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Status in strongswan package in Ubuntu: Invalid Status in avahi source package in Bionic: Fix Released Status in bind9 source package in Bionic: Confirmed Status in avahi source package in Cosmic: Fix Released Status in bind9 source package in Cosmic: Confirmed Status in avahi package in Debian: New Bug description: [Impact] * Network connections for some users fail (in some cases a direct interface, in others when connecting a VPN) because the 'host' command to check for .local in DNS called by /usr/lib/avahi/avahi-daemon- check-dns.sh never times out like it should - leaving the script hanging indefinitely blocking interface up and start-up. This appears to be a bug in host caused in some circumstances however we implement a workaround to call it under 'timeout' as the issue with 'host' has not easily been identified, and in any case acts as a fall-back. [Test Case] * Multiple people have been unable to create a reproducer on a generic machine (e.g. it does not occur in a VM), I have a specific machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM) by simply "ifdown br0; ifup br0" and there are clearly 10s of other users affected in varying circumstances that all involve the same symptoms but no clear test case exists. Best I can suggest is that I test the patch on my system to ensure it works as expected, and the change is only 1 line which is fairly easily auditible and understandable. [Regression Potential] * The change is a single line change to the shell script to call host with "timeout". When tested on working and non-working system this appears to function as expected. I believe the regression potential for this is subsequently low. * In attempt to anticipate possible issues, I checked that the timeout command is in the same path (/usr/bin) as the host command that is already called without a path, and the coreutils package (which contains timeout) is an Essential package. I also checked that timeout is not a built-in in bash, for those that have changed /bin/sh to bash (just in case). [Other Info] * N/A [Original Bug Description] On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0 liam@liam-lat:~$ ping 172.29.88.11 PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data. ^C --- 172.29.88.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3054ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:11:33 2018 InstallationDate: Installed on 2017-06-15 (258 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago) To manage notifications about this bug go to:
[Touch-packages] [Bug 400766] Re: ubuntu 9.04 installation problem
** Package changed: libgcrypt11 (Ubuntu) => libgcrypt20 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgcrypt11 in Ubuntu. https://bugs.launchpad.net/bugs/400766 Title: ubuntu 9.04 installation problem Status in libgcrypt20 package in Ubuntu: New Bug description: Binary package hint: libgcrypt11 Not installated this pack until ubuntu 9.04 update. ProblemType: Package Architecture: i386 Dependencies: libgcc1 1:4.3.2-1ubuntu12 libgpg-error0 1.4-2ubuntu7 gcc-4.3-base 4.3.2-1ubuntu12 findutils 4.4.0-2ubuntu3 libc6 2.8~20080505-0ubuntu9 DistroRelease: Ubuntu 8.10 ErrorMessage: ErrorMessage: A(z) libgcrypt11 csomag már települt és be van állítva Package: libgcrypt11 1.4.1-1ubuntu1 SourcePackage: libgcrypt11 Title: package libgcrypt11 1.4.1-1ubuntu1 failed to install/upgrade: Uname: Linux 2.6.27-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt20/+bug/400766/+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 1771340] Re: sshd failed on config reload
@tronde, I just tried and the fix worked for me. With the proposed package: root@xenial-ssh-reload:~# ps fxaw PID TTY STAT TIME COMMAND 1 ?Ss 0:02 /sbin/init 55 ?Ss 0:00 /lib/systemd/systemd-journald ... 2443 ?Ss 0:00 /usr/sbin/sshd -D Note the sshd pid: 2443 Reload fails after the config file is corrupted, as expected: root@xenial-ssh-reload:~# echo "blah blah" >>/etc/ssh/sshd_config root@xenial-ssh-reload:~# systemctl reload ssh Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. But service is still running as before, same pid: root@xenial-ssh-reload:~# ps fxaw PID TTY STAT TIME COMMAND 1 ?Ss 0:02 /sbin/init ... 2443 ?Ss 0:00 /usr/sbin/sshd -D And status agrees: root@xenial-ssh-reload:~# systemctl status ssh ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: active (running) (Result: exit-code) since Wed 2018-10-10 18:00:30 UTC; 1min 55s ago Process: 2491 ExecReload=/usr/sbin/sshd -t (code=exited, status=255) Process: 2442 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Main PID: 2443 (sshd) Tasks: 1 Memory: 1.5M CPU: 24ms CGroup: /system.slice/ssh.service └─2443 /usr/sbin/sshd -D Oct 10 18:00:30 xenial-ssh-reload systemd[1]: Starting OpenBSD Secure Shell server... Oct 10 18:00:30 xenial-ssh-reload sshd[2443]: Server listening on 0.0.0.0 port 22. Oct 10 18:00:30 xenial-ssh-reload sshd[2443]: Server listening on :: port 22. Oct 10 18:00:30 xenial-ssh-reload systemd[1]: Started OpenBSD Secure Shell server. Oct 10 18:01:01 xenial-ssh-reload systemd[1]: Reloading OpenBSD Secure Shell server. Oct 10 18:01:01 xenial-ssh-reload sshd[2491]: /etc/ssh/sshd_config: line 89: Bad configuration option: blah Oct 10 18:01:01 xenial-ssh-reload sshd[2491]: /etc/ssh/sshd_config: terminating, 1 bad configuration options Oct 10 18:01:01 xenial-ssh-reload systemd[1]: ssh.service: Control process exited, code=exited status=255 Oct 10 18:01:01 xenial-ssh-reload systemd[1]: Reload failed for OpenBSD Secure Shell server. Note how it logged that there was a bad config option (as a result of calling sshd -t before the actual reload). Could you please double check? For me, this update is fine. -- 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/1771340 Title: sshd failed on config reload Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Fix Committed Status in openssh package in Debian: Fix Released Bug description: [Impact] sshd doesn't check the configuration when reloading. If a user generates an invalid configuration file, sshd will shut down and not come back up when the user issues a reload. [Test Case] $ lxc launch ubuntu:xenial tester $ lxc exec tester bash # echo "blah blah" >>/etc/ssh/sshd_config # systemctl reload sshd Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. # systemctl status ssh.service ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-08-21 18:15:41 UTC; 19s ago * The service should have checked the config file, failed to reload, but remained active in its current configuration. In this case ssh has shut down. [Regression Potential] This code will only trigger on an invalid configuration file (in which case sshd would not load anyway), so there should be no regressions. [Other Info] autopkgtest [13:45:46]: test regress: ---] autopkgtest [13:45:47]: test regress: - - - - - - - - - - results - - - - - - - - - - regress PASS autopkgtest [13:45:47]: summary regress PASS [Original Description] After adding some lines to /etc/ssh/sshd_config I tried to reload the configuration with the command: ``` sudo systemctl reload sshd ``` No error message was returned. So I assumed that the sshd was running with the current config. But `sudo systemctl status sshd` told me that the service failed due to a wrong option in /etc/ssh/sshd_config. Please see the following output: ~~~ :~$ sudo vim /etc/ssh/sshd_config :~$ sudo systemctl reload sshd :~$ sudo systemctl status sshd ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s ago Process: 12089 ExecReload=/bin/kill
Re: [Touch-packages] [Bug 1069959] Re: HP 8500 skips printing about 3/32 inch of top of document
GF, As far as I can tell the problem is now gone. There is definitely no problem using the HP driver which names the printer as somethng-Officejet-Pro_8500-A910. The other one (which names it as Officejet_Pro_8500_A910_174835_ and I think is the new generic printer) doesn't print as close to the margins but does not seem to move the image down 3/32 which used to be the problem. Thanks for keeping track. Keith On Wed, Oct 10, 2018 at 12:30 AM Launchpad Bug Tracker < 1069...@bugs.launchpad.net> wrote: > [Expired for cups (Ubuntu) because there has been no activity for 60 > days.] > > ** Changed in: cups (Ubuntu) >Status: Incomplete => Expired > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1069959 > > Title: > HP 8500 skips printing about 3/32 inch of top of document > > Status in cups package in Ubuntu: > Expired > > Bug description: > The top few pixels of anything printed from Evolution, Firefox, > LibreOffice applications, Shotwell, and probably others are missing on > the printout with HP 8500A on wifi. The problem does not occur with > "lpr". Note that this is the logical top but could be any of the four > sides of the paper. > > ProblemType: Bug > DistroRelease: Ubuntu 12.10 > Package: cups 1.6.1-0ubuntu11 > ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 > Uname: Linux 3.5.0-17-generic i686 > NonfreeKernelModules: wl > ApportVersion: 2.6.1-0ubuntu3 > Architecture: i386 > CupsErrorLog: >W [22/Oct/2012:08:43:35 -0400] CreateProfile failed: > org.freedesktop.ColorManager.AlreadyExists:profile id 'HP-8500-Gray..' > already exists >W [22/Oct/2012:08:43:35 -0400] CreateProfile failed: > org.freedesktop.ColorManager.AlreadyExists:profile id 'HP-8500-RGB..' > already exists >W [22/Oct/2012:08:43:35 -0400] CreateDevice failed: > org.freedesktop.ColorManager.AlreadyExists:device id 'cups-HP-8500' already > exists > Date: Mon Oct 22 14:40:33 2012 > InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release > i386 (20101007) > KernLog: > > Lpstat: device for HP-8500: hp:/net/Officejet_Pro_8500_A910?zc=HPOccam > MachineType: Hewlett-Packard HP Mini 110-1100 > Papersize: letter > PpdFiles: HP-8500: HP Officejet Pro 8500 a910, hpcups 3.12.6 > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic > root=UUID=a22204da-1373-4d36-878a-46dd58edb287 ro quiet nosplash > resume=UUID=34000a46-658f-4470-89ac-463117af72af > SourcePackage: cups > UpgradeStatus: Upgraded to quantal on 2012-10-20 (1 days ago) > dmi.bios.date: 08/27/2009 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: 308F0 Ver. F.15 > dmi.board.name: 308F > dmi.board.vendor: Hewlett-Packard > dmi.board.version: KBC Version 02.10 > dmi.chassis.asset.tag: CNU9371TT7 > dmi.chassis.type: 10 > dmi.chassis.vendor: Inventec > dmi.modalias: > dmi:bvnHewlett-Packard:bvr308F0Ver.F.15:bd08/27/2009:svnHewlett-Packard:pnHPMini110-1100:pvr039511001B030:rvnHewlett-Packard:rn308F:rvrKBCVersion02.10:cvnInventec:ct10:cvr: > dmi.product.name: HP Mini 110-1100 > dmi.product.version: 039511001B030 > dmi.sys.vendor: Hewlett-Packard > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1069959/+subscriptions > -- 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/1069959 Title: HP 8500 skips printing about 3/32 inch of top of document Status in cups package in Ubuntu: Expired Bug description: The top few pixels of anything printed from Evolution, Firefox, LibreOffice applications, Shotwell, and probably others are missing on the printout with HP 8500A on wifi. The problem does not occur with "lpr". Note that this is the logical top but could be any of the four sides of the paper. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 CupsErrorLog: W [22/Oct/2012:08:43:35 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP-8500-Gray..' already exists W [22/Oct/2012:08:43:35 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP-8500-RGB..' already exists W [22/Oct/2012:08:43:35 -0400] CreateDevice failed: org.freedesktop.ColorManager.AlreadyExists:device id 'cups-HP-8500' already exists Date: Mon Oct 22 14:40:33 2012 InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007) KernLog: Lpstat: device for HP-8500:
[Touch-packages] [Bug 1797192] [NEW] package libapparmor-perl 2.12-4ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: no knowledge ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libapparmor-perl 2.12-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: libapparmor-perl:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 10 19:47:09 2018 DpkgTerminalLog: Gør klar til at udpakke .../libapparmor-perl_2.12-4ubuntu5.1_amd64.deb ... Udpakker libapparmor-perl (2.12-4ubuntu5.1) over (2.12-4ubuntu5) ... dpkg-deb: fejl: kunne ikke læse arkivet '/var/cache/apt/archives/libapparmor-perl_2.12-4ubuntu5.1_amd64.deb': Ingen sådan fil eller filkatalog dpkg: fejl under behandling af arkivet /var/cache/apt/archives/libapparmor-perl_2.12-4ubuntu5.1_amd64.deb (--unpack): dpkg-deb --fsys-tarfile subprocess returned error exit status 2 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-03-15 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=143ba28a-b1c2-455c-8a76-303a87108ad9 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apparmor Title: package libapparmor-perl 2.12-4ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-04-27 (166 days ago) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1797192 Title: package libapparmor-perl 2.12-4ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in apparmor package in Ubuntu: New Bug description: no knowledge ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libapparmor-perl 2.12-4ubuntu5.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: libapparmor-perl:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 10 19:47:09 2018 DpkgTerminalLog: Gør klar til at udpakke .../libapparmor-perl_2.12-4ubuntu5.1_amd64.deb ... Udpakker libapparmor-perl (2.12-4ubuntu5.1) over (2.12-4ubuntu5) ... dpkg-deb: fejl: kunne ikke læse arkivet '/var/cache/apt/archives/libapparmor-perl_2.12-4ubuntu5.1_amd64.deb': Ingen sådan fil eller filkatalog dpkg: fejl under behandling af arkivet /var/cache/apt/archives/libapparmor-perl_2.12-4ubuntu5.1_amd64.deb (--unpack): dpkg-deb --fsys-tarfile subprocess returned error exit status 2 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-03-15 (209 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=143ba28a-b1c2-455c-8a76-303a87108ad9 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apparmor Title: package libapparmor-perl 2.12-4ubuntu5.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-04-27 (166 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1797192/+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 1797097] Re: Missaligned border wit ComboBox in Headerbar
Mh, I don't see this in evince... Where can i reproduce this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1797097 Title: Missaligned border wit ComboBox in Headerbar Status in ubuntu-themes package in Ubuntu: New Bug description: Hi, with ubuntu-themes_16.10+18.10.20181005 the left border of a GtkComboBox with a GtkTextEntry in the GtkHeaderbar seems to be slightly misaligned leaving an additional white space to its left. The bug isn't visible once the GtkTextEntry gets the focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1797097/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD
I started a kernel bisect between v4.14 final and v4.15-rc1. The kernel bisect will require testing of about 7-10 test kernels. I built the first test kernel, up to the following commit: 1be2172e96e33bfa22a5c7a651f768ef30ce3984 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1777674 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
Hello Damiön, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Committed Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1762385] Re: dell_wmi: Unknown key codes
Hello Dmitriy, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+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 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial
Hello Alex, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1738153 Title: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Artful: Won't Fix Bug description: [Impact] dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 0x100150, so need to add a new mapping for it. related commit: https://github.com/systemd/systemd/pull/5012 [Test Case] 1. install the udev package which applied patch. 2. check if Microphone mute hotkey works. 3. if it not works, please provide the log of evtest. [Regression Potential] low regression potential, because it just add one more mapping. also affect: LP: #1736352 LP: #1740080 LP: #1734609 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1738153/+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 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
Hello errors.ubuntu.com, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+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 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
Hello Nick, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in debhelper source package in Xenial: Won't Fix Status in rsyslog source package in Xenial: Invalid Status in systemd source package in Xenial: Fix Committed Status in debhelper source package in Artful: Won't Fix Status in rsyslog source package in Artful: Invalid Status in systemd source package in Artful: Won't Fix Status in debhelper source package in Bionic: Won't Fix Status in rsyslog source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Released Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if rsyslog is installed (default) [Resolution] Ensure that dh_installinit does not "helpfully" generate partial systemd-tmpfiles snippets in systemd package postinst. Ensure that a generic systemd-tmpfiles call is done in systemd postinst, which takes into account /all/ configurations, not just some. [Regression Potential] * This fix was already tested in bionic and works well there. * Bad autogenerated calls to systemd-tmpfiles are removed from systemd postinst, and replaced by a call that takes all configs into account, thus this is a very safe thing to do - and simply repeats what is done on boot, thus is as safe as it gets. [Test Case] 1. Launch xenila container 2. ls -latr /var 3. apt install --reinstall systemd 4. ls -latr /var The ownership, group and permissions for /var/log should remain the same. To manage notifications about this bug go to: https://bugs.launchpad.net/debhelper/+bug/1748147/+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 1795658] Re: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently
Hello Mauricio, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1795658 Title: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] * In case a service unit has repeatedly failed to restart, it should be reported as 'failed' permanently, but currently it's instead reported as 'inactive'. * System monitoring tools that evaluate the status of systemd service units and act upon it (for example: restart service, report permanent failure) are currently misled by information in 'systemctl status .service'. * System management tools based on such information may take wrong and/or sub-optimal actions in the managed systems regarding such service units. * This systemd patch [1] directly addresses this issue (see systemd github PR #3166 [2]), and its code is still effectice in upstream systemd today, without further fixes/changes (the only changes were in doc text and the busname files that were removed, but still without further fixes to this). [Test Case] * This is copied from systemd PR #3166 [2]. * This has been tested by a customer as well, and with its system monitoring and management solution, for interoperability verification. $ cat
[Touch-packages] [Bug 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
Note: the Cosmic fix for this is in the unapproved queue, and could in theory be rejected by the release team. The Xenial SRU should land in updates only once Cosmic is resolved. -- 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/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+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 1796788] Re: resize2fs: Illegal indirect block found while trying to resize
Note a file system which is significantly shrunk --- which tends to be the case with resize2fs -M --- is going to have files fragmented which will have performance implications. It's not clear to me what you are trying to optimize for --- I assume you're just wanting to save on download bandwidth so you want a highly compressed image? You might want to consider using a raw qemu image, e.g: e2image -Q /dev/sda1 /tmp/sda1.qcow bzip /tmp/sda1.qcow # optional which can then be unpacked via: bunzip /tmp/sda1.qcow.bz2 e2image -r /dev/sda1.qcow /dev/sda1 You can of course also use qemu-img from the qemu package. e2image -Q is a bit more efficient though since it will only include blocks which are in use in the file system, where as qemu-img is not aware of the underlying file system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1796788 Title: resize2fs: Illegal indirect block found while trying to resize Status in e2fsprogs package in Ubuntu: Confirmed Bug description: The new resize2fs(1.43+) failed to resize attached image file, and e2fsck didn't report any error before the resizing. Test steps: 1/ e2fsck -fy userdata.img 2/ resize2fs userdata.img 220M Result: When using resize2fs from e2fsprogs 1.43+(tested 1.43.4/1.43.5/1.44.4), it would abort with: Resizing the filesystem on userdata.img to 225280 (1k) blocks. resize2fs: Illegal indirect block found while trying to resize userdata.img Please run 'e2fsck -fy userdata.img' to fix the filesystem after the aborted resize operation. More information: 1/ The image is generated on xenial with genext2fs 2/ It works well on xenial with e2fsprogs 1.42.13-1ubuntu1 3/ It works well when resizing with a size less than 220M, for example "resize2fs userdata.img 219M" 4/ online resize works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1796788/+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 1797159] [NEW] package gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1 failed to install/upgrade: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它
Public bug reported: I can't install the package,so many other package I also can't install.I hope the bug can be solved quickly. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 AptOrdering: apparmor:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 10 23:15:41 2018 DpkgHistoryLog: Start-Date: 2018-10-10 23:15:36 Commandline: /usr/bin/unattended-upgrade Upgrade: apparmor:amd64 (2.12-4ubuntu5, 2.12-4ubuntu5.1) ErrorMessage: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它 InstallationDate: Installed on 2018-09-18 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: gst-plugins-good1.0 Title: package gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1 failed to install/upgrade: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1797159 Title: package gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1 failed to install/upgrade: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它 Status in gst-plugins-good1.0 package in Ubuntu: New Bug description: I can't install the package,so many other package I also can't install.I hope the bug can be solved quickly. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 AptOrdering: apparmor:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 10 23:15:41 2018 DpkgHistoryLog: Start-Date: 2018-10-10 23:15:36 Commandline: /usr/bin/unattended-upgrade Upgrade: apparmor:amd64 (2.12-4ubuntu5, 2.12-4ubuntu5.1) ErrorMessage: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它 InstallationDate: Installed on 2018-09-18 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: gst-plugins-good1.0 Title: package gstreamer1.0-pulseaudio:amd64 1.14.1-1ubuntu1~ubuntu18.04.1 failed to install/upgrade: 该软件包正处于非常不稳定的状态； 您最好在配置它之前，先重新安装它 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1797159/+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 1797145] [NEW] package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: I was trying to run apt upgrade when i got this ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 10 15:13:24 2018 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-10-02 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess 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 bionic -- 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/1797145 Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I was trying to run apt upgrade when i got this ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 10 15:13:24 2018 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-10-02 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess 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/1797145/+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 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial
> low regression potential, because it just add one more mapping. The patch uploaded also removes the old mapping. Is there any possibility that this will regress some users? How would one test for this? -- 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/1738153 Title: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Artful: Won't Fix Bug description: [Impact] dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 0x100150, so need to add a new mapping for it. related commit: https://github.com/systemd/systemd/pull/5012 [Test Case] 1. install the udev package which applied patch. 2. check if Microphone mute hotkey works. 3. if it not works, please provide the log of evtest. [Regression Potential] low regression potential, because it just add one more mapping. also affect: LP: #1736352 LP: #1740080 LP: #1734609 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1738153/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1726803] Re: unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess insta
@vorlon My bad, thought that a generic solution would be useful in u-u,
but now I'm implementing now the special case.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1726803
Title:
unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-
signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to
install/upgrade: subprocess installed post-installation script
returned error exit status 1)
Status in shim-signed package in Ubuntu:
New
Status in unattended-upgrades package in Ubuntu:
Incomplete
Status in shim-signed source package in Bionic:
Triaged
Status in unattended-upgrades source package in Bionic:
Incomplete
Bug description:
[Impact]
* When Secure Boot is enabled and a new dkms module is installed sim-
signed asks for a new Secure Boot key, or aborts package installation
in non-interactive mode. When unattended-upgrades performed the
upgrade the aborted installation leaves an unconfigured system behind
that may even fail to boot.
* The fix in u-u detects new dkms-related packages and holds them
back from installation.
[Test Case]
1. Set up a fully - or almost fully updated Bionic system.
2. Install packagages to trigger the block:
apt install dkms shim-signed r8168-dkms
3. Fake enabled secure boot:
echo "shim-signed shim/enable_secureboot boolean true" |
debconf-set-selections
4. Add and enable PPA hosting updated dkms package pulling in a new dkms-like
dependency:
add-apt-repository ppa:rbalint/scratch
echo 'Unattended-Upgrade::Allowed-Origins
{"LP-PPA-rbalint-scratch:${distro_codename}";}' >
/etc/apt/apt.conf.d/51unattended-upgrades-all
5. Observe u-u keeping back the new package:
unattended-upgrade --verbose --dry-run --debug
...
Checking: r8168-dkms ([])
pkg new-dkms-dep may trigger secure boot key prompt
sanity check failed
...
[Regression Potential]
* Since the fix is holding back packages from installation it is
expected that systems that would have otherwise broke during the
installation would not receive all updates. Since exact detection of
the installation failure reported here does not seem possible u-u
holds back more packages than it would be absolutely necessary.
* Administrators are expected to set up email notifications about the
updates performed by u-u and act on held back packages.
* Since updates pulling in new packages are fairly rare especially in
the -security pocket which u-u installs from by default unwanted
regressions are unlikely to show up.
[Original Bug Text]
Occurred a minute after logging in
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Oct 24 11:35:53 2017
EFITables:
Oct 24 11:33:04 paddy-laptop kernel: efi: EFI v2.40 by American Megatrends
Oct 24 11:33:04 paddy-laptop kernel: efi: ACPI=0x7866 ACPI
2.0=0x7866 SMBIOS=0xf SMBIOS 3.0=0xf0020 ESRT=0x79360598
Oct 24 11:33:04 paddy-laptop kernel: esrt: Reserving ESRT space from
0x79360598 to 0x793605d0.
Oct 24 11:33:04 paddy-laptop kernel: Secure boot enabled
ErrorMessage: subprocess installed post-installation script returned error
exit status 1
InstallationDate: Installed on 2017-09-11 (42 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.2
apt 1.2.24
SecureBoot: 6 0 0 0 1
SourcePackage: shim-signed
Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
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/shim-signed/+bug/1726803/+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 1771340] Re: sshd failed on config reload
** Changed in: openssh (Ubuntu Xenial) Assignee: Karl Stenerud (kstenerud) => Andreas Hasenack (ahasenack) -- 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/1771340 Title: sshd failed on config reload Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Fix Committed Status in openssh package in Debian: Fix Released Bug description: [Impact] sshd doesn't check the configuration when reloading. If a user generates an invalid configuration file, sshd will shut down and not come back up when the user issues a reload. [Test Case] $ lxc launch ubuntu:xenial tester $ lxc exec tester bash # echo "blah blah" >>/etc/ssh/sshd_config # systemctl reload sshd Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. # systemctl status ssh.service ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-08-21 18:15:41 UTC; 19s ago * The service should have checked the config file, failed to reload, but remained active in its current configuration. In this case ssh has shut down. [Regression Potential] This code will only trigger on an invalid configuration file (in which case sshd would not load anyway), so there should be no regressions. [Other Info] autopkgtest [13:45:46]: test regress: ---] autopkgtest [13:45:47]: test regress: - - - - - - - - - - results - - - - - - - - - - regress PASS autopkgtest [13:45:47]: summary regress PASS [Original Description] After adding some lines to /etc/ssh/sshd_config I tried to reload the configuration with the command: ``` sudo systemctl reload sshd ``` No error message was returned. So I assumed that the sshd was running with the current config. But `sudo systemctl status sshd` told me that the service failed due to a wrong option in /etc/ssh/sshd_config. Please see the following output: ~~~ :~$ sudo vim /etc/ssh/sshd_config :~$ sudo systemctl reload sshd :~$ sudo systemctl status sshd ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Di 2018-05-15 10:00:04 CEST; 8s ago Process: 12089 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Process: 7536 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 7536 (code=exited, status=255) ~~~ I would expect that a warning or error message is returned when the service fails while reloading it's configuration. A fix for this behaviour would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.4 ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39 Uname: Linux 3.13.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Tue May 15 10:18:25 2018 InstallationDate: Installed on 2013-01-10 (1950 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) SourcePackage: openssh UpgradeStatus: Upgraded to xenial on 2017-03-12 (428 days ago) mtime.conffile..etc.pam.d.sshd: 2017-03-13T19:59:01.965420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1771340/+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 1797124] [NEW] Xorg crashes
Public bug reported: Frequent crashes when I; * unlock the screen * resume from suspend Usually, I see the login page, I put my password and then it's 50:50 chance that it will crash. If it crashes, there's a brief flash in screen and then it goes black. I cannot fire up tty with ctrl+alt+[1-7]. I had to reboot in that case (I use SysRq Magic+R,E,I,S,U,B) If it does not crash, then I can login to system, I can see the desktop but it stays unresponsive for 10-30 seconds and then gnome-shell restarts, and then I can start using the windows/programs. Not sure if this is Xorg or gnome-shell or gdm3 problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 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: GNOME Date: Wed Oct 10 16:31:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.15.0-34-generic, x86_64: installed nvidia, 390.87, 4.15.0-36-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-34-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:11cd] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 750M] [1043:11cd] InstallationDate: Installed on 2018-06-01 (131 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N550JV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=d62c0813-bece-408d-8a4c-773ce7fbe368 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JV.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze possible-manual-nvidia-install ubuntu ** Summary changed: - Xorg freeze + Xorg crashes -- 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/1797124 Title: Xorg crashes Status in xorg package in Ubuntu: New Bug description: Frequent crashes when I; * unlock the screen * resume from suspend Usually, I see the login page, I put my password and then it's 50:50 chance that it will crash. If it crashes, there's a brief flash in screen and then it goes black. I cannot fire up tty with ctrl+alt+[1-7]. I had to reboot in that case (I use SysRq Magic+R,E,I,S,U,B) If it does not crash, then I can login to system, I can see the desktop but it stays unresponsive for 10-30 seconds and then gnome- shell restarts, and then I can start using the windows/programs. Not sure if this is Xorg or gnome-shell
[Touch-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD
Ideally, we'd want to bisect and fix the kernel itself to reliably shutdown. yanking ahci sounds like a large hammer. Invalidating systemd task, and pinging kernely people. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: Incomplete Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1796822] Re: Desktop live cd boots corrupted screen in Virtualbox on Bionic
This bug was fixed in the package initramfs-tools - 0.131ubuntu14 --- initramfs-tools (0.131ubuntu14) cosmic; urgency=medium * hooks/framebuffer: manual_add_modules vboxvideo to support graphical boot in VirtualBox. LP: #1796822 -- Dimitri John Ledkov Wed, 10 Oct 2018 11:06:00 +0100 ** Changed in: initramfs-tools (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1796822 Title: Desktop live cd boots corrupted screen in Virtualbox on Bionic Status in initramfs-tools package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Confirmed Status in initramfs-tools source package in Cosmic: Fix Released Status in xorg-server source package in Cosmic: Confirmed Bug description: On a Bionic host running the standard archive version of Virtualbox and the daily ISO of Cosmic, the live session starts with a corrupted graphical display, as can be seen here: https://imgur.com/a/rkTId4S (also attached) Switching VTs to 2 and back to 1 clears the display and things work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1796822/+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 1797127] [NEW] can't see bugs I reported earlier in Launchpad
Public bug reported: I reported couple of bugs earlier about my struggle with gnome-shell. I had similar issues arising right now and I wanted to refer to my earlier bug report and I cannot find in the website. How can I access my older bug reports in Launchpad site? ** Affects: launchpad Importance: Undecided Status: New ** Tags: launchpad rant ** Package changed: xorg (Ubuntu) => launchpad -- 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/1797127 Title: can't see bugs I reported earlier in Launchpad Status in Launchpad itself: New Bug description: I reported couple of bugs earlier about my struggle with gnome-shell. I had similar issues arising right now and I wanted to refer to my earlier bug report and I cannot find in the website. How can I access my older bug reports in Launchpad site? To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1797127/+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 1797002] Re: all my bluetooth headsets skips terribly after todays update
I'm experiencing this as well. After rebooting today for the first time since September 25, I noticed somewhat choppy audio over bluetooth, first with mp3s on disk, then tried Youtube and it was significantly worse. Same audio content over laptop speakers seems to play without problems. Attaching a pulseaudio verbose log in case that helps. ** Attachment added: "pulseverbose.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+attachment/5199509/+files/pulseverbose.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1521754] Re: documentation of gi.repository.Gtk.Application.run missing
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: pygtk (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1521754 Title: documentation of gi.repository.Gtk.Application.run missing Status in gtk+3.0 package in Ubuntu: New Status in pygtk package in Ubuntu: Invalid Bug description: Invoking `help(gi.repository.Gtk.Application.run)` in `python` after importing `gi.repository.Gtk` shows that no function is properly documented. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: python-gtk2-doc 2.24.0-4ubuntu1 Uname: Linux 4.3.0-040300-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Tue Dec 1 21:15:48 2015 InstallationDate: Installed on 2015-09-14 (77 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MarkForUpload: True PackageArchitecture: all SourcePackage: pygtk SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: UpgradeStatus: Upgraded to wily on 2015-10-23 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1521754/+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 1780332] Re: vaultlocker does not ensure that udev is triggered to create /dev/disk/by-uuid/ symlink and fails
do we need and want to enable udev synchronisation in dmsetup package in
xenial?
--
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/1780332
Title:
vaultlocker does not ensure that udev is triggered to create /dev/disk
/by-uuid/ symlink and fails
Status in vaultlocker:
Fix Released
Status in cryptsetup package in Ubuntu:
New
Status in lvm2 package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
When an encrypted device is setup up a UUID (osd_fsid) is passed from
the charm to be used in the cryptsetup command which accepts a UUID to
place into the LUKS header (shown in cryptsetup luksDump ).
https://github.com/openstack/charm-ceph-osd/blob/stable/18.05/lib/ceph/utils.py#L1788-L1804
UUID comes from osd_fsid
https://github.com/openstack-charmers/vaultlocker/blob/8c9cb85dc3ed5dbf18c66a810d189a5230d85c34/vaultlocker/shell.py#L69-L80
# else statement is used here
block_uuid = str(uuid.uuid4()) if not args.uuid else args.uuid
dmcrypt.luks_format(key, block_device, block_uuid) # creates a LUKS
header
# ...
dmcrypt.luks_open(key, block_uuid) # sets up a device with device mapper
decrypting it via dmcrypt
https://github.com/openstack-
charmers/vaultlocker/blob/d813233179bdf2eec8ed101c702a8e552a966f44/vaultlocker/dmcrypt.py#L44-L56
This UUID is visible in blkid output
/dev/sdc: UUID="" TYPE="crypto_LUKS"
and a udev rule exists to create a /dev/disk/by-uuid/ symlink (which is normally used for filesystem -> block device
resolution)
https://git.launchpad.net/~usd-import-team/ubuntu/+source/lvm2/tree/udev/13-dm-disk.rules.in#n25
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*",
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
Where vaultlocker fails is in luks_open command (right after luks_format)
# cryptsetup --batch-mode --key-file - open UUID=
crypt- --type luks
because it tries to access /dev/disk/by-uuid/ which
does not exist.
This happens since udev rules are not re-triggered to create this
symlink after a LUKS device is created.
Solution: call the command below after luks_format before luks_open
udevadm settle --exit-if-exists=/dev/disk/by-uuid/
To manage notifications about this bug go to:
https://bugs.launchpad.net/vaultlocker/+bug/1780332/+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 1797097] Re: Missaligned border wit ComboBox in Headerbar
Hi i sadly can not comment on that. I noticed the bug while trying out an application on ubuntu 18.04 with all updates installed and it already had the same behavior. There where other problems too but they all seem to be fixed with ubuntu-themes_16.10+18.10.20181005. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1797097 Title: Missaligned border wit ComboBox in Headerbar Status in ubuntu-themes package in Ubuntu: New Bug description: Hi, with ubuntu-themes_16.10+18.10.20181005 the left border of a GtkComboBox with a GtkTextEntry in the GtkHeaderbar seems to be slightly misaligned leaving an additional white space to its left. The bug isn't visible once the GtkTextEntry gets the focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1797097/+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 1797097] Re: Missaligned border wit ComboBox in Headerbar
Thank you for your bug report, is that a regression from the recent SRU? ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1797097 Title: Missaligned border wit ComboBox in Headerbar Status in ubuntu-themes package in Ubuntu: New Bug description: Hi, with ubuntu-themes_16.10+18.10.20181005 the left border of a GtkComboBox with a GtkTextEntry in the GtkHeaderbar seems to be slightly misaligned leaving an additional white space to its left. The bug isn't visible once the GtkTextEntry gets the focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1797097/+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 1791995] Re: Lightdm crashes when trying to login as a user with "Don't ask at login" setting enabled
In the feature please take a look at https://ubuntu-mate.community/t /how-to-report-problems-in-ubuntu-mate/17943 ** Description changed: Lightdm crashes when trying to login as a user with "Don't ask at login" setting enabled. + + OS: Ubuntu Mate 18.04 ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1791995 Title: Lightdm crashes when trying to login as a user with "Don't ask at login" setting enabled Status in ubuntu-mate: Invalid Status in lightdm package in Ubuntu: New Bug description: Lightdm crashes when trying to login as a user with "Don't ask at login" setting enabled. OS: Ubuntu Mate 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1791995/+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 1794843] Re: New release of 'gstreamer1.0' (1.14.4)
It's accepted now. ** Changed in: gstreamer1.0 (Ubuntu) Status: In Progress => Fix Committed -- 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/1794843 Title: New release of 'gstreamer1.0' (1.14.4) Status in gstreamer1.0 package in Ubuntu: Fix Committed Bug description: Hello, https://packages.debian.org/source/sid/gstreamer1.0 'Source Package: gstreamer1.0 (1.14.3-1)' Best regards, -- Cristian Aravena Romero (caravena) --- https://gstreamer.freedesktop.org/releases/1.14/#1.14.3 == 1.14.3 == The third 1.14 bug-fix release (1.14.3) was released on 16 September 2018. This release only contains bugfixes and it should be safe to update from 1.14.x. Highlighted bugfixes in 1.14.3 opusenc: fix crash on 32-bit platforms compositor: fix major buffer leak when doing crossfading on some but not all pads wasapi: various fixes for wasapisrc and wasapisink regressions x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. Rebuild to..." runtime errors with x264 version ≥ 153 audioaggregator, audiomixer: caps negotiation fixes input-selector: latency handling fixes playbin, playsink: audio visualization support fixes dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand profile opencv: Fix build for opencv >= 3.4.2 h265parse: miscellaneous fixes backported from h264parse pads: fix changing of pad offsets from inside pad probes pads: ensure that pads are blocked for IDLE probes if they are called from the streaming thread too ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.2-2 Uname: Linux 4.18.10-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 13:43:05 2018 InstallationDate: Installed on 2017-10-13 (349 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1794843/+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 1793092] Re: [FFe] openssl 1.1.1
wrong bug number typpo! -- 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/1793092 Title: [FFe] openssl 1.1.1 Status in openssl package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python3.6 package in Ubuntu: Fix Released Bug description: Merge openssl 1.1.1 from debian unstable. OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream LTS release. Resulting in the following changes in Ubuntu: - openssl moves from 1.1.0 series to 1.1.1 LTS series - TLS1.3 is enabled, and used by default, when possible. Major feature. - All existing delta, and minimally accepted key sizes, and minimally accepted protocol versions remain the same. Proposed package is in https://launchpad.net/~xnox/+archive/ubuntu/openssl with a rebuild of all the reverse dependencies. It demonstrates that openssl compiled as above is more compatible and has less issues than debian config. There are a few FTBFS, which are also present in cosmic-release; there are some test-suite expectations mismatch (connectivity succeeds with tls1.3 even though lower/different algos are expected); there are very little connectivity tests thus connectivity interop are the biggest issues which will be unavoidable with introducing 1.3. === Ubuntu delta summary versus debian unstable in this merge: - Replace duplicate files in the doc directory with symlinks. - debian/libssl1.1.postinst: + Display a system restart required notification on libssl1.1 upgrade on servers. + Use a different priority for libssl1.1/restart-services depending on whether a desktop, or server dist-upgrade is being performed. - Revert "Enable system default config to enforce TLS1.2 as a minimum" & "Increase default security level from 1 to 2". - Further decrease security level from 1 to 0, for compatibility with openssl 1.0.2. These mitigate most of the runtime incompatibilities, and ensure client<->server compatibility between 1.1.1, 1.1.0, and 1.0.2 series and thus one can continue to mix & match xenial/bionic/cosmic releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092/+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 1797040] Re: QtWebkit - missing doxygen tags file
Hi Anton! Can you please forward the patch upstream to https://github.com/annulen/webkit? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1797040 Title: QtWebkit - missing doxygen tags file Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: Current version of qtwebkit5-doc-html package doesn't contains qtwebkit.tags file which leads to incomplete doxygen documentation generation for external projects (kdewebkit for example). This can fixed with small patch (see attachment). I test it on my 18.04 system - all works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1797040/+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 1796822] Re: Desktop live cd boots corrupted screen in Virtualbox on Bionic
** Changed in: initramfs-tools (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: initramfs-tools (Ubuntu Cosmic) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/1796822 Title: Desktop live cd boots corrupted screen in Virtualbox on Bionic Status in initramfs-tools package in Ubuntu: Fix Committed Status in xorg-server package in Ubuntu: Confirmed Status in initramfs-tools source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Confirmed Bug description: On a Bionic host running the standard archive version of Virtualbox and the daily ISO of Cosmic, the live session starts with a corrupted graphical display, as can be seen here: https://imgur.com/a/rkTId4S (also attached) Switching VTs to 2 and back to 1 clears the display and things work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1796822/+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 1794843] Re: New release of 'gstreamer1.0' (1.14.4)
** Tags added: rls-cc-incoming -- 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/1794843 Title: New release of 'gstreamer1.0' (1.14.4) Status in gstreamer1.0 package in Ubuntu: In Progress Bug description: Hello, https://packages.debian.org/source/sid/gstreamer1.0 'Source Package: gstreamer1.0 (1.14.3-1)' Best regards, -- Cristian Aravena Romero (caravena) --- https://gstreamer.freedesktop.org/releases/1.14/#1.14.3 == 1.14.3 == The third 1.14 bug-fix release (1.14.3) was released on 16 September 2018. This release only contains bugfixes and it should be safe to update from 1.14.x. Highlighted bugfixes in 1.14.3 opusenc: fix crash on 32-bit platforms compositor: fix major buffer leak when doing crossfading on some but not all pads wasapi: various fixes for wasapisrc and wasapisink regressions x264enc: Set bit depth to fix "This build of x264 requires 8-bit depth. Rebuild to..." runtime errors with x264 version ≥ 153 audioaggregator, audiomixer: caps negotiation fixes input-selector: latency handling fixes playbin, playsink: audio visualization support fixes dashdemux: fix possible crash if stream is neither isobmff nor isoff_ondemand profile opencv: Fix build for opencv >= 3.4.2 h265parse: miscellaneous fixes backported from h264parse pads: fix changing of pad offsets from inside pad probes pads: ensure that pads are blocked for IDLE probes if they are called from the streaming thread too ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.2-2 Uname: Linux 4.18.10-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 27 13:43:05 2018 InstallationDate: Installed on 2017-10-13 (349 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1794843/+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 1796822] Re: Desktop live cd boots corrupted screen in Virtualbox on Bionic
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1796822 Title: Desktop live cd boots corrupted screen in Virtualbox on Bionic Status in initramfs-tools package in Ubuntu: New Status in xorg-server package in Ubuntu: Confirmed Status in initramfs-tools source package in Cosmic: New Status in xorg-server source package in Cosmic: Confirmed Bug description: On a Bionic host running the standard archive version of Virtualbox and the daily ISO of Cosmic, the live session starts with a corrupted graphical display, as can be seen here: https://imgur.com/a/rkTId4S (also attached) Switching VTs to 2 and back to 1 clears the display and things work again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1796822/+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 1797097] [NEW] Missaligned border wit ComboBox in Headerbar
Public bug reported: Hi, with ubuntu-themes_16.10+18.10.20181005 the left border of a GtkComboBox with a GtkTextEntry in the GtkHeaderbar seems to be slightly misaligned leaving an additional white space to its left. The bug isn't visible once the GtkTextEntry gets the focus. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "combobox in headerbar" https://bugs.launchpad.net/bugs/1797097/+attachment/5199437/+files/combobox.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1797097 Title: Missaligned border wit ComboBox in Headerbar Status in ubuntu-themes package in Ubuntu: New Bug description: Hi, with ubuntu-themes_16.10+18.10.20181005 the left border of a GtkComboBox with a GtkTextEntry in the GtkHeaderbar seems to be slightly misaligned leaving an additional white space to its left. The bug isn't visible once the GtkTextEntry gets the focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1797097/+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 1797097] Re: Missaligned border wit ComboBox in Headerbar
** Attachment added: "combobox in headerbar with focus" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1797097/+attachment/5199438/+files/combobox_focus.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1797097 Title: Missaligned border wit ComboBox in Headerbar Status in ubuntu-themes package in Ubuntu: New Bug description: Hi, with ubuntu-themes_16.10+18.10.20181005 the left border of a GtkComboBox with a GtkTextEntry in the GtkHeaderbar seems to be slightly misaligned leaving an additional white space to its left. The bug isn't visible once the GtkTextEntry gets the focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1797097/+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 1768166] Re: Random crashes
** Also affects: libpinyin (Ubuntu) Importance: Undecided Status: New ** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Also affects: language-selector (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libpinyin (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ibus-libpinyin (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: language-selector (Ubuntu Bionic) ** No longer affects: language-selector (Ubuntu) ** Changed in: ibus-libpinyin (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: ibus-libpinyin (Ubuntu Bionic) Status: New => In Progress ** Changed in: ibus-libpinyin (Ubuntu Bionic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: libpinyin (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: libpinyin (Ubuntu Bionic) Status: New => In Progress ** Changed in: libpinyin (Ubuntu Bionic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: ibus-libpinyin (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libpinyin (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes Status in ibus-libpinyin package in Ubuntu: Fix Released Status in libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin source package in Bionic: In Progress Status in libpinyin source package in Bionic: In Progress Bug description: I have experienced random ibus-libpinyin crashes in bionic. I cannot reproduce it, but it occurred at least a few times, even after the official bionic release. Same crashes were also reported in the Ubuntu Chinese forum. Currently, the workaround is to delete the ~/.cache/ibus/libpinyin folder. I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he suggested that we update the version of ibus-libpinyin to 1.10. Can we give this update a trial? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+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 1793459] Re: package python3-problem-report 2.20.9-0ubuntu7.3 failed to install/upgrade: installed python3-problem-report package post-installation script subprocess returned err
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1793459 Title: package python3-problem-report 2.20.9-0ubuntu7.3 failed to install/upgrade: installed python3-problem-report package post- installation script subprocess returned error exit status 3 Status in apport package in Ubuntu: Confirmed Bug description: updating using the system updater. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-problem-report 2.20.9-0ubuntu7.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.3 AptOrdering: linux-headers-4.15.0-32-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 Date: Thu Sep 20 09:12:05 2018 Dependencies: DuplicateSignature: package:python3-problem-report:2.20.9-0ubuntu7.3 Setting up libglib2.0-dev-bin (2.56.2-0ubuntu0.18.04.1) ... E: py3compile:243: Requested versions are not installed dpkg: error processing package libglib2.0-dev-bin (--configure): installed libglib2.0-dev-bin package post-installation script subprocess returned error exit status 3 ErrorMessage: installed python3-problem-report package post-installation script subprocess returned error exit status 3 InstallationDate: Installed on 2016-07-05 (806 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6m, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apport Title: package python3-problem-report 2.20.9-0ubuntu7.3 failed to install/upgrade: installed python3-problem-report package post-installation script subprocess returned error exit status 3 UpgradeStatus: Upgraded to bionic on 2018-08-19 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1793459/+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 1797040] Re: QtWebkit - missing doxygen tags file
The attachment "git patch to fix the problem" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1797040 Title: QtWebkit - missing doxygen tags file Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: Current version of qtwebkit5-doc-html package doesn't contains qtwebkit.tags file which leads to incomplete doxygen documentation generation for external projects (kdewebkit for example). This can fixed with small patch (see attachment). I test it on my 18.04 system - all works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1797040/+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 1797064] [NEW] Update to 2.9.8 next cycle
Public bug reported: The new version is in Debian experimental but it's late to update on Ubuntu this cycle, especially with a non trivial update on a component like that, the update is for next cycle ** Affects: libxml2 (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: upgrade-software-version version-blocked-ff ** Changed in: libxml2 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1797064 Title: Update to 2.9.8 next cycle Status in libxml2 package in Ubuntu: Triaged Bug description: The new version is in Debian experimental but it's late to update on Ubuntu this cycle, especially with a non trivial update on a component like that, the update is for next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1797064/+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 1797063] [NEW] Update to 130 next cycle
Public bug reported: The new version is in Debian but the changes are not trivial enough to update in cosmic, that's for next cycle ** Affects: cron (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: upgrade-software-version version-blocked-ff ** Changed in: cron (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1797063 Title: Update to 130 next cycle Status in cron package in Ubuntu: Triaged Bug description: The new version is in Debian but the changes are not trivial enough to update in cosmic, that's for next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1797063/+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 1713448] Re: Adobe Reader doesn't print on OKI C911
I had a similar issue with Adobe Reader. I think you should check your file because this bug is missing log files. It is also available Adobe's Photoshop. It is a very interesting software. If you have any issue with Photoshop, like error issue, then simply visit https://www.adobesupportphonenumber.com/blog/fix-adobe-photoshop- error-16/. They will solve your issue quickly. -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+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 1797059] [NEW] Update to 1.9.0 next cycle
Public bug reported: The new version has changes that are not trivial, let's delay to next cycle ** Affects: harfbuzz (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: upgrade-software-version version-blocked-ff ** Changed in: harfbuzz (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to harfbuzz in Ubuntu. https://bugs.launchpad.net/bugs/1797059 Title: Update to 1.9.0 next cycle Status in harfbuzz package in Ubuntu: Triaged Bug description: The new version has changes that are not trivial, let's delay to next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/harfbuzz/+bug/1797059/+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 1797055] [NEW] Working printer stops after upgrade to 18.04
Public bug reported: After an upgrade from 16.04 to 18.04 my printer stopped working. The printer is an Epson E360-dn. After printing a test page the I get the message Printing followed by Printing Stopped with the Printer's state message saying "Filter Failed". The printer is network attached. This printer works fine from a Windows PC on the network and also works if I boot from an 18.04 live usb. It seems something broke or was carried forward in the upgrade process. I have posted to https://askubuntu.com/questions/1081885/printer- stopped-working-after-upgrade-16-04-to-18-04 with no help forthcoming. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 10 17:43:18 2018 InstallationDate: Installed on 2016-03-18 (935 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lpstat: device for Lexmark_Lexmark_International_Lexmark_E360dn: dnssd://Lexmark%20E360dn._ipp._tcp.local/?uuid=6bd76abb-9aa9-41ee-b582-12e3fecf735f Papersize: a4 PpdFiles: Lexmark_Lexmark_International_Lexmark_E360dn: Lexmark E360dn ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=bcf0b349-99b2-425e-81da-0a9ca8ae1890 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-02 (7 days ago) dmi.bios.date: 01/03/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0065.2018.0103.1000 dmi.board.asset.tag: �]/� dmi.board.name: NUC6i5SYB dmi.board.vendor: Intel corporation dmi.board.version: H81131-502 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0065.2018.0103.1000:bd01/03/2018:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-502:cvn:ct3:cvr: ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "debugging steps from Wiki DebuggingPrintingProblems" https://bugs.launchpad.net/bugs/1797055/+attachment/5199405/+files/Debugging%20Printing%20after%20upgrade%20to%20Bionic.txt -- 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/1797055 Title: Working printer stops after upgrade to 18.04 Status in cups package in Ubuntu: New Bug description: After an upgrade from 16.04 to 18.04 my printer stopped working. The printer is an Epson E360-dn. After printing a test page the I get the message Printing followed by Printing Stopped with the Printer's state message saying "Filter Failed". The printer is network attached. This printer works fine from a Windows PC on the network and also works if I boot from an 18.04 live usb. It seems something broke or was carried forward in the upgrade process. I have posted to https://askubuntu.com/questions/1081885/printer- stopped-working-after-upgrade-16-04-to-18-04 with no help forthcoming. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 10 17:43:18 2018 InstallationDate: Installed on 2016-03-18 (935 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lpstat: device for Lexmark_Lexmark_International_Lexmark_E360dn: dnssd://Lexmark%20E360dn._ipp._tcp.local/?uuid=6bd76abb-9aa9-41ee-b582-12e3fecf735f Papersize: a4 PpdFiles: Lexmark_Lexmark_International_Lexmark_E360dn: Lexmark E360dn ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=bcf0b349-99b2-425e-81da-0a9ca8ae1890 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-02 (7 days ago) dmi.bios.date: 01/03/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0065.2018.0103.1000 dmi.board.asset.tag: �]/� dmi.board.name: NUC6i5SYB dmi.board.vendor: Intel corporation dmi.board.version: H81131-502 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0065.2018.0103.1000:bd01/03/2018:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-502:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1797055/+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 1795407] Re: python-apt frontend locking
** Description changed: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. - [Other info] + [Other info (1)] CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. - [Other info] + [Other info (2)] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html + + - This SRU depends on the apt SRU above, and breaks unattended-upgrades + in bionic without its SRU due to a bug in the u-u code in handling the + new API. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Bug description: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most:
[Touch-packages] [Bug 1797040] Re: QtWebkit - missing doxygen tags file
** Patch added: "git patch to fix the problem" https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1797040/+attachment/5199390/+files/qdoc.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1797040 Title: QtWebkit - missing doxygen tags file Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: Current version of qtwebkit5-doc-html package doesn't contains qtwebkit.tags file which leads to incomplete doxygen documentation generation for external projects (kdewebkit for example). This can fixed with small patch (see attachment). I test it on my 18.04 system - all works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1797040/+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 1797040] [NEW] QtWebkit - missing doxygen tags file
Public bug reported: Current version of qtwebkit5-doc-html package doesn't contains qtwebkit.tags file which leads to incomplete doxygen documentation generation for external projects (kdewebkit for example). This can fixed with small patch (see attachment). I test it on my 18.04 system - all works as expected. ** Affects: qtwebkit-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1797040 Title: QtWebkit - missing doxygen tags file Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: Current version of qtwebkit5-doc-html package doesn't contains qtwebkit.tags file which leads to incomplete doxygen documentation generation for external projects (kdewebkit for example). This can fixed with small patch (see attachment). I test it on my 18.04 system - all works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1797040/+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 1173827] Re: Switch gdebi to pkexec
18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1173827 Title: Switch gdebi to pkexec Status in gdebi package in Ubuntu: Won't Fix Bug description: Well gksu isn't default installed anymore & 64 bit users run into the su mode deal, gksu-polkit isn't suitable either So makes no sense to keep using gksu in gdebi. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gdebi (not installed) ProcVersionSignature: Ubuntu 3.9.0-0.1-generic 3.9.0-rc8 Uname: Linux 3.9.0-0-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 27 22:50:03 2013 InstallationDate: Installed on 2013-04-24 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1173827/+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 1173827] Re: Switch gdebi to pkexec
Any news? it also affects ubuntu mate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1173827 Title: Switch gdebi to pkexec Status in gdebi package in Ubuntu: Won't Fix Bug description: Well gksu isn't default installed anymore & 64 bit users run into the su mode deal, gksu-polkit isn't suitable either So makes no sense to keep using gksu in gdebi. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gdebi (not installed) ProcVersionSignature: Ubuntu 3.9.0-0.1-generic 3.9.0-rc8 Uname: Linux 3.9.0-0-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat Apr 27 22:50:03 2013 InstallationDate: Installed on 2013-04-24 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1173827/+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 1770082] Re: systemd-networkd not renaming devices on boot
Hi, This works on reboot but not so well after the system boots. Say I have the following file: network: version: 2 ethernets: ens7: dhcp4: true match: macaddress: 52:54:00:b4:02:6e set-name: myif1 optional: true If I reboot, everything is fine: ubuntu@netplan2:~$ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:d2:9b:b5 brd ff:ff:ff:ff:ff:ff 3: myif1: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:b4:02:6e brd ff:ff:ff:ff:ff:ff But if I now change set-name to myif0, I can't get it to change the name 'live'. If I apply with the interface 'up', nothing happens, which is fine: ubuntu@netplan2:~$ sudo netplan apply ubuntu@netplan2:~$ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:d2:9b:b5 brd ff:ff:ff:ff:ff:ff 3: myif1: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:b4:02:6e brd ff:ff:ff:ff:ff:ff But if I bring it down and run netplan apply, the interface is renamed to ens7, not myif0, and it stays down. ubuntu@netplan2:~$ sudo ip l set dev myif1 down ubuntu@netplan2:~$ sudo netplan apply ubuntu@netplan2:~$ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:d2:9b:b5 brd ff:ff:ff:ff:ff:ff 3: ens7: mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:b4:02:6e brd ff:ff:ff:ff:ff:ff If I downgrade to 0.36.3, the interface is correctly renamed and brought up: 9: myif0: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:b4:02:6e brd ff:ff:ff:ff:ff:ff So not an unqualified success here. Regards, Daniel -- 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/1770082 Title: systemd-networkd not renaming devices on boot Status in netplan: Fix Released Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in nplan source package in Xenial: Fix Released Status in netplan.io source package in Bionic: Fix Committed Bug description: [Impact] Systems relying on renaming network interfaces at boot and when 'netplan apply' is run. [Test case] - Write a new netplan YAML (adjusting for current system as necessary): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:de:bd:f6 set-name: myif0 - Run 'netplan apply' - Verify that the device is correctly renamed to 'myif0'. - Reboot. - Make sure the device is correctly renamed to 'myif0'. [Regression potential] Changes in rename logic to add udev rules may otherwise impact applying different settings to the network interfaces. Changes in settings on network interfaces, missing parameters (especially on bonds, bridges) should be investigated as potential regressions. Other failures to apply network settings might also happen if there's a race between applying renames via the udev rules, and using the new names to apply configuration changes to the interfaces. === systemd issue === Renaming devices doesn't seem to work. If I disable all other network configuration and create /etc/systemd/network/10-network.link with: [Match] MACAddress=52:54:00:c1:c9:bb [Link] Name=myiface3 I expect this to cause the device with that MAC address to be renamed to myiface3. However, when I reboot, I instead see: $ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff The device is not renamed. This link file is pretty much identical to Example 2 in https://www.freedesktop.org/software/systemd/man/systemd.link.html. The renaming does work if I boot with net.ifnames=0, and oddly, it also works if I unbind the device and rebind it as netplan apply does. No setting of NamePolicy seems to help. === Original Bug == 'set-name:' doesn't
