[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I would like to report back that on Ubuntu 20.04 with Intel AX200 network card (8087:0029), I resolved this issue by following @Hui Wang's instruction ibt-20-1-3.sfi and ibt-20-1-3.ddc from 20.10 driver HSP/HSF was greyed out before but is now available and functioning after powering off and on again. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902108] Re: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
Please check that you don't have 'timidity' installed. If the problem continues then please try a higher kernel version like this one: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.2/amd64/ ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1902108 Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: Since I upgraded from Ubuntu 18.04 to 20.04 any sound is played. The audio output is not detected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dario 9759 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:55:36 2020 InstallationDate: Installed on 2019-08-09 (446 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-10-15 (14 days ago) dmi.bios.date: 12/12/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8257 dmi.board.vendor: HP dmi.board.version: 82.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd12/12/2019:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8257:rvr82.39:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1LZ10EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902094] Re: High CPU usage while Sound Settings opened
Oddly, confirmed. Only when in Sound settings... PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1841 dan 20 0 1125668 168248 120056 S 12.9 1.0 103:17.70 Xorg 1984 dan 20 0 5481060 435396 90896 S 8.3 2.7 89:49.05 gnome-shell 346704 dan 20 0 1611480 120968 90512 S 6.0 0.7 0:06.76 gnome-control-c ** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu) ** Summary changed: - High CPU usage while Sound Settings opened + High Xorg CPU usage while Sound Settings opened ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Summary changed: - High Xorg CPU usage while Sound Settings opened + High Xorg and gnome-shell CPU usage while Sound Settings opened ** No longer affects: xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902094 Title: High Xorg and gnome-shell CPU usage while Sound Settings opened Status in gnome-control-center package in Ubuntu: Triaged Bug description: Several days ago I found huge lags over all system on my Ubuntu 20.04.1 LTS. Today I think found the problem, but not the reason. So when I open Settings -> Sound menu, the CPU usage comes to about 100%. If I close Settings window or go to other tab, it becomes OK. Nothing special in my sound configuration - monitor and notebook with built in audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04 LTS. xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:27:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0824] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0824] InstallationDate: Installed on 2020-09-12 (47 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. G5 5587 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=ef73abac-57c7-4134-90f3-1f52f41127a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 03PVDF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd02/11/2019:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn03PVDF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.product.sku: 0824 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
[Touch-packages] [Bug 1902086] Re: xorg on Ubuntu 20.04 fails to show correctly background image and icons
*** This bug is a duplicate of bug 1867668 *** https://bugs.launchpad.net/bugs/1867668 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1867668, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1867668 Visual artifacts in Gnome Shell when using the old 'intel' Xorg driver -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902086 Title: xorg on Ubuntu 20.04 fails to show correctly background image and icons Status in xorg package in Ubuntu: New Bug description: Hello I have PC with Xeon E processor and I am using integrated Intel graphics to drive a VGA display. I am using Ubuntu 20.04 Everything works fine. Then I add xorg.conf file, for other reasons, to /etc/X11 ( by default no xorg.conf file is present ) and I get the first screen after the log in is corrupted by yellow vertical lines and/or corrupted icons and eventually a block box is present at half height of the screen. See here below the incriminated xorg.conf : Section "ServerLayout" Identifier "layout" Screen 0 "intel" EndSection Section "Device" Identifier "intel" Driver "intel" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "intel" Device "intel" EndSection and photo of the corrupted screen is attached. If I open terminal or what else looks good but the first screen is always a bit corrupted. If I change the background image , the new background appears without vertical lines. If I go back to the original background image that is still corrupted with vertical lines. I am sure the corruption is because of the xorg.conf file but how can I fix the situation ? I need the xorg.conf file because I want xorg.conf to use only the internal integrated intel graphics and not other graphics cards/drivers that will be present. If I do exactly the same , adding the same xorg.conf file to on Ubuntu 18.04, same HW, same configuration, I don't see this problem. It happens only with Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902086/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901946] Re: [Lenovo ideapad 330-15ICH] Pulseaudio fails to detect card
*** This bug is a duplicate of bug 1793640 *** https://bugs.launchpad.net/bugs/1793640 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1793640, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1793640 Pulseaudio fails to detect sound card, while timidity is installed -- 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/1901946 Title: [Lenovo ideapad 330-15ICH] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading distribution pulseaudio only sees dummy output and no input ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:16:37 2020 InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Title: [HDA-Intel - HDA Intel PCH, recording] Pulseaudio fails to detect card UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846557] Re: Unable to debug any kernel on i386 qemu machine
Ignore my last comment - I took another look and it appears to be generic. -- 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/1846557 Title: Unable to debug any kernel on i386 qemu machine Status in gdb package in Ubuntu: Fix Released Bug description: Hi, On my x86_64 machine [running Ubuntu 18.04.3 LTS] with gdb version 'Ubuntu 8.1-0ubuntu3' I could happily debug any kernel running on a i386 qemu VM (qemu-system-i386) by just doing the following: > target remote localhost:1234 > b term.c:694 and then, when the breakpoint was hit I used to observe output like: > Breakpoint 1, term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) > at /home/vlad/dev/tilck/kernel/char/tty/term.c:694 And then I was able to do `s`, `si` or `c`, exactly like with regular user applications. With the newest update of gdb, version 'Ubuntu 8.1-0ubuntu3.1', instead, something is broken. By doing the same things I observe: > (gdb) b term.c:693 > warning: Breakpoint address adjusted from 0xc01158fe to 0xc01158fe. Which seems (and actually is) a bad sign, for what comes later. [why do you need to change the address? why do you want to extend it to 64-bit for a 32-bit machine?? mmm..] GDB detects the breakpoint, but in a weird way: Program received signal SIGTRAP, Trace/breakpoint trap. term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) At this point, I'm able to read the memory and the variables BUT, I cannot continue the execution, NOR doing any kind of step. The commands apparently don't get delivered to the remote side (QEMU), or they get delivered in a wrong way somehow. Example output: (gdb) b 709 warning: Breakpoint address adjusted from 0xc0115a45 to 0xc0115a45. Breakpoint 2 at 0xc0115a45: file /home/vlad/dev/tilck/kernel/char/tty/term.c, line 709. (gdb) c Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) at /home/vlad/dev/tilck/kernel/char/tty/term.c:693 693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols); (gdb) c Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) at /home/vlad/dev/tilck/kernel/char/tty/term.c:693 693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols); (gdb) c Continuing. As you see, the whole QEMU VM is stuck until I quit GDB. Note: I downgraded exclusively GDB back to version 'Ubuntu 8.1-0ubuntu3' in order to check if the problem would be fixed and it is. I'm sure the problem has been introduced in this specific version 'Ubuntu 8.1-0ubuntu3.1' and it's *not* related with QEMU *nor* with the kernel that is being debugged. It's totally independent from that. Final remark: note that I'm running gdb on x86_64 machine, while I'm debugging a kernel running on a i386 (virtual) machine. I believe that the cross-arch scenario almost certainly has something to do with the bug, as it happened in the past on both sides (qemu and gdb). Thanks a lot, Vlad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1846557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846557] Re: Unable to debug any kernel on i386 qemu machine
The fix for bug #1848200 was ARM specific. This is about x86, so it's a different issue. -- 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/1846557 Title: Unable to debug any kernel on i386 qemu machine Status in gdb package in Ubuntu: Fix Released Bug description: Hi, On my x86_64 machine [running Ubuntu 18.04.3 LTS] with gdb version 'Ubuntu 8.1-0ubuntu3' I could happily debug any kernel running on a i386 qemu VM (qemu-system-i386) by just doing the following: > target remote localhost:1234 > b term.c:694 and then, when the breakpoint was hit I used to observe output like: > Breakpoint 1, term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) > at /home/vlad/dev/tilck/kernel/char/tty/term.c:694 And then I was able to do `s`, `si` or `c`, exactly like with regular user applications. With the newest update of gdb, version 'Ubuntu 8.1-0ubuntu3.1', instead, something is broken. By doing the same things I observe: > (gdb) b term.c:693 > warning: Breakpoint address adjusted from 0xc01158fe to 0xc01158fe. Which seems (and actually is) a bad sign, for what comes later. [why do you need to change the address? why do you want to extend it to 64-bit for a 32-bit machine?? mmm..] GDB detects the breakpoint, but in a weird way: Program received signal SIGTRAP, Trace/breakpoint trap. term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) At this point, I'm able to read the memory and the variables BUT, I cannot continue the execution, NOR doing any kind of step. The commands apparently don't get delivered to the remote side (QEMU), or they get delivered in a wrong way somehow. Example output: (gdb) b 709 warning: Breakpoint address adjusted from 0xc0115a45 to 0xc0115a45. Breakpoint 2 at 0xc0115a45: file /home/vlad/dev/tilck/kernel/char/tty/term.c, line 709. (gdb) c Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) at /home/vlad/dev/tilck/kernel/char/tty/term.c:693 693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols); (gdb) c Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true) at /home/vlad/dev/tilck/kernel/char/tty/term.c:693 693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols); (gdb) c Continuing. As you see, the whole QEMU VM is stuck until I quit GDB. Note: I downgraded exclusively GDB back to version 'Ubuntu 8.1-0ubuntu3' in order to check if the problem would be fixed and it is. I'm sure the problem has been introduced in this specific version 'Ubuntu 8.1-0ubuntu3.1' and it's *not* related with QEMU *nor* with the kernel that is being debugged. It's totally independent from that. Final remark: note that I'm running gdb on x86_64 machine, while I'm debugging a kernel running on a i386 (virtual) machine. I believe that the cross-arch scenario almost certainly has something to do with the bug, as it happened in the past on both sides (qemu and gdb). Thanks a lot, Vlad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1846557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program
*** This bug is a duplicate of bug 1846557 ***
https://bugs.launchpad.net/bugs/1846557
@James: In theory it should be, but that code is from 2 different
branches - and you may well be seeing a different issue. Please report a
new bug.
--
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/1848200
Title:
gdb not stopping on breakpoint in a 32-bit program
Status in gdb package in Ubuntu:
Fix Released
Status in gdb source package in Bionic:
Fix Released
Bug description:
[Impact]
After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
on breakpoint when running a 32-bit application (on 64-bit Ubuntu).
[Test Case]
This can be reproduced with a simple “hello world” program:
$ cat hello.c
#include
int main()
{
// printf() displays the string inside quotation
printf("Hello, World!");
return 0;
}
$ gcc -ggdb -m32 hello.c
$ gdb a.out
(gdb) b hello.c:5
Breakpoint 1 at 0x536: file hello.c, line 5.
(gdb) run
Starting program: /home/user/sandbox/a.out
warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.
--- (and not stopping nor outputting the text…) ---
[Regression Risk]
Test case ran on arm64 and regression tested using the above test case on
amd64, i386 and s390x.
This regression was fixed on the upstream gdb-8.1 branch within a few
weeks of the breakage back in May 2018. Since then there have been no
other fixes in this area on that branch, implying this fixed the issue
and there were no further regressions discovered.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520928] Re: package ... failed to install/upgrade: end of file on stdin at conffile prompt
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1520928 Title: package ... failed to install/upgrade: end of file on stdin at conffile prompt Status in dpkg package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: it was about the detected the ProblemType: Package DistroRelease: Ubuntu 15.10 Package: open-vm-tools 2:9.10.2-2822639-1ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Sun Nov 29 04:58:20 2015 DuplicateSignature: package:open-vm-tools:2:9.10.2-2822639-1ubuntu3:end of file on stdin at conffile prompt ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2015-11-29 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: open-vm-tools Title: package open-vm-tools 2:9.10.2-2822639-1ubuntu3 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.vmware.tools.tools.conf: [deleted] modified.conffile..etc.vmware.tools.vm.support: [deleted] mtime.conffile..etc.pam.d.vmtoolsd: 2015-11-29T04:38:14.726165 mtime.conffile..etc.vmware.tools.poweroff.vm.default: 2015-11-29T04:37:58.870079 mtime.conffile..etc.vmware.tools.poweron.vm.default: 2015-11-29T04:37:58.986080 mtime.conffile..etc.vmware.tools.resume.vm.default: 2015-11-29T04:37:58.902079 mtime.conffile..etc.vmware.tools.scripts.vmware.network: 2015-11-29T04:37:58.942080 mtime.conffile..etc.vmware.tools.statechange.subr: 2015-11-29T04:37:58.838079 mtime.conffile..etc.vmware.tools.suspend.vm.default: 2015-11-29T04:37:56.670067 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1520928/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
I see that the burp armhf autopkgtest keeps on failing on the new zlib. I wonder if the burp-unit-test suite is really flaky and the release- pocket run only passed by chance? -- 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: Fix Committed Status in zlib package in Ubuntu: Fix Released Status in zlib source package in Focal: Fix Committed Status in zlib source package in Groovy: Fix Released 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. [Impact] * Certain rsync builds fail with "error in rsync protocol data stream" on z15. * On ubuntu, rsync normally uses zstd or lz4. But when rsync is forced to use non-default zlib compression (-z flag) it uses inflateSyncPoint() API. This can also happen when rsync on the the other end doesn't support zstd & lz4. * inflateSyncPoint() does not take into account the hardware compression state and returns an incorrect result. * Make inflateSyncPoint() fail if the hardware compression is on. The hardware does not provide enough information in order to implement this function. * Above makes rsync to succeed, when zlib uses hardware compression. [Test Case] Reproduction: z15 only: printf 1 >1 && rsync -z 1 2 [Regression Potential] * inflateSyncPoint API is rarely used. Scanning codesearch, there is a lot of false positives due to embedded copies of zlib in all the things. I do see that both rsync and backuppc-rsync use it. It used during a safety check to ensure that algorithm is not at a sync point (or that cannot be determined). Nonetheless, returning error is a safer implementation for this API call. [Other Info] * This is a regression introduced by adding & enabling zlib hw acceleration by default on z15; and discovering using rsync that one API is implemented incorrectly. 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 1902138] [NEW] Update manager failed by python
Public bug reported:
Whenever the update-manager starts,the following error occurs if
software-properties-gtk is opened that also lead to the error which was
listed next to update-manager
$ sudo update-manager
Checking for a new Ubuntu release
authenticate 'groovy.tar.gz' against 'groovy.tar.gz.gpg'
extracting 'groovy.tar.gz'
Traceback (most recent call last):
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeQuirks.py", line
197, in _get_from_and_to_version
di.version('%s' % self.controller.fromDist).split()[0]
AttributeError: 'UbuntuDistroInfo' object has no attribute 'version'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-9omt7t12/groovy", line 8, in
sys.exit(main())
File "/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeMain.py",
line 238, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeController.py",
line 2089, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeController.py",
line 1926, in fullUpgrade
if not self.doPostInitialUpdate():
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeController.py",
line 924, in doPostInitialUpdate
self.quirks.run("PostInitialUpdate")
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeQuirks.py", line
99, in run
func()
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeQuirks.py", line
118, in groovyPostInitialUpdate
self._get_from_and_to_version()
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeQuirks.py", line
203, in _get_from_and_to_version
(r.version for r in di.get_all("object")
AttributeError: 'UbuntuDistroInfo' object has no attribute 'get_all'
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in
add_to_existing
self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write
block = f.read(1048576)
File "/usr/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid
start byte
Original exception was:
Traceback (most recent call last):
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeQuirks.py", line
197, in _get_from_and_to_version
di.version('%s' % self.controller.fromDist).split()[0]
AttributeError: 'UbuntuDistroInfo' object has no attribute 'version'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-9omt7t12/groovy", line 8, in
sys.exit(main())
File "/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeMain.py",
line 238, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeController.py",
line 2089, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeController.py",
line 1926, in fullUpgrade
if not self.doPostInitialUpdate():
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeController.py",
line 924, in doPostInitialUpdate
self.quirks.run("PostInitialUpdate")
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeQuirks.py", line
99, in run
func()
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeQuirks.py", line
118, in groovyPostInitialUpdate
self._get_from_and_to_version()
File
"/tmp/ubuntu-release-upgrader-9omt7t12/DistUpgrade/DistUpgradeQuirks.py", line
203, in _get_from_and_to_version
(r.version for r in di.get_all("object")
AttributeError: 'UbuntuDistroInfo' object has no attribute 'get_all'
$ software-properties-gtk
ERROR:dbus.proxies:Introspect error on :1.198:/: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message
bus without replying
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 211, in __init__
self.backend.Reload();
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
return self._connection.call_blocking(self._named_service,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in
call_blocking
reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The
name :1.198 was not provided by
[Touch-packages] [Bug 1902135] [NEW] package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: el subproceso instalado paquete openssh-server script post-installation devolvió el código de
Public bug reported: just following the installation guide https://community.home-assistant.io/t/installing-home-assistant-supervised-on-debian-10/200253 it crashed installing openssh-server, because docker already have the port 22 binded ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 AptOrdering: ncurses-term:amd64: Install openssh-sftp-server:amd64: Install openssh-server:amd64: Install ssh-import-id:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 29 21:04:55 2020 ErrorMessage: el subproceso instalado paquete openssh-server script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2020-10-29 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: el subproceso instalado paquete openssh-server script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1902135 Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: el subproceso instalado paquete openssh-server script post- installation devolvió el código de salida de error 1 Status in openssh package in Ubuntu: New Bug description: just following the installation guide https://community.home-assistant.io/t/installing-home-assistant-supervised-on-debian-10/200253 it crashed installing openssh-server, because docker already have the port 22 binded ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 AptOrdering: ncurses-term:amd64: Install openssh-sftp-server:amd64: Install openssh-server:amd64: Install ssh-import-id:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 29 21:04:55 2020 ErrorMessage: el subproceso instalado paquete openssh-server script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2020-10-29 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.1 failed to install/upgrade: el subproceso instalado paquete openssh-server script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1902135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901020] Re: new upstream release 2020d
This bug was fixed in the package tzdata - 2020d-0ubuntu0.16.04 --- tzdata (2020d-0ubuntu0.16.04) xenial; urgency=medium * New upstream version (LP: #1901020), affecting past and future timestamps: - Palestine ends DST earlier than predicted, on 2020-10-24. - Fiji starts DST later than usual, on 2020-12-20. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. * Restore old SystemV timezones. -- Brian Murray Fri, 23 Oct 2020 14:51:23 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901020] Re: new upstream release 2020d
This bug was fixed in the package tzdata - 2020d-0ubuntu0.16.04 --- tzdata (2020d-0ubuntu0.16.04) xenial; urgency=medium * New upstream version (LP: #1901020), affecting past and future timestamps: - Palestine ends DST earlier than predicted, on 2020-10-24. - Fiji starts DST later than usual, on 2020-12-20. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. * Restore old SystemV timezones. -- Brian Murray Fri, 23 Oct 2020 14:51:23 -0700 ** Changed in: tzdata (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901020] Re: new upstream release 2020d
This bug was fixed in the package tzdata - 2020d-0ubuntu0.20.04 --- tzdata (2020d-0ubuntu0.20.04) focal; urgency=medium * New upstream version (LP: #1901020), affecting past and future timestamps: - Palestine ends DST earlier than predicted, on 2020-10-24. - Fiji starts DST later than usual, on 2020-12-20. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. * Update ICU timezone data files to 2020d. * Restore old SystemV timezones. -- Brian Murray Thu, 22 Oct 2020 12:29:22 -0700 ** Changed in: tzdata (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901020] Re: new upstream release 2020d
This bug was fixed in the package tzdata - 2020d-0ubuntu0.20.04 --- tzdata (2020d-0ubuntu0.20.04) focal; urgency=medium * New upstream version (LP: #1901020), affecting past and future timestamps: - Palestine ends DST earlier than predicted, on 2020-10-24. - Fiji starts DST later than usual, on 2020-12-20. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. * Update ICU timezone data files to 2020d. * Restore old SystemV timezones. -- Brian Murray Thu, 22 Oct 2020 12:29:22 -0700 ** Changed in: tzdata (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: tzdata (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901020] Update Released
The verification of the Stable Release Update for tzdata has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901020] Re: new upstream release 2020d
This bug was fixed in the package tzdata - 2020d-1ubuntu1 --- tzdata (2020d-1ubuntu1) groovy; urgency=medium * Merge from Debian unstable (LP: #1901020). Remaining changes: - Ship ICU timezone data files which are utilized by php and update them to 2020d. tzdata (2020d-1) unstable; urgency=high * New upstream version, affecting the following future timestamp: - Palestine ends DST earlier than predicted, on 2020-10-24. * Set urgency to high to get the package into testing before the next change. tzdata (2020c-1) unstable; urgency=medium * New upstream version, affecting the following future timestamp: - Fiji starts DST later than usual, on 2020-12-20. -- Brian Murray Thu, 22 Oct 2020 05:53:02 -0700 ** Changed in: tzdata (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: tzdata (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901020] Re: new upstream release 2020d
This bug was fixed in the package tzdata - 2020d-1ubuntu1 --- tzdata (2020d-1ubuntu1) groovy; urgency=medium * Merge from Debian unstable (LP: #1901020). Remaining changes: - Ship ICU timezone data files which are utilized by php and update them to 2020d. tzdata (2020d-1) unstable; urgency=high * New upstream version, affecting the following future timestamp: - Palestine ends DST earlier than predicted, on 2020-10-24. * Set urgency to high to get the package into testing before the next change. tzdata (2020c-1) unstable; urgency=medium * New upstream version, affecting the following future timestamp: - Fiji starts DST later than usual, on 2020-12-20. -- Brian Murray Thu, 22 Oct 2020 05:53:02 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
this is related to libssl1.0 ("libcurl3") -> libssl1.1 ("libcurl4")
transition.
The two conflict on disk.
After bionic release, we have upgraded to libssl1.1. Which means switch
to libcurl4 for everything.
There were two packages, in bionic, that did not support libssl1.1 and
thus had to use the old libssl1.0 based "libcurl3" which conflicts with
libcurl4.
Post-bionic those two packages were ported to libssl1.1 and libcurl3 was
removed from the archive.
If you must use the two apps that need libcurl3 on bionic, ensure that
you install them in a chroot/container, such that it doesn't conflict
and try to remove most of the system.
I'm not sure what i can do, to make any of this better on bionic or
xenial.
Upgrade to focal? Everything is fixed there for this.
** Also affects: curl (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: curl (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: curl (Ubuntu Bionic)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1754294
Title:
After last updated libcurl3 on libcurl4, some apps are removed.
Status in curl package in Ubuntu:
Fix Released
Status in curl source package in Bionic:
Opinion
Bug description:
Hi!
After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic)
deleted such applications as:
virtualbox-5.2
opera-stable
slack-desktop
mongodb
I really need these applications, I installed them with broken
dependencies, but they are deleted after each update. Is it possible
to make the dependence of the libcurl3 in libcurl4, and not remove it
altogether from system?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901000] Re: dmesg need permission after kernel 5.8
** Tags added: fr-886 ** Tags removed: rls-gg-incoming ** Also affects: apport (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: apport (Ubuntu) Status: New => Confirmed ** Changed in: apport (Ubuntu Groovy) Status: New => Confirmed ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu Groovy) Importance: Undecided => High -- 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/1901000 Title: dmesg need permission after kernel 5.8 Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Confirmed Status in apport source package in Groovy: Confirmed Bug description: apport used to collect dmesg well before kernel 5.8. But not it just show permission issue while collect dmesg so that apport not able to upload dmesg information for launchpad bugs after kernel 5.8. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu50 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 +0800:2020-10-15 18:43:15.784183502 +0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash Date: Thu Oct 22 18:54:46 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2157 F pulseaudio CasperMD5CheckResult: skip CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) MachineType: Dell Inc. Precision 5550 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 06/01/2020 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0203K4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 7654321 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902045] Re: package libkmod2 22-1ubuntu5.2 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: zkouším přepsat sdílený „/usr/share/doc/libkmod2/cha
*** This bug is a duplicate of bug 1658374 *** https://bugs.launchpad.net/bugs/1658374 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1658374, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1658374 package libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1902045 Title: package libkmod2 22-1ubuntu5.2 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: zkouším přepsat sdílený „/usr/share/doc/libkmod2/changelog.Debian.gz“, který se liší od ostatních instancí balíku libkmod2:i386 Status in kmod package in Ubuntu: New Bug description: I dont really know what is going on.I was trying to install a game and a steam but is not working some error occured ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkmod2 22-1ubuntu5.2 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-193.224-generic 4.4.236 Uname: Linux 4.4.0-193-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.25 Architecture: amd64 Date: Thu Oct 29 09:55:43 2020 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu11.2 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: zkouším přepsat sdílený „/usr/share/doc/libkmod2/changelog.Debian.gz“, který se liší od ostatních instancí balíku libkmod2:i386 InstallationDate: Installed on 2018-01-25 (1008 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: kmod Title: package libkmod2 22-1ubuntu5.2 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: zkouším přepsat sdílený „/usr/share/doc/libkmod2/changelog.Debian.gz“, který se liší od ostatních instancí balíku libkmod2:i386 UpgradeStatus: Upgraded to xenial on 2019-03-15 (593 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1902045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902109] Re: rsync uses lchmod and fails in Ubuntu >= 20.10
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This is interesting and I appreciate your investigation! I wonder though
if there's a third outcome here - that it's not a bug because the glibc
implementation of lchmod() requires /proc to be mounted, and if you
don't have /proc mounted then by that definition you have a broken
system and lchmod() is not expected to work, so rsync won't work, as a
design decision of upstream glibc.
I'm not claiming that this is the case, just that it's another case to
consider.
** Changed in: rsync (Ubuntu)
Status: New => Triaged
** Summary changed:
- rsync uses lchmod and fails in Ubuntu >= 20.10
+ rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1902109
Title:
rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted
Status in rsync package in Ubuntu:
Triaged
Bug description:
Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it
returned "no" before.
Steps to reproduce:
# Emulate /proc not being mounted
$ mount --bind / /mnt
$ chroot /mnt rsync -a /bin/ls .
rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not
supported (95)
rsync error: some files/attrs were not transferred (see previous errors)
(code 3) at main.c(1330) [sender=3.2.3]
I reported this issue upstream in
https://github.com/WayneD/rsync/issues/109 but the rsync developer
says it's a problem in libc, and it might well be.
Simple C code to reproduce the problem without rsync:
printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));
If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
when /proc isn't mounted, yet it succeeds if it is mounted.
Python had a similar issue, and they ended up avoiding
AC_CHECK_FUNC(lchmod) under Linux:
https://bugs.python.org/issue34652
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140
```c
if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
fi
```
So I'm not sure which package is causing the bug here. Should autoconf
return false? Should libc implement lchown without the bug? Or should
rsync skip lchmod under Linux, like python did?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1902109/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902108] [NEW] [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: Since I upgraded from Ubuntu 18.04 to 20.04 any sound is played. The audio output is not detected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dario 9759 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:55:36 2020 InstallationDate: Installed on 2019-08-09 (446 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-10-15 (14 days ago) dmi.bios.date: 12/12/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8257 dmi.board.vendor: HP dmi.board.version: 82.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd12/12/2019:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8257:rvr82.39:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1LZ10EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902108 Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: Since I upgraded from Ubuntu 18.04 to 20.04 any sound is played. The audio output is not detected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dario 9759 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:55:36 2020 InstallationDate: Installed on 2019-08-09 (446 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-10-15 (14 days ago) dmi.bios.date: 12/12/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8257 dmi.board.vendor: HP dmi.board.version: 82.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd12/12/2019:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8257:rvr82.39:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: OMEN by HP Laptop dmi.product.sku: 1LZ10EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902109] [NEW] rsync uses lchmod and fails in Ubuntu >= 20.10
Public bug reported:
Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it
returned "no" before.
Steps to reproduce:
# Emulate /proc not being mounted
$ mount --bind / /mnt
$ chroot /mnt rsync -a /bin/ls .
rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not
supported (95)
rsync error: some files/attrs were not transferred (see previous errors) (code
3) at main.c(1330) [sender=3.2.3]
I reported this issue upstream in
https://github.com/WayneD/rsync/issues/109 but the rsync developer says
it's a problem in libc, and it might well be.
Simple C code to reproduce the problem without rsync:
printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));
If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails when
/proc isn't mounted, yet it succeeds if it is mounted.
Python had a similar issue, and they ended up avoiding
AC_CHECK_FUNC(lchmod) under Linux:
https://bugs.python.org/issue34652
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140
```c
if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
fi
```
So I'm not sure which package is causing the bug here. Should autoconf
return false? Should libc implement lchown without the bug? Or should
rsync skip lchmod under Linux, like python did?
** Affects: rsync (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1902109
Title:
rsync uses lchmod and fails in Ubuntu >= 20.10
Status in rsync package in Ubuntu:
New
Bug description:
Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it
returned "no" before.
Steps to reproduce:
# Emulate /proc not being mounted
$ mount --bind / /mnt
$ chroot /mnt rsync -a /bin/ls .
rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not
supported (95)
rsync error: some files/attrs were not transferred (see previous errors)
(code 3) at main.c(1330) [sender=3.2.3]
I reported this issue upstream in
https://github.com/WayneD/rsync/issues/109 but the rsync developer
says it's a problem in libc, and it might well be.
Simple C code to reproduce the problem without rsync:
printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));
If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
when /proc isn't mounted, yet it succeeds if it is mounted.
Python had a similar issue, and they ended up avoiding
AC_CHECK_FUNC(lchmod) under Linux:
https://bugs.python.org/issue34652
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140
```c
if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
fi
```
So I'm not sure which package is causing the bug here. Should autoconf
return false? Should libc implement lchown without the bug? Or should
rsync skip lchmod under Linux, like python did?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1902109/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901020] Re: new upstream release 2020d
After confirming the behavior around SystemV timezones and changed timezones, tzdata 2020d-0ubuntu0.12.04 and tzdata 2020d- 0ubuntu0.14.04+esm1 are now published in their respective ESM releases. Thanks for preparing the updates, Brian! ** Changed in: tzdata (Ubuntu Precise) Status: In Progress => Fix Released ** Changed in: tzdata (Ubuntu Trusty) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1901020 Title: new upstream release 2020d Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following future timestamps: - Fiji starts DST later than usual, on 2020-12-20. - Palestine ends DST earlier than predicted, on 2020-10-24. - Revised predictions for Morocco's changes starting in 2023. - Canada's Yukon changes to -07 on 2020-11-01, not 2020-03-08. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. Additionally, upstream removed the "old" SystemV timezones, but the SRU will ensure that they are kept. Subsequently, these should be checked for using the following: zdump -v SystemV/MST7 zdump -v America/Phoenix The information returned by SystemV/MST7 should be included in America/Phoenix's output. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1901020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
Verification passed on Ubuntu 16.04 LTS. bdmurray@clean-xenial-amd64:~$ apt list apport Listing... Done apport/xenial-updates,xenial-updates,xenial-security,xenial-security,now 2.20.1-0ubuntu2.23 all [installed] N: There is 1 additional version. Please use the '-a' switch to see it bdmurray@clean-xenial-amd64:~$ /usr/share/apport/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' Usage: /usr/share/apport/apport [global pid] [exe path] The core dump is read from stdin. bdmurray@clean-xenial-amd64:~$ sudo apt-get update &> /dev/null; sudo apt-get install apport &> /dev/null bdmurray@clean-xenial-amd64:~$ apt list apport Listing... Done apport/xenial-proposed,xenial-proposed,now 2.20.1-0ubuntu2.26 all [installed] N: There are 3 additional versions. Please use the '-a' switch to see them. bdmurray@clean-xenial-amd64:~$ /usr/share/apport/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' ERROR: apport (pid 2644) Thu Oct 29 10:20:50 2020: cannot create lock file (uid 1000): [Errno 13] Permission denied: '/var/run/apport.lock' ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-xenial -- 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 Status in apport source package in Xenial: Fix Committed Status in apport source package in Bionic: Fix Committed Status in apport source package in Focal: Fix Committed Bug description: Impact -- apport is crashing for some users when a crash file is created about an executable which has been deleted. Test Case - While you won't get a Traceback (because there is a location for apport to print its usages message) with the following test case you will see apport usage printed: $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] With the fixed version of apport you'll see no such usage message. Regression Potential Because new code is being added its possible that the python syntax could be bad which would result in another crash, so careful review the code. Original 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 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
Verification passed on Ubuntu 18.04 LTS. bdmurray@clean-bionic-amd64:~$ apt list apport Listing... Done apport/bionic-proposed,bionic-proposed 2.20.9-0ubuntu7.19 all [upgradable from: 2.20.9-0ubuntu7.18] N: There are 3 additional versions. Please use the '-a' switch to see them. bdmurray@clean-bionic-amd64:~$ /usr/share/apport/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] [-E [EXECUTABLE_PATH]] bdmurray@clean-bionic-amd64:~$ sudo apt-get update &> /dev/null; sudo apt-get install apport python3-apport &> /dev/null bdmurray@clean-bionic-amd64:~$ apt list apport Listing... Done apport/bionic-proposed,bionic-proposed,now 2.20.9-0ubuntu7.19 all [installed,automatic] N: There are 3 additional versions. Please use the '-a' switch to see them. bdmurray@clean-bionic-amd64:~$ /usr/share/apport/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' ERROR: apport (pid 2868) Thu Oct 29 10:11:04 2020: cannot create lock file (uid 1000): [Errno 13] Permission denied: '/var/run/apport.lock' -- 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 Status in apport source package in Xenial: Fix Committed Status in apport source package in Bionic: Fix Committed Status in apport source package in Focal: Fix Committed Bug description: Impact -- apport is crashing for some users when a crash file is created about an executable which has been deleted. Test Case - While you won't get a Traceback (because there is a location for apport to print its usages message) with the following test case you will see apport usage printed: $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] With the fixed version of apport you'll see no such usage message. Regression Potential Because new code is being added its possible that the python syntax could be bad which would result in another crash, so careful review the code. Original 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 1899195] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message
Verification passed on Ubuntu 20.04 LTS. bdmurray@clean-focal-amd64:~$ apt list apport Listing... Done apport/focal-updates,focal-updates,now 2.20.11-0ubuntu27.10 all [installed] N: There are 2 additional versions. Please use the '-a' switch to see them. bdmurray@clean-focal-amd64:~$ /usr/share/apport/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] [-E [EXECUTABLE_PATH]] bdmurray@clean-focal-amd64:~$ sudo apt-get update &> /dev/null; sudo apt-get install apport python3-apport &> /dev/null bdmurray@clean-focal-amd64:~$ apt list apport Listing... Done apport/focal-proposed,focal-proposed,now 2.20.11-0ubuntu27.11 all [installed] N: There are 3 additional versions. Please use the '-a' switch to see them. bdmurray@clean-focal-amd64:~$ /usr/share/apport/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' ERROR: apport (pid 2571) Thu Oct 29 10:06:17 2020: cannot create lock file (uid 1000): [Errno 13] Permission denied: '/var/run/apport.lock' -- 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 Status in apport source package in Xenial: Fix Committed Status in apport source package in Bionic: Fix Committed Status in apport source package in Focal: Fix Committed Bug description: Impact -- apport is crashing for some users when a crash file is created about an executable which has been deleted. Test Case - While you won't get a Traceback (because there is a location for apport to print its usages message) with the following test case you will see apport usage printed: $ PYTHONPATH=/home/bdmurray/source-trees/apport/trunk data/apport '8219' '11' '0' '1' '8219' '!usr!bin!yes' '(deleted)' usage: apport [-h] [-p PID] [-s SIGNAL_NUMBER] [-c CORE_ULIMIT] [-d DUMP_MODE] [-P [GLOBAL_PID]] With the fixed version of apport you'll see no such usage message. Regression Potential Because new code is being added its possible that the python syntax could be bad which would result in another crash, so careful review the code. Original 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 764414] Re: private master bugs are confusing and lead to more duplicate filings
** Tags removed: rls-hh-incoming -- 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/764414 Title: private master bugs are confusing and lead to more duplicate filings Status in apport package in Ubuntu: Triaged Bug description: Binary package hint: apport Apport currently tracks the master bug as a private bug visible only to Ubuntu developers (bugcontrol) and makes duplicate bugs public after stripping their data. This works well but has some downsides: - Launchpad cannot show the master bug to folk reporting bugs via apport (so they file new bugs always) - After users file a new bug apport detects its a duplicate and then they cannot see the master bug and get frustrated. It would be nice to have: - the master bug be public so that reporters of dups can see it in the dupe finder and can see if a dupe is detected post-filing. - Developers still have easy access to the raw crash data. - One way to do that that does not need much development would be to have a private bug exist, linked from the master bug (e.g. with a comment or in the description; something like 'Confidential crashdump for this bug is attached to bug 12345 - only visible to Ubuntu developers'). One way to achieve this is to have apport file a new public bug to be the master. This would have the necessary metadata and would include the link to the private bug + gather all the duplicates to itself. One downside is that Apport would appear to be the bug reporter for all crashdump based bug reports. That's not necessarily a bad thing, but it may confuse people. Another way would be to have apport file a new private bug, move the attachments over from the original bug, add explanation and metadata in the description, subscribe bugcontrol and then sanitise the original bug report the same way it sanitises public bugs today. This would make the original bug be the public master, preserving the date of filing and the reporter. OTOH large files would need to be shuffled around and this might be unreliable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/764414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424768] Re: Consider switching to path based activation
** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1424768 Title: Consider switching to path based activation Status in whoopsie package in Ubuntu: Confirmed Status in whoopsie source package in Bionic: Confirmed Bug description: 1) Ubuntu 15.04 2) 0.2.46 3) Whoopsie to only run when it is needed. 4) Instead it runs constantly, using network activity, l See bug (there are more..): https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481 also try: sudo fnotifystat -p whoopsie Instead whoopsie should use path based activation to only run when /var/crash has changed. http://www.freedesktop.org/software/systemd/man/systemd.path.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875019] Re: ftbfs: Test failed: Basic functionality with the bind-mounted cache dir
do you still see the issue? ** Changed in: fontconfig (Ubuntu) Status: New => Incomplete -- 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/1875019 Title: ftbfs: Test failed: Basic functionality with the bind-mounted cache dir Status in fontconfig package in Ubuntu: Incomplete Bug description: 1) apt-src install fontconfig 2) cd fontconfig-2.13.1/ 3) debuild -us -uc -b gets to PASS: test-hash PASS: test-bz106632 FAIL: run-test.sh fontconfig 2.13.1: test/test-suite.log # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: run-test == Running: Basic check Running: With a subdir Running: Subdir with a cache file Running: Complicated directory structure Running: Subdir with an out-of-date cache file Running: Dir with an out-of-date cache file Running: Re-creating .uuid Running: Consistency between .uuid and cache name b41b6931-2503-44dd-a5d0-465a2c171511/home/z/fontconfig-2.13.1/test/cache.dir/08acdce6-36bc-4684-9a7b-0f24192abc6b-le64.cache-7 Running: Keep mtime of the font directory Running: Basic functionality with the bind-mounted cache dir *** Test failed: Basic functionality with the bind-mounted cache dir cache was updated. FAIL run-test.sh (exit status: 1) ubuntu: focal 20.04 LTS fontconfig1: fontconfig: Installed: 2.13.1-2ubuntu3 Candidate: 2.13.1-2ubuntu3 Version table: *** 2.13.1-2ubuntu3 500 500 http://speglar.simnet.is/ubuntu focal/main amd64 Packages 500 http://ubuntu.hysing.is/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fontconfig 2.13.1-2ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 25 13:15:14 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fontconfig UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1875019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902094] [NEW] High CPU usage while Sound Settings opened
Public bug reported: Several days ago I found huge lags over all system on my Ubuntu 20.04.1 LTS. Today I think found the problem, but not the reason. So when I open Settings -> Sound menu, the CPU usage comes to about 100%. If I close Settings window or go to other tab, it becomes OK. Nothing special in my sound configuration - monitor and notebook with built in audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04 LTS. xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:27:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0824] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0824] InstallationDate: Installed on 2020-09-12 (47 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. G5 5587 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=ef73abac-57c7-4134-90f3-1f52f41127a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 03PVDF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd02/11/2019:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn03PVDF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.product.sku: 0824 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal performance ubuntu ** Attachment added: "top screenshot" https://bugs.launchpad.net/bugs/1902094/+attachment/5429064/+files/Screenshot%20from%202020-10-29%2018-11-53.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902094 Title: High CPU usage while Sound Settings opened Status in xorg package in Ubuntu: New Bug description: Several days ago I found huge lags over all system on my Ubuntu 20.04.1 LTS. Today I think found the problem, but not the reason. So when I open Settings -> Sound menu, the CPU usage comes to about 100%. If I close Settings window or go to other tab, it becomes OK. Nothing special in my sound configuration - monitor and notebook with built in audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04 LTS. xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04
[Touch-packages] [Bug 1901723] Re: backport Refactor BN_R_NO_INVERSE logic in internal functions
** Tags removed: rls-ff-incoming rls-gg-incoming rls-hh-incoming ** Tags added: fr-872 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1901723 Title: backport Refactor BN_R_NO_INVERSE logic in internal functions Status in openssl package in Ubuntu: Confirmed Bug description: backport Refactor BN_R_NO_INVERSE logic in internal functions https://github.com/openssl/openssl/commit/35bb0e44c6168facbb3acedbc7d4f2dcbdd65224 https://github.com/openssl/openssl/issues/12129 https://github.com/pyca/cryptography/issues/5521#issuecomment-717293145 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1901723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902088] [NEW] u8_totitle() fails to handle "." as a word separator
Public bug reported:
u8_totitle() fails to handle "." as a word separator, though the dot is
commonly used without any space-character where initials precede a surname.
for example, the street address "Largo A.Gemelli"is rendered "Largo A.gemelli"
I find it necessary to include the dot (.), comma (,), opening and
closing parentheses [(,)], hyphen (-), single and double quotes (',"),
and the forward slash (/) as word separators; but the dot (.) is the
most common, after the correctly-handled space ( ).
I have libunistring 0.9.10-2
under Ubuntu 20.04 LTS
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
apt-cache policy libunistring2
libunistring2:
Installed: 0.9.10-2
Candidate: 0.9.10-2
Version table:
*** 0.9.10-2 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
** Affects: libunistring (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunistring in Ubuntu.
https://bugs.launchpad.net/bugs/1902088
Title:
u8_totitle() fails to handle "." as a word separator
Status in libunistring package in Ubuntu:
New
Bug description:
u8_totitle() fails to handle "." as a word separator, though the dot is
commonly used without any space-character where initials precede a surname.
for example, the street address "Largo A.Gemelli"is rendered "Largo A.gemelli"
I find it necessary to include the dot (.), comma (,), opening and
closing parentheses [(,)], hyphen (-), single and double quotes (',"),
and the forward slash (/) as word separators; but the dot (.) is the
most common, after the correctly-handled space ( ).
I have libunistring 0.9.10-2
under Ubuntu 20.04 LTS
lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
apt-cache policy libunistring2
libunistring2:
Installed: 0.9.10-2
Candidate: 0.9.10-2
Version table:
*** 0.9.10-2 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1902088/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902086] [NEW] xorg on Ubuntu 20.04 fails to show correctly background image and icons
Public bug reported: Hello I have PC with Xeon E processor and I am using integrated Intel graphics to drive a VGA display. I am using Ubuntu 20.04 Everything works fine. Then I add xorg.conf file, for other reasons, to /etc/X11 ( by default no xorg.conf file is present ) and I get the first screen after the log in is corrupted by yellow vertical lines and/or corrupted icons and eventually a block box is present at half height of the screen. See here below the incriminated xorg.conf : Section "ServerLayout" Identifier "layout" Screen 0 "intel" EndSection Section "Device" Identifier "intel" Driver "intel" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "intel" Device "intel" EndSection and photo of the corrupted screen is attached. If I open terminal or what else looks good but the first screen is always a bit corrupted. If I change the background image , the new background appears without vertical lines. If I go back to the original background image that is still corrupted with vertical lines. I am sure the corruption is because of the xorg.conf file but how can I fix the situation ? I need the xorg.conf file because I want xorg.conf to use only the internal integrated intel graphics and not other graphics cards/drivers that will be present. If I do exactly the same , adding the same xorg.conf file to on Ubuntu 18.04, same HW, same configuration, I don't see this problem. It happens only with Ubuntu 20.04. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: 20.04 xorg ** Attachment added: "1yYZU.jpg" https://bugs.launchpad.net/bugs/1902086/+attachment/5429027/+files/1yYZU.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902086 Title: xorg on Ubuntu 20.04 fails to show correctly background image and icons Status in xorg package in Ubuntu: New Bug description: Hello I have PC with Xeon E processor and I am using integrated Intel graphics to drive a VGA display. I am using Ubuntu 20.04 Everything works fine. Then I add xorg.conf file, for other reasons, to /etc/X11 ( by default no xorg.conf file is present ) and I get the first screen after the log in is corrupted by yellow vertical lines and/or corrupted icons and eventually a block box is present at half height of the screen. See here below the incriminated xorg.conf : Section "ServerLayout" Identifier "layout" Screen 0 "intel" EndSection Section "Device" Identifier "intel" Driver "intel" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "intel" Device "intel" EndSection and photo of the corrupted screen is attached. If I open terminal or what else looks good but the first screen is always a bit corrupted. If I change the background image , the new background appears without vertical lines. If I go back to the original background image that is still corrupted with vertical lines. I am sure the corruption is because of the xorg.conf file but how can I fix the situation ? I need the xorg.conf file because I want xorg.conf to use only the internal integrated intel graphics and not other graphics cards/drivers that will be present. If I do exactly the same , adding the same xorg.conf file to on Ubuntu 18.04, same HW, same configuration, I don't see this problem. It happens only with Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902086/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1044549] Re: The "Access Prompt" randomly pop up!
Forgot: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734908 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748729 ** Bug watch added: Debian Bug tracker #734908 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734908 ** Bug watch added: Debian Bug tracker #748729 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748729 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1044549 Title: The "Access Prompt" randomly pop up! Status in gcr package in Ubuntu: Triaged Bug description: Access Prompt randomly pop up and prompt you for the password. Have you ever when opened Youtube, Facebook, Launchpad account!n And now opened a picture of the computer when pop up"Access Prompt" I use autologin. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gcr 3.5.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 Date: Fri Aug 31 22:33:44 2012 ExecutablePath: /usr/lib/gcr/gcr-prompter InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) SourcePackage: gcr UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (gnome-settings-daemon:1401): libappindicator-WARNING **: Unable to connect to the Notification Watcher: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.48 was not provided by any .service files (gnome-control-center:2016): background-cc-panel-WARNING **: Could not load /usr/share/themes/Adwaita/index.theme: Nincs ilyen fájl vagy könyvtár (gnome-control-center:2016): GLib-GIO-CRITICAL **: g_settings_set_value: assertion `G_IS_SETTINGS (settings)' failed (gnome-control-center:2016): Gtk-CRITICAL **: gtk_builder_get_object: assertion `GTK_IS_BUILDER (builder)' failed (gnome-control-center:2016): Gtk-CRITICAL **: gtk_icon_view_get_selected_items: assertion `GTK_IS_ICON_VIEW (icon_view)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1044549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901946] Re: [Lenovo ideapad 330-15ICH] Pulseaudio fails to detect card
Timidity deinstalled. The sound is back. thanks, Daniel. You can close the ticket. -- 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/1901946 Title: [Lenovo ideapad 330-15ICH] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading distribution pulseaudio only sees dummy output and no input ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:16:37 2020 InstallationDate: Installed on 2019-03-26 (581 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Title: [HDA-Intel - HDA Intel PCH, recording] Pulseaudio fails to detect card UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) dmi.bios.date: 10/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN34WW:bd10/15/2019:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901295] Re: python3-chardet breaks install of python-chardet
Sorry for the typos: I meant "with the Hope", and "my Python2 application doesn't really depend on python-chardet". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-chardet in Ubuntu. https://bugs.launchpad.net/bugs/1901295 Title: python3-chardet breaks install of python-chardet Status in python3-chardet package in Ubuntu: Incomplete Bug description: I'm trying to install python-chardet (for python-2.7), but it fails because latest python3-chardet breaks python-chardet. I fail to understand why the python3 version of chardet would break the python2.7 version of the same module. PS: I know that python2.7 is not supported anymore, but I have an application that depends on it, and I need to install it, and that's now impossible because of this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-chardet/+bug/1901295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456338] Re: USB floppy drive is running without floppy
I found a partial workaround to this problem:
The solution has been tested under Ubuntu 14.04 and should work also on
more recent versions of Ubuntu.
This solution works only for the cheap Teac USB floppy controllers (for
other usb controllers you will maybe have to adapt the solution
yourself):
In the terminal simply type lsscsi (if it's not installed type sudo apt-
get install lsscsi):
Output: [6:0:0:0]diskTEAC USB UF000x 0.00
If you don't see TEAC and USB UF000x when the floppy drive is connected,
this solution is not for you.
Create this file with administrative privileges :
/etc/udev/rules.d/00-teacfloppy.rules
Paste in this line:
ACTION=="add", SUBSYSTEM=="block", ATTR{removable}=="1",
ATTRS{idVendor}=="0644", ATTRS{idProduct}=="",
ATTR{events_poll_msecs}="-1"
Save and reboot.
The drive will seek for a few seconds then the motor will quickly stop.
--
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/1456338
Title:
USB floppy drive is running without floppy
Status in systemd package in Ubuntu:
New
Bug description:
When I connect USB floppy drive (Gembird) without floppy under Ubuntu, the
drive engine seems to be running (the floppy drive LED is on and the drive is
sounding). The same behaviour takes place if I connect the drive with a floppy
and then remove the floppy. It seems that the system accesses the drive
permanently when there is no floppy. Under Windows XP it works normally - when
there is no floppy, the LED and engine are switched off. I have tried Ubuntu
14.10 (amd64) with upstart, LXQt and KDE 5; Ubuntu 15.04 with systemd, LXQt -
the same behaviour.
If I boot using bash as init (init=/bin/bash) and connect the floppy drive
after boot, the engine is off (the normal behaviour).
lsof /dev/sdb during engine running outputs nothing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456338/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901295] Re: python3-chardet breaks install of python-chardet
Hi Paride, I've just reported this bug for the record, and with the ope that it could help other people with the same problem. As to me, I have already found a workaround: my Python2 doesn't really depend on python-chardet, but on python-requests (which itself depends on python-chardet). So i "fixed" it by creating my own "python-requests-with-chardet" package which includes both python-request and python-chardet modules. This way I can install my application without generating a conflict with python3-chardet. If no proper solution can be found in Debian/Ubuntu, feel free to just close it WONTFIX. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-chardet in Ubuntu. https://bugs.launchpad.net/bugs/1901295 Title: python3-chardet breaks install of python-chardet Status in python3-chardet package in Ubuntu: Incomplete Bug description: I'm trying to install python-chardet (for python-2.7), but it fails because latest python3-chardet breaks python-chardet. I fail to understand why the python3 version of chardet would break the python2.7 version of the same module. PS: I know that python2.7 is not supported anymore, but I have an application that depends on it, and I need to install it, and that's now impossible because of this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-chardet/+bug/1901295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901295] Re: python3-chardet breaks install of python-chardet
Hi Julien and thanks for filing this bug. I think your suggestion could work in principle, however I doubt it will be implemented in practice. It would mean modifying a package to support an unsupported package and more in general an unsupported setup. Splitting the package in Debian would require it to go through the NEW queue again, which can be a quite lengthy process. Moreover Ubuntu would pickup the fixed package only in Hirsute (at best), so your existing systems wouldn't get the fix. Fixing the package directly in Ubuntu isn't a good idea either, as it's currently a sync from Debian, and we tend to avoid adding package deltas when possible, and still the fix could only land in Hirsute. If you still want to try this way I suggest you to file a bug in Debian and wait for the package maintainers opinion, however the true way forward here is to leave Python2 behind. If that's not an option you can still stick to Bionic for the moment, it's supported until 2028. I'm setting this bug to Incomplete to leave it open for further discussion if needed, but I think it should be considered a Won't Fix. ** Changed in: python3-chardet (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-chardet in Ubuntu. https://bugs.launchpad.net/bugs/1901295 Title: python3-chardet breaks install of python-chardet Status in python3-chardet package in Ubuntu: Incomplete Bug description: I'm trying to install python-chardet (for python-2.7), but it fails because latest python3-chardet breaks python-chardet. I fail to understand why the python3 version of chardet would break the python2.7 version of the same module. PS: I know that python2.7 is not supported anymore, but I have an application that depends on it, and I need to install it, and that's now impossible because of this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-chardet/+bug/1901295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902045] [NEW] package libkmod2 22-1ubuntu5.2 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: zkouším přepsat sdílený „/usr/share/doc/libkmod2/c
Public bug reported: I dont really know what is going on.I was trying to install a game and a steam but is not working some error occured ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkmod2 22-1ubuntu5.2 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-193.224-generic 4.4.236 Uname: Linux 4.4.0-193-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.25 Architecture: amd64 Date: Thu Oct 29 09:55:43 2020 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu11.2 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: zkouším přepsat sdílený „/usr/share/doc/libkmod2/changelog.Debian.gz“, který se liší od ostatních instancí balíku libkmod2:i386 InstallationDate: Installed on 2018-01-25 (1008 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: kmod Title: package libkmod2 22-1ubuntu5.2 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: zkouším přepsat sdílený „/usr/share/doc/libkmod2/changelog.Debian.gz“, který se liší od ostatních instancí balíku libkmod2:i386 UpgradeStatus: Upgraded to xenial on 2019-03-15 (593 days ago) ** Affects: kmod (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1902045 Title: package libkmod2 22-1ubuntu5.2 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: zkouším přepsat sdílený „/usr/share/doc/libkmod2/changelog.Debian.gz“, který se liší od ostatních instancí balíku libkmod2:i386 Status in kmod package in Ubuntu: New Bug description: I dont really know what is going on.I was trying to install a game and a steam but is not working some error occured ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkmod2 22-1ubuntu5.2 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-193.224-generic 4.4.236 Uname: Linux 4.4.0-193-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.25 Architecture: amd64 Date: Thu Oct 29 09:55:43 2020 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu11.2 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: zkouším přepsat sdílený „/usr/share/doc/libkmod2/changelog.Debian.gz“, který se liší od ostatních instancí balíku libkmod2:i386 InstallationDate: Installed on 2018-01-25 (1008 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: kmod Title: package libkmod2 22-1ubuntu5.2 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: zkouším přepsat sdílený „/usr/share/doc/libkmod2/changelog.Debian.gz“, který se liší od ostatních instancí balíku libkmod2:i386 UpgradeStatus: Upgraded to xenial on 2019-03-15 (593 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1902045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902022] Re: package dh-python 4.20191017ubuntu7 failed to install/upgrade: installed dh-python package pre-removal script subprocess returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1902022 Title: package dh-python 4.20191017ubuntu7 failed to install/upgrade: installed dh-python package pre-removal script subprocess returned error exit status 127 Status in dh-python package in Ubuntu: New Bug description: This error occured after my attempts to correct the inability to import pygame into PyCharm-Environment (it works in Python2.7 and Python3.6 and 3.8). A package distutils.utils is requested, which I cannot find anywhere and should be superseeded by setuptools. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: dh-python 4.20191017ubuntu7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 28 20:55:00 2020 DuplicateSignature: package:dh-python:4.20191017ubuntu7 Removing dh-python (4.20191017ubuntu7) ... /var/lib/dpkg/info/dh-python.prerm: 7: py3clean: not found dpkg: error processing package dh-python (--remove): installed dh-python package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed dh-python package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2020-04-07 (205 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dh-python Title: package dh-python 4.20191017ubuntu7 failed to install/upgrade: installed dh-python package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1902022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902022] [NEW] package dh-python 4.20191017ubuntu7 failed to install/upgrade: installed dh-python package pre-removal script subprocess returned error exit status 127
Public bug reported: This error occured after my attempts to correct the inability to import pygame into PyCharm-Environment (it works in Python2.7 and Python3.6 and 3.8). A package distutils.utils is requested, which I cannot find anywhere and should be superseeded by setuptools. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: dh-python 4.20191017ubuntu7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 28 20:55:00 2020 DuplicateSignature: package:dh-python:4.20191017ubuntu7 Removing dh-python (4.20191017ubuntu7) ... /var/lib/dpkg/info/dh-python.prerm: 7: py3clean: not found dpkg: error processing package dh-python (--remove): installed dh-python package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed dh-python package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2020-04-07 (205 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dh-python Title: package dh-python 4.20191017ubuntu7 failed to install/upgrade: installed dh-python package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dh-python (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 dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1902022 Title: package dh-python 4.20191017ubuntu7 failed to install/upgrade: installed dh-python package pre-removal script subprocess returned error exit status 127 Status in dh-python package in Ubuntu: New Bug description: This error occured after my attempts to correct the inability to import pygame into PyCharm-Environment (it works in Python2.7 and Python3.6 and 3.8). A package distutils.utils is requested, which I cannot find anywhere and should be superseeded by setuptools. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: dh-python 4.20191017ubuntu7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 28 20:55:00 2020 DuplicateSignature: package:dh-python:4.20191017ubuntu7 Removing dh-python (4.20191017ubuntu7) ... /var/lib/dpkg/info/dh-python.prerm: 7: py3clean: not found dpkg: error processing package dh-python (--remove): installed dh-python package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed dh-python package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2020-04-07 (205 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all Python3Details: /usr/bin/python3, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dh-python Title: package dh-python 4.20191017ubuntu7 failed to install/upgrade: installed dh-python package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1902022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901908] Re: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1901908 Title: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem Status in alsa-driver package in Ubuntu: Incomplete Bug description: The volume keys of my keyboard not working since the last ubuntu update release. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: lumantar 3208 F pulseaudio /dev/snd/controlC0: lumantar 3208 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 10:01:27 2020 InstallationDate: Installed on 2018-09-14 (775 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: oct 28 09:15:18 lumantar dbus-daemon[776]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=120 pid=1243 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") oct 28 09:15:23 lumantar pulseaudio[1243]: No UCM verb is valid for hw:0 oct 28 09:15:26 lumantar pulseaudio[1243]: No UCM verb is valid for hw:2 oct 28 09:19:41 lumantar systemd[1199]: pulseaudio.service: Succeeded. oct 28 09:19:51 lumantar systemd[1199]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [20354, Conexant CX20751/2, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to focal on 2020-10-21 (7 days ago) dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900059WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN31WW:bd04/20/2015:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.family: IDEAPAD dmi.product.name: 20354 dmi.product.sku: LENOVO_MT_20354_BU_idea_FM_Lenovo Z50-70 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901954] Re: Bluetooth sound card not detected
Thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be more understandable to triagers. Could you please translate them? ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1901954 Title: Bluetooth sound card not detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: Uso o Ubuntu 20.04, e por algum motibo meu fone de ouvido Beats Dr.dree nao parea com o bluetooth. Uso o Ubuntu baixado direto do site nao fiz nenhuma alteração relevante, mesmo assim o bluetooth nao funciona especificamente com o Beats Studio3 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: inuyasha 1106 F pulseaudio /dev/snd/controlC0: inuyasha 1106 F pulseaudio /dev/snd/pcmC0D0p: inuyasha 1106 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 18:08:17 2020 InstallationDate: Installed on 2020-10-24 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2012 dmi.bios.vendor: Copyright Itautec S.A. ST 4273 dmi.bios.version: F2N BI-SL2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ST 4273 dmi.board.vendor: Itautec S.A. dmi.board.version: ST-4273 Custom 01(Itau-Unibanco) dmi.chassis.type: 3 dmi.chassis.vendor: Itautec S.A. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnCopyrightItautecS.A.ST4273:bvrF2NBI-SL2:bd12/24/2012:svnItautecS.A.:pnInfowayST-4273:pvrCorp:rvnItautecS.A.:rnST4273:rvrST-4273Custom01(Itau-Unibanco):cvnItautecS.A.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Infoway ST-4273 dmi.product.sku: 40071191 dmi.product.version: Corp dmi.sys.vendor: Itautec S.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890270] Re: SRU: update gdb 9.2 for 20.04 LTS
** Changed in: gdb (Ubuntu) Status: New => Fix Released -- 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/1890270 Title: SRU: update gdb 9.2 for 20.04 LTS Status in gdb package in Ubuntu: Fix Released Status in gdb source package in Focal: Fix Released Bug description: SRU: update gdb 9.2 for 20.04 LTS according to https://sourceware.org/gdb/ this is a bug fix release: """ This is a minor corrective release over GDB 9.1, fixing the following issues: PR tui/25586 (Resizing the source/disassembly or command window produces corrupted display) PR gdb/25650 (GDB can't 'printf' a convenience variable holding an inferior address) PR build/25981 (Use of short i386 register names breaks compilation on recent Solaris 11.4) PR symtab/26003 (infinite loop loading symbols from separate debug objfile) PR build/26029 (GDB build failure on SPARC) """ Regression potential: minimal, package also not used by normal users, but for development. Acceptence criteria: Package builds, no regressions in the testsuite. The package also was part of a focal test rebuild, see LP: #1879481. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1890270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1898869] Re: System slow on booting
> a) On theory it compromises the throughput (the whole CPU time that will take > for a > process to finish will be longer) for better responsiveness, even under high > load. So > mouse clicks/UI events should be handled faster and say, when decompressing > large files > or other CPU load by specific process the user interface should not freeze. err, nope ... it will prioritize processes differently (the preemption model is completely different) and is not actually optimized for desktop style performance, i'd really go back to the generic kernel here (we'd ship the lowlatency kernel by default on the desktop images if it would actually behave like you describe ;) ) -- 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/1898869 Title: System slow on booting Status in snapd package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I have installed a Kubuntu 20.04.1 for my grandma, the system is slow to boot, takes between a minute 30 seconds to two minutes to display the Plasma Desktop. I am attaching a journalctl log and a systemd- bootchart img. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Wed Oct 7 15:26:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:14dd] InstallationDate: Installed on 2020-09-22 (14 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b404 Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 002: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X551MA ProcEnviron: LANGUAGE=ru:en_US TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgkubuntu-root ro quiet splash init=/lib/systemd/systemd-bootchart vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X551MA.515 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X551MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX551MA.515:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X551MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1898869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
