[Touch-packages] [Bug 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers
Hi Daniel, so I deleted the pulse config, and rebooted, but amazingly my stupid BIOS doesn't have an option to disable the sound. Now regardless of the kernel I go into for the output device it shows "dummy output" and the sound doesn't work. I guess the config is broken from the "rm -r ~/.config/pulse*" command. Any idea how to fix or reset things without using BIOS? Now not able to use any sound at all regardless of kernel -- 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/1898603 Title: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound output is detected as "headphones" instead of Speakers when this laptop doesn't even have any headphones connected at all... reverting to a prior kernel fixes the problem and then the output is correctly Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and the Mint Linux support chat said I should file a bug for this because this kernel broke something. See attached detailed log reports for more info... Thanks team!!! Best Regards, -Avery Tarasov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chr0meice2 2656 F pulseaudio /dev/snd/controlC0: chr0meice2 2656 F pulseaudio /dev/snd/pcmC0D0c: chr0meice2 2656 F...m pulseaudio /dev/snd/pcmC0D0p: chr0meice2 2656 F...m pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-10-05 (0 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-driver (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: ulyana Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers
Hey Daniel, Re-testing on Linux frozenkeep 5.4.0-51-generic #56-Ubuntu SMP Mon Oct 5 14:28:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux and still have the problem... I'm double checking the above and seeing if still have same issue but looks like it still is broken -- 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/1898603 Title: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound output is detected as "headphones" instead of Speakers when this laptop doesn't even have any headphones connected at all... reverting to a prior kernel fixes the problem and then the output is correctly Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and the Mint Linux support chat said I should file a bug for this because this kernel broke something. See attached detailed log reports for more info... Thanks team!!! Best Regards, -Avery Tarasov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chr0meice2 2656 F pulseaudio /dev/snd/controlC0: chr0meice2 2656 F pulseaudio /dev/snd/pcmC0D0c: chr0meice2 2656 F...m pulseaudio /dev/snd/pcmC0D0p: chr0meice2 2656 F...m pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-10-05 (0 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-driver (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: ulyana Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899619] Re: [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds
** Tags added: a2dp -- 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/1899619 Title: [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds Status in pulseaudio package in Ubuntu: New Bug description: Hello! I'm not really sure if is pulseaudio of bluez issue. Playback (from Gnome Settings sound test and Firefox), volume change, mute/resume is delayed for 2sec or bit more. I've verified this on two Ubuntu 20.04 laptops. To verify the AV receiver, I've paired MBP 2019 with OS X Catalina 10.15.7 and there are no audible delay. Here is sink information: * index: 16 name: driver: flags: HARDWARE DECIBEL_VOLUME LATENCY state: RUNNING suspend cause: (none) priority: 9550 volume: front-left: 46512 / 71% / -8,93 dB, front-right: 46512 / 71% / -8,93 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 56,81 ms max request: 4 KiB max rewind: 0 KiB monitor source: 18 sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 1 linked by: 4 fixed latency: 48,22 ms card: 17 module: 45 properties: bluetooth.protocol = "a2dp_sink" device.description = "Denon AVR-S650H" device.string = "00:05:CD:DF:C4:DD" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "speaker" bluez.path = "/org/bluez/hci0/dev_00_05_CD_DF_C4_DD" bluez.class = "0x240414" bluez.alias = "Denon AVR-S650H" device.icon_name = "audio-speakers-bluetooth" ports: speaker-output: Speaker (priority 0, latency offset 0 usec, available: yes) properties: active port: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.5-050805-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bogdan82720 F pulseaudio /dev/snd/controlC1: bogdan82720 F pulseaudio /dev/snd/controlC0: bogdan82720 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 13 13:46:35 2020 InstallationDate: Installed on 2020-08-05 (68 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Denon AVR-S650H Symptom_Type: None of the above Title: [Denon AVR-S650H, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 2.1 dmi.bios.vendor: HP dmi.bios.version: S79 Ver. 01.02.01 dmi.board.name: 8730 dmi.board.vendor: HP dmi.board.version: KBC Version 13.1C.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 19.28 dmi.modalias: dmi:bvnHP:bvrS79Ver.01.02.01:bd07/02/2020:br2.1:efr19.28:svnHP:pnHPProBook455G7:pvr:rvnHP:rn8730:rvrKBCVersion13.1C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 455 G7 dmi.product.sku: 2D242EA#ACB dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
azeam, please open a new bug by running: ubuntu-bug linux -- 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/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899628] Re: ubuntu-bug fails just after installing apt update has never been done
Yeah, or at least to have a button to start updating, so that it allows then to proceed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899628 Title: ubuntu-bug fails just after installing apt update has never been done Status in apport package in Ubuntu: New Bug description: Doing the ISO testing in a machine, that I did it staying offline. After installing, I connected and noticed a bug I wanted to report in ubuntu-drivers-common, but doing `ubuntu-bug` on it failed: This does not seem to be an official Ubuntu Package. Please retry after updating the indexes of available packages... https://i.imgur.com/fnDz6vf.png This is true as per: $ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.5.4 Candidate: 1:0.8.5.4 Version table: *** 1:0.8.5.4 100 100 /var/lib/dpkg/status However, apport should probably trigger an apt-update in such case first instead of failing, or adding a button to do this easily and then proceed with the report. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu49 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:19:30 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
Some regression with mainline kernel 5.9 (during all 5.9 release candidates I've tested as well) - my mouse has to be removed from the previous connections list and re-paired after each time the mouse goes to sleep (waiting a couple of minutes). Working fine with 5.8.x kernels. Ubuntu 20.04, HP travel mouse, Intel AX200 controller (8087:0029) in a Lenovo 14ARE05. -- 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/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 483928] Re: ssh-keyscan(1) exits prematurely on some non-fatal errors
According to the upstream bug it was fixed in version 6.8, which Ubuntu release are you using? Ubuntu >= Xenial should be fixed. -- 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/483928 Title: ssh-keyscan(1) exits prematurely on some non-fatal errors Status in portable OpenSSH: Confirmed Status in openssh package in Ubuntu: Confirmed Bug description: Binary package hint: openssh-client This concerns openssh-client 1:5.1p1-5ubuntu1 in Karmic. I am using ssh-keyscan(1) for its intended purpose: building an ssh_known_hosts file for a large network. Most of the hosts on this network are well-maintained systems, with properly-functioning SSH servers, and present no difficulty to the program. However, a handful of hosts are barely alive, with SSH servers that are not exactly in good working order. ssh-keyscan(1) currently will scan these systems, encounter some form of error, and then---right here is the problem---exit in the middle of the scan. The last bit of stderr output may look like # A.B.C.D SSH-2.0-OpenSSH_4.3 # A.B.C.E SSH-2.0-OpenSSH_4.3 # A.B.C.F SSH-1.99-OpenSSH_3.7p1 Connection closed by A.B.C.F or # A.B.C.D SSH-2.0-OpenSSH_4.1 # A.B.C.E SSH-2.0-OpenSSH_4.1 # A.B.C.F SSH-2.0-mpSSH_0.1.0 Received disconnect from A.B.C.F: 10: Protocol error or # A.B.C.D SSH-2.0-OpenSSH_4.4p1 # A.B.C.E SSH-2.0-OpenSSH_5.0p1 # A.B.C.F SSH-2.0-mpSSH_0.1.0 Received disconnect from A.B.C.F: 11: SSH Disabled (These are the different failure modes I've observed to date) ssh-keyscan(1) needs to be robust to these kinds of errors---simply make a note of them, and continue on with the scan. I don't want to have to find out which systems are misbehaving by running and re- running the scan (each run yields at most one bad host, obviously), nor manually edit out the few bad apples from the input list of hosts (especially considering that this particular subset can change over time). Neither is feasible when the number of hosts being scanned is very large. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/483928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
** Branch linked: lp:apport
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
In Progress
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Confirmed
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
--ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
--ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
-linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1898418] Re: imagehash python library won't install due to libffi dependency
This report has very little to do with systemd or with other packaged
software.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1898418
Title:
imagehash python library won't install due to libffi dependency
Status in systemd package in Ubuntu:
Invalid
Bug description:
Steps to reproduce:
pip3 install imagehash
Standard output:
ERROR: Command errored out with exit status 1:
command: /home/adam/.pyenv/versions/3.7.2/bin/python3.7 -c 'import sys,
setuptools, tokenize; sys.argv[0] =
'"'"'/tmp/pip-install-utmdqduu/imagehash/setup.py'"'"';
__file__='"'"'/tmp/pip-install-utmdqduu/imagehash/setup.py'"'"';f=getattr(tokenize,
'"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"',
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info
--egg-base /tmp/pip-pip-egg-info-aak1sa__
cwd: /tmp/pip-install-utmdqduu/imagehash/
Complete output (11 lines):
Traceback (most recent call last):
File "", line 1, in
File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/__init__.py",
line 18, in
from setuptools.dist import Distribution, Feature
File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/dist.py",
line 31, in
from setuptools import windows_support
File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/windows_support.py",
line 2, in
import ctypes
File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/ctypes/__init__.py", line 7, in
from _ctypes import Union, Structure, Array
ImportError: libffi.so.7: cannot open shared object file: No such file or
directory
ERROR: Command errored out with exit status 1: python setup.py egg_info Check
the logs for full command output.
Logfile
2020-10-04T10:17:33,752 Collecting imagehash
2020-10-04T10:17:33,753 Created temporary directory:
/tmp/pip-unpack-nj1u3xsb
2020-10-04T10:17:33,755 Using cached ImageHash-4.1.0.tar.gz (291 kB)
2020-10-04T10:17:33,764 Added imagehash from
https://files.pythonhosted.org/packages/1a/5d/cc81830be3c4705a46cdbca74439b67f1017881383ba0127c41c4cecb7b3/ImageHash-4.1.0.tar.gz#sha256=978e25d3df66ae8fa4fb24542e46cea6d0724f02c0c760b2de4931a54d5c7482
to build tracker '/tmp/pip-req-tracker-jayrgcrc'
2020-10-04T10:17:33,764 Running setup.py
(path:/tmp/pip-install-khjz0dgm/imagehash/setup.py) egg_info for package
imagehash
2020-10-04T10:17:33,764 Created temporary directory:
/tmp/pip-pip-egg-info-59aoxqk7
2020-10-04T10:17:33,765 Running command python setup.py egg_info
2020-10-04T10:17:33,848 Traceback (most recent call last):
2020-10-04T10:17:33,848 File "", line 1, in
2020-10-04T10:17:33,848 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/__init__.py",
line 18, in
2020-10-04T10:17:33,848 from setuptools.dist import Distribution,
Feature
2020-10-04T10:17:33,848 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/dist.py",
line 31, in
2020-10-04T10:17:33,848 from setuptools import windows_support
2020-10-04T10:17:33,848 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/setuptools/windows_support.py",
line 2, in
2020-10-04T10:17:33,849 import ctypes
2020-10-04T10:17:33,849 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/ctypes/__init__.py", line 7, in
2020-10-04T10:17:33,849 from _ctypes import Union, Structure, Array
2020-10-04T10:17:33,849 ImportError: libffi.so.7: cannot open shared
object file: No such file or directory
2020-10-04T10:17:33,855 ERROR: Command errored out with exit status 1: python
setup.py egg_info Check the logs for full command output.
2020-10-04T10:17:33,855 Exception information:
2020-10-04T10:17:33,855 Traceback (most recent call last):
2020-10-04T10:17:33,855 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pip/_internal/cli/base_command.py",
line 228, in _main
2020-10-04T10:17:33,855 status = self.run(options, args)
2020-10-04T10:17:33,855 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pip/_internal/cli/req_command.py",
line 182, in wrapper
2020-10-04T10:17:33,855 return func(self, options, args)
2020-10-04T10:17:33,855 File
"/home/adam/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pip/_internal/commands/install.py",
line 324, in run
2020-10-04T10:17:33,855 reqs, check_supported_wheels=not
options.target_dir
2020-10-04T10:17:33,855 File
[Touch-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Changed in: pam (Ubuntu Bionic) Status: New => Invalid ** Changed in: pam (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in gdm3 package in Ubuntu: Confirmed Status in pam package in Ubuntu: Invalid Status in gdm3 source package in Bionic: New Status in pam source package in Bionic: Invalid Status in gdm3 source package in Focal: Confirmed Status in pam source package in Focal: Invalid Status in gdm3 source package in Groovy: Confirmed Status in pam source package in Groovy: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
I've managed to workaround this in apport by creating a symlink from the
host system's /usr/share/debug/.dwz to the gdb sandbox's
/usr/share/debug/.dwz folder. That being said I still think there is an
issue with gdb not checking the debug-file-directory for the "Separate
debug info file" in the .gnu_debugaltlink section.
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apport
Importance: Undecided
Status: New
** Changed in: apport
Status: New => In Progress
** Changed in: apport
Importance: Undecided => High
** Changed in: apport
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
In Progress
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Confirmed
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
--ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
--ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
-linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
** Tags added: fr-823
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in gdb package in Ubuntu:
Confirmed
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64
/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb'
--ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute-
prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox'
--ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms
/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64
-linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox-
dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1818918/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899628] Re: ubuntu-bug fails just after installing apt update has never been done
This error message was actually recently changed and now recommends updating your apt indexes. I gather you'd like to to do more and update the indexes for you? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899628 Title: ubuntu-bug fails just after installing apt update has never been done Status in apport package in Ubuntu: New Bug description: Doing the ISO testing in a machine, that I did it staying offline. After installing, I connected and noticed a bug I wanted to report in ubuntu-drivers-common, but doing `ubuntu-bug` on it failed: This does not seem to be an official Ubuntu Package. Please retry after updating the indexes of available packages... https://i.imgur.com/fnDz6vf.png This is true as per: $ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.5.4 Candidate: 1:0.8.5.4 Version table: *** 1:0.8.5.4 100 100 /var/lib/dpkg/status However, apport should probably trigger an apt-update in such case first instead of failing, or adding a button to do this easily and then proceed with the report. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu49 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:19:30 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886714] Re: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect
If I restart and try to use my Sony headphones, then sound stutter and fails. If I run `sudo hcidump --ext avdtp`, then it works… This is weird! -- 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/1886714 Title: [Broadcom BCM20702A0] Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [
[Touch-packages] [Bug 1848731] Re: Audio output device changes upon unlock/login
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Ubuntu needs a lock feature in the gnome sound settings, because each time a device is detected the output/input will change automatically. Sometimes this feature is wanted (I plug-in a headphone) sometimes it's not (I don't want the sound output to switch to my monitor when I power it since no speakers are plugged to it) -- 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/1848731 Title: Audio output device changes upon unlock/login Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a ThinkPad X250 and updated To Ubuntu 19.10 today from 19.04. Locking/Suspending and logging in changes my audio output device. This did not happen in 19.04. How to reproduce When I lock my session with key combination "Win+L" and then unlock it again, the sound that's been playing through my headphones/speakers stops playing. When I check the audio settings, "HDMI/DisplayPort 2 - Built-in audio" is selected. When I select "Headphones - Built-in audio", sound continues playing. There is no related log output in dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1898590] Re: Verify DNS fingerprints not working
this is likely a dup of bug 1897744 -- 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/1898590 Title: Verify DNS fingerprints not working Status in openssh package in Ubuntu: New Bug description: When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints are fetched, but the result is always: debug1: found n insecure fingerprints in DNS With dig +dnssec -tsshfp hostname the result is ok: ad flg is set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1898590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault
apport information ** Tags added: apport-collected uec-images ** Description changed: [Steps to reproduce] 1) launch a focal container $ lxc launch images:ubuntu/focal focal-1897561 2) enter the container $ lxc shell focal-1897561 3) install libnginx-mod-http-perl # apt-get install -y nginx-core libnginx-mod-http-perl 4) check nginx journal # journalctl -fu nginx & 5) reload nginx 2-3 times # systemctl reload nginx Eventually you will see this from the journal: Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web server and a reverse proxy server. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, code=dumped, status=11/SEGV Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 'core-dump'. [Workaround] If libnginx-mod-http-perl is not needed, purging it and restarting nginx sidesteps the problem. [Original bug description] Ubuntu 20.04 LTS Looks that Perl 5.30 has bug that causes nginx to die, usually occurs after "service nginx reload" This looks like nginx, but it really is perl issue: https://github.com/Perl/perl5/issues/17154 Fix done in 5.32 (Perl5 commit bf0) and people are asking backport to 5.30 to get fix also to nginx. Error: Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in libperl.so.5.30.0[7fbf321a5000+166000] Symptom: Nginx terminates + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.9 + Architecture: amd64 + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + Package: perl 5.30.0-9build1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + Tags: focal uec-images + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1897561/+attachment/5421794/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault Status in perl package in Ubuntu: Incomplete Bug description: [Steps to reproduce] 1) launch a focal container $ lxc launch images:ubuntu/focal focal-1897561 2) enter the container $ lxc shell focal-1897561 3) install libnginx-mod-http-perl # apt-get install -y nginx-core libnginx-mod-http-perl 4) check nginx journal # journalctl -fu nginx & 5) reload nginx 2-3 times # systemctl reload nginx Eventually you will see this from the journal: Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web server and a reverse proxy server. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, code=dumped, status=11/SEGV Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 'core-dump'. [Workaround] If libnginx-mod-http-perl is not needed, purging it and restarting nginx sidesteps the problem. [Original bug description] Ubuntu 20.04 LTS Looks that Perl 5.30 has bug that causes nginx to die, usually occurs after "service nginx reload" This looks like nginx, but it really is perl issue: https://github.com/Perl/perl5/issues/17154 Fix done in 5.32 (Perl5 commit bf0) and people are asking backport to 5.30 to get fix also to nginx. Error: Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in libperl.so.5.30.0[7fbf321a5000+166000] Symptom: Nginx terminates --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Package: perl 5.30.0-9build1 PackageArchitecture: amd64 ProcEnviron:
[Touch-packages] [Bug 1897561] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1897561/+attachment/5421795/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault Status in perl package in Ubuntu: Incomplete Bug description: [Steps to reproduce] 1) launch a focal container $ lxc launch images:ubuntu/focal focal-1897561 2) enter the container $ lxc shell focal-1897561 3) install libnginx-mod-http-perl # apt-get install -y nginx-core libnginx-mod-http-perl 4) check nginx journal # journalctl -fu nginx & 5) reload nginx 2-3 times # systemctl reload nginx Eventually you will see this from the journal: Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web server and a reverse proxy server. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, code=dumped, status=11/SEGV Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 'core-dump'. [Workaround] If libnginx-mod-http-perl is not needed, purging it and restarting nginx sidesteps the problem. [Original bug description] Ubuntu 20.04 LTS Looks that Perl 5.30 has bug that causes nginx to die, usually occurs after "service nginx reload" This looks like nginx, but it really is perl issue: https://github.com/Perl/perl5/issues/17154 Fix done in 5.32 (Perl5 commit bf0) and people are asking backport to 5.30 to get fix also to nginx. Error: Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in libperl.so.5.30.0[7fbf321a5000+166000] Symptom: Nginx terminates --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Package: perl 5.30.0-9build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal uec-images Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1897561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault
** Description changed: + [Steps to reproduce] + + 1) launch a focal container + $ lxc launch images:ubuntu/focal focal-1897561 + 2) enter the container + $ lxc shell focal-1897561 + 3) install libnginx-mod-http-perl + # apt-get install -y nginx-core libnginx-mod-http-perl + 4) check nginx journal + # journalctl -fu nginx & + 5) reload nginx 2-3 times + # systemctl reload nginx + + Eventually you will see this from the journal: + + Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web server and a reverse proxy server. + Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, code=dumped, status=11/SEGV + Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. + Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. + Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. + Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. + Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 'core-dump'. + + + [Original bug description] + Ubuntu 20.04 LTS Looks that Perl 5.30 has bug that causes nginx to die, usually occurs after "service nginx reload" This looks like nginx, but it really is perl issue: https://github.com/Perl/perl5/issues/17154 Fix done in 5.32 (Perl5 commit bf0) and people are asking backport to 5.30 to get fix also to nginx. Error: Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in libperl.so.5.30.0[7fbf321a5000+166000] Symptom: Nginx terminates ** Description changed: [Steps to reproduce] 1) launch a focal container $ lxc launch images:ubuntu/focal focal-1897561 2) enter the container $ lxc shell focal-1897561 3) install libnginx-mod-http-perl # apt-get install -y nginx-core libnginx-mod-http-perl 4) check nginx journal # journalctl -fu nginx & 5) reload nginx 2-3 times # systemctl reload nginx Eventually you will see this from the journal: Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web server and a reverse proxy server. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, code=dumped, status=11/SEGV Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Failed with result 'core-dump'. + [Workaround] + + If libnginx-mod-http-perl is not needed, purging it and restarting nginx + sidesteps the problem. [Original bug description] Ubuntu 20.04 LTS Looks that Perl 5.30 has bug that causes nginx to die, usually occurs after "service nginx reload" This looks like nginx, but it really is perl issue: https://github.com/Perl/perl5/issues/17154 Fix done in 5.32 (Perl5 commit bf0) and people are asking backport to 5.30 to get fix also to nginx. Error: Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in libperl.so.5.30.0[7fbf321a5000+166000] Symptom: Nginx terminates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault Status in perl package in Ubuntu: Incomplete Bug description: [Steps to reproduce] 1) launch a focal container $ lxc launch images:ubuntu/focal focal-1897561 2) enter the container $ lxc shell focal-1897561 3) install libnginx-mod-http-perl # apt-get install -y nginx-core libnginx-mod-http-perl 4) check nginx journal # journalctl -fu nginx & 5) reload nginx 2-3 times # systemctl reload nginx Eventually you will see this from the journal: Oct 13 17:13:34 focal-1897561 systemd[1]: Reloaded A high performance web server and a reverse proxy server. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Main process exited, code=dumped, status=11/SEGV Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 589 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing process 588 (nginx) with signal SIGKILL. Oct 13 17:13:35 focal-1897561 systemd[1]: nginx.service: Killing
[Touch-packages] [Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
This bug was fixed in the package apport - 2.20.11-0ubuntu50 --- apport (2.20.11-0ubuntu50) groovy; urgency=medium * etc/apport/crashdb.conf: Disable Launchpad crash reports for 20.10 release. * data/apport: In the event that the crashing executable does not exist on disk any more the path name of the executable (passed by core) is appended with '(deleted)' because apport is currently using sys.argv for argument parsing there end up being too many arguments and apport crashes. This is fixed by adding handling for six arguments. (LP: #1899195) -- Brian Murray Mon, 12 Oct 2020 13:44:05 -0700 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899195 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.10, the problem page at https://errors.ubuntu.com/problem/290470c9cf5f278596966c386aac31e70a49988e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. Traceback (most recent call last): File "/usr/share/apport/apport", line 451, in options = parse_arguments() File "/usr/share/apport/apport", line 396, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' After working on https://bugs.launchpad.net/apport/+bug/1732962, the error tracker started throwing the error above. it appears that print_usage is called and throwing an error because in this context (called with core_pattern) apport doesn't have an stdout or stderr. after looking at traces it seems the kernel is adding 'deleted' to the name of the process which cause argument parsing to fail. The fix below from bdmurray seems to fix it. https://paste.ubuntu.com/p/pVKNP9kWP4/ There is report of this issue in Focal, Bionic and xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault
** Changed in: perl (Ubuntu) Importance: High => Undecided ** Changed in: perl (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault Status in perl package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS Looks that Perl 5.30 has bug that causes nginx to die, usually occurs after "service nginx reload" This looks like nginx, but it really is perl issue: https://github.com/Perl/perl5/issues/17154 Fix done in 5.32 (Perl5 commit bf0) and people are asking backport to 5.30 to get fix also to nginx. Error: Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in libperl.so.5.30.0[7fbf321a5000+166000] Symptom: Nginx terminates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1897561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault
Thank you for reporting this bug and make ubuntu better! Please run apport-collect 1897561 from a terminal to pull relevant info into your bug so developers can debug better -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault Status in perl package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 LTS Looks that Perl 5.30 has bug that causes nginx to die, usually occurs after "service nginx reload" This looks like nginx, but it really is perl issue: https://github.com/Perl/perl5/issues/17154 Fix done in 5.32 (Perl5 commit bf0) and people are asking backport to 5.30 to get fix also to nginx. Error: Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in libperl.so.5.30.0[7fbf321a5000+166000] Symptom: Nginx terminates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1897561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault
** Changed in: perl (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault Status in perl package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 LTS Looks that Perl 5.30 has bug that causes nginx to die, usually occurs after "service nginx reload" This looks like nginx, but it really is perl issue: https://github.com/Perl/perl5/issues/17154 Fix done in 5.32 (Perl5 commit bf0) and people are asking backport to 5.30 to get fix also to nginx. Error: Sep 28 07:39:43 host kernel: [1340832.811014] nginx[3253005]: segfault at 10 ip 7fbf3220d593 sp 7ffd6bba6260 error 4 in libperl.so.5.30.0[7fbf321a5000+166000] Symptom: Nginx terminates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1897561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899619] Re: [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds
Could you try reporting it upstream on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/ ? Ubuntu doesn't have a dedicated maintainer for those components at the moment and it's not likely that will get traction on launchpad ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- 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/1899619 Title: [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds Status in pulseaudio package in Ubuntu: New Bug description: Hello! I'm not really sure if is pulseaudio of bluez issue. Playback (from Gnome Settings sound test and Firefox), volume change, mute/resume is delayed for 2sec or bit more. I've verified this on two Ubuntu 20.04 laptops. To verify the AV receiver, I've paired MBP 2019 with OS X Catalina 10.15.7 and there are no audible delay. Here is sink information: * index: 16 name: driver: flags: HARDWARE DECIBEL_VOLUME LATENCY state: RUNNING suspend cause: (none) priority: 9550 volume: front-left: 46512 / 71% / -8,93 dB, front-right: 46512 / 71% / -8,93 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 56,81 ms max request: 4 KiB max rewind: 0 KiB monitor source: 18 sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 1 linked by: 4 fixed latency: 48,22 ms card: 17 module: 45 properties: bluetooth.protocol = "a2dp_sink" device.description = "Denon AVR-S650H" device.string = "00:05:CD:DF:C4:DD" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "speaker" bluez.path = "/org/bluez/hci0/dev_00_05_CD_DF_C4_DD" bluez.class = "0x240414" bluez.alias = "Denon AVR-S650H" device.icon_name = "audio-speakers-bluetooth" ports: speaker-output: Speaker (priority 0, latency offset 0 usec, available: yes) properties: active port: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.5-050805-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bogdan82720 F pulseaudio /dev/snd/controlC1: bogdan82720 F pulseaudio /dev/snd/controlC0: bogdan82720 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 13 13:46:35 2020 InstallationDate: Installed on 2020-08-05 (68 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Denon AVR-S650H Symptom_Type: None of the above Title: [Denon AVR-S650H, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 2.1 dmi.bios.vendor: HP dmi.bios.version: S79 Ver. 01.02.01 dmi.board.name: 8730 dmi.board.vendor: HP dmi.board.version: KBC Version 13.1C.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 19.28 dmi.modalias: dmi:bvnHP:bvrS79Ver.01.02.01:bd07/02/2020:br2.1:efr19.28:svnHP:pnHPProBook455G7:pvr:rvnHP:rn8730:rvrKBCVersion13.1C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 455 G7 dmi.product.sku: 2D242EA#ACB dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899603] Re: Can't upgrade on Manjaro 20.1.1
Thank you but Manjaro isn't an Ubuntu version, you should report the issue to the distribution you are using ** Changed in: fontconfig (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1899603 Title: Can't upgrade on Manjaro 20.1.1 Status in fontconfig package in Ubuntu: Invalid Bug description: Ubuntu release: Manjaro 20.1.1 using KDE+Plasma installed package version: fontconfig-ubuntu 2.13.0-2 What you expected to happen: It upgraded successfully to 2.13.1-1. What happens: It fails one of the tests during the build(when using the UI package manager) Output from build is attached in a file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1899603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881943] Re: [Inspiron 5391, Realtek ALC3204] Sound stopped to work, "error : DSP panic!" in dmesg
Seems to be fixed in sof v.1.6: https://github.com/thesofproject/sof/issues/2828 Can you add new SOF to linux-firmware? ** Bug watch added: github.com/thesofproject/sof/issues #2828 https://github.com/thesofproject/sof/issues/2828 ** Package changed: alsa-driver (Ubuntu) => linux-firmware (Ubuntu) -- 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/1881943 Title: [Inspiron 5391, Realtek ALC3204] Sound stopped to work, "error : DSP panic!" in dmesg Status in linux-firmware package in Ubuntu: New Bug description: Sound worked, but accidentally stopped to work at all. Just before it I had plugged and unplugged HDMI display (but without sound via HDMI). Only restart helped. Here is dmesg output while the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 4612 F pulseaudio /dev/snd/pcmC0D0p: username 4612 F...m pulseaudio /dev/snd/pcmC0D6c: username 4612 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 3 20:42:33 2020 InstallationDate: Installed on 2020-05-28 (5 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: июн 03 20:04:56 username-5391 dbus-daemon[3386]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=114 pid=4302 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") июн 03 20:04:59 username-5391 systemd[4295]: pulseaudio.service: Succeeded. июн 03 20:05:09 username-5391 systemd[4295]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5391, Realtek ALC3204, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 07DM2C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5391 dmi.product.sku: 096E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1881943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899329] Re: symbol U+240e seems to misrepresent the `Shift Out' character by `SS' instead of `SO'
Thank yoi for your bug report, the issue is probably rather one with the font than one from the browser utility ** Package changed: gucharmap (Ubuntu) => fonts-freefont (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-freefont in Ubuntu. https://bugs.launchpad.net/bugs/1899329 Title: symbol U+240e seems to misrepresent the `Shift Out' character by `SS' instead of `SO' Status in fonts-freefont package in Ubuntu: New Bug description: Hallo, A similar bug has been described (and repaired) earlier. See https://bugs.launchpad.net/ubuntu/+source/fonts-freefont/+bug/1070669. I first encountered this typographical error on the website of Wikipedia (using the Firefox web browser) https://en.wikipedia.org/wiki/C0_and_C1_control_codes when looking at the table representing ASCII control characters. U+240e ␎ Shift Out should probably be represented by `SO' and not `SS'. See for reference (as in the report referred to above) the following document on the Unicode website http://www.unicode.org/charts/PDF/U2400.pdf. This typographical error also seems to appear in other programs such as Libre Office Calc, the xfc4-terminal, chromium-browser. I am guessing it is visible in most, and possibly in all programs. Kind regards, Michael ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gucharmap 1:10.0.4-1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Oct 11 10:55:22 2020 InstallationDate: Installed on 2019-02-17 (601 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gucharmap UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-freefont/+bug/1899329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15
** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1899621 Title: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15 Status in Release Notes for Ubuntu: New Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899329] [NEW] symbol U+240e seems to misrepresent the `Shift Out' character by `SS' instead of `SO'
You have been subscribed to a public bug: Hallo, A similar bug has been described (and repaired) earlier. See https://bugs.launchpad.net/ubuntu/+source/fonts-freefont/+bug/1070669. I first encountered this typographical error on the website of Wikipedia (using the Firefox web browser) https://en.wikipedia.org/wiki/C0_and_C1_control_codes when looking at the table representing ASCII control characters. U+240e ␎ Shift Out should probably be represented by `SO' and not `SS'. See for reference (as in the report referred to above) the following document on the Unicode website http://www.unicode.org/charts/PDF/U2400.pdf. This typographical error also seems to appear in other programs such as Libre Office Calc, the xfc4-terminal, chromium-browser. I am guessing it is visible in most, and possibly in all programs. Kind regards, Michael ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gucharmap 1:10.0.4-1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Oct 11 10:55:22 2020 InstallationDate: Installed on 2019-02-17 (601 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gucharmap UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fonts-freefont (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- symbol U+240e seems to misrepresent the `Shift Out' character by `SS' instead of `SO' https://bugs.launchpad.net/bugs/1899329 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-freefont in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1898590] Re: Verify DNS fingerprints not working
** Tags added: server-next -- 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/1898590 Title: Verify DNS fingerprints not working Status in openssh package in Ubuntu: New Bug description: When setting in /etc/ssh/ssh_config VerifyHostKeyDNS to yes the fingerprints are fetched, but the result is always: debug1: found n insecure fingerprints in DNS With dig +dnssec -tsshfp hostname the result is ok: ad flg is set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1898590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Changed in: gdm3 (Ubuntu Groovy) Importance: Medium => High ** Also affects: pam (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pam (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Focal) Status: New => Confirmed ** Changed in: gdm3 (Ubuntu Focal) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in gdm3 package in Ubuntu: Confirmed Status in pam package in Ubuntu: Invalid Status in gdm3 source package in Bionic: New Status in pam source package in Bionic: New Status in gdm3 source package in Focal: Confirmed Status in pam source package in Focal: New Status in gdm3 source package in Groovy: Confirmed Status in pam source package in Groovy: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899645] Re: It's not possible to enable the VMware SVGA II Adapter, from software properties UI
*** This bug is a duplicate of bug 1878553 *** https://bugs.launchpad.net/bugs/1878553 ** This bug has been marked a duplicate of bug 1878553 Ubuntu could not install Virtualbox Guest addons -- 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/1899645 Title: It's not possible to enable the VMware SVGA II Adapter, from software properties UI Status in software-properties package in Ubuntu: New Bug description: I've installed ubuntu groovy in a VMware machine without selecting the easy install mode, and without requesting to install drivers automatically during setup. Once logged in, I tried to install the vmware drivers from software updates, but this is not enabled: https://i.imgur.com/MyESY7P.png If I launch `sudo ubuntu-drivers install` from a terminal, the drivers gets correctly installed (and working) instead (and UI adapts things well afterwards https://i.imgur.com/BLMk5Og.png): $ sudo ubuntu-drivers install [sudo] password for marco: Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools zerofree Suggested packages: cloud-init The following NEW packages will be installed: ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools open-vm-tools-desktop zerofree 0 upgraded, 7 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/1.191 kB of archives. After this operation, 4.849 kB of additional disk space will be used. Selecting previously unselected package ethtool. (Reading database ... 146927 files and directories currently installed.) Preparing to unpack .../0-ethtool_1%3a5.8-1_amd64.deb ... Unpacking ethtool (1:5.8-1) ... Selecting previously unselected package libmspack0:amd64. Preparing to unpack .../1-libmspack0_0.10.1-2_amd64.deb ... Unpacking libmspack0:amd64 (0.10.1-2) ... Selecting previously unselected package libxmlsec1-openssl:amd64. Preparing to unpack .../2-libxmlsec1-openssl_1.2.28-2_amd64.deb ... Unpacking libxmlsec1-openssl:amd64 (1.2.28-2) ... Selecting previously unselected package net-tools. Preparing to unpack .../3-net-tools_1.60+git20180626.aebd88e-1ubuntu2_amd64.deb ... Unpacking net-tools (1.60+git20180626.aebd88e-1ubuntu2) ... Selecting previously unselected package open-vm-tools. Preparing to unpack .../4-open-vm-tools_2%3a11.1.5-1ubuntu1_amd64.deb ... Unpacking open-vm-tools (2:11.1.5-1ubuntu1) ... Selecting previously unselected package open-vm-tools-desktop. Preparing to unpack .../5-open-vm-tools-desktop_2%3a11.1.5-1ubuntu1_amd64.deb ... Unpacking open-vm-tools-desktop (2:11.1.5-1ubuntu1) ... Selecting previously unselected package zerofree. Preparing to unpack .../6-zerofree_1.1.1-1build1_amd64.deb ... Unpacking zerofree (1.1.1-1build1) ... Setting up zerofree (1.1.1-1build1) ... Setting up net-tools (1.60+git20180626.aebd88e-1ubuntu2) ... Setting up libxmlsec1-openssl:amd64 (1.2.28-2) ... Setting up libmspack0:amd64 (0.10.1-2) ... Setting up open-vm-tools (2:11.1.5-1ubuntu1) ... Failed to restart open-vm-tools.service: Unit vgauth.service is masked. Setting up ethtool (1:5.8-1) ... Setting up open-vm-tools-desktop (2:11.1.5-1ubuntu1) ... Processing triggers for libc-bin (2.32-0ubuntu3) ... Processing triggers for systemd (246.6-1ubuntu1) ... Processing triggers for man-db (2.9.3-2) ... marco@marco-virtual-machine:~$ $ ubuntu-drivers devices == /sys/devices/pci:00/:00:0f.0 == modalias : pci:v15ADd0405sv15ADsd0405bc03sc00i00 vendor : VMware model: SVGA II Adapter driver : open-vm-tools-desktop - distro free So, ProblemType: BugDistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 15:19:54 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: allSourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) Update: once installed, if you select "Do not use the device", then close "Software & updates" and open it again, it will be in broken state again, so it should be easy to test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1899645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1899645] Re: It's not possible to enable the VMware SVGA II Adapter, from software properties UI
** Summary changed: - It's not possible to enable the VMware SVGA II Adapter after installation from UI + It's not possible to enable the VMware SVGA II Adapter, from software properties UI -- 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/1899645 Title: It's not possible to enable the VMware SVGA II Adapter, from software properties UI Status in software-properties package in Ubuntu: New Bug description: I've installed ubuntu groovy in a VMware machine without selecting the easy install mode, and without requesting to install drivers automatically during setup. Once logged in, I tried to install the vmware drivers from software updates, but this is not enabled: https://i.imgur.com/MyESY7P.png If I launch `sudo ubuntu-drivers install` from a terminal, the drivers gets correctly installed (and working) instead (and UI adapts things well afterwards https://i.imgur.com/BLMk5Og.png): $ sudo ubuntu-drivers install [sudo] password for marco: Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools zerofree Suggested packages: cloud-init The following NEW packages will be installed: ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools open-vm-tools-desktop zerofree 0 upgraded, 7 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/1.191 kB of archives. After this operation, 4.849 kB of additional disk space will be used. Selecting previously unselected package ethtool. (Reading database ... 146927 files and directories currently installed.) Preparing to unpack .../0-ethtool_1%3a5.8-1_amd64.deb ... Unpacking ethtool (1:5.8-1) ... Selecting previously unselected package libmspack0:amd64. Preparing to unpack .../1-libmspack0_0.10.1-2_amd64.deb ... Unpacking libmspack0:amd64 (0.10.1-2) ... Selecting previously unselected package libxmlsec1-openssl:amd64. Preparing to unpack .../2-libxmlsec1-openssl_1.2.28-2_amd64.deb ... Unpacking libxmlsec1-openssl:amd64 (1.2.28-2) ... Selecting previously unselected package net-tools. Preparing to unpack .../3-net-tools_1.60+git20180626.aebd88e-1ubuntu2_amd64.deb ... Unpacking net-tools (1.60+git20180626.aebd88e-1ubuntu2) ... Selecting previously unselected package open-vm-tools. Preparing to unpack .../4-open-vm-tools_2%3a11.1.5-1ubuntu1_amd64.deb ... Unpacking open-vm-tools (2:11.1.5-1ubuntu1) ... Selecting previously unselected package open-vm-tools-desktop. Preparing to unpack .../5-open-vm-tools-desktop_2%3a11.1.5-1ubuntu1_amd64.deb ... Unpacking open-vm-tools-desktop (2:11.1.5-1ubuntu1) ... Selecting previously unselected package zerofree. Preparing to unpack .../6-zerofree_1.1.1-1build1_amd64.deb ... Unpacking zerofree (1.1.1-1build1) ... Setting up zerofree (1.1.1-1build1) ... Setting up net-tools (1.60+git20180626.aebd88e-1ubuntu2) ... Setting up libxmlsec1-openssl:amd64 (1.2.28-2) ... Setting up libmspack0:amd64 (0.10.1-2) ... Setting up open-vm-tools (2:11.1.5-1ubuntu1) ... Failed to restart open-vm-tools.service: Unit vgauth.service is masked. Setting up ethtool (1:5.8-1) ... Setting up open-vm-tools-desktop (2:11.1.5-1ubuntu1) ... Processing triggers for libc-bin (2.32-0ubuntu3) ... Processing triggers for systemd (246.6-1ubuntu1) ... Processing triggers for man-db (2.9.3-2) ... marco@marco-virtual-machine:~$ $ ubuntu-drivers devices == /sys/devices/pci:00/:00:0f.0 == modalias : pci:v15ADd0405sv15ADsd0405bc03sc00i00 vendor : VMware model: SVGA II Adapter driver : open-vm-tools-desktop - distro free So, ProblemType: BugDistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 15:19:54 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: allSourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) Update: once installed, if you select "Do not use the device", then close "Software & updates" and open it again, it will be in broken state again, so it should be easy to test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1899645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1899146] Re: systemd-resolve has no --verbose or --debug flag
You can start systemd-resolved (the daemon side of it) with Environment=SYSTEMD_LOG_LEVEL=debug. Then you will have more data of what is being asked; where the requests go; what is returned, etc. Do not forget to drop caches between requests! But I do agree cli option would be nice. -- 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/1899146 Title: systemd-resolve has no --verbose or --debug flag Status in systemd package in Ubuntu: New Bug description: I understand that systemd-resolve is the tool to test queries through systemd-resolved. When investigation resolution issues (if it resolves fine with dig @server domain.to.test but not with systemd-resolved), you can use systemd-resolve --status to view the active configuration with the link related parameters, OR use systemd-resolve domain.to.test to test the resolution (but you have no details, just either a result, or a simple "not found"). It would really help a lot to have either a --verbose or a --debug flag, to see which server is queried, why, which domains are actually sent in the query (based on the search domains), was the cache used (something like the dig output would already be better). Thanks! Ubuntu version: Ubuntu 18.04.5 LTS Systemd version: 237-3ubuntu10.42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1899146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15
** Changed in: zlib (Ubuntu Groovy) Importance: Undecided => Critical ** Changed in: zlib (Ubuntu Focal) Importance: Undecided => Critical ** Also affects: ubuntu-release-notes Importance: Undecided Status: New ** Changed in: zlib (Ubuntu Groovy) Milestone: None => ubuntu-20.10 ** Changed in: zlib (Ubuntu Focal) Milestone: None => focal-updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1899621 Title: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15 Status in Release Notes for Ubuntu: New Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1899621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899647] [NEW] APT crashes on search
Public bug reported: Apt binary just crashes on search command $ apt search linux Sorting... Done Segmentation fault (core dumped) But apt-cache works: $ apt-cache search linux alsa-base - ALSA driver configuration files alsa-topology-conf - ALSA topology configuration files alsa-ucm-conf - ALSA Use Case Manager configuration files alsa-utils - Utilities for configuring and using ALSA apparmor - user-space parser utility for AppArmor auditd - User space tools for security auditing ... ... etc I had same problem on clean installations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 13 16:03:43 2020 InstallationDate: Installed on 2018-12-03 (679 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-10-03 (9 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "crashpump" https://bugs.launchpad.net/bugs/1899647/+attachment/5421741/+files/_usr_bin_apt.0.crash -- 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/1899647 Title: APT crashes on search Status in apt package in Ubuntu: New Bug description: Apt binary just crashes on search command $ apt search linux Sorting... Done Segmentation fault (core dumped) But apt-cache works: $ apt-cache search linux alsa-base - ALSA driver configuration files alsa-topology-conf - ALSA topology configuration files alsa-ucm-conf - ALSA Use Case Manager configuration files alsa-utils - Utilities for configuring and using ALSA apparmor - user-space parser utility for AppArmor auditd - User space tools for security auditing ... ... etc I had same problem on clean installations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 13 16:03:43 2020 InstallationDate: Installed on 2018-12-03 (679 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-10-03 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1899647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899645] Re: It's not possible to enable the VMware SVGA II Adapter after installation from UI
** Description changed: I've installed ubuntu groovy in a VMware machine without selecting the easy install mode, and without requesting to install drivers automatically during setup. Once logged in, I tried to install the vmware drivers from software updates, but this is not enabled: - https://i.imgur.com/MyESY7P.png + https://i.imgur.com/MyESY7P.png If I launch `sudo ubuntu-drivers install` from a terminal, the drivers - gets correctly installed (and working) instead: + gets correctly installed (and working) instead (and UI adapts things + well afterwards https://i.imgur.com/BLMk5Og.png): $ sudo ubuntu-drivers install - [sudo] password for marco: + [sudo] password for marco: Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following additional packages will be installed: - ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools zerofree + ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools zerofree Suggested packages: - cloud-init + cloud-init The following NEW packages will be installed: - ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools - open-vm-tools-desktop zerofree + ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools + open-vm-tools-desktop zerofree 0 upgraded, 7 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/1.191 kB of archives. After this operation, 4.849 kB of additional disk space will be used. Selecting previously unselected package ethtool. (Reading database ... 146927 files and directories currently installed.) Preparing to unpack .../0-ethtool_1%3a5.8-1_amd64.deb ... Unpacking ethtool (1:5.8-1) ... Selecting previously unselected package libmspack0:amd64. Preparing to unpack .../1-libmspack0_0.10.1-2_amd64.deb ... Unpacking libmspack0:amd64 (0.10.1-2) ... Selecting previously unselected package libxmlsec1-openssl:amd64. Preparing to unpack .../2-libxmlsec1-openssl_1.2.28-2_amd64.deb ... Unpacking libxmlsec1-openssl:amd64 (1.2.28-2) ... Selecting previously unselected package net-tools. Preparing to unpack .../3-net-tools_1.60+git20180626.aebd88e-1ubuntu2_amd64.deb ... Unpacking net-tools (1.60+git20180626.aebd88e-1ubuntu2) ... Selecting previously unselected package open-vm-tools. Preparing to unpack .../4-open-vm-tools_2%3a11.1.5-1ubuntu1_amd64.deb ... Unpacking open-vm-tools (2:11.1.5-1ubuntu1) ... Selecting previously unselected package open-vm-tools-desktop. Preparing to unpack .../5-open-vm-tools-desktop_2%3a11.1.5-1ubuntu1_amd64.deb ... Unpacking open-vm-tools-desktop (2:11.1.5-1ubuntu1) ... Selecting previously unselected package zerofree. Preparing to unpack .../6-zerofree_1.1.1-1build1_amd64.deb ... Unpacking zerofree (1.1.1-1build1) ... Setting up zerofree (1.1.1-1build1) ... Setting up net-tools (1.60+git20180626.aebd88e-1ubuntu2) ... Setting up libxmlsec1-openssl:amd64 (1.2.28-2) ... Setting up libmspack0:amd64 (0.10.1-2) ... Setting up open-vm-tools (2:11.1.5-1ubuntu1) ... Failed to restart open-vm-tools.service: Unit vgauth.service is masked. Setting up ethtool (1:5.8-1) ... Setting up open-vm-tools-desktop (2:11.1.5-1ubuntu1) ... Processing triggers for libc-bin (2.32-0ubuntu3) ... Processing triggers for systemd (246.6-1ubuntu1) ... Processing triggers for man-db (2.9.3-2) ... marco@marco-virtual-machine:~$ - $ ubuntu-drivers devices == /sys/devices/pci:00/:00:0f.0 == modalias : pci:v15ADd0405sv15ADsd0405bc03sc00i00 vendor : VMware model: SVGA II Adapter driver : open-vm-tools-desktop - distro free - So, - ProblemType: Bug - DistroRelease: Ubuntu 20.10 + ProblemType: BugDistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 15:19:54 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) - PackageArchitecture: all - SourcePackage: software-properties + PackageArchitecture: allSourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I've installed ubuntu groovy in a VMware machine without selecting the easy install mode, and without requesting to install drivers automatically during setup. Once logged in, I tried to install the vmware drivers from software updates, but this is not enabled: https://i.imgur.com/MyESY7P.png If I launch `sudo ubuntu-drivers install` from a terminal, the drivers gets correctly installed (and working) instead (and UI adapts things well afterwards https://i.imgur.com/BLMk5Og.png): $ sudo ubuntu-drivers install
[Touch-packages] [Bug 1899645] [NEW] It's not possible to enable the VMware SVGA II Adapter after installation from UI
Public bug reported: I've installed ubuntu groovy in a VMware machine without selecting the easy install mode, and without requesting to install drivers automatically during setup. Once logged in, I tried to install the vmware drivers from software updates, but this is not enabled: https://i.imgur.com/MyESY7P.png If I launch `sudo ubuntu-drivers install` from a terminal, the drivers gets correctly installed (and working) instead (and UI adapts things well afterwards https://i.imgur.com/BLMk5Og.png): $ sudo ubuntu-drivers install [sudo] password for marco: Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools zerofree Suggested packages: cloud-init The following NEW packages will be installed: ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools open-vm-tools-desktop zerofree 0 upgraded, 7 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/1.191 kB of archives. After this operation, 4.849 kB of additional disk space will be used. Selecting previously unselected package ethtool. (Reading database ... 146927 files and directories currently installed.) Preparing to unpack .../0-ethtool_1%3a5.8-1_amd64.deb ... Unpacking ethtool (1:5.8-1) ... Selecting previously unselected package libmspack0:amd64. Preparing to unpack .../1-libmspack0_0.10.1-2_amd64.deb ... Unpacking libmspack0:amd64 (0.10.1-2) ... Selecting previously unselected package libxmlsec1-openssl:amd64. Preparing to unpack .../2-libxmlsec1-openssl_1.2.28-2_amd64.deb ... Unpacking libxmlsec1-openssl:amd64 (1.2.28-2) ... Selecting previously unselected package net-tools. Preparing to unpack .../3-net-tools_1.60+git20180626.aebd88e-1ubuntu2_amd64.deb ... Unpacking net-tools (1.60+git20180626.aebd88e-1ubuntu2) ... Selecting previously unselected package open-vm-tools. Preparing to unpack .../4-open-vm-tools_2%3a11.1.5-1ubuntu1_amd64.deb ... Unpacking open-vm-tools (2:11.1.5-1ubuntu1) ... Selecting previously unselected package open-vm-tools-desktop. Preparing to unpack .../5-open-vm-tools-desktop_2%3a11.1.5-1ubuntu1_amd64.deb ... Unpacking open-vm-tools-desktop (2:11.1.5-1ubuntu1) ... Selecting previously unselected package zerofree. Preparing to unpack .../6-zerofree_1.1.1-1build1_amd64.deb ... Unpacking zerofree (1.1.1-1build1) ... Setting up zerofree (1.1.1-1build1) ... Setting up net-tools (1.60+git20180626.aebd88e-1ubuntu2) ... Setting up libxmlsec1-openssl:amd64 (1.2.28-2) ... Setting up libmspack0:amd64 (0.10.1-2) ... Setting up open-vm-tools (2:11.1.5-1ubuntu1) ... Failed to restart open-vm-tools.service: Unit vgauth.service is masked. Setting up ethtool (1:5.8-1) ... Setting up open-vm-tools-desktop (2:11.1.5-1ubuntu1) ... Processing triggers for libc-bin (2.32-0ubuntu3) ... Processing triggers for systemd (246.6-1ubuntu1) ... Processing triggers for man-db (2.9.3-2) ... marco@marco-virtual-machine:~$ $ ubuntu-drivers devices == /sys/devices/pci:00/:00:0f.0 == modalias : pci:v15ADd0405sv15ADsd0405bc03sc00i00 vendor : VMware model: SVGA II Adapter driver : open-vm-tools-desktop - distro free So, ProblemType: BugDistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 15:19:54 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: allSourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) Update: once installed, if you select "Do not use the device", then close "Software & updates" and open it again, it will be in broken state again, so it should be easy to test. ** Affects: software-properties (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug groovy -- 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/1899645 Title: It's not possible to enable the VMware SVGA II Adapter after installation from UI Status in software-properties package in Ubuntu: New Bug description: I've installed ubuntu groovy in a VMware machine without selecting the easy install mode, and without requesting to install drivers automatically during setup. Once logged in, I tried to install the vmware drivers from software updates, but this is not enabled: https://i.imgur.com/MyESY7P.png If I launch `sudo ubuntu-drivers install` from a terminal, the drivers gets correctly installed (and working) instead (and UI adapts things well afterwards https://i.imgur.com/BLMk5Og.png): $ sudo ubuntu-drivers
[Touch-packages] [Bug 1899638] [NEW] ubuntu-bug won't show GUI window in pure wayland-sessions
Public bug reported: In case only `WAYLAND_DISPLAY` env variable is set (but no `DISPLAY` as XWayland is disabled), ubuntu-bug won't show its window, even though GTK will use the Wayland backend. Test case, in an Ubuntu wayland session: - Run: env -u DISPLAY ubuntu-bug -w apport You will get: *** 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 (5.9 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. 92% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/.. ? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 marco@marco-virtual-machine:~$ Error: no DISPLAY environment variable specified ^C --- So, ubuntu-bug should both consider `DISPLAY` and `WAYLAND_DISPLAY` to be enough to use a graphical session. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu49 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:125:21823957:2020-10-13 15:15:42.354004383 +0200:2020-10-13 15:15:43.354004383 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 15:22:34 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899638 Title: ubuntu-bug won't show GUI window in pure wayland-sessions Status in apport package in Ubuntu: New Bug description: In case only `WAYLAND_DISPLAY` env variable is set (but no `DISPLAY` as XWayland is disabled), ubuntu-bug won't show its window, even though GTK will use the Wayland backend. Test case, in an Ubuntu wayland session: - Run: env -u DISPLAY ubuntu-bug -w apport You will get: *** 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 (5.9 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. 92% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/.. ? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 marco@marco-virtual-machine:~$ Error: no DISPLAY environment variable specified ^C --- So, ubuntu-bug should both consider `DISPLAY` and `WAYLAND_DISPLAY` to be enough to use a graphical session. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu49 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:125:21823957:2020-10-13 15:15:42.354004383 +0200:2020-10-13 15:15:43.354004383 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 15:22:34 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Touch-packages] [Bug 1899628] Re: ubuntu-bug fails just after installing apt update has never been done
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1899628 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899628 Title: ubuntu-bug fails just after installing apt update has never been done Status in apport package in Ubuntu: New Bug description: Doing the ISO testing in a machine, that I did it staying offline. After installing, I connected and noticed a bug I wanted to report in ubuntu-drivers-common, but doing `ubuntu-bug` on it failed: This does not seem to be an official Ubuntu Package. Please retry after updating the indexes of available packages... https://i.imgur.com/fnDz6vf.png This is true as per: $ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.5.4 Candidate: 1:0.8.5.4 Version table: *** 1:0.8.5.4 100 100 /var/lib/dpkg/status However, apport should probably trigger an apt-update in such case first instead of failing, or adding a button to do this easily and then proceed with the report. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu49 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:19:30 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15
** Also affects: zlib (Ubuntu Groovy) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Also affects: zlib (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1899621 Title: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15 Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1899621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899621] Re: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1899621 Title: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15 Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Bug description: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1899621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899628] [NEW] ubuntu-bug fails just after installing apt update has never been done
Public bug reported: Doing the ISO testing in a machine, that I did it staying offline. After installing, I connected and noticed a bug I wanted to report in ubuntu-drivers-common, but doing `ubuntu-bug` on it failed: This does not seem to be an official Ubuntu Package. Please retry after updating the indexes of available packages... https://i.imgur.com/fnDz6vf.png This is true as per: $ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.5.4 Candidate: 1:0.8.5.4 Version table: *** 1:0.8.5.4 100 100 /var/lib/dpkg/status However, apport should probably trigger an apt-update in such case first instead of failing, or adding a button to do this easily and then proceed with the report. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu49 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:19:30 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899628 Title: ubuntu-bug fails just after installing apt update has never been done Status in apport package in Ubuntu: New Bug description: Doing the ISO testing in a machine, that I did it staying offline. After installing, I connected and noticed a bug I wanted to report in ubuntu-drivers-common, but doing `ubuntu-bug` on it failed: This does not seem to be an official Ubuntu Package. Please retry after updating the indexes of available packages... https://i.imgur.com/fnDz6vf.png This is true as per: $ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.5.4 Candidate: 1:0.8.5.4 Version table: *** 1:0.8.5.4 100 100 /var/lib/dpkg/status However, apport should probably trigger an apt-update in such case first instead of failing, or adding a button to do this easily and then proceed with the report. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu49 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:19:30 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899621] patch
Default Comment by Bridge ** Attachment added: "patch" https://bugs.launchpad.net/bugs/1899621/+attachment/5421694/+files/patch ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => zlib (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1899621 Title: [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15 Status in zlib package in Ubuntu: New Bug description: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1899621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899621] [NEW] [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15
You have been subscribed to a public bug: Description: zlib: inflateSyncPoint() returns an incorrect result on z15 Symptom: Certain rsync builds fail with "error in rsync protocol data stream" on z15. Problem: inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. Solution: Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 ** Affects: zlib (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-188656 severity-high targetmilestone-inin2004 -- [Ubuntu 20.04] zlib: inflateSyncPoint() returns an incorrect result on z15 https://bugs.launchpad.net/bugs/1899621 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899619] [NEW] [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds
Public bug reported: Hello! I'm not really sure if is pulseaudio of bluez issue. Playback (from Gnome Settings sound test and Firefox), volume change, mute/resume is delayed for 2sec or bit more. I've verified this on two Ubuntu 20.04 laptops. To verify the AV receiver, I've paired MBP 2019 with OS X Catalina 10.15.7 and there are no audible delay. Here is sink information: * index: 16 name: driver: flags: HARDWARE DECIBEL_VOLUME LATENCY state: RUNNING suspend cause: (none) priority: 9550 volume: front-left: 46512 / 71% / -8,93 dB, front-right: 46512 / 71% / -8,93 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 56,81 ms max request: 4 KiB max rewind: 0 KiB monitor source: 18 sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 1 linked by: 4 fixed latency: 48,22 ms card: 17 module: 45 properties: bluetooth.protocol = "a2dp_sink" device.description = "Denon AVR-S650H" device.string = "00:05:CD:DF:C4:DD" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "speaker" bluez.path = "/org/bluez/hci0/dev_00_05_CD_DF_C4_DD" bluez.class = "0x240414" bluez.alias = "Denon AVR-S650H" device.icon_name = "audio-speakers-bluetooth" ports: speaker-output: Speaker (priority 0, latency offset 0 usec, available: yes) properties: active port: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.5-050805-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bogdan82720 F pulseaudio /dev/snd/controlC1: bogdan82720 F pulseaudio /dev/snd/controlC0: bogdan82720 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 13 13:46:35 2020 InstallationDate: Installed on 2020-08-05 (68 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Denon AVR-S650H Symptom_Type: None of the above Title: [Denon AVR-S650H, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 2.1 dmi.bios.vendor: HP dmi.bios.version: S79 Ver. 01.02.01 dmi.board.name: 8730 dmi.board.vendor: HP dmi.board.version: KBC Version 13.1C.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 19.28 dmi.modalias: dmi:bvnHP:bvrS79Ver.01.02.01:bd07/02/2020:br2.1:efr19.28:svnHP:pnHPProBook455G7:pvr:rvnHP:rn8730:rvrKBCVersion13.1C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 455 G7 dmi.product.sku: 2D242EA#ACB dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) -- 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/1899619 Title: [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds Status in pulseaudio package in Ubuntu: New Bug description: Hello! I'm not really sure if is pulseaudio of bluez issue. Playback (from Gnome Settings sound test and Firefox), volume change, mute/resume is delayed for 2sec or bit more. I've verified this on two Ubuntu 20.04 laptops. To verify the AV receiver, I've paired MBP 2019 with OS X Catalina 10.15.7 and there are no audible delay. Here is sink information: * index: 16 name: driver: flags: HARDWARE DECIBEL_VOLUME LATENCY state: RUNNING suspend cause: (none) priority: 9550 volume: front-left: 46512 / 71% / -8,93 dB, front-right: 46512 / 71% / -8,93 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 56,81 ms max request: 4 KiB max rewind: 0 KiB monitor source: 18 sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 1 linked by: 4 fixed latency: 48,22 ms card: 17 module: 45
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
It's not really. I've reworded it so that it's more clear. It's important to realize that this is not a regression in functionality, it works the same way as before, you just get a warning because new security features (which are arguably fairly incomplete) could not be used. ** Description changed: READ ME FIRST = - This is a cosmetic issue. The warning message is just that— a warning. Though the message comes up, there is no problem with the install/upgrade happening like normal. That said, feel free to ignore it. It will get fixed, but it's nowhere near as urgent as bugs that actually result in the wrong behavior rather than just a simple extra message. + This is only a regression on a cosmetic level. Previous versions of apt did not have any sandboxing whatsoever, so this means apt reverted back to that old behavior. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data-downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: Confirmed Status in synaptic source package in Xenial: Confirmed Status in update-notifier source package in Xenial: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is only a regression on a cosmetic level. Previous versions of apt did not have any sandboxing whatsoever, so this means apt reverted back to that old behavior. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem
[Touch-packages] [Bug 1899274] Re: India Ubuntu repository (in.archive.ubuntu.com) has corrupt file for libwebkit2gtk-4.0-37
That's a topic to take up with the indian mirror operators. in.archive.ubuntu.com canonical name = ubuntu- archive.mirrors.estointernet.in. I'm not sure if there's a better place, but I'll reassign to ubuntu generic, and assign the mirror operator. ** Package changed: apt (Ubuntu) => ubuntu ** Changed in: ubuntu Assignee: (unassigned) => Rahul makhija (rahulmkhj-i) -- 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/1899274 Title: India Ubuntu repository (in.archive.ubuntu.com) has corrupt file for libwebkit2gtk-4.0-37 Status in Ubuntu: New Bug description: The India Ubuntu repository (in.archive.ubuntu.com) has corrupt .deb file for libwebkit2gtk-4.0-37 as a result the apt upgrade process fails with following error: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: libfprint-2-tod1 Use 'sudo apt autoremove' to remove it. The following packages will be upgraded: libjavascriptcoregtk-4.0-18 libwebkit2gtk-4.0-37 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 18.3 MB of archives. After this operation, 28.7 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://in.archive.ubuntu.com/ubuntu focal-updates/main amd64 libwebkit2gtk-4.0-37 amd64 2.28.4-0ubuntu0.20.04.1 [12.8 MB] Err:1 http://in.archive.ubuntu.com/ubuntu focal-updates/main amd64 libwebkit2gtk-4.0-37 amd64 2.28.4-0ubuntu0.20.04.1 Hash Sum mismatch Hashes of expected file: - SHA512:e5e6e65c9150699fb3b6eb09434851885979e1ce8a19b05c05c8a3febea168103c0e96c8dfdeaa589b02227a0909deefaf8ef45a52b1ca384820944c3d9daa8e - SHA256:10e3ddc54631c791b158ea478d45e55f71351e52091c24bc052d57343dad3c3f - SHA1:8dbe47667cc089207d76f0de0ae5802b6bc67a2d [weak] - MD5Sum:5385544456e9c5599dc3ad0aefba59db [weak] - Filesize:12753540 [weak] Hashes of received file: - SHA512:4a26e8af5ff2b3dfc1e869701593fa609e3d534f1b8cfbef603bdf08f787f32c67a2ecef71b324cd22d324e97abe466eb08466655bc17510bea76a2484f6adf3 - SHA256:4956739cca95a4f3c132bbeebbe8acd151552883b617344bd50fb946758f6924 - SHA1:d1377c500b98c6fbecbe5a893154641a706011e8 [weak] - MD5Sum:3be3162a1cd8b2be4f07bd79fca2bb42 [weak] - Filesize:12753540 [weak] Last modification reported: Mon, 03 Aug 2020 12:53:39 + Get:2 http://in.archive.ubuntu.com/ubuntu focal-updates/main amd64 libjavascriptcoregtk-4.0-18 amd64 2.28.4-0ubuntu0.20.04.1 [5,531 kB] Fetched 18.3 MB in 37s (496 kB/s) E: Failed to fetch http://in.archive.ubuntu.com/ubuntu/pool/main/w/webkit2gtk/libwebkit2gtk-4.0-37_2.28.4-0ubuntu0.20.04.1_amd64.deb Hash Sum mismatch Hashes of expected file: - SHA512:e5e6e65c9150699fb3b6eb09434851885979e1ce8a19b05c05c8a3febea168103c0e96c8dfdeaa589b02227a0909deefaf8ef45a52b1ca384820944c3d9daa8e - SHA256:10e3ddc54631c791b158ea478d45e55f71351e52091c24bc052d57343dad3c3f - SHA1:8dbe47667cc089207d76f0de0ae5802b6bc67a2d [weak] - MD5Sum:5385544456e9c5599dc3ad0aefba59db [weak] - Filesize:12753540 [weak] Hashes of received file: - SHA512:4a26e8af5ff2b3dfc1e869701593fa609e3d534f1b8cfbef603bdf08f787f32c67a2ecef71b324cd22d324e97abe466eb08466655bc17510bea76a2484f6adf3 - SHA256:4956739cca95a4f3c132bbeebbe8acd151552883b617344bd50fb946758f6924 - SHA1:d1377c500b98c6fbecbe5a893154641a706011e8 [weak] - MD5Sum:3be3162a1cd8b2be4f07bd79fca2bb42 [weak] - Filesize:12753540 [weak] Last modification reported: Mon, 03 Aug 2020 12:53:39 + I changed the repository to US archive and it succeeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1899274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899483] Re: long hang apt install mariadb-server on Ubuntu 20.04 server
Reassigning to mariadb-10.3. Note that mariadb is in universe, and likely does not receive much if any support. ** Package changed: apt (Ubuntu) => mariadb-10.3 (Ubuntu) -- 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/1899483 Title: long hang apt install mariadb-server on Ubuntu 20.04 server Status in mariadb-10.3 package in Ubuntu: New Bug description: Ubuntu 20.04 server => no graphical user interface MariaDb is functional: mysqlshow works, mysqladmin create xxx works After 10 Minutes - the installation terminates - dbms terminates Oct 12 12:38:19 host systemd[1]: Starting MariaDB 10.3.22 database server... Oct 12 12:38:19 host mysqld[124254]: 2020-10-12 12:38:19 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 124254 ... Oct 12 12:53:19 host systemd[1]: mariadb.service: start operation timed out. Terminating. Oct 12 12:53:20 host systemd[1]: mariadb.service: Failed with result 'timeout'. Oct 12 12:53:20 host systemd[1]: Failed to start MariaDB 10.3.22 database server. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Oct 12 12:43:49 2020 ExecutablePath: /usr/bin/apt InstallationDate: Installed on 2020-05-11 (154 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1899483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884514] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2020-10-13 06:13 EDT--- The released zlib1g:s390x 1:1.2.11.dfsg-2ubuntu3 s390x passes all my tests. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1884514 Title: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement Status in Ubuntu on IBM z Systems: Fix Released Status in zlib package in Ubuntu: Fix Released Bug description: [Feature Freeze Exception] 1. Feature: The latest s390x hardware comes with a new concept for hardware assisted compression/decompression, based on a 'Next Accelerator Function unit' (NXU). This is an on-chip concept, a co-processor for compression available to all cores on the same chip. It provides functions as normal 'problem state' instructions (in other words user space instructions that are directly consumable by libraries and applications) and supports DEFLATE compliant compression/decompression + GZIP CRC/ZLIB Adler. To enable this hardware support for zlib and gzip, zlib needs to be compiled with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e". The value of 0x7e enables hardware compression for the compression levels 1-6 (out of 0-9). There is a significant business value of having the enablement active by default, since tests on a system with 4 IFLs and hardware compression enabled this way offered (especially for DEFLATE as best case) a speed up of more than 40x. 2. Changes Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro during build of zlib and gzip. 3. Regression risk The concept is new and comes with IBM z15 and LinuxONE III only and is with that specific and limited to s390x. Hence a potential regressions of this late addition would be limited to s390x and there again with the above changes to zlib (and gzip). In case of unforeseen issues with the NXU hardware component, a fallback to software is done. On top a modified zlib package was build and made available in a PPA for further testing. This change should have been included earlier, but was blocked by other zlib tickets/bugs that needed to be fixed and integrated first (like LP 1893170), hence this request for late addition. __ HW Compression need to be enabled with Default-Compression-Level 6. Adding following CFLAGS attributes during build of zlib and gzip "-DDFLTCC_LEVEL_MASK=0x7e" CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899603] [NEW] Can't upgrade on Manjaro 20.1.1
Public bug reported: Ubuntu release: Manjaro 20.1.1 using KDE+Plasma installed package version: fontconfig-ubuntu 2.13.0-2 What you expected to happen: It upgraded successfully to 2.13.1-1. What happens: It fails one of the tests during the build(when using the UI package manager) Output from build is attached in a file. ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Attachment added: "build output" https://bugs.launchpad.net/bugs/1899603/+attachment/5421647/+files/fontconfigubuntu-fail.txt -- 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/1899603 Title: Can't upgrade on Manjaro 20.1.1 Status in fontconfig package in Ubuntu: New Bug description: Ubuntu release: Manjaro 20.1.1 using KDE+Plasma installed package version: fontconfig-ubuntu 2.13.0-2 What you expected to happen: It upgraded successfully to 2.13.1-1. What happens: It fails one of the tests during the build(when using the UI package manager) Output from build is attached in a file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1899603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899588] Re: Stuck at "Add Printer" (in CUPS web interface) on Ubuntu 20.04
Not a solution, but at least a short-term solution. I edited /etc/cups/cupsd.conf and commented out the following lines: AuthType Default Require user @SYSTEM And it worked! -- 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/1899588 Title: Stuck at "Add Printer" (in CUPS web interface) on Ubuntu 20.04 Status in cups package in Ubuntu: New Bug description: I have a freshly installed Ubuntu 20.04.1 on my Lenovo ThinkPad X1 (8th gen). Whenever I go to http://localhost:631. I click on "Add Printer" and the status bar indicates that the page is loading. Nothing else happens. I'm stuck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: Unity Date: Tue Oct 13 10:01:26 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-08-24 (49 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 20U9004PFR Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=4a93b148-f388-4849-9a18-9e0e4d32c97a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET22W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9004PFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET22W(1.12):bd08/25/2020:svnLENOVO:pn20U9004PFR:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9004PFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9004PFR dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1899588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899595] [NEW] PCI/internal sound card not detected
Public bug reported: The speaker used to work fine but the internal microphone was not showing in Settings -> Sound -> Input. I tried to purge alsa. $ sudo apt-get remove --purge alsa-base pulseaudio and then reinstall it $ sudo apt-get install ubuntu-desktop alsa-base pulseaudio After that even output sound is not working.it is showing "Dummy Output" in Settings -> Sound -> Output. After that i run this command $ cat /proc/asound/cards it is showing "--- no soundcards ---" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:01:16 2020 InstallationDate: Installed on 2020-10-08 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 02VYDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd08/26/2020:svnDellInc.:pnLatitude3410:pvr:rvnDellInc.:rn02VYDM:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3410 dmi.product.sku: 09EC dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Dmesg audio log" https://bugs.launchpad.net/bugs/1899595/+attachment/5421633/+files/dmesg_grep_audio.log -- 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/1899595 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: The speaker used to work fine but the internal microphone was not showing in Settings -> Sound -> Input. I tried to purge alsa. $ sudo apt-get remove --purge alsa-base pulseaudio and then reinstall it $ sudo apt-get install ubuntu-desktop alsa-base pulseaudio After that even output sound is not working.it is showing "Dummy Output" in Settings -> Sound -> Output. After that i run this command $ cat /proc/asound/cards it is showing "--- no soundcards ---" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:01:16 2020 InstallationDate: Installed on 2020-10-08 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 02VYDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd08/26/2020:svnDellInc.:pnLatitude3410:pvr:rvnDellInc.:rn02VYDM:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3410 dmi.product.sku: 09EC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899584] Re: package udev 245.4-4ubuntu3.2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1899584 Title: package udev 245.4-4ubuntu3.2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Invalid Bug description: The bug report page occurs ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.core.rules 70-snap.zoom-client.rules 70-snap.gnome-characters.rules 70-snap.postman.rules 70-snap.vlc.rules 70-snap.stickynotes.rules 70-snap.gnome-calculator.rules 70-snap.notepad-plus-plus.rules Date: Mon Oct 12 17:13:33 2020 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-01-18 (269 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Latitude E7450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=2f2e9866-22c1-4ad8-8681-17ff7370cef9 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: systemd Title: package udev 245.4-4ubuntu3.2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.product.sku: 062E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1899584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899588] [NEW] Stuck at "Add Printer" (in CUPS web interface) on Ubuntu 20.04
Public bug reported: I have a freshly installed Ubuntu 20.04.1 on my Lenovo ThinkPad X1 (8th gen). Whenever I go to http://localhost:631. I click on "Add Printer" and the status bar indicates that the page is loading. Nothing else happens. I'm stuck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: Unity Date: Tue Oct 13 10:01:26 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-08-24 (49 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 20U9004PFR Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=4a93b148-f388-4849-9a18-9e0e4d32c97a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET22W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9004PFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET22W(1.12):bd08/25/2020:svnLENOVO:pn20U9004PFR:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9004PFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9004PFR dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1899588 Title: Stuck at "Add Printer" (in CUPS web interface) on Ubuntu 20.04 Status in cups package in Ubuntu: New Bug description: I have a freshly installed Ubuntu 20.04.1 on my Lenovo ThinkPad X1 (8th gen). Whenever I go to http://localhost:631. I click on "Add Printer" and the status bar indicates that the page is loading. Nothing else happens. I'm stuck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: Unity Date: Tue Oct 13 10:01:26 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-08-24 (49 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 20U9004PFR Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=4a93b148-f388-4849-9a18-9e0e4d32c97a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET22W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9004PFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET22W(1.12):bd08/25/2020:svnLENOVO:pn20U9004PFR:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9004PFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9004PFR dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1899588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899584] Re: package udev 245.4-4ubuntu3.2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1899584 Title: package udev 245.4-4ubuntu3.2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: The bug report page occurs ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.core.rules 70-snap.zoom-client.rules 70-snap.gnome-characters.rules 70-snap.postman.rules 70-snap.vlc.rules 70-snap.stickynotes.rules 70-snap.gnome-calculator.rules 70-snap.notepad-plus-plus.rules Date: Mon Oct 12 17:13:33 2020 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-01-18 (269 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Latitude E7450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=2f2e9866-22c1-4ad8-8681-17ff7370cef9 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: systemd Title: package udev 245.4-4ubuntu3.2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.product.sku: 062E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1899584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899584] [NEW] package udev 245.4-4ubuntu3.2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
Public bug reported: The bug report page occurs ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.core.rules 70-snap.zoom-client.rules 70-snap.gnome-characters.rules 70-snap.postman.rules 70-snap.vlc.rules 70-snap.stickynotes.rules 70-snap.gnome-calculator.rules 70-snap.notepad-plus-plus.rules Date: Mon Oct 12 17:13:33 2020 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-01-18 (269 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Latitude E7450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=2f2e9866-22c1-4ad8-8681-17ff7370cef9 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: systemd Title: package udev 245.4-4ubuntu3.2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.product.sku: 062E dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1899584 Title: package udev 245.4-4ubuntu3.2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: The bug report page occurs ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.core.rules 70-snap.zoom-client.rules 70-snap.gnome-characters.rules 70-snap.postman.rules 70-snap.vlc.rules 70-snap.stickynotes.rules 70-snap.gnome-calculator.rules 70-snap.notepad-plus-plus.rules Date: Mon Oct 12 17:13:33 2020 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-01-18 (269 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Latitude E7450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=2f2e9866-22c1-4ad8-8681-17ff7370cef9 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: systemd Title: package udev 245.4-4ubuntu3.2 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-12 (0 days ago) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.product.sku: 062E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1899584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899146] Re: systemd-resolve has no --verbose or --debug flag
Hi Sebastien, I just opened this feature request on the upstream: https://github.com/systemd/systemd/issues/17330 ** Bug watch added: github.com/systemd/systemd/issues #17330 https://github.com/systemd/systemd/issues/17330 -- 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/1899146 Title: systemd-resolve has no --verbose or --debug flag Status in systemd package in Ubuntu: New Bug description: I understand that systemd-resolve is the tool to test queries through systemd-resolved. When investigation resolution issues (if it resolves fine with dig @server domain.to.test but not with systemd-resolved), you can use systemd-resolve --status to view the active configuration with the link related parameters, OR use systemd-resolve domain.to.test to test the resolution (but you have no details, just either a result, or a simple "not found"). It would really help a lot to have either a --verbose or a --debug flag, to see which server is queried, why, which domains are actually sent in the query (based on the search domains), was the cache used (something like the dig output would already be better). Thanks! Ubuntu version: Ubuntu 18.04.5 LTS Systemd version: 237-3ubuntu10.42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1899146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
