[Touch-packages] [Bug 1847183] Re: Intel video driver problem
*** This bug is a duplicate of bug 1829053 *** https://bugs.launchpad.net/bugs/1829053 ** This bug has been marked a duplicate of bug 1829053 driver won't install of intel -- 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/1847183 Title: Intel video driver problem Status in xorg package in Ubuntu: Invalid Bug description: New to Linux/UBUNTU but expert in Windows/programming. Evidently my Device/Display options are very limited, when I connect a projector the second display can use only a low resolution, much below the projectors capability. I tried to check for the video driver and I got error messages: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-23 Depends: xserver-xorg-core (>= 2:1.18.99.901) E: Unable to correct problems, you have held broken packages. # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Tue Oct 8 06:38:28 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:07a7] Subsystem: Dell GM108M [GeForce 930MX] [1028:07a7] InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=372b7ab4-d94d-4af9-993d-20170a3a8fa3 ro resume=UUID=5876659d-5846-4aa2-a490-f4fde866001e quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 00XT4W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/12/2018:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn00XT4W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1847183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847183] Re: Intel video driver problem
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. The message "E: Unable to correct problems, you have held broken packages." tells you prior commands have had errors that have not corrected, is support is appropriate. If it's a bug, it's related to the user/operator (who hoped it'd go away). You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community- support/709 For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: xorg (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/xorg/+question/684816 -- 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/1847183 Title: Intel video driver problem Status in xorg package in Ubuntu: Invalid Bug description: New to Linux/UBUNTU but expert in Windows/programming. Evidently my Device/Display options are very limited, when I connect a projector the second display can use only a low resolution, much below the projectors capability. I tried to check for the video driver and I got error messages: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-23 Depends: xserver-xorg-core (>= 2:1.18.99.901) E: Unable to correct problems, you have held broken packages. # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Tue Oct 8 06:38:28 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:07a7] Subsystem: Dell GM108M [GeForce 930MX] [1028:07a7] InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=372b7ab4-d94d-4af9-993d-20170a3a8fa3 ro resume=UUID=5876659d-5846-4aa2-a490-f4fde866001e quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 00XT4W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/12/2018:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn00XT4W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1847183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847183] [NEW] Intel video driver problem
Public bug reported: New to Linux/UBUNTU but expert in Windows/programming. Evidently my Device/Display options are very limited, when I connect a projector the second display can use only a low resolution, much below the projectors capability. I tried to check for the video driver and I got error messages: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-23 Depends: xserver-xorg-core (>= 2:1.18.99.901) E: Unable to correct problems, you have held broken packages. # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Tue Oct 8 06:38:28 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:07a7] Subsystem: Dell GM108M [GeForce 930MX] [1028:07a7] InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=372b7ab4-d94d-4af9-993d-20170a3a8fa3 ro resume=UUID=5876659d-5846-4aa2-a490-f4fde866001e quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 00XT4W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/12/2018:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn00XT4W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1847183 Title: Intel video driver problem Status in xorg package in Ubuntu: New Bug description: New to Linux/UBUNTU but expert in Windows/programming. Evidently my Device/Display options are very limited, when I connect a projector the second display can use only a low resolution, much below the projectors capability. I tried to check for the video driver and I got error messages: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-23 Depends: xserver-xorg-core (>= 2:1.18.99.901) E: Unable to correct problems, you have held broken packages. # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Tue Oct 8 06:38:28 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:07a7] Subsystem: Dell GM108M [GeForce 930MX] [1028:07a7] InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 1bcf:2b96
[Touch-packages] [Bug 1176548] Re: nut-server fails if modemmanager is scanning serial ports
[Expired for nut (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nut (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1176548 Title: nut-server fails if modemmanager is scanning serial ports Status in modemmanager package in Ubuntu: Expired Status in nut package in Ubuntu: Expired Bug description: Similar to whatPaavo Leinonen reported in 031601ce2a49$20b2efe0$6218cfa0$@leinonen.fi on the NUT mailing list. See also my mail in reply. Ubuntu runs modemmanager as a native upstart service. nut-server ends up running in parallel (on my system, probably a matter of timing). When modemmanager scans the serial ports for modems, upsd is unable to open the port configured for an UPS. (It might be possible to exclude some ports from the scan, I didn't check because I have no modem it could configure, I just kicked the package. Please convert nut-server to a native upstart service to be able to have it wait for modemmanager. (I hope upstart is clever enough to have a service wait for an optional package and let it proceed if not installed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1176548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1176548] Re: nut-server fails if modemmanager is scanning serial ports
[Expired for modemmanager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: modemmanager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1176548 Title: nut-server fails if modemmanager is scanning serial ports Status in modemmanager package in Ubuntu: Expired Status in nut package in Ubuntu: Expired Bug description: Similar to whatPaavo Leinonen reported in 031601ce2a49$20b2efe0$6218cfa0$@leinonen.fi on the NUT mailing list. See also my mail in reply. Ubuntu runs modemmanager as a native upstart service. nut-server ends up running in parallel (on my system, probably a matter of timing). When modemmanager scans the serial ports for modems, upsd is unable to open the port configured for an UPS. (It might be possible to exclude some ports from the scan, I didn't check because I have no modem it could configure, I just kicked the package. Please convert nut-server to a native upstart service to be able to have it wait for modemmanager. (I hope upstart is clever enough to have a service wait for an optional package and let it proceed if not installed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1176548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839446] Re: When trying to print a test page CUPS crashes
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839446 Title: When trying to print a test page CUPS crashes Status in cups package in Ubuntu: Expired Bug description: I'm trying to get my printer working correctly and when I try and print test pages it seems like cups crashes and restarts in the background. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 10:33:49 2019 InstallationDate: Installed on 2019-07-03 (35 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Samsung_C43x_Series_printer_: ipp://printer.local:631/ipp/print MachineType: LENOVO 20HN0016UK Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET57W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HN0016UK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HN0016UK dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845317] Re: Add new pci-id's for CML-S, ICL
the mesa part does what it says ** 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1845317 Title: Add new pci-id's for CML-S, ICL Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Bug description: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. There's also one ICL pci-id which was added recently (not in 5.3). [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: Expired Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: CTRL-EVENT-DISCONNECTED
[Touch-packages] [Bug 1847176] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1847176 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1847176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847176] Re: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
It appears the kernel can't find any speaker outputs: [ 38.211994] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC295: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 38.211997] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 38.212000] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 38.212001] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 38.212002] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 38.212004] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 [ 38.212006] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1847176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847176] [NEW] [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847176 Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: No Sound on laptop speaker after upgrading ubuntu 19.04 a few days ago. Soundcard is found in alsamixer but only "dummy" is available in gnome settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 20:18:10 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-25 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A9 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.sku: 1KT13UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838525] Re: LVM setup fails to install grub on virtio storage
Verifying the fix from the PPA: (k)rafaeldtinoco@keoan:~$ ls /dev/disk/by-id ls: cannot access '/dev/disk/by-id': No such file or directory (k)rafaeldtinoco@keoan:~$ sudo grub-mkdevicemap --no-floppy -m - (hd0) /dev/vda (hd1) /dev/vdb This is the expected behavior (by installer). (k)rafaeldtinoco@keoan:~$ sudo pvcreate /dev/vdb Physical volume "/dev/vdb" successfully created. (k)rafaeldtinoco@keoan:~$ sudo vgcreate vgubuntu /dev/vdb Volume group "vgubuntu" successfully created (k)rafaeldtinoco@keoan:~$ sudo lvcreate -l100%VG -n lvubuntu vgubuntu Logical volume "lvubuntu" created. (k)rafaeldtinoco@keoan:~$ sudo grub-mkdevicemap --no-floppy -m - (hd0) /dev/disk/by-id/lvm-pv-uuid-tdcf0A-qcPJ-1A1H-Oh2G-I1vE-GQPx-tjjeva (hd1) /dev/vda After installing the fix: (k)rafaeldtinoco@keoan:~$ ls -1 /dev/disk/by-id dm-name-vgubuntu-lvubuntu dm-uuid-LVM-btjm85kImnUtxMqC6ObQmM64kO1Bop7Gv7v1qbZIaKsBfOB0uyFfC3cG37LaB3KN lvm-pv-uuid-tdcf0A-qcPJ-1A1H-Oh2G-I1vE-GQPx-tjjeva (k)rafaeldtinoco@keoan:~$ sudo grub-mkdevicemap --no-floppy -m - (hd0) /dev/vda (hd1) /dev/vdb Back to same behavior! ** Description changed: [Impact] * Any Eoan installation that depends on latest installer will face this issue when final user chooses LVM full disk partitioning type. * Grub won't be able to install due to bad bootdevice variable in the installer. It will try to install grub to "/dev/mapper" and will fail. The default boot option will also be "/dev/mapper". [Test Case] * Download netboot files from current installer (vmlinuz and initrd files). * Create a KVM guest running from these files, with a NIC connected to the internet. * Initiate a network installation inside the KVM guest, choosing the Entire Disk - LVM partitioning option. * Wait installation to finish and to start the grub-install phase. It will ask where to install grub, having, as default, "/dev/mapper". By default, it might simply try to grub-install /dev/mapper, which will also fail. * That happens because /dev/disk/by-id/ has an unexpected (by the installer) symlink added by lvm2 package that grub-installer (used by debian-installer) does not expect (when using grub-mkdevice command). [Simplified Test Case] - * To add a PV + VG + LVM in a KVM guest to an empty virtio disk, for + * To add a PV + VG + LVM in a KVM guest to an empty virtio disk, for example, and to check if the command: - grub-mkdevice --no-floppy -m - + grub-mkdevicemap --no-floppy -m - lists /dev/vdX1 in front of /dev/vdX. This will be a sign that: /dev/disk/by-id/*lvm* file exists and will be enough to confuse installer. [Regression Potential] There are 3 alternatives to fix this and I have chosen the one I believe has the smaller potential for any type of regression. Comment #30 describes what caused the regression and these 3 alternatives: (1) To revert this change for current release, since this rule was added to "make navigation a bit easier using PV UUIDs", as the commit says. We would worry about installer changes in the next release. (2) Another possibility would be to change the logic inside "grub- mkdevicemap.c: make_device_map()->grub_util_iterate_devices()" to ignore all symlinks from /dev/disk/by-id/ containing lvm-pv-uuid-*. We would not have to worry about this in the next release if using debian- installer. (3) Another option would be to change grub-installer package/logic. Unfortunately, a few days before the full freeze, I don't think messing with the installer would be a good option to avoid regressions (potential regression item would grow in significance). => I'm choosing (2) because ubuntu foundations already faced a similar situation, when grub-mkdevicemap.c file was removed from grub2 code and they re-added it by using a quilt patch, assuming it was the easiest and better to maintain. I'm doing something similar, patching the patch that creates grub-mkdevicemap.c file again to ignore /dev/disk/by-id/lvm-pv- uuid-* files (like it already does for other symlinks, actually). [Other Info] Comment #26 has the TL;DR version of the problem. https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/comments/26 [Original Description] The Eoan debian-installer ISO fails to install GRUB on LVM installs with virtio storage, as it runs grub-install with /dev/mapper as a target (a directory), even if instructed to target a device. The following steps to reproduce have been prepared running the 20190730 build, but this has been broken since about June 18, 2019. Steps to reproduce: $ md5sum eoan-server-amd64.iso f591e30485e5f0b5117f6c116e538c42 eoan-server-amd64.iso $ qemu-img create -f raw disk1.img 8G Formatting 'disk1.img', fmt=raw size=8589934592 $ kvm -m 1024 -boot d -cdrom eoan-server-amd64.iso -drive file=disk1.img,if=virtio Proceed
[Touch-packages] [Bug 1838525] Re: LVM setup fails to install grub on virtio storage
Merge request was done here: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/grub2/+git/grub2/+merge/373792 And the following PPA is available: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1838525 ** Description changed: + [Impact] + + * Any Eoan installation that depends on latest installer will face this + issue when final user chooses LVM full disk partitioning type. + + * Grub won't be able to install due to bad bootdevice variable in the + installer. It will try to install grub to "/dev/mapper" and will fail. + The default boot option will also be "/dev/mapper". + + [Test Case] + + * Download netboot files from current installer (vmlinuz and initrd + files). + + * Create a KVM guest running from these files, with a NIC connected to + the internet. + + * Initiate a network installation inside the KVM guest, choosing the + Entire Disk - LVM partitioning option. + + * Wait installation to finish and to start the grub-install phase. It + will ask where to install grub, having, as default, "/dev/mapper". By + default, it might simply try to grub-install /dev/mapper, which will + also fail. + + * That happens because /dev/disk/by-id/ has an unexpected (by the + installer) symlink added by lvm2 package that grub-installer (used by + debian-installer) does not expect (when using grub-mkdevice command). + + [Regression Potential] + + There are 3 alternatives to fix this and I have chosen the one I believe + has the smaller potential for any type of regression. Comment #30 + describes what caused the regression and these 3 alternatives: + + (1) To revert this change for current release, since this rule was added + to "make navigation a bit easier using PV UUIDs", as the commit says. We + would worry about installer changes in the next release. + + (2) Another possibility would be to change the logic inside "grub- + mkdevicemap.c: make_device_map()->grub_util_iterate_devices()" to ignore + all symlinks from /dev/disk/by-id/ containing lvm-pv-uuid-*. We would + not have to worry about this in the next release if using debian- + installer. + + (3) Another option would be to change grub-installer package/logic. + Unfortunately, a few days before the full freeze, I don't think messing + with the installer would be a good option to avoid regressions + (potential regression item would grow in significance). + + => I'm choosing (2) because ubuntu foundations already faced a similar + situation, when grub-mkdevicemap.c file was removed from grub2 code and + they re-added it by using a quilt patch, assuming it was the easiest and + better to maintain. I'm doing something similar, patching the patch that + creates grub-mkdevicemap.c file again to ignore /dev/disk/by-id/lvm-pv- + uuid-* files (like it already does for other symlinks, actually). + + [Other Info] + Comment #26 has the TL;DR version of the problem. https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/comments/26 [Original Description] The Eoan debian-installer ISO fails to install GRUB on LVM installs with virtio storage, as it runs grub-install with /dev/mapper as a target (a directory), even if instructed to target a device. The following steps to reproduce have been prepared running the 20190730 build, but this has been broken since about June 18, 2019. Steps to reproduce: $ md5sum eoan-server-amd64.iso f591e30485e5f0b5117f6c116e538c42 eoan-server-amd64.iso $ qemu-img create -f raw disk1.img 8G Formatting 'disk1.img', fmt=raw size=8589934592 $ kvm -m 1024 -boot d -cdrom eoan-server-amd64.iso -drive file=disk1.img,if=virtio Proceed with all the defaults. In the "Partition disk" step select "Guided - use entire disk and set up LVM". Go ahead accepting the defaults. At the "Install the GRUB boot loader" step select "/dev/vda" as the target device. The installer will actually run `grub-install --force /dev/mapper` and fail after a while. The wrong command is visible both in the d-i screen and by running `ps` on a different console. Full installer syslog: http://paste.ubuntu.com/p/qtZy86dTp6/ It's interesting how this doesn't happen when not using virtio. If from the commands above the "if=virtio" option is dropped then everything works as expected. In this case the target block device is called /dev/sda instead of /dev/vda. ** Description changed: [Impact] - * Any Eoan installation that depends on latest installer will face this + * Any Eoan installation that depends on latest installer will face this issue when final user chooses LVM full disk partitioning type. - * Grub won't be able to install due to bad bootdevice variable in the + * Grub won't be able to install due to bad bootdevice variable in the installer. It will try to install grub to "/dev/mapper" and will fail. The default boot option will also be "/dev/mapper". [Test Case] - * Download netboot files from current installer
[Touch-packages] [Bug 1838525] Re: LVM setup fails to install grub on virtio storage
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/grub2/+git/grub2/+merge/373792 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1838525 Title: LVM setup fails to install grub on virtio storage Status in debian-installer package in Ubuntu: In Progress Status in grub2 package in Ubuntu: In Progress Status in lvm2 package in Ubuntu: In Progress Status in debian-installer package in Debian: New Bug description: Comment #26 has the TL;DR version of the problem. https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/comments/26 [Original Description] The Eoan debian-installer ISO fails to install GRUB on LVM installs with virtio storage, as it runs grub-install with /dev/mapper as a target (a directory), even if instructed to target a device. The following steps to reproduce have been prepared running the 20190730 build, but this has been broken since about June 18, 2019. Steps to reproduce: $ md5sum eoan-server-amd64.iso f591e30485e5f0b5117f6c116e538c42 eoan-server-amd64.iso $ qemu-img create -f raw disk1.img 8G Formatting 'disk1.img', fmt=raw size=8589934592 $ kvm -m 1024 -boot d -cdrom eoan-server-amd64.iso -drive file=disk1.img,if=virtio Proceed with all the defaults. In the "Partition disk" step select "Guided - use entire disk and set up LVM". Go ahead accepting the defaults. At the "Install the GRUB boot loader" step select "/dev/vda" as the target device. The installer will actually run `grub-install --force /dev/mapper` and fail after a while. The wrong command is visible both in the d-i screen and by running `ps` on a different console. Full installer syslog: http://paste.ubuntu.com/p/qtZy86dTp6/ It's interesting how this doesn't happen when not using virtio. If from the commands above the "if=virtio" option is dropped then everything works as expected. In this case the target block device is called /dev/sda instead of /dev/vda. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844775] Re: HDR support for Ubuntu 20.04
Hi Timo and Daniel (@vanvugt), Any plan for enabling HDR in part of X.org? Thanks! Gary -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1844775 Title: HDR support for Ubuntu 20.04 Status in ffmpeg package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in weston package in Ubuntu: Confirmed Bug description: This is a tracker bug for getting HDR support integrated in Ubuntu. Kernel i915: - 5.3 (Ice Lake) - plus at least https://patchwork.freedesktop.org/series/65656/ - gen4+ needs https://patchwork.freedesktop.org/series/63373/ - so anything beyond initial Ice Lake support will not be in 5.4 Mesa - needs current git master plus https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942 Mutter: https://gitlab.gnome.org/GNOME/mutter/merge_requests/804 Weston: https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847077] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => 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/1847077 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: oct 07 06:10:22 linux systemd[14697]: Listening on D-Bus User Message Bus Socket oct 07 06:10:22 linux systemd[14697]: Reached target Sockets. oct 07 06:10:22 linux systemd[14697]: Reached target Basic System. oct 07 06:10:22 linux systemd[14697]: Reached target Default. oct 07 06:10:22 linux systemd[14697]: Startup finished in 52ms. oct 07 06:10:22 linux systemd[1]: Started User Manager for UID 121. oct 07 06:10:22 linux systemd[14697]: Started D-Bus User Message Bus. oct 07 06:10:22 linux dbus-daemon[14711]: [session uid=121 pid=14711] AppArmor D oct 07 06:10:22 linux gnome-shell[14719]: Failed to apply DRM plane transform 0: oct 07 06:10:22 linux gnome-shell[14719]: WL: error in client communication (pid oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: (EE) oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: Fatal server error: oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: (EE) wl_drm@4: error 0: au oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: (EE) oct 07 06:10:22 linux gnome-shell[14719]: X Wayland crashed; exiting oct 07 06:10:22 linux gnome-session[14713]: gnome-session-binary[14713]: WARNING oct 07 06:10:22 linux gnome-session-binary[14713]: WARNING: App 'org.gnome.Shell oct 07 06:10:22 linux gnome-session-binary[14713]: Unrecoverable failure in requ oct 07 06:10:22 linux gdm-launch-environment][14693]: pam_unix(gdm-launch-enviro oct 07 06:10:22 linux gdm3[1178]: GdmDisplay: display lasted 0,643077 seconds oct 07 06:10:22 linux gdm3[1178]: Child process -14709 was already dead. oct 07 06:10:22 linux gdm3[1178]: Child process 14693 was already dead. oct 07 06:10:22 linux gdm3[1178]: Unable to kill session worker process oct 07 06:10:23 linux gdm-launch-environment][14732]: pam_unix(gdm-launch-enviro oct 07 06:10:23 linux systemd-logind[738]: New session c503 of user gdm. oct 07 06:10:23 linux systemd[1]: Started Session c503 of user gdm. oct 07 06:10:23 linux systemd-logind[738]: Removed session c502. oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: (--) Log file renamed oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: X.Org X Server 1.20.4 oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: X Protocol Version 11, oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Build Operating System oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Current Operating Syst oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Kernel command line: B oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Build Date: 02 May 201 oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: xorg-server-hwe-18.04 oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Current version of pix oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Before reporti oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: to make sure t oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Markers: (--) probed, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 06:30:25 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.0.0-27-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom,
[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan
Probably fixed in 2.0.7 which fixed a parallel make issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]
Launchpad has imported 1 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1759285. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-10-07T18:32:51+00:00 ali.sherif10 wrote: Description of problem: After installing Fedora 30, I found that vertical sensitivity is much higher than horizontal sensitivity. Version-Release number: 1.14.1. How reproducible: Always, because I got it in Kubuntu 19.04 too. Steps to Reproduce: 1. Install Fedora 30. Actual results: Vertical sensitivity is higher than horizontal sensitivity and moving the cursor horizontally is slow. Expected results: Vertical and horizontal touchpad speeds are proper. Additional info: Laptop: HP Pavilion g6. I didn't have the problem in previous versions of distributions. I don't know exactly when it started. Reply at: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1825499/comments/25 ** Changed in: libinput (Fedora) Status: Unknown => Confirmed ** Changed in: libinput (Fedora) Importance: Unknown => Undecided -- 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/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] Status in systemd: Fix Released Status in libinput package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Status in libinput package in Fedora: Confirmed Bug description: After installing Kubuntu 19.04, I found that vertical sensitivity is much higher than horizontal sensitivity. Installing xserver-xorg-input-synaptics improved the situation a bit and enabled KDE touchpad setting that were disabled. It's very annoying. Laptop: HP Pavilion g6. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Apr 19 12:00:02 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1825499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan
The root failure is: objcopy -O binary usr/klibc/syscalls/typesize.o usr/klibc/syscalls/typesize.bin mkdir -p usr/include/klibc/; perl /tmp/klibc-2.0.6/usr/klibc/syscalls.pl -2 usr/klibc/syscalls/SYSCALLS.i /tmp/klibc-2.0.6/usr/klibc/arch/x86_64/sysstub.ph x86_64 64 usr/klibc/syscalls/syscalls.nrs usr/klibc/syscalls usr/include/klibc/havesyscall.h usr/klibc/syscalls/typesize.bin > usr/klibc/syscalls/syscalls.mk || ( rm -f usr/klibc/syscalls/syscalls.mk ; exit 1 ) [...] /tmp/klibc-2.0.6/usr/klibc/syscalls.pl: usr/klibc/syscalls/typesize.bin: magic number not found -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Confirmed Status in klibc source package in Eoan: Confirmed Bug description: https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan- amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847152] [NEW] printf escape sentences are insufficiently documented
Public bug reported: The info page for ‘printf’ is misleading because the C ‘printf’ function does not interpret any escape sequences. So, interpreting this specification literally, all escape sequences are differences but not all of them are listed below. In particular, the sequence ‘\e’ is not listed. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 8.30-1ubuntu1 3) What you expected to happen ‘printf’ prints the FORMAT string, interpreting ‘\’ escapes as specified below and interpreting ‘%’ directives to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. 4) What happened instead ‘printf’ prints the FORMAT string, interpreting ‘%’ directives and ‘\’ escapes to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: coreutils 8.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 23:24:39 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1847152 Title: printf escape sentences are insufficiently documented Status in coreutils package in Ubuntu: New Bug description: The info page for ‘printf’ is misleading because the C ‘printf’ function does not interpret any escape sequences. So, interpreting this specification literally, all escape sequences are differences but not all of them are listed below. In particular, the sequence ‘\e’ is not listed. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 8.30-1ubuntu1 3) What you expected to happen ‘printf’ prints the FORMAT string, interpreting ‘\’ escapes as specified below and interpreting ‘%’ directives to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. 4) What happened instead ‘printf’ prints the FORMAT string, interpreting ‘%’ directives and ‘\’ escapes to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: coreutils 8.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 23:24:39 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1847152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes
** Tags added: ddstreet systemd ** Tags added: bionic disco -- 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/1796501 Title: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: In Progress Bug description: I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the following steps: 1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size. 2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit. 3. Ask upstream for SOA of test.asdf. with EDNS0. 4. Ask upstream for SOA of test.asdf. without EDNS0. 5. Repeat 1-4 for DS of test.asdf. 6. Repeat 1-5 for asdf. 7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size. 8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size. The upstream returns an unfragmented NXDOMAIN response for steps 1-6, an unfragmented NOERROR response for step 7 and a fragmented NOERROR response for step 8 which is the correct behaviour. DNSSEC records are included in the response if the DO-bit in the request was set. systemd-resolved should take the response from step 1 and start with validation instead of starting useless retries with reduced feture set. Step 3 and 4 are completely useless and probably lead to the SERVFAIL because I have configured it with DNSSEC=yes to prevent downgrade attacks. This regression seems to be caused by the patch resolved-Mitigate- DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic should only be executed if it is configured as DNSSEC=allow-downgrade or DNSSEC=no. See also https://github.com/systemd/systemd/pull/8608#issuecomment-396927885. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110]
This driver (along with necessary alsa ucm files) as now included with 5.3.x is working on my system (vanilla 5.3.4). I'd recommend closing this bug as FIXED. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838525] Re: LVM setup fails to install grub on virtio storage
The following commit:
commit 417e52c13a8156b11c25c411d44bda8b32bf87e4
Author: Peter Rajnoha
Date: Tue Feb 18 07:27:21 2014
udev: create /dev/disk/by-id/lvm-pv-uuid- symlink for a PV
We already have /dev/disk/by-id/dm-uuid-... (which encompasses the
VG UUID and LV UUID in case of LVs since the mapping's UUID is
VG+LV UUID together) and /dev/disk/by-id/dm-name-... (which encompasses
the VG and LV name in case of LVs).
This patch addds /dev/disk/by-id/lvm-pv-uuid- that completes
this scheme and makes navigation a bit easier using PV UUIDs since
one can navigate using PV UUIDs only and there's no need to do extra
PV UUID <--> kernel name matching (the PV UUID is stable across reboots).
This may come in handy in various scripts.
Since we already have the PV UUID stored in udev database (as a result
of blkid call - returned in ID_FS_UUID blkid's variable), this operation
is very cheap indeed, just creating the extra one symlink.
diff --git a/WHATS_NEW b/WHATS_NEW
index 39e8b886a..5bb37d8ad 100644
--- a/WHATS_NEW
+++ b/WHATS_NEW
@@ -1,5 +1,6 @@
Version 2.02.106 -
+ Create /dev/disk/by-id/lvm-pv-uuid- symlink for each PV via udev.
lvcreate computes RAID4/5/6 stripes if not given from # of allocatable PVs.
Fix merging of old snapshot into thin volume origin.
Use --ignoreskippedcluster in lvm2-monitor initscript/systemd unit.
diff --git a/udev/69-dm-lvm-metad.rules.in b/udev/69-dm-lvm-metad.rules.in
index e8304b5e0..bd75fc8ef 100644
--- a/udev/69-dm-lvm-metad.rules.in
+++ b/udev/69-dm-lvm-metad.rules.in
@@ -34,6 +34,9 @@ ENV{DM_MULTIPATH_DEVICE_PATH}=="1", GOTO="lvm_end"
# Inform lvmetad about any PV that is gone.
ACTION=="remove", GOTO="lvm_scan"
+# Create /dev/disk/by-id/lvm-pv-uuid- symlink for each PV
+ENV{ID_FS_UUID_ENC}=="?*",
SYMLINK+="disk/by-id/lvm-pv-uuid-$env{ID_FS_UUID_ENC}"
+
# If the PV is a special device listed below, scan only if the device is
# properly activated. These devices are not usable after an ADD event,
# but they require an extra setup and they are ready after a CHANGE event.
was the one responsible to add the change that causes:
/dev/disk/by-id/ to be populated with the LVM volume (not the entire
disk), breaking the current installer logic. There are 2 alternatives
here:
To revert this change for current release, since this rule was
added to "make navigation a bit easier using PV UUIDs", as the commit
says. We would worry about installer changes in the next release.
Another possibility would be to change the logic inside
"grub-mkdevicemap.c: make_device_map()->grub_util_iterate_devices()" to ignore
all symlinks from /dev/disk/by-id/ containing lvm-pv-uuid-*. We would not have
to worry about this in the next release if using debian-installer. I'm choosing
this option because ubuntu foundations already faced a similar situation, when
grub-mkdevicemap.c file was removed from grub2 code and they re-added it by
using a quilt patch, assuming it was the easiest and better to maintain. I'm
doing something similar, patching the patch that creates grub-mkdevicemap.c
file again.
Another option would be to change grub-installer package/logic.
Unfortunately, a few days before the full freeze, I don't think messing with
the instaler would be a good option to avoid regressions (potential regression
item would grow in significance).
So I'm going with (2) and providing a MR for Eoan to be reviewed in a
few moments.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1838525
Title:
LVM setup fails to install grub on virtio storage
Status in debian-installer package in Ubuntu:
In Progress
Status in grub2 package in Ubuntu:
In Progress
Status in lvm2 package in Ubuntu:
In Progress
Status in debian-installer package in Debian:
New
Bug description:
Comment #26 has the TL;DR version of the problem.
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/comments/26
[Original Description]
The Eoan debian-installer ISO fails to install GRUB on LVM installs
with virtio storage, as it runs grub-install with /dev/mapper as a
target (a directory), even if instructed to target a device.
The following steps to reproduce have been prepared running the
20190730 build, but this has been broken since about June 18, 2019.
Steps to reproduce:
$ md5sum eoan-server-amd64.iso
f591e30485e5f0b5117f6c116e538c42 eoan-server-amd64.iso
$ qemu-img create -f raw disk1.img 8G
Formatting 'disk1.img', fmt=raw size=8589934592
$ kvm -m 1024 -boot d -cdrom eoan-server-amd64.iso -drive
file=disk1.img,if=virtio
Proceed with all the defaults. In the "Partition disk" step select
"Guided - use entire disk and set up LVM". Go ahead accepting the
defaults. At the "Install the GRUB boot
[Touch-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]
** Bug watch added: Red Hat Bugzilla #1759285 https://bugzilla.redhat.com/show_bug.cgi?id=1759285 ** Also affects: libinput (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1759285 Importance: Unknown Status: Unknown -- 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/1825499 Title: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6] Status in systemd: Fix Released Status in libinput package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Status in libinput package in Fedora: Unknown Bug description: After installing Kubuntu 19.04, I found that vertical sensitivity is much higher than horizontal sensitivity. Installing xserver-xorg-input-synaptics improved the situation a bit and enabled KDE touchpad setting that were disabled. It's very annoying. Laptop: HP Pavilion g6. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Apr 19 12:00:02 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183E dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D4Z91EA#ABV dmi.product.version: 088512005D160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1825499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843007] Re: namespace: make MountFlags=shared work again
@harri-afaics I tried the test service from the upstream bug, but I couldn't reproduce the problem - please let me know if you are able to repro and what steps and/or config file you use to repro this on Bionic. ** Tags removed: ddstreet -- 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/1843007 Title: namespace: make MountFlags=shared work again Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Incomplete Bug description: Systemd in Bionic fails to handle MountFlags correctly. Would you mind to include https://github.com/systemd/systemd/commit/37ed15d7edaf59a1fc7c9e3552cd93a83f3814ef into Bionic? This bug seriously affects Docker > 18.6, see the Docker release notes for 18.09.1 (https://docs.docker.com/engine/release- notes/#18091). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1843007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845652] Re: rsync sends everything, not just changes
I frequently rebuild USB keys. If memory serves me correctly, the USB device was LUKS encrypted ext4. ** Changed in: rsync (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1845652 Title: rsync sends everything, not just changes Status in rsync package in Ubuntu: New Bug description: Repeated runs of rsync from PC to USB key send everything, not just the changes. This is reproducible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: rsync 3.1.3-6 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 09:18:19 2019 InstallationDate: Installed on 2019-06-10 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1845652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option
This bug was fixed in the package ubiquity - 19.10.15 --- ubiquity (19.10.15) eoan; urgency=medium [ Jean-Baptiste Lallement ] * debian/rules: grub-installer doesn't exist on some archs. Do not patch it in this cases. [ Iain Lane ] * Run debconf-updatepo to re-generate translation template -- Iain Lane Mon, 07 Oct 2019 14:40:28 +0100 ** Changed in: ubiquity (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1843768 Title: [FFe] Ubiquity with zfs install option Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-budgie-meta package in Ubuntu: Fix Released Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: Fix Released Bug description: Part of the 19.10 feature announcement is zfs experimental support in the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on- ubuntu-19-10-an-introduction). We modified ubiquity to present an “EXPERIMENTAL” (with warning) ZSYS install option. This option is only visible is zfsutils-linux is installed on the system. So, it won't be available for derivatives that use ubiquity but do not seed zfsutils- linux. Update as of 20/09/2019: the plan is to not seed zsys (security review will take a while), but to only seed zfsutils-linux. People can then opt-in to zsys which should be available by default next cycle. This option takes an entire disk and have a fix set of dataset installed. There is no support but we need this to make an official install option for the next LTS. The patch has been created to be as minimal as possible. Partman does a full disk partitioning, and then the script zsys-setup the first non-ESP partition and replaces with zfs pools. 4 partitions are created: 1. if GPT partitioning: ESP partition. This one is done by partman directly. 2. bpool (for boot), pool with older zfs compatible version to be readable by grub) 3. rpool (for / and userdataset) 4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on moved to the ESP) Additionaly if a swap file has been created by ubiquity, it is recreated as a ZFS volume. If the script fails to execute, the final installation is an ext4 installation on entire disk. Note that the implementation is slightly different from the specification due to a difficult cohabitation with partman in the custom partitioning page. Please find attached the MP on ubiquity as well as the package build log. https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan- amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1843768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845652] Re: rsync sends everything, not just changes
What's the filesystem on the target? If the target is vfat, for example, setting ownership and permissions won't work, and -W tells rsync to transfer the whole file. ** Changed in: rsync (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1845652 Title: rsync sends everything, not just changes Status in rsync package in Ubuntu: Incomplete Bug description: Repeated runs of rsync from PC to USB key send everything, not just the changes. This is reproducible. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: rsync 3.1.3-6 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 09:18:19 2019 InstallationDate: Installed on 2019-06-10 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1845652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
"Same Result" means it wakes up a few seconds after sleep. With bluetooth disabled, it stays in sleep as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes
** Changed in: systemd Status: Unknown => 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/1839290 Title: systemd doesn't restart a service after crashes Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Status in systemd source package in Disco: Fix Released Bug description: Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1839290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847108] [NEW] /usr/libexec/evolution-calendar-factory:11:malloc:pvl_newlist:icalcomponent_new_impl:icalcomponent_new:icalparser_add_line
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.0-2, the problem page at https://errors.ubuntu.com/problem/2d9621cf44347384040932fe78ef30f8bc83e6ee 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/. ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1847108 Title: /usr/libexec/evolution-calendar- factory:11:malloc:pvl_newlist:icalcomponent_new_impl:icalcomponent_new:icalparser_add_line Status in evolution-data-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.0-2, the problem page at https://errors.ubuntu.com/problem/2d9621cf44347384040932fe78ef30f8bc83e6ee 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/evolution-data-server/+bug/1847108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes
** Bug watch added: github.com/systemd/systemd/issues #11456 https://github.com/systemd/systemd/issues/11456 ** Also affects: systemd via https://github.com/systemd/systemd/issues/11456 Importance: Unknown Status: Unknown ** Bug watch added: github.com/systemd/systemd/issues #11305 https://github.com/systemd/systemd/issues/11305 ** Changed in: systemd Remote watch: github.com/systemd/systemd/issues #11456 => github.com/systemd/systemd/issues #11305 -- 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/1839290 Title: systemd doesn't restart a service after crashes Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Status in systemd source package in Disco: Fix Released Bug description: Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1839290/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728013] Re: NetworkManager segfaults when starting and an interface is up
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => 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/1728013 Title: NetworkManager segfaults when starting and an interface is up Status in network-manager package in Ubuntu: Confirmed Bug description: This is the kernel output I get when restarting NetworkManager with an interface being up. This is reproducible across all of my machines. I am running Funtoo with gentoo sources 4.13.9 and have been able to reproduce this problem for over 6 months. [Thu Oct 26 22:40:36 2017] NetworkManager[484]: segfault at 8 ip 00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:46:40 2017] NetworkManager[9577]: segfault at 8 ip 00479ef7 sp 7fffefab0200 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:48:37 2017] NetworkManager[9936]: segfault at 8 ip 00479ef7 sp 7ffd46445950 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:16:19 2017] NetworkManager[4029]: segfault at 8 ip 00479ef7 sp 7fff07455bc0 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:17:23 2017] NetworkManager[4474]: segfault at 8 ip 00479ef7 sp 7ffd73cca230 error 4 in NetworkManager[40+23b000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: dbus (Ubuntu)
Importance: Undecided => Medium
** Changed in: dbus (Ubuntu Xenial)
Importance: Undecided => Medium
** Tags added: ddstreet sts-sponsor-ddstreet systemd xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1846787
Title:
systemd-logind leaves leftover sessions and scope files
Status in dbus package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in dbus source package in Xenial:
In Progress
Status in systemd source package in Xenial:
In Progress
Bug description:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.
To fix this issue, patches are needed in both dbus and systemd. These improve
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.
== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification
(d8fdc62037b5)
$ git describe --contains d8fdc62037b5
v230~71^2~2
$ rmadison systemd
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.22 | xenial-updates | source, ... <
systemd | 237-3ubuntu10| bionic | source, ...
systemd | 237-3ubuntu10.29 | bionic-security | source, ...
systemd | 237-3ubuntu10.29 | bionic-updates | source, ...
systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...
== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)
$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2
$ rmadison dbus
dbus | 1.10.6-1ubuntu3| xenial | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-security | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-updates | source, ... <
dbus | 1.12.2-1ubuntu1| bionic | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-security | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-updates | source, ...
[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 & done
2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-131.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-134.scope.d
...
[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files
** Description changed:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.
To fix this issue, patches are needed in both dbus and systemd. These improve
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.
== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification
(d8fdc62037b5)
$ git describe --contains d8fdc62037b5
v230~71^2~2
$ rmadison systemd
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.22 | xenial-updates | source, ... <
systemd | 237-3ubuntu10| bionic | source, ...
systemd | 237-3ubuntu10.29 | bionic-security | source, ...
systemd | 237-3ubuntu10.29 | bionic-updates | source, ...
systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...
== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)
$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2
$ rmadison dbus
dbus | 1.10.6-1ubuntu3| xenial | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-security | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-updates | source, ... <
dbus | 1.12.2-1ubuntu1| bionic | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-security | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-updates | source, ...
[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 & done
2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-131.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-134.scope.d
...
[Regression Potential]
- The regression potential is low, as these patches have seen extensive testing
- both upstream and in more recent releases of Ubuntu. Nonetheless, these new
- packages will be rigorously tested through autopkgtest to avoid any possible
- Xenial-specific regressions.
+ As the patches change the communication socket between dbus and systemd,
possible regressions could cause systemd to not be notified of dbus events and
vice-versa. We could see units not getting started properly, and communication
between different services break down (e.g. between systemd-logind and other
processes).
+
+ In this case, the regression potential should be low as these patches
+ have seen extensive testing both upstream and in more recent releases of
+ Ubuntu.
[Touch-packages] [Bug 1847059] Re: cups crashes when trying to print double-sided
** Attachment removed: "UdevDb.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295106/+files/UdevDb.txt
** Attachment removed: "ProcModules.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295105/+files/ProcModules.txt
** Attachment removed: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295095/+files/CurrentDmesg.txt
** Attachment removed: "Dependencies.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295096/+files/Dependencies.txt
** Attachment removed: "ProcInterrupts.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295104/+files/ProcInterrupts.txt
** Attachment removed: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295103/+files/ProcCpuinfoMinimal.txt
** Attachment removed: "KernLog.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295097/+files/KernLog.txt
** Attachment removed: "Locale.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295098/+files/Locale.txt
** Attachment removed: "Lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295099/+files/Lspci.txt
** Attachment removed: "Lsusb.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295100/+files/Lsusb.txt
** Attachment removed: "PrintingPackages.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295101/+files/PrintingPackages.txt
** Attachment removed: "ProcCpuinfo.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+attachment/5295102/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1847059
Title:
cups crashes when trying to print double-sided
Status in cups package in Ubuntu:
New
Bug description:
cups fails to print, makes the printer unavailable ("backend
failure"), and subsequently reports a crash when trying to print
double-sided to a networked printer.
This behavior does not occur with the proprietary driver.Brother MFC-
L2750DW, network.
Daniel
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.12-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia wl
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CupsErrorLog:
W [07/Oct/2019:05:32:45 -0400] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
\'Brother_MFC_L2750DW_series-Gray..\' already exists
W [07/Oct/2019:05:32:45 -0400] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
\'Brother_MFC_L2750DW_series-DeviceN..\' already exists
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 7 06:34:05 2019
InstallationDate: Installed on 2019-10-02 (5 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lpstat:
device for Brother_MFC_L2750DW_series:
implicitclass://brother_mfc_l2750dw_series/
device for MFCL2750DW:
dnssd://Brother%20MFC-L2750DW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af46cd663
MachineType: To be filled by O.E.M. To be filled by O.E.M.
Papersize: letter
PpdFiles:
Brother_MFC_L2750DW_series: MFC-L2750DW series - IPP Everywhere
MFCL2750DW: Brother MFCL2750DW for CUPS
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic
root=UUID=29ce6912-3799-4448-863e-a29337317010 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to eoan on 2019-10-06 (0 days ago)
dmi.bios.date: 04/03/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99X EVO R2.0
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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: SKU
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847059/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 1847088] [NEW] Cups appends extra page with %EndDocument %%EOF to every print
Public bug reported: I am using cups with a printer connected via samba. The Printer is a Kyocera Taskalfa 5021ci. Every print I make through cups results in a last page with only %%EndDocument %%EOF on it. I've tried to debug this further and if I print with smbclient directly like this: $smbclient -W DOMAIN -U USER //server/printer Unable to initialize messaging context Enter NET.CHALMERS.SE\jochens's password: Try "help" to get a list of possible commands. smb: \> print test.pdf putting file test.pdf as test.pdf (1947.9 kb/s) (average 1947.9 kb/s) smb: \> it works without the extra page. I've tried to find the filter that adds the extra page but can not find it. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Attachment added: "/var/log/cups/error_log with debugging turned on" https://bugs.launchpad.net/bugs/1847088/+attachment/5295138/+files/error_log -- 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/1847088 Title: Cups appends extra page with %EndDocument %%EOF to every print Status in cups package in Ubuntu: New Bug description: I am using cups with a printer connected via samba. The Printer is a Kyocera Taskalfa 5021ci. Every print I make through cups results in a last page with only %%EndDocument %%EOF on it. I've tried to debug this further and if I print with smbclient directly like this: $smbclient -W DOMAIN -U USER //server/printer Unable to initialize messaging context Enter NET.CHALMERS.SE\jochens's password: Try "help" to get a list of possible commands. smb: \> print test.pdf putting file test.pdf as test.pdf (1947.9 kb/s) (average 1947.9 kb/s) smb: \> it works without the extra page. I've tried to find the filter that adds the extra page but can not find it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files
** Description changed:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.
To fix this issue, patches are needed in both dbus and systemd. These improve
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.
== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification
(d8fdc62037b5)
- - tree-wide: introduce new SOCKADDR_UN_LEN() macro, and use it everywhere
(fc2fffe7706e)
- - journald: stack allocation cannot fail (23be5709e10b)
- $ git describe --contains d8fdc62037b5 fc2fffe7706e 23be5709e10b
+ $ git describe --contains d8fdc62037b5
v230~71^2~2
- v230~71^2~1
- v230~71^2
$ rmadison systemd
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.22 | xenial-updates | source, ... <
systemd | 237-3ubuntu10| bionic | source, ...
systemd | 237-3ubuntu10.29 | bionic-security | source, ...
systemd | 237-3ubuntu10.29 | bionic-updates | source, ...
systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...
== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)
$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2
$ rmadison dbus
dbus | 1.10.6-1ubuntu3| xenial | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-security | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-updates | source, ... <
dbus | 1.12.2-1ubuntu1| bionic | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-security | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-updates | source, ...
[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 & done
2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-131.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-134.scope.d
...
[Regression Potential]
The regression potential is low, as these patches have seen extensive testing
both upstream and in more recent releases of Ubuntu. Nonetheless, these new
packages will be rigorously tested through autopkgtest to avoid any possible
Xenial-specific regressions.
** Tags added: sts-sponsor
** Patch added: "lp1846787-dbus-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1846787/+attachment/5295136/+files/lp1846787-dbus-xenial.debdiff
--
You received this bug notification
[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files
** Patch added: "lp1846787-systemd-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1846787/+attachment/5295137/+files/lp1846787-systemd-xenial.debdiff
--
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/1846787
Title:
systemd-logind leaves leftover sessions and scope files
Status in dbus package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in dbus source package in Xenial:
In Progress
Status in systemd source package in Xenial:
In Progress
Bug description:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.
To fix this issue, patches are needed in both dbus and systemd. These improve
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.
== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification
(d8fdc62037b5)
$ git describe --contains d8fdc62037b5
v230~71^2~2
$ rmadison systemd
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.22 | xenial-updates | source, ... <
systemd | 237-3ubuntu10| bionic | source, ...
systemd | 237-3ubuntu10.29 | bionic-security | source, ...
systemd | 237-3ubuntu10.29 | bionic-updates | source, ...
systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...
== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)
$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2
$ rmadison dbus
dbus | 1.10.6-1ubuntu3| xenial | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-security | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-updates | source, ... <
dbus | 1.12.2-1ubuntu1| bionic | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-security | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-updates | source, ...
[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 & done
2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-131.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-134.scope.d
...
[Regression Potential]
The regression potential is low, as these patches have seen extensive testing
both upstream and in more recent releases of Ubuntu.
[Touch-packages] [Bug 1847077] [NEW] Xorg crash
Public bug reported: oct 07 06:10:22 linux systemd[14697]: Listening on D-Bus User Message Bus Socket oct 07 06:10:22 linux systemd[14697]: Reached target Sockets. oct 07 06:10:22 linux systemd[14697]: Reached target Basic System. oct 07 06:10:22 linux systemd[14697]: Reached target Default. oct 07 06:10:22 linux systemd[14697]: Startup finished in 52ms. oct 07 06:10:22 linux systemd[1]: Started User Manager for UID 121. oct 07 06:10:22 linux systemd[14697]: Started D-Bus User Message Bus. oct 07 06:10:22 linux dbus-daemon[14711]: [session uid=121 pid=14711] AppArmor D oct 07 06:10:22 linux gnome-shell[14719]: Failed to apply DRM plane transform 0: oct 07 06:10:22 linux gnome-shell[14719]: WL: error in client communication (pid oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: (EE) oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: Fatal server error: oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: (EE) wl_drm@4: error 0: au oct 07 06:10:22 linux org.gnome.Shell.desktop[14719]: (EE) oct 07 06:10:22 linux gnome-shell[14719]: X Wayland crashed; exiting oct 07 06:10:22 linux gnome-session[14713]: gnome-session-binary[14713]: WARNING oct 07 06:10:22 linux gnome-session-binary[14713]: WARNING: App 'org.gnome.Shell oct 07 06:10:22 linux gnome-session-binary[14713]: Unrecoverable failure in requ oct 07 06:10:22 linux gdm-launch-environment][14693]: pam_unix(gdm-launch-enviro oct 07 06:10:22 linux gdm3[1178]: GdmDisplay: display lasted 0,643077 seconds oct 07 06:10:22 linux gdm3[1178]: Child process -14709 was already dead. oct 07 06:10:22 linux gdm3[1178]: Child process 14693 was already dead. oct 07 06:10:22 linux gdm3[1178]: Unable to kill session worker process oct 07 06:10:23 linux gdm-launch-environment][14732]: pam_unix(gdm-launch-enviro oct 07 06:10:23 linux systemd-logind[738]: New session c503 of user gdm. oct 07 06:10:23 linux systemd[1]: Started Session c503 of user gdm. oct 07 06:10:23 linux systemd-logind[738]: Removed session c502. oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: (--) Log file renamed oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: X.Org X Server 1.20.4 oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: X Protocol Version 11, oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Build Operating System oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Current Operating Syst oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Kernel command line: B oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Build Date: 02 May 201 oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: xorg-server-hwe-18.04 oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Current version of pix oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Before reporti oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: to make sure t oct 07 06:10:23 linux /usr/lib/gdm3/gdm-x-session[14737]: Markers: (--) probed, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 06:30:25 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.0.0-27-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.0.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.0.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2019-08-22 (45 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 3442 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=08ab3346-65ab-48e9-862e-5d9bc103907e ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 021VNN dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn021VNN:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3442 dmi.product.sku: 0651 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri:
[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files
** Changed in: dbus (Ubuntu Xenial)
Status: New => In Progress
** Changed in: systemd (Ubuntu Xenial)
Status: New => In Progress
** Description changed:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.
To fix this issue, patches are needed in both dbus and systemd. These improve
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.
== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification
(d8fdc62037b5)
- tree-wide: introduce new SOCKADDR_UN_LEN() macro, and use it everywhere
(fc2fffe7706e)
- journald: stack allocation cannot fail (23be5709e10b)
$ git describe --contains d8fdc62037b5 fc2fffe7706e 23be5709e10b
v230~71^2~2
v230~71^2~1
v230~71^2
$ rmadison systemd
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.22 | xenial-updates | source, ... <
systemd | 237-3ubuntu10| bionic | source, ...
systemd | 237-3ubuntu10.29 | bionic-security | source, ...
systemd | 237-3ubuntu10.29 | bionic-updates | source, ...
systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...
== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)
$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2
$ rmadison dbus
dbus | 1.10.6-1ubuntu3| xenial | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-security | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-updates | source, ... <
dbus | 1.12.2-1ubuntu1| bionic | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-security | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-updates | source, ...
[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
- multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 > /dev/null & done
+ multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 & done
2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-131.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-134.scope.d
...
[Regression Potential]
The regression potential is low, as these patches have seen extensive testing
both upstream and in more recent releases of Ubuntu. Nonetheless, these new
packages will be rigorously tested through autopkgtest to avoid any possible
Xenial-specific regressions.
--
You received this bug
[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Sorry, completely forgot about it... :-/ So bug 1828639 is now fixed. I guess no need to fix gconf triggers now? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour
Uploads ready in unapproved queues.
** Changed in: initramfs-tools (Ubuntu Bionic)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1831252
Title:
panic=-1 is completely ignored by the initrd causing unexpected
behaviour
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
In Progress
Status in initramfs-tools source package in Bionic:
In Progress
Status in initramfs-tools source package in Disco:
In Progress
Status in initramfs-tools source package in Eoan:
Fix Released
Bug description:
[Impact]
in Ubuntu Core we default to using panic=-1 on the kernel command line
(documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a
kernel level this works just fine and the system reboots immediately ...
when in the initramfs during boot and a panic occurs, no reboot
happens at all, the initrd spawns a shell regardless of the panic=
value ...
[Test case]
Before booting change root=$foo to root=x$foo - this will make it
panic. Then test that
1) "panic=-1" causes an immediate reboot
2) "panic=5" waits 5 seconds
3) no "panic" drops you to a shell
[Regression potential]
This adds some very specific checks for -1 in places that use ${panic}, as
such the regression potential is somewhat limited. If there were a regression,
it could be a syntax error (causing boot to fail) or a sleep not working
correctly (causing sleep to, well, not sleep) - but that's unrealistic.
[Other info]
this is caused by a filter in /usr/share/initramfs-tools/init
panic=*)
panic="${x#panic=}"
case ${panic} in
*[![:digit:].]*)
panic=
;;
esac
;;
this function only lets positive values through, else panic= simply
gets unset
the panic() function itself is also not capable of handling negative
values, it has a sleep call that interprets negative values as
commandline options instead of simply ignoring a negative sleep time
[2] (line 11).
the filter in the init script should allow the -1 value (to comply
with the kernel documentation and behaviour) and the panic() function
should properly skip the sleep call when a negative value for panic=
is set.
[1]
https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931
[2] https://paste.ubuntu.com/p/mswD8Cd869/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour
** Also affects: initramfs-tools (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu Disco)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1831252
Title:
panic=-1 is completely ignored by the initrd causing unexpected
behaviour
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
In Progress
Status in initramfs-tools source package in Bionic:
In Progress
Status in initramfs-tools source package in Disco:
In Progress
Status in initramfs-tools source package in Eoan:
Fix Released
Bug description:
[Impact]
in Ubuntu Core we default to using panic=-1 on the kernel command line
(documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a
kernel level this works just fine and the system reboots immediately ...
when in the initramfs during boot and a panic occurs, no reboot
happens at all, the initrd spawns a shell regardless of the panic=
value ...
[Test case]
Before booting change root=$foo to root=x$foo - this will make it
panic. Then test that
1) "panic=-1" causes an immediate reboot
2) "panic=5" waits 5 seconds
3) no "panic" drops you to a shell
[Regression potential]
This adds some very specific checks for -1 in places that use ${panic}, as
such the regression potential is somewhat limited. If there were a regression,
it could be a syntax error (causing boot to fail) or a sleep not working
correctly (causing sleep to, well, not sleep) - but that's unrealistic.
[Other info]
this is caused by a filter in /usr/share/initramfs-tools/init
panic=*)
panic="${x#panic=}"
case ${panic} in
*[![:digit:].]*)
panic=
;;
esac
;;
this function only lets positive values through, else panic= simply
gets unset
the panic() function itself is also not capable of handling negative
values, it has a sleep call that interprets negative values as
commandline options instead of simply ignoring a negative sleep time
[2] (line 11).
the filter in the init script should allow the -1 value (to comply
with the kernel documentation and behaviour) and the panic() function
should properly skip the sleep call when a negative value for panic=
is set.
[1]
https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931
[2] https://paste.ubuntu.com/p/mswD8Cd869/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847059] [NEW] cups crashes when trying to print double-sided
Public bug reported:
cups fails to print, makes the printer unavailable ("backend failure"),
and subsequently reports a crash when trying to print double-sided to a
networked printer.
This behavior does not occur with the proprietary driver.Brother MFC-
L2750DW, network.
Daniel
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.12-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia wl
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CupsErrorLog:
W [07/Oct/2019:05:32:45 -0400] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
\'Brother_MFC_L2750DW_series-Gray..\' already exists
W [07/Oct/2019:05:32:45 -0400] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
\'Brother_MFC_L2750DW_series-DeviceN..\' already exists
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 7 06:34:05 2019
InstallationDate: Installed on 2019-10-02 (5 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lpstat:
device for Brother_MFC_L2750DW_series:
implicitclass://brother_mfc_l2750dw_series/
device for MFCL2750DW:
dnssd://Brother%20MFC-L2750DW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af46cd663
MachineType: To be filled by O.E.M. To be filled by O.E.M.
Papersize: letter
PpdFiles:
Brother_MFC_L2750DW_series: MFC-L2750DW series - IPP Everywhere
MFCL2750DW: Brother MFCL2750DW for CUPS
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic
root=UUID=29ce6912-3799-4448-863e-a29337317010 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to eoan on 2019-10-06 (0 days ago)
dmi.bios.date: 04/03/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99X EVO R2.0
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.:bvr2501:bd04/03/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99XEVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: SKU
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
** Affects: cups (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
--
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/1847059
Title:
cups crashes when trying to print double-sided
Status in cups package in Ubuntu:
New
Bug description:
cups fails to print, makes the printer unavailable ("backend
failure"), and subsequently reports a crash when trying to print
double-sided to a networked printer.
This behavior does not occur with the proprietary driver.Brother MFC-
L2750DW, network.
Daniel
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.12-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia wl
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CupsErrorLog:
W [07/Oct/2019:05:32:45 -0400] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
\'Brother_MFC_L2750DW_series-Gray..\' already exists
W [07/Oct/2019:05:32:45 -0400] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
\'Brother_MFC_L2750DW_series-DeviceN..\' already exists
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 7 06:34:05 2019
InstallationDate: Installed on 2019-10-02 (5 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lpstat:
device for Brother_MFC_L2750DW_series:
implicitclass://brother_mfc_l2750dw_series/
device for MFCL2750DW:
dnssd://Brother%20MFC-L2750DW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af46cd663
MachineType: To be filled by O.E.M. To be filled by O.E.M.
Papersize: letter
PpdFiles:
Brother_MFC_L2750DW_series: MFC-L2750DW series - IPP Everywhere
MFCL2750DW: Brother MFCL2750DW for CUPS
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic
root=UUID=29ce6912-3799-4448-863e-a29337317010 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to eoan on 2019-10-06 (0 days ago)
dmi.bios.date: 04/03/2014
dmi.bios.vendor: American Megatrends
[Touch-packages] [Bug 1846405] Re: MSI GS65 8RF key between space and alt-gr in german layout is mapped wrong
** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => 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/1846405 Title: MSI GS65 8RF key between space and alt-gr in german layout is mapped wrong Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Disco: New Bug description: on a MSI GS65 8RF laptop the key between space and alt-gr is currently mapped to the same keycode as "#". Please backport the upstream fix at https://github.com/systemd/systemd/pull/11508 to fix this. Without this fix there is no way to type "|", "<" or ">" an this laptop model when using the german keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: udev 240-6ubuntu5.7 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CustomUdevRuleFiles: 99-msi-rgb.rules 70-snap.core.rules Date: Wed Oct 2 22:08:27 2019 InstallationDate: Installed on 2019-09-23 (9 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1038:1122 SteelSeries ApS Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=540feb73-7de0-4295-ba5a-a098cbf5f0b4 ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16Q2IMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-16Q2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.112:bd05/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GS dmi.product.name: GS65 Stealth Thin 8RF dmi.product.sku: 16Q2.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1846405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843768] Re: [FFe] Ubiquity with zfs install option
This bug was fixed in the package ubuntustudio-meta - 0.196 --- ubuntustudio-meta (0.196) eoan; urgency=medium * Refreshed dependencies * Added zfsutils-linux to desktop-core-recommends, desktop-recommends (LP: #1843768) -- Erich Eickmeyer Sun, 06 Oct 2019 14:00:12 -0700 ** Changed in: ubuntustudio-meta (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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1843768 Title: [FFe] Ubiquity with zfs install option Status in ubiquity package in Ubuntu: New Status in ubuntu-budgie-meta package in Ubuntu: Fix Released Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntustudio-meta package in Ubuntu: Fix Released Bug description: Part of the 19.10 feature announcement is zfs experimental support in the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on- ubuntu-19-10-an-introduction). We modified ubiquity to present an “EXPERIMENTAL” (with warning) ZSYS install option. This option is only visible is zfsutils-linux is installed on the system. So, it won't be available for derivatives that use ubiquity but do not seed zfsutils- linux. Update as of 20/09/2019: the plan is to not seed zsys (security review will take a while), but to only seed zfsutils-linux. People can then opt-in to zsys which should be available by default next cycle. This option takes an entire disk and have a fix set of dataset installed. There is no support but we need this to make an official install option for the next LTS. The patch has been created to be as minimal as possible. Partman does a full disk partitioning, and then the script zsys-setup the first non-ESP partition and replaces with zfs pools. 4 partitions are created: 1. if GPT partitioning: ESP partition. This one is done by partman directly. 2. bpool (for boot), pool with older zfs compatible version to be readable by grub) 3. rpool (for / and userdataset) 4. /boot/grub (ext4) to contain a single grub (NOTE: this could be later on moved to the ESP) Additionaly if a swap file has been created by ubiquity, it is recreated as a ZFS volume. If the script fails to execute, the final installation is an ext4 installation on entire disk. Note that the implementation is slightly different from the specification due to a difficult cohabitation with partman in the custom partitioning page. Please find attached the MP on ubiquity as well as the package build log. https://launchpadlibrarian.net/442036321/buildlog_ubuntu-eoan- amd64.ubiquity_19.10.10~ppa1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1843768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04
Got the same issue after the upgrade. In my case: moshe@moshe-desktop:~/New$ grep . /run/resolvconf/interface/* nameserver 127.0.0.53 moshe@moshe-desktop:~/New$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 The difference from Zoltn's issue is that I don't have the lines: options edns0 search home During the upgrade which was done using Wi-Fi, the connection went down but it was after the download completed so the upgrade ended. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1816530 Title: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04 Status in resolvconf package in Ubuntu: Invalid Bug description: I upgraded my 16.04 to 18.04 before the official release. After the upgrade I noticed that I don't have internet access. The wired network and the wifi settings looked good, but the internet didn't work. After the login the system always switched itself into airplane mode. I tethered the network via USB and Bluetooth by my mobile but they also didn't work. I found a useful answer from @andrew-woodhead666: https://answers.launchpad.net/ubuntu/+question/665374 it seems this bug is still not fixed for the upgraded dists in the main release and affects a few dozens of ubuntu users. https://askubuntu.com/questions/1021884/no-internet-after-upgrade-from-16-04-to-18-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1816530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800965] Re: Browsers don't display Devanagari script correctly
+1 on this. Some ligatures are not rendered: eg, त्र is showing up as त् र (two letters) with the default Ubuntu, because of this "Raghindi" font setting. Changing it to (in my case) Noto fixes the rendering. I made the change in my home directory (.config/fontconfig/conf.d/). Please change this system setting. -- 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/1800965 Title: Browsers don't display Devanagari script correctly Status in fontconfig package in Ubuntu: Confirmed Bug description: In the file /etc/fonts/conf.avail/65-nonlatin.conf the "Raghindi" font family is specified for devanagari script in Serif and Sans-serif style while "Lohit Hindi" in monospace. On the other hand, the Raghindi font is not installed by default. Because of this, the web browsers including Chrome and Firefox don't display the script correctly. A lot of people struggle to correct it by manually changing the settings in the browsers and partially succeed. The problem can be completely solved by replacing "Raghindi" in /etc/fonts/conf.avail/65-nonlatin.conf with "Lohit Hindi" or any other pre-installed font. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: fontconfig-config 2.13.0-5ubuntu3 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: ubuntu:GNOME Date: Thu Nov 1 07:38:12 2018 InstallationDate: Installed on 2018-10-22 (9 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.fonts.conf.avail.65-nonlatin.conf: 2018-10-26T14:54:05.700607 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1800965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800965] Re: Browsers don't display Devanagari script correctly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- 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/1800965 Title: Browsers don't display Devanagari script correctly Status in fontconfig package in Ubuntu: Confirmed Bug description: In the file /etc/fonts/conf.avail/65-nonlatin.conf the "Raghindi" font family is specified for devanagari script in Serif and Sans-serif style while "Lohit Hindi" in monospace. On the other hand, the Raghindi font is not installed by default. Because of this, the web browsers including Chrome and Firefox don't display the script correctly. A lot of people struggle to correct it by manually changing the settings in the browsers and partially succeed. The problem can be completely solved by replacing "Raghindi" in /etc/fonts/conf.avail/65-nonlatin.conf with "Lohit Hindi" or any other pre-installed font. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: fontconfig-config 2.13.0-5ubuntu3 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: ubuntu:GNOME Date: Thu Nov 1 07:38:12 2018 InstallationDate: Installed on 2018-10-22 (9 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.fonts.conf.avail.65-nonlatin.conf: 2018-10-26T14:54:05.700607 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1800965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
