[Touch-packages] [Bug 2059418] Re: Bluetooth earbuds not being 'set up' on new machine
Purchased via : https://www.amazon.com/gp/product/B0C3W4MNN1 FCC ID:2A33A-T60 -- 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/2059418 Title: Bluetooth earbuds not being 'set up' on new machine Status in bluez package in Ubuntu: Incomplete Bug description: The problem concerns earbuds 0B:20:24:A3:E7:56 T60 that worked perfectly under completely patched Ubuntu 22.04 on my old machine but now refuse to be setup on a new box running completely patched Ubuntu 22.04 . Other old bluetooth gadgets attached without issue. The end result at the very bottom of this page indicates ‘requestor exited before bonding was completed’ . root@bill:~# bluetoothctl --version bluetoothctl: 5.64 root@bill:~# hciconfig -a hci0: Type: Primary Bus: USB BD Address: BC:C7:46:9D:25:98 ACL MTU: 1021:8 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:11627 acl:0 sco:0 events:466 errors:0 TX bytes:78563 acl:0 sco:0 commands:422 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'bill' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: (0xc) Revision: 0x40d LMP Version: (0xc) Subversion: 0x7225 Manufacturer: Realtek Semiconductor Corporation (93) root@bill:~# bluetoothctl Agent registered [CHG] Controller BC:C7:46:9D:25:98 Pairable: yes [bluetooth]# show Controller BC:C7:46:9D:25:98 (public) Name: bill Alias: bill Class: 0x007c0104 Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink (110b--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer (1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0540 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0a (10) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded [bluetooth]# devices Device 74:45:CE:BA:24:65 WH-CH710N At this point I started the earbuds (T60) having a problem getting set up. [CHG] Controller BC:C7:46:9D:25:98 Discoverable: yes [CHG] Controller BC:C7:46:9D:25:98 Discovering: yes [NEW] Device 34:95:04:4B:07:3C 34-95-04-4B-07-3C [CHG] Device 34:95:04:4B:07:3C RSSI: -86 [NEW] Device 0B:20:24:A3:E7:56 T60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -52 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -64 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7
[Touch-packages] [Bug 2059418] [NEW] Bluetooth earbuds not being 'set up' on new machine
Public bug reported: The problem concerns earbuds 0B:20:24:A3:E7:56 T60 that worked perfectly under completely patched Ubuntu 22.04 on my old machine but now refuse to be setup on a new box running completely patched Ubuntu 22.04 . Other old bluetooth gadgets attached without issue. The end result at the very bottom of this page indicates ‘requestor exited before bonding was completed’ . root@bill:~# bluetoothctl --version bluetoothctl: 5.64 root@bill:~# hciconfig -a hci0: Type: Primary Bus: USB BD Address: BC:C7:46:9D:25:98 ACL MTU: 1021:8 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:11627 acl:0 sco:0 events:466 errors:0 TX bytes:78563 acl:0 sco:0 commands:422 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'bill' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: (0xc) Revision: 0x40d LMP Version: (0xc) Subversion: 0x7225 Manufacturer: Realtek Semiconductor Corporation (93) root@bill:~# bluetoothctl Agent registered [CHG] Controller BC:C7:46:9D:25:98 Pairable: yes [bluetooth]# show Controller BC:C7:46:9D:25:98 (public) Name: bill Alias: bill Class: 0x007c0104 Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink (110b--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer (1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0540 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0a (10) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded [bluetooth]# devices Device 74:45:CE:BA:24:65 WH-CH710N At this point I started the earbuds (T60) having a problem getting set up. [CHG] Controller BC:C7:46:9D:25:98 Discoverable: yes [CHG] Controller BC:C7:46:9D:25:98 Discovering: yes [NEW] Device 34:95:04:4B:07:3C 34-95-04-4B-07-3C [CHG] Device 34:95:04:4B:07:3C RSSI: -86 [NEW] Device 0B:20:24:A3:E7:56 T60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -54 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -52 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -56 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -58 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -64 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -60 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: yes [CHG] Device 0B:20:24:A3:E7:56 RSSI: -48 [CHG] Device 0B:20:24:A3:E7:56 LegacyPairing: no [CHG] Device 0B:20:24:A3:E7:56 RSSI: -50 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -50 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -80 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -72 [CHG] Device 0B:20:24:A3:E7:56 RSSI: -46 [bluetooth]# info 0B:20:24:A3:E7:56 Device 0B:20:24:A3:E7:56 (public) Name: T60 Alias: T60 Class: 0x00240404 Icon: audio-headset Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: no ManufacturerData Key: 0x7262
[Touch-packages] [Bug 2058249] Re: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy
I see it now within `/usr/share/doc/tzdata/changelog.Debian.gz`, that's a file I did not check. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2058249 Title: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy Status in tzdata package in Ubuntu: Invalid Bug description: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058249] Re: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy
Thank you, that certainly resolves the missing files. While I understand the reason behind the switch, I can't find where the "intentional change" is communicated. There is no `apt changelog tzdata`, and nothing else I see gives me a hint that the package was split in that way. While it may not impact everybody like it did me, is there some way to formally communicate this, perhaps within the package description for `tzdata`? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2058249 Title: US symlinks missing in /usr/share/zoneinfo -> now in tzdata-legacy Status in tzdata package in Ubuntu: Invalid Bug description: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058249] [NEW] US symlinks missing in /usr/share/zoneinfo
Public bug reported: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2058249 Title: US symlinks missing in /usr/share/zoneinfo Status in tzdata package in Ubuntu: New Bug description: On 22.04 Jammy with tzdata version 2024a-0ubuntu0.22.04 installed, we have `/usr/share/zoneinfo/US/*` symlinks. On 23.10 Mantic with tzdata version 2024a-0ubuntu0.23.10, we do not. Is this an intentional removal? I don't follow the IANA mailing lists, but I had thought/assumed that "Country/Region" symlinks were being maintained for backward compatibility. Many tools I use reference multiple timezones (regardless of the system TZ), so it is necessary to have them available. As a temporary workaround, we can make the symlinks manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2058249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
I have installed the proposed release and the file /usr/share/zoneinfo/leap-seconds.list expiry date is '28 June 2024'. A future update should be schedule for May. Thanks for the update. Test regressions may be related to this change in 2023a data set. If so test should be updated accordingly. Changes to past timestamps America/Yellowknife has changed from a Zone to a backward compatibility Link, as it no longer differs from America/Edmonton since 1970. (Thanks to Almaz Mingaleev.) This affects some pre-1948 timestamps. The old data are now in 'backzone'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Lunar: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047314] [NEW] leap-second.list expiring this week
Public bug reported: It appears the tzdata package has not been updated with the 2023d timezone data. Current distribution is 2023c. leap-seconds.list is expiring Dec 28th 2023, My fix was to download and extract https://data.iana.org/time- zones/releases/tzdata2023d.tar.gz. Then copy the included leap- seconds.list and leapseconds files to /usr/share/zoneinfo. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2047314 Title: leap-second.list expiring this week Status in tzdata package in Ubuntu: New Bug description: It appears the tzdata package has not been updated with the 2023d timezone data. Current distribution is 2023c. leap-seconds.list is expiring Dec 28th 2023, My fix was to download and extract https://data.iana.org/time- zones/releases/tzdata2023d.tar.gz. Then copy the included leap- seconds.list and leapseconds files to /usr/share/zoneinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039357] [NEW] Bluetooth headphones not detected properly
Public bug reported: On a fresh system boot, stereo Bluetooth headphones with a microphone that identify as WH-CH710N connect but provide no sound until Settings is used to pick the only microphone option, the headphones, whereupon sound immediately works. Thereafter, doing a sound Test reveals the headphones are considered mono, not stereo. Sound works, but periodically the Bluetooth connection halts the browser that's playing the sound and in about 10 seconds, Bluetooth disconnects then reconnects a short time later but with the original sound problem. The issue is with the Bluetooth detection. The symptom is no sound. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1876 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Oct 14 08:38:00 2023 InstallationDate: Installed on 2019-11-18 (1425 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to jammy on 2022-11-01 (346 days ago) dmi.bios.date: 09/21/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd09/21/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2039357 Title: Bluetooth headphones not detected properly Status in alsa-driver package in Ubuntu: New Bug description: On a fresh system boot, stereo Bluetooth headphones with a microphone that identify as WH-CH710N connect but provide no sound until Settings is used to pick the only microphone option, the headphones, whereupon sound immediately works. Thereafter, doing a sound Test reveals the headphones are considered mono, not stereo. Sound works, but periodically the Bluetooth connection halts the browser that's playing the sound and in about 10 seconds, Bluetooth disconnects then reconnects a short time later but with the original sound problem. The issue is with the Bluetooth detection. The symptom is no sound. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-86.96-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bill 1876 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Oct 14 08:38:00 2023 InstallationDate: Installed on 2019-11-18 (1425 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to jammy on 2022-11-01 (346 days ago) dmi.bios.date: 09/21/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd09/21/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/20
[Touch-packages] [Bug 1916931] Re: omshell returns inconsistent results or segfaults
Apologies for the poorly wrapped response. I pulled down the isc-dhcp source package from Kinetic and built it for Jammy. In my initial test showed that this does indeed seem to fix the problem. There was an issue with 'gbp buildpackage' deleting some files in the source repository that caused the initial build to fail: deleted:config.guess deleted:config.sub deleted:keama/tests/samples/example.conf.orig deleted:keama/tests/samples/test-a6.conf.orig deleted:keama/tests/samples/vmnet8.conf.orig I just 'git commit'ed the deletions and the package built successfully. Bill -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults Status in isc-dhcp package in Ubuntu: Expired Bug description: I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail. Here is the initial, working, session: # omshell > server localhost > port 7911 > key omapi_key > connect obj: > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00 Here is what I see when the connect fails. Well, just hangs really. # omshell > server localhost > port 7911 > key omapi_key > connect And then I hit ctrl-c to break out and tried again: # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the peer to this server is still running Ubuntu 18.04 with isc-dhcp-server 4.3.5. Running the exact same commands on the peer works reliably. (They are using the same python script to drive omshell.) The DHCP server on the new system appears to be working just fine as reported by omshell on the peer and systemctl. I was curious if the problem could be with the mis-matched versions of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system and get the same results. I also tried using a python script with the pypureomapi module to try and determine if the problem was in omshell or the server. I got very similar results when I attempted to get information about the failover state of the server. Interestingly interrogating the server about host information seems to work just fine. This is a critical bug since I don't see how to fail over a DHCP that is running the isc-dhcp-server on 20.04 without being able to issue omapi commands. I am attaching apport output to this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916931] Re: omshell returns inconsistent results or segfaults
> Bill, Lukas asked a question in comment #10 and set the bug to 'incomplete', > hoping > to get feedback from someone who could reproduce the problem. If you can > provide an > answer, please do set the bug back to 'confirmed' when answering. I don't agree with Lukas' action. The bug is still valid for Jammy, the LTS version. If Lukas wants to provide a package to test on Jammy I can do that, but setting up a DHCP peer environment in a version of Ubuntu that I don't have a build environment for will take quite a bit of effort. It is particularly onerous because I only use LTS versions of Ubuntu, so even if the Kinetic works it doesn't solve my problem for another 2 years. > Could somebody confirm if this issue is still happening with omshell v4.4.3 > from > the Ubuntu Kinetic package? I suppose there is an alternative. I'll see if I can backport the 4.4.3 version from Kinetic to Jammy. I can confirm that the bug exists in 4.4.1 on Debian 11, Bullseye. Bill -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults Status in isc-dhcp package in Ubuntu: Expired Bug description: I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail. Here is the initial, working, session: # omshell > server localhost > port 7911 > key omapi_key > connect obj: > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00 Here is what I see when the connect fails. Well, just hangs really. # omshell > server localhost > port 7911 > key omapi_key > connect And then I hit ctrl-c to break out and tried again: # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the peer to this server is still running Ubuntu 18.04 with isc-dhcp-server 4.3.5. Running the exact same commands on the peer works reliably. (They are using the same python script to drive omshell.) The DHCP server on the new system appears to be working just fine as reported by omshell on the peer and systemctl. I was curious if the problem could be with the mis-matched versions of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system and get the same results. I also tried using a python script with the pypureomapi module to try and determine if the problem was in omshell or the server. I got very similar results when I attempted to get information about the failover state of the server. Interestingly interrogating the server about host information seems to work just fine. This is a critical bug since I don't see how to fail over a DHCP that is running the isc-dhcp-server on 20.04 without being able to issue omapi commands. I am attaching apport output to this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916931] Re: omshell returns inconsistent results or segfaults
Hmm, why would an unresolved bug be expired? The problem has been confirmed by more than one of us. I just finished tested with 22.04 and can report that the problem persists. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults Status in isc-dhcp package in Ubuntu: Expired Bug description: I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail. Here is the initial, working, session: # omshell > server localhost > port 7911 > key omapi_key > connect obj: > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00 Here is what I see when the connect fails. Well, just hangs really. # omshell > server localhost > port 7911 > key omapi_key > connect And then I hit ctrl-c to break out and tried again: # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the peer to this server is still running Ubuntu 18.04 with isc-dhcp-server 4.3.5. Running the exact same commands on the peer works reliably. (They are using the same python script to drive omshell.) The DHCP server on the new system appears to be working just fine as reported by omshell on the peer and systemctl. I was curious if the problem could be with the mis-matched versions of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system and get the same results. I also tried using a python script with the pypureomapi module to try and determine if the problem was in omshell or the server. I got very similar results when I attempted to get information about the failover state of the server. Interestingly interrogating the server about host information seems to work just fine. This is a critical bug since I don't see how to fail over a DHCP that is running the isc-dhcp-server on 20.04 without being able to issue omapi commands. I am attaching apport output to this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2000024] [NEW] Font alignment/search bar size issue when using scaling factor > 1
Public bug reported: When using 'gsettings set org.gnome.desktop.interface text-scaling- factor' command to set the scaling factor to something greater than 1, the text gets misaligned in the search bar, which seems to be too small (shown in an attachment here). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 18 18:07:13 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3090] [10de:2204] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GA102 [GeForce RTX 3090] [1043:87b3] InstallationDate: Installed on 2022-12-18 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=fc0c0197-bcc1-4eb2-abf4-af87b54ca0e2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2022 dmi.bios.release: 22.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z690-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd11/30/2022:br22.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ690-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu ** Attachment added: "font alignment issue" https://bugs.launchpad.net/bugs/224/+attachment/5636288/+files/Screenshot%20from%202022-12-18%2018-10-45.png -- 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/224 Title: Font alignment/search bar size issue when using scaling factor > 1 Status in xorg package in Ubuntu: New Bug description: When using 'gsettings set org.gnome.desktop.interface text-scaling- factor' command to set the scaling factor to something greater than 1, the text gets misaligned in the search bar, which seems to be too small (shown in an attachment here). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission
[Touch-packages] [Bug 1999320] [NEW] Font alignment issue when using scaling factor > 1
Public bug reported: When I use a desktop interface text scaling factor of 1.5, the alignment text in the applications menu search bar is not set properly I have attached a screenshot showing the issue. 1) Description:Ubuntu 22.04.1 LTS Release:22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) text was centered 4) it is not centered ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2022-12-11 01-10-12.png" https://bugs.launchpad.net/bugs/1999320/+attachment/5635299/+files/Screenshot%20from%202022-12-11%2001-10-12.png -- 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/1999320 Title: Font alignment issue when using scaling factor > 1 Status in xorg package in Ubuntu: New Bug description: When I use a desktop interface text scaling factor of 1.5, the alignment text in the applications menu search bar is not set properly I have attached a screenshot showing the issue. 1) Description: Ubuntu 22.04.1 LTS Release: 22.04 2) xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) text was centered 4) it is not centered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1999320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987573] Re: /home on btrfs subvolume shared with / stops boot; adding nofail to fstab fixes it
The `journalctl -xb` output is attached. The error is noted at time "Aug 29 11:12:19". I had to press Ctrl-D at the right moment during boot so that I could get this output. For clarity, I removed the "nofail" to get this error again, and it is reproducible by adding/removing "nofail". ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1987573/+attachment/5612388/+files/journalctl.txt -- 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/1987573 Title: /home on btrfs subvolume shared with / stops boot; adding nofail to fstab fixes it Status in systemd package in Ubuntu: Incomplete Bug description: After performing `do-release-upgrade` from 20.04 to 22.04.01, the system failed to boot with a message of: Failed to mount /home Dependency failed for Local File Systems. It took some work to figure out, but adding "nofail" to the fstab line allowed boot to proceed, and with that, the system appears to be working without issue. Both /boot and /home are mounted from subvolumes on the same btrfs filesystem. The working fstab is below: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # LABEL=Root / btrfs defaults,subvol=@ 0 1 LABEL=Root /home btrfs defaults,subvol=@home,nofail 0 2 LABEL=EscherBackup /mnt/EscherBackup btrfs defaults0 2 LABEL=PicassoBackup /mnt/PicassoBackup btrfs defaults0 2 LABEL=scratch /mnt/scratchbtrfs defaults0 2 /dev/mapper/cryptswap1 none swap sw 0 0 /dev/mapper/cryptswap2 none swap sw 0 0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.13 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Wed Aug 24 20:16:42 2022 EcryptfsInUse: Yes PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-08-24 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1987573/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987665] Re: The "Settings" app is missing the 'Appearance' option
I tried to use ubuntu-bug to report the lock up of chrome during the ubuntu-bug reporting process but ubuntu-bug won't allow a report on ubuntu-bug itself. bill@bill ~$ ubuntu-bug ubuntu-bug dpkg-query: no packages found matching ubuntu-bug FYI - When I attempted to report the bug this page is about the first time, the ubuntu-bug output on the terminal showed the following if that's any help: bill@bill ~$ ubuntu-bug ubuntu-settings bill@bill ~$ [75943:75943:0825/071203.322589:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported. Opening in existing browser session. You guys should use ubuntu-bug to report something and attempt to add an attachment as I did and you might see the chrome lock up yourselves. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1987665 Title: The "Settings" app is missing the 'Appearance' option Status in ubuntu-settings package in Ubuntu: New Bug description: In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine. Ubuntu Forum users report they have an Appearance option in their Settings app; I don't. bill@bill ~$ apt show ubuntu-settings Package: ubuntu-settings Version: 22.04.6 Priority: optional Section: x11 Origin: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987665] Re: The "Settings" app is missing the 'Appearance' option
I tried to attach an image to this report AFTER the report was already accepted and chrome locked up immediately after I selected a file. That's the second lock up when selecting a file. ** Attachment added: "Settings.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/+attachment/5611652/+files/Settings.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1987665 Title: The "Settings" app is missing the 'Appearance' option Status in ubuntu-settings package in Ubuntu: New Bug description: In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine. Ubuntu Forum users report they have an Appearance option in their Settings app; I don't. bill@bill ~$ apt show ubuntu-settings Package: ubuntu-settings Version: 22.04.6 Priority: optional Section: x11 Origin: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987665] [NEW] The "Settings" app is missing the 'Appearance' option
Public bug reported: In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine. Ubuntu Forum users report they have an Appearance option in their Settings app; I don't. bill@bill ~$ apt show ubuntu-settings Package: ubuntu-settings Version: 22.04.6 Priority: optional Section: x11 Origin: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1987665 Title: The "Settings" app is missing the 'Appearance' option Status in ubuntu-settings package in Ubuntu: New Bug description: In-situ upgraded V20.04LTS to V22.04.1LTS. Everything went fine. Ubuntu Forum users report they have an Appearance option in their Settings app; I don't. bill@bill ~$ apt show ubuntu-settings Package: ubuntu-settings Version: 22.04.6 Priority: optional Section: x11 Origin: Ubuntu Maintainer: Ubuntu Desktop Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 41.0 kB Depends: dconf-gsettings-backend | gsettings-backend, gnome-control-center-data, gsettings-desktop-schemas (>= 40), libglib2.0-bin (>= 2.53.4-3ubuntu1~) Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntukylin-desktop Download-Size: 6,508 B APT-Manual-Installed: no APT-Sources: http://hn.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Description: default settings for the Ubuntu desktop This package contains the default settings used by Ubuntu. I wanted to move the DOCK from BOTTOM to LEFT and found no way to do that through Settings. I found what looks like the proper key/value pair in dconf Editor and changed 'BOTTOM' to 'LEFT', rebooted and it didn't change anything. I double checked in dconf Editor after the reboot and it says 'LEFT' but the dock is still at the bottom. BTW - this is my second attempt at trying to report this bug but chrome locked up the first time after I picked a .png as an attachment, so I'm not going to attach an image of my Settings app showing The 'About' along side the list of available options with Appearance missing from the list. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-settings 22.04.6 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Aug 25 07:33:19 2022 InstallationDate: Installed on 2021-07-21 (399 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: Upgraded to jammy on 2022-08-21 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1987665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packag
[Touch-packages] [Bug 1981849] Re: Xorg freeze
One more note: While booting, my external (USB) monitor was disconnected. -- 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/1981849 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Although I filed this against X11, this might be a kernel issue. I upgraded packages on 7/13/22 & rebooted today (7/15/22 -- I hadn't noted the "reboot required pop-up). After reboot, the screen was blank/black and unresponsive. Looking at indicator lights, I believe that the system had booted OK. The syslog supports this. Included in the update: xserver-xorg-core:amd64 2:1.20.13-1ubuntu1~20.04.3 linux-libc-dev:amd64 5.4.0-122.138 linux-image-5.15.0-41-generic:amd64 5.15.0-41.44~20.04.1 Repeated attempts to boot all ended the same -- blank unresponsive screen. I could boot in recovery mode and with the 5.13 kernel (which I'm running now and was used for the bug report). > lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: Ubuntu 20.04.4 LTS Release: 20.04 Code> uname -a Linux turk 5.13.0-52-generic #59~20.04.1-Ubuntu SMP Thu Jun 16 21:21:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux name: focal Again, note that the problem occurred when booting to the 5.15 kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 13:51:44 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell GM107GLM [Quadro M2000M] [1028:16d9] InstallationDate: Installed on 2021-10-28 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Precision 7510 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-52-generic root=UUID=b611bb21-5970-4191-bf68-230392700099 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2021 dmi.bios.release: 1.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.25.3 dmi.board.name: 0M91XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 0010333 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.25.3:bd12/18/2021:br1.25:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0M91XC:rvrA00:cvnDellInc.:ct9:cvr:sku06D9: dmi.product.family: Precision dmi.product.name: Precision 7510 dmi.product.sku: 06D9 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Jul 15 10:40:20 2022 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::01:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.13-1ubuntu1~20.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1981849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981849] [NEW] Xorg freeze
Public bug reported: Although I filed this against X11, this might be a kernel issue. I upgraded packages on 7/13/22 & rebooted today (7/15/22 -- I hadn't noted the "reboot required pop-up). After reboot, the screen was blank/black and unresponsive. Looking at indicator lights, I believe that the system had booted OK. The syslog supports this. Included in the update: xserver-xorg-core:amd64 2:1.20.13-1ubuntu1~20.04.3 linux-libc-dev:amd64 5.4.0-122.138 linux-image-5.15.0-41-generic:amd64 5.15.0-41.44~20.04.1 Repeated attempts to boot all ended the same -- blank unresponsive screen. I could boot in recovery mode and with the 5.13 kernel (which I'm running now and was used for the bug report). > lsb_release -a LSB Version:core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Code> uname -a Linux turk 5.13.0-52-generic #59~20.04.1-Ubuntu SMP Thu Jun 16 21:21:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux name: focal Again, note that the problem occurred when booting to the 5.15 kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 13:51:44 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell GM107GLM [Quadro M2000M] [1028:16d9] InstallationDate: Installed on 2021-10-28 (260 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Precision 7510 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-52-generic root=UUID=b611bb21-5970-4191-bf68-230392700099 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2021 dmi.bios.release: 1.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.25.3 dmi.board.name: 0M91XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 0010333 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.25.3:bd12/18/2021:br1.25:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0M91XC:rvrA00:cvnDellInc.:ct9:cvr:sku06D9: dmi.product.family: Precision dmi.product.name: Precision 7510 dmi.product.sku: 06D9 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Jul 15 10:40:20 2022 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::01:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.13-1ubuntu1~20.04.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1981849 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Although I filed this against X11, this might be a kernel issue. I upgraded packages on 7/13/22 & rebooted today (7/15/22 -- I hadn't noted the "reboot required pop-up). After reboot, the screen was blank/black and unresponsive. Looking at indicator lights, I believe that the system had booted OK. The syslog supports this. Included in the update: xserver-xorg-core:amd64 2:1.20.13-1ubuntu1~20.04.3 linux-libc-dev:amd64 5.4.0-122.138 linux-image-5.15.0-41-generic:amd64 5.15.0-41.44~20.04.1
[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform
@Robie and @Lukas Sorry for pushing. May I have your comments on this. Thank you. -- 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/1955997 Title: The airplane hotkey has no function on a HP platform Status in OEM Priority Project: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Impish: In Progress Status in systemd source package in Jammy: Fix Released Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. Before the patch, nothing happens. After the patch, the rfkill works as expected. In some old HP platforms (contains Intel-HID and HPQ6001 in same machine), the user will aware the airplane mode toggled very quickly e.g. turn-on and turn-off immediately (or works good without problem, depends on how DM handles multiple rfkill events). In this case, you could check: 1. sudo evtest # You probably could see # ... # /dev/input/event8: Intel HID events # ... # /dev/input/event11: Wireless hotkeys # or "HP Wireless hotkeys" depends on your kernel version 2. try to listen these events when pressing airplane key, you will probably see these two events will send the keycode out. 3. check the components own this event $ sudo udevadm info -a /dev/input/event11 # ... # ATTRS{phys}=="hpq6001/input0" $ sudo udevadm info -a /dev/input/event8 # ... #DRIVERS=="intel-hid" 4. check your hwdb is affect. $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb # If you didn't see anything then it means your intel-hid is unmask. 5. You could report a bug to your DM for dealing with two rfkill events (same as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as workaround (but it will be overwritten in next upgrade) by adding: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr* ``` to /lib/udev/hwdb.d/60-keyboard.hwdb then $ systemd-hwdb update $ udevadm trigger [Where problems could occur] In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will not work but HP confirmed the new HP generation won't contain the HPQ6001 and also each DM still need to deal with multi-rfkill events because upstream changes[2]. --- In the last year, HP mentions HP machines need to use hp-wireless (HPQ6001) as the rfkill source[1]. However, HP confirms the HPQ6001 has been retired in the platforms since 2022. In the platforms after 2022, there are two sources of rkfill events (intel-hid, atkbd) and HP only guarantee the intel-hid works. Therefore, the upstream already accept the patch[2] to unmask intel-hid and mention this big change in the NEWS. This change makes the pre-2022 HP platforms meet the regression since they have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing function key. Thus, there is a patch[3] to make sure the GNOME could deal with this case smoothly. However, the systemd change will still cause other DEs meet the regression (xfce, KDE, lxde, etc..). Backport systemd change to make HP 2022 platforms work is not the best choice on stable version (focal in this case). We still need a solution to make airplane key works on 2022 HP platforms (intel-hid and atkbd only). The potential solution from my mind that is to maintain a whitelist to unmask intel-hid in ubuntu-patch in focal, something like: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:* KEYBOARD_KEY_8=wlan # Use hp-wireless instead ``` after "KEYBOARD_KEY_8=unkown". [1] https://bugs.launchpad.net/bugs/1883846 [2] https://github.com/systemd/systemd/pull/20219 [3] https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform
Hi Robie and Lukas, From our understanding, the concern is only related to Jammy, not focal. Is that OK to change to fix released on focal. This is one of the blocking issue for Stella Magneta platform. We need your help to comment on this. Thank you. -- 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/1955997 Title: The airplane hotkey has no function on a HP platform Status in OEM Priority Project: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Impish: In Progress Status in systemd source package in Jammy: Fix Released Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. Before the patch, nothing happens. After the patch, the rfkill works as expected. In some old HP platforms (contains Intel-HID and HPQ6001 in same machine), the user will aware the airplane mode toggled very quickly e.g. turn-on and turn-off immediately (or works good without problem, depends on how DM handles multiple rfkill events). In this case, you could check: 1. sudo evtest # You probably could see # ... # /dev/input/event8: Intel HID events # ... # /dev/input/event11: Wireless hotkeys # or "HP Wireless hotkeys" depends on your kernel version 2. try to listen these events when pressing airplane key, you will probably see these two events will send the keycode out. 3. check the components own this event $ sudo udevadm info -a /dev/input/event11 # ... # ATTRS{phys}=="hpq6001/input0" $ sudo udevadm info -a /dev/input/event8 # ... #DRIVERS=="intel-hid" 4. check your hwdb is affect. $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb # If you didn't see anything then it means your intel-hid is unmask. 5. You could report a bug to your DM for dealing with two rfkill events (same as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as workaround (but it will be overwritten in next upgrade) by adding: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr* ``` to /lib/udev/hwdb.d/60-keyboard.hwdb then $ systemd-hwdb update $ udevadm trigger [Where problems could occur] In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will not work but HP confirmed the new HP generation won't contain the HPQ6001 and also each DM still need to deal with multi-rfkill events because upstream changes[2]. --- In the last year, HP mentions HP machines need to use hp-wireless (HPQ6001) as the rfkill source[1]. However, HP confirms the HPQ6001 has been retired in the platforms since 2022. In the platforms after 2022, there are two sources of rkfill events (intel-hid, atkbd) and HP only guarantee the intel-hid works. Therefore, the upstream already accept the patch[2] to unmask intel-hid and mention this big change in the NEWS. This change makes the pre-2022 HP platforms meet the regression since they have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing function key. Thus, there is a patch[3] to make sure the GNOME could deal with this case smoothly. However, the systemd change will still cause other DEs meet the regression (xfce, KDE, lxde, etc..). Backport systemd change to make HP 2022 platforms work is not the best choice on stable version (focal in this case). We still need a solution to make airplane key works on 2022 HP platforms (intel-hid and atkbd only). The potential solution from my mind that is to maintain a whitelist to unmask intel-hid in ubuntu-patch in focal, something like: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:* KEYBOARD_KEY_8=wlan # Use hp-wireless instead ``` after "KEYBOARD_KEY_8=unkown". [1] https://bugs.launchpad.net/bugs/1883846 [2] https://github.com/systemd/systemd/pull/20219 [3] https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform
Hi Robie, May we have your comment on this. Since we would like to have this solution in the latest kernel, need you help to check on this. Thank you. -- 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/1955997 Title: The airplane hotkey has no function on a HP platform Status in OEM Priority Project: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Impish: In Progress Status in systemd source package in Jammy: Fix Released Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. Before the patch, nothing happens. After the patch, the rfkill works as expected. In some old HP platforms (contains Intel-HID and HPQ6001 in same machine), the user will aware the airplane mode toggled very quickly e.g. turn-on and turn-off immediately (or works good without problem, depends on how DM handles multiple rfkill events). In this case, you could check: 1. sudo evtest # You probably could see # ... # /dev/input/event8: Intel HID events # ... # /dev/input/event11: Wireless hotkeys # or "HP Wireless hotkeys" depends on your kernel version 2. try to listen these events when pressing airplane key, you will probably see these two events will send the keycode out. 3. check the components own this event $ sudo udevadm info -a /dev/input/event11 # ... # ATTRS{phys}=="hpq6001/input0" $ sudo udevadm info -a /dev/input/event8 # ... #DRIVERS=="intel-hid" 4. check your hwdb is affect. $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb # If you didn't see anything then it means your intel-hid is unmask. 5. You could report a bug to your DM for dealing with two rfkill events (same as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as workaround (but it will be overwritten in next upgrade) by adding: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr* ``` to /lib/udev/hwdb.d/60-keyboard.hwdb then $ systemd-hwdb update $ udevadm trigger [Where problems could occur] In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will not work but HP confirmed the new HP generation won't contain the HPQ6001 and also each DM still need to deal with multi-rfkill events because upstream changes[2]. --- In the last year, HP mentions HP machines need to use hp-wireless (HPQ6001) as the rfkill source[1]. However, HP confirms the HPQ6001 has been retired in the platforms since 2022. In the platforms after 2022, there are two sources of rkfill events (intel-hid, atkbd) and HP only guarantee the intel-hid works. Therefore, the upstream already accept the patch[2] to unmask intel-hid and mention this big change in the NEWS. This change makes the pre-2022 HP platforms meet the regression since they have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing function key. Thus, there is a patch[3] to make sure the GNOME could deal with this case smoothly. However, the systemd change will still cause other DEs meet the regression (xfce, KDE, lxde, etc..). Backport systemd change to make HP 2022 platforms work is not the best choice on stable version (focal in this case). We still need a solution to make airplane key works on 2022 HP platforms (intel-hid and atkbd only). The potential solution from my mind that is to maintain a whitelist to unmask intel-hid in ubuntu-patch in focal, something like: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:* KEYBOARD_KEY_8=wlan # Use hp-wireless instead ``` after "KEYBOARD_KEY_8=unkown". [1] https://bugs.launchpad.net/bugs/1883846 [2] https://github.com/systemd/systemd/pull/20219 [3] https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946595] Re: indicator-applet-complete clock occasionally shows UTC
Ok, but the standalone clock indicator works. The clock in "indicator applet complete" doesn't. See https://i.stack.imgur.com/x11A4.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1946595 Title: indicator-applet-complete clock occasionally shows UTC Status in indicator-datetime package in Ubuntu: New Bug description: Sometimes at login, but sometimes at other times, the clock in indicator-applet-complete starts showing UTC instead of local. It is not a system clock problem, in the terminal and in the standalone clock applet the time is correct. See https://i.stack.imgur.com/x11A4.png ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-applet-complete (not installed) ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Oct 10 08:37:00 2021 InstallationDate: Installed on 2018-04-27 (1261 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: indicator-applet UpgradeStatus: Upgraded to focal on 2021-10-03 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1946595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369651] Re: "libmtp error: Could not send object info" when copying content to root MTP folder
This happens for me on 20.04 LTS when the file being copied has a colon (:) in its name. The error doesn't pop up until the very end of the file copy process, and in the end, the file is not copied to the destination. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1369651 Title: "libmtp error: Could not send object info" when copying content to root MTP folder Status in mtp package in Ubuntu: Confirmed Bug description: ENVIRONMENT: Ubuntu device: ubuntu-rtm/14.09-proposed build 40 Desktop: Ubuntu 14.10 SUMMARY: "libmtp error: Could not send object info" when copying content to root MTP folder STEPS: 1) Connect Ubuntu MTP device over USB 2) Attempt to copy some content to the root of the MTP folder EXPECTED RESULT: The copy operation should succeed. (This is the Android behaviour). ACTUAL RESULT: An error message is presented on desktop: "libmtp error: Could not send object info" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1369651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940691] Re: sfdisk fails to overwrite disks that contain a pre-existing linux partition
** Description changed: This command should non-interactively obliterate whatever partition table is on /dev/sde, and create a new table with a linux partition that spans the whole disk: - $ sfdisk --label gpt /dev/sde <<< 'start=2048, type='"$(sfdisk --label + $ sfdisk --label gpt /dev/sde <<< 'start=2048, type='"$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux filesystem/{print $1}')" Sometimes it works correctly; sometimes not. It seems to work correctly as long as the pre-existing partition table does not already contain a linux partition. E.g. if the existing table just contains an exFAT partition, there's no issue. But if there is a linux partition, it gives this output: - Old situation: Device StartEndSectors Size Type /dev/sde1 2048 1953525134 1953523087 931.5G Linux root (x86-64) >>> Created a new GPT disklabel (GUID: ). /dev/sde1: Sector 2048 already used. Failed to add #1 partition: Numerical result out of range Leaving. - sfdisk should *always* overwrite the target disk unconditionally. This is what the dump of the target drive looks like in the failure case: $ sfdisk -d /dev/sdd label: gpt label-id: device: /dev/sdd unit: sectors first-lba: 34 last-lba: 1953525134 grain: 33553920 sector-size: 512 /dev/sdd1 : start=2048, size= 1953523087, type=4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709, uuid=, name="Linux x86-64 root (/)" $ sfdisk -v sfdisk from util-linux 2.36.1 Even the workaround is broken. That is, running the following: $ wipefs -a /dev/sde should put the disk in a state that can be overwritten. But whatever residual metadata it leaves behind still triggers the sfdisk bug: $ sfdisk --label gpt /dev/sde <<< 'start=2048, type='"$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux filesystem/{print $1}')" Checking that no-one is using this disk right now ... OK Disk /dev/sde: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors - Disk model: Disk + Disk model: Disk Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes >>> Created a new GPT disklabel (GUID: ). /dev/sde1: Sector 2048 already used. Failed to add #1 partition: Numerical result out of range Leaving. + + Workaround 2 (also fails): + + $ dd if=/dev/zero of=/dev/sde bs=1M count=512 + + $ sfdisk -d /dev/sde + sfdisk: /dev/sde: does not contain a recognized partition table + + ^ the nuclear option did the right thing, but sfdisk still fails to + partition the drive (same error). + + The *only* workaround that works is an interactive partitioning with + gdisk. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1940691 Title: sfdisk fails to overwrite disks that contain a pre-existing linux partition Status in util-linux package in Ubuntu: New Bug description: This command should non-interactively obliterate whatever partition table is on /dev/sde, and create a new table with a linux partition that spans the whole disk: $ sfdisk --label gpt /dev/sde <<< 'start=2048, type='"$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux filesystem/{print $1}')" Sometimes it works correctly; sometimes not. It seems to work correctly as long as the pre-existing partition table does not already contain a linux partition. E.g. if the existing table just contains an exFAT partition, there's no issue. But if there is a linux partition, it gives this output: - Old situation: Device StartEndSectors Size Type /dev/sde1 2048 1953525134 1953523087 931.5G Linux root (x86-64) >>> Created a new GPT disklabel (GUID: ). /dev/sde1: Sector 2048 already used. Failed to add #1 partition: Numerical result out of range Leaving. - sfdisk should *always* overwrite the target disk unconditionally. This is what the dump of the target drive looks like in the failure case: $ sfdisk -d /dev/sdd label: gpt label-id: device: /dev/sdd unit: sectors first-lba: 34 last-lba: 1953525134 grain: 33553920 sector-size: 512 /dev/sdd1 : start=2048, size= 1953523087, type=4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709, uuid=, name="Linux x86-64 root (/)" $ sfdisk -v sfdisk from util-linux 2.36.1 Even the workaround is broken. That is, running the following: $ wipefs -a /dev/sde should put the disk in a state that can be overwritten. But whatever residual metadata it leaves behind still triggers the sfdisk bug: $ sfdisk --label gpt /dev/sde <<< 'start=2048, type='"$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux filesystem/{print $1}')" Checking that no-one is using this disk right now ... OK Disk /dev/sde: 931.51
[Touch-packages] [Bug 1940691] [NEW] sfdisk fails to overwrite disks that contain a pre-existing linux partition
Public bug reported: This command should non-interactively obliterate whatever partition table is on /dev/sde, and create a new table with a linux partition that spans the whole disk: $ sfdisk --label gpt /dev/sde <<< 'start=2048, type='"$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux filesystem/{print $1}')" Sometimes it works correctly; sometimes not. It seems to work correctly as long as the pre-existing partition table does not already contain a linux partition. E.g. if the existing table just contains an exFAT partition, there's no issue. But if there is a linux partition, it gives this output: - Old situation: Device StartEndSectors Size Type /dev/sde1 2048 1953525134 1953523087 931.5G Linux root (x86-64) >>> Created a new GPT disklabel (GUID: ). /dev/sde1: Sector 2048 already used. Failed to add #1 partition: Numerical result out of range Leaving. - sfdisk should *always* overwrite the target disk unconditionally. This is what the dump of the target drive looks like in the failure case: $ sfdisk -d /dev/sdd label: gpt label-id: device: /dev/sdd unit: sectors first-lba: 34 last-lba: 1953525134 grain: 33553920 sector-size: 512 /dev/sdd1 : start=2048, size= 1953523087, type=4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709, uuid=, name="Linux x86-64 root (/)" $ sfdisk -v sfdisk from util-linux 2.36.1 Even the workaround is broken. That is, running the following: $ wipefs -a /dev/sde should put the disk in a state that can be overwritten. But whatever residual metadata it leaves behind still triggers the sfdisk bug: $ sfdisk --label gpt /dev/sde <<< 'start=2048, type='"$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux filesystem/{print $1}')" Checking that no-one is using this disk right now ... OK Disk /dev/sde: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Disk Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes >>> Created a new GPT disklabel (GUID: ). /dev/sde1: Sector 2048 already used. Failed to add #1 partition: Numerical result out of range Leaving. Workaround 2 (also fails): $ dd if=/dev/zero of=/dev/sde bs=1M count=512 $ sfdisk -d /dev/sde sfdisk: /dev/sde: does not contain a recognized partition table ^ the nuclear option did the right thing, but sfdisk still fails to partition the drive (same error). The *only* workaround that works is an interactive partitioning with gdisk. ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1940691 Title: sfdisk fails to overwrite disks that contain a pre-existing linux partition Status in util-linux package in Ubuntu: New Bug description: This command should non-interactively obliterate whatever partition table is on /dev/sde, and create a new table with a linux partition that spans the whole disk: $ sfdisk --label gpt /dev/sde <<< 'start=2048, type='"$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux filesystem/{print $1}')" Sometimes it works correctly; sometimes not. It seems to work correctly as long as the pre-existing partition table does not already contain a linux partition. E.g. if the existing table just contains an exFAT partition, there's no issue. But if there is a linux partition, it gives this output: - Old situation: Device StartEndSectors Size Type /dev/sde1 2048 1953525134 1953523087 931.5G Linux root (x86-64) >>> Created a new GPT disklabel (GUID: ). /dev/sde1: Sector 2048 already used. Failed to add #1 partition: Numerical result out of range Leaving. - sfdisk should *always* overwrite the target disk unconditionally. This is what the dump of the target drive looks like in the failure case: $ sfdisk -d /dev/sdd label: gpt label-id: device: /dev/sdd unit: sectors first-lba: 34 last-lba: 1953525134 grain: 33553920 sector-size: 512 /dev/sdd1 : start=2048, size= 1953523087, type=4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709, uuid=, name="Linux x86-64 root (/)" $ sfdisk -v sfdisk from util-linux 2.36.1 Even the workaround is broken. That is, running the following: $ wipefs -a /dev/sde should put the disk in a state that can be overwritten. But whatever residual metadata it leaves behind still triggers the sfdisk bug: $ sfdisk --label gpt /dev/sde <<< 'start=2048, type='"$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux filesystem/{print $1}')" Checking that no-one is using this disk right now ... OK Disk /dev/sde: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: Disk Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size
[Touch-packages] [Bug 1937874] [NEW] one --accept-regex expression negates another
Public bug reported: This command should theoretically fetch all PDFs on a page: $ wget -v -d -r --level 1 --adjust-extension --no-clobber --no-directories\ --accept-regex 'administrative-orders/.*/administrative-order-matter-'\ --accept-regex 'administrative-orders.*.pdf'\ --accept-regex 'administrative-orders.page[^&]*$'\ --directory-prefix=/tmp\ 'https://www.ncua.gov/regulation-supervision/enforcement-actions/administrative-orders?page=56' But it fails to grab any of them, giving the output: --- Deciding whether to enqueue "https://www.ncua.gov/files/administrative-orders/AO14-0241-R4.pdf;. https://www.ncua.gov/files/administrative-orders/AO14-0241-R4.pdf is excluded/not-included through regex. Decided NOT to load it. --- That's bogus. The workaround is to remove this option: --accept-regex 'administrative-orders.page[^&]*$' But that should not be necessary. Adding an --accept-* clause should never cause another --accept-* clause to become invalidated and it should not shrink the set of fetched files. ** Affects: wget (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1937874 Title: one --accept-regex expression negates another Status in wget package in Ubuntu: New Bug description: This command should theoretically fetch all PDFs on a page: $ wget -v -d -r --level 1 --adjust-extension --no-clobber --no-directories\ --accept-regex 'administrative-orders/.*/administrative-order-matter-'\ --accept-regex 'administrative-orders.*.pdf'\ --accept-regex 'administrative-orders.page[^&]*$'\ --directory-prefix=/tmp\ 'https://www.ncua.gov/regulation-supervision/enforcement-actions/administrative-orders?page=56' But it fails to grab any of them, giving the output: --- Deciding whether to enqueue "https://www.ncua.gov/files/administrative-orders/AO14-0241-R4.pdf;. https://www.ncua.gov/files/administrative-orders/AO14-0241-R4.pdf is excluded/not-included through regex. Decided NOT to load it. --- That's bogus. The workaround is to remove this option: --accept-regex 'administrative-orders.page[^&]*$' But that should not be necessary. Adding an --accept-* clause should never cause another --accept-* clause to become invalidated and it should not shrink the set of fetched files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1937874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937850] [NEW] the -L / --relative option breaks --accept-regex
Public bug reported: This code should in principle (per the docs) fetch a few *.pdf files: $ wget -r --level 1 --adjust-extension --relative --no-clobber --no-directories\ --domains=ncua.gov --accept-regex 'administrative-orders/.*.pdf'\ 'https://www.ncua.gov/regulation-supervision/enforcement-actions/administrative-orders?page=22=year=desc=' But it misses all *.pdf files. When the --relative option is removed, the PDF files are downloaded. However, when you examine the tree-top HTML file, the links pointing to PDF files actually are relative. ** Affects: wget (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1937850 Title: the -L / --relative option breaks --accept-regex Status in wget package in Ubuntu: New Bug description: This code should in principle (per the docs) fetch a few *.pdf files: $ wget -r --level 1 --adjust-extension --relative --no-clobber --no-directories\ --domains=ncua.gov --accept-regex 'administrative-orders/.*.pdf'\ 'https://www.ncua.gov/regulation-supervision/enforcement-actions/administrative-orders?page=22=year=desc=' But it misses all *.pdf files. When the --relative option is removed, the PDF files are downloaded. However, when you examine the tree-top HTML file, the links pointing to PDF files actually are relative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1937850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937082] [NEW] gunzip fails to extract data from stdin when the zip holds multiple files
Public bug reported: There is no good reason for this command to fail: $ wget --quiet -O - https://web.archive.org/web/20210721004028/freefontsdownload.net/download/76451/lucida_fax.zip | gunzip - The output is: [InternetShortcut] URL=HOMESITEfree-lucida_fax-font-76451.htmgzip: stdin has more than one entry--rest ignored What's happening is gzip logic has gotten tangled up with the gunzip logic. If gzip receives an input stream, it's sensible that the resulting archive contain just one file. But there's no reason gunzip should not be able to produce multiple files from a zip stream. Note that -c was not given to gunzip, so it should not have the constraints that use of stdout would impose. The man page is also a problem. The gunzip portion of the aggregated man page makes no statement about how stdin is expected to operate. At a minimum, it should say that a minus ("-") directs gunzip to read from stdin. ** Affects: gzip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1937082 Title: gunzip fails to extract data from stdin when the zip holds multiple files Status in gzip package in Ubuntu: New Bug description: There is no good reason for this command to fail: $ wget --quiet -O - https://web.archive.org/web/20210721004028/freefontsdownload.net/download/76451/lucida_fax.zip | gunzip - The output is: [InternetShortcut] URL=HOMESITEfree-lucida_fax-font-76451.htmgzip: stdin has more than one entry--rest ignored What's happening is gzip logic has gotten tangled up with the gunzip logic. If gzip receives an input stream, it's sensible that the resulting archive contain just one file. But there's no reason gunzip should not be able to produce multiple files from a zip stream. Note that -c was not given to gunzip, so it should not have the constraints that use of stdout would impose. The man page is also a problem. The gunzip portion of the aggregated man page makes no statement about how stdin is expected to operate. At a minimum, it should say that a minus ("-") directs gunzip to read from stdin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1937082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1918970] Re: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration
** Changed in: maas Status: New => Triaged -- 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/1918970 Title: Unable to netboot Ubuntu 18.04 and older on an IBM Z DPM Partition - no manual nor automatic qeth device configuration Status in MAAS: Triaged Status in Ubuntu on IBM z Systems: Triaged Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in s390-tools package in Ubuntu: New Bug description: I tried to deploy Ubuntu 18.04 with the GA-18.04 kernel on an IBM Z14 DPM Partition. The initrd fails to bring up network and thus fails to boot in MAAS. I haven't tried older versions of Ubuntu but suspect they also have the same bug. mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init. run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console /scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o r address /scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty3: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty4: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty4: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty5: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty5: No such device or ad dress /scripts/panic/console_setup: line 1: can't create /dev/tty6: No such device or address /scripts/panic/console_setup: line 1: can't open /dev/tty6: No such device or ad dress BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n [ 78.114530] random: crng init done [ 78.114538] random: 7 urandom warning(s) missed due to ratelimiting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1918970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934040] Re: openssl s_client's '-ssl2' & '-ssl3' options gone, prematurely!
** Description changed: SSL2 and SSL3 have been hastily removed, apparently by developers who are unaware that these protocols serve purposes other than encryption. SSL2/3 is *still used* on onion sites. Why? For verification. An onion site has inherent encryption, so it matters not how weak the SSL crypto is when the purpose is purely to verify that the server is owned by who they say it's owned by. Proof that disclosure attacks on ssl2/3 are irrelevant to onion sites: https://blog.torproject.org/tls-certificate-for-onion-site + https://community.torproject.org/onion-services/overview/ So here is a real world impact case. Suppose you get your email from one of these onion mail servers: http://onionmail.info/directory.html Some (if not all) use ssl2/3 on top of Tor's inherent onion tunnel. They force users to use ssl2/3, so even if a user configures the client not to impose TLS, the server imposes it. And it's reasonable because the ssl2/3 vulns are orthoganol to the use case. Some users will get lucky and use a mail client that still supports ssl2/3. But there's still a problem: users can no longer use openssl to obtain the fingerprint to pin. e.g. $ openssl s_client -proxy 127.0.0.1:8118 -connect xhfheq5i37waj6qb.onion:110 -showcerts CONNECTED(0003) 140124399195456:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 44 bytes and written 330 bytes Verification: OK --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok) --- That's openssl version 1.1.1k Being denied the ability to pin the SSL cert is actually a *degredation* of security. Cert Pinning is particularly useful with self-signed certs, as is often the scenario with onion sites. -- 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/1934040 Title: openssl s_client's '-ssl2' & '-ssl3' options gone, prematurely! Status in openssl package in Ubuntu: New Bug description: SSL2 and SSL3 have been hastily removed, apparently by developers who are unaware that these protocols serve purposes other than encryption. SSL2/3 is *still used* on onion sites. Why? For verification. An onion site has inherent encryption, so it matters not how weak the SSL crypto is when the purpose is purely to verify that the server is owned by who they say it's owned by. Proof that disclosure attacks on ssl2/3 are irrelevant to onion sites: https://blog.torproject.org/tls-certificate-for-onion-site https://community.torproject.org/onion-services/overview/ So here is a real world impact case. Suppose you get your email from one of these onion mail servers: http://onionmail.info/directory.html Some (if not all) use ssl2/3 on top of Tor's inherent onion tunnel. They force users to use ssl2/3, so even if a user configures the client not to impose TLS, the server imposes it. And it's reasonable because the ssl2/3 vulns are orthoganol to the use case. Some users will get lucky and use a mail client that still supports ssl2/3. But there's still a problem: users can no longer use openssl to obtain the fingerprint to pin. e.g. $ openssl s_client -proxy 127.0.0.1:8118 -connect xhfheq5i37waj6qb.onion:110 -showcerts CONNECTED(0003) 140124399195456:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 44 bytes and written 330 bytes Verification: OK --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok) --- That's openssl version 1.1.1k Being denied the ability to pin the SSL cert is actually a *degredation* of security. Cert Pinning is particularly useful with self-signed certs, as is often the scenario with onion sites. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1934040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934044] [NEW] openssl removed ssl2/3 and broke cURL because curl uses openssl instead of libssl
Public bug reported: cURL supports a -ssl3 option (and rightly so), but openssl removed it prematurely (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1934040). The fallout: torsocks curl --insecure --ssl-allow-beast -ssl3 -vvI https://xhfheq5i37waj6qb.onion:110 2>&1 * Trying 127.42.42.0:110... * Connected to xhfheq5i37waj6qb.onion (127.42.42.0) port 110 (#0) * OpenSSL was built without SSLv3 support * Closing connection 0 Is it possible that curl's check for ssl3 is flawed? I say that because both curl and fetchmail are dependant on the same libssl pkg, and yet fetchmail can still do ssl3 but curl can't. Neither curl nor fetchmail names "openssl" as a dependency. So curl perhaps should not look to the openssl package to detect ssl3 capability. SSL3 is still useful for onion sites, so curl should do the necessary to retain that capability. ** Affects: curl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1934044 Title: openssl removed ssl2/3 and broke cURL because curl uses openssl instead of libssl Status in curl package in Ubuntu: New Bug description: cURL supports a -ssl3 option (and rightly so), but openssl removed it prematurely (see https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1934040). The fallout: torsocks curl --insecure --ssl-allow-beast -ssl3 -vvI https://xhfheq5i37waj6qb.onion:110 2>&1 * Trying 127.42.42.0:110... * Connected to xhfheq5i37waj6qb.onion (127.42.42.0) port 110 (#0) * OpenSSL was built without SSLv3 support * Closing connection 0 Is it possible that curl's check for ssl3 is flawed? I say that because both curl and fetchmail are dependant on the same libssl pkg, and yet fetchmail can still do ssl3 but curl can't. Neither curl nor fetchmail names "openssl" as a dependency. So curl perhaps should not look to the openssl package to detect ssl3 capability. SSL3 is still useful for onion sites, so curl should do the necessary to retain that capability. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1934044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934040] [NEW] openssl s_client's '-ssl2' & '-ssl3' options gone, prematurely!
Public bug reported: SSL2 and SSL3 have been hastily removed, apparently by developers who are unaware that these protocols serve purposes other than encryption. SSL2/3 is *still used* on onion sites. Why? For verification. An onion site has inherent encryption, so it matters not how weak the SSL crypto is when the purpose is purely to verify that the server is owned by who they say it's owned by. Proof that disclosure attacks on ssl2/3 are irrelevant to onion sites: https://blog.torproject.org/tls-certificate-for-onion-site So here is a real world impact case. Suppose you get your email from one of these onion mail servers: http://onionmail.info/directory.html Some (if not all) use ssl2/3 on top of Tor's inherent onion tunnel. They force users to use ssl2/3, so even if a user configures the client not to impose TLS, the server imposes it. And it's reasonable because the ssl2/3 vulns are orthoganol to the use case. Some users will get lucky and use a mail client that still supports ssl2/3. But there's still a problem: users can no longer use openssl to obtain the fingerprint to pin. e.g. $ openssl s_client -proxy 127.0.0.1:8118 -connect xhfheq5i37waj6qb.onion:110 -showcerts CONNECTED(0003) 140124399195456:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 44 bytes and written 330 bytes Verification: OK --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok) --- That's openssl version 1.1.1k Being denied the ability to pin the SSL cert is actually a *degredation* of security. Cert Pinning is particularly useful with self-signed certs, as is often the scenario with onion sites. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Description changed: SSL2 and SSL3 have been hastily removed, apparently by developers who are unaware that these protocols serve purposes other than encryption. SSL2/3 is *still used* on onion sites. Why? For verification. An onion site has inherent encryption, so it matters not how weak the SSL crypto is when the purpose is purely to verify that the server is owned by who they say it's owned by. Proof that disclosure attacks on ssl2/3 are irrelevant to onion sites: https://blog.torproject.org/tls-certificate-for-onion-site So here is a real world impact case. Suppose you get your email from one of these onion mail servers: http://onionmail.info/directory.html Some (if not all) use ssl2/3 on top of Tor's inherent onion tunnel. They force users to use ssl2/3, so even if a user configures the client not to impose TLS, the server imposes it. And it's reasonable because the ssl2/3 vulns are orthoganol to the use case. Some users will get lucky and use a mail client that still supports ssl2/3. But there's still a problem: users can no longer use openssl to obtain the fingerprint to pin. e.g. $ openssl s_client -proxy 127.0.0.1:8118 -connect xhfheq5i37waj6qb.onion:110 -showcerts CONNECTED(0003) 140124399195456:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 44 bytes and written 330 bytes Verification: OK --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE No ALPN negotiated Early data was not sent Verify return code: 0 (ok) --- + That's openssl version 1.1.1k - That's openssl version 1.1.1k + Being denied the ability to pin the SSL cert is actually a *degredation* + of security. Cert Pinning is particularly useful with self-signed + certs, as is often the scenario with onion sites. -- 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/1934040 Title: openssl s_client's '-ssl2' & '-ssl3' options gone, prematurely! Status in openssl package in Ubuntu: New Bug description: SSL2 and SSL3 have been hastily removed, apparently by developers who are unaware that these protocols serve purposes other than encryption. SSL2/3 is *still used* on onion sites. Why? For verification. An onion site has inherent encryption, so it matters not how weak the SSL crypto is when the purpose is purely to verify that the server is owned by who they say it's owned by. Proof that disclosure attacks on ssl2/3 are irrelevant to onion sites: https://blog.torproject.org/tls-certificate-for-onion-site So here is a real world impact case. Suppose you get your email from one of these onion mail servers: http://onionmail.info/directory.html
[Touch-packages] [Bug 1933913] [NEW] "Xorg -configure" results in "modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64"
Public bug reported: With x11 not running, this was executed: "Xorg -configure". It should simply build a configuration file. The output below appears in the terminal with an error. It manages to create a config file anyway, but what it creates causes "startx" to fall over. So I am forced to run x11 without a config file (which is a problem for me because I have two displays and need to change the RightOf/LeftOf setting). OUTPUT: X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 Build Operating System: linux Debian Current Operating System: Linux billyikes 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-7-amd64 root=/dev/mapper/grp-root ro rd.luks.name=UUID=279a24dc-1014-6495-38cc-75ce88144f44=cryptdisk quiet Build Date: 13 April 2021 04:07:31PM xorg-server 2:1.20.11-1 (https://www.debian.org/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 29 02:19:12 2021 List of video drivers: amdgpu ati intel nouveau qxl radeon vmware modesetting fbdev vesa (++) Using config file: "/root/xorg.conf.new" (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64 intel: waited 2020 ms for i915.ko driver to load Number of created screens does not match number of detected devices. Configuration failed. (EE) Server terminated with error (2). Closing log file. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1933913 Title: "Xorg -configure" results in "modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64" Status in xorg package in Ubuntu: New Bug description: With x11 not running, this was executed: "Xorg -configure". It should simply build a configuration file. The output below appears in the terminal with an error. It manages to create a config file anyway, but what it creates causes "startx" to fall over. So I am forced to run x11 without a config file (which is a problem for me because I have two displays and need to change the RightOf/LeftOf setting). OUTPUT: X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 Build Operating System: linux Debian Current Operating System: Linux billyikes 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-7-amd64 root=/dev/mapper/grp-root ro rd.luks.name=UUID=279a24dc-1014-6495-38cc-75ce88144f44=cryptdisk quiet Build Date: 13 April 2021 04:07:31PM xorg-server 2:1.20.11-1 (https://www.debian.org/support) Current version of pixman: 0.40.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 29 02:19:12 2021 List of video drivers: amdgpu ati intel nouveau qxl radeon vmware modesetting fbdev vesa (++) Using config file: "/root/xorg.conf.new" (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" modprobe: FATAL: Module fbcon not found in directory /lib/modules/5.10.0-7-amd64 intel: waited 2020 ms for i915.ko driver to load Number of created screens does not match number of detected devices. Configuration failed. (EE) Server terminated with error (2). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1933913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931815] Re: the %{remote_ip} output format is broken on proxied connections
The socks.c code shows that cURL does not even attempt DNS resolution on SOCKS4a. Strictly speaking, the SOCKS4a spec expects apps to /attempt/ DNS resolution before contacting the socks server. I won't complain on this point though because the status quo is favorable to Tor users (as it protects them from DNS leaks). The fallout is that the SOCKS server does not give feedback to the app on the IP it settles on in the socks4a scenario. This means cURL has no possible way of knowing which IP to express in the %{remote_ip} output. After seeing the code I'm calling out these bugs: bug 1) SOCKS4a: Considering that Curl_resolve() is unconditionally bypassed, when a user supplies both --resolve and also demands socks4a cURL will neglect to honor the --resolve option even though the two options are theoretically compatible. This is a minor bug because socks4 can be used instead as a workaround. But certainly the man page should at a minimum disclose the artificial incompatibility between socks4a and --resolve. bug 2) SOCKS4a docs: cURL has some discretion whether to attempt DNS resolution or not. Yet the docs do not clarify. Users should get reassurance in the man page that using socks4a unconditionally refrains from internal DNS resolution. bug 3) SOCKS4: Since cURL *must* do DNS resolution, cURL must also know what the target IP is. Thus cURL should properly return the %{remote_ip} value. bug 4) The docs for %{remote_ip} should tell users what to expect for that value. The man page is vague enough to be useless. Workaround: if proxy users need to know which IP cURL connected to, they must do their own DNS resolution manually outside of cURL (e.g. using dig), supply the IP & hostname via --resolve, and use SOCKS4 or SOCKS5 (not SOCKS4a). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1931815 Title: the %{remote_ip} output format is broken on proxied connections Status in curl package in Ubuntu: New Bug description: This is how a Tor user would use cURL to grab a header, and also expect to be told which IP address was contacted: curl --ssl --socks4a 127.0.0.1:9050 -L --head -w '(effective URL => "%{url_effective} @ %{remote_ip}")' "$target_url" It's broken because the "remote_ip" is actually just printed as the 127.0.0.1 (likely that of the proxy server not the remote target host). tested on curl ver 7.52.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1931815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931815] Re: the %{remote_ip} output format is broken on proxied connections
According to the SOCKS4a spec: https://www.openssh.com/txt/socks4.protocol https://www.openssh.com/txt/socks4a.protocol With SOCKS4 cURL *must* do DNS resolution and pass the selected IP to the SOCKS server. OTOH, SOCKS4a gives cURL the option to resolve. If cURL fails at DNS resolution, it's expected to send the hostname and 0.0.0.x. So generally cURL should succeed at DNS resolution and thus have the IP of the target server. Yet it's not sharing that info with the user. SOCKS4a was a bad test case because we can't know whether or not cURL did the DNS resolution. A better test case is with SOCKS4 as follows: curl --ssl --socks4 127.0.0.1:9050 -L --head -w '(effective URL => "%{url_effective} @ %{remote_ip}")' "$target_url" We are assured per the SOCKS4 protocol that cURL *must* do DNS resolution, so cURL must know the remote IP address. Yet it still neglects to correctly set the %{remote_ip} value. This is certainly a bug. Secondary bug-- the manpage states: "remote_ip The remote IP address of the most recently done connection - can be either IPv4 or IPv6 (Added in 7.29.0)" The man page is ambiguous. The /rule of least astonishment/ would have the user naturally expecting "remote IP" to be the target IP whenever cURL knows it. Since the behavior is non-intuitive, the man page should state in detail what the user should expect to receive for the %{remote_ip} value. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1931815 Title: the %{remote_ip} output format is broken on proxied connections Status in curl package in Ubuntu: New Bug description: This is how a Tor user would use cURL to grab a header, and also expect to be told which IP address was contacted: curl --ssl --socks4a 127.0.0.1:9050 -L --head -w '(effective URL => "%{url_effective} @ %{remote_ip}")' "$target_url" It's broken because the "remote_ip" is actually just printed as the 127.0.0.1 (likely that of the proxy server not the remote target host). tested on curl ver 7.52.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1931815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931815] [NEW] the %{remote_ip} output format is broken on proxied connections
Public bug reported: This is how a Tor user would use cURL to grab a header, and also expect to be told which IP address was contacted: curl --ssl --socks4a 127.0.0.1:9050 -L --head -w '(effective URL => "%{url_effective} @ %{remote_ip}")' "$target_url" It's broken because the "remote_ip" is actually just printed as the 127.0.0.1 (likely that of the proxy server not the remote target host). tested on curl ver 7.52.1 ** Affects: curl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1931815 Title: the %{remote_ip} output format is broken on proxied connections Status in curl package in Ubuntu: New Bug description: This is how a Tor user would use cURL to grab a header, and also expect to be told which IP address was contacted: curl --ssl --socks4a 127.0.0.1:9050 -L --head -w '(effective URL => "%{url_effective} @ %{remote_ip}")' "$target_url" It's broken because the "remote_ip" is actually just printed as the 127.0.0.1 (likely that of the proxy server not the remote target host). tested on curl ver 7.52.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1931815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 978587] Re: apt should ensure .deb are not corrupted before handing them to dpkg
This is actually a security issue and it's surprising it's gone unfixed for 9 years. It's inconsistent for apt to check the hash on deb files that it downloads, but then neglect to do so on user-supplied deb files. The status quo is a recipe for disaster. To exacerbate the problem, the man page does not document the inconsistency or the fact that . There are a variety of ways to fix this: 1) apt could refuse to accept local .deb files 2) apt could require local .deb files to be supplied with a hash string (which would need a new CLI arg) 3) apt could print the hash to the string and instruct the user to confirm whether the hash matches 4) apt could check the repos it's aware of to see if the hash matches anything served by a trusted repo. If not, follow option 1 or 3 above. It's also important to note that users don't generally know how deb files are structured or how deb files are structured. Should they be responsible for knowing whether a hash is embedded within the deb file or not? Particularly when the man page makes no mention of it? Generally, the user might know that hashes are checked by the apt-* tools one way or another. The apt suite of tools (and docs for it) keep the user in the dark, and yet the user is responsible knowing how it works. The user is not served well in this case. -- 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/978587 Title: apt should ensure .deb are not corrupted before handing them to dpkg Status in apt package in Ubuntu: Confirmed Bug description: Upon upgrading to libreoffice-core 3.5.2 version, I stumbled upon what seems to be a bad download issue: Preparing to replace libreoffice-core 1:3.5.1-1ubuntu5 (using .../libreoffice-core_1%3a3.5.2-2ubuntu1_amd64.deb) ... rmdir: failed to remove `/var/lib/libreoffice/basis3.4/program/': No such file or directory rmdir: failed to remove `/var/lib/libreoffice/basis3.4': No such file or directory Unpacking replacement libreoffice-core ... dpkg-deb (subprocess): data: internal bzip2 read error: 'DATA_ERROR' dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing /var/cache/apt/archives/libreoffice-core_1%3a3.5.2-2ubuntu1_amd64.deb (--unpack): subprocess dpkg-deb --fsys-tarfile returned error exit status 2 I was asked to file a bug about it, as it might be possible for dpkg to recover from that more gracefully. Further information upon requests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/978587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930139] [NEW] the --no-directories option incorrectly documented in the man page
Public bug reported: man page shows: -nd --no-directories Do not create a hierarchy of directories when retrieving recursively. With this option turned on, all files will get saved to the current directory, without clobbering (if a name shows up more than once, the filenames will get extensions .n). The way that's written implies that the -nd option would conflict with the -P option. But when -nd is combined with --directory-prefix (-P), wget honors the prefix and also downloads to a flat non-hierarchical "structure". The behavior is sensible but the docs are wrong (-nd does not necessarily download to the current dir). ** Affects: wget (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1930139 Title: the --no-directories option incorrectly documented in the man page Status in wget package in Ubuntu: New Bug description: man page shows: -nd --no-directories Do not create a hierarchy of directories when retrieving recursively. With this option turned on, all files will get saved to the current directory, without clobbering (if a name shows up more than once, the filenames will get extensions .n). The way that's written implies that the -nd option would conflict with the -P option. But when -nd is combined with --directory-prefix (-P), wget honors the prefix and also downloads to a flat non-hierarchical "structure". The behavior is sensible but the docs are wrong (-nd does not necessarily download to the current dir). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1930139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1929087] Re: sfdisk refuses to write GPT table between sector 34 and 2047
A secondary bug manifests from this, whereby sfdisk chokes on its own output and therefore cannot restore its own backup. E.g. suppose another tool is used to put a BIOS boot partition from sector 34 to 2047, as follows: $ sgdisk --clear -a 1 --new=1:34:2047 -c 1:"BIOS boot" --typecode=1:$(sgdisk --list-types | sed -ne 's/.*\(\).bios.*/\1/gip') /dev/sdb That works fine, and from that we can run "sfdisk -d /dev/sdb > dump.txt". But when dump.txt is fed back into sfdisk, it pukes. Yet the docs claim "It is recommended to save the layout of your devices. sfdisk supports two ways." .. "Use the --dump option to save a description of the device layout to a text file." .. "This can later be restored by: sfdisk /dev/sda < sda.dump" It's actually a security issue, because someone can make an non- restorable backup and have the false sense of security that it is restorable. They wouldn't necessary test restoration either because that's a destructive process. ** Description changed: According to https://wiki.archlinux.org/title/GRUB#BIOS_systems, it's both legal and interesting to place the BIOS BOOT partition from sector 34 to sector 2047, as follows: $ sudo sfdisk --no-act -f --label gpt /dev/sdb << EOF start= 34, size=2013, name=bios, type=$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /bios boot/{print $1}') start= 2048, size=12582912, name=swap, type=$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux swap/{print $1}') EOF The output is: /dev/sdb1: Sector 34 already used. Failed to add #1 partition: Numerical result out of range Leaving. - It's a false error. As a workaround, users must omit the BIOS BOOT - partition then use gdisk to insert it manually. This was uncovered in - 2015 and perhaps never reported to a bug tracker because it's still - broken. See https://www.spinics.net/lists/util-linux-ng/msg11253.html + It's a false error. As a workaround, users must use parted or sgdisk + instead. (note fdisk & gdisk are also broken in the same way) + + This bug was uncovered in 2015 and perhaps never reported to a bug + tracker because it's still broken. See https://www.spinics.net/lists + /util-linux-ng/msg11253.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1929087 Title: sfdisk refuses to write GPT table between sector 34 and 2047 Status in util-linux package in Ubuntu: New Bug description: According to https://wiki.archlinux.org/title/GRUB#BIOS_systems, it's both legal and interesting to place the BIOS BOOT partition from sector 34 to sector 2047, as follows: $ sudo sfdisk --no-act -f --label gpt /dev/sdb << EOF start= 34, size=2013, name=bios, type=$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /bios boot/{print $1}') start= 2048, size=12582912, name=swap, type=$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux swap/{print $1}') EOF The output is: /dev/sdb1: Sector 34 already used. Failed to add #1 partition: Numerical result out of range Leaving. It's a false error. As a workaround, users must use parted or sgdisk instead. (note fdisk & gdisk are also broken in the same way) This bug was uncovered in 2015 and perhaps never reported to a bug tracker because it's still broken. See https://www.spinics.net/lists /util-linux-ng/msg11253.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1929087/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1929087] [NEW] sfdisk refuses to write GPT table between sector 34 and 2047
Public bug reported: According to https://wiki.archlinux.org/title/GRUB#BIOS_systems, it's both legal and interesting to place the BIOS BOOT partition from sector 34 to sector 2047, as follows: $ sudo sfdisk --no-act -f --label gpt /dev/sdb << EOF start= 34, size=2013, name=bios, type=$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /bios boot/{print $1}') start= 2048, size=12582912, name=swap, type=$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux swap/{print $1}') EOF The output is: /dev/sdb1: Sector 34 already used. Failed to add #1 partition: Numerical result out of range Leaving. It's a false error. As a workaround, users must omit the BIOS BOOT partition then use gdisk to insert it manually. This was uncovered in 2015 and perhaps never reported to a bug tracker because it's still broken. See https://www.spinics.net/lists/util-linux-ng/msg11253.html ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1929087 Title: sfdisk refuses to write GPT table between sector 34 and 2047 Status in util-linux package in Ubuntu: New Bug description: According to https://wiki.archlinux.org/title/GRUB#BIOS_systems, it's both legal and interesting to place the BIOS BOOT partition from sector 34 to sector 2047, as follows: $ sudo sfdisk --no-act -f --label gpt /dev/sdb << EOF start= 34, size=2013, name=bios, type=$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /bios boot/{print $1}') start= 2048, size=12582912, name=swap, type=$(sfdisk --label gpt -T | awk '{IGNORECASE = 1;} /linux swap/{print $1}') EOF The output is: /dev/sdb1: Sector 34 already used. Failed to add #1 partition: Numerical result out of range Leaving. It's a false error. As a workaround, users must omit the BIOS BOOT partition then use gdisk to insert it manually. This was uncovered in 2015 and perhaps never reported to a bug tracker because it's still broken. See https://www.spinics.net/lists/util-linux-ng/msg11253.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1929087/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925973] Re: Nvidia driver 450.119 crashes lxpanel on Ubuntu 18.04
** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1925973 Title: Nvidia driver 450.119 crashes lxpanel on Ubuntu 18.04 Status in xorg package in Ubuntu: Invalid Bug description: Running Ubuntu 18.04 with the LXDE desktop. After installing the Nvidia driver version 450.119 and rebooting, the LXDE desktop crashes, specifically lxpanel. Reloaded clonezilla clone of / with Nvidia driver 450.102, all is well again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-72.80~18.04.1-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.102.04 Tue Dec 29 06:51:23 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: LXDE Date: Fri Apr 23 15:46:27 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 450.102.04, 5.4.0-67-generic, x86_64: installed nvidia, 450.102.04, 5.4.0-70-generic, x86_64: installed nvidia, 450.102.04, 5.4.0-72-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6253] InstallationDate: Installed on 2018-04-27 (1092 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=0ca22edb-e6b0-412b-ad6e-00b2126b37c7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD 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.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: M11AD dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1925973/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925973] [NEW] Nvidia driver 450.119 crashes lxpanel on Ubuntu 18.04
Public bug reported: Running Ubuntu 18.04 with the LXDE desktop. After installing the Nvidia driver version 450.119 and rebooting, the LXDE desktop crashes, specifically lxpanel. Reloaded clonezilla clone of / with Nvidia driver 450.102, all is well again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-72.80~18.04.1-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.102.04 Tue Dec 29 06:51:23 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: LXDE Date: Fri Apr 23 15:46:27 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 450.102.04, 5.4.0-67-generic, x86_64: installed nvidia, 450.102.04, 5.4.0-70-generic, x86_64: installed nvidia, 450.102.04, 5.4.0-72-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6253] InstallationDate: Installed on 2018-04-27 (1092 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=0ca22edb-e6b0-412b-ad6e-00b2126b37c7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD 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.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: M11AD dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu ** Description changed: Running Ubuntu 18.04 with the LXDE desktop. - After installing the Nvidia driver version 150.119 and rebooting, the + After installing the Nvidia driver version 450.119 and rebooting, the LXDE desktop crashes, specifically lxpanel. Reloaded clonezilla clone of / with Nvidia driver 150.102, all is well again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-72.80~18.04.1-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.102.04 Tue Dec 29 06:51:23 UTC 2020 - GCC version: gcc version 7.5.0 (Ubuntu
[Touch-packages] [Bug 1925381] Re: rsync conceals file deletions from reporting when --dry-run --remove-source-files are used together
For me the fact that the upstream repo moved from bugzilla.samba.org to github.com is sufficient to diverge from upstream. But to each his own. My contempt for github is in fact why I reported the bug downstream. I will not use github but I still intended to make a public record of the bug, hence why it's here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1925381 Title: rsync conceals file deletions from reporting when --dry-run --remove- source-files are used together Status in rsync package in Ubuntu: Triaged Bug description: Rsync has an astonishing and dangerous bug: The dry run feature (-n / --dry-run) inhibits reporting of file deletions when --remove-source-files is used. This is quite serious. People use --dry-run to see if an outcome will work as expected before a live run. When the simulated run shows *less* destruction than the live run, the consequences can be serious because rsync may unexpectedly destroy the only copy(*) of a file. Users rely on --dry-run. Although users probably expect --dry-run to have limitations, we don't expect destructive operations to be under reported. If it were reversed, such that the live run were less destructive than the dry run, this wouldn't be as serious. Reproducer: $ mkdir -p /tmp/src /tmp/dest $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt $ cp /tmp/src/foo.txt /tmp/dest $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt foo.txt $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/ (no output) $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/ sender removed foo.txt $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt (*) note when I say it can destroy the only copy of a file, another circumstance is needed: that is, rsync does not do a checksum by default. It checks for identical files based on superficial parameters like name and date. So it's possible that two files match in the default superficial comparison but differ in the actual content. Losing a unique file in this scenario is perhaps a rare corner case, but this bug should be fixed nonetheless. In the typical case of losing files at the source, there is still a significant inconvenience of trying to identify what files to copy back. Note this bug is similar but differs in a few ways: https://bugzilla.samba.org/show_bug.cgi?id=3844 I've marked this as a security vulnerability because it causes unexpected data loss due to --dry-run creating a false expectation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1925381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925381] Re: rsync conceals file deletions from reporting when --dry-run --remove-source-files are used together
** Description changed: Rsync has an astonishing and dangerous bug: The dry run feature (-n / --dry-run) fails to report file deletions when --remove-source-files is used. This is quite serious. People use --dry- run to see if an outcome will work as expected before a live run. When the simulated run shows *less* destruction than the live run, the consequences can be serious because rsync may unexpectedly destroy the - only copy of a file. + only copy(*) of a file. Users rely on --dry-run. Although users probably expect --dry-run to have limitations, we don't expect destructive operations to be under reported. If it were reversed, such that the live run were less destructive than the dry run, this wouldn't be as serious. Reproducer: $ mkdir -p /tmp/src /tmp/dest $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt $ cp /tmp/src/foo.txt /tmp/dest $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt foo.txt $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/ (no output) $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/ sender removed foo.txt $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt + (*) note when I say it can destroy the only copy of a file, another + circumstance is needed: that is, rsync does not do a checksum by + default. It checks for identical files based on parameters like name + and date. So it's possible that two files match in the default + comparison but differ in the actual content. Losing a unique file in + this scenario is perhaps a rare corner case, but this bug should be + fixed nonetheless. + Note this bug is similar but differs in a few ways: https://bugzilla.samba.org/show_bug.cgi?id=3844 I've marked this as a security vulnerability because it causes unexpected data loss due to --dry-run creating a false expectation. ** Description changed: Rsync has an astonishing and dangerous bug: The dry run feature (-n / --dry-run) fails to report file deletions when --remove-source-files is used. This is quite serious. People use --dry- run to see if an outcome will work as expected before a live run. When the simulated run shows *less* destruction than the live run, the consequences can be serious because rsync may unexpectedly destroy the only copy(*) of a file. Users rely on --dry-run. Although users probably expect --dry-run to have limitations, we don't expect destructive operations to be under reported. If it were reversed, such that the live run were less destructive than the dry run, this wouldn't be as serious. Reproducer: $ mkdir -p /tmp/src /tmp/dest $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt $ cp /tmp/src/foo.txt /tmp/dest $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt foo.txt $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/ (no output) $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/ sender removed foo.txt $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt (*) note when I say it can destroy the only copy of a file, another circumstance is needed: that is, rsync does not do a checksum by - default. It checks for identical files based on parameters like name - and date. So it's possible that two files match in the default - comparison but differ in the actual content. Losing a unique file in - this scenario is perhaps a rare corner case, but this bug should be - fixed nonetheless. + default. It checks for identical files based on superficial parameters + like name and date. So it's possible that two files match in the + default superficial comparison but differ in the actual content. Losing + a unique file in this scenario is perhaps a rare corner case, but this + bug should be fixed nonetheless. Note this bug is similar but differs in a few ways: https://bugzilla.samba.org/show_bug.cgi?id=3844 I've marked this as a security vulnerability because it causes unexpected data loss due to --dry-run creating a false expectation. ** Description changed: Rsync has an astonishing and dangerous bug: - The dry run feature (-n / --dry-run) fails to report file deletions when - --remove-source-files is used. This is quite serious. People use --dry- - run to see if an outcome will work as expected before a live run. When - the simulated run shows *less* destruction than the live run, the - consequences can be serious because rsync may unexpectedly destroy the - only copy(*) of a file. + The dry run feature (-n / --dry-run) inhibits reporting of file + deletions when --remove-source-files is used. This is quite serious. + People use --dry-run to see if an outcome will work as expected before a + live run. When the simulated run shows
[Touch-packages] [Bug 1925381] [NEW] rsync conceals file deletions from reporting when --dry-run --remove-source-files are used together
Public bug reported: Rsync has an astonishing and dangerous bug: The dry run feature (-n / --dry-run) fails to report file deletions when --remove-source-files is used. This is quite serious. People use --dry- run to see if an outcome will work as expected before a live run. When the simulated run shows *less* destruction than the live run, the consequences can be serious because rsync may unexpectedly destroy the only copy of a file. Users rely on --dry-run. Although users probably expect --dry-run to have limitations, we don't expect destructive operations to be under reported. If it were reversed, such that the live run were less destructive than the dry run, this wouldn't be as serious. Reproducer: $ mkdir -p /tmp/src /tmp/dest $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt $ cp /tmp/src/foo.txt /tmp/dest $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt foo.txt $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/ (no output) $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/ sender removed foo.txt $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt Note this bug is similar but differs in a few ways: https://bugzilla.samba.org/show_bug.cgi?id=3844 I've marked this as a security vulnerability because it causes unexpected data loss due to --dry-run creating a false expectation. ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1925381 Title: rsync conceals file deletions from reporting when --dry-run --remove- source-files are used together Status in rsync package in Ubuntu: New Bug description: Rsync has an astonishing and dangerous bug: The dry run feature (-n / --dry-run) fails to report file deletions when --remove-source-files is used. This is quite serious. People use --dry-run to see if an outcome will work as expected before a live run. When the simulated run shows *less* destruction than the live run, the consequences can be serious because rsync may unexpectedly destroy the only copy of a file. Users rely on --dry-run. Although users probably expect --dry-run to have limitations, we don't expect destructive operations to be under reported. If it were reversed, such that the live run were less destructive than the dry run, this wouldn't be as serious. Reproducer: $ mkdir -p /tmp/src /tmp/dest $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt $ cp /tmp/src/foo.txt /tmp/dest $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt foo.txt $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/ (no output) $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/ sender removed foo.txt $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt Note this bug is similar but differs in a few ways: https://bugzilla.samba.org/show_bug.cgi?id=3844 I've marked this as a security vulnerability because it causes unexpected data loss due to --dry-run creating a false expectation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1925381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916931] Re: omshell returns inconsistent results or segfaults
I imported version 4.4.2 from upstream and built for focal. The problem persists. OMAPI failover queries work sometimes and fail most of the time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults Status in isc-dhcp package in Ubuntu: New Bug description: I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail. Here is the initial, working, session: # omshell > server localhost > port 7911 > key omapi_key > connect obj: > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00 Here is what I see when the connect fails. Well, just hangs really. # omshell > server localhost > port 7911 > key omapi_key > connect And then I hit ctrl-c to break out and tried again: # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the peer to this server is still running Ubuntu 18.04 with isc-dhcp-server 4.3.5. Running the exact same commands on the peer works reliably. (They are using the same python script to drive omshell.) The DHCP server on the new system appears to be working just fine as reported by omshell on the peer and systemctl. I was curious if the problem could be with the mis-matched versions of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system and get the same results. I also tried using a python script with the pypureomapi module to try and determine if the problem was in omshell or the server. I got very similar results when I attempted to get information about the failover state of the server. Interestingly interrogating the server about host information seems to work just fine. This is a critical bug since I don't see how to fail over a DHCP that is running the isc-dhcp-server on 20.04 without being able to issue omapi commands. I am attaching apport output to this bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1916931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917183] Re: Font spacing and rendering is wrong in latest 21.04
** Changed in: fonts-noto-color-emoji (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1917183 Title: Font spacing and rendering is wrong in latest 21.04 Status in Ubuntu MATE: Confirmed Status in firefox package in Ubuntu: Confirmed Status in fontconfig package in Ubuntu: Confirmed Status in fonts-noto-color-emoji package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: Ubuntu MATE 21.04 Font spacing is incorrect. Including screen shots of pages. This front spacing issue is occurring whilst filing this bug report on Launchpad. Expected outcome: Font's space and render properly in Firefox Actual outcome: Font space and render is incorrect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 86.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: franksmcb 2695 F pulseaudio BuildID: 20210222142601 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: MATE Date: Sat Feb 27 16:50:33 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2019-12-13 (442 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20191213) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.154 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348 Profile0PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=77.0/20200528194502 (Out of date) Profile0 - LastVersion=86.0/20210222142601 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2020-06-02 (270 days ago) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GBU dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2347GBU:pvrThinkPadT430:rvnLENOVO:rn2347GBU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GBU dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1917183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916931] [NEW] omshell returns inconsistent results or segfaults
Public bug reported: I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail. Here is the initial, working, session: # omshell > server localhost > port 7911 > key omapi_key > connect obj: > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00 Here is what I see when the connect fails. Well, just hangs really. # omshell > server localhost > port 7911 > key omapi_key > connect And then I hit ctrl-c to break out and tried again: # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the peer to this server is still running Ubuntu 18.04 with isc-dhcp-server 4.3.5. Running the exact same commands on the peer works reliably. (They are using the same python script to drive omshell.) The DHCP server on the new system appears to be working just fine as reported by omshell on the peer and systemctl. I was curious if the problem could be with the mis-matched versions of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system and get the same results. I also tried using a python script with the pypureomapi module to try and determine if the problem was in omshell or the server. I got very similar results when I attempted to get information about the failover state of the server. Interestingly interrogating the server about host information seems to work just fine. This is a critical bug since I don't see how to fail over a DHCP that is running the isc-dhcp-server on 20.04 without being able to issue omapi commands. I am attaching apport output to this bug report. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Attachment added: "omapi-failures.apport" https://bugs.launchpad.net/bugs/1916931/+attachment/5467107/+files/omapi-failures.apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1916931 Title: omshell returns inconsistent results or segfaults Status in isc-dhcp package in Ubuntu: New Bug description: I have just built a Ubuntu 20.04 server and installed isc-dhcp-server 4.4.1 on it and I am seeing inconsistent returns from omshell. Initially omshell returns data as expected, but when I exit and re-enter omshell connections fail. Here is the initial, working, session: # omshell > server localhost > port 7911 > key omapi_key > connect obj: > new failover-state obj: failover-state > set name = "dhcp-failover" obj: failover-state name = "dhcp-failover" > open obj: failover-state name = "dhcp-failover" partner-address = c0:9d:e9:76:e9:55:00:00 partner-port = 00:00:02:07 local-address = 10:9d:e9:76:e9:55:00:00 local-port = 00:00:02:07 max-outstanding-updates = 00:00:00:0a mclt = 00:00:01:2c load-balance-max-secs = 00:00:00:03 load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 partner-state = 00:00:00:02 local-state = 00:00:00:02 partner-stos = 60:36:d0:68 local-stos = 60:36:8b:3b hierarchy = 00:00:00:01 last-packet-sent = 00:00:00:00 last-timestamp-received = 00:00:00:00 skew = 00:00:00:00 max-response-delay = 00:00:00:3c cur-unacked-updates = 00:00:00:00 Here is what I see when the connect fails. Well, just hangs really. # omshell > server localhost > port 7911 > key omapi_key > connect And then I hit ctrl-c to break out and tried again: # omshell > server localhost > port 7911 > key omapi_key > connect Segmentation fault (core dumped) Note, the peer to this server is still running Ubuntu 18.04 with isc-dhcp-server 4.3.5. Running the exact same commands on the peer works reliably. (They are using the same python script to drive omshell.) The DHCP server on the new system appears to be working just fine as reported by omshell on the peer and systemctl. I was curious if the problem could be with the mis-matched versions of isc-dhcp-server so I shutdown isc-dhcp-server on the
[Touch-packages] [Bug 1916341] [NEW] poppler-utils/pdfimages list function names the wrong color in output table
Public bug reported: When running: $ pdfimages -list grayscale-document.pdf the output is: ``` page num type width height color comp bpc enc interp object ID x-ppi y-ppi size ratio 1 0 image2556 3288 rgb 3 8 jpeg no 7 0 301 300 200K 0.8% 2 1 image2556 3288 rgb 3 8 jpeg no12 0 301 300 275K 1.5% 3 2 image2556 3288 rgb 3 8 jpeg no17 0 301 300 395K 0.8% 4 3 image2556 3288 rgb 3 8 jpeg no22 0 301 300 583K 2.8% 5 4 image2556 3288 rgb 3 8 jpeg no27 0 301 300 317K 1.3% ... ``` "rgb" is incorrect, which is evident after running: 'pdfimages -all -f 1 -l 1 grayscale-document.pdf foo && identify -format "%[type]" foo-000.jpg', which correctly outputs "Grayscale". Strangely, when "pdfimages -list" is fed a bilevel document, it states that every page has color "gray". ** Affects: poppler (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1916341 Title: poppler-utils/pdfimages list function names the wrong color in output table Status in poppler package in Ubuntu: New Bug description: When running: $ pdfimages -list grayscale-document.pdf the output is: ``` page num type width height color comp bpc enc interp object ID x-ppi y-ppi size ratio 1 0 image2556 3288 rgb 3 8 jpeg no 7 0 301 300 200K 0.8% 2 1 image2556 3288 rgb 3 8 jpeg no12 0 301 300 275K 1.5% 3 2 image2556 3288 rgb 3 8 jpeg no17 0 301 300 395K 0.8% 4 3 image2556 3288 rgb 3 8 jpeg no22 0 301 300 583K 2.8% 5 4 image2556 3288 rgb 3 8 jpeg no27 0 301 300 317K 1.3% ... ``` "rgb" is incorrect, which is evident after running: 'pdfimages -all -f 1 -l 1 grayscale-document.pdf foo && identify -format "%[type]" foo-000.jpg', which correctly outputs "Grayscale". Strangely, when "pdfimages -list" is fed a bilevel document, it states that every page has color "gray". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1916341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
Some follow-up with users from the Ubuntu MATE Community forums show that this is occurring on Focal and Groovy; with 5.4, 5.8, and 5.10 kernels. Following is a list of hardware and graphics information from affected users: System: Host: huppyryzen Kernel: 5.4.0-54-generic x86_64 bits: 64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x serial: UEFI: American Megatrends v: 5602 date: 07/14/2020 Graphics: Device-1: AMD Vega 10 XL/XT [Radeon RX Vega 56/64] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 3440x1440~60Hz OpenGL: renderer: Radeon RX Vega (VEGA10 DRM 3.35.0 5.4.0-54-generic LLVM 11.0.0) v: 4.6 Mesa 20.3.0-rc2 System: Host: marptop Kernel: 5.4.0-54-generic x86_64 bits: 64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: HP product: HP Laptop 17-ca0xxx v: N/A serial: Mobo: HP model: 84D2 v: 91.17 serial: UEFI: AMI v: F.21 date: 11/15/2018 Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1600x900~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.35.0 5.4.0-54-generic LLVM 10.0.0) v: 4.6 Mesa 20.0.8 System: Host: duck-laptop2 Kernel: 5.8.0-29-generic x86_64 bits: 64 Desktop: MATE 1.24.1 Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Laptop System: HP product: HP Laptop 15-db0xxx v: Type1ProductConfigId serial: Mobo: HP model: 84AE v: 86.20 serial: UEFI: Insyde v: F.10 date: 05/31/2018 Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] driver: amdgpu v: kernel Device-2: Lite-On 1351 type: USB driver: uvcvideo Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.38.0 5.8.0-29-generic LLVM 11.0.0) v: 4.6 Mesa 20.2.1 System: Host: jgjmate-ThinkPad-E595 Kernel: 5.8.0-32-generic x86_64 bits: 64 Desktop: MATE 1.24.1 Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Laptop System: LENOVO product: 20NF0012US v: ThinkPad E595 serial: Mobo: LENOVO model: 20NF0012US serial: UEFI: LENOVO v: R11ET39W (1.19 ) date: 09/11/2020 Graphics: Device-1: AMD Picasso driver: amdgpu v: kernel Device-2: Acer SunplusIT Integrated Camera type: USB driver: uvcvideo Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.38.0 5.8.0-32-generic LLVM 11.0.0) v: 4.6 Mesa 20.2.1 System: Host: Kernel: 5.4.0-58-generic x86_64 bits: 64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Laptop System: HP product: HP Laptop 15-db0xxx v: Type1ProductConfigId serial: Mobo: HP model: 84AC v: 85.26 serial: UEFI: Insyde v: F.22 date: 11/06/2019 Graphics: Device-1: AMD Stoney [Radeon R2/R3/R4/R5 Graphics] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD STONEY (DRM 3.35.0 5.4.0-58-generic LLVM 10.0.0) v: 4.5 Mesa 20.0.8 System: Host: pc Kernel: 5.4.0-58-generic x86_64 bits: 64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: MSI model: B75MA-P45 (MS-7798) v: 1.0 serial: BIOS: American Megatrends v: 1.9 date: 09/30/2013 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.38.0 5.4.0-58-generic LLVM 11.0.0) v: 4.6 Mesa 21.0.0-devel (git-6a34a68 2020-12-13 focal-oibaf-ppa) System: Host: ACER-xk2308 Kernel: 5.10.4-051004-generic x86_64 bits: 64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Desktop Mobo: MSI model: B75MA-P45 (MS-7798) v: 1.0 serial: BIOS: American Megatrends v: 1.9 date: 09/30/2013 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.40.0 5.10.4-051004-generic LLVM 11.0.0) v: 4.6 Mesa 21.0.0-devel (git-24dcdc3 2021-01-04 focal-oibaf-ppa) System: Host: ACER-xk2308 Kernel: 5.8.0-38-generic
[Touch-packages] [Bug 1903199] Re: systemd version 237-3ubuntu10.43 causes 32 bit Lubuntu 18.04 login to fail
*** This bug is a duplicate of bug 1890394 *** https://bugs.launchpad.net/bugs/1890394 Sounds right, thanks! I was morally certain it would have been reported previously, but I couldn't find it. -- 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/1903199 Title: systemd version 237-3ubuntu10.43 causes 32 bit Lubuntu 18.04 login to fail Status in systemd package in Ubuntu: New Bug description: After installing routine updates including systemd version 237-3ubuntu10.43 this 32 bit Lubuntu 18.04 booted to a black screen with a blinking cursor. I booted to recovery mode and removed the systemd update. This gave me a normal boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.38 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.19 Architecture: i386 CurrentDesktop: LXDE Date: Thu Nov 5 13:20:12 2020 InstallationDate: Installed on 2020-11-05 (0 days ago) InstallationMedia: Lubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) MachineType: Hewlett-Packard Compaq Mini 110c-1100 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=fe274718-dc90-49c2-90f4-fb2d29b46d89 ro recovery nomodeset dis_ucode_ldr SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 308F0 Ver. F.19 dmi.board.name: 308F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 02.10 dmi.chassis.asset.tag: CNU9424KL9 dmi.chassis.type: 10 dmi.chassis.vendor: Inventec dmi.modalias: dmi:bvnHewlett-Packard:bvr308F0Ver.F.19:bd01/12/2010:svnHewlett-Packard:pnCompaqMini110c-1100:pvr039411001C030:rvnHewlett-Packard:rn308F:rvrKBCVersion02.10:cvnInventec:ct10:cvr: dmi.product.family: 103C_5335KV dmi.product.name: Compaq Mini 110c-1100 dmi.product.sku: VM146UA#ABA dmi.product.version: 039411001C030 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1903199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903199] [NEW] systemd version 237-3ubuntu10.43 causes 32 bit Lubuntu 18.04 login to fail
Public bug reported: After installing routine updates including systemd version 237-3ubuntu10.43 this 32 bit Lubuntu 18.04 booted to a black screen with a blinking cursor. I booted to recovery mode and removed the systemd update. This gave me a normal boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.38 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.19 Architecture: i386 CurrentDesktop: LXDE Date: Thu Nov 5 13:20:12 2020 InstallationDate: Installed on 2020-11-05 (0 days ago) InstallationMedia: Lubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) MachineType: Hewlett-Packard Compaq Mini 110c-1100 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=fe274718-dc90-49c2-90f4-fb2d29b46d89 ro recovery nomodeset dis_ucode_ldr SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 308F0 Ver. F.19 dmi.board.name: 308F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 02.10 dmi.chassis.asset.tag: CNU9424KL9 dmi.chassis.type: 10 dmi.chassis.vendor: Inventec dmi.modalias: dmi:bvnHewlett-Packard:bvr308F0Ver.F.19:bd01/12/2010:svnHewlett-Packard:pnCompaqMini110c-1100:pvr039411001C030:rvnHewlett-Packard:rn308F:rvrKBCVersion02.10:cvnInventec:ct10:cvr: dmi.product.family: 103C_5335KV dmi.product.name: Compaq Mini 110c-1100 dmi.product.sku: VM146UA#ABA dmi.product.version: 039411001C030 dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- 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/1903199 Title: systemd version 237-3ubuntu10.43 causes 32 bit Lubuntu 18.04 login to fail Status in systemd package in Ubuntu: New Bug description: After installing routine updates including systemd version 237-3ubuntu10.43 this 32 bit Lubuntu 18.04 booted to a black screen with a blinking cursor. I booted to recovery mode and removed the systemd update. This gave me a normal boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.38 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.19 Architecture: i386 CurrentDesktop: LXDE Date: Thu Nov 5 13:20:12 2020 InstallationDate: Installed on 2020-11-05 (0 days ago) InstallationMedia: Lubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) MachineType: Hewlett-Packard Compaq Mini 110c-1100 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=fe274718-dc90-49c2-90f4-fb2d29b46d89 ro recovery nomodeset dis_ucode_ldr SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 308F0 Ver. F.19 dmi.board.name: 308F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 02.10 dmi.chassis.asset.tag: CNU9424KL9 dmi.chassis.type: 10 dmi.chassis.vendor: Inventec dmi.modalias: dmi:bvnHewlett-Packard:bvr308F0Ver.F.19:bd01/12/2010:svnHewlett-Packard:pnCompaqMini110c-1100:pvr039411001C030:rvnHewlett-Packard:rn308F:rvrKBCVersion02.10:cvnInventec:ct10:cvr: dmi.product.family: 103C_5335KV dmi.product.name: Compaq Mini 110c-1100 dmi.product.sku: VM146UA#ABA dmi.product.version: 039411001C030 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1903199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897934] Re: [SRU][Intel HDA] The initial sound level is set to zero (muted)
This is confirmed working correctly on Ubuntu MATE with 20201022 re- spin. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) Status in Release Notes for Ubuntu: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] Fail to run '/usr/sbin/alsactl restore' on the HDA-Intel machines, this results in the failure on setting the init mixer values for HDA sound card, and users experience the mute of audio after installing the 20.10. [Fix] Backport a patch from the latest alsa-lib (v1.2.3+) [Test] Without the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is muted. Install the patched alsa-lib, rm ~/.config/pulse/*;sudo rm /var/lib/alsa/*; sudo sh -c "echo b > /proc/sysrq-trigger", after booting up, the audio is not muted. [Regression Potential] This could make the ucm audio fail to initialize, but this possibility is very low, since this patch is from upstream, and I tested on a ucm based machine, the audio is good. On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 20.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: BugDistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897934] Re: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute)
This breaks Screen Reader installs for Visually impaired users and breaks testcase #1305 -- 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/1897934 Title: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute) Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 18.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897934] Re: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute)
This is occurring on 20.10 Ubuntu MATE 20201021.2 -- 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/1897934 Title: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute) Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: On boot into the live session - or on first install the sound level is muted. I have to use GNOME Control Center - Sounds to change to an appropriate level. Once changed the level chosen is correctly retained between reboots. This appears to be a regression from 18.04 where the sound level was set to - I guess - 80% on the live-session/first install ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu-budgie 5041 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: Budgie:GNOME Date: Wed Sep 30 16:03:08 2020 LiveMediaBuild: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2016 dmi.bios.release: 15.31 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.22 dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:br15.31:efr95.22:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 910272] Re: USB->Parallel adapter produces crappy device URI and CUPS "usb" backend cannot cope with it
Same problem for me. I have an old parallel-only printer. It has been working with a dedicated printer server, but the printer server died and the PC has no parallel port. So I connected a USB-to-LPT cable. As I attach the cable /var/log/syslog shows: parport0: fix this legacy no-device port driver! lp0: using parport0 (polling) There does not exist a /dev/usb/lp0. I still set "DeviceURI parallel:/dev/usb/lp0" since that is what the instructions still say (https://wiki.ubuntu.com/DebuggingPrintingProblems#USB_-.3E_Parallel_adapter), and indeed that fails. I also tried "DeviceURI parallel:/dev/parport0" and CUPS rejected it. Then I tried "DeviceURI parallel:/dev/lp0". CUPS accepted it, I sent a test print, and it just sits on the job queue with the msg "Printer not connected; will retry in 30 seconds". # usb_printerid /dev/lp0 Error: Invalid argument: GET_DEVICE_ID on '/dev/lp0' # usb_printerid /dev/parport0 Error: Invalid argument: GET_DEVICE_ID on '/dev/parport0' At another moment, I got a different error: # usb_printerid /dev/lp0 Error: Device or resource busy: can't open '/dev/lp0' This is on Bionic. -- 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/910272 Title: USB->Parallel adapter produces crappy device URI and CUPS "usb" backend cannot cope with it Status in cups package in Ubuntu: Fix Released Status in cups source package in Oneiric: Won't Fix Bug description: Parallel port dot matrix printer Panasonic KX-P2124 connected via usb- parallel cable to HP6600 PC; running Ubuntu 11.10 system located on external hard drive attached by usb. Worked on Ubuntu version 8 using URI "parallel:/dev/usb/lp0". Understand that usblp has been deprecated; replace with ??? Cups reports printer not connected. CUPS version is (from UbuntuSoftwareCenter) - "cups 1.5.0-8ubuntu6". #Researched existing bugs - lots of info - no results. No "Help" menu found by selecting upper right located "Gear"/"Printers; could not find any "Wizard." Thank you for your assistance, nvsoar w8@w8-FJ463AAR-ABA-a6528p:~$ uname -a Linux w8-FJ463AAR-ABA-a6528p 3.0.0-15-generic #24-Ubuntu SMP Mon Dec 12 15:25:25 UTC 2011 i686 i686 i386 GNU/Linux w8@w8-FJ463AAR-ABA-a6528p:~$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 067b:3507 Prolific Technology, Inc. PL3507 ATAPI6 Bridge Bus 001 Device 004: ID 058f:6377 Alcor Micro Corp. Multimedia Card Reader Bus 002 Device 002: ID 050d:0002 Belkin Components #Device immediately above is usb to parallel cable w8@w8-FJ463AAR-ABA-a6528p:~$ lsmod | grep lp lp 17455 0 parport40930 4 parport_pc,ppdev,uss720,lp w8@w8-FJ463AAR-ABA-a6528p:~$ lsmod | grep ppdev ppdev 12849 0 parport40930 4 parport_pc,ppdev,uss720,lp w8@w8-FJ463AAR-ABA-a6528p:~$ lsmod | grep parport_pc parport_pc 32114 0 parport40930 4 parport_pc,ppdev,uss720,lp w8@w8-FJ463AAR-ABA-a6528p:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/* ls: cannot access /dev/usb/lp*: No such file or directory crw-rw-r-- 1 root root 189, 0 2011-12-30 15:04 /dev/bus/usb/001/001 crw-rw-r-- 1 root root 189, 1 2011-12-30 15:04 /dev/bus/usb/001/002 crw-rw-r-- 1 root root 189, 3 2011-12-30 15:04 /dev/bus/usb/001/004 crw-rw-r-- 1 root root 189, 128 2011-12-30 15:04 /dev/bus/usb/002/001 crw-rw-r-- 1 root lp 189, 129 2011-12-30 15:25 /dev/bus/usb/002/002 w8@w8-FJ463AAR-ABA-a6528p:~$ dmesg | grep par [0.00] Booting paravirtualized kernel on bare hardware [0.00] vt handoff: transparent VT on vt#7 [0.210399] hpet0: 3 comparators, 32-bit 25.00 MHz counter [ 28.754567] uss720: protocols (eg. bitbang) over USS720 usb to parallel cables [ 28.893725] type=1400 audit(1325286282.534:2): apparmor="STATUS" operation="profile_load" name="/sbin/dhclient" pid=705 comm="apparmor_parser" [ 28.893736] type=1400 audit(1325286282.534:3): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=755 comm="apparmor_parser" [ 28.894175] type=1400 audit(1325286282.534:4): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=755 comm="apparmor_parser" [ 28.894324] type=1400 audit(1325286282.534:5): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=705 comm="apparmor_parser" [ 28.894438] type=1400 audit(1325286282.534:6): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=755 comm="apparmor_parser" [ 28.894592] type=1400 audit(1325286282.534:7): apparmor="STATUS" operation="profile_replace"
[Touch-packages] [Bug 1890836] Re: udev rule read but "RUN" command is not executed
Bug report to improve debugging output: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890890 -- 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/1890836 Title: udev rule read but "RUN" command is not executed Status in systemd package in Ubuntu: Invalid Bug description: The following was introduced as "/etc/udev/rules.d/99-harvest_camera.rules": ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D", RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh" When the device is attached, it gets mounted but the harvest_camera.sh script does not execute. The udev_log=debug parameter is set in /etc/udev/udev.conf. Verbosity was also maximized by running "udevadm control --log-priority=debug". After running "udevadm monitor --environment --udev", the drive was attached. The output shows a device being created (/dev/sda1) and the UUID in the rule matches. But the script simply never executes. The /var/log/syslog file shows: " Reading rules file: /etc/udev/rules.d/99-harvest_camera.rules Successfully forked off 'n/a' as PID 2201. 1-2.3: Worker [2201] is forced for rocessing SEQNUM=7973. " So the logs make it look as though the script was executed. The script is simply a stub that does a "touch /tmp/IhaveExecuted" and a call to zenity to give a popup announcement. But none of that happens (no popup and no new file in /tmp/). With maximum verbosity, there is no way to further diagnose this. Deeper detail is needed that shows which matching criteria in the rules is being tried and what the result is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890890] [NEW] more debugging verbosity for udev rules needed
Public bug reported: I wrote a udev rule that would not trigger when expected. I spent 2 days working on it, trying to understand what the problem was. I finally figured it out -- it was a matching problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836 The most verbose output possible is with the log level set to "debug". This level of logging does not show users what criteria is being checked and what the result is. So users are working in the dark. We have to guess what udev is doing. And we're bad at it, because if we could guess correctly we probably would have written the rule correctly in the first place. Consider procmail. This is an application where users write rules that contain matching criteria. When Procmail doesn't work as expected, the logs show in detail what criteria matches and what does not. This is what udev needs. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890890 Title: more debugging verbosity for udev rules needed Status in systemd package in Ubuntu: New Bug description: I wrote a udev rule that would not trigger when expected. I spent 2 days working on it, trying to understand what the problem was. I finally figured it out -- it was a matching problem: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836 The most verbose output possible is with the log level set to "debug". This level of logging does not show users what criteria is being checked and what the result is. So users are working in the dark. We have to guess what udev is doing. And we're bad at it, because if we could guess correctly we probably would have written the rule correctly in the first place. Consider procmail. This is an application where users write rules that contain matching criteria. When Procmail doesn't work as expected, the logs show in detail what criteria matches and what does not. This is what udev needs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890836] Re: udev rule read but "RUN" command is not executed
PEBKAC ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Bill Yikes (yik3s) -- 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/1890836 Title: udev rule read but "RUN" command is not executed Status in systemd package in Ubuntu: Invalid Bug description: The following was introduced as "/etc/udev/rules.d/99-harvest_camera.rules": ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D", RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh" When the device is attached, it gets mounted but the harvest_camera.sh script does not execute. The udev_log=debug parameter is set in /etc/udev/udev.conf. Verbosity was also maximized by running "udevadm control --log-priority=debug". After running "udevadm monitor --environment --udev", the drive was attached. The output shows a device being created (/dev/sda1) and the UUID in the rule matches. But the script simply never executes. The /var/log/syslog file shows: " Reading rules file: /etc/udev/rules.d/99-harvest_camera.rules Successfully forked off 'n/a' as PID 2201. 1-2.3: Worker [2201] is forced for rocessing SEQNUM=7973. " So the logs make it look as though the script was executed. The script is simply a stub that does a "touch /tmp/IhaveExecuted" and a call to zenity to give a popup announcement. But none of that happens (no popup and no new file in /tmp/). With maximum verbosity, there is no way to further diagnose this. Deeper detail is needed that shows which matching criteria in the rules is being tried and what the result is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890836] Re: udev rule read but "RUN" command is not executed
It turns out the problem arises out of cargo cult programming on my part. The bang in KERNEL=="sd*[!0-9]" is what I copied out of stackexchange, and it's exactly what prevents the mount from matching. I suspected that early on, but ruled it out because when the device first connects it must connect as /dev/sda (as the partition table must be read before there can be an sda1). Now I'm figuring the sda gets replaced with sda1 before it reaches my custom rule. In any case, the bug is not as I reported. I'm sorry this turned out to be a non-bug and I'm sorry I wasted your time Mr. Streetman. This can be closed. I may open a new bug report to improve the debug output, because we shouldn't have to work in the dark and guess about what the matching criteria is doing. -- 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/1890836 Title: udev rule read but "RUN" command is not executed Status in systemd package in Ubuntu: Invalid Bug description: The following was introduced as "/etc/udev/rules.d/99-harvest_camera.rules": ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D", RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh" When the device is attached, it gets mounted but the harvest_camera.sh script does not execute. The udev_log=debug parameter is set in /etc/udev/udev.conf. Verbosity was also maximized by running "udevadm control --log-priority=debug". After running "udevadm monitor --environment --udev", the drive was attached. The output shows a device being created (/dev/sda1) and the UUID in the rule matches. But the script simply never executes. The /var/log/syslog file shows: " Reading rules file: /etc/udev/rules.d/99-harvest_camera.rules Successfully forked off 'n/a' as PID 2201. 1-2.3: Worker [2201] is forced for rocessing SEQNUM=7973. " So the logs make it look as though the script was executed. The script is simply a stub that does a "touch /tmp/IhaveExecuted" and a call to zenity to give a popup announcement. But none of that happens (no popup and no new file in /tmp/). With maximum verbosity, there is no way to further diagnose this. Deeper detail is needed that shows which matching criteria in the rules is being tried and what the result is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890836] Re: udev rule read but "RUN" command is not executed
It fails for me on two different systems: * Ubuntu 20.04 (Focal) * Linux Mint 19.2 (Tina, which is based on Bionic) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890836 Title: udev rule read but "RUN" command is not executed Status in systemd package in Ubuntu: Incomplete Bug description: The following was introduced as "/etc/udev/rules.d/99-harvest_camera.rules": ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D", RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh" When the device is attached, it gets mounted but the harvest_camera.sh script does not execute. The udev_log=debug parameter is set in /etc/udev/udev.conf. Verbosity was also maximized by running "udevadm control --log-priority=debug". After running "udevadm monitor --environment --udev", the drive was attached. The output shows a device being created (/dev/sda1) and the UUID in the rule matches. But the script simply never executes. The /var/log/syslog file shows: " Reading rules file: /etc/udev/rules.d/99-harvest_camera.rules Successfully forked off 'n/a' as PID 2201. 1-2.3: Worker [2201] is forced for rocessing SEQNUM=7973. " So the logs make it look as though the script was executed. The script is simply a stub that does a "touch /tmp/IhaveExecuted" and a call to zenity to give a popup announcement. But none of that happens (no popup and no new file in /tmp/). With maximum verbosity, there is no way to further diagnose this. Deeper detail is needed that shows which matching criteria in the rules is being tried and what the result is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890836] [NEW] udev rule read but "RUN" command is not executed
Public bug reported: The following was introduced as "/etc/udev/rules.d/99-harvest_camera.rules": ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D", RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh" When the device is attached, it gets mounted but the harvest_camera.sh script does not execute. The udev_log=debug parameter is set in /etc/udev/udev.conf. Verbosity was also maximized by running "udevadm control --log-priority=debug". After running "udevadm monitor --environment --udev", the drive was attached. The output shows a device being created (/dev/sda1) and the UUID in the rule matches. But the script simply never executes. The /var/log/syslog file shows: " Reading rules file: /etc/udev/rules.d/99-harvest_camera.rules Successfully forked off 'n/a' as PID 2201. 1-2.3: Worker [2201] is forced for rocessing SEQNUM=7973. " So the logs make it look as though the script was executed. The script is simply a stub that does a "touch /tmp/IhaveExecuted" and a call to zenity to give a popup announcement. But none of that happens (no popup and no new file in /tmp/). With maximum verbosity, there is no way to further diagnose this. Deeper detail is needed that shows which matching criteria in the rules is being tried and what the result is. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890836 Title: udev rule read but "RUN" command is not executed Status in systemd package in Ubuntu: New Bug description: The following was introduced as "/etc/udev/rules.d/99-harvest_camera.rules": ACTION=="add", KERNEL=="sd*[!0-9]", ENV{ID_FS_UUID_ENC}=="C355-A42D", RUN+="/usr/bin/sudo -u bill /home/bill/scripts/harvest_camera.sh" When the device is attached, it gets mounted but the harvest_camera.sh script does not execute. The udev_log=debug parameter is set in /etc/udev/udev.conf. Verbosity was also maximized by running "udevadm control --log-priority=debug". After running "udevadm monitor --environment --udev", the drive was attached. The output shows a device being created (/dev/sda1) and the UUID in the rule matches. But the script simply never executes. The /var/log/syslog file shows: " Reading rules file: /etc/udev/rules.d/99-harvest_camera.rules Successfully forked off 'n/a' as PID 2201. 1-2.3: Worker [2201] is forced for rocessing SEQNUM=7973. " So the logs make it look as though the script was executed. The script is simply a stub that does a "touch /tmp/IhaveExecuted" and a call to zenity to give a popup announcement. But none of that happens (no popup and no new file in /tmp/). With maximum verbosity, there is no way to further diagnose this. Deeper detail is needed that shows which matching criteria in the rules is being tried and what the result is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890520] Re: catastrophic bug with deluser command -- destroys large number of system files
Notice also there is a serious transparency problem. The output only shows files for which removal failed. This acutely heightens the destruction because it potentially destroyed *thousands* of files as I sat there and let it run. The tool gives no idea how what's being destroyed. The admin has to trust that their understanding of the scope of removal is accurate. In the absence of errors, an admin would let it run through to the end, resulting in maximum damage. This tool badly needs a --simulate option. And regardless of simulation, it should show what files are affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1890520 Title: catastrophic bug with deluser command -- destroys large number of system files Status in adduser package in Ubuntu: New Bug description: I installed rygel and created a specific rygel user to run it with (as directed by the docs). I then realized a specific user was not needed. To reverse my steps, I ran deluser which proceeded to delete lots of files that have nothing to do with the rygel user: root@host:~# adduser --home /home/rygel --disabled-password --disabled-login --gecos 'Rygel media server' rygel root@host:~# sudo su - rygel rygel@host:$ systemctl start rygel rygel@host:$ exit root@host:~# deluser --remove-home --remove-all-files rygel Looking for files to backup/remove ... /usr/sbin/deluser: Cannot handle special file /etc/systemd/system/mdm.service /usr/sbin/deluser: Cannot handle special file /etc/systemd/system/samba-ad-dc.service /usr/sbin/deluser: Cannot handle special file /etc/systemd/system/cgmanager.service /usr/sbin/deluser: Cannot handle special file /etc/systemd/system/cgproxy.service /usr/sbin/deluser: Cannot handle special file /dev/vcsa7 /usr/sbin/deluser: Cannot handle special file /dev/vcsu7 /usr/sbin/deluser: Cannot handle special file /dev/vcs7 /usr/sbin/deluser: Cannot handle special file /dev/gpiochip0 /usr/sbin/deluser: Cannot handle special file /dev/dvdrw /usr/sbin/deluser: Cannot handle special file /dev/dvd /usr/sbin/deluser: Cannot handle special file /dev/cdrw /usr/sbin/deluser: Cannot handle special file /dev/zfs /usr/sbin/deluser: Cannot handle special file /dev/vhost-vsock /usr/sbin/deluser: Cannot handle special file /dev/vhost-net /usr/sbin/deluser: Cannot handle special file /dev/uhid /usr/sbin/deluser: Cannot handle special file /dev/vhci /usr/sbin/deluser: Cannot handle special file /dev/userio /usr/sbin/deluser: Cannot handle special file /dev/nvram /usr/sbin/deluser: Cannot handle special file /dev/btrfs-control /usr/sbin/deluser: Cannot handle special file /dev/cuse /usr/sbin/deluser: Cannot handle special file /dev/autofs /usr/sbin/deluser: Cannot handle special file /dev/sde /usr/sbin/deluser: Cannot handle special file /dev/sdd /usr/sbin/deluser: Cannot handle special file /dev/sdc /usr/sbin/deluser: Cannot handle special file /dev/sdb /usr/sbin/deluser: Cannot handle special file /dev/sg5 /usr/sbin/deluser: Cannot handle special file /dev/sg4 /usr/sbin/deluser: Cannot handle special file /dev/sg3 /usr/sbin/deluser: Cannot handle special file /dev/sg2 /usr/sbin/deluser: Cannot handle special file /dev/vcsa6 /usr/sbin/deluser: Cannot handle special file /dev/vcsu6 /usr/sbin/deluser: Cannot handle special file /dev/vcs6 /usr/sbin/deluser: Cannot handle special file /dev/vcsa5 /usr/sbin/deluser: Cannot handle special file /dev/vcsu5 /usr/sbin/deluser: Cannot handle special file /dev/vcs5 /usr/sbin/deluser: Cannot handle special file /dev/vcsa4 /usr/sbin/deluser: Cannot handle special file /dev/vcsu4 /usr/sbin/deluser: Cannot handle special file /dev/vcs4 /usr/sbin/deluser: Cannot handle special file /dev/vcsa3 /usr/sbin/deluser: Cannot handle special file /dev/vcsu3 /usr/sbin/deluser: Cannot handle special file /dev/vcs3 /usr/sbin/deluser: Cannot handle special file /dev/vcsa2 /usr/sbin/deluser: Cannot handle special file /dev/vcsu2 /usr/sbin/deluser: Cannot handle special file /dev/vcs2 /usr/sbin/deluser: Cannot handle special file /dev/hidraw2 /usr/sbin/deluser: Cannot handle special file /dev/hidraw1 /usr/sbin/deluser: Cannot handle special file /dev/cdrom /usr/sbin/deluser: Cannot handle special file /dev/hidraw0 /usr/sbin/deluser: Cannot handle special file /dev/fb0 /usr/sbin/deluser: Cannot handle special file /dev/i2c-5 /usr/sbin/deluser: Cannot handle special file /dev/i2c-4 /usr/sbin/deluser: Cannot handle special file /dev/i2c-3 /usr/sbin/deluser: Cannot handle special file /dev/i2c-2 /usr/sbin/deluser: Cannot handle special file /dev/i2c-1 /usr/sbin/deluser: Cannot handle special file /dev/i2c-0 /usr/sbin/deluser: Cannot handle special file /dev/rtc /usr/sbin/deluser: Cannot handle special file /dev/stderr /usr/sbin/deluser: Cannot handle
[Touch-packages] [Bug 1890827] [NEW] udev and udevadm documentation missing
Public bug reported: The man page for udevadm neglects to mention options which seem to only be documented in stackexchange. E.g. udevadm monitor --environment udevadm control --reload-rules >From the man page, it's unclear what the difference is between /udevadm trigger/ and /udevadm test/. The description should tell the user enough to work out which one they need to use for a certain situation. E.g. I wrote a new rule and it's not triggering. Is the trigger command or the test command suitable for diagnosing the problem? The documentation in /usr/share/doc/udev/ is strangely specific to some esoteric network interface naming. There is no basic description of what udev's purpose is or what its capabilities are. One of the most notable tasks is to react to the insertion of USB drives, and there is no mention of this. The /etc/fstab table also has a role in mounting USB drives, but there is no mention as to how udev works with /etc/fstab. I've found that if I remove a line in /etc/fstab and attach the drive pertaining to that line, it gets mounted anyway. If the fstab file supercedes udev, then this should be mentioned in the documentation. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890827 Title: udev and udevadm documentation missing Status in systemd package in Ubuntu: New Bug description: The man page for udevadm neglects to mention options which seem to only be documented in stackexchange. E.g. udevadm monitor --environment udevadm control --reload-rules From the man page, it's unclear what the difference is between /udevadm trigger/ and /udevadm test/. The description should tell the user enough to work out which one they need to use for a certain situation. E.g. I wrote a new rule and it's not triggering. Is the trigger command or the test command suitable for diagnosing the problem? The documentation in /usr/share/doc/udev/ is strangely specific to some esoteric network interface naming. There is no basic description of what udev's purpose is or what its capabilities are. One of the most notable tasks is to react to the insertion of USB drives, and there is no mention of this. The /etc/fstab table also has a role in mounting USB drives, but there is no mention as to how udev works with /etc/fstab. I've found that if I remove a line in /etc/fstab and attach the drive pertaining to that line, it gets mounted anyway. If the fstab file supercedes udev, then this should be mentioned in the documentation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890654] Re: udev service does not log
Sorry, i mean to say /var/log/syslog (not /var/log/system) shows the device was attached. The verbosity in /var/log/syslog increases when udev_log=debug, but still no /var/log/udev. -- 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/1890654 Title: udev service does not log Status in systemd package in Ubuntu: New Bug description: By default udev is supposed to log to /var/log. In Ubuntu 20 it is not logging. Logging was then explicitly enabled by uncommenting this line in /etc/udev/udev.conf: "udev_log=info" After running "systemctl restart udev" and plugging in a USB drive, there is still no udev log in /var/log. Yet /var/log/system shows that a device was in fact attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844426] Re: Impossible to set up Livepatch on Ubuntu MATE
** Also 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/1844426 Title: Impossible to set up Livepatch on Ubuntu MATE Status in Ubuntu MATE: Confirmed Status in software-properties package in Ubuntu: New Bug description: In Ubuntu MATEE 18.04, in the Software Properties window (available from Software Boutique > Preferences > Show Software Sources > Manage Repositories, among other places), there is a Livepatch tab. This tab says "To use Livepatch, you need to sign in" and provides a "Sign In..." button. This button launches an empty version of gnome-control-center with no icons in it. If one is technically adept, it is possible to do what (I think) that button is trying to do by launching g-c-c directly in a terminal and overriding the desktop, thus: env XDG_CURRENT_DESKTOP=GNOME gnome-control-center online-accounts This online accounts window permits attempting to add an Ubuntu One account. However, when one tries, a window pops up with a place to add one's Ubuntu One username and password, but the window has no Submit button; there is no way to actually initiate sign in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1844426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875944] Re: Lenovo Ideapad 130-15AST 20.04 distorted and unusable
*** This bug is a duplicate of bug 1873895 *** https://bugs.launchpad.net/bugs/1873895 ** This bug has been marked a duplicate of bug 1873895 Regression: block staircase display with side-by-side monitors of different pixel widths -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1875944 Title: Lenovo Ideapad 130-15AST 20.04 distorted and unusable Status in Ubuntu MATE: Confirmed Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Output of lshw here: https://pastebin.com/NMBigV4G Screenshot of the desktop here in the community forum: https://ubuntu-mate.community/t/lenovo-ideapad-20-04-upgrade-distorted-and-unusable/21617 I'm not all that experienced at filing bug reports here so I have included the attachment of the photo found at the forum link. The picture in the community forum link is what the MATE 20.04 live USB boots to. I first upgraded from 18.04 using do-release-upgrade. The result looked like the photo as well. Then I reinstalled 18.04, upgraded to 19.10, which looked and performed normally. I then upgraded the 19.10 install to 20.04 with the same result as the photo. I also tried with a different flash drive just to rule that out. Then I made the live USB of the 20.04 image and booted it to what you see in the forum post. I made a live USB of both Stock Ubuntu and Kubuntu 20.04 and both worked just fine. Until I tried the other two flavors I was thinking it was system specific, but after they worked normally it seems to be a MATE specific issue with this system. It appears to be only a display problem. The DE is completely unusable with the mouse, but I can launch a terminal and run commands, although the terminal is just as distorted as the photo above, so you can't see what you are typing or the resulting output. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: clay 1524 F pulseaudio /dev/snd/controlC0: clay 1524 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: rtl8821ce, v5.5.2_34066.20200325, 5.3.0-46-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev ea) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:39f5] InstallationDate: Installed on 2020-04-27 (11 days ago) InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: LENOVO 81H5 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=bec09cbc-83af-49f6-8aeb-f02059977f4a ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: bionic ubuntu Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN15WW(V1.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 130-15AST dmi.modalias: dmi:bvnLENOVO:bvr8ZCN15WW(V1.04):bd06/27/2018:svnLENOVO:pn81H5:pvrLenovoideapad130-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad130-15AST: dmi.product.family: ideapad 130-15AST dmi.product.name: 81H5 dmi.product.sku: LENOVO_MT_81H5_BU_idea_FM_ideapad 130-15AST dmi.product.version: Lenovo ideapad 130-15AST dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1875944/+subscriptions
[Touch-packages] [Bug 1875892] [NEW] Display Interfaces Not Detected
Public bug reported: My laptop (Lenovo ThinkPad P51) has 2 display interfaces. One mini-dp and one HDMI. But none of them is shown in xrandr, and my external display connected through mini-dp is not detected also. When I used LiveCD, the external monitor works normally. The above situation happens when my boot from SSD with the fully-installed system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 21:37:28 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics P630 [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics P630 [17aa:224d] Subsystem: Lenovo GM206GLM [Quadro M2200 Mobile] [17aa:224d] InstallationDate: Installed on 2020-04-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20HHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=05a90498-4cfc-4877-8f08-b096eb36e91b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET77W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET77W(1.51):bd02/10/2020:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HHCTO1WW dmi.product.sku: LENOVO_MT_20HH_BU_Think_FM_ThinkPad P51 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1875892 Title: Display Interfaces Not Detected Status in xorg package in Ubuntu: New Bug description: My laptop (Lenovo ThinkPad P51) has 2 display interfaces. One mini-dp and one HDMI. But none of them is shown in xrandr, and my external display connected through mini-dp is not detected also. When I used LiveCD, the external monitor works normally. The above situation happens when my boot from SSD with the fully-installed system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 21:37:28 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu
[Touch-packages] [Bug 1873386] Re: nmcli error report on reboot after latest 20.04 updates
Link to crash report from step #2: https://errors.ubuntu.com/oops/88d785d4-80ba-11ea-a860-fa163ee63de6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1873386 Title: nmcli error report on reboot after latest 20.04 updates Status in network-manager package in Ubuntu: Invalid Bug description: Ubuntu MATE 20.04. Updated to latest updates and newest kernel, on 20200416. Upon reboot system should error and error for nmcli. Crash file located in /var/crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Apr 16 21:58:56 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.159 metric 600 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-04 (12 days ago) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Lothlorien 41892137-acd0-46f2-8959-5f1e126489b0 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1873386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873386] [NEW] nmcli error report on reboot after latest 20.04 updates
Public bug reported: Ubuntu MATE 20.04. Updated to latest updates and newest kernel, on 20200416. Upon reboot system should error and error for nmcli. Crash file located in /var/crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Apr 16 21:58:56 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.159 metric 600 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-04 (12 days ago) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Lothlorien 41892137-acd0-46f2-8959-5f1e126489b0 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1873386 Title: nmcli error report on reboot after latest 20.04 updates Status in network-manager package in Ubuntu: New Bug description: Ubuntu MATE 20.04. Updated to latest updates and newest kernel, on 20200416. Upon reboot system should error and error for nmcli. Crash file located in /var/crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Apr 16 21:58:56 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.159 metric 600 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-04 (12 days ago) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Lothlorien 41892137-acd0-46f2-8959-5f1e126489b0 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1873386/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1869923] [NEW] lightdm crashes on login to system 20.04
Public bug reported: Ubuntu MATE 20.04 updated 03312020 Hesitation on login to system Login successful System reports error and crash file located in /var/crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: MATE Date: Tue Mar 31 11:13:52 2020 InstallationDate: Installed on 2019-12-13 (109 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20191213) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1869923 Title: lightdm crashes on login to system 20.04 Status in lightdm package in Ubuntu: New Bug description: Ubuntu MATE 20.04 updated 03312020 Hesitation on login to system Login successful System reports error and crash file located in /var/crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: MATE Date: Tue Mar 31 11:13:52 2020 InstallationDate: Installed on 2019-12-13 (109 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20191213) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1869923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
Tested with latest packages in proposed Ubuntu MATE and able to install and use balena-etcher-electron. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869787] Re: libpango1.0-0 has been removed from 20.04 and is not installable
*** This bug is a duplicate of bug 1869716 *** https://bugs.launchpad.net/bugs/1869716 https://packages.ubuntu.com/bionic/libpango1.0-0 ** Package changed: ubuntu => pango1.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869787 Title: libpango1.0-0 has been removed from 20.04 and is not installable Status in pango1.0 package in Ubuntu: New Bug description: Upon update on 30 March 2020 libpango1.0-0 was removed from the system. Package libpango1.0-0 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libpangox-1.0-0 However applications such as balena-etcher require libpango1.0-0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
Still stuck on version 7.5 3 months later. -- 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/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Won't Fix Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed
Using 20.04 current build still see: $ python Command 'python' not found, but can be installed with: If I run sudo apt install python Package python is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: python2-minimal:i386 python2:i386 python2-minimal python2 2to3 E: Package 'python' has no installation candidate This has an effect on an upgrade to 20.04 of uninstalling any package that depends on "python" for example slack-desktop. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863532 Title: Invoking "python" brings inappropriate response from command-not-found when python3 installed Status in command-not-found package in Ubuntu: Triaged Status in python3-defaults package in Ubuntu: Triaged Status in command-not-found source package in Focal: Triaged Status in python3-defaults source package in Focal: Triaged Bug description: Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't have python 2.7 installed, but have python 3 installed as per default. Please see ascii-cast at https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 . Running `python` brings up text from command-not-found which suggests installing `python3` as a solution to the missing command. `python3` is already installed, is a later version than the one indicated by command-not-found and does not supply a binary or symlink named `python`. $ apt policy python python: Installed: (none) Candidate: (none) Version table: 2.7.17-1 -1 100 /var/lib/dpkg/status $ apt policy python3 python3: Installed: 3.8.0-3 Candidate: 3.8.0-3 Version table: *** 3.8.0-3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy command-not-found command-not-found: Installed: 19.10.0 Candidate: 19.10.0 Version table: *** 19.10.0 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status I don't know whether this is a bug in python3 or command-not-found (the latter of which doesn't seem to have been updated for 20.04 yet). i don't know if it is intentional that `python3` will not provide a binary or symlink named `python`. if that is the case, the output of `command-not-found` should be updated to reflect that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.0-3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: MATE Date: Mon Feb 17 01:35:16 2020 InstallationDate: Installed on 2019-10-11 (128 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) SourcePackage: python3-defaults UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863825] [NEW] 20.04 apt update of python 3.8 gives errors
Public bug reported: Run sudo apt dist-upgrade on 20.04 install. Expected result: python3 is updated without issue Actual result: After this operation, 1,114 kB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-minimal amd64 3.8.0-3ubuntu1 [23.3 kB] Get:2 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3 amd64 3.8.0-3ubuntu1 [47.6 kB] Get:3 http://us.archive.ubuntu.com/ubuntu focal/main amd64 libpython3-stdlib amd64 3.8.0-3ubuntu1 [6,872 B] Get:4 http://us.archive.ubuntu.com/ubuntu focal/main amd64 libnewt0.52 amd64 0.52.21-4ubuntu2 [41.1 kB] Get:5 http://us.archive.ubuntu.com/ubuntu focal/main amd64 whiptail amd64 0.52.21-4ubuntu2 [17.0 kB] Get:6 http://us.archive.ubuntu.com/ubuntu focal/main amd64 gnome-disk-utility amd64 3.35.91-1ubuntu1 [186 kB] Get:7 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard-data all 1.4.1-2ubuntu7 [3,803 kB] Get:8 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard amd64 1.4.1-2ubuntu7 [351 kB] Get:9 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 onboard-common all 1.4.1-2ubuntu7 [530 kB] Get:10 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 python3-html5-parser amd64 0.4.9-3build1 [125 kB] Get:11 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-renderpm amd64 3.5.34-1build1 [60.4 kB] Get:12 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-reportlab-accel amd64 3.5.34-1build1 [19.4 kB] Get:13 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-reportlab all 3.5.34-1build1 [546 kB] Get:14 http://us.archive.ubuntu.com/ubuntu focal/main amd64 python3-systemd amd64 234-3build2 [36.5 kB] Fetched 5,793 kB in 8s (694 kB/s) (Reading database ... 529746 files and directories currently installed.) Preparing to unpack .../python3-minimal_3.8.0-3ubuntu1_amd64.deb ... Unpacking python3-minimal (3.8.0-3ubuntu1) over (3.8.0-3) ... Setting up python3-minimal (3.8.0-3ubuntu1) ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be use d self.stdin = io.open(p2cwrite, 'wb', bufsize) (Reading database ... 529746 files and directories currently installed.) Preparing to unpack .../00-python3_3.8.0-3ubuntu1_amd64.deb ... running python pre-rtupdate hooks for python3.8... Unpacking python3 (3.8.0-3ubuntu1) over (3.8.0-3) ... Preparing to unpack .../01-libpython3-stdlib_3.8.0-3ubuntu1_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.8.0-3ubuntu1) over (3.8.0-3) ... Preparing to unpack .../02-libnewt0.52_0.52.21-4ubuntu2_amd64.deb ... Unpacking libnewt0.52:amd64 (0.52.21-4ubuntu2) over (0.52.21-4ubuntu1) ... Preparing to unpack .../03-whiptail_0.52.21-4ubuntu2_amd64.deb ... Unpacking whiptail (0.52.21-4ubuntu2) over (0.52.21-4ubuntu1) ... Preparing to unpack .../04-gnome-disk-utility_3.35.91-1ubuntu1_amd64.deb ... Unpacking gnome-disk-utility (3.35.91-1ubuntu1) over (3.35.2-1ubuntu1) ... Preparing to unpack .../05-onboard-data_1.4.1-2ubuntu7_all.deb ... Unpacking onboard-data (1.4.1-2ubuntu7) over (1.4.1-2ubuntu6) ... Preparing to unpack .../06-onboard_1.4.1-2ubuntu7_amd64.deb ... Unpacking onboard (1.4.1-2ubuntu7) over (1.4.1-2ubuntu6) ... Preparing to unpack .../07-onboard-common_1.4.1-2ubuntu7_all.deb ... Unpacking onboard-common (1.4.1-2ubuntu7) over (1.4.1-2ubuntu6) ... Preparing to unpack .../08-python3-html5-parser_0.4.9-3build1_amd64.deb ... Unpacking python3-html5-parser (0.4.9-3build1) over (0.4.9-3) ... Preparing to unpack .../09-python3-renderpm_3.5.34-1build1_amd64.deb ... Unpacking python3-renderpm:amd64 (3.5.34-1build1) over (3.5.34-1) ... Preparing to unpack .../10-python3-reportlab-accel_3.5.34-1build1_amd64.deb ... Unpacking python3-reportlab-accel:amd64 (3.5.34-1build1) over (3.5.34-1) ... Preparing to unpack .../11-python3-reportlab_3.5.34-1build1_all.deb ... Unpacking python3-reportlab (3.5.34-1build1) over (3.5.34-1) ... Preparing to unpack .../12-python3-systemd_234-3build2_amd64.deb ... Unpacking python3-systemd (234-3build2) over (234-3build1) ... Setting up libnewt0.52:amd64 (0.52.21-4ubuntu2) ... Setting up whiptail (0.52.21-4ubuntu2) ... Setting up gnome-disk-utility (3.35.91-1ubuntu1) ... Setting up libpython3-stdlib:amd64 (3.8.0-3ubuntu1) ... Setting up python3 (3.8.0-3ubuntu1) ... running python rtupdate hooks for python3.8... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be use d
[Touch-packages] [Bug 1856927] Re: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping()
@seb128 this is working correctly now after the grilo update. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1856927 Title: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping() Status in Grilo Plugins: Fix Released Status in grilo-plugins package in Ubuntu: Fix Released Status in totem package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/55095074fb3c3335c19f63f3c91d3a8231be2034 --- Test case: Fresh 20.04 install, updated Open totem What happens: segfault Installing grilo-plugins-0.3-extra allows totem to open fine. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 19:51:40 2019 ExecutablePath: /usr/bin/totem ExecutableTimestamp: 1570435741 InstallationDate: Installed on 2019-12-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) ProcCmdline: /usr/bin/totem --gapplication-service ProcCwd: /home/doug ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f76b92f6dd6:movzbl (%rax),%eax PC (0x7f76b92f6dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libtracker-sparql-2.0.so.0 Title: totem crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' separator: To manage notifications about this bug go to: https://bugs.launchpad.net/grilo-plugins/+bug/1856927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861191] Re: System hangs on graphical boot after kernel and nVidia upgrade
nVidia driver 340.107 is available, however switching to that in Software & Updates has resulted in some issues. After Apply Changes, I am kicked to the Nouveau driver. And I get an ErrorBrokenCount > 0 Trying to resolve with sudo apt --fix-broken install as recommended by apt gives me: The following additional packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 The following NEW packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/29.1 MB of archives. After this operation, 147 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 482145 files and directories currently installed.) Preparing to unpack .../libnvidia-gl-390_390.116-0ubuntu0.18.04.3_i386.deb ... diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_i386.deb (--unpack): new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 Preparing to unpack .../libnvidia-gl-390_390.116-0ubuntu0.18.04.3_amd64.deb ... diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_amd64.deb (--unpack): new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_i386.deb /var/cache/apt/archives/libnvidia-gl-390_390.116-0ubuntu0.18.04.3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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/1861191 Title: System hangs on graphical boot after kernel and nVidia upgrade Status in xorg package in Ubuntu: New Bug description: System is Ubuntu MATE 18.04.3 T430 with nVidia On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no issues. On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no issues. System was rebooted today. Expected outcome: System reboots into desktop login Actual outcome: System gets to grub menu then hangs on black screen. TTYs are not responsive. This is reproducible and consistent. System will return to black screen and hung state. Workaround: Editing Grub and adding nouveau.modset=0 allows system to boot to GUI login. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Tue Jan 28 09:57:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 5.3.0-26-generic, x86_64: installed nvidia, 390.116, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time 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:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [NVS 5400M] [17aa:21f4] InstallationDate: Installed on 2019-12-05
[Touch-packages] [Bug 1861191] [NEW] System hangs on graphical boot after kernel and nVidia upgrade
Public bug reported: System is Ubuntu MATE 18.04.3 T430 with nVidia On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no issues. On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no issues. System was rebooted today. Expected outcome: System reboots into desktop login Actual outcome: System gets to grub menu then hangs on black screen. TTYs are not responsive. This is reproducible and consistent. System will return to black screen and hung state. Workaround: Editing Grub and adding nouveau.modset=0 allows system to boot to GUI login. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Tue Jan 28 09:57:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 5.3.0-26-generic, x86_64: installed nvidia, 390.116, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time 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:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [NVS 5400M] [17aa:21f4] InstallationDate: Installed on 2019-12-05 (53 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 23445PU ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5977afa2-a407-43bd-a6f4-e5dfd01188c0 ro quiet splash mouveau.modset=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 23445PU dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:svnLENOVO:pn23445PU:pvrThinkPadT430:rvnLENOVO:rn23445PU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 23445PU dmi.product.sku: LENOVO_MT_2344 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1861191 Title: System hangs on graphical boot after kernel and nVidia upgrade Status in xorg package in Ubuntu: New Bug description: System is Ubuntu MATE 18.04.3 T430 with nVidia On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no issues. On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no issues. System was rebooted today. Expected outcome: System reboots into desktop login Actual outcome: System gets to grub menu then hangs on black screen. TTYs are not responsive. This is reproducible and consistent. System will return to black screen and hung state. Workaround: Editing Grub and adding nouveau.modset=0
[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
I have an Nvidia based video card that has 2 DVI outputs, an HDMI output, a DisplayPort output. I have 2 monitors that are plugged in to the DVI outputs, and nothing plugged in to the HDMI or DP outputs. And still, XUbuntu insists on switching audio to the HDMI outputs that have nothing plugged into them. -- 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: [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] Low. 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 1850964] Re: Always explain why packages are held back in logs even without debugging enabled
I'd prefer that the message be suppressed when the packages in question are pinned. In this case, not updating them is the desired action, and errors/warnings are not appropriate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1850964 Title: Always explain why packages are held back in logs even without debugging enabled Status in unattended-upgrades package in Ubuntu: Confirmed Status in unattended-upgrades package in Debian: Unknown Bug description: [Impact] * Unattended-upgrades' log does not contain information about why held packages are kept back unless debugging is enabled. Users should be explained why packages are kept back to let them easily resolve the issues keeping the packages from being upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1850964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1857345] [NEW] Misleading login message from unattended-upgrades
Public bug reported: A recent update to unattended-upgrades causes messages to be displayed at login similar to this: "1 updates could not be installed automatically. For more details,see /var/log/unattended-upgrades /unattended-upgrades.log" However, when the user has pinned/held a package, this is expected behavior, and should not cause a warning or error. Additionally, in this case, the the logfile that the user is directed to reference contains no useful information. Either the message should not be issued for pinned packages (preferred) or the logfile that the user is directed to reference should contain useful information. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.13 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Dec 23 07:16:09 2019 InstallationDate: Installed on 2016-08-27 (1213 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to bionic on 2018-08-04 (505 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "1"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-08-18T18:55:52.439072 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1857345 Title: Misleading login message from unattended-upgrades Status in unattended-upgrades package in Ubuntu: New Bug description: A recent update to unattended-upgrades causes messages to be displayed at login similar to this: "1 updates could not be installed automatically. For more details,see /var/log/unattended-upgrades /unattended-upgrades.log" However, when the user has pinned/held a package, this is expected behavior, and should not cause a warning or error. Additionally, in this case, the the logfile that the user is directed to reference contains no useful information. Either the message should not be issued for pinned packages (preferred) or the logfile that the user is directed to reference should contain useful information. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.13 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Dec 23 07:16:09 2019 InstallationDate: Installed on 2016-08-27 (1213 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to bionic on 2018-08-04 (505 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "1"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-08-18T18:55:52.439072 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1605189] Re: Authentication is required for suspending the system
*** This bug is a duplicate of bug 1441460 *** https://bugs.launchpad.net/bugs/1441460 I'm using Mint 19.2 XFCE. I went with chrisc1073 setup and things seem to be working fine. Thanks for the 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/1605189 Title: Authentication is required for suspending the system Status in systemd package in Ubuntu: Confirmed Bug description: Automatic suspend from the xfce power manager does not work, as a window opens and asks for my password. Well, if it wants to suspend the system after a given timeout, I cannot enter my password as I'm not in front of my system then. Once I'm able to enter my password it is too late to run the suspend action. The window asking for my password prints: Password: Details Action: org.freedesktop.login1.suspend Vendor: The systemd project ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 21 13:13:12 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-17 (703 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 4236ML1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/ubuntu--vg-root ro intel_pstate=enable SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to xenial on 2016-05-28 (53 days ago) dmi.bios.date: 07/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236ML1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236ML1:pvrThinkPadT420:rvnLENOVO:rn4236ML1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4236ML1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1605189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832967] Re: /etc/resolv.conf does not include the local domain name
Thanks for the quick response. Yesterday to fix the issue, I uninstalled the resolvconf package. I reinstalled it today, and now it is working with the correct "search" domain. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1832967 Title: /etc/resolv.conf does not include the local domain name Status in resolvconf package in Ubuntu: Incomplete Bug description: When I rebooted my system after an update, `/etc/resolv.conf` was symlinked to `/run/resolvconf/resolv.conf`. That file did not have my local domain name in the search even though it is supplied by the dhcp server. The systemd resolv.conf file (in `/run/systemd/resolve/resolv.conf`) had the correct search information. Please ensure that the search is correctly added. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 15 22:18:05 2019 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-08-21 (299 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1832967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832967] [NEW] /etc/resolv.conf does not include the local domain name
Public bug reported: When I rebooted my system after an update, `/etc/resolv.conf` was symlinked to `/run/resolvconf/resolv.conf`. That file did not have my local domain name in the search even though it is supplied by the dhcp server. The systemd resolv.conf file (in `/run/systemd/resolve/resolv.conf`) had the correct search information. Please ensure that the search is correctly added. This is also described here: https://askubuntu.com/a/1041631/326601 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 15 22:18:05 2019 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-08-21 (299 days ago) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1832967 Title: /etc/resolv.conf does not include the local domain name Status in resolvconf package in Ubuntu: New Bug description: When I rebooted my system after an update, `/etc/resolv.conf` was symlinked to `/run/resolvconf/resolv.conf`. That file did not have my local domain name in the search even though it is supplied by the dhcp server. The systemd resolv.conf file (in `/run/systemd/resolve/resolv.conf`) had the correct search information. Please ensure that the search is correctly added. This is also described here: https://askubuntu.com/a/1041631/326601 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 15 22:18:05 2019 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: Upgraded to bionic on 2018-08-21 (299 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1832967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813234] [NEW] package initramfs-tools 0.130ubuntu3.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: crashes on start up of gui ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Jan 20 13:32:42 2019 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-25 (152 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1813234 Title: package initramfs-tools 0.130ubuntu3.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: crashes on start up of gui ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Jan 20 13:32:42 2019 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-25 (152 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1813234/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I see the messages (starting with "Could not find key with description") on a fresh install of Linux Mint 19 Cinnamon. Second line of kern.log says: "Linux version 4.15.0-36-generic (buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 (Ubuntu 4.15.0-36.39-generic 4.15.18)" -- 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/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110]
Hi is not merged on 4.16 / 4.17 / 4.18 / 4.19 for what ? https://forum.manjaro.org/t/asus-e200ha-no-sound/44205/17 marcin19883 say : Kernel 4.19 RC1 Audio not working. No codec include. :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110]
(In reply to Caitlyn Martin from comment #98) > It is fixed in the 4.18 kernel but more than an updated kerne is > required. You also need an up to date version of alsa and the new > codec to be included when the kernel is compiled. The problem with > Manjaro is almost certainly a Manjaro problem, not an upstream > problem. > > On Sat, Jul 14, 2018 at 4:15 AM, > wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=115531 > > > > liberodark (bill@live.fr) changed: > > > >What|Removed |Added > > > ---- > > CC| |bill@live.fr > > > > --- Comment #97 from liberodark (bill@live.fr) --- > > Hi, > > > > But not work on manjaro 17.1.11 ! > > The bug is not fixed is not integrated to kernel no ? > > Have possibility to merge driver on kernel 4.18 ? > > > > https://www.manjaro.fr/forum/viewtopic.php?f=19=8812=asus > > https://forum.manjaro.org/t/asus-e200ha-no-sound/44205/7 > > https://bugzilla.kernel.org/show_bug.cgi?id=200491 > > > > Cordialy > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. And have view is not officialy merged arch and majanro is not implicated for this problem. Please make a official merge to add audio codec. Cordialy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 533974] Re: HP Officejet will not print in Bk only after udate
No problem. I really forgot about it. Bill On Sun, Aug 5, 2018 at 2:32 PM, gf <533...@bugs.launchpad.net> wrote: > Thanks for the update, Bill. I am just trying to clear up these old > tickets. I will close the report now. > Have a great day! > :) > G > > Closed per reporter’s feedback. > > ** Changed in: cups (Ubuntu) >Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/533974 > > Title: > HP Officejet will not print in Bk only after udate > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/533974/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/533974 Title: HP Officejet will not print in Bk only after udate Status in cups package in Ubuntu: Invalid Bug description: I set my printer to black ink only at 300 DPI and have never had a problem until the last update. Every time the printer will print in color draft mode only no matter what print settings are chosen. 600 dpi black ink only, grey scale or what ever. I deleted and reinstalled the printer and it still will only print color. I am tired of wasting ink. I use 9.04 and would load 4.10 if the video drivers were stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/533974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 533974] Re: HP Officejet will not print in Bk only after udate
I have no idea if this was resolved. It's at least 10 years since I had an HP-5400 I quit using Ubuntu when it became too much like Windoze. Other distros work fine. On Sun, Aug 5, 2018 at 10:19 AM, gf <533...@bugs.launchpad.net> wrote: > Hello Bill, > Thank you for submitting this bug and reporting a problem with cups and > printing. You made this bug report some time ago and Ubuntu has been > updated since then. > > Could you confirm that this is no longer a problem and that we can close > the ticket? > If it is still a problem, are you still interested in finding a solution > to this bug? > If you are, could you let us know, and in the current version, run the > following (only once): > apport-collect BUGNUMBER > and upload the updated logs and and any other logs that are relevant for > this particular issue. > > Thank you again for helping make Ubuntu better. > G > > ** Changed in: cups (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/533974 > > Title: > HP Officejet will not print in Bk only after udate > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/533974/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/533974 Title: HP Officejet will not print in Bk only after udate Status in cups package in Ubuntu: Incomplete Bug description: I set my printer to black ink only at 300 DPI and have never had a problem until the last update. Every time the printer will print in color draft mode only no matter what print settings are chosen. 600 dpi black ink only, grey scale or what ever. I deleted and reinstalled the printer and it still will only print color. I am tired of wasting ink. I use 9.04 and would load 4.10 if the video drivers were stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/533974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
For anyone that's interested --- I added the following to root's crontab: @reboot sleep 120 && /bin/systemctl restart sshd That works for me to get sshd up AND listening -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
Robie: If the service offers a mechanism to set a specific NIC to listen on, then the service should make good on that offer when it's requested. Doesn't that make sense to you? All services that require a NIC to function should wait for that NIC to come alive. Having a service start or attempt to start before what it needs for life support is available makes no sense. Allowing a service to start on a bogus IP address provides no "service". What's the point of having a service technically up if it's deaf to traffic? I can't see where this qualifies as a wishlist item. The service advertises a feature and doesn't provide it. To me, that's a bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
I created Bug 1774788 which is for rsyncd not starting at boot and was provided with a fix by Andreas Hasenack that works. I tried using that fix for ssh and it does not work. Both services fail when an attempt is made to specify a particular NIC via their respective config files. In the case of rsync, the fix was to create the override.conf file containing: [Unit] After=network.target,network-online.target via the command systemctl edit rsync.service Using a similar procedure to create the override.conf file for ssh does not fix the ssh daemon startup issue. I'm curious as to why that is. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776329] [NEW] apport-cli and cowbuilder fail with cert and keyring errors
Public bug reported: Description: Ubuntu 18.04 LTS Release: 18.04 ubuntu-keyring: Installed: 2018.02.28 apport: Installed: 2.20.9-0ubuntu7.2 cowbuilder: Installed: 0.86 On a bionic system when attempting to report what I suspect is a bug in ubuntu-keying I got the following error start capture- $ apport-cli ubuntu-keyring *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (1.2 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. *** Error: Network problem Cannot connect to crash database, please check your Internet connection. Press any key to continue... end capture--- I worked around the problem by K'eeping the report and copying it to a Xenial system. From there I am submitting this bug report. The original problem that caused me to attempt to file a bug report against ubuntu-keyring was an attempt to build a bionic chroot for package building with the following command: start capture- # DIST=bionic cowbuilder --create --distribution bionic --components "main universe" --basepath /var/cache/pbuilder/base-bionic-amd64-test.cow --mirror http://us.archive.ubuntu.com:80/ubuntu --debootstrapopts --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg I: Invoking pbuilder I: forking: pbuilder create --components 'main universe' --debootstrapopts --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --buildplace /var/cache/pbuilder/base-bionic-amd64-test.cow --mirror http://us.archive.ubuntu.com:80/ubuntu --distribution bionic --no-targz --extrapackages cowdancer W: /root/.pbuilderrc does not exist I: Running in no-targz mode I: Distribution is bionic. I: Current time: Mon Jun 11 22:44:21 UTC 2018 I: pbuilder-time-stamp: 1528757061 I: Building the build environment I: running debootstrap /usr/sbin/debootstrap I: Retrieving InRelease I: Checking Release signature E: Release signed by unknown key (key id 3B4FE6ACC0B21F32) E: debootstrap failed E: Tail of debootstrap.log: gpgv: Signature made Thu Apr 26 23:38:40 2018 UTC gpgv:using RSA key 3B4FE6ACC0B21F32 gpgv: Can't check signature: No public key E: End of debootstrap.log W: Aborting with an error E: pbuilder create failed I: forking: rm -rf /var/cache/pbuilder/base-bionic-amd64-test.cow end capture--- On the same system the following command succeeds: start capture- DIST=xenial cowbuilder --create --distribution xenial \ --components "main universe" \ --basepath /var/cache/pbuilder/base-xenial-amd64.cow \ --mirror http://us.archive.ubuntu.com:80/ubuntu \ --debootstrapopts --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg end capture--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-keyring 2018.02.28 [modified: usr/share/keyrings/ubuntu-archive-keyring.gpg] ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Jun 11 22:51:48 2018 Dependencies: PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 TERM=xterm SHELL=/bin/bash PATH=(custom, no user) SourcePackage: ubuntu-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1776329 Title: apport-cli and cowbuilder fail with cert and keyring errors Status in ubuntu-keyring package in Ubuntu: New Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 ubuntu-keyring: Installed: 2018.02.28 apport: Installed: 2.20.9-0ubuntu7.2 cowbuilder: Installed: 0.86 On a bionic system when attempting to report what I suspect is a bug in ubuntu-keying I got the following error start
[Touch-packages] [Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)
I'm a recent convert to Ubuntu, having been on Fedora from FC2 through F26; quite a long time. Over the last few years, their support became nonexistent. Bugs reported would not even be acknowledged, much less worked on. To have someone actually respond to a bug report is so unusual in my experience that I'm pleasantly shocked. Thank You. Thank You. Shouldn't services (sshd, rsync, etc) that depend on a NIC being available ALL wait till that's true? Shouldn't the fix presented for this bug become SOP for all the control files for services that require a NIC to be up? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1774788 Title: Daemon won't start at boot up (18LTS fully patched) Status in rsync: Unknown Status in rsync package in Ubuntu: Triaged Bug description: By adding the 'address=' option to the /etc/rsyncd.conf file, the daemon fails at boot. Once the NIC(s) is/are up, it will start fine when executed via systemctl start rsync ● rsync.service - fast remote file copy program daemon Loaded: loaded (/lib/systemd/system/rsync.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10) Main PID: 851 (code=exited, status=10) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873 Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873 Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 08:48:15 2018 InstallationDate: Installed on 2018-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1774788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)
I'm impressed! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1774788 Title: Daemon won't start at boot up (18LTS fully patched) Status in rsync: Unknown Status in rsync package in Ubuntu: Triaged Bug description: By adding the 'address=' option to the /etc/rsyncd.conf file, the daemon fails at boot. Once the NIC(s) is/are up, it will start fine when executed via systemctl start rsync ● rsync.service - fast remote file copy program daemon Loaded: loaded (/lib/systemd/system/rsync.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10) Main PID: 851 (code=exited, status=10) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873 Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873 Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 08:48:15 2018 InstallationDate: Installed on 2018-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1774788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774788] [NEW] Daemon won't start at boot up (18LTS fully patched)
Public bug reported: By adding the 'address=' option to the /etc/rsyncd.conf file, the daemon fails at boot. Once the NIC(s) is/are up, it will start fine when executed via systemctl start rsync ● rsync.service - fast remote file copy program daemon Loaded: loaded (/lib/systemd/system/rsync.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10) Main PID: 851 (code=exited, status=10) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873 Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873 Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 08:48:15 2018 InstallationDate: Installed on 2018-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1774788 Title: Daemon won't start at boot up (18LTS fully patched) Status in rsync package in Ubuntu: New Bug description: By adding the 'address=' option to the /etc/rsyncd.conf file, the daemon fails at boot. Once the NIC(s) is/are up, it will start fine when executed via systemctl start rsync ● rsync.service - fast remote file copy program daemon Loaded: loaded (/lib/systemd/system/rsync.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-06-02 08:01:31 CST; 52min ago Process: 851 ExecStart=/usr/bin/rsync --daemon --no-detach (code=exited, status=10) Main PID: 851 (code=exited, status=10) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: Started fast remote file copy program daemon. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsyncd version 3.1.2 starting, listening on port 873 Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: bind() failed: Cannot assign requested address (address-family 2) Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Main process exited, code=exited, status=10/n/a Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: unable to bind any inbound sockets on port 873 Jun 02 08:01:31 billlaptop.private.ycc systemd[1]: rsync.service: Failed with result 'exit-code'. Jun 02 08:01:31 billlaptop.private.ycc rsyncd[851]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 2 08:48:15 2018 InstallationDate: Installed on 2018-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1774788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
I installed version 16LTS recently and just upgraded the box to 18LTS and both display the error. I have 2 NICs (Private / Public) with an sshd config file set to only listen to the private side. It appears sshd attempt to start after the Public NIC is up, but before the private NIC is available. The Private NIC becomes available several seconds after sshd is initiated according to journalctl. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp