[Touch-packages] [Bug 1300382] Re: input events not being flushed in browser until pressing hardware keys
If the input events not being flushed in the browser until pressing hardware keys then you can use https://ienjoyshayari.in/best-whatsapp- status/ this file in the browser settings to flush it -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1300382 Title: input events not being flushed in browser until pressing hardware keys Status in Oxide: Fix Released Status in ubuntu-keyboard: Fix Released Status in The Webapps-core project: Invalid Status in oxide-qt package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: Fix Released Bug description: using webbrowser-app from Silo 9 and oxide in universe Log in to Facebook on the phone Click "comment" in someone's post Start typing Expected results: The comment button should become enabled so you can submit comment Actual results: The comment button always stays disabled. Tested this on webbrowser-app on desktop with oxide (explicilty loading m.facebook.com) and becomes enabled as it should after typing. Seems specific to device. Guessing it's a UA String issue. Is there a way to see the JS console to see if a JS error is occuring? To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1300382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776622] Re: snapd updates on cosmic never finish installing. Can't install any other updates.
Although that may just be because I am mainly using 19.04 and to a lesser extent 18.04. -- 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/1776622 Title: snapd updates on cosmic never finish installing. Can't install any other updates. Status in snapd: Incomplete Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't install any other updates. The first time I gave up waiting and killed it. Then... $ sudo apt full-upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a Setting up snapd (2.33+18.10ubuntu3) ... snapd.snap-repair.service is a disabled or a static unit, not starting it. << never ends >> All the while the snap and snapd process use about 0.3% CPU (which is more than usual). WORKAROUND: sudo killall apt dpkg sudo dpkg -r snapd gnome-software-plugin-snap sudo apt update sudo apt full-upgrade --- ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: snapd 2.33+18.10ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 Date: Wed Jun 13 16:49:20 2018 InstallationDate: Installed on 2018-05-26 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776622] Re: snapd updates on cosmic never finish installing. Can't install any other updates.
Was this fixed? I haven't encountered it in a while. ** Changed in: snapd Status: Confirmed => Incomplete ** Changed in: snapd (Ubuntu) Status: In Progress => Incomplete ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1776622 Title: snapd updates on cosmic never finish installing. Can't install any other updates. Status in snapd: Incomplete Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't install any other updates. The first time I gave up waiting and killed it. Then... $ sudo apt full-upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a Setting up snapd (2.33+18.10ubuntu3) ... snapd.snap-repair.service is a disabled or a static unit, not starting it. << never ends >> All the while the snap and snapd process use about 0.3% CPU (which is more than usual). WORKAROUND: sudo killall apt dpkg sudo dpkg -r snapd gnome-software-plugin-snap sudo apt update sudo apt full-upgrade --- ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: snapd 2.33+18.10ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 Date: Wed Jun 13 16:49:20 2018 InstallationDate: Installed on 2018-05-26 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758261] Re: i want toinstall intel graphics for my pc which is as under
It appears the Xorg modeset driver is only offering you 1024x768 because it can't retrieve the EDID (monitor resolution information etc) from the monitor. This might be a shortcoming of the monitor itself or it might be a cable problem. Please try: 1. A different monitor cable; or 2. The older intel driver: https://manpages.ubuntu.com/manpages/xenial/en/man4/intel.4.html or 3. A different monitor. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1758261 Title: i want toinstall intel graphics for my pc which is as under Status in xorg-server package in Ubuntu: Incomplete Bug description: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) Kindly show me the way as my screen resolution supports till 1920x1080_60.00 which is not coming in display settings ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 23 13:07:08 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2018-03-23 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=e987af12-2770-408b-a79c-0a658a9c61fb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-CS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-CS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Mar 23 12:58:44 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output VGA-1 xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1758261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818777] Re: Lubuntu 19.04 qa-test; suspend then wake & keyboard & mouse movement, but not mouse-buttons
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1818777 Title: Lubuntu 19.04 qa-test; suspend then wake & keyboard & mouse movement, but not mouse-buttons Status in xorg-server package in Ubuntu: New Bug description: // please ignore this at present.. // i've still got some more testing to do. // (i want to test this on another box without KVM (kbd/vid/mouse) switching this machine has // ALSO NOTE: lynorian (lubuntu-devel) also said guiverc: I think I filed something about this in a vm a few weeks ago // so I need to look for it, read & link (mark this one as duplicate if appropriate) Lubuntu 19.04 QA-TEST on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) // info from QA-TEST comments .. firefox paused; suspended machine (using menu) ISSUE: on wake (used keyboard to wake system) the mouse couldn't click on anything, but keyboard functions worked perfectly (ctrl+alt+t to open term etc). i'll reboot & reload, re-try reboot & retried.. same issue (on reboot; after reboot I ctrl+alt+T to open term & ran `htop` so I had some changing data on screen to confirm more than just mouse was moving on screen, then suspended.. on wake [2nd boot], notification boxes appeared... mouse moves correctly, keyboard keys appear all good (can switch to tty & back) but no mouse buttons work ran `xev` & is see all keyboard, and mouse movements, but no buttons appear in window on pressing (unless I accidentally cause mouse to move) Of note: I've experienced this behavior BEFORE & not reported, as the reboot & re-try has always worked flawlessly. Rebooted again & re-tested it a third time (menu->suspend, used mouse to click yes [normally I hit enter]) & counted to 20 Woke machine (using power-button instead of keyboard) & keyboard perfect, mouse movement perfect, alas no mouse-button function on screen or menu, nor appearing in `xev` .. mouse wheel is recognized in `xev`. // this is typed into another box - no mouse function on ubuntu-bug machine since suspend ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu9 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.402 CompositorRunning: None CurrentDesktop: LXQt Date: Wed Mar 6 04:22:12 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1818777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818777] [NEW] Lubuntu 19.04 qa-test; suspend then wake & keyboard & mouse movement, but not mouse-buttons
Public bug reported: // please ignore this at present.. // i've still got some more testing to do. // (i want to test this on another box without KVM (kbd/vid/mouse) switching this machine has // ALSO NOTE: lynorian (lubuntu-devel) also said guiverc: I think I filed something about this in a vm a few weeks ago // so I need to look for it, read & link (mark this one as duplicate if appropriate) Lubuntu 19.04 QA-TEST on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) // info from QA-TEST comments .. firefox paused; suspended machine (using menu) ISSUE: on wake (used keyboard to wake system) the mouse couldn't click on anything, but keyboard functions worked perfectly (ctrl+alt+t to open term etc). i'll reboot & reload, re-try reboot & retried.. same issue (on reboot; after reboot I ctrl+alt+T to open term & ran `htop` so I had some changing data on screen to confirm more than just mouse was moving on screen, then suspended.. on wake [2nd boot], notification boxes appeared... mouse moves correctly, keyboard keys appear all good (can switch to tty & back) but no mouse buttons work ran `xev` & is see all keyboard, and mouse movements, but no buttons appear in window on pressing (unless I accidentally cause mouse to move) Of note: I've experienced this behavior BEFORE & not reported, as the reboot & re-try has always worked flawlessly. Rebooted again & re-tested it a third time (menu->suspend, used mouse to click yes [normally I hit enter]) & counted to 20 Woke machine (using power-button instead of keyboard) & keyboard perfect, mouse movement perfect, alas no mouse-button function on screen or menu, nor appearing in `xev` .. mouse wheel is recognized in `xev`. // this is typed into another box - no mouse function on ubuntu-bug machine since suspend ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu9 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.402 CompositorRunning: None CurrentDesktop: LXQt Date: Wed Mar 6 04:22:12 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu ** Attachment added: "dmesg >dmesg.txt (ran on dc7700 box during live session)" https://bugs.launchpad.net/bugs/1818777/+attachment/5243845/+files/dmesg.txt ** Description changed: // please ignore this at present.. // i've still got some more testing to do. // (i want to test this on another box without KVM (kbd/vid/mouse) switching this machine has // ALSO NOTE: lynorian (lubuntu-devel) also said guiverc: I think I filed something about this in a vm a few weeks ago // so I need to look for it, read & link (mark this one as duplicate if appropriate) Lubuntu 19.04 QA-TEST on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) // info from QA-TEST comments .. firefox paused; suspended machine (using menu) ISSUE: on wake (used keyboard to wake system) the mouse couldn't click on anything, but keyboard functions worked perfectly (ctrl+alt+t to open term etc). i'll reboot & reload, re-try reboot & retried.. same iss
[Touch-packages] [Bug 1801439] Re: Unable to add software sources via the software-properties-qt
This bug was fixed in the package software-properties - 0.97.8 --- software-properties (0.97.8) disco; urgency=medium * Change debconf frontend to kde for software-properties-qt. * Change Qt Desktop Entry to be shown in LXQt. * Add Drivers Qt Desktop Entry to be shown in LXQt. * Fix adding of PPAs (LP: #1801439). * Fixed typos in Qt Additional Driver tab. -- hmolle...@lubuntu.me (Hans P. Moller) Thu, 21 Feb 2019 22:49:39 -0300 ** Changed in: software-properties (Ubuntu) Status: Triaged => Fix Released -- 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/1801439 Title: Unable to add software sources via the software-properties-qt Status in software-properties package in Ubuntu: Fix Released Bug description: Test 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the example repo given in the dialog, which is not a PPA) 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked self.add_source_from_line(line) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line enable_source_code=enable_source_code) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52 2018 InstallationDate: Installed on 2018-10-19 (14 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) 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/1801439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 707299] Re: cheese crashed with SIGSEGV in gst_mini_object_copy()
[Expired for cheese (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cheese (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/707299 Title: cheese crashed with SIGSEGV in gst_mini_object_copy() Status in cheese package in Ubuntu: Expired Status in gstreamer0.10 package in Ubuntu: Expired Bug description: Binary package hint: cheese Open cheese Fast scenes makes cheese crash . Just shake with webcam. I reproduced crash when i was in dark room and shoot at window. Needs compensate exposure, then image gets glitchy and cheese crashed. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: cheese 2.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37 Uname: Linux 2.6.37-12-generic x86_64 Architecture: amd64 Date: Tue Jan 25 09:20:20 2011 ExecutablePath: /usr/bin/cheese InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: LENOVO 7661CH8 ProcCmdline: cheese ProcEnviron: LANGUAGE=en LANG=cs_CZ.utf8 LC_MESSAGES=en_AG.utf8 SHELL=/bin/bash RelatedPackageVersions: cheese 2.32.0-0ubuntu1 cheese-common 2.32.0-0ubuntu1 SegvAnalysis: Segfault happened at: 0x7fb80dbdbd0c : mov 0x8(%rax),%rax PC (0x7fb80dbdbd0c) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: cheese StacktraceTop: gst_mini_object_copy (mini_object=0xbdc240) at gstminiobject.c:231 gst_buffer_copy (v4l2src=0xd8e470, buf=0x7fb7f325d908) at /usr/include/gstreamer-0.10/gst/gstbuffer.h:383 gst_v4l2src_grab_frame (v4l2src=0xd8e470, buf=0x7fb7f325d908) at v4l2src_calls.c:166 gst_v4l2src_get_mmap (v4l2src=0xd8e470, buf=0x7fb7f325db08) at gstv4l2src.c:899 gst_v4l2src_create (src=0xd8e470, buf=0x7fb7f325db08) at gstv4l2src.c:948 Title: cheese crashed with SIGSEGV in gst_mini_object_copy() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (gnome-settings-daemon:1464): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed (gnome-settings-daemon:1464): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed (nautilus:1595): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed (nautilus:1595): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed dmi.bios.date: 04/08/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC7WW (2.27 ) dmi.board.name: 7661CH8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC7WW(2.27):bd04/08/2010:svnLENOVO:pn7661CH8:pvrThinkPadT61:rvnLENOVO:rn7661CH8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7661CH8 dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/707299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 707299] Re: cheese crashed with SIGSEGV in gst_mini_object_copy()
[Expired for gstreamer0.10 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gstreamer0.10 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/707299 Title: cheese crashed with SIGSEGV in gst_mini_object_copy() Status in cheese package in Ubuntu: Expired Status in gstreamer0.10 package in Ubuntu: Expired Bug description: Binary package hint: cheese Open cheese Fast scenes makes cheese crash . Just shake with webcam. I reproduced crash when i was in dark room and shoot at window. Needs compensate exposure, then image gets glitchy and cheese crashed. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: cheese 2.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37 Uname: Linux 2.6.37-12-generic x86_64 Architecture: amd64 Date: Tue Jan 25 09:20:20 2011 ExecutablePath: /usr/bin/cheese InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: LENOVO 7661CH8 ProcCmdline: cheese ProcEnviron: LANGUAGE=en LANG=cs_CZ.utf8 LC_MESSAGES=en_AG.utf8 SHELL=/bin/bash RelatedPackageVersions: cheese 2.32.0-0ubuntu1 cheese-common 2.32.0-0ubuntu1 SegvAnalysis: Segfault happened at: 0x7fb80dbdbd0c : mov 0x8(%rax),%rax PC (0x7fb80dbdbd0c) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: cheese StacktraceTop: gst_mini_object_copy (mini_object=0xbdc240) at gstminiobject.c:231 gst_buffer_copy (v4l2src=0xd8e470, buf=0x7fb7f325d908) at /usr/include/gstreamer-0.10/gst/gstbuffer.h:383 gst_v4l2src_grab_frame (v4l2src=0xd8e470, buf=0x7fb7f325d908) at v4l2src_calls.c:166 gst_v4l2src_get_mmap (v4l2src=0xd8e470, buf=0x7fb7f325db08) at gstv4l2src.c:899 gst_v4l2src_create (src=0xd8e470, buf=0x7fb7f325db08) at gstv4l2src.c:948 Title: cheese crashed with SIGSEGV in gst_mini_object_copy() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (gnome-settings-daemon:1464): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed (gnome-settings-daemon:1464): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed (nautilus:1595): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed (nautilus:1595): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed dmi.bios.date: 04/08/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC7WW (2.27 ) dmi.board.name: 7661CH8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC7WW(2.27):bd04/08/2010:svnLENOVO:pn7661CH8:pvrThinkPadT61:rvnLENOVO:rn7661CH8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7661CH8 dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/707299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818688] Re: Impossible to use Ubuntu 18.04
Please: 1. Edit /etc/default/grub and remove any of "recovery" and "nomodeset". Save the changes. 2. Run: sudo update-grub 3. Reboot. Does that fix it? ** 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/1818688 Title: Impossible to use Ubuntu 18.04 Status in Ubuntu: Incomplete Bug description: Ubuntu 18.04 starts in recovery mode only 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 i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 5 16:09:40 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [1043:1252] Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1043:1252] InstallationDate: Installed on 2010-12-15 (3001 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) MachineType: ASUSTeK Computer Inc. F7F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=62f67c93-44cb-40be-90fd-6dbc4a7d4f19 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F7F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 2.1 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr203:bd08/14/2007:svnASUSTeKComputerInc.:pnF7F:pvr1.0:rvnASUSTeKComputerInc.:rnF7F:rvr2.1:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: F7F dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Tue Mar 5 13:22:01 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1818688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818700] Re: some problems
Can you please take a video of the flashing and attach it here? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1818700 Title: some problems Status in xorg-server package in Ubuntu: Incomplete Bug description: Nautilus doesn t work - as I try to manage files thru grafical way it just causes my screen flashig in a fast way ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 5 18:32:29 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:105c] NVIDIA Corporation GF108M [GeForce GT 620M/630M/635M/640M LE] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 630M] [1043:2128] InstallationDate: Installed on 2018-03-06 (364 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: ASUSTeK Computer Inc. K93SM ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=dc7bbf0d-c12f-4b29-9787-54ac74c97c4e ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K93SM 204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K93SM 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.:bvrK93SM204:bd12/16/2011:svnASUSTeKComputerInc.:pnK93SM:pvr1.0:rvnASUSTeKComputerInc.:rnK93SM:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K93SM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1818700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818530] Re: bluetooth always starts at startup
*** This bug is a duplicate of bug 1809783 *** https://bugs.launchpad.net/bugs/1809783 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1809783, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1809783 When TLP is installed, Bluetooth always on when power on my laptop regardless of its previous state -- 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/1818530 Title: bluetooth always starts at startup Status in bluez package in Ubuntu: Incomplete Bug description: after every startup, I have to manually turn off bluetooth which is enabled at startup ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Mar 4 20:24:42 2019 InstallationDate: Installed on 2018-10-16 (139 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5d5 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-br0xx ProcEnviron: LC_CTYPE=en_IN TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=0bb24ccc-6f8f-43ca-8a73-ccd2f46a3633 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/10/2017:svnHP:pnHPLaptop15g-br0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15g-br0xx dmi.product.sku: 2JR17PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:AF:BD:F0:13:69 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:1787 acl:0 sco:0 events:224 errors:0 TX bytes:43852 acl:0 sco:0 commands:224 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1818530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818530] Re: bluetooth always starts at startup
*** This bug is a duplicate of bug 1809783 *** https://bugs.launchpad.net/bugs/1809783 Sachin Humar via email: > Yes, tlp is installed. Any problem having that being installed? Please help. -- 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/1818530 Title: bluetooth always starts at startup Status in bluez package in Ubuntu: Incomplete Bug description: after every startup, I have to manually turn off bluetooth which is enabled at startup ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Mar 4 20:24:42 2019 InstallationDate: Installed on 2018-10-16 (139 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5d5 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-br0xx ProcEnviron: LC_CTYPE=en_IN TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=0bb24ccc-6f8f-43ca-8a73-ccd2f46a3633 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/10/2017:svnHP:pnHPLaptop15g-br0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15g-br0xx dmi.product.sku: 2JR17PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:AF:BD:F0:13:69 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:1787 acl:0 sco:0 events:224 errors:0 TX bytes:43852 acl:0 sco:0 commands:224 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1818530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes
This has been happening to me for 3-4 years. I'm nearly ready to trash the AMD Athlon Please Please fix this... -- 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/1746638 Title: [GeForce 6150SE nForce 430] PC freezes and crashes Status in xorg package in Ubuntu: Confirmed Bug description: When using the nouveau graphics driver my pc freezes and crashes. WORKAROUND: Use the proprietary nvidia driver. WORKAROUND: Use PPA from https://launchpad.net/~oibaf/+archive/ubuntu /graphics-drivers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Thu Feb 1 01:36:25 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] [1043:8234] InstallationDate: Installed on 2017-11-23 (69 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus CX3900/DX4000/DX4050] Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-MX SE Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 1 01:34:53 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 1241:1166MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS
This bug was fixed in the package pygobject - 3.26.1-2ubuntu1 --- pygobject (3.26.1-2ubuntu1) bionic; urgency=medium * Update Vcs fields for ubuntu/bionic branch * Cherry-pick fix-tests-with-newest-glib.patch: - Fix pygobject build test failure with glib2.0 2.56 (LP: #1813591) -- Jeremy Bicha Tue, 29 Jan 2019 07:46:03 -0500 ** Changed in: pygobject (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1813591 Title: pygobject ftbfs in 18.04 LTS Status in pygobject package in Ubuntu: Fix Released Status in pygobject source package in Bionic: Fix Released Bug description: Impact -- pygobject doesn't build from source which means someone would need to fix that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 LTS. Test Case - Does pygobject build successfully? Regression Potential pygobject 3.28 is the intended version to match glib 2.56 but it missed the deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to fix the build tests with 18.04's glib2.0 2.56. The only change that is made in this upload is to the tests. There should be no effect on anything else. https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7 Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): File "/<>/tests/test_glib.py", line 66, in test_filenames self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) torture test 1 (1 iterations): 0.012186 secs torture test 2 (1 iterations): 0.068459 secs torture test 3 (1 iterations): 0.029216 secs torture test 4 (1 iterations): 0.065890 secs Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1813591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813591] Update Released
The verification of the Stable Release Update for pygobject has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1813591 Title: pygobject ftbfs in 18.04 LTS Status in pygobject package in Ubuntu: Fix Released Status in pygobject source package in Bionic: Fix Released Bug description: Impact -- pygobject doesn't build from source which means someone would need to fix that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 LTS. Test Case - Does pygobject build successfully? Regression Potential pygobject 3.28 is the intended version to match glib 2.56 but it missed the deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to fix the build tests with 18.04's glib2.0 2.56. The only change that is made in this upload is to the tests. There should be no effect on anything else. https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7 Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): File "/<>/tests/test_glib.py", line 66, in test_filenames self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) torture test 1 (1 iterations): 0.012186 secs torture test 2 (1 iterations): 0.068459 secs torture test 3 (1 iterations): 0.029216 secs torture test 4 (1 iterations): 0.065890 secs Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1813591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801439] Re: Unable to add software sources via the software-properties-qt
** Changed in: software-properties (Ubuntu) Assignee: Simon Quigley (tsimonq2) => Hans P Möller (hmollercl) -- 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/1801439 Title: Unable to add software sources via the software-properties-qt Status in software-properties package in Ubuntu: Triaged Bug description: Test 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the example repo given in the dialog, which is not a PPA) 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked self.add_source_from_line(line) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line enable_source_code=enable_source_code) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52 2018 InstallationDate: Installed on 2018-10-19 (14 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) 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/1801439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
There is only one bug task for this bug report and the default bug task in that case is meant to target the development release of Ubuntu, subsequently it is not clear if this bug is fixed in Disco. Is it? Additionally, is it fixed in Ubuntu 18.10? ** Changed in: cups (Ubuntu) Status: Confirmed => Incomplete -- 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/1783298 Title: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Incomplete Bug description: [Impact] If a print queue is set up with "auth-info-required=negotiate" because the server requires authentication (for example Kerberos) the user is asked for user name and password on every jon, insteaf of the authentication working automatically. This worked correctly in 14.04 and 16.04. Also setting "AuthType Default" for "/" in cupsd.conf leads to be prompted for a password on commands like "lpatat -a", even for root. Works correctly in Xenial and Cosmic. [Test Case] Set up a queue pointing to a Kerberos-authenticated Windows server with "lpadmin ... -o auth-info-required=negotiate ..." OR set "AuthType Default" for "/" in cupsd.conf. When printing or running other commands accessing your print queue you will get prompted for credentials. With the fix the authentication will get automatic again. [Regression Potential] Low, as the fix are simple one-line corrections taken from upstream. [Original report] Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1732962] Re: apport uses sys.argv instead of named arguments
This bug was fixed in the package apport - 2.20.10-0ubuntu23
---
apport (2.20.10-0ubuntu23) disco; urgency=medium
* Fix python coding style issue introduced in previous upload.
-- Julian Andres Klode Tue, 05 Mar 2019 10:35:17
+0100
** Changed in: apport (Ubuntu Disco)
Status: Fix Committed => Fix Released
--
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/1732962
Title:
apport uses sys.argv instead of named arguments
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Trusty:
New
Status in apport source package in Xenial:
New
Status in apport source package in Bionic:
New
Status in apport source package in Cosmic:
New
Status in apport source package in Disco:
Fix Released
Bug description:
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with
some security updates where we were trying to support a new version of
apport on a host system and one inside a container. Here's something
of an example:
347 # Normal startup
348 if len(sys.argv) not in (5, 6):
349 try:
350 print('Usage: %s [global pid]' % sys.argv[0])
351 print('The core dump is read from stdin.')
We could not maintain backwards compatibility because "global pid" is
an optional argument and "dump mode" was a new argument. So if there
were five arguments its possible the last one was "dump mode" (no
global pid) or "global pid" (no support for dump mode).
Its possible to use strings in /proc/sys/kernel/core_pattern so we
could use those and have apport accept named arguments e.g:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d
--global-pid=%P
['/home/bdmurray/source-trees/apport/artful/data/apport', '--
pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
pid=5870']
Tyler said "that's probably a nice cleanup to make no matter what
because the magic arg ordering is dangerous".
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1010421] Re: Text antialiasing is green.....
Did you try if it's still an issue with the Debian in recent versions of Ubuntu? -- 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/1010421 Title: Text antialiasing is green. Status in fontconfig package in Ubuntu: Confirmed Bug description: g. So upgraded to Gimp 2.8 and now text antialaising is green. Use white text on a black background to check it out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1010421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817048] Re: apt/trusty: Stack overflow in apt-ftparchive; on arm64, breaking about a third of the tests
Hello Julian, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.21 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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1817048 Title: apt/trusty: Stack overflow in apt-ftparchive; on arm64, breaking about a third of the tests Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Committed Bug description: [Impact] autopkgtest suite on arm64 is basically useless, as about a third of the tests do not work, because they rely on apt-ftparchive generating an archive [Test case] Substantially less tests should fail, there should be no segfaults. [Regression potential] I am cherry-picking a fix that changes statically length arrays (that are too small) to vector. A possible regression could be fields missing I guess, it should definitely be easily noticeable. Low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1817048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817088] Re: (silent) testsuite failure in test-apt-progress-fd-errror
Hello Julian, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.21 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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1817088 Title: (silent) testsuite failure in test-apt-progress-fd-errror Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Committed Bug description: [Impact] test-apt-progress-fd-error is failing on trusty due to a space difference, but the failure is not causing the tests to fail. [Test case] The fix fixes the test case and rewrites it to also detect failure. We can however, only detect success in the testsuite, as we do not have a testsuite testsuite :) [Regression potential] If something is wrong with the change, it could cause the tests to fail even though they are good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1817088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815761] Re: Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be invoked
Hello Julian, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.21 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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815761 Title: Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be invoked Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Committed Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able to show some extra output even if no changes had been made. Imagine "the user disabled the security repo, and does not get any updates shown scenario" - we'd like to be able to tell them that there are security updates available after all. [Test case] 1. Specify an APT::Install::Post-Invoke-Success hook 2. Make sure it runs even if there are no changes, using apt upgrade -tnow [Regression potential] No-change upgrades/install can now fail if this new hooks fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic
Hello Dean, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.30 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-xenial ** Changed in: apt (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Trusty: Fix Committed Status in linux-meta source package in Trusty: New Status in linux-meta-hwe source package in Trusty: New Status in apt source package in Xenial: Fix Committed Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Released Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully
[Touch-packages] [Bug 1787460] Please test proposed package
Hello Dean, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.21 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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Trusty: Fix Committed Status in linux-meta source package in Trusty: New Status in linux-meta-hwe source package in Trusty: New Status in apt source package in Xenial: Fix Committed Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Released Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
[Touch-packages] [Bug 1811120] Re: Backport auth.conf.d
Hello Julian, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.21 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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1811120 Title: Backport auth.conf.d Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Committed Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Status in apt source package in Disco: Fix Released Bug description: [Impact] Backport auth.conf.d support to allow specifying per-repository authentication data in separate files, so packages can setup authenticated repositories. [Regression potential] We ignore errors from opening auth.conf.d files, so regressions can only occur when parsing a file fails, in which case apt would exit with an error. [Test case] The test suite provides autopkgtests for auth.conf.d which creates an auth.conf.d file and checks that it is successfully used; so we can check if those passed. Except on trusty- do it manually there, by adding a file for a private ppa, and then running update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1811120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814727] Re: Backport never pinning and Packages-Require-Authorization
Hello Julian, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.21 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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1814727 Title: Backport never pinning and Packages-Require-Authorization Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Committed Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] These are not driven from a direct user experience, but are related to other developments: (1) unattended-upgrades could use the never pinning to disable repositories rather than switching candidates. That would simplify code quite a bit. (2) Packages-Require-Authorization lets a repository declare that downloading packages from it requires authorization. This is useful both for private repositories, as it can prevent unattended-upgrades failures if you remove authorization info; and it also allows creating a new form of semi-private repository, where only pool/ requires authorization. [Test case] Tests are included in autopkgtests and cover the common scenarios https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-packages-require-authorization: (1) Add repository with Packages-Require-Authorization and no auth.conf entry: pin -32768 (2) Add repository with Packages-Require-Authorization and a auth.conf entry: pin 500 (3) As (2), but a custom pin still applies https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-policy-pinning#L365 (1) Test that Pin-Priority: never overrides both per-package pins and per-repository pins (2) Test that Pin-Priority: never is only applied for per-repository (Package: *) pins Tests in older releases should be the same, but it's not clear yet. Bug will be updated once the SRUs are ready. [Regression potential] The changes might introduce regressions in pinning. The pinning implementation in trusty is substantially different from the other releases, and should thus require more testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815760] Re: Additional hooks for update
Hello Julian, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.30 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815760 Title: Additional hooks for update Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] We want to write some scripts for apt that run on update if apt shows an update count, to provide further details about the new cache. [Test case] Specify a APT::Update-Post-Invoke-Stats script and check that (1) it shows in apt update (2) it does not show in apt-get update [Regression potential] More scripts may fail the update now, but there should not be any registered so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814727] Re: Backport never pinning and Packages-Require-Authorization
Hello Julian, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.30 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1814727 Title: Backport never pinning and Packages-Require-Authorization Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] These are not driven from a direct user experience, but are related to other developments: (1) unattended-upgrades could use the never pinning to disable repositories rather than switching candidates. That would simplify code quite a bit. (2) Packages-Require-Authorization lets a repository declare that downloading packages from it requires authorization. This is useful both for private repositories, as it can prevent unattended-upgrades failures if you remove authorization info; and it also allows creating a new form of semi-private repository, where only pool/ requires authorization. [Test case] Tests are included in autopkgtests and cover the common scenarios https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-packages-require-authorization: (1) Add repository with Packages-Require-Authorization and no auth.conf entry: pin -32768 (2) Add repository with Packages-Require-Authorization and a auth.conf entry: pin 500 (3) As (2), but a custom pin still applies https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-policy-pinning#L365 (1) Test that Pin-Priority: never overrides both per-package pins and per-repository pins (2) Test that Pin-Priority: never is only applied for per-repository (Package: *) pins Tests in older releases should be the same, but it's not clear yet. Bug will be updated once the SRUs are ready. [Regression potential] The changes might introduce regressions in pinning. The pinning implementation in trusty is substantially different from the other releases, and should thus require more testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811120] Re: Backport auth.conf.d
Hello Julian, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.30 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1811120 Title: Backport auth.conf.d Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Status in apt source package in Disco: Fix Released Bug description: [Impact] Backport auth.conf.d support to allow specifying per-repository authentication data in separate files, so packages can setup authenticated repositories. [Regression potential] We ignore errors from opening auth.conf.d files, so regressions can only occur when parsing a file fails, in which case apt would exit with an error. [Test case] The test suite provides autopkgtests for auth.conf.d which creates an auth.conf.d file and checks that it is successfully used; so we can check if those passed. Except on trusty- do it manually there, by adding a file for a private ppa, and then running update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1811120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
Hello Eric, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.30 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] APT documentation/example/manpages isn't referencing the current release which could be misleading for certain users. --- APT src code: --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Xenial and late in APT points to 'trusty or 'xenial' which generate the doc example & manpage with the wrong release instead of the actual ubuntu-codename. APT in Xenial point to 'trusty'. APT in Bionic and late to 'xenial' It also affect the man page: Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html [Test Case] With Xenial and late: * Look sources.list(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html * Look apt_preferences(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html * Look /usr/share/doc/apt/examples/sources.list $ lsb_release -cs bionic $ cat /usr/share/doc/apt/examples/sources.list # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu xenial main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted deb http://security.ubuntu.com/ubuntu xenial-security main restricted deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted -- You'll notice they all point to the wrong release. While we understand it's not a "bug' and only a reference/example... I think it's for the best interest of all if the examples/manpage reference the current release. [Regression Potential] * None, it only affect documentation/examples and manpages. No behavior change in the APT code. [Other Info] [Original Description] From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic:
[Touch-packages] [Bug 1815750] Re: autopkgtest failure due to security update
Hello Dan, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.30 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1815750 Title: autopkgtest failure due to security update Status in apt package in Ubuntu: New Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Invalid Status in apt source package in Cosmic: Invalid Bug description: [impact] the security update for: SECURITY UPDATE: content injection in http method (CVE-2019-3462) (LP: #1812353) causes an autopkgtest failure for: Failed tests: test-cve-2019-3462-dequote-injection [test case] run autopkgtest on the security-patched version [regression potential] the test needs to be updated, so the regression potential is around the test continuing to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815761] Re: Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be invoked
Hello Julian, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.30 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815761 Title: Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be invoked Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able to show some extra output even if no changes had been made. Imagine "the user disabled the security repo, and does not get any updates shown scenario" - we'd like to be able to tell them that there are security updates available after all. [Test case] 1. Specify an APT::Install::Post-Invoke-Success hook 2. Make sure it runs even if there are no changes, using apt upgrade -tnow [Regression potential] No-change upgrades/install can now fail if this new hooks fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814543] Please test proposed package
Hello Julian, or anyone else affected,
Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.9 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1814543
Title:
deal with EPIPE from json hooks
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Cosmic:
Fix Committed
Status in apt source package in Disco:
Fix Released
Bug description:
[Impact]
json hooks ending with EPIPE on first read fail, but should simply do
nothing. This causes spurious failures of uninstalled hooks.
Also, there is a missing error exit, causing errors reported by the
script to not exit.
[Test case]
For the first part, I cannot generate one. This was discovered by snapd ci,
but I did not find a reproducer yet.
FWIW, the change should be tiny enough to see that it is not wrong:
-if (errno != ECONNRESET)
+if (errno != ECONNRESET && errno != EPIPE)
_error->Error("Could not read response to hello message from hook
%s: %s", Opts->Value.c_str(), strerror(errno));
The missing error handling is the next lines:
else if (strstr(line, "error") != nullptr)
{
_error->Error("Hook %s reported an error during hello: %s",
Opts->Value.c_str(), line);
+goto out;
}
that can be checked:
sudo apt -o AptCli::Hooks::Install::="/usr/bin/printf '{error should
be json}\n\n' >&3" install
[Regression potential]
JSON hooks failures with EPIPE are now ignored, so if it fails with EPIPE for
other reasons than just exiting, I guess we might miss it
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814543/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814543] Re: deal with EPIPE from json hooks
Hello Julian, or anyone else affected,
Accepted apt into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.7.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: apt (Ubuntu Cosmic)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-cosmic
** Changed in: apt (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1814543
Title:
deal with EPIPE from json hooks
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Cosmic:
Fix Committed
Status in apt source package in Disco:
Fix Released
Bug description:
[Impact]
json hooks ending with EPIPE on first read fail, but should simply do
nothing. This causes spurious failures of uninstalled hooks.
Also, there is a missing error exit, causing errors reported by the
script to not exit.
[Test case]
For the first part, I cannot generate one. This was discovered by snapd ci,
but I did not find a reproducer yet.
FWIW, the change should be tiny enough to see that it is not wrong:
-if (errno != ECONNRESET)
+if (errno != ECONNRESET && errno != EPIPE)
_error->Error("Could not read response to hello message from hook
%s: %s", Opts->Value.c_str(), strerror(errno));
The missing error handling is the next lines:
else if (strstr(line, "error") != nullptr)
{
_error->Error("Hook %s reported an error during hello: %s",
Opts->Value.c_str(), line);
+goto out;
}
that can be checked:
sudo apt -o AptCli::Hooks::Install::="/usr/bin/printf '{error should
be json}\n\n' >&3" install
[Regression potential]
JSON hooks failures with EPIPE are now ignored, so if it fails with EPIPE for
other reasons than just exiting, I guess we might miss it
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814543/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
Hello Eric, or anyone else affected, Accepted apt into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.7.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: apt (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] APT documentation/example/manpages isn't referencing the current release which could be misleading for certain users. --- APT src code: --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Xenial and late in APT points to 'trusty or 'xenial' which generate the doc example & manpage with the wrong release instead of the actual ubuntu-codename. APT in Xenial point to 'trusty'. APT in Bionic and late to 'xenial' It also affect the man page: Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html [Test Case] With Xenial and late: * Look sources.list(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html * Look apt_preferences(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html * Look /usr/share/doc/apt/examples/sources.list $ lsb_release -cs bionic $ cat /usr/share/doc/apt/examples/sources.list # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu xenial main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted deb http://security.ubuntu.com/ubuntu xenial-security main restricted deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted -- You'll notice they all point to the wrong release. While we understand it's not a "bug' and only a reference/example... I think it's for the best interest of all if the examples/manpage reference the current release. [Regression Potential] * None, it only affect documentation/examples and manpages. No behavior change in the APT code. [Other Info] [Original Description] From APT src code : --- [GOOD ubuntu-codename] * trusty:
[Touch-packages] [Bug 1812696] Please test proposed package
Hello Eric, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.9 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] APT documentation/example/manpages isn't referencing the current release which could be misleading for certain users. --- APT src code: --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Xenial and late in APT points to 'trusty or 'xenial' which generate the doc example & manpage with the wrong release instead of the actual ubuntu-codename. APT in Xenial point to 'trusty'. APT in Bionic and late to 'xenial' It also affect the man page: Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html [Test Case] With Xenial and late: * Look sources.list(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html * Look apt_preferences(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html * Look /usr/share/doc/apt/examples/sources.list $ lsb_release -cs bionic $ cat /usr/share/doc/apt/examples/sources.list # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu xenial main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted deb http://security.ubuntu.com/ubuntu xenial-security main restricted deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted -- You'll notice they all point to the wrong release. While we understand it's not a "bug' and only a reference/example... I think it's for the best interest of all if the examples/manpage reference the current release. [Regression Potential] * None, it only affect documentation/examples and manpages. No behavior change in the APT code. [Other Info] [Original Description] From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See
[Touch-packages] [Bug 1815760] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.9 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815760 Title: Additional hooks for update Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] We want to write some scripts for apt that run on update if apt shows an update count, to provide further details about the new cache. [Test case] Specify a APT::Update-Post-Invoke-Stats script and check that (1) it shows in apt update (2) it does not show in apt-get update [Regression potential] More scripts may fail the update now, but there should not be any registered so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814727] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.9 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1814727 Title: Backport never pinning and Packages-Require-Authorization Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] These are not driven from a direct user experience, but are related to other developments: (1) unattended-upgrades could use the never pinning to disable repositories rather than switching candidates. That would simplify code quite a bit. (2) Packages-Require-Authorization lets a repository declare that downloading packages from it requires authorization. This is useful both for private repositories, as it can prevent unattended-upgrades failures if you remove authorization info; and it also allows creating a new form of semi-private repository, where only pool/ requires authorization. [Test case] Tests are included in autopkgtests and cover the common scenarios https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-packages-require-authorization: (1) Add repository with Packages-Require-Authorization and no auth.conf entry: pin -32768 (2) Add repository with Packages-Require-Authorization and a auth.conf entry: pin 500 (3) As (2), but a custom pin still applies https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-policy-pinning#L365 (1) Test that Pin-Priority: never overrides both per-package pins and per-repository pins (2) Test that Pin-Priority: never is only applied for per-repository (Package: *) pins Tests in older releases should be the same, but it's not clear yet. Bug will be updated once the SRUs are ready. [Regression potential] The changes might introduce regressions in pinning. The pinning implementation in trusty is substantially different from the other releases, and should thus require more testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815761] Please test proposed package
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.9 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815761 Title: Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be invoked Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able to show some extra output even if no changes had been made. Imagine "the user disabled the security repo, and does not get any updates shown scenario" - we'd like to be able to tell them that there are security updates available after all. [Test case] 1. Specify an APT::Install::Post-Invoke-Success hook 2. Make sure it runs even if there are no changes, using apt upgrade -tnow [Regression potential] No-change upgrades/install can now fail if this new hooks fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814727] Re: Backport never pinning and Packages-Require-Authorization
Hello Julian, or anyone else affected, Accepted apt into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.7.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Cosmic) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: apt (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1814727 Title: Backport never pinning and Packages-Require-Authorization Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] These are not driven from a direct user experience, but are related to other developments: (1) unattended-upgrades could use the never pinning to disable repositories rather than switching candidates. That would simplify code quite a bit. (2) Packages-Require-Authorization lets a repository declare that downloading packages from it requires authorization. This is useful both for private repositories, as it can prevent unattended-upgrades failures if you remove authorization info; and it also allows creating a new form of semi-private repository, where only pool/ requires authorization. [Test case] Tests are included in autopkgtests and cover the common scenarios https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-packages-require-authorization: (1) Add repository with Packages-Require-Authorization and no auth.conf entry: pin -32768 (2) Add repository with Packages-Require-Authorization and a auth.conf entry: pin 500 (3) As (2), but a custom pin still applies https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-policy-pinning#L365 (1) Test that Pin-Priority: never overrides both per-package pins and per-repository pins (2) Test that Pin-Priority: never is only applied for per-repository (Package: *) pins Tests in older releases should be the same, but it's not clear yet. Bug will be updated once the SRUs are ready. [Regression potential] The changes might introduce regressions in pinning. The pinning implementation in trusty is substantially different from the other releases, and should thus require more testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815761] Re: Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be invoked
Hello Julian, or anyone else affected, Accepted apt into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.7.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: apt (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815761 Title: Alternative to Dpkg::Post-Invoke that runs even if dpkg did not have to be invoked Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able to show some extra output even if no changes had been made. Imagine "the user disabled the security repo, and does not get any updates shown scenario" - we'd like to be able to tell them that there are security updates available after all. [Test case] 1. Specify an APT::Install::Post-Invoke-Success hook 2. Make sure it runs even if there are no changes, using apt upgrade -tnow [Regression potential] No-change upgrades/install can now fail if this new hooks fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815760] Re: Additional hooks for update
Hello Julian, or anyone else affected, Accepted apt into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.7.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apt (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: apt (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1815760 Title: Additional hooks for update Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] We want to write some scripts for apt that run on update if apt shows an update count, to provide further details about the new cache. [Test case] Specify a APT::Update-Post-Invoke-Stats script and check that (1) it shows in apt update (2) it does not show in apt-get update [Regression potential] More scripts may fail the update now, but there should not be any registered so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817302] Re: growpart changes diskid of mbr disks
This bug was fixed in the package util-linux - 2.33.1-0.1ubuntu2 --- util-linux (2.33.1-0.1ubuntu2) disco; urgency=medium * debian/patches/32-bit-safe-mbr-parsing.patch: [PATCH] libfdisk: (dos) Use strtoul to parse the label-id. Thanks to Juerg Haefliger . LP: #1817302. -- Steve Langasek Fri, 22 Feb 2019 21:46:00 +0100 ** Changed in: util-linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1817302 Title: growpart changes diskid of mbr disks Status in util-linux package in Ubuntu: Fix Released Bug description: When growpart is run against a disk with a dos partition table, it evidently changes the disk id in the MBR. This was noticed because the diskid is part of the "PARTUUID" that is synthesized for DOS partitions (unlike GPT, which has UUIDs for each partition as part of the partition table). This means that if someone is using root=PARTUUID=foo on the kernel commandline, the cloud image will successfully boot exactly once, and subsequently fail to boot because the partition uuid has changed. I don't know at this point if this is a bug in cloud-utils or in sfdisk (util-linux). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1817302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session
@Donvdh, Thanks I'll have a look at it probably next week. Thanks ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Fix Released Status in pam source package in Xenial: In Progress Status in pam source package in Bionic: Fix Committed Status in pam source package in Cosmic: Fix Committed Status in pam package in Debian: Fix Released Bug description: [Impact] * Kernel keystroke auditing via pam_tty_audit.so not working * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. [Test Case] 1) Open a shell & escalate to root 2) Update /etc/pam.d/common-session & /etc/pam.d/common-session-noninteractive and add the following line directly after the line: "session required pam_unix.so": "session required pam_tty_audit.so enable=*" 3) Start a second new shell session on the box and type a variety of commands 4) Exit the second shell session to flush the buffer? 5) In the root shell run "aureport -tty -i". The output should show the commands run in the other shell. [Regression Potential] * Low, we are simply including the missing header file and copy the old status as initialization of new. The fix is already found/part of Debian and Disco. [Other Info] # Upstream fix: https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee # git describe --contains c5f829931a22c65feffee16570efdae036524bee Linux-PAM-1_2_0~75 # rmadision pam => pam | 1.1.8-1ubuntu2.2 | trusty-updates | source => pam | 1.1.8-3.2ubuntu2 | xenial | source => pam | 1.1.8-3.2ubuntu2.1 | xenial-updates | source => pam | 1.1.8-3.6ubuntu2 | bionic | source => pam | 1.1.8-3.6ubuntu2 | cosmic | source pam | 1.3.1-5ubuntu1 | disco| source [Original Description] Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299
[Touch-packages] [Bug 1812760] Re: networkd: [Route] PreferredSource not working in *.network files
** Tags removed: verification-failed verification-failed-bionic verification-failed-cosmic -- 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/1812760 Title: networkd: [Route] PreferredSource not working in *.network files Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Released Bug description: [Impact] Users cannot create IPv6 routes that specify PreferredSource. This means that users cannot specify a number of valid IPv6 routes that are useful in some circumstances. These routes can be created with the 'ip' tool, just not with systemd. This was reported upstream in systemd issue #5882 is fixed by pulling in the changes in systemd PR #11375 - https://github.com/systemd/systemd/pull/11375 [Test Case] Start a Bionic or Cosmic VM. Add the following netplan yaml (adjust for ethernet card and MAC): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:e2:c2:d7 set-name: ens3 addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"] routes: - to: "a::/16" via: "fd8f:1d7d:b141::1" from: "fd8f:1d7d:b141::2" - to: "fd8f:1d7d:b141::/64" scope: link from: "fd8f:1d7d:b141::2" metric: 255 Run netplan apply or reboot. Wait ~10s. Currently, ip -6 route will not include a route to "a::/16", and will not include the route to "fd8f:1d7d:b141::/64" that has "fd8f:1d7d:b141::2" as the source address - both those addresses will be missing. Correct behaviour is for ip -6 route to report the following: ubuntu@b-np:~$ ip -6 route a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 metric 1024 pref medium fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 pref medium fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium Check before and after upgrade that 'systemctl status network- online.target' shows that the target has been reached. [Regression Potential] This changes the state machine in systemd which configures the links. It passes systemd's internal tests, and has been approved by systemd maintainers, but it remains possible that the changes will break the configuration of obscure network setups. The backport requires pulling in two further commits that also change behaviour: currently systemd deletes all addresses and routes that were attached to an interface. With this change, it will only delete those that are not specified in the configuration files. A side effect of this is that restarting networkd will not cause remove/add netlink events to be emitted for these addresses, so if anyone is relying on this behavior this will break compatibility; but that is an unlikely thing to be relying on, and it seems worth this risk to reduce unnecessary network state changes. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1812760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1818340] Re: systemd-networkd core dumps in bionic-proposed
Confirmed that 3ubuntu10.15 fixes the core-dump in systemd-networkd. -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] during restart, systemd-networkd fails an assertion and aborts, leaving the system networking partially (if at all) configured. Further restarts continue to fail. [Test Case] Install a bionic system (cosmic affected also) with only systemd- networkd networking (i.e. uninstall or do not configure netplan). Ensure no networkd conf files are in /run/systemd/network. Stop networkd (sudo systemctl stop systemd-networkd). The interface to test with networkd (e.g. ens3) should have no address assigned and should be down. Create a file similar to below, adjusting for interface name: $ cat /etc/systemd/network/10-netplan-ens3.network [Match] Name=ens3 [Network] Address=192.168.122.68/24 Start networkd: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Stop networkd; ens3 should retain its address: ubuntu@lp1818340-b:~$ sudo systemctl stop systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Start networkd again; the bug is triggered: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd Job for systemd-networkd.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status systemd-networkd.service" and "journalctl -xe" for details. Alternately, instead of separately stopping and then starting networkd, the failure can be reproduced with just a restart. Note the failure only happens with statically-assigned addresses; interfaces configured with dhcp do not trigger this bug. [Regression Potential] TBD [Other Info] This was introduced by the SRU for bug 1812760; both the new behavior of networkd not removing managed addresses/routes from managed interfaces, as well as the assertion failure bug. This does not fail in disco; I believe additional commit(s) from upstream need to be backported. Original description: --- I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799279] Re: kernel update hangs inside update-secureboot-policy
Sorry, that's Roger Wolff, with two f. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1799279 Title: kernel update hangs inside update-secureboot-policy Status in apt package in Ubuntu: Confirmed Bug description: I just ran `apt-get --auto-remove dist-upgrade` on 18.04. It is hung on update-secureboot-policy waiting for confirmation from whiptail. apt-get --auto-remove dist-upgrade | -/usr/bin/dpkg --status-fd 80 --configure --pending | -/bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-38-generic.postinst configure | -run-parts --report --exit-on-error --arg=4.15.0-38-generic /etc/kernel/header_postinst.d | -/bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-38-generic | -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic | -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic | -/usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/update-secureboot-policy --enroll-key | -/bin/sh /usr/sbin/update-secureboot-policy --enroll-key -whiptail --backtitle Package configuration --title Configuring Secure Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot enabled. UEFI Secure Boot requires additional configuration to work with third-party drivers. The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system's firmware. To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the "Enroll MOK" and "Change Secure Boot state" menus that will be presented to you when this system reboots. If you proceed but do not confirm the password upon reboot, Ubuntu will still be able to boot on your system but any hardware that requires third-party drivers to work correctly may not be usable. --scrolltext 20 77 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.3ubuntu0.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 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 15:15:56 2018 InstallationDate: Installed on 2018-09-27 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1799279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799279] Re: kernel update hangs inside update-secureboot-policy
I've had the very same issue for the first time with Kubuntu 16.04 LTS (that's not a typo, the issue is with both versions). Roger Wolf explained on AskUbuntu[1] that's it's because the output of whiptail is being redirected to /dev/null. And indeed, by answering the questions I could read thanks to htop, I got out of the hang flawlessly. I've done countless upgrades on the same machine in the past, and I've been asked the same question serveral times before without it being redirected to /dev/null, so I assume the issue is new for the 16.04. Maybe some recent backport of the 18.04 bug? [1] https://askubuntu.com/questions/1052000/all-kernel-upgrades-hang-on- update-secureboot-policy-enroll-key -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1799279 Title: kernel update hangs inside update-secureboot-policy Status in apt package in Ubuntu: Confirmed Bug description: I just ran `apt-get --auto-remove dist-upgrade` on 18.04. It is hung on update-secureboot-policy waiting for confirmation from whiptail. apt-get --auto-remove dist-upgrade | -/usr/bin/dpkg --status-fd 80 --configure --pending | -/bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-38-generic.postinst configure | -run-parts --report --exit-on-error --arg=4.15.0-38-generic /etc/kernel/header_postinst.d | -/bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-38-generic | -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic | -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic | -/usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/update-secureboot-policy --enroll-key | -/bin/sh /usr/sbin/update-secureboot-policy --enroll-key -whiptail --backtitle Package configuration --title Configuring Secure Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot enabled. UEFI Secure Boot requires additional configuration to work with third-party drivers. The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system's firmware. To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the "Enroll MOK" and "Change Secure Boot state" menus that will be presented to you when this system reboots. If you proceed but do not confirm the password upon reboot, Ubuntu will still be able to boot on your system but any hardware that requires third-party drivers to work correctly may not be usable. --scrolltext 20 77 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.3ubuntu0.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 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 15:15:56 2018 InstallationDate: Installed on 2018-09-27 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1799279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772512] Re: Unable to install i386 and amd64 arch at the same time
There was another upload with just security fixes which conflicted with the backport, but this is all sorted now and the backport is now on the queue and should be processed reviewed soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1772512 Title: Unable to install i386 and amd64 arch at the same time Status in libxkbcommon package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: In Progress Bug description: [Impact] libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the package isn't properly multi-archified in bionic [Test case] apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64 should succeed [Regression potential] not really -- Not sure if this is intended, but it's not possible to install two architectures of the libxkbcommon-dev at the same time. On Ubuntu 16.04 and 18.04 apt-get says that they are in conflict. The package is a dependency for libegl1-mesa-dev, which I need to have installed in 64 and 32-bit variants. Please see the example output below: $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic $ sudo apt-get install libxkbcommon-dev:* Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be installed libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814727] Re: Backport never pinning and Packages-Require-Authorization
Sure ** Changed in: apt (Ubuntu Disco) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1814727 Title: Backport never pinning and Packages-Require-Authorization Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: Incomplete Status in apt source package in Disco: Fix Released Bug description: [Impact] These are not driven from a direct user experience, but are related to other developments: (1) unattended-upgrades could use the never pinning to disable repositories rather than switching candidates. That would simplify code quite a bit. (2) Packages-Require-Authorization lets a repository declare that downloading packages from it requires authorization. This is useful both for private repositories, as it can prevent unattended-upgrades failures if you remove authorization info; and it also allows creating a new form of semi-private repository, where only pool/ requires authorization. [Test case] Tests are included in autopkgtests and cover the common scenarios https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-packages-require-authorization: (1) Add repository with Packages-Require-Authorization and no auth.conf entry: pin -32768 (2) Add repository with Packages-Require-Authorization and a auth.conf entry: pin 500 (3) As (2), but a custom pin still applies https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-policy-pinning#L365 (1) Test that Pin-Priority: never overrides both per-package pins and per-repository pins (2) Test that Pin-Priority: never is only applied for per-repository (Package: *) pins Tests in older releases should be the same, but it's not clear yet. Bug will be updated once the SRUs are ready. [Regression potential] The changes might introduce regressions in pinning. The pinning implementation in trusty is substantially different from the other releases, and should thus require more testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818201] Re: packagekitd crashed with SIGSEGV in __memmove_{sse2, avx}_unaligned_erms() from std::char_traits::copy() from ... from show_errors (errorCode=PK_ERROR_ENUM_CAN
Hello errors.ubuntu.com, or anyone else affected,
Accepted packagekit into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/packagekit/1.1.9-1ubuntu2.18.04.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-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: packagekit (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1818201
Title:
packagekitd crashed with SIGSEGV in
__memmove_{sse2,avx}_unaligned_erms() from
std::char_traits::copy() from ... from show_errors
(errorCode=PK_ERROR_ENUM_CANNOT_FETCH_SOURCES)
Status in packagekit package in Ubuntu:
Fix Released
Status in packagekit source package in Xenial:
Won't Fix
Status in packagekit source package in Bionic:
Fix Committed
Status in packagekit source package in Cosmic:
Fix Committed
Status in packagekit source package in Disco:
Fix Released
Bug description:
[Impact]
packagekit (sometimes) crashes when there are errors.
https://errors.ubuntu.com/problem/1bdc3e539949aa164d276979f62ca0282a54fcbd
https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034
[Test case]
Check that there are no further cases on the error tracker with the proposed
version.
[Regression potential]
Given that this just changes the return type of a function only used in
calls, and the code compiles, there should be no possibility for a regression.
Of course, if there were, it'd be segfaults or stuff.
[Original info]
The Ubuntu Error Tracker has been receiving reports about a problem regarding
packagekit. This problem was most recently seen with package version
1.1.12-1ubuntu1, the problem page at
https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1818201/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814727] Re: Backport never pinning and Packages-Require-Authorization
Is this fixed in Disco yet? ** Changed in: apt (Ubuntu Cosmic) Status: In Progress => Incomplete ** Changed in: apt (Ubuntu Disco) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1814727 Title: Backport never pinning and Packages-Require-Authorization Status in apt package in Ubuntu: Incomplete Status in apt source package in Trusty: In Progress Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: Incomplete Status in apt source package in Disco: Incomplete Bug description: [Impact] These are not driven from a direct user experience, but are related to other developments: (1) unattended-upgrades could use the never pinning to disable repositories rather than switching candidates. That would simplify code quite a bit. (2) Packages-Require-Authorization lets a repository declare that downloading packages from it requires authorization. This is useful both for private repositories, as it can prevent unattended-upgrades failures if you remove authorization info; and it also allows creating a new form of semi-private repository, where only pool/ requires authorization. [Test case] Tests are included in autopkgtests and cover the common scenarios https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-packages-require-authorization: (1) Add repository with Packages-Require-Authorization and no auth.conf entry: pin -32768 (2) Add repository with Packages-Require-Authorization and a auth.conf entry: pin 500 (3) As (2), but a custom pin still applies https://salsa.debian.org/apt-team/apt/blob/master/test/integration/test-policy-pinning#L365 (1) Test that Pin-Priority: never overrides both per-package pins and per-repository pins (2) Test that Pin-Priority: never is only applied for per-repository (Package: *) pins Tests in older releases should be the same, but it's not clear yet. Bug will be updated once the SRUs are ready. [Regression potential] The changes might introduce regressions in pinning. The pinning implementation in trusty is substantially different from the other releases, and should thus require more testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1814727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818201] Re: packagekitd crashed with SIGSEGV in __memmove_{sse2, avx}_unaligned_erms() from std::char_traits::copy() from ... from show_errors (errorCode=PK_ERROR_ENUM_CAN
Hello errors.ubuntu.com, or anyone else affected,
Accepted packagekit into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/packagekit/1.1.10-1ubuntu7.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: packagekit (Ubuntu Cosmic)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1818201
Title:
packagekitd crashed with SIGSEGV in
__memmove_{sse2,avx}_unaligned_erms() from
std::char_traits::copy() from ... from show_errors
(errorCode=PK_ERROR_ENUM_CANNOT_FETCH_SOURCES)
Status in packagekit package in Ubuntu:
Fix Released
Status in packagekit source package in Xenial:
Won't Fix
Status in packagekit source package in Bionic:
In Progress
Status in packagekit source package in Cosmic:
Fix Committed
Status in packagekit source package in Disco:
Fix Released
Bug description:
[Impact]
packagekit (sometimes) crashes when there are errors.
https://errors.ubuntu.com/problem/1bdc3e539949aa164d276979f62ca0282a54fcbd
https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034
[Test case]
Check that there are no further cases on the error tracker with the proposed
version.
[Regression potential]
Given that this just changes the return type of a function only used in
calls, and the code compiles, there should be no possibility for a regression.
Of course, if there were, it'd be segfaults or stuff.
[Original info]
The Ubuntu Error Tracker has been receiving reports about a problem regarding
packagekit. This problem was most recently seen with package version
1.1.12-1ubuntu1, the problem page at
https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1818201/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818167] Re: Canon Pixma TS6220 will not print with drvr Canon TS6000 series - CUPS+Gutenprint v5.2.13-2
No Gutenprint driver exists. See https://lists.cups.org/pipermail/cups/2019-March/074499.html This report should be closed. -- Brian. -- 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/1818167 Title: Canon Pixma TS6220 will not print with drvr Canon TS6000 series - CUPS+Gutenprint v5.2.13-2 Status in cups package in Ubuntu: New Bug description: Ubuntu 18.04.2 LTS CUPS Installed: 2.2.7-1ubuntu2.3 The printer can print using drvr Canon TS6200 series Ver.5.70(en). But with the Gutenprint driver, printing files or test pages causes a response on the control panel of the printer, but no action mechanically. When the control panel returns to its normal idle state, the "job" is reported as completed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:47:42 2019 InstallationDate: Installed on 2018-08-04 (209 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for Canon_Gutenprint_Driver: usb://Canon/TS6200%20series?serial=30644B=1 device for Canon_Pixma_TS6220: usb://Canon/TS6200%20series?serial=30644B=1 MachineType: Acer Aspire XC-603 Papersize: letter PpdFiles: Canon_Pixma_TS6220: Canon TS6200 series Ver.5.70 Canon_Gutenprint_Driver: Canon TS6000 series - CUPS+Gutenprint v5.2.13 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5ed3623f-f174-4ac2-b301-9dd35c726d45 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-B4 dmi.board.name: Aspire XC-603 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-B4:bd09/15/2015:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Aspire XC-603 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1818167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818713] Re: WARNING: icon cache generation failed when installing elementary-icon-theme
** Package changed: apport (Ubuntu) => gtk+3.0 (Ubuntu) -- 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/1818713 Title: WARNING: icon cache generation failed when installing elementary-icon- theme Status in gtk+3.0 package in Ubuntu: New Bug description: WHen installing elementary-icon-theme, receive the message: gtk-update-icon-cache: The generated cache was invalid. WARNING: icon cache generation failed for /usr/share/icons/elementary I believe this is because there is a folder with a space in the name: root@howard:/usr/share/icons/elementary# find ./ -name "* *" ./status/48/untitled folder After removing that directory, the cache is created successfully: root@howard:/usr/share/icons/elementary# rm -rf "./status/48/untitled folder" root@howard:/usr/share/icons/elementary# gtk-update-icon-cache /usr/share/icons/elementary gtk-update-icon-cache: Cache file created successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1818713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818713] Re: WARNING: icon cache generation failed when installing elementary-icon-theme
Please note: the package is elementary-icon-theme, however when I try to select that package in the bug reporter, i get the following message (have tried waiting): Sorry, something went wrong with your search. Trying again in a couple of minutes might work. (Error ID: OOPS-8d80495a1fce50039808450d1db713b0) -- 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/1818713 Title: WARNING: icon cache generation failed when installing elementary-icon- theme Status in apport package in Ubuntu: New Bug description: WHen installing elementary-icon-theme, receive the message: gtk-update-icon-cache: The generated cache was invalid. WARNING: icon cache generation failed for /usr/share/icons/elementary I believe this is because there is a folder with a space in the name: root@howard:/usr/share/icons/elementary# find ./ -name "* *" ./status/48/untitled folder After removing that directory, the cache is created successfully: root@howard:/usr/share/icons/elementary# rm -rf "./status/48/untitled folder" root@howard:/usr/share/icons/elementary# gtk-update-icon-cache /usr/share/icons/elementary gtk-update-icon-cache: Cache file created successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1818713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818713] [NEW] WARNING: icon cache generation failed when installing elementary-icon-theme
Public bug reported: WHen installing elementary-icon-theme, receive the message: gtk-update-icon-cache: The generated cache was invalid. WARNING: icon cache generation failed for /usr/share/icons/elementary I believe this is because there is a folder with a space in the name: root@howard:/usr/share/icons/elementary# find ./ -name "* *" ./status/48/untitled folder After removing that directory, the cache is created successfully: root@howard:/usr/share/icons/elementary# rm -rf "./status/48/untitled folder" root@howard:/usr/share/icons/elementary# gtk-update-icon-cache /usr/share/icons/elementary gtk-update-icon-cache: Cache file created successfully. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- 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/1818713 Title: WARNING: icon cache generation failed when installing elementary-icon- theme Status in apport package in Ubuntu: New Bug description: WHen installing elementary-icon-theme, receive the message: gtk-update-icon-cache: The generated cache was invalid. WARNING: icon cache generation failed for /usr/share/icons/elementary I believe this is because there is a folder with a space in the name: root@howard:/usr/share/icons/elementary# find ./ -name "* *" ./status/48/untitled folder After removing that directory, the cache is created successfully: root@howard:/usr/share/icons/elementary# rm -rf "./status/48/untitled folder" root@howard:/usr/share/icons/elementary# gtk-update-icon-cache /usr/share/icons/elementary gtk-update-icon-cache: Cache file created successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1818713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818679] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Hello, can you please run this command and report back the results? ls -ld / Thanks -- 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/1818679 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in openssh package in Ubuntu: New Bug description: I can't tell you anything. There was a error message without specific details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 5 06:48:59 2019 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2016-08-12 (935 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1818679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818691] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hello, can you please run this command and report back the results? ls -ld / Thanks -- 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/1818691 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 5 15:29:31 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-01-21 (43 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 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/openssh/+bug/1818691/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1010421] Re: Text antialiasing is green.....
Runnig Gimp using flatpak fixes this problem. So most likely the problem is some dependency related with Gimp. Official bug: https://gitlab.gnome.org/GNOME/gimp/issues/3065 -- 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/1010421 Title: Text antialiasing is green. Status in fontconfig package in Ubuntu: Confirmed Bug description: g. So upgraded to Gimp 2.8 and now text antialaising is green. Use white text on a black background to check it out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1010421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817527] Re: ufw status problem
Thank you for reporting a bug. What you are seeing is normal and this is nothing to worry about. The ufw systemd service is not long running but a oneshot service. ** Changed in: ufw (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1817527 Title: ufw status problem Status in ufw package in Ubuntu: Invalid Bug description: I recently have a spontaneous problem when running the command "service ufw status" and below picture is a result that shows me "active (exited)" status how can fix it ??? thanks a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1817527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766337] Re: uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't decode byte; invalid continuation byte
DpkgTerminalLog.txt still appears in an update-manager crash report
using the version of apport from bionic-proposed.
bdmurray@clean-bionic-amd64:~$ grep -A4 DpkgTerminal
/var/crash/_usr_bin_update-manager.1000.crash
DpkgTerminalLog.txt:
Log started: 2019-03-05 09:00:54
(Reading database ... 166173 files and directories currently installed.)
Removing apport-noui (2.20.9-0ubuntu7.6) ...
Failed to stop apport-noui.path: Unit apport-noui.path not loaded.
bdmurray@clean-bionic-amd64:~$ apt-cache policy apport
apport:
Installed: 2.20.9-0ubuntu7.6
Candidate: 2.20.9-0ubuntu7.6
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
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/1766337
Title:
uncaught python exception : UnicodeDecodeError: 'utf-8' codec can't
decode byte; invalid continuation byte
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
Fix Committed
Bug description:
[Impact]
Ubuntu crash reports and package installation failures may not include
DpkgTerminalLog.txt if there is a UnicodeDecodeError trying to read the dpkg
log file.
[Test Case]
Because the fix is simple and its complicated to have a dpkg log file with
unicode in it we'll just test that truncating of a dpkg log file still works.
1) Install 2vcard (so we have a recent dpkg log entry)
2) Run update-manager
3) Kill it with signal 11 e.g. kill -11 $PID of update-manager
4) Run ubuntu-bug /var/crash/_usr_bin_update-manager.1000.crash
5) Observe DpkgTerminalLog.txt only contains a log entry regarding the
installation of 2vcard and matches the content in /var/log/apt/term.log.
[Regression Potential]
Its possible that the code to replace the DpkgTerminalLog contents of the
report is wrong but the test case above ensures that it isn't.
[Original Description]
Hi,
here is a python exception I got while reporting a bug:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 89, in add_info
check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 208, in
check_attachment_for_errors
trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in trim_dpkg_log
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 508, in
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line
in lines])
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 3070:
invalid continuation byte
It can also be seen here:
https://launchpadlibrarian.net/367002573/HookError_ubuntu.txt
ProblemType: BugDistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu6
Uname: Linux 4.16.3-041603-generic x86_64
ApportLog:
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Apr 23 20:13:24 2018
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bashSourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1766337/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
I installed apport version 2.20.9-0ubuntu7.6 from bionic-proposed and ran through the test case from the bug description and can confirm that automatic reporting was enabled and that there were no issues with whoopsie. bdmurray@clean-bionic-amd64:~$ systemctl status apport-autoreport.service ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled) Active: inactive (dead) since Tue 2019-03-05 08:49:56 PST; 4min 13s ago Process: 589 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, status=0/SUCCESS) Main PID: 589 (code=exited, status=0/SUCCESS) Mar 05 08:49:55 clean-bionic-amd64 systemd[1]: Starting Process error reports when automatic reporting is enabled... Mar 05 08:49:56 clean-bionic-amd64 systemd[1]: Started Process error reports when automatic reporting is enabled. bdmurray@clean-bionic-amd64:~$ apt-cache policy apport apport: Installed: 2.20.9-0ubuntu7.6 Candidate: 2.20.9-0ubuntu7.6 I'd prefer if somebody experiencing the issue on Ubuntu 18.04 could verify it though. -- 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/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Status in apport source package in Cosmic: Fix Released Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818700] [NEW] some problems
Public bug reported: Nautilus doesn t work - as I try to manage files thru grafical way it just causes my screen flashig in a fast way ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 5 18:32:29 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:105c] NVIDIA Corporation GF108M [GeForce GT 620M/630M/635M/640M LE] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 630M] [1043:2128] InstallationDate: Installed on 2018-03-06 (364 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: ASUSTeK Computer Inc. K93SM ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=dc7bbf0d-c12f-4b29-9787-54ac74c97c4e ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K93SM 204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K93SM 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.:bvrK93SM204:bd12/16/2011:svnASUSTeKComputerInc.:pnK93SM:pvr1.0:rvnASUSTeKComputerInc.:rnK93SM:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K93SM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- 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/1818700 Title: some problems Status in xorg package in Ubuntu: New Bug description: Nautilus doesn t work - as I try to manage files thru grafical way it just causes my screen flashig in a fast way ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 5 18:32:29 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:105c] NVIDIA Corporation GF108M [GeForce GT 620M/630M/635M/640M LE] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 630M] [1043:2128] InstallationDate: Installed on 2018-03-06 (364 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: ASUSTeK Computer Inc. K93SM ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=dc7bbf0d-c12f-4b29-9787-54ac74c97c4e ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K93SM 204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K93SM dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10
[Touch-packages] [Bug 1813584] Update Released
The verification of the Stable Release Update for libidn has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813584 Title: libidn ftbfs in 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Released Status in libidn source package in Cosmic: Fix Released Bug description: [Impact] according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libidn ftbfs. It is important that packages in stable series are buildable at all times in case security updates need to be prepared. [Test Case] Make sure the package builds successfully. [Regression Potential] Should be relatively minimal. The same change was present in Ubuntu since cosmic, so we would already get mentions of regressions previously. [Original Description] = GNU Libidn 1.33: lib/gltests/test-suite.log = # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-lock === Starting test_lock ...FAIL test-lock (exit status: 134) SKIP: test-setlocale1.sh Skipping test: no locale for testing is installed SKIP test-setlocale1.sh (exit status: 77) FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) Testsuite summary for GNU Libidn 1.33 # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See lib/gltests/test-suite.log Please report to bug-lib...@gnu.org Makefile:2137: recipe for target 'test-suite.log' failed make[6]: *** [test-suite.log] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813584] Re: libidn ftbfs in 18.04 LTS
This bug was fixed in the package libidn - 1.33-2.1ubuntu1.1 --- libidn (1.33-2.1ubuntu1.1) bionic; urgency=medium * Backport change from cosmic to resolve the current FTBFS (LP: #1813584): - Do not set as-needed, to work-around a testsuite failure -- Łukasz 'sil2100' Zemczak Wed, 30 Jan 2019 14:07:10 +0100 ** Changed in: libidn (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813584 Title: libidn ftbfs in 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Released Status in libidn source package in Cosmic: Fix Released Bug description: [Impact] according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libidn ftbfs. It is important that packages in stable series are buildable at all times in case security updates need to be prepared. [Test Case] Make sure the package builds successfully. [Regression Potential] Should be relatively minimal. The same change was present in Ubuntu since cosmic, so we would already get mentions of regressions previously. [Original Description] = GNU Libidn 1.33: lib/gltests/test-suite.log = # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-lock === Starting test_lock ...FAIL test-lock (exit status: 134) SKIP: test-setlocale1.sh Skipping test: no locale for testing is installed SKIP test-setlocale1.sh (exit status: 77) FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) Testsuite summary for GNU Libidn 1.33 # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See lib/gltests/test-suite.log Please report to bug-lib...@gnu.org Makefile:2137: recipe for target 'test-suite.log' failed make[6]: *** [test-suite.log] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809909] Re: package apport 2.20.1-0ubuntu2.18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239.
There was a segfault w/ python2.7 and its not actually an issue with apport. From dmesg: [ 5506.922549] python2.7[5699]: segfault at 8e ip 004f4af3 sp 74e5c4d0 error 4 in python2.7[40+2de000] ** Package changed: apport (Ubuntu) => python2.7 (Ubuntu) -- 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/1809909 Title: package apport 2.20.1-0ubuntu2.18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239. Status in python2.7 package in Ubuntu: Confirmed Bug description: Happened while upgrading via apt. apport did not upgrade, gave a segmentation fault. Now, the OS (Ubuntu 16.04.5 LTS) does not even boot sometimes. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.18 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashReports: 640:0:116:406436:2018-12-27 20:44:57.411726236 +0530:2018-12-27 20:44:58.411726236 +0530:/var/crash/_usr_lib_xorg_Xorg.0.crash 600:0:116:454368:2018-12-26 23:50:15.102489948 +0530:2018-12-26 23:50:16.102489948 +0530:/var/crash/apport.0.crash Date: Wed Dec 26 23:50:15 2018 DuplicateSignature: package:apport:2.20.1-0ubuntu2.18 Installing new version of config file /etc/init/apport.conf ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2018-12-26 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1809909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776626] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-03-05 10:44 EDT--- IBM bugzilla status -> closed, Fix Released for all requested distros -- 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/1776626 Title: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part Status in Ubuntu on IBM z Systems: Fix Released Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: Won't Fix Status in systemd source package in Bionic: Fix Released Bug description: [Impact] * cryptsetup in bionic supports creating luks volumes with a non- standard sector-size option, and thus this option also needs to be used when activating the LUKS volumes. Add sector-size= option support to /etc/crypttab. [Test Case] * Create a plain LUKS volume with sector-size 4096 * Specify sector-size=4096 option in /etc/crypttab * reload systemd, start systemd-cryptsetup@.service for that volume * check the journal, to ensure that `sector-size` option was recognized and is active. (i.e. there is not error messages about unrecognized option `sector-size` from systemd-cryptsetup) [Regression Potential] * This is an optional argument, not used by default. Currently custom sector-size crypttab does not work correctly, and thus cannot regress. [Other Info] * Original bug report Support fast clear key dm-crypt with 4k support Extend /etc/crypttab to enable 4k sector support in plain mode The proposed enhancements are posted on github, see https://github.com/systemd/systemd/issues/8881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Changed in: ecj (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in activemq package in Ubuntu: New Status in afterburner.fx package in Ubuntu: New Status in annotation-indexer package in Ubuntu: New Status in apache-directory-server package in Ubuntu: New Status in aspectj package in Ubuntu: New Status in aspectj-maven-plugin package in Ubuntu: New Status in batik package in Ubuntu: New Status in bindex package in Ubuntu: New Status in bridge-method-injector package in Ubuntu: New Status in ca-certificates-java package in Ubuntu: New Status in carrotsearch-hppc package in Ubuntu: New Status in commons-httpclient package in Ubuntu: New Status in ecj package in Ubuntu: New Status in eclipselink package in Ubuntu: New Status in elki package in Ubuntu: New Status in figtree package in Ubuntu: New Status in fontawesomefx package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gkl package in Ubuntu: New Status in gluegen2 package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in hikaricp package in Ubuntu: New Status in hsqldb package in Ubuntu: New Status in hsqldb1.8.0 package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jackson-core package in Ubuntu: New Status in jackson-databind package in Ubuntu: New Status in jackson-dataformat-xml package in Ubuntu: New Status in jackson-module-jaxb-annotations package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javafxsvg package in Ubuntu: New Status in javamail package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jboss-classfilewriter package in Ubuntu: New Status in jboss-jdeparser2 package in Ubuntu: New Status in jboss-modules package in Ubuntu: New Status in jcommander package in Ubuntu: New Status in jersey1 package in Ubuntu: New Status in jftp package in Ubuntu: New Status in jmdns package in Ubuntu: New Status in jnr-posix package in Ubuntu: New Status in jruby package in Ubuntu: New Status in jruby-openssl package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jxgrabkey package in Ubuntu: New Status in jython package in Ubuntu: New Status in libapache-poi-java package in Ubuntu: New Status in libbtm-java package in Ubuntu: New Status in libcommons-collections3-java package in Ubuntu: New Status in libcommons-collections4-java package in Ubuntu: New Status in libcommons-compress-java package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in libjackson-json-java package in Ubuntu: New Status in libjavaewah-java package in Ubuntu: New Status in libjdo-api-java package in Ubuntu: New Status in libjdom1-java package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libnetx-java package in Ubuntu: New Status in libpdfbox2-java package in Ubuntu: New Status in libpicocontainer-java package in Ubuntu: New Status in libquartz-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in libsambox-java package in Ubuntu: New Status in libscram-java package in Ubuntu: New Status in libsejda-java package in Ubuntu: New Status in libspring-java package in Ubuntu: New Status in libswingx-java package in Ubuntu: New Status in libxml-security-java package in Ubuntu: New Status in libxstream-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in lucene-solr package in Ubuntu: New Status in mariadb-connector-java package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in mavibot package in Ubuntu: New Status in mckoisqldb package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in mockito package in Ubuntu: New Status in msv package in Ubuntu: New Status in obantoo package in Ubuntu: New
[Touch-packages] [Bug 1818691] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1818691 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 5 15:29:31 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-01-21 (43 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 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/openssh/+bug/1818691/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818688] [NEW] Impossible to use Ubuntu 18.04
Public bug reported: Ubuntu 18.04 starts in recovery mode only 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 i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 5 16:09:40 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [1043:1252] Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1043:1252] InstallationDate: Installed on 2010-12-15 (3001 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) MachineType: ASUSTeK Computer Inc. F7F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=62f67c93-44cb-40be-90fd-6dbc4a7d4f19 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F7F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 2.1 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr203:bd08/14/2007:svnASUSTeKComputerInc.:pnF7F:pvr1.0:rvnASUSTeKComputerInc.:rnF7F:rvr2.1:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: F7F dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Tue Mar 5 13:22:01 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1818688 Title: Impossible to use Ubuntu 18.04 Status in xorg package in Ubuntu: New Bug description: Ubuntu 18.04 starts in recovery mode only 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 i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 5 16:09:40 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [1043:1252] Subsystem: ASUSTeK Computer Inc. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1043:1252] InstallationDate: Installed on 2010-12-15 (3001 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) MachineType: ASUSTeK Computer Inc. F7F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=62f67c93-44cb-40be-90fd-6dbc4a7d4f19 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F7F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 2.1 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr203:bd08/14/2007:svnASUSTeKComputerInc.:pnF7F:pvr1.0:rvnASUSTeKComputerInc.:rnF7F:rvr2.1:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: F7F dmi.product.version:
[Touch-packages] [Bug 1818691] [NEW] package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 5 15:29:31 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-01-21 (43 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1818691 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 5 15:29:31 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-01-21 (43 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 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/openssh/+bug/1818691/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818340] Re: systemd-networkd core dumps in bionic-proposed
bug number typo in the last comment - i meant that the patches from bug 1812760 have been removed. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Released ** Changed in: systemd (Ubuntu Cosmic) Status: In Progress => Fix Released -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] during restart, systemd-networkd fails an assertion and aborts, leaving the system networking partially (if at all) configured. Further restarts continue to fail. [Test Case] Install a bionic system (cosmic affected also) with only systemd- networkd networking (i.e. uninstall or do not configure netplan). Ensure no networkd conf files are in /run/systemd/network. Stop networkd (sudo systemctl stop systemd-networkd). The interface to test with networkd (e.g. ens3) should have no address assigned and should be down. Create a file similar to below, adjusting for interface name: $ cat /etc/systemd/network/10-netplan-ens3.network [Match] Name=ens3 [Network] Address=192.168.122.68/24 Start networkd: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Stop networkd; ens3 should retain its address: ubuntu@lp1818340-b:~$ sudo systemctl stop systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Start networkd again; the bug is triggered: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd Job for systemd-networkd.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status systemd-networkd.service" and "journalctl -xe" for details. Alternately, instead of separately stopping and then starting networkd, the failure can be reproduced with just a restart. Note the failure only happens with statically-assigned addresses; interfaces configured with dhcp do not trigger this bug. [Regression Potential] TBD [Other Info] This was introduced by the SRU for bug 1812760; both the new behavior of networkd not removing managed addresses/routes from managed interfaces, as well as the assertion failure bug. This does not fail in disco; I believe additional commit(s) from upstream need to be backported. Original description: --- I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812760] Re: networkd: [Route] PreferredSource not working in *.network files
** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => In Progress ** Changed in: systemd (Ubuntu Cosmic) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1812760 Title: networkd: [Route] PreferredSource not working in *.network files Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Released Bug description: [Impact] Users cannot create IPv6 routes that specify PreferredSource. This means that users cannot specify a number of valid IPv6 routes that are useful in some circumstances. These routes can be created with the 'ip' tool, just not with systemd. This was reported upstream in systemd issue #5882 is fixed by pulling in the changes in systemd PR #11375 - https://github.com/systemd/systemd/pull/11375 [Test Case] Start a Bionic or Cosmic VM. Add the following netplan yaml (adjust for ethernet card and MAC): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:e2:c2:d7 set-name: ens3 addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"] routes: - to: "a::/16" via: "fd8f:1d7d:b141::1" from: "fd8f:1d7d:b141::2" - to: "fd8f:1d7d:b141::/64" scope: link from: "fd8f:1d7d:b141::2" metric: 255 Run netplan apply or reboot. Wait ~10s. Currently, ip -6 route will not include a route to "a::/16", and will not include the route to "fd8f:1d7d:b141::/64" that has "fd8f:1d7d:b141::2" as the source address - both those addresses will be missing. Correct behaviour is for ip -6 route to report the following: ubuntu@b-np:~$ ip -6 route a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 metric 1024 pref medium fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 pref medium fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium Check before and after upgrade that 'systemctl status network- online.target' shows that the target has been reached. [Regression Potential] This changes the state machine in systemd which configures the links. It passes systemd's internal tests, and has been approved by systemd maintainers, but it remains possible that the changes will break the configuration of obscure network setups. The backport requires pulling in two further commits that also change behaviour: currently systemd deletes all addresses and routes that were attached to an interface. With this change, it will only delete those that are not specified in the configuration files. A side effect of this is that restarting networkd will not cause remove/add netlink events to be emitted for these addresses, so if anyone is relying on this behavior this will break compatibility; but that is an unlikely thing to be relying on, and it seems worth this risk to reduce unnecessary network state changes. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1812760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716976] Re: DNS resolver mixes IPv6 and IPv4 caches
I'm currently on 18.10 and this bug seems to have been fixed. Abam, the bug you point to does not currently happen on my system, so maybe both have been fixed in 18.10. -- 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/1716976 Title: DNS resolver mixes IPv6 and IPv4 caches Status in systemd package in Ubuntu: Confirmed Bug description: In our network we have a DNS server that resolves some names to local addresses, while the same names are resolved to our public IP when public DNSs are used. For instance (using fictitious names and IPs), xyz.mydomain.com resolves to the public IP 65.254.242.180 when using an external DNS server, but resolves to 192.168.0.14 when using our internal DNS server (which all our computers are told to use via DHCP). This used to work fine until a somewhat recent update in Ubuntu 17.10. Now, xyz.domain.com almost always resolves to the public IP instead of the internal IP. Interestingly, restarting the systemd-resolved service fixes the problem for a while (from a few seconds to a few minutes). Right after restarting the service, the dig command reports the expected internal IP, but after a while it gets back to reporting the public IP. Forcing the dig command to query our DNS server instead of the local resolver returns the correct IP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu9 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 13:34:50 2017 InstallationDate: Installed on 2015-01-23 (963 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-06-15 (90 days ago) dmi.bios.date: 03/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN43WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.family: IDEAPAD dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818340] Re: systemd-networkd core dumps in bionic-proposed
With the patches from bug 1812670 reverted/removed, this should be now fixed in systemd at versions: bionic-proposed: https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.15 cosmic-proposed: https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.10 -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] during restart, systemd-networkd fails an assertion and aborts, leaving the system networking partially (if at all) configured. Further restarts continue to fail. [Test Case] Install a bionic system (cosmic affected also) with only systemd- networkd networking (i.e. uninstall or do not configure netplan). Ensure no networkd conf files are in /run/systemd/network. Stop networkd (sudo systemctl stop systemd-networkd). The interface to test with networkd (e.g. ens3) should have no address assigned and should be down. Create a file similar to below, adjusting for interface name: $ cat /etc/systemd/network/10-netplan-ens3.network [Match] Name=ens3 [Network] Address=192.168.122.68/24 Start networkd: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Stop networkd; ens3 should retain its address: ubuntu@lp1818340-b:~$ sudo systemctl stop systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Start networkd again; the bug is triggered: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd Job for systemd-networkd.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status systemd-networkd.service" and "journalctl -xe" for details. Alternately, instead of separately stopping and then starting networkd, the failure can be reproduced with just a restart. Note the failure only happens with statically-assigned addresses; interfaces configured with dhcp do not trigger this bug. [Regression Potential] TBD [Other Info] This was introduced by the SRU for bug 1812760; both the new behavior of networkd not removing managed addresses/routes from managed interfaces, as well as the assertion failure bug. This does not fail in disco; I believe additional commit(s) from upstream need to be backported. Original description: --- I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818340] Re: systemd-networkd core dumps in bionic-proposed
> I think the backport just needs to add a check to not flow through to setting > the > routes until after we've gone through the process of setting the addresses; we > can do that with the attached patch yeah, maybe, I was thinking more along the lines of needing c42ff3a1a7bfea66dc4655096c79bd481159091b and maybe e4a71bf36f422c3728b902aaa5846add7bbc0eb9, and we might also need 2428613f854f46b6624199c2dc58d02617320133 to actually initialize our flags to false. In short, the backport is much more complex than a quick patch; even if a 1-liner really is all that's needed, I need to look *very* closely at all 4 patches from bug 1812760 to make 100% that's the case. Hence, removing those patches from the current systemd upload, which will fix this bug. Then, I can take more time in the original bug to evaluate the patches. -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Released Bug description: [Impact] during restart, systemd-networkd fails an assertion and aborts, leaving the system networking partially (if at all) configured. Further restarts continue to fail. [Test Case] Install a bionic system (cosmic affected also) with only systemd- networkd networking (i.e. uninstall or do not configure netplan). Ensure no networkd conf files are in /run/systemd/network. Stop networkd (sudo systemctl stop systemd-networkd). The interface to test with networkd (e.g. ens3) should have no address assigned and should be down. Create a file similar to below, adjusting for interface name: $ cat /etc/systemd/network/10-netplan-ens3.network [Match] Name=ens3 [Network] Address=192.168.122.68/24 Start networkd: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Stop networkd; ens3 should retain its address: ubuntu@lp1818340-b:~$ sudo systemctl stop systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Start networkd again; the bug is triggered: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd Job for systemd-networkd.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status systemd-networkd.service" and "journalctl -xe" for details. Alternately, instead of separately stopping and then starting networkd, the failure can be reproduced with just a restart. Note the failure only happens with statically-assigned addresses; interfaces configured with dhcp do not trigger this bug. [Regression Potential] TBD [Other Info] This was introduced by the SRU for bug 1812760; both the new behavior of networkd not removing managed addresses/routes from managed interfaces, as well as the assertion failure bug. This does not fail in disco; I believe additional commit(s) from upstream need to be backported. Original description: --- I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted gluegen2 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gluegen2/2.3.2-7~18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gluegen2 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in activemq package in Ubuntu: New Status in afterburner.fx package in Ubuntu: New Status in annotation-indexer package in Ubuntu: New Status in apache-directory-server package in Ubuntu: New Status in aspectj package in Ubuntu: New Status in aspectj-maven-plugin package in Ubuntu: New Status in batik package in Ubuntu: New Status in bindex package in Ubuntu: New Status in bridge-method-injector package in Ubuntu: New Status in ca-certificates-java package in Ubuntu: New Status in carrotsearch-hppc package in Ubuntu: New Status in commons-httpclient package in Ubuntu: New Status in ecj package in Ubuntu: New Status in eclipselink package in Ubuntu: New Status in elki package in Ubuntu: New Status in figtree package in Ubuntu: New Status in fontawesomefx package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gkl package in Ubuntu: New Status in gluegen2 package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in hikaricp package in Ubuntu: New Status in hsqldb package in Ubuntu: New Status in hsqldb1.8.0 package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jackson-core package in Ubuntu: New Status in jackson-databind package in Ubuntu: New Status in jackson-dataformat-xml package in Ubuntu: New Status in jackson-module-jaxb-annotations package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javafxsvg package in Ubuntu: New Status in javamail package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jboss-classfilewriter package in Ubuntu: New Status in jboss-jdeparser2 package in Ubuntu: New Status in jboss-modules package in Ubuntu: New Status in jcommander package in Ubuntu: New Status in jersey1 package in Ubuntu: New Status in jftp package in Ubuntu: New Status in jmdns package in Ubuntu: New Status in jnr-posix package in Ubuntu: New Status in jruby package in Ubuntu: New Status in jruby-openssl package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jxgrabkey package in Ubuntu: New Status in jython package in Ubuntu: New Status in libapache-poi-java package in Ubuntu: New Status in libbtm-java package in Ubuntu: New Status in libcommons-collections3-java package in Ubuntu: New Status in libcommons-collections4-java package in Ubuntu: New Status in libcommons-compress-java package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in libjackson-json-java package in Ubuntu: New Status in libjavaewah-java package in Ubuntu: New Status in libjdo-api-java package in Ubuntu: New Status in libjdom1-java package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libnetx-java package in Ubuntu: New Status in libpdfbox2-java package in Ubuntu: New Status in
[Touch-packages] [Bug 1818666] Re: no network(with cable)
** Package changed: xorg (Ubuntu) => network-manager (Ubuntu) -- 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/1818666 Title: no network(with cable) Status in network-manager package in Ubuntu: New Bug description: Description: Trisquel GNU/Linux 8.0, Flidas Release: 8.0 --- network-manager: Installiert: 1.2.6-0ubuntu0.16.04.3 Installationskandidat: 1.2.6-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.6-0ubuntu0.16.04.3 500 500 https://archive.trisquel.info/trisquel flidas-security/main amd64 Packages 500 https://archive.trisquel.info/trisquel flidas-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 https://archive.trisquel.info/trisquel flidas/main amd64 Packages --- after starting the system there is no eth(0?) network available, after gdm-login it take some time, starting the network-managager leads to a freeze of the network-manager while rebooting the system it take a lot more time and there are also some error messages. i think they are included in the "Extra debug information". sorry i'm not sure, this is my first bug-report. a have this problem since i use trisquel, this problem doesnt exist with ubuntu, i think sometimes everything works fine. :) if this bug-report is not written correct, please contact me if possible. thanks ProblemType: Bug DistroRelease: Trisquel 8.0 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168+8.0trisquel2-generic 4.4.167-gnu Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 5 14:38:31 2019 InstallationDate: Installed on 2018-12-27 (68 days ago) InstallationMedia: Trisquel 8.0 "flidas" - Release amd64 (20180417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1818666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818679] [NEW] package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Public bug reported: I can't tell you anything. There was a error message without specific details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 5 06:48:59 2019 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2016-08-12 (935 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- 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/1818679 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in openssh package in Ubuntu: New Bug description: I can't tell you anything. There was a error message without specific details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Mar 5 06:48:59 2019 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2016-08-12 (935 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1818679/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Please test proposed package
Hello Eric, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.15 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Released Bug description: [Impact] Mounting manually a network share (NFS) and masking it breaks the state of other units (and their dependencies). Casper is masking a mounted NFS share, blocking the normal boot process as described in the original description, but the issue comes from systemd. [Test Case] - NFS mount point at /media root@iscsi-bionic:/home/ubuntu# mount | grep media 10.230.56.72:/tmp/mnt on /media type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72) - Test mount point (/test) defined in /etc/fstab: root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test tmpfs /test tmpfs nosuid,nodev 0 0 1. If media.mount is not masked, everything works fine: root@iscsi-bionic:/home/ubuntu# mount | grep test root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days ago root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago root@iscsi-bionic:/home/ubuntu# systemctl start test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test 2. If media.mount is masked, other mounts are failing: root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount Created symlink /etc/systemd/system/media.mount → /dev/null. root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test
[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
Hello Eric, or anyone else affected, Accepted systemd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-cosmic ** Tags added: verification-needed-cosmic ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- 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 systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Released Bug description: [Impact] Mounting manually a network share (NFS) and masking it breaks the state of other units (and their dependencies). Casper is masking a mounted NFS share, blocking the normal boot process as described in the original description, but the issue comes from systemd. [Test Case] - NFS mount point at /media root@iscsi-bionic:/home/ubuntu# mount | grep media 10.230.56.72:/tmp/mnt on /media type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72) - Test mount point (/test) defined in /etc/fstab: root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test tmpfs /test tmpfs nosuid,nodev 0 0 1. If media.mount is not masked, everything works fine: root@iscsi-bionic:/home/ubuntu# mount | grep test root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days ago root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago root@iscsi-bionic:/home/ubuntu# systemctl start test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test 2. If media.mount is masked, other mounts are failing: root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount Created symlink /etc/systemd/system/media.mount → /dev/null. root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime)
[Touch-packages] [Bug 1818666] [NEW] no network(with cable)
Public bug reported: Description:Trisquel GNU/Linux 8.0, Flidas Release:8.0 --- network-manager: Installiert: 1.2.6-0ubuntu0.16.04.3 Installationskandidat: 1.2.6-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.6-0ubuntu0.16.04.3 500 500 https://archive.trisquel.info/trisquel flidas-security/main amd64 Packages 500 https://archive.trisquel.info/trisquel flidas-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 https://archive.trisquel.info/trisquel flidas/main amd64 Packages --- after starting the system there is no eth(0?) network available, after gdm-login it take some time, starting the network-managager leads to a freeze of the network-manager while rebooting the system it take a lot more time and there are also some error messages. i think they are included in the "Extra debug information". sorry i'm not sure, this is my first bug-report. a have this problem since i use trisquel, this problem doesnt exist with ubuntu, i think sometimes everything works fine. :) if this bug-report is not written correct, please contact me if possible. thanks ProblemType: Bug DistroRelease: Trisquel 8.0 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168+8.0trisquel2-generic 4.4.167-gnu Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 5 14:38:31 2019 InstallationDate: Installed on 2018-12-27 (68 days ago) InstallationMedia: Trisquel 8.0 "flidas" - Release amd64 (20180417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug flidas -- 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/1818666 Title: no network(with cable) Status in xorg package in Ubuntu: New Bug description: Description: Trisquel GNU/Linux 8.0, Flidas Release: 8.0 --- network-manager: Installiert: 1.2.6-0ubuntu0.16.04.3 Installationskandidat: 1.2.6-0ubuntu0.16.04.3 Versionstabelle: *** 1.2.6-0ubuntu0.16.04.3 500 500 https://archive.trisquel.info/trisquel flidas-security/main amd64 Packages 500 https://archive.trisquel.info/trisquel flidas-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 https://archive.trisquel.info/trisquel flidas/main amd64 Packages --- after starting the system there is no eth(0?) network available, after gdm-login it take some time, starting the network-managager leads to a freeze of the network-manager while rebooting the system it take a lot more time and there are also some error messages. i think they are included in the "Extra debug information". sorry i'm not sure, this is my first bug-report. a have this problem since i use trisquel, this problem doesnt exist with ubuntu, i think sometimes everything works fine. :) if this bug-report is not written correct, please contact me if possible. thanks ProblemType: Bug DistroRelease: Trisquel 8.0 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168+8.0trisquel2-generic 4.4.167-gnu Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 5 14:38:31 2019 InstallationDate: Installed on 2018-12-27 (68 days ago) InstallationMedia: Trisquel 8.0 "flidas" - Release amd64 (20180417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1818666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
I will try it out on bionic in a few hours -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Status in xkeyboard-config source package in Disco: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818340] Re: systemd-networkd core dumps in bionic-proposed
OK, so with the magic of debug symbols and gdb on Cosmic:
(gdb) run
...
ens8: Gained IPv6LL
Assertion 'link->state == LINK_STATE_SETTING_ADDRESSES' failed at
../src/network/networkd-link.c:803, function link_enter_set_routes(). Aborting.
...
(gdb) up
#3 0x5566b194 in link_enter_set_routes (link=0x5571d050) at
../src/network/networkd-link.c:803
803 ../src/network/networkd-link.c: No such file or directory.
(gdb) p link->state
$3 = LINK_STATE_PENDING
Looking at the code, it seems we are hitting link_enter_set_routes()
before link_enter_set_addresses() which is where the state is set. We're
hitting link_enter_set_routes() because link_check_ready() now calls it
straight off the bat.
I think the backport just needs to add a check to not flow through to
setting the routes until after we've gone through the process of setting
the addresses; we can do that with the attached patch. (It applies to
the cosmic version, I haven't tested it against Bionic.)
Having said that Dan you've obviously had a closer look at the code and more
recently, what patches did you think were needed? It looks like perhaps you
could solve this by backporting c42ff3a1a7bf ("networkd: Track address
configuration")
and 289e6774d0da ("networkd: Use only a generic CONFIGURING state") - is that
what you had in mind?
** Patch added:
"0001-Do-not-call-link_enter_set_routes-until-LINK_STATE_S.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+attachment/5243670/+files/0001-Do-not-call-link_enter_set_routes-until-LINK_STATE_S.patch
--
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/1818340
Title:
systemd-networkd core dumps in bionic-proposed
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Cosmic:
In Progress
Status in systemd source package in Disco:
Fix Released
Bug description:
[Impact]
during restart, systemd-networkd fails an assertion and aborts,
leaving the system networking partially (if at all) configured.
Further restarts continue to fail.
[Test Case]
Install a bionic system (cosmic affected also) with only systemd-
networkd networking (i.e. uninstall or do not configure netplan).
Ensure no networkd conf files are in /run/systemd/network. Stop
networkd (sudo systemctl stop systemd-networkd). The interface to
test with networkd (e.g. ens3) should have no address assigned and
should be down.
Create a file similar to below, adjusting for interface name:
$ cat /etc/systemd/network/10-netplan-ens3.network
[Match]
Name=ens3
[Network]
Address=192.168.122.68/24
Start networkd:
ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd
ubuntu@lp1818340-b:~$ ip a show ens3
2: ens3: mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff
inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe6e:8c9f/64 scope link
valid_lft forever preferred_lft forever
Stop networkd; ens3 should retain its address:
ubuntu@lp1818340-b:~$ sudo systemctl stop systemd-networkd
ubuntu@lp1818340-b:~$ ip a show ens3
2: ens3: mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff
inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe6e:8c9f/64 scope link
valid_lft forever preferred_lft forever
Start networkd again; the bug is triggered:
ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd
Job for systemd-networkd.service failed because a fatal signal was delivered
causing the control process to dump core.
See "systemctl status systemd-networkd.service" and "journalctl -xe" for
details.
Alternately, instead of separately stopping and then starting
networkd, the failure can be reproduced with just a restart.
Note the failure only happens with statically-assigned addresses;
interfaces configured with dhcp do not trigger this bug.
[Regression Potential]
TBD
[Other Info]
This was introduced by the SRU for bug 1812760; both the new behavior
of networkd not removing managed addresses/routes from managed
interfaces, as well as the assertion failure bug. This does not fail
in disco; I believe additional commit(s) from upstream need to be
backported.
Original description:
---
I run a number of servers with -proposed enabled and have seen a bunch
of this today:
Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with
result 'core-dump'.
Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service.
These machines have numerous bonds,
[Touch-packages] [Bug 1770271] Re: VegaM support
bionic has 4.18 backport now, installed with 18.04.2 image or manually via 'linux-generic-hwe-18.04' ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1770271 Title: VegaM support Status in amd: New Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in mesa source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: VegaM is a new GPU. Please include support for VegaM in the next LTS (16.04.x and 18.04.x) and non-LTS releases. Kernel support starts here (32 patches): https://patchwork.freedesktop.org/patch/218839/ Mesa support: https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123 https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8 https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1770271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted scilab into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/scilab/6.0.1-7~18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: scilab (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in activemq package in Ubuntu: New Status in afterburner.fx package in Ubuntu: New Status in annotation-indexer package in Ubuntu: New Status in apache-directory-server package in Ubuntu: New Status in aspectj package in Ubuntu: New Status in aspectj-maven-plugin package in Ubuntu: New Status in batik package in Ubuntu: New Status in bindex package in Ubuntu: New Status in bridge-method-injector package in Ubuntu: New Status in ca-certificates-java package in Ubuntu: New Status in carrotsearch-hppc package in Ubuntu: New Status in commons-httpclient package in Ubuntu: New Status in ecj package in Ubuntu: New Status in eclipselink package in Ubuntu: New Status in elki package in Ubuntu: New Status in figtree package in Ubuntu: New Status in fontawesomefx package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gkl package in Ubuntu: New Status in gluegen2 package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in hikaricp package in Ubuntu: New Status in hsqldb package in Ubuntu: New Status in hsqldb1.8.0 package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jackson-core package in Ubuntu: New Status in jackson-databind package in Ubuntu: New Status in jackson-dataformat-xml package in Ubuntu: New Status in jackson-module-jaxb-annotations package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javafxsvg package in Ubuntu: New Status in javamail package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jboss-classfilewriter package in Ubuntu: New Status in jboss-jdeparser2 package in Ubuntu: New Status in jboss-modules package in Ubuntu: New Status in jcommander package in Ubuntu: New Status in jersey1 package in Ubuntu: New Status in jftp package in Ubuntu: New Status in jmdns package in Ubuntu: New Status in jnr-posix package in Ubuntu: New Status in jruby package in Ubuntu: New Status in jruby-openssl package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jxgrabkey package in Ubuntu: New Status in jython package in Ubuntu: New Status in libapache-poi-java package in Ubuntu: New Status in libbtm-java package in Ubuntu: New Status in libcommons-collections3-java package in Ubuntu: New Status in libcommons-collections4-java package in Ubuntu: New Status in libcommons-compress-java package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in libjackson-json-java package in Ubuntu: New Status in libjavaewah-java package in Ubuntu: New Status in libjdo-api-java package in Ubuntu: New Status in libjdom1-java package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libnetx-java package in Ubuntu: New Status in libpdfbox2-java package in Ubuntu: New Status in libpicocontainer-java
[Touch-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
reopened
** Changed in: network-manager (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1818340] Re: systemd-networkd core dumps in bionic-proposed
Just to let you know, I still see 237-3ubuntu10.14 in -proposed and I think that's the one that has the issue. Mark -- 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/1818340 Title: systemd-networkd core dumps in bionic-proposed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Released Bug description: [Impact] during restart, systemd-networkd fails an assertion and aborts, leaving the system networking partially (if at all) configured. Further restarts continue to fail. [Test Case] Install a bionic system (cosmic affected also) with only systemd- networkd networking (i.e. uninstall or do not configure netplan). Ensure no networkd conf files are in /run/systemd/network. Stop networkd (sudo systemctl stop systemd-networkd). The interface to test with networkd (e.g. ens3) should have no address assigned and should be down. Create a file similar to below, adjusting for interface name: $ cat /etc/systemd/network/10-netplan-ens3.network [Match] Name=ens3 [Network] Address=192.168.122.68/24 Start networkd: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Stop networkd; ens3 should retain its address: ubuntu@lp1818340-b:~$ sudo systemctl stop systemd-networkd ubuntu@lp1818340-b:~$ ip a show ens3 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6e:8c:9f brd ff:ff:ff:ff:ff:ff inet 192.168.122.68/24 brd 192.168.122.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6e:8c9f/64 scope link valid_lft forever preferred_lft forever Start networkd again; the bug is triggered: ubuntu@lp1818340-b:~$ sudo systemctl start systemd-networkd Job for systemd-networkd.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status systemd-networkd.service" and "journalctl -xe" for details. Alternately, instead of separately stopping and then starting networkd, the failure can be reproduced with just a restart. Note the failure only happens with statically-assigned addresses; interfaces configured with dhcp do not trigger this bug. [Regression Potential] TBD [Other Info] This was introduced by the SRU for bug 1812760; both the new behavior of networkd not removing managed addresses/routes from managed interfaces, as well as the assertion failure bug. This does not fail in disco; I believe additional commit(s) from upstream need to be backported. Original description: --- I run a number of servers with -proposed enabled and have seen a bunch of this today: Mar 02 16:20:58 4-ridge-fw1 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Mar 02 16:20:58 4-ridge-fw1 systemd[1]: Failed to start Network Service. These machines have numerous bonds, so I suspect that's a factor. So far I have only observed the issue on machines with -proposed enabled so I suspect it is a problem with systemd 237-3ubuntu10.14 Example netplan.yaml attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted libjavaewah-java into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /libjavaewah-java/0.7.9-1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libjavaewah-java (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in activemq package in Ubuntu: New Status in afterburner.fx package in Ubuntu: New Status in annotation-indexer package in Ubuntu: New Status in apache-directory-server package in Ubuntu: New Status in aspectj package in Ubuntu: New Status in aspectj-maven-plugin package in Ubuntu: New Status in batik package in Ubuntu: New Status in bindex package in Ubuntu: New Status in bridge-method-injector package in Ubuntu: New Status in ca-certificates-java package in Ubuntu: New Status in carrotsearch-hppc package in Ubuntu: New Status in commons-httpclient package in Ubuntu: New Status in ecj package in Ubuntu: New Status in eclipselink package in Ubuntu: New Status in elki package in Ubuntu: New Status in figtree package in Ubuntu: New Status in fontawesomefx package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gkl package in Ubuntu: New Status in gluegen2 package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in hikaricp package in Ubuntu: New Status in hsqldb package in Ubuntu: New Status in hsqldb1.8.0 package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jackson-core package in Ubuntu: New Status in jackson-databind package in Ubuntu: New Status in jackson-dataformat-xml package in Ubuntu: New Status in jackson-module-jaxb-annotations package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javafxsvg package in Ubuntu: New Status in javamail package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jboss-classfilewriter package in Ubuntu: New Status in jboss-jdeparser2 package in Ubuntu: New Status in jboss-modules package in Ubuntu: New Status in jcommander package in Ubuntu: New Status in jersey1 package in Ubuntu: New Status in jftp package in Ubuntu: New Status in jmdns package in Ubuntu: New Status in jnr-posix package in Ubuntu: New Status in jruby package in Ubuntu: New Status in jruby-openssl package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jxgrabkey package in Ubuntu: New Status in jython package in Ubuntu: New Status in libapache-poi-java package in Ubuntu: New Status in libbtm-java package in Ubuntu: New Status in libcommons-collections3-java package in Ubuntu: New Status in libcommons-collections4-java package in Ubuntu: New Status in libcommons-compress-java package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in libjackson-json-java package in Ubuntu: New Status in libjavaewah-java package in Ubuntu: New Status in libjdo-api-java package in Ubuntu: New Status in libjdom1-java package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libnetx-java package in Ubuntu: New Status in libpdfbox2-java package in Ubuntu:
[Touch-packages] [Bug 1716976] Re: DNS resolver mixes IPv6 and IPv4 caches
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1716976 Title: DNS resolver mixes IPv6 and IPv4 caches Status in systemd package in Ubuntu: Confirmed Bug description: In our network we have a DNS server that resolves some names to local addresses, while the same names are resolved to our public IP when public DNSs are used. For instance (using fictitious names and IPs), xyz.mydomain.com resolves to the public IP 65.254.242.180 when using an external DNS server, but resolves to 192.168.0.14 when using our internal DNS server (which all our computers are told to use via DHCP). This used to work fine until a somewhat recent update in Ubuntu 17.10. Now, xyz.domain.com almost always resolves to the public IP instead of the internal IP. Interestingly, restarting the systemd-resolved service fixes the problem for a while (from a few seconds to a few minutes). Right after restarting the service, the dig command reports the expected internal IP, but after a while it gets back to reporting the public IP. Forcing the dig command to query our DNS server instead of the local resolver returns the correct IP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu9 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 13:34:50 2017 InstallationDate: Installed on 2015-01-23 (963 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-06-15 (90 days ago) dmi.bios.date: 03/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN43WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.family: IDEAPAD dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792118] Re: systemd-resolved periodically fails to resolve names from corporate network
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1792118 Title: systemd-resolved periodically fails to resolve names from corporate network Status in systemd package in Ubuntu: Confirmed Bug description: I never experienced problems with corporate servers on 14.04 and 16.04, but with 18.04 I have to restart systemd-resolved a few times per day. What I see: Internet addresses are resolved, but corporate ones aren't. What I do to fix: sudo service systemd-resolved restart. After that corporate servers are resolved. It looks like some issue with DNS cache. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy systemd systemd: Installed: 237-3ubuntu10.3 Candidate: 237-3ubuntu10.3 Version table: *** 237-3ubuntu10.3 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1792118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716976] Re: DNS resolver mixes IPv6 and IPv4 caches
I have a the same kind of errors. DNS resolution sometimes fails due to cache issues. Is you bug similar to mine https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818527 ? -- 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/1716976 Title: DNS resolver mixes IPv6 and IPv4 caches Status in systemd package in Ubuntu: Confirmed Bug description: In our network we have a DNS server that resolves some names to local addresses, while the same names are resolved to our public IP when public DNSs are used. For instance (using fictitious names and IPs), xyz.mydomain.com resolves to the public IP 65.254.242.180 when using an external DNS server, but resolves to 192.168.0.14 when using our internal DNS server (which all our computers are told to use via DHCP). This used to work fine until a somewhat recent update in Ubuntu 17.10. Now, xyz.domain.com almost always resolves to the public IP instead of the internal IP. Interestingly, restarting the systemd-resolved service fixes the problem for a while (from a few seconds to a few minutes). Right after restarting the service, the dig command reports the expected internal IP, but after a while it gets back to reporting the public IP. Forcing the dig command to query our DNS server instead of the local resolver returns the correct IP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu9 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 13:34:50 2017 InstallationDate: Installed on 2015-01-23 (963 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-06-15 (90 days ago) dmi.bios.date: 03/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN43WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.family: IDEAPAD dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
bionic got the hwe update already ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in mesa source package in Bionic: Invalid Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in mesa source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Fix Committed Status in xorg-server-hwe-18.04 source package in Cosmic: Invalid Status in mesa source package in Disco: Invalid Status in xorg-server source package in Disco: Fix Released Status in xorg-server-hwe-18.04 source package in Disco: Invalid Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2:
[Touch-packages] [Bug 1811225] Re: Mesa 18.2.8 stable release
once all bugs have been verified -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1811225 Title: Mesa 18.2.8 stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Status in mesa source package in Cosmic: Fix Committed Bug description: [Impact] Ubuntu 18.10 shipped with mesa 18.2.2, and deserves to get the last point release of the series. This will also be backported to 18.04 as part of the HWE stack update. Upstream changes: 18.2.3 - Different patches for the DirectX9 and DRI state trackers. - Several fixes and workarounds for different games, inlcuding RAGE, Yakuza and The Evil Within, Wolfenstein The Old Blood ARMA 3, or No Mans Sky. - A bunch of fixes for different drivers, including r600, nouveau, radeonsi, anv, radv, virgl, i965, nvc0 or nv50. Worth to mention a fix for GPU hangs in Radeonsi. - State Trackers also get different fixes and corrections. - Finally, fixes for GLSL and NIR are also in this queue. 18.2.4 - Different fixes for different drivers: freedreno, radeonsi, swr, anv and radv. - Also there are fixes for ac, gallium, spirv and blorp. 18.2.5 - A patch for nine state tracker that fixes several crashes using nine's thread_submit feature. There are other patches to other state trackers. - A couple of patches for Meson build system, as well as for autotools. - In the drivers side, there are a couple of fixes for RADV, one regarding subgroups and another regarding conditional rendering. There are also fixes for virgl, r600, and i965. - Finally, the queue contains a couple of fixes for NIR, Wayland, and other components. 18.2.6 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.7 - Several patches fixing leaks in glsl, winsys and r600. - Improvements in the scripts that helps in preparing releases. - Added PCI IDs for Amber Lake and Whiskey Lake. - Fixes for radv, anv, i965 and vc4 drivers. - A couple of fixes in NIR backend. - Finally, several fixes in meson build system. 18.2.8 - Several fixes in Meson build system. - Also several fixes for st/nine subcomponent. - Patch for RADV driver that fixes a hang in Yakuza using DXVK. - There are also fixes for Virgl driver. - Added PCI IDs for VegaM, Vega20 and Vega10. [Test Case] Check on intel/radeon hw that things still work fine. [Regression potential] Mesa stable releases are tested by vendor CI systems, this is the last of the series so should be safe to update to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1811225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update
please test the new mesa on bionic/cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
oops, bionic did not get this yet ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in mesa source package in Bionic: Invalid Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in mesa source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Fix Committed Status in xorg-server-hwe-18.04 source package in Cosmic: Invalid Status in mesa source package in Disco: Invalid Status in xorg-server source package in Disco: Fix Released Status in xorg-server-hwe-18.04 source package in Disco: Invalid Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2:
[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
anyone willing to test it on bionic? ** Tags removed: verification-failed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Status in xkeyboard-config source package in Disco: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
