[Touch-packages] [Bug 2064093] Re: if-up.d files do not have effect on ubuntu 24.04 LTS
It also looks like on 24.04, the if-up.d scripts aren't run at all when resuming from sleep. Before 24.04: - Boot - My if-up.d script that triggers for "IFACE=wlp0s20f3" gets properly triggered (it adds an IP alias to this interface using "ip addr add"). - Put ubuntu to sleep - Resume ubuntu - My if-up.d script that triggers for "IFACE=wlp0s20f3" gets properly triggered. After 24.04: - Boot - My if-up.d script that triggers for "IFACE=wlp0s20f3" gets properly triggered (it adds an IP alias to this interface using "ip addr add"). Apparently I could fix this by triggering this script with "IFACE=-all". For now I manually run the "ip addr add" command. - Put ubuntu to sleep - Resume ubuntu - My if-up.d script that triggers for "IFACE=wlp0s20f3" is not called (not even with "IFACE=-all"). The IP alias disappeared, so the interface did go down and get back up, but the script wasn't called at all. For this I don't think I have a fix? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/2064093 Title: if-up.d files do not have effect on ubuntu 24.04 LTS Status in ifupdown package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Some time ago I wrote a detailed answer to fix an error for lowering MTU size for a cisco-compatible VPN (here:https://unix.stackexchange.com/questions/768757/unable-to-ssh- into-remote-machine-but-able-to-ping-vpnc/768758#768758) After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to lower the MTU size. In particular, if I run the following command from the terminal sudo ifconfig your_tunnel_name mtu 1370 up it seems to lower the MTU size. However, the script under /etc/network/if-up.d is not automatically triggered. Does something change with the newer Ubuntu version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2064093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063484] Re: Other Software now displays the Suites instead of the Comments
** Attachment added: "with-comment-result.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+attachment/5770432/+files/with-comment-result.png ** Description changed: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. + + This has been working well for the past 10-15 years, so it’s definitely + a mistake that has been introduced with the new version. The field edit + dialogue has changed a little bit, so I’m guessing that change + introduced the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2063484 Title: Other Software now displays the Suites instead of the Comments Status in software-properties package in Ubuntu: New Bug description: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063484] Re: Other Software now displays the Suites instead of the Comments
** Attachment added: "without-comment-result.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+attachment/5770430/+files/without-comment-result.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2063484 Title: Other Software now displays the Suites instead of the Comments Status in software-properties package in Ubuntu: New Bug description: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063484] Re: Other Software now displays the Suites instead of the Comments
** Attachment added: "with-comment.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+attachment/5770431/+files/with-comment.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2063484 Title: Other Software now displays the Suites instead of the Comments Status in software-properties package in Ubuntu: New Bug description: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063484] Re: Other Software now displays the Suites instead of the Comments
** Attachment added: "without-comment.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+attachment/5770409/+files/without-comment.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2063484 Title: Other Software now displays the Suites instead of the Comments Status in software-properties package in Ubuntu: New Bug description: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2063484] [NEW] Other Software now displays the Suites instead of the Comments
Public bug reported: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2063484 Title: Other Software now displays the Suites instead of the Comments Status in software-properties package in Ubuntu: New Bug description: Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk shows the wrong field in the UI for Other Software. Where it should show the Comment field, it shows the Suites field. It only does it if there is a value in Comment though. For instance, imagine I have Inkscape PPA as a software source, with the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show “hirsute” instead of “Inkscape” as a title like it used to do. If I empty the Comment field, it does remove the title and “hirsute” is not displayed. One more thing from the upgrade: all the Comment fields’ content got lost in the process. So I have no some sources that I can’t remember why I had installed, even though I have software coming from them, which I had indicated in Comment. This has been working well for the past 10-15 years, so it’s definitely a mistake that has been introduced with the new version. The field edit dialogue has changed a little bit, so I’m guessing that change introduced the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056666] Re: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine
After some updates on friday, this morning, I was able to connect my headset. -- 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/205 Title: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine Status in bluez package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Bug description: headphone is not showing up in my ubuntu bluetooth so i cant connect my headphone to my computer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 14:10:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 82C7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic root=UUID=bed00b3d-206b-4607-8c0b-63d4f55998ef ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-ADA dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrE8CN38WW:bd12/05/2022:br1.38:efr1.38:svnLENOVO:pn82C7:pvrLenovoV15-ADA:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-ADA:skuLENOVO_MT_82C7_BU_idea_FM_V15-ADA: dmi.product.family: V15-ADA dmi.product.name: 82C7 dmi.product.sku: LENOVO_MT_82C7_BU_idea_FM_V15-ADA dmi.product.version: Lenovo V15-ADA dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 28:CD:C4:D1:98:3A ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:35089 acl:0 sco:0 events:1074 errors:0 TX bytes:48329 acl:0 sco:0 commands:549 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056666] Re: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine
Hi! Since this morning, I'm not able to plug my bluetooth headset. The bluetooth remains off, even after trying to activate it from the settings. I already did a reboot, but nothing changed. My laptop is a Lenovo P15s. Ubuntu 22.04.4 6.2.0-31-generic -- 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/205 Title: [RTL8822CE] i could not able to connect my bluetooth headphone or for context any headphone to my ubuntu machine Status in bluez package in Ubuntu: Confirmed Status in linux-hwe-6.5 package in Ubuntu: Confirmed Bug description: headphone is not showing up in my ubuntu bluetooth so i cant connect my headphone to my computer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 14:10:46 2024 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 82C7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-25-generic root=UUID=bed00b3d-206b-4607-8c0b-63d4f55998ef ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN38WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-ADA dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrE8CN38WW:bd12/05/2022:br1.38:efr1.38:svnLENOVO:pn82C7:pvrLenovoV15-ADA:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoV15-ADA:skuLENOVO_MT_82C7_BU_idea_FM_V15-ADA: dmi.product.family: V15-ADA dmi.product.name: 82C7 dmi.product.sku: LENOVO_MT_82C7_BU_idea_FM_V15-ADA dmi.product.version: Lenovo V15-ADA dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 28:CD:C4:D1:98:3A ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:35089 acl:0 sco:0 events:1074 errors:0 TX bytes:48329 acl:0 sco:0 commands:549 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
Thanks for the ping.. I have had no feedback from NVIDIA (DGX, Bluefield, Tegra), and I have informed them that from now on, we consider that 'no feedback' meant they are ok with the change. -- 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/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2048105] [NEW] Connecting second bluetooth device fails
Public bug reported: System: Ubuntu 22.04 bluez version 5.64 Devices: 2x Playstation 5 DualSense Controllers Problem description: Connecting either of the controllers individually works without a problem. But when trying to connect both of them, the second fails. Following sequence is typical and shows that there is no problem with the controllers itself: 1) connect controller #1 > succeeds 2) connect controller #2 > fails 3) disconnect controller #1 4) connect controller #2 > succeeds 5) connect controller #1 > fails SOMETIMES it works though and I didn't found out what was different. Connecting both of the controllers immediately after boot+logon works most of the times! When connecting a controller fails, there is _nothing_ in syslog. Both controllers have been paired successfully and marked as trusted devices. The failing connect attempt of the second controller first shows the system notification "connected", followed by a "disconnected" approximately 10-20 seconds later. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- 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/2048105 Title: Connecting second bluetooth device fails Status in bluez package in Ubuntu: New Bug description: System: Ubuntu 22.04 bluez version 5.64 Devices: 2x Playstation 5 DualSense Controllers Problem description: Connecting either of the controllers individually works without a problem. But when trying to connect both of them, the second fails. Following sequence is typical and shows that there is no problem with the controllers itself: 1) connect controller #1 > succeeds 2) connect controller #2 > fails 3) disconnect controller #1 4) connect controller #2 > succeeds 5) connect controller #1 > fails SOMETIMES it works though and I didn't found out what was different. Connecting both of the controllers immediately after boot+logon works most of the times! When connecting a controller fails, there is _nothing_ in syslog. Both controllers have been paired successfully and marked as trusted devices. The failing connect attempt of the second controller first shows the system notification "connected", followed by a "disconnected" approximately 10-20 seconds later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2048105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642112] Re: Can’t connect to the second BT device successfully
@Daniel van Vugt ok -- 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/1642112 Title: Can’t connect to the second BT device successfully Status in bluez package in Ubuntu: New Bug description: OS: 14.04 bluez version: 4.x After first bt device(eg. mouse) connected, try to connect second device(eg. keyboard), found it has no function when connected, and sometimes it fails to connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1642112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642112] Re: Can’t connect to the second BT device successfully
Same problem for me. System: Ubuntu 22.04 bluez version 5.64 Devices: 2x Playstation 5 DualSense Controllers Problem description: Connecting either of the controllers individually works without a problem. But when trying to connect both of them, the second fails. SOMETIMES it works though and I didn't found out what was different. Can someome tell, if this is fixed in newer versions? If yes, I will try a system upgrade out of the LTS sequence. -- 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/1642112 Title: Can’t connect to the second BT device successfully Status in bluez package in Ubuntu: New Bug description: OS: 14.04 bluez version: 4.x After first bt device(eg. mouse) connected, try to connect second device(eg. keyboard), found it has no function when connected, and sometimes it fails to connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1642112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039611] Re: [SRU] Fix fcc-unlock script for Lenovo X13s
thanks! I got feedback from xnox on my SRU, so it was still on my list to improve it but got swamped with the sprints prep (it's only my 2nd SRU..). Just to be clear I understand, do I need to open a new bug for mantic, or can i reuse this one? -- 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/2039611 Title: [SRU] Fix fcc-unlock script for Lenovo X13s Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Mantic: New Status in modemmanager source package in Noble: Fix Released Bug description: [ Impact ] Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon 8cx, come with an integrated 4G/5G modem. The modem on the X13s is manufactured by foxconn, and is based on the Qualcomm Snapdragon X55 PCIe modem. Here is the output of mmcli -m 0 on an X13s Hardware |manufacturer: foxconn | model: Qualcomm Snapdragon X55 5G | firmware revision: T99W175.F0.6.0.0.6.OG.005 | 045 1 [Feb 03 2023 10:00:00] All Linux kernel drivers are upstream to support this data modem, and included in the Ubuntu kernel for mantic. The support for this modem is also merged in modemmanager, including the fcc-unlock script for this modem model (https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22). We are however missing the symlink for the specific PCIe ID link reported on the X13s for this modem, which is shown by lspci as: 0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] [105b:e0c3] This is already fixed upstream with https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838. With the backport of this patch the modem on the X13S can be enabled by laptop users using the fcc-unlock generic guidelines. And mobile broadband is working out of the box. Without it, the modem won't work. [ Test Plan ] Without the ability to FCC unlock this modem model, any attempt to enable/start the modem will fail / stall, as detailed on https://modemmanager.org/docs/modemmanager/fcc-unlock/. With this backport/fix, the Ubuntu Mobile network settings/UI can be used to enabled the modem, unlock the SIM card and connect to the 4G/5G network (assuming the user has a SIM card with an appropriate data plan). [ Where problems could occur ] The patch is fairly isolated change. The purpose of this change is to create an additional symlink in /usr/share/ModemManager/fcc- unlock.available.d/ whose name is the PCIe ID of this specific device. PCIe IDs are documented here: https://cateee.net/lkddb/web- lkddb/MHI_BUS.html. Also links in this folder have no effect on the system, unless the user manually enable the appropriate fcc unlock script, typically by adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate modem model script. [ Other Info ] I am working on a debdiff, and will upload shortly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039611] Re: [SRU] Fix fcc-unlock script for Lenovo X13s
** Patch added: "modemmanager-1.20.6-1ubuntu2.patch" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+attachment/5710761/+files/modemmanager-1.20.6-1ubuntu2.patch -- 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/2039611 Title: [SRU] Fix fcc-unlock script for Lenovo X13s Status in modemmanager package in Ubuntu: New Bug description: [ Impact ] Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon 8cx, come with an integrated 4G/5G modem. The modem on the X13s is manufactured by foxconn, and is based on the Qualcomm Snapdragon X55 PCIe modem. Here is the output of mmcli -m 0 on an X13s Hardware |manufacturer: foxconn | model: Qualcomm Snapdragon X55 5G | firmware revision: T99W175.F0.6.0.0.6.OG.005 | 045 1 [Feb 03 2023 10:00:00] All Linux kernel drivers are upstream to support this data modem, and included in the Ubuntu kernel for mantic. The support for this modem is also merged in modemmanager, including the fcc-unlock script for this modem model (https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22). We are however missing the symlink for the specific PCIe ID link reported on the X13s for this modem, which is shown by lspci as: 0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] [105b:e0c3] This is already fixed upstream with https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838. With the backport of this patch the modem on the X13S can be enabled by laptop users using the fcc-unlock generic guidelines. And mobile broadband is working out of the box. Without it, the modem won't work. [ Test Plan ] Without the ability to FCC unlock this modem model, any attempt to enable/start the modem will fail / stall, as detailed on https://modemmanager.org/docs/modemmanager/fcc-unlock/. With this backport/fix, the Ubuntu Mobile network settings/UI can be used to enabled the modem, unlock the SIM card and connect to the 4G/5G network (assuming the user has a SIM card with an appropriate data plan). [ Where problems could occur ] The patch is fairly isolated change. The purpose of this change is to create an additional symlink in /usr/share/ModemManager/fcc- unlock.available.d/ whose name is the PCIe ID of this specific device. PCIe IDs are documented here: https://cateee.net/lkddb/web- lkddb/MHI_BUS.html. Also links in this folder have no effect on the system, unless the user manually enable the appropriate fcc unlock script, typically by adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate modem model script. [ Other Info ] I am working on a debdiff, and will upload shortly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039611] [NEW] [SRU] Fix fcc-unlock script for Lenovo X13s
Public bug reported: [ Impact ] Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon 8cx, come with an integrated 4G/5G modem. The modem on the X13s is manufactured by foxconn, and is based on the Qualcomm Snapdragon X55 PCIe modem. Here is the output of mmcli -m 0 on an X13s Hardware |manufacturer: foxconn | model: Qualcomm Snapdragon X55 5G | firmware revision: T99W175.F0.6.0.0.6.OG.005 | 045 1 [Feb 03 2023 10:00:00] All Linux kernel drivers are upstream to support this data modem, and included in the Ubuntu kernel for mantic. The support for this modem is also merged in modemmanager, including the fcc-unlock script for this modem model (https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22). We are however missing the symlink for the specific PCIe ID link reported on the X13s for this modem, which is shown by lspci as: 0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] [105b:e0c3] This is already fixed upstream with https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838. With the backport of this patch the modem on the X13S can be enabled by laptop users using the fcc-unlock generic guidelines. And mobile broadband is working out of the box. Without it, the modem won't work. [ Test Plan ] Without the ability to FCC unlock this modem model, any attempt to enable/start the modem will fail / stall, as detailed on https://modemmanager.org/docs/modemmanager/fcc-unlock/. With this backport/fix, the Ubuntu Mobile network settings/UI can be used to enabled the modem, unlock the SIM card and connect to the 4G/5G network (assuming the user has a SIM card with an appropriate data plan). [ Where problems could occur ] The patch is fairly isolated change. The purpose of this change is to create an additional symlink in /usr/share/ModemManager/fcc- unlock.available.d/ whose name is the PCIe ID of this specific device. PCIe IDs are documented here: https://cateee.net/lkddb/web- lkddb/MHI_BUS.html. Also links in this folder have no effect on the system, unless the user manually enable the appropriate fcc unlock script, typically by adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate modem model script. [ Other Info ] I am working on a debdiff, and will upload shortly ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- 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/2039611 Title: [SRU] Fix fcc-unlock script for Lenovo X13s Status in modemmanager package in Ubuntu: New Bug description: [ Impact ] Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon 8cx, come with an integrated 4G/5G modem. The modem on the X13s is manufactured by foxconn, and is based on the Qualcomm Snapdragon X55 PCIe modem. Here is the output of mmcli -m 0 on an X13s Hardware |manufacturer: foxconn | model: Qualcomm Snapdragon X55 5G | firmware revision: T99W175.F0.6.0.0.6.OG.005 | 045 1 [Feb 03 2023 10:00:00] All Linux kernel drivers are upstream to support this data modem, and included in the Ubuntu kernel for mantic. The support for this modem is also merged in modemmanager, including the fcc-unlock script for this modem model (https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22). We are however missing the symlink for the specific PCIe ID link reported on the X13s for this modem, which is shown by lspci as: 0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc. T99W175 5G Modem [Snapdragon X55] [105b:e0c3] This is already fixed upstream with https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838. With the backport of this patch the modem on the X13S can be enabled by laptop users using the fcc-unlock generic guidelines. And mobile broadband is working out of the box. Without it, the modem won't work. [ Test Plan ] Without the ability to FCC unlock this modem model, any attempt to enable/start the modem will fail / stall, as detailed on https://modemmanager.org/docs/modemmanager/fcc-unlock/. With this backport/fix, the Ubuntu Mobile network settings/UI can be used to enabled the modem, unlock the SIM card and connect to the 4G/5G network (assuming the user has a SIM card with an appropriate data plan). [ Where problems could occur ] The patch is fairly isolated change. The purpose of this change is to create an additional
[Touch-packages] [Bug 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
Deleting the certificate also worked for me. To do this user needs admin privileges. I guess this breaks basic printing functionality for regular users. This is my printer: HP_Smart_Tank_530_series_21D133 -- 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/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
** Patch added: "openssl-atexit-1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100/+attachment/5607147/+files/openssl-atexit-1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983100
Title:
dotnet build intermittently crashes with segfault on Ubuntu 18.04
Status in openssl package in Ubuntu:
New
Status in openssl source package in Bionic:
New
Bug description:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that
does not have support for the OPENSSL_NO_ATEXIT functionality from
1.1.1b (openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background
threads are still running when exit() is called, which can cause
SIGSEGV if a background thread interacts with OpenSSL after/while it
has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with
the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only
has no effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published
into the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
[Test Plan]
The described behavior can be reproduced by passing the
OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
terminate with a SEGFAULT. More concretely, a minimal reproducer is:
#include
#include
#include
#ifndef OPENSSL_INIT_NO_ATEXIT
#define OPENSSL_INIT_NO_ATEXIT 0x0008L
#endif
static void print_error_string()
{
printf("print_error_string:\n");
printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0));
}
int main(int argc, char* argv[])
{
// register this handler first, so it runs last.
atexit(print_error_string);
OPENSSL_init_ssl(
OPENSSL_INIT_ADD_ALL_CIPHERS |
OPENSSL_INIT_ADD_ALL_DIGESTS |
OPENSSL_INIT_LOAD_CONFIG |
OPENSSL_INIT_NO_ATEXIT |
OPENSSL_INIT_LOAD_CRYPTO_STRINGS |
OPENSSL_INIT_LOAD_SSL_STRINGS,
NULL);
print_error_string();
return 0;
}
Building
$ sudo apt install libssl-dev
$ gcc test.c -lssl -lcrypto
$ ./a.out
print_error_string:
ERR_reason_error_string(0) => (null)
print_error_string:
Segmentation fault (core dumped)
[Where problems could occur]
The patches adds an option to the OPENSSL_init_crypto() function to
disable the default behavior of calling of a cleanup function on
application exit. The patch also includes a few bug fixes around
various initializations that were supposed to happen once when running
threaded but were not.
These changes have the potential for regressions and it is conceivable
that they lead to incorrect behavior. However, I have also backported
and included all new testing functions in the hope that the changed
behavior will get appropriate testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
** Description changed:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that does
not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b
(openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background threads
are still running when exit() is called, which can cause SIGSEGV if a
background thread interacts with OpenSSL after/while it has unloaded.
For that reason, we always initialize OpenSSL 1.1.1 with the
OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only has no
effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published into
the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
[Test Plan]
The described behavior can be reproduced by passing the
OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
terminate with a SEGFAULT. More concretely, a minimal reproducer is:
#include
#include
#include
-
+
#ifndef OPENSSL_INIT_NO_ATEXIT
#define OPENSSL_INIT_NO_ATEXIT 0x0008L
#endif
-
+
static void print_error_string()
{
- printf("print_error_string:\n");
- printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0));
+ printf("print_error_string:\n");
+ printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0));
}
-
+
int main(int argc, char* argv[])
{
- // register this handler first, so it runs last.
- atexit(print_error_string);
-
- OPENSSL_init_ssl(
- OPENSSL_INIT_ADD_ALL_CIPHERS |
- OPENSSL_INIT_ADD_ALL_DIGESTS |
- OPENSSL_INIT_LOAD_CONFIG |
- OPENSSL_INIT_NO_ATEXIT |
- OPENSSL_INIT_LOAD_CRYPTO_STRINGS |
- OPENSSL_INIT_LOAD_SSL_STRINGS,
- NULL);
-
- print_error_string();
-
- return 0;
+ // register this handler first, so it runs last.
+ atexit(print_error_string);
+
+ OPENSSL_init_ssl(
+ OPENSSL_INIT_ADD_ALL_CIPHERS |
+ OPENSSL_INIT_ADD_ALL_DIGESTS |
+ OPENSSL_INIT_LOAD_CONFIG |
+ OPENSSL_INIT_NO_ATEXIT |
+ OPENSSL_INIT_LOAD_CRYPTO_STRINGS |
+ OPENSSL_INIT_LOAD_SSL_STRINGS,
+ NULL);
+
+ print_error_string();
+
+ return 0;
}
Building
$ sudo apt install libssl-dev
$ gcc test.c -lssl -lcrypto
- $ ./a.out
+ $ ./a.out
print_error_string:
ERR_reason_error_string(0) => (null)
print_error_string:
Segmentation fault (core dumped)
[Where problems could occur]
- * Think about what the upload changes in the software. Imagine the change is
-wrong or breaks something else: how would this show up?
+ The patches adds an option to the OPENSSL_init_crypto() function to
+ disable the default behavior of calling of a cleanup function on
+ application exit. The patch also includes a few bug fixes around various
+ initializations that were supposed to happen once when running threaded
+ but were not.
- * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
-
- * This must '''never''' be "None" or "Low", or entirely an argument as to why
-your upload is low risk.
-
- * This both shows the SRU team that the risks have been considered,
-and provides guidance to testers in regression-testing the SRU.
-
-
- [Other Info]
-
- * Anything else you think is useful to include
- * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
- * and address these questions in advance
+ These changes have the potential for regressions and it is conceivable
+ that they lead to incorrect behavior. However, I have also backported
+ and included all new testing functions in the hope that the changed
+ behavior will get appropriate testing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983100
Title:
dotnet build intermittently crashes with segfault on Ubuntu 18.04
Status in openssl package in Ubuntu:
New
Status in openssl source package in Bionic:
New
Bug description:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that
does not have support for the OPENSSL_NO_ATEXIT functionality from
1.1.1b (openssl/openssl@c2b3db2).
The threading model in .NET has the
[Touch-packages] [Bug 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
** Description changed:
+ [Impact]
+
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that does
not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b
(openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background threads
are still running when exit() is called, which can cause SIGSEGV if a
background thread interacts with OpenSSL after/while it has unloaded.
For that reason, we always initialize OpenSSL 1.1.1 with the
OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only has no
effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published into
the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
+
+ [Test Plan]
+
+ The described behavior can be reproduced by passing the
+ OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
+ terminate with a SEGFAULT. More concretely, a minimal reproducer is:
+
+ #include
+ #include
+ #include
+
+ #ifndef OPENSSL_INIT_NO_ATEXIT
+ #define OPENSSL_INIT_NO_ATEXIT 0x0008L
+ #endif
+
+ static void print_error_string()
+ {
+ printf("print_error_string:\n");
+ printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0));
+ }
+
+ int main(int argc, char* argv[])
+ {
+ // register this handler first, so it runs last.
+ atexit(print_error_string);
+
+ OPENSSL_init_ssl(
+ OPENSSL_INIT_ADD_ALL_CIPHERS |
+ OPENSSL_INIT_ADD_ALL_DIGESTS |
+ OPENSSL_INIT_LOAD_CONFIG |
+ OPENSSL_INIT_NO_ATEXIT |
+ OPENSSL_INIT_LOAD_CRYPTO_STRINGS |
+ OPENSSL_INIT_LOAD_SSL_STRINGS,
+ NULL);
+
+ print_error_string();
+
+ return 0;
+ }
+
+ Building
+
+ $ sudo apt install libssl-dev
+ $ gcc test.c -lssl -lcrypto
+ $ ./a.out
+ print_error_string:
+ ERR_reason_error_string(0) => (null)
+ print_error_string:
+ Segmentation fault (core dumped)
+
+ [Where problems could occur]
+
+ * Think about what the upload changes in the software. Imagine the change is
+wrong or breaks something else: how would this show up?
+
+ * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+
+ * This must '''never''' be "None" or "Low", or entirely an argument as to why
+your upload is low risk.
+
+ * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+
+
+ [Other Info]
+
+ * Anything else you think is useful to include
+ * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
+ * and address these questions in advance
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983100
Title:
dotnet build intermittently crashes with segfault on Ubuntu 18.04
Status in openssl package in Ubuntu:
New
Status in openssl source package in Bionic:
New
Bug description:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that
does not have support for the OPENSSL_NO_ATEXIT functionality from
1.1.1b (openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background
threads are still running when exit() is called, which can cause
SIGSEGV if a background thread interacts with OpenSSL after/while it
has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with
the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only
has no effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published
into the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
[Test Plan]
The described behavior can be reproduced by passing the
OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
terminate with a SEGFAULT. More concretely, a minimal reproducer is:
#include
#include
#include
#ifndef OPENSSL_INIT_NO_ATEXIT
#define OPENSSL_INIT_NO_ATEXIT 0x0008L
#endif
static void print_error_string()
{
printf("print_error_string:\n");
printf("ERR_reason_error_string(0) =>
[Touch-packages] [Bug 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
I uploaded a patched package to https://launchpad.net/~nicolasbock/+archive/ubuntu/lp1983100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1983100 Title: dotnet build intermittently crashes with segfault on Ubuntu 18.04 Status in openssl package in Ubuntu: New Status in openssl source package in Bionic: New Bug description: Bionic's OpenSSL 1.1.1 package (https://launchpad.net/ubuntu/bionic/+source/openssl) is the only version of openssl 1.1.1 on any distro that we've encountered that does not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b (openssl/openssl@c2b3db2). The threading model in .NET has the possibility that background threads are still running when exit() is called, which can cause SIGSEGV if a background thread interacts with OpenSSL after/while it has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only has no effect on Bionic). We feel that the stability of applications on Ubuntu 18.04 would be improved if the functionality of OPENSSL_NO_ATEXIT was merged into the bionic openssl 1.1.1 package, even if the constant isn't published into the header for the dev package. Context: https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1983100] [NEW] dotnet build intermittently crashes with segfault on Ubuntu 18.04
Public bug reported: Bionic's OpenSSL 1.1.1 package (https://launchpad.net/ubuntu/bionic/+source/openssl) is the only version of openssl 1.1.1 on any distro that we've encountered that does not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b (openssl/openssl@c2b3db2). The threading model in .NET has the possibility that background threads are still running when exit() is called, which can cause SIGSEGV if a background thread interacts with OpenSSL after/while it has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only has no effect on Bionic). We feel that the stability of applications on Ubuntu 18.04 would be improved if the functionality of OPENSSL_NO_ATEXIT was merged into the bionic openssl 1.1.1 package, even if the constant isn't published into the header for the dev package. Context: https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101 ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Affects: openssl (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: openssl (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1983100 Title: dotnet build intermittently crashes with segfault on Ubuntu 18.04 Status in openssl package in Ubuntu: New Status in openssl source package in Bionic: New Bug description: Bionic's OpenSSL 1.1.1 package (https://launchpad.net/ubuntu/bionic/+source/openssl) is the only version of openssl 1.1.1 on any distro that we've encountered that does not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b (openssl/openssl@c2b3db2). The threading model in .NET has the possibility that background threads are still running when exit() is called, which can cause SIGSEGV if a background thread interacts with OpenSSL after/while it has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only has no effect on Bionic). We feel that the stability of applications on Ubuntu 18.04 would be improved if the functionality of OPENSSL_NO_ATEXIT was merged into the bionic openssl 1.1.1 package, even if the constant isn't published into the header for the dev package. Context: https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752]
*** Bug 447585 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752]
*** Bug 447039 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752]
*** Bug 444851 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941752]
*** Bug 445763 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Hi Dan, Before the upstream openssl fix [1] the behavior was to send a proper CertificateStatus if the client requested the status_request extension from the server in a CertificateRequest. In other words, the additional information contains valid data. [1] https://github.com/openssl/openssl/pull/9780 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 The issue leads to various client failures with TLS 1.3 as described in, e.g. https://github.com/golang/go/issues/35722 https://github.com/golang/go/issues/34040 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694989] Re: apt-mark overwrites existing held package info
This is very annoying, I agree that either, apt-mark should not accept 'uninstalled' packages or we should avoid losing packages marked as 'hold' Steps to reproduce (assuming none of these two packages are available) Trying to mark as hold two uninstalled packages... and notice that the second we add the second one we lost the status for the first one.. > apt update > apt-mark hold p0f p0f set on hold. > apt-mark showhold p0f > grep -c p0f /var/lib/dpkg/status 1 > apt-mark hold dovecot-core dovecot-core set on hold. > apt-mark showhold dovecot-core > grep -c p0f /var/lib/dpkg/status 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1694989 Title: apt-mark overwrites existing held package info Status in apt package in Ubuntu: Triaged Status in apt package in Debian: New Bug description: Running apt-mark hold commands overwrites / nullifies any existing held package data. Not sure if this is by design, but I assume it's meant to be cumulative. Ubuntu version: 16.04.2 LTS Package version: apt 1.2.19 amd64 Expected behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 3dchess 0ad Actual behaviour: apt-mark hold 3dchess apt-mark hold 0ad apt-mark showhold 0ad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
** Description changed: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 + + The issue leads to various client failures with TLS 1.3 as described in, + e.g. + + https://github.com/golang/go/issues/35722 + https://github.com/golang/go/issues/34040 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 The issue leads to various client failures with TLS 1.3 as described in, e.g. https://github.com/golang/go/issues/35722 https://github.com/golang/go/issues/34040 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
** Description changed: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: - Version = TLS 1.2 (0x303) - Content Type = ApplicationData (23) - Length = 1591 - Inner Content Type = Handshake (22) - CertificateRequest, Length=1570 - request_context (len=0): - extensions, length = 1567 - extension_type=status_request(5), length=1521 - - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. - 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. - 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. - 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG + Version = TLS 1.2 (0x303) + Content Type = ApplicationData (23) + Length = 1591 + Inner Content Type = Handshake (22) + CertificateRequest, Length=1570 + request_context (len=0): + extensions, length = 1567 + extension_type=status_request(5), length=1521 + - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. + 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. + 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. + 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break - with this patch. As a non-empty reply is incorrect behavior + with this patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. To manage notifications about this bug go to:
[Touch-packages] [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
Test package at https://launchpad.net/~nicolasbock/+archive/ubuntu/sf00317240 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: New Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. As a non-empty reply is incorrect behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest
** Patch added: "bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+attachment/5518220/+files/bionic.debdiff ** Changed in: openssl (Ubuntu) Assignee: (unassigned) => Nicolas Bock (nicolasbock) ** Changed in: openssl (Ubuntu Bionic) Assignee: (unassigned) => Nicolas Bock (nicolasbock) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: New Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. As a non-empty reply is incorrect behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940141] [NEW] OpenSSL servers can send a non-empty status_request in a CertificateRequest
Public bug reported: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. As a non-empty reply is incorrect behavior ** Affects: openssl (Ubuntu) Importance: Undecided Assignee: Nicolas Bock (nicolasbock) Status: New ** Affects: openssl (Ubuntu Bionic) Importance: Undecided Assignee: Nicolas Bock (nicolasbock) Status: New ** Also affects: openssl (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1940141 Title: OpenSSL servers can send a non-empty status_request in a CertificateRequest Status in openssl package in Ubuntu: New Status in openssl source package in Bionic: New Bug description: [Impact] openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a CertificateRequest message to the client with a non-empty status_request extension. This issue was fixed in openssl-1.1.1d and is included in Focal onward. Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767 Upstream patch review at https://github.com/openssl/openssl/pull/9780 [Test Plan] The issue can be reproduced by building with `enable-ssl-trace` and then running `s_server` like this: ``` openssl s_server -key key.pem -cert cert.pem -status_file test/recipes/ocsp-response.der -Verify 5 ``` And running `s_client` like this: ``` openssl s_client -status -trace -cert cert.pem -key key.pem ``` The output shows a `status_request` extension in the `CertificateRequest` as follows: Received Record Header: Version = TLS 1.2 (0x303) Content Type = ApplicationData (23) Length = 1591 Inner Content Type = Handshake (22) CertificateRequest, Length=1570 request_context (len=0): extensions, length = 1567 extension_type=status_request(5), length=1521 - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2 0.. 000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01 0.+.0.. 001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86 0...0.. 002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47 0..1.0...UG ...more lines omitted... If the `status_request` extension is present in a `CertificateRequest` then it must be empty according to RFC8446, Sec. 4.4.2.1. [Where problems could occur] The patch disables the `status_request` extension inside a `CertificateRequest`. Applications expecting the incorrect, non-empty reply for the `status_request` extension will break with this patch. As a non-empty reply is incorrect behavior To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934147] Re: systemd leaks abandoned session scopes
** Description changed:
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
The simple reproducer
- for i in {1..100}; do ssh localhost sudo systemctl daemon-reload & ssh
localhost sleep 1 & done
- jobs -p | xargs --verbose --no-run-if-empty kill -KILL
- systemctl status --all 2> /dev/null | grep --before-context 3 abandoned
+ $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl daemon-
+ reload & ssh localhost sleep 1 & done
+
+ $ systemctl status --all 2> /dev/null | grep --before-context 3
+ abandoned
will produce something similar to
-│ ├─ 175 su - ubuntu
-│ ├─ 178 -su
-│ ├─62375 systemctl status --all
-│ └─62376 grep --color=auto --before-context 3 abandoned
+ │ ├─ 175 su - ubuntu
+ │ ├─ 178 -su
+ │ ├─62375 systemctl status --all
+ │ └─62376 grep --color=auto --before-context 3 abandoned
--
● session-273.scope - Session 273 of user ubuntu
-Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
+ Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
Transient: yes
-Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
+ Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-274.scope - Session 274 of user ubuntu
-Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
+ Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
Transient: yes
-Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
+ Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-30.scope - Session 30 of user ubuntu
-Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
+ Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
Transient: yes
-Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
+ Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
--
● session-302.scope - Session 302 of user ubuntu
-Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
+ Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
Transient: yes
-Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
+ Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
--
-│ ├─ 175 su - ubuntu
-│ ├─ 178 -su
-│ ├─62375 systemctl status --all
-│ └─62376 grep --color=auto --before-context 3 abandoned
+ │ ├─ 175 su - ubuntu
+ │ ├─ 178 -su
+ │ ├─62375 systemctl status --all
+ │ └─62376 grep --color=auto --before-context 3 abandoned
The system in question is running Bionic, systemd-237-3ubuntu10.48
** Description changed:
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
The simple reproducer
$ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl daemon-
reload & ssh localhost sleep 1 & done
+
+ Wait > 1 second
+
+ $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL
+
+ To clean out STOPPED jobs and
$ systemctl status --all 2> /dev/null | grep --before-context 3
abandoned
will produce something similar to
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
--
● session-273.scope - Session 273 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-274.scope - Session 274 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-30.scope - Session 30 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
--
● session-302.scope - Session 302 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
--
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376
[Touch-packages] [Bug 1934147] [NEW] systemd leaks abandoned session scopes
Public bug reported:
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
The simple reproducer
for i in {1..100}; do ssh localhost sudo systemctl daemon-reload & ssh
localhost sleep 1 & done
jobs -p | xargs --verbose --no-run-if-empty kill -KILL
systemctl status --all 2> /dev/null | grep --before-context 3 abandoned
will produce something similar to
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
--
● session-273.scope - Session 273 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-274.scope - Session 274 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-30.scope - Session 30 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
--
● session-302.scope - Session 302 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
--
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
The system in question is running Bionic, systemd-237-3ubuntu10.48
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Dan Streetman (ddstreet)
Status: New
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dan Streetman (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/1934147
Title:
systemd leaks abandoned session scopes
Status in systemd package in Ubuntu:
New
Bug description:
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
The simple reproducer
for i in {1..100}; do ssh localhost sudo systemctl daemon-reload & ssh
localhost sleep 1 & done
jobs -p | xargs --verbose --no-run-if-empty kill -KILL
systemctl status --all 2> /dev/null | grep --before-context 3 abandoned
will produce something similar to
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
--
● session-273.scope - Session 273 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-274.scope - Session 274 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-30.scope - Session 30 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
--
● session-302.scope - Session 302 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
--
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
The system in question is running Bionic, systemd-237-3ubuntu10.48
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934147/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933669] Re: qt3d5-dev - cmake support missing for Qt3D Animation
** Tags added: foca ** Tags removed: foca ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt3d-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1933669 Title: qt3d5-dev - cmake support missing for Qt3D Animation Status in qt3d-opensource-src package in Ubuntu: New Bug description: Hello, I'm working on a Qt application which uses the Qt3D module. The application is spec'd to support ubuntu 20.04 at least. The qt3d-dev package (at least on focal) is missing the following files: /usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfig.cmake /usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfigVersion.cmake All others Qt3D modules have their own similar files but not the Animation module. This prevent me from building my application using official packages. Are they missing on purpose? Is there any work around? All the best To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1933669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933669] [NEW] qt3d5-dev - cmake support missing for Qt3D Animation
Public bug reported: Hello, I'm working on a Qt application which uses the Qt3D module. The application is spec'd to support ubuntu 20.04 at least. The qt3d-dev package (at least on focal) is missing the following files: /usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfig.cmake /usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfigVersion.cmake All others Qt3D modules have their own similar files but not the Animation module. This prevent me from building my application using official packages. Are they missing on purpose? Is there any work around? All the best ** Affects: qt3d-opensource-src (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello, - I'm working on a Qt application which use the Qt3D module. The + I'm working on a Qt application which uses the Qt3D module. The application is spec'd to support ubuntu 20.04 at least. in the qt3d-dev package (at least on focal) is missing the following files: /usr/lib/-linux-gnu/cmake/Qt53DCore/Qt53DAnimationConfig.cmake /usr/lib/-linux-gnu/cmake/Qt53DCore/Qt53DAnimationConfigVersion.cmake All others Qt3D modules have their own similar files but not the Animation module. This prevent me from building my application using official packages. Are they missing on purpose? Is there any work around? All the best ** Description changed: Hello, I'm working on a Qt application which uses the Qt3D module. The application is spec'd to support ubuntu 20.04 at least. - in the qt3d-dev package (at least on focal) is missing the following - files: + The qt3d-dev package (at least on focal) is missing the following files: /usr/lib/-linux-gnu/cmake/Qt53DCore/Qt53DAnimationConfig.cmake /usr/lib/-linux-gnu/cmake/Qt53DCore/Qt53DAnimationConfigVersion.cmake All others Qt3D modules have their own similar files but not the Animation module. This prevent me from building my application using official packages. Are they missing on purpose? Is there any work around? All the best ** Description changed: Hello, I'm working on a Qt application which uses the Qt3D module. The application is spec'd to support ubuntu 20.04 at least. The qt3d-dev package (at least on focal) is missing the following files: - /usr/lib/-linux-gnu/cmake/Qt53DCore/Qt53DAnimationConfig.cmake - /usr/lib/-linux-gnu/cmake/Qt53DCore/Qt53DAnimationConfigVersion.cmake + /usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfig.cmake + /usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfigVersion.cmake All others Qt3D modules have their own similar files but not the Animation module. This prevent me from building my application using official packages. Are they missing on purpose? Is there any work around? All the best -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt3d-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1933669 Title: qt3d5-dev - cmake support missing for Qt3D Animation Status in qt3d-opensource-src package in Ubuntu: New Bug description: Hello, I'm working on a Qt application which uses the Qt3D module. The application is spec'd to support ubuntu 20.04 at least. The qt3d-dev package (at least on focal) is missing the following files: /usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfig.cmake /usr/lib/-linux-gnu/cmake/Qt53DAnimation/Qt53DAnimationConfigVersion.cmake All others Qt3D modules have their own similar files but not the Animation module. This prevent me from building my application using official packages. Are they missing on purpose? Is there any work around? All the best To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1933669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1929305] [NEW] [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at all
Public bug reported: Inserting a headset jack is detected. I can slide the volume. But no sound at all in the headset. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fanchon1613 F pulseaudio /dev/snd/pcmC0D0p: fanchon1613 F...m pulseaudio /dev/snd/controlC1: fanchon1613 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 22 21:46:36 2021 InstallationDate: Installed on 2021-05-22 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_BE:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_BE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Audio interne - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fanchon1613 F pulseaudio /dev/snd/pcmC0D0p: fanchon1613 F...m pulseaudio /dev/snd/controlC1: fanchon1613 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2010 dmi.bios.release: 11.40 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1140Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 11.40 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:br11.40:efr11.40:svnSonyCorporation:pnVPCEB3E1E:pvrC606TWY5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCEB3E1E dmi.product.sku: N/A dmi.product.version: C606TWY5 dmi.sys.vendor: Sony Corporation ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1929305 Title: [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Inserting a headset jack is detected. I can slide the volume. But no sound at all in the headset. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fanchon1613 F pulseaudio /dev/snd/pcmC0D0p: fanchon1613 F...m pulseaudio /dev/snd/controlC1: fanchon1613 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 22 21:46:36 2021 InstallationDate: Installed on 2021-05-22 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_BE:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_BE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Audio interne - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fanchon1613 F pulseaudio /dev/snd/pcmC0D0p: fanchon1613 F...m pulseaudio /dev/snd/controlC1: fanchon1613 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2010 dmi.bios.release: 11.40 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1140Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 11.40 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:br11.40:efr11.40:svnSonyCorporation:pnVPCEB3E1E:pvrC606TWY5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCEB3E1E dmi.product.sku: N/A dmi.product.version: C606TWY5 dmi.sys.vendor: Sony Corporation To manage notifications
[Touch-packages] [Bug 1846334] Re: cupsd assert failure: free(): invalid pointer
I confirm the hirsute version fixes the issue. I created https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/ recently without having seen this bug report, and I'm pretty confident it's the same issue. I reinstalled groovy on a VM, confirmed the bug occurred (it did), rebuilt 2.3.3op1 from hirsute and installed it. The problem no longer occurs after that. -- 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/1846334 Title: cupsd assert failure: free(): invalid pointer Status in cups package in Ubuntu: Fix Committed Bug description: Just running in the background, no user action (printing) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: free(): invalid pointer Date: Tue Oct 1 19:41:35 2019 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-09 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: letter PpdFiles: HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at malloc.c:5332 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] Re: cups crashes with SIGABRT every other printing attempt
Looks like it may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334. The backtrace I got from the core dump locates the errorneous free() call in ippDelete as well. Plus it's also a samsung printer. -- 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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. Cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-01-28 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) KernLog: Lpstat: device for Samsung_C48x_Series_SEC842519933D78_: implicitclass://Samsung_C48x_Series_SEC842519933D78_/ MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 RebootRequiredPkgs: linux-image-5.8.0-43-generic linux-base Tags: groovy Uname: Linux 5.8.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434DA_UM433DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434DA_UM433DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] Re: cups crashes with SIGABRT every other printing attempt
** Description changed: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. - I could not find a trace of the coredump, and cuspd's error_log shows - nothing happening around the crash (it does show some - "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, - but I figured this would be normal, I can see the same message on other - machines that have no printing issues). - - I would expect this kind of event to trigger an apport report, but there - is no apport popup when it happens. Maybe because it's not a user - process, not sure (this is not my usual setup, I've not been using - Ubuntu for years). + Cuspd's error_log shows nothing happening around the crash (it does show + some "org.freedesktop.ColorManager.AlreadyExists" error messages on + restart, but I figured this would be normal, I can see the same message + on other machines that have no printing issues). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-01-28 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) KernLog: Lpstat: - device for Samsung_C48x_Series_SEC842519933D78_: implicitclass://Samsung_C48x_Series_SEC842519933D78_/ + device for Samsung_C48x_Series_SEC842519933D78_: implicitclass://Samsung_C48x_Series_SEC842519933D78_/ MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA Package: cups 2.3.3-3ubuntu1 PackageArchitecture: amd64 Papersize: a4 PpdFiles: - Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission denied + Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 RebootRequiredPkgs: linux-image-5.8.0-43-generic linux-base Tags: groovy Uname: Linux 5.8.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434DA_UM433DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434DA_UM433DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu.
[Touch-packages] [Bug 1915181] Re: cups crashes with SIGABRT every other printing attempt
** Description changed: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). + + --- + + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.5 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2021-01-28 (12 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + KernLog: + Lpstat: + device for Samsung_C48x_Series_SEC842519933D78_: implicitclass://Samsung_C48x_Series_SEC842519933D78_/ + MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA + Package: cups 2.3.3-3ubuntu1 + PackageArchitecture: amd64 + Papersize: a4 + PpdFiles: + Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission denied + ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776 + ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 + RebootRequiredPkgs: linux-image-5.8.0-43-generic linux-base + Tags: groovy + Uname: Linux 5.8.0-41-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True + + dmi.bios.date: 09/05/2019 + dmi.bios.release: 5.14 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: UX434DA_UM433DA.302 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX434DA + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: ZenBook + dmi.product.name: ZenBook UX434DA_UM433DA + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer
[Touch-packages] [Bug 1915181] Re: cups crashes with SIGABRT every other printing attempt
I managed to find a core dump for one of those crashes. ** Attachment added: "cupsd core dump" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+attachment/5462043/+files/_usr_sbin_cupsd.0.crash -- 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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461772/+files/acpidump.txt ** Description changed: - Using ubuntu 20.04, cups 2.3.3-3ubuntu1, with a networked Samsung C480 + Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. - The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). - --- - ProblemType: Bug - ApportVersion: 2.20.11-0ubuntu50.5 - Architecture: amd64 - CasperMD5CheckResult: skip - CurrentDesktop: ubuntu:GNOME - DistroRelease: Ubuntu 20.10 - InstallationDate: Installed on 2021-01-28 (12 days ago) - InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) - KernLog: - - Lpstat: device for Samsung_C48x_Series_SEC842519933D78_: implicitclass://Samsung_C48x_Series_SEC842519933D78_/ - MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA - Package: cups 2.3.3-3ubuntu1 - PackageArchitecture: amd64 - Papersize: a4 - PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission denied - ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776 - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash - ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776 - ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 - RebootRequiredPkgs: - linux-image-5.8.0-43-generic - linux-base - Tags: groovy - Uname: Linux 5.8.0-41-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo - _MarkForUpload: True - dmi.bios.date: 09/05/2019 - dmi.bios.release: 5.14 - dmi.bios.vendor: American Megatrends Inc. - dmi.bios.version: UX434DA_UM433DA.302 - dmi.board.asset.tag: ATN12345678901234567 - dmi.board.name: UX434DA - dmi.board.vendor: ASUSTeK COMPUTER INC. - dmi.board.version: 1.0 - dmi.chassis.asset.tag: No Asset Tag - dmi.chassis.type: 10 - dmi.chassis.vendor: ASUSTeK COMPUTER INC. - dmi.chassis.version: 1.0 - dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: - dmi.product.family: ZenBook - dmi.product.name: ZenBook UX434DA_UM433DA - dmi.product.version: 1.0 - dmi.sys.vendor: ASUSTeK COMPUTER INC. + The same printer works flawlessly on a different computer using Arch and + cups 2.3.3 as well (albeit without any ubuntu patches, obviously). -- 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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt
[Touch-packages] [Bug 1915181] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461771/+files/UdevDb.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461770/+files/ProcModules.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461769/+files/ProcInterrupts.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461768/+files/ProcCpuinfoMinimal.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461767/+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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] PrintingPackages.txt
apport information ** Attachment added: "PrintingPackages.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461766/+files/PrintingPackages.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461764/+files/Lsusb-t.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461765/+files/Lsusb-v.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461762/+files/Lspci-vt.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461761/+files/Lspci.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] Locale.txt
apport information ** Attachment added: "Locale.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461760/+files/Locale.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461759/+files/Dependencies.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461763/+files/Lsusb.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461758/+files/CurrentDmesg.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] CupsErrorLog.txt
apport information ** Attachment added: "CupsErrorLog.txt" https://bugs.launchpad.net/bugs/1915181/+attachment/5461757/+files/CupsErrorLog.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/1915181 Title: cups crashes with SIGABRT every other printing attempt Status in cups package in Ubuntu: New Bug description: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915181] [NEW] cups crashes with SIGABRT every other printing attempt
Public bug reported: Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected groovy ** Tags added: apport-collected groovy ** Description changed: Using ubuntu 20.04, cups 2.3.3-3ubuntu1, with a networked Samsung C480 printer (was automatically detected and set up on installation of the system). Every other attempt to print fails with a varying message depending on the printing app (eg. on libreoffice write, "Cannot start printer"). Waiting a few minutes and retrying prints successfully. Looking at cups.service journal messages while attempting to print, it looks like the second printing attempt crashes cupsd cupsd[]: free(): invalid pointer systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: cups.service: Failed with result core-dump The service then proceeds to restart after a few seconds, and trying to print again succeeds. Trying to print once more thereafter triggers the issue again. I could not find a trace of the coredump, and cuspd's error_log shows nothing happening around the crash (it does show some "org.freedesktop.ColorManager.AlreadyExists" error messages on restart, but I figured this would be normal, I can see the same message on other machines that have no printing issues). I would expect this kind of event to trigger an apport report, but there is no apport popup when it happens. Maybe because it's not a user process, not sure (this is not my usual setup, I've not been using Ubuntu for years). This is a pretty standard (and recent) ubuntu install, with not much customized; in particular no apport custom config was made, and nothing was configured on cups side or ubuntu print settings, everything is set up as it was autodetected on install. - The same printer works flawlessly on a different computer using Arch and - cups 2.3.3 as well (albeit without any ubuntu patches, obviously). + The same printer works flawlessly on a different computer using Arch and cups 2.3.3 as well (albeit without any ubuntu patches, obviously). + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.5 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2021-01-28 (12 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + KernLog: + + Lpstat: device for Samsung_C48x_Series_SEC842519933D78_: implicitclass://Samsung_C48x_Series_SEC842519933D78_/ + MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA + Package: cups 2.3.3-3ubuntu1 + PackageArchitecture: amd64 + Papersize: a4 + PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission denied + ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root resume_offset=6731776 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic
Re: [Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Tue, Sep 29 2020, Brian Murray wrote: > On Tue, Sep 29, 2020 at 12:38:38PM -0000, Nicolas Bock wrote: > Could you please run 'systemctl status whoopsie' and > include the output of the command here? $ sudo systemctl status whoopsie ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-09-29 06:27:06 MDT; 10h ago Main PID: 2686 (whoopsie) Tasks: 3 (limit: 47889) Memory: 5.0M CGroup: /system.slice/whoopsie.service └─2686 /usr/bin/whoopsie -f Sep 29 08:18:55 rubberducky whoopsie[2686]: [08:18:55] offline Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] online Sep 29 08:59:15 rubberducky whoopsie[2686]: [08:59:15] offline Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] online -- 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/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in apport source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
Still failing for me. I see now: Sep 29 06:32:27 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 29 06:32:27 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 29 06:32:27 rubberducky systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.path: Failed with result 'unit-start-limit-hit'. I have 2 crash files in /var/crash. Note that those two files were in /var/crash already on boot, I didn't add anything to this directory. -- 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/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in apport source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start
Re: [Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Fri, Sep 25 2020, Brian Murray wrote: > The issue with PathChanged is that /var/crash is used for writing three > types of files. The .crash file, the .upload file (which signifies the > crash is ready to be uploaded), and the .uploaded file (which contains > the UUID of the crash in the error tracker and indicates the crash has > been uploaded). So if PathChanged is used then whoopsie-upload-all will > be called for .upload and .uploaded files. Additionally, there is no > PathChangedGlob so that we could watch for just .crash files. Thanks, that makes sense. Although re-reading the systemd.path manpage over again I still don't understand how this ever worked. It says: "PathExists= may be used to watch the mere existence of a file or directory. If the file specified exists, the configured unit is activated." I read this as saying that the current behavior on Groovy is actually correct. Or am I missing something? > To help with the issue I'm working on a change to whoopsie-upload-all to > remove the .crash file after a .uploaded file exists. Thanks! I think this certainly should help. -- 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/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: In Progress Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
@balint I was wondering why we don't use `PathChanged` in the systemd path file. This checks for any changes in the path and will pick up new crash files... But after reading the systemd docs again I guess the reason is that we want the service to activate if the crash directory already contains a crash file on startup. Am I understanding this correctly? -- 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/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: In Progress Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On systemd-246.4-1ubuntu1 the setting PathChangedGlob leads to an error. But I tried the following which seems to work correctly: [Path] # PathExistsGlob=/var/crash/*.crash PathChanged=/var/crash Thanks @rockrequin for the hint! -- 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/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: In Progress Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
After deleting the files *.upload{,ed} I can run
$ sudo /usr/share/apport/whoopsie-upload-all
/var/crash/_usr_bin_emacs-gtk.1000.crash already has info collected
Marking /var/crash/_usr_bin_emacs-gtk.1000.crash for whoopsie upload
All reports processed
And get the two files back. The content of the uploaded file is
$ sudo cat _usr_bin_emacs-gtk.1000.uploaded
1c9b8196-f9f4-11ea-b6f1-fa163ee63de6
Is this procedure supposed to delete the crash file at some point?
--
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/1891657
Title:
systemd 100% cpu usage apport-autoreport.service: Failed with result
'start-limit-hit'
Status in apport package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Status in apport source package in Groovy:
Confirmed
Status in systemd source package in Groovy:
Confirmed
Bug description:
after upgrade from Ubuntu 20.04 to 20.10
seeing systemd use 100% cpu forever
top
top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39
Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie
%Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si,
0.0 st
MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9
buff/cache
MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail
Mem
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+
COMMAND
1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25
systemd
4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56
tracker-miner-f
820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06
dbus-daemon
316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41
systemd-journal
844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52
rsyslogd
858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98
systemd-logind
5 root 20 0 0 0 0 I 3.4 0.0 0:05.01
kworker/0:0-events
35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48
MainThread
5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19
gnome-shell
7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05
gnome-terminal-
36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99
Web Content
957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48
containerd
1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16
fancontrol
sudo tail -n 100 /var/log/syslog
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed
with result 'start-limit-hit'.
Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error
reports when automatic reporting is enabled.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start
request repeated too quickly.
Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed
with result 'start-limit-hit'.
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
When I run the whoopsie upload script I get: $ sudo /usr/share/apport/whoopsie-upload-all /var/crash/_usr_bin_emacs-gtk.1000.crash already marked for upload, skipping All reports processed Why is it skipping the crash? -- 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/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
$ journalctl -b -u apport-autoreport Sep 14 13:01:52 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: Collecting info for /var/crash/_usr_bin_gnome-shell.1000.crash... Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: Marking /var/crash/_usr_bin_gnome-shell.1000.crash for whoopsie upload Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147307]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147307]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147310]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147310]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147313]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147313]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147315]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147315]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147317]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147317]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 14 13:02:07 rubberducky systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 14 13:02:07 rubberducky systemd[1]: Failed to start Process error reports when automatic reporting is enabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
The error message (the last 3 lines) keep repeating ad infinitum until I manually remove the crash files in /var/crash as Rocky notes in https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/comments/13. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when
[Touch-packages] [Bug 1846334] Re: cupsd assert failure: free(): invalid pointer
It seems to be the third time I encounter this bug in a week... -- 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/1846334 Title: cupsd assert failure: free(): invalid pointer Status in cups package in Ubuntu: Confirmed Bug description: Just running in the background, no user action (printing) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: free(): invalid pointer Date: Tue Oct 1 19:41:35 2019 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-09 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: letter PpdFiles: HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at malloc.c:5332 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872015] [NEW] resolv.conf symlink is broken
Public bug reported: see description here: https://askubuntu.com/a/1041631/436647 *The Default* $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 39 Apr 26 12:07 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf I deleted this and pointed to the correct file. After rebooting, this solved my issue. And I was even able to switch networks on my laptop and the DNS switched correctly. Of course when on external networks I can't resolve any of my local machines but that is expected. As soon as I switch back to my local network, all the local machines resolve correctly because my router is the DNS. - *The Fix* $ sudo rm -f /etc/resolv.conf $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 32 May 29 08:48 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf $ sudo reboot ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Apr 10 07:04:17 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP ProLiant MicroServer Gen8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=2351ab04-e595-4761-ad9d-d2d5975d1b08 ro maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2014 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ06:bd06/06/2014:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP mtime.conffile..etc.systemd.resolved.conf: 2020-04-10T06:39:38.172640 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan uec-images -- 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/1872015 Title: resolv.conf symlink is broken Status in systemd package in Ubuntu: New Bug description: see description here: https://askubuntu.com/a/1041631/436647 *The Default* $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 39 Apr 26 12:07 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf I deleted this and pointed to the correct file. After rebooting, this solved my issue. And I was even able to switch networks on my laptop and the DNS switched correctly. Of course when on external networks I can't resolve any of my local machines but that is expected. As soon as I switch back to my local network, all the local machines resolve correctly because my router is the DNS. - *The Fix* $ sudo rm -f /etc/resolv.conf $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 32 May 29 08:48 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf $ sudo reboot ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Apr 10 07:04:17 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP ProLiant MicroServer Gen8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=2351ab04-e595-4761-ad9d-d2d5975d1b08 ro maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2014 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ06:bd06/06/2014:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP mtime.conffile..etc.systemd.resolved.conf: 2020-04-10T06:39:38.172640 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1872015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869913] Re: "Click or press a key to unlock" string not translated into french
@seb128 does it also fix lockscreen date format? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-fr in Ubuntu. https://bugs.launchpad.net/bugs/1869913 Title: "Click or press a key to unlock" string not translated into french Status in language-pack-gnome-fr package in Ubuntu: Fix Committed Bug description: On the lockscreen, the "Click or press a key to unlock" string is not translated, at least in french. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 14:56:11 2020 InstallationDate: Installed on 2019-02-21 (404 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-fr/+bug/1869913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
Successfully tested on eoan. I enabled the proposed repository, upgraded everything (so including pulseaudio 13.0-1ubuntu1.1) then rebooted. The audio device is no longer switched to HDMI when the screen wake up after standby or when login-out and in. (note that the workaround from the description was not applied, so no possible confusion here) So this is all good from my point of view. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
@vanvugt: I booted the latest 20.04 daily (which does contain the new pulseaudio package) and I confirm the behaviour is now back to "normal", which is to say to the 19.04 (and older) behaviour. So this is indeed fixed on Focal in my point of view. -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Fix Released Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. --- WORKAROUND Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840577] Re: package linux-image-3.13.0-170-generic 3.13.0-170.220 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Hi, I tried to upgrade my deprecated system ... I double check to understand : a lot of old kernels full the too tiny boot partition, because of that, upgrade processing stops, and grub was broken after that ... I recover a disk backup and retry after removing all old kernels, it should be ok (I just upgrade other deprecated system from 12.04 to 16.04 this week.) Thanks -- 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/1840577 Title: package linux-image-3.13.0-170-generic 3.13.0-170.220 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: Error while executing do-release-upgrade on an old Ubuntu 12.04 LTS (to Ubuntu 14.04 LTS) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-170-generic 3.13.0-170.220 ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33 Uname: Linux 3.5.0-54-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', '/dev/dsp1', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Sun Aug 18 14:29:43 2019 DuplicateSignature: package:linux-image-3.13.0-170-generic:3.13.0-170.220:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=11052198-9e4e-4724-aa4b-412975fc8ad8 InstallationDate: Installed on 2013-03-12 (2349 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release i386 (20130214) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProcFB: 0 psbfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-54-generic root=/dev/mapper/dedale-root ro RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-3.13.0-170-generic 3.13.0-170.220 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to trusty on 2019-08-18 (0 days ago) dmi.bios.date: 11/01/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: MUCDT10N.86A.0073.2012.1101.1638 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D2500HN dmi.board.vendor: Intel Corporation dmi.board.version: AAG81480-500 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrMUCDT10N.86A.0073.2012.1101.1638:bd11/01/2012:svn:pn:pvr:rvnIntelCorporation:rnD2500HN:rvrAAG81480-500:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1840577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840577] [NEW] package linux-image-3.13.0-170-generic 3.13.0-170.220 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Error while executing do-release-upgrade on an old Ubuntu 12.04 LTS (to Ubuntu 14.04 LTS) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-170-generic 3.13.0-170.220 ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33 Uname: Linux 3.5.0-54-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', '/dev/dsp1', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Sun Aug 18 14:29:43 2019 DuplicateSignature: package:linux-image-3.13.0-170-generic:3.13.0-170.220:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=11052198-9e4e-4724-aa4b-412975fc8ad8 InstallationDate: Installed on 2013-03-12 (2349 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release i386 (20130214) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ProcFB: 0 psbfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-54-generic root=/dev/mapper/dedale-root ro RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-3.13.0-170-generic 3.13.0-170.220 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to trusty on 2019-08-18 (0 days ago) dmi.bios.date: 11/01/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: MUCDT10N.86A.0073.2012.1101.1638 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D2500HN dmi.board.vendor: Intel Corporation dmi.board.version: AAG81480-500 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrMUCDT10N.86A.0073.2012.1101.1638:bd11/01/2012:svn:pn:pvr:rvnIntelCorporation:rnD2500HN:rvrAAG81480-500:cvn:ct3:cvr: ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package dist-upgrade i386 trusty -- 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/1840577 Title: package linux-image-3.13.0-170-generic 3.13.0-170.220 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Error while executing do-release-upgrade on an old Ubuntu 12.04 LTS (to Ubuntu 14.04 LTS) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-170-generic 3.13.0-170.220 ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33 Uname: Linux 3.5.0-54-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', '/dev/dsp1', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Sun Aug 18 14:29:43 2019 DuplicateSignature: package:linux-image-3.13.0-170-generic:3.13.0-170.220:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=11052198-9e4e-4724-aa4b-412975fc8ad8 InstallationDate: Installed on 2013-03-12 (2349 days ago) InstallationMedia:
[Touch-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
root@ubuntu1604:~# dpkg --list | grep iproute2
ii iproute2 4.3.0-1ubuntu3.16.04.4
amd64networking and traffic control tools
root@ubuntu1604:~# apt-get install iproute2/xenial-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '4.3.0-1ubuntu3.16.04.5' (Ubuntu:16.04/xenial-proposed
[amd64]) for 'iproute2'
Suggested packages:
iproute2-doc
The following packages will be upgraded:
iproute2
1 upgraded, 0 newly installed, 0 to remove and 38 not upgraded.
Need to get 523 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 iproute2
amd64 4.3.0-1ubuntu3.16.04.5 [523 kB]
Fetched 523 kB in 0s (6,782 kB/s)
(Reading database ... 85262 files and directories currently installed.)
Preparing to unpack .../iproute2_4.3.0-1ubuntu3.16.04.5_amd64.deb ...
Unpacking iproute2 (4.3.0-1ubuntu3.16.04.5) over (4.3.0-1ubuntu3.16.04.4) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up iproute2 (4.3.0-1ubuntu3.16.04.5) ...
root@ubuntu1604:~# dpkg --list | grep iproute2
ii iproute2 4.3.0-1ubuntu3.16.04.5
amd64networking and traffic control tools
root@ubuntu1604:~# ip link add dev dummy0 type dummy
RTNETLINK answers: File exists
root@ubuntu1604:~# ip link add dev dummy1 type dummy
root@ubuntu1604:~# ip link set dev dummy0 up
root@ubuntu1604:~# ip link set dev dummy1 up
root@ubuntu1604:~# tc qdisc add dev dummy0 handle 1: root prio
root@ubuntu1604:~# tc filter add dev dummy0 parent 1: matchall skip_hw action
mirred egress mirror dev dummy1
root@ubuntu1604:~# tc filter show dev dummy0
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1
root@ubuntu1604:~#
=> test is OK.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Bug description:
[SRU Justification]
== Impact ==
The Xenial 4.4 kernel already has a patch applied which implements the
matchall filter. But in order to actually use it, iproute2 needs to pick up the
user-space
side of the implementation.
== Fix ==
Backported a patch from iproute2 upstream which adds the missing support.
Tested against the standard 4.4 and the HWE kernel in 16.04 (see testcase).
== Risk of Regression ==
This adds a new filter type which has to be actively selected. This should
not impact existing uses. So low.
== Testcase ==
ip link add dev dummy0 type dummy
ip link add dev dummy1 type dummy
ip link set dev dummy0 up
ip link set dev dummy1 up
tc qdisc add dev dummy0 handle 1: root prio
tc filter add dev dummy0 parent 1: matchall skip_hw action mirred egress
mirror dev dummy1
at this point, "tc filter show dev dummy0" should spit out something
like:
filter parent 1: protocol all pref 49152 matchall
filter parent 1: protocol all pref 49152 matchall handle 0x1
action order 1: mirred (Egress Mirror to device dummy1) pipe
index 1 ref 1 bind 1
and the functionality can be tested via
tcpdump -n -i dummy1 &
ping -I dummy0 1.2.3.4
---
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777415] Re: Local authorization bypass by using suspend mode
> Jonathan Polak (jpolak) wrote on 2018-07-09: > I confirm it affects Mate 18.04 as well. > > Moreover, a new bug on mate 18.04, plugging in an HDMI screen upon receiving > the lockscreen, > sometimes allows you to bypass it completely. I know this bug since years. When setting my Thinkpad on the Dockingstation while it was sleeping it sometimes happens that the gnome-shell just starts without asking for a password. And I don't even have to extract the harddisk. I remember some guys of the ubuntu community told me years ago that's a known issue with Xorg and gnome- shell. I did not file a bug or was looking for a known bug because it happened very seldom but the bug persisted many years and I don't know if it was fixed until now for sure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1777415 Title: Local authorization bypass by using suspend mode Status in Unity: New Status in pam package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Version: Ubuntu 16.04.04 LTS Desktop, all packets are updated at 15.06.2018 Affects: access to latest user opened applications, that can contain sensitive information (documents, private information, passwords, etc.) How to reproduce: 1. open some applications (LibreOffice, browsers, editors, ...) 2. go to suspend mode 3. extract hard drive 4. wake up 5. after that can be several behaviors: * Ubuntu show lock screen. Enter ANY password -> access granted. * Ubuntu show lock screen. Enter ANY password, access denied. Fast press the hardware shutdown button -> access granted. * Ubuntu does not show lock screen, only black screen. We can repeat actions like in previous paragraphs To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1777415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
> Note that the iproute2 patch will be needed to use this filter:
>
> https://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=d5cbf3ff0561
> (embedded headers must be updated also).
This link is dead, here is another one:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=d5cbf3ff0561
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
New
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
New
Status in linux source package in Xenial:
Fix Released
Bug description:
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771783] Re: iproute2: frr route protocols are not converted to string on xenial
It works on my side:
$ ./ip/ip r a 2.2.2.0/24 via 10.0.2.123 dev mgmt0 proto 188 metric 20
$ ./ip/ip r | grep 2.2.2
2.2.2.0/24 via 10.0.2.123 dev mgmt0 proto 188 metric 20
$ mkdir -p /etc/iproute2/rt_protos.d
$ echo "188 foo" > /etc/iproute2/rt_protos.d/bar.conf
$ ./ip/ip r | grep 2.2.2
2.2.2.0/24 via 10.0.2.123 dev mgmt0 proto foo metric 20
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1771783
Title:
iproute2: frr route protocols are not converted to string on xenial
Status in iproute2 package in Ubuntu:
New
Bug description:
FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20
iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos
A patch has been pushed upstream so that external applications can define
their protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795808] [NEW] Xorg freeze
Public bug reported: Hi, Since the installation of Ubuntu 18.10, I get the login screen but once logged in I get a black screen. It happens only with the proprietary nvidia driver 390. If I remove the nvidia driver to use nouveau, it works. My graphic card is: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] So the automatic report in attachement will show you no nvidia driver installed. It's because I am doing this bug report after removing the nvidia driver to be able to get a desktop. In attachement I add the journalctl of the preview boot which failed with nvidia driver. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 3 09:19:03 2018 DistUpgraded: 2018-10-03 00:59:01,660 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-36-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070 Ti] [1043:8620] InstallationDate: Installed on 2017-09-17 (380 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-8-generic root=UUID=567a9b2b-0864-450e-9cfe-dab7a54b9fce ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to cosmic on 2018-10-02 (0 days ago) dmi.bios.date: 09/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd09/28/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Wed Oct 3 09:03:39 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze third-party-packages ubuntu ** Attachment added: "journalctl.failed_screen_nvidia.log" https://bugs.launchpad.net/bugs/1795808/+attachment/5196411/+files/journalctl.failed_screen_nvidia.log -- 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/1795808 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Hi, Since the installation of Ubuntu 18.10, I get the login screen but once logged in I get a black screen. It happens only with the proprietary nvidia driver 390. If I remove the nvidia driver to use nouveau, it works. My graphic card is: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] So the automatic report in attachement will show you no nvidia driver installed. It's because I am doing this bug report after removing the nvidia driver to be able to get a desktop. In attachement I add the journalctl of the preview boot which failed with nvidia driver. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic
[Touch-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial
I tested the patch, it works.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1771764
Title:
iproute2: unable to add ip lwt mpls route on xenial
Status in iproute2 package in Ubuntu:
Triaged
Bug description:
The following command does not work:
$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"
In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103
=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4
With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2
At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790242] Re: Converting PDF to PS with pdftocairo results in wrong character spacing with some Adobe fonts
** Attachment added: "PS conversion using pdftocairo" https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1790242/+attachment/5183831/+files/testcase-pdftocairo.ps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1790242 Title: Converting PDF to PS with pdftocairo results in wrong character spacing with some Adobe fonts Status in cairo package in Ubuntu: New Bug description: I use pdftocairo as the default renderer in CUPS to print to my HP LaserJet printer. It's the tool that better manages PDF documents with shading and transparency (common in beamer presentations and PDFs generated by cairo). Everything worked fine until I discovered some pages in documents were incorrectly printed. I tried to print a PDF document (produced by pdfTeX) containing the Helvetica-Narrow fonts, and some lines of the document exhibited wrong character spacing. I tried to print the same document using Chrome and the text was printed with correct spacing so the printer wasn't the responsible. After changing the default PDF->PS renderer I discovered the fault was in pdftocairo because any conversion with pdftops and pdf2gs resulted in correct character spacing on my screen. Changing the PS language level did not work. Also, this bug doesn't manifest when pdfTeX uses the URW base 35 fonts instead of the Adobe ones. I am attaching a PDF document that can be converted with pdftocairo, pdftops and pdf2ps with pdftocairo being the only one that looks different at the narrow fonts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1790242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790242] Re: Converting PDF to PS with pdftocairo results in wrong character spacing with some Adobe fonts
** Attachment added: "PS conversion using pdftops" https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1790242/+attachment/5183829/+files/testcase-pdftops.ps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1790242 Title: Converting PDF to PS with pdftocairo results in wrong character spacing with some Adobe fonts Status in cairo package in Ubuntu: New Bug description: I use pdftocairo as the default renderer in CUPS to print to my HP LaserJet printer. It's the tool that better manages PDF documents with shading and transparency (common in beamer presentations and PDFs generated by cairo). Everything worked fine until I discovered some pages in documents were incorrectly printed. I tried to print a PDF document (produced by pdfTeX) containing the Helvetica-Narrow fonts, and some lines of the document exhibited wrong character spacing. I tried to print the same document using Chrome and the text was printed with correct spacing so the printer wasn't the responsible. After changing the default PDF->PS renderer I discovered the fault was in pdftocairo because any conversion with pdftops and pdf2gs resulted in correct character spacing on my screen. Changing the PS language level did not work. Also, this bug doesn't manifest when pdfTeX uses the URW base 35 fonts instead of the Adobe ones. I am attaching a PDF document that can be converted with pdftocairo, pdftops and pdf2ps with pdftocairo being the only one that looks different at the narrow fonts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1790242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790242] Re: Converting PDF to PS with pdftocairo results in wrong character spacing with some Adobe fonts
** Attachment added: "PS conversion using pdf2ps (Ghostscript)" https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1790242/+attachment/5183830/+files/testcase-gs.ps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1790242 Title: Converting PDF to PS with pdftocairo results in wrong character spacing with some Adobe fonts Status in cairo package in Ubuntu: New Bug description: I use pdftocairo as the default renderer in CUPS to print to my HP LaserJet printer. It's the tool that better manages PDF documents with shading and transparency (common in beamer presentations and PDFs generated by cairo). Everything worked fine until I discovered some pages in documents were incorrectly printed. I tried to print a PDF document (produced by pdfTeX) containing the Helvetica-Narrow fonts, and some lines of the document exhibited wrong character spacing. I tried to print the same document using Chrome and the text was printed with correct spacing so the printer wasn't the responsible. After changing the default PDF->PS renderer I discovered the fault was in pdftocairo because any conversion with pdftops and pdf2gs resulted in correct character spacing on my screen. Changing the PS language level did not work. Also, this bug doesn't manifest when pdfTeX uses the URW base 35 fonts instead of the Adobe ones. I am attaching a PDF document that can be converted with pdftocairo, pdftops and pdf2ps with pdftocairo being the only one that looks different at the narrow fonts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1790242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790242] [NEW] Converting PDF to PS with pdftocairo results in wrong character spacing with some Adobe fonts
Public bug reported: I use pdftocairo as the default renderer in CUPS to print to my HP LaserJet printer. It's the tool that better manages PDF documents with shading and transparency (common in beamer presentations and PDFs generated by cairo). Everything worked fine until I discovered some pages in documents were incorrectly printed. I tried to print a PDF document (produced by pdfTeX) containing the Helvetica-Narrow fonts, and some lines of the document exhibited wrong character spacing. I tried to print the same document using Chrome and the text was printed with correct spacing so the printer wasn't the responsible. After changing the default PDF->PS renderer I discovered the fault was in pdftocairo because any conversion with pdftops and pdf2gs resulted in correct character spacing on my screen. Changing the PS language level did not work. Also, this bug doesn't manifest when pdfTeX uses the URW base 35 fonts instead of the Adobe ones. I am attaching a PDF document that can be converted with pdftocairo, pdftops and pdf2ps with pdftocairo being the only one that looks different at the narrow fonts. ** Affects: cairo (Ubuntu) Importance: Undecided Status: New ** Attachment added: "PDF test case." https://bugs.launchpad.net/bugs/1790242/+attachment/5183198/+files/testcase.pdf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1790242 Title: Converting PDF to PS with pdftocairo results in wrong character spacing with some Adobe fonts Status in cairo package in Ubuntu: New Bug description: I use pdftocairo as the default renderer in CUPS to print to my HP LaserJet printer. It's the tool that better manages PDF documents with shading and transparency (common in beamer presentations and PDFs generated by cairo). Everything worked fine until I discovered some pages in documents were incorrectly printed. I tried to print a PDF document (produced by pdfTeX) containing the Helvetica-Narrow fonts, and some lines of the document exhibited wrong character spacing. I tried to print the same document using Chrome and the text was printed with correct spacing so the printer wasn't the responsible. After changing the default PDF->PS renderer I discovered the fault was in pdftocairo because any conversion with pdftops and pdf2gs resulted in correct character spacing on my screen. Changing the PS language level did not work. Also, this bug doesn't manifest when pdfTeX uses the URW base 35 fonts instead of the Adobe ones. I am attaching a PDF document that can be converted with pdftocairo, pdftops and pdf2ps with pdftocairo being the only one that looks different at the narrow fonts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1790242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780303] [NEW] can't maximise in one monitor
Public bug reported: I have a dual monitor setup. Sometimes, when I log back in from the lock screen (I mean the session is already running), one of the screens does something quite strange. When I try maximise a window, it only uses a small part of the screen's width, as you can see here https://ibb.co/epueGd I also can't drag the right border of a window to make it bigger. The left border works fine. The only solution I've found is to go to system settings-> displays, disable on of the monitors, and then enabling it again. Logging out and back in, doesn't help. I suppose it is an xorg related bug, sorry if it's not. information: 1) Description: Ubuntu 16.04.4 LTS Release:16.04 2) xorg: Installed: 1:7.7+13ubuntu3 Candidate: 1:7.7+13ubuntu3 Version table: *** 1:7.7+13ubuntu3 500 500 http://ar.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) Expected: window is maximised normally. 4) What happens: It only uses a portion of the width. PS: Here's the screenshot again, in case the other one fails. https://photos.app.goo.gl/sdh37ktA8nCAHAum6 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jul 5 13:16:07 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:307b] InstallationDate: Installed on 2018-05-18 (48 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: LENOVO 1782A2Y ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic root=UUID=5cac15b6-1f9d-412c-ab2c-2f9318328d66 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 9PKT26AUS dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: LENOVO dmi.board.version: 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:bvnLENOVO:bvr9PKT26AUS:bd08/23/2011:svnLENOVO:pn1782A2Y:pvrThinkCentreM71z:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 1782A2Y dmi.product.version: ThinkCentre M71z dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jun 29 00:13:48 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputIntegrated Camera: Integrated C KEYBOARD, id 8 inputLenovo Optical USB Mouse MOUSE, id 9 inputCHICONY USB NetVista Full Width Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial ** Attachment added: "bug.jpg" https://bugs.launchpad.net/bugs/1780303/+attachment/5160125/+files/bug.jpg ** Description changed: - I have a dual monitor setup. Sometimes, when I log back in from the lock screen (I mean the session is already running), one of the screens does something quite strange. When I try maximise, it only uses a small part of the screen, as you can see here https://ibb.co/epueGd - I also can't drag the right border of a window to make it bigger. The left border works fine. The only solution I've found is to go to system settings-> displays, disable on of
[Touch-packages] [Bug 1777634] Re: no more than 1 GATT descriptor allowed
** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1777634 Title: no more than 1 GATT descriptor allowed Status in bluez package in Ubuntu: Invalid Bug description: By running the example-gatt-server and example-gatt-advertising, it was impossible to get more than one Descriptor per characteristic. if i comment one i can see the other in the test characteristic. but if i set both, it just act like no descriptor available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777634] Re: no more than 1 GATT descriptor allowed
hum i fell bad about this one... in communication there is to part and apparently it was a bug from the other part. My bad and thanks fr your time. Nicolas. -- 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/1777634 Title: no more than 1 GATT descriptor allowed Status in bluez package in Ubuntu: Incomplete Bug description: By running the example-gatt-server and example-gatt-advertising, it was impossible to get more than one Descriptor per characteristic. if i comment one i can see the other in the test characteristic. but if i set both, it just act like no descriptor available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777634] [NEW] no more than 1 GATT descriptor allowed
Public bug reported: By running the example-gatt-server and example-gatt-advertising, it was impossible to get more than one Descriptor per characteristic. if i comment one i can see the other in the test characteristic. but if i set both, it just act like no descriptor available. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: gatt server -- 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/1777634 Title: no more than 1 GATT descriptor allowed Status in bluez package in Ubuntu: New Bug description: By running the example-gatt-server and example-gatt-advertising, it was impossible to get more than one Descriptor per characteristic. if i comment one i can see the other in the test characteristic. but if i set both, it just act like no descriptor available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1777634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774151] [NEW] Xorg crashed with SIGABRT in RSetChanged()
Public bug reported: I guess it happens because I made and update of my nvidia drivers using apt-get dist-upgrade while gnome was up and running. Because during the update gnome freezes and restarts itself after a while. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.130 Wed Mar 21 03:37:26 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed May 30 10:34:15 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5] NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5] InstallationDate: Installed on 2014-04-18 (1502 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: LENOVO 24474GG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=b44fee51-1765-4794-b840-a8e5272c94c7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 24474GG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET95WW(2.55):bd09/13/2013:svnLENOVO:pn24474GG:pvrThinkPadW530:rvnLENOVO:rn24474GG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24474GG dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed May 30 10:11:32 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1774151 Title: Xorg crashed with SIGABRT in RSetChanged() Status in xorg package in Ubuntu: New Bug description: I guess it happens because I made and update of my nvidia drivers using apt-get dist-upgrade while gnome was up and running. Because during the update gnome freezes and restarts itself after a while. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.130 Wed Mar 21 03:37:26 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed May 30 10:34:15 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu
[Touch-packages] [Bug 1642514] Re: sched: Match-all classifier is missing in xenial
Any news for the iproute2 part?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1642514
Title:
sched: Match-all classifier is missing in xenial
Status in iproute2 package in Ubuntu:
New
Status in linux package in Ubuntu:
Fix Released
Status in iproute2 source package in Xenial:
New
Status in linux source package in Xenial:
Fix Released
Bug description:
This is implemented in linux v4.8 by the following upstream patch:
bf3994d2ed31 ("net/sched: introduce Match-all classifier")
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bf3994d2ed31
The backport is straightforward. It's useful in combination with
clsact qdisc (see bug #1642510).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1642514/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial
** Package changed: linux (Ubuntu) => iproute2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1771764
Title:
iproute2: unable to add ip lwt mpls route on xenial
Status in iproute2 package in Ubuntu:
Incomplete
Bug description:
The following command does not work:
$ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
Error: "nexthop" or end of line is expected instead of "encap"
In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
$ ip -V
ip utility, iproute2-ss151103
=>
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4
With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
$ modprobe mpls_iptunnel
$ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev
ntfp2
$ ./ip/ip r
[snip]
10.201.0.0/24 encap mpls 300 via 10.200.0.1 dev ntfp2
At least, this patch is missing:
1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771783] [NEW] iproute2: frr route protocols are not converted to string on xenial
Public bug reported:
FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20
iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos
A patch has been pushed upstream so that external applications can define their
protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619
** Affects: iproute2 (Ubuntu)
Importance: Undecided
Status: New
** Package changed: linux (Ubuntu) => iproute2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1771783
Title:
iproute2: frr route protocols are not converted to string on xenial
Status in iproute2 package in Ubuntu:
New
Bug description:
FRR puts its own proto numbers when inserting a route, example:
$ ip route
[snip]
2.2.2.0/24 via 3.3.3.2 dev eth2 proto 188 metric 20
iproute2 defines some protocols, but not all:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos
A patch has been pushed upstream so that external applications can define
their protocols numbers:
719e331ff619 ("Add support for rt_protos.d")
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717769] Re: day of week in german despite i configured the system in english
I understood the mecanism (but not the involved code): This problem is easily reproductible: installing a fresh Ubuntu from CD, choosing "English" as the language and the keymap"Belgian", makes everytime the region language in German. ** Attachment added: "screenshot.png" https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1717769/+attachment/5070815/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en in Ubuntu. https://bugs.launchpad.net/bugs/1717769 Title: day of week in german despite i configured the system in english Status in language-pack-en package in Ubuntu: Incomplete Bug description: Description --- I chose the english language and live in Belgium. So I chose Brussels for the Time Zone, and the Belgian keymap. The Ubuntu date & time applet, in the top bar of the Ubuntu desktop interface shows me "Son HH:MM", Son standing for "Sonntag" which is german. I don't get why there is german in my interface since I configured this language nowhere but English. Expected Behavior -- Having the day of week in English. My configuration to reproduce the problem - Here is the region & language configuration as seen in the settings pannel: Language: English (United States) Formats : Belgien Input Sources: Belgian In the "Date & Time" settings: Time Zone: CEST (Brussels, Belgium) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1717769/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752085] [NEW] package cups-core-drivers 2.1.3-4ubuntu0.4 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: la verdad es que incié en el escritorio y me apareció este error, no tengo claro de que se tratrá. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-core-drivers 2.1.3-4ubuntu0.4 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 AptOrdering: sensible-utils: Install sensible-utils: Configure cups-daemon: Configure cups-core-drivers: Configure NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Tue Feb 27 10:03:25 2018 ErrorMessage: problemas de dependencias - se deja sin configurar Lpstat: device for DCP1610W: socket://192.168.1.5 MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 Papersize: letter PpdFiles: DCP1610W: Brother DCP-1610W for CUPS ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=28ecc83e-73d2-4ad1-b998-af13e220885b ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=28ecc83e-73d2-4ad1-b998-af13e220885b ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: cups Title: package cups-core-drivers 2.1.3-4ubuntu0.4 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 12HX.M037.20110616.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 12HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr12HX.M037.20110616.SSH:bd06/16/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr12HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr12HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: RF511/RF411/RF711 dmi.product.version: 12HX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1752085 Title: package cups-core-drivers 2.1.3-4ubuntu0.4 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in cups package in Ubuntu: New Bug description: la verdad es que incié en el escritorio y me apareció este error, no tengo claro de que se tratrá. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-core-drivers 2.1.3-4ubuntu0.4 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 AptOrdering: sensible-utils: Install sensible-utils: Configure cups-daemon: Configure cups-core-drivers: Configure NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Tue Feb 27 10:03:25 2018 ErrorMessage: problemas de dependencias - se deja sin configurar Lpstat: device for DCP1610W: socket://192.168.1.5 MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 Papersize: letter PpdFiles: DCP1610W: Brother DCP-1610W for CUPS ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=28ecc83e-73d2-4ad1-b998-af13e220885b ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=28ecc83e-73d2-4ad1-b998-af13e220885b ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: cups Title: package cups-core-drivers 2.1.3-4ubuntu0.4 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 12HX.M037.20110616.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 12HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr12HX.M037.20110616.SSH:bd06/16/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr12HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr12HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: RF511/RF411/RF711 dmi.product.version: 12HX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go
Re: [Touch-packages] [Bug 1717769] Re: day of week in german despite i configured the system in english
Hi, I don't think it is about a wrongly translated string, but more about the combination of regional choices that makes the langage mecanism choose the locale in german (all my interface is in right english but my calendar and days of weeks in softwares). I guess it is something because of: - in Belgium we have 3 official languages: Dutch, German, French - I chose in my settings english language with Belgium format and Belgian keyboard - so maybe since there is no english locales for belgium, maybe the code is written to go by default for german locales strings What do you think? [image: Screenshot from 2018-01-21 22-24-31.png] Le dim. 15 oct. 2017 à 01:05, Anthony Harrington <1717...@bugs.launchpad.net> a écrit : > Hi Nicolas, thanks for the bug report. > > On quick inspection, I can't see why this is happening. > Occasionally, native german speakers will accidentally translate strings > that are supposed to be under 'english (US/GB/CA/AU)' into German, however, > as this affects English US (the default language that is taken as-is > without any intervention from translators on launchpad's side - i.e. as the > developers originally wrote the strings), English US should be ok. I also > can't see anything in indicator-datetime that has been accidentally > uploaded in German to begin with? > > Are you missing any required locale packages? > If it's not accepting English US for some strange reason, could you try > uninstalling any German locale packages (language-pack-de and > language-pack-de-base) (perhaps also language-pack-gnome-de and > language-pack-gnome-de-base to be safe) and be sure you have the "en" > equivalents. > Not sure why it isn't configuring the language properly. > > Failing that, what happens if you switch your language to English UK? I > can personally vouch for English UK being fine as our team gets every > single string finished for the next ubuntu release, so everything's been > checked over (almost certainly by yours truly ;) ) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1717769 > > Title: > day of week in german despite i configured the system in english > > Status in language-pack-en package in Ubuntu: > New > > Bug description: > Description > --- > I chose the english language and live in Belgium. So I chose Brussels > for the Time Zone, and the Belgian keymap. > > The Ubuntu date & time applet, in the top bar of the Ubuntu desktop > interface shows me "Son HH:MM", Son standing for "Sonntag" which is > german. I don't get why there is german in my interface since I > configured this language nowhere but English. > > Expected Behavior > -- > Having the day of week in English. > > My configuration to reproduce the problem > - > Here is the region & language configuration as seen in the settings > pannel: > Language: English (United States) > Formats : Belgien > Input Sources: Belgian > > In the "Date & Time" settings: > Time Zone: CEST (Brussels, Belgium) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1717769/+subscriptions > ** Attachment added: "Screenshot from 2018-01-21 22-24-31.png" https://bugs.launchpad.net/bugs/1717769/+attachment/5040685/+files/Screenshot%20from%202018-01-21%2022-24-31.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en in Ubuntu. https://bugs.launchpad.net/bugs/1717769 Title: day of week in german despite i configured the system in english Status in language-pack-en package in Ubuntu: Incomplete Bug description: Description --- I chose the english language and live in Belgium. So I chose Brussels for the Time Zone, and the Belgian keymap. The Ubuntu date & time applet, in the top bar of the Ubuntu desktop interface shows me "Son HH:MM", Son standing for "Sonntag" which is german. I don't get why there is german in my interface since I configured this language nowhere but English. Expected Behavior -- Having the day of week in English. My configuration to reproduce the problem - Here is the region & language configuration as seen in the settings pannel: Language: English (United States) Formats : Belgien Input Sources: Belgian In the "Date & Time" settings: Time Zone: CEST (Brussels, Belgium) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1717769/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725455] Re: Login screen invisible / UI hanging when both 4K monitors connected via Displayport MST (docking station)
** Summary changed: - UI login invisible / UI hanging when Dual 4K monitor via Displayport MST is connected (Lenovo Ultra Dock) + Login screen invisible / UI hanging when both 4K monitors connected via Displayport MST (docking station) -- 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/1725455 Title: Login screen invisible / UI hanging when both 4K monitors connected via Displayport MST (docking station) Status in xorg package in Ubuntu: New Bug description: I am experiencing serious issues after upgrading to Ubuntu 17.10 (coming from 17.04 with Gnome, kernel 4.13). I have 2 x 4K (Asus PB279Q) monitors, connected to a Lenovo Ultra Dock (containing 2 x Displayport via MST), where the Lenovo T550 is connected onto it. Both monitors were working perfectly fine at 30Hz simultaneously in an extended desktop, 4K resolution in my old setup with Gnome for over half a year (since kernel 4.10 blink issues on 4K were solved, i used this setup since then). However after upgrading to 17.10 using the new Gnome interface: When the laptop is connected to the Lenovo Ultra Dock (to work on both monitors), the system is hanging and becoming unresponsive. The mouse pointer is freezing and the only way is to do a hard-reboot. I have checked the monitor settings, it's displayed at 60Hz when active, and it appears I am never able to use both monitors simultaneously. When I get 1 monitor working (disconnecting the 2nd monitor from the MST port), after rebooting it works fine. I tried to put settings of the 4K manually on 30Hz, reconnecting, but the system hangs again. I have tried several combinations. It results in a blank (purple) screen and hanging mouse (see attachment). I tried also with the installation-iso to run a fresh 17.10 and tried the same, the symptoms are similar. I suspect that must be an issue with the Displayport MST on dual 4K setups in the new 17.10. When I connect 1 x 4K monitor to the rear displayport of the Lenovo Ultra Dock (there are 2 for MST on the rear, so I disconnected the other) *and* when I connect the other 4K monitor on the separate displayport of the T550 itself instead, it works 100% fine! Shortly: based on my knowledge that must definitely be some issue with the MST displayport functionality itself, that is unable to recognize/identify both 4K monitors when connected to the dock's both displayport connections? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.13.4-041304-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 21:10:50 2017 DistUpgraded: 2017-10-19 21:54:53,162 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2225] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:2225] InstallationDate: Installed on 2017-04-16 (186 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.4-041304-generic root=UUID=9fcc7f4c-35c0-4297-9c98-4dac9acee798 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CKCTO1WW dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
[Touch-packages] [Bug 1725455] Re: UI login invisible / UI hanging when Dual 4K monitor via Displayport MST is connected (Lenovo Ultra Dock)
Update: I did a full 17.10 reinstall as last attempt. I can confirm the following symptoms: - When both 4k displays are connected to the docking (displayport MST), UI login screen is already hanging (see earlier screenshot) - When 1 x 4K display is connected it works. When connecting 2nd display after login (using Wayland), the UI is completely hanging ** Summary changed: - Dual 4K monitor via Displayport MST not working (Lenovo Ultra Dock) + UI login invisible / UI hanging when Dual 4K monitor via Displayport MST is connected (Lenovo Ultra Dock) -- 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/1725455 Title: UI login invisible / UI hanging when Dual 4K monitor via Displayport MST is connected (Lenovo Ultra Dock) Status in xorg package in Ubuntu: New Bug description: I am experiencing serious issues after upgrading to Ubuntu 17.10 (coming from 17.04 with Gnome, kernel 4.13). I have 2 x 4K (Asus PB279Q) monitors, connected to a Lenovo Ultra Dock (containing 2 x Displayport via MST), where the Lenovo T550 is connected onto it. Both monitors were working perfectly fine at 30Hz simultaneously in an extended desktop, 4K resolution in my old setup with Gnome for over half a year (since kernel 4.10 blink issues on 4K were solved, i used this setup since then). However after upgrading to 17.10 using the new Gnome interface: When the laptop is connected to the Lenovo Ultra Dock (to work on both monitors), the system is hanging and becoming unresponsive. The mouse pointer is freezing and the only way is to do a hard-reboot. I have checked the monitor settings, it's displayed at 60Hz when active, and it appears I am never able to use both monitors simultaneously. When I get 1 monitor working (disconnecting the 2nd monitor from the MST port), after rebooting it works fine. I tried to put settings of the 4K manually on 30Hz, reconnecting, but the system hangs again. I have tried several combinations. It results in a blank (purple) screen and hanging mouse (see attachment). I tried also with the installation-iso to run a fresh 17.10 and tried the same, the symptoms are similar. I suspect that must be an issue with the Displayport MST on dual 4K setups in the new 17.10. When I connect 1 x 4K monitor to the rear displayport of the Lenovo Ultra Dock (there are 2 for MST on the rear, so I disconnected the other) *and* when I connect the other 4K monitor on the separate displayport of the T550 itself instead, it works 100% fine! Shortly: based on my knowledge that must definitely be some issue with the MST displayport functionality itself, that is unable to recognize/identify both 4K monitors when connected to the dock's both displayport connections? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.13.4-041304-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 21:10:50 2017 DistUpgraded: 2017-10-19 21:54:53,162 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2225] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:2225] InstallationDate: Installed on 2017-04-16 (186 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.4-041304-generic root=UUID=9fcc7f4c-35c0-4297-9c98-4dac9acee798 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CKCTO1WW dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core
[Touch-packages] [Bug 1725455] Re: Dual 4K monitor via Displayport MST not working (Lenovo Ultra Dock)
** Tags added: displayport multimonitor -- 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/1725455 Title: Dual 4K monitor via Displayport MST not working (Lenovo Ultra Dock) Status in xorg package in Ubuntu: New Bug description: I am experiencing serious issues after upgrading to Ubuntu 17.10 (coming from 17.04 with Gnome, kernel 4.13). I have 2 x 4K (Asus PB279Q) monitors, connected to a Lenovo Ultra Dock (containing 2 x Displayport via MST), where the Lenovo T550 is connected onto it. Both monitors were working perfectly fine at 30Hz simultaneously in an extended desktop, 4K resolution in my old setup with Gnome for over half a year (since kernel 4.10 blink issues on 4K were solved, i used this setup since then). However after upgrading to 17.10 using the new Gnome interface: When the laptop is connected to the Lenovo Ultra Dock (to work on both monitors), the system is hanging and becoming unresponsive. The mouse pointer is freezing and the only way is to do a hard-reboot. I have checked the monitor settings, it's displayed at 60Hz when active, and it appears I am never able to use both monitors simultaneously. When I get 1 monitor working (disconnecting the 2nd monitor from the MST port), after rebooting it works fine. I tried to put settings of the 4K manually on 30Hz, reconnecting, but the system hangs again. I have tried several combinations. It results in a blank (purple) screen and hanging mouse (see attachment). I tried also with the installation-iso to run a fresh 17.10 and tried the same, the symptoms are similar. I suspect that must be an issue with the Displayport MST on dual 4K setups in the new 17.10. When I connect 1 x 4K monitor to the rear displayport of the Lenovo Ultra Dock (there are 2 for MST on the rear, so I disconnected the other) *and* when I connect the other 4K monitor on the separate displayport of the T550 itself instead, it works 100% fine! Shortly: based on my knowledge that must definitely be some issue with the MST displayport functionality itself, that is unable to recognize/identify both 4K monitors when connected to the dock's both displayport connections? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.13.4-041304-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 21:10:50 2017 DistUpgraded: 2017-10-19 21:54:53,162 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2225] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:2225] InstallationDate: Installed on 2017-04-16 (186 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.4-041304-generic root=UUID=9fcc7f4c-35c0-4297-9c98-4dac9acee798 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CKCTO1WW dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Apr 17 17:36:46 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset To manage notifications about this bug go to:
[Touch-packages] [Bug 1725949] [NEW] nouveau drivers fails to start a wayland session and fallback to x11
Public bug reported: I have a Nvidia GTX 670. I tried the nouveau driver. At boot, it takes a unusual long time then finally shows me gdm3 and everything is working after. But echo $XDG_SESSION_TYPE is set to "x11". Reading the logs, I can see that after multiple failures to launch wayland, it falls back to X11. I added an attachement of journalctl -b -1 where it fails with nouveau (I'm filling the bug after reinstalling nvidia proprietary driver). lspci -v 01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 670] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 670] Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f600 (32-bit, non-prefetchable) [size=16M] Memory at e800 (64-bit, prefetchable) [size=128M] Memory at f000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: automatic crash report generation. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 11:37:08 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 670] [10de:1189] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 670] [3842:2678] InstallationDate: Installed on 2017-09-17 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=567a9b2b-0864-450e-9cfe-dab7a54b9fce ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd09/28/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Oct 22 11:26:32 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu ** Attachment added: "nouveau-fails-wayland.log"
