[Touch-packages] [Bug 1884345] [NEW] printer HP laserjet P2035 prints ASCI characters and tremendously lots of pages by itself
Public bug reported: ubuntu 18.04.4 LTS release 18.04, unable to get pkgname, CUPS problem probably, printer was installed in ubuntu 16 after upgrade to 18 version was working fine for 2 years ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CupsErrorLog: E [20/Jun/2020:09:25:53 +0300] [Job 493] Stopping unresponsive job. CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 10:01:58 2020 InstallationDate: Installed on 2016-11-09 (1318 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for HP-LaserJet-P2035: hp:/usb/HP_LaserJet_P2035?serial=RZ4JQ79 MachineType: Dell Inc. Inspiron 3537 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-LaserJet-P2035.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-LaserJet-P2035.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=a09951af-688e-41b0-9891-0529420ff209 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-09-10 (648 days ago) dmi.bios.date: 08/30/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0PHTY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/30/2013:svnDellInc.:pnInspiron3537:pvrA05:rvnDellInc.:rn0PHTY0:rvrA00:cvnDellInc.:ct8:cvrA05: dmi.product.family: 00 dmi.product.name: Inspiron 3537 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1884345 Title: printer HP laserjet P2035 prints ASCI characters and tremendously lots of pages by itself Status in cups package in Ubuntu: New Bug description: ubuntu 18.04.4 LTS release 18.04, unable to get pkgname, CUPS problem probably, printer was installed in ubuntu 16 after upgrade to 18 version was working fine for 2 years ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CupsErrorLog: E [20/Jun/2020:09:25:53 +0300] [Job 493] Stopping unresponsive job. CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 10:01:58 2020 InstallationDate: Installed on 2016-11-09 (1318 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for HP-LaserJet-P2035: hp:/usb/HP_LaserJet_P2035?serial=RZ4JQ79 MachineType: Dell Inc. Inspiron 3537 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-LaserJet-P2035.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-LaserJet-P2035.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=a09951af-688e-41b0-9891-0529420ff209 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-09-10 (648 days ago) dmi.bios.date: 08/30/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0PHTY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/30/2013:svnDellInc.:pnInspiron3537:pvrA05:rvnDellInc.:rn0PHTY0:rvrA00:cvnDellInc.:ct8:cvrA05: dmi.product.family: 00 dmi.product.name: Inspiron 3537 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1884345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 725126]
Tracking the new bug here now: https://sourceware.org/bugzilla/show_bug.cgi?id=26141 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/725126 Title: gas may assemble b to locally-defined, preemptible global symbol as "b.n" Status in binutils: Fix Released Status in Linaro Binutils: Won't Fix Status in Cortex String Routines: Invalid Status in armel-cross-toolchain-base package in Ubuntu: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: There's no guarantee that R_ARM_THM_JUMP11 relocation can be resolved correctly if the symbol gets preempted. Observed in binutils-arm-linux-gnueabi 2.20.51.20100908-0ubuntu2cross1.52. Observed on binutils trunk on 2011-02-25. The problem seems to strike when the compiler optimises a sibling call to "b ", for which the assembler generates a b.n. As a side-effect of the presence of this relocation, Thumb-2 kernel modules may fail to load, since the kernel doesn't support fixing up this relocation. I believe the kernel doesn't do any symbol preemption processing when loading modules -- if so, the relocation is actually redundant. But there's no way for the kernel to detect at module load time that the relocation can safely be ignored. In kernel builds, about 1 out every 6 modules suffers from this problem. It's not clear to me whether the method used by the kernel to link .ko objects is wrong or not. It seems that either the tools should support symbol preemption in this scenario (implying that a short branch is not adequate to guarantee that preemption will work -- i.e., a gas bug) or not (in this case the fixup should be done locally and there should presumably be no relocation -- i.e., a different gas bug). It appears that passing -fno-optimize-sibling-calls to GCC can work around the problem by avoiding the generation of local branches to global symbols, but this is clearly not the correct fix. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/725126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 725126] Re: gas may assemble b to locally-defined, preemptible global symbol as "b.n"
** Bug watch added: Sourceware.org Bugzilla #26141 https://sourceware.org/bugzilla/show_bug.cgi?id=26141 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/725126 Title: gas may assemble b to locally-defined, preemptible global symbol as "b.n" Status in binutils: Fix Released Status in Linaro Binutils: Won't Fix Status in Cortex String Routines: Invalid Status in armel-cross-toolchain-base package in Ubuntu: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: There's no guarantee that R_ARM_THM_JUMP11 relocation can be resolved correctly if the symbol gets preempted. Observed in binutils-arm-linux-gnueabi 2.20.51.20100908-0ubuntu2cross1.52. Observed on binutils trunk on 2011-02-25. The problem seems to strike when the compiler optimises a sibling call to "b ", for which the assembler generates a b.n. As a side-effect of the presence of this relocation, Thumb-2 kernel modules may fail to load, since the kernel doesn't support fixing up this relocation. I believe the kernel doesn't do any symbol preemption processing when loading modules -- if so, the relocation is actually redundant. But there's no way for the kernel to detect at module load time that the relocation can safely be ignored. In kernel builds, about 1 out every 6 modules suffers from this problem. It's not clear to me whether the method used by the kernel to link .ko objects is wrong or not. It seems that either the tools should support symbol preemption in this scenario (implying that a short branch is not adequate to guarantee that preemption will work -- i.e., a gas bug) or not (in this case the fixup should be done locally and there should presumably be no relocation -- i.e., a different gas bug). It appears that passing -fno-optimize-sibling-calls to GCC can work around the problem by avoiding the generation of local branches to global symbols, but this is clearly not the correct fix. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/725126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
FYI Canonical's legal departement is reviewing motd-news "feature" (such as telemetry) and will provide updated information next week. All motd-news related tickets https://bugs.launchpad.net/ubuntu/+source/base- files/+bugs?field.searchtext=motd- news&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.status%3Alist=OPINION&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE "Canonical has launched the Ubuntu Appliance initiative which aims to transform Raspberry Pi devices or personal computers into secure, self- updating solutions" (source 9to5linux). I checked nextcloud- core18-pi.img (and core18_1753.snap), motd-news is still present but turned off by default -- Good! ENABLED=0 in the file /etc/default/motd- news. I hope Canonical will apply "Secure by design" motto to the rest of Ubuntu products https://ubuntu.com/appliance -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884361] [NEW] User icon not updated in login screen
Public bug reported: I created 2 users. The first and the second user have their own user pictures. When start the laptop and see the login dialog I see the first user picture, but the second user picture is the standard icon (women head profile), but not the picture I assigned to the second user. So, the seond user picture does not get updated in the login screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Sat Jun 20 13:34:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-05-17 (34 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=ed4f23e0-6712-4e26-a125-0da798c01065 ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884361 Title: User icon not updated in login screen Status in xorg package in Ubuntu: New Bug description: I created 2 users. The first and the second user have their own user pictures. When start the laptop and see the login dialog I see the first user picture, but the second user picture is the standard icon (women head profile), but not the picture I assigned to the second user. So, the seond user picture does not get updated in the login screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Sat Jun 20 13:34:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-05-17 (34 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=ed4f23e0-6712-4e26-a125-0da798c01065 ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.
[Touch-packages] [Bug 1877726] Re: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working
I am experiencing the same problem with a RODECaster Pro and (in my case) Arch Linux. The following log output is generated when I connect the RODECaster via USB: kernel: usb 2-9.4.2: new high-speed USB device number 20 using xhci_hcd kernel: usb 2-9.4.2: New USB device found, idVendor=19f7, idProduct=0011, bcdDevice= 2.10 kernel: usb 2-9.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: usb 2-9.4.2: Product: RODECaster Pro kernel: usb 2-9.4.2: Manufacturer: RODE Microphones kernel: usb 2-9.4.2: SerialNumber: 001A kernel: hid-generic 0003:19F7:0011.0009: hiddev1,hidraw7: USB HID v1.10 Device [RODE Microphones RODECaster Pro] on usb-:00:14.0-9.4.2/input0 kernel: usb 2-9.4.2: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 1) kernel: usb 2-9.4.2: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 1) mtp-probe[4037]: checking bus 2, device 20: "/sys/devices/pci:00/:00:14.0/usb2/2-9/2-9.4/2-9.4.2" mtp-probe[4037]: bus: 2, device: 20 was not an MTP device systemd-udevd[4043]: controlC4: Process '/usr/bin/alsactl restore 4' failed with exit code 99. mtp-probe[4050]: checking bus 2, device 20: "/sys/devices/pci:00/:00:14.0/usb2/2-9/2-9.4/2-9.4.2" mtp-probe[4050]: bus: 2, device: 20 was not an MTP device pulseaudio[1460]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile. pulseaudio[1460]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="4" name="usb-RODE_Microphones_RODECaster_Pro_001A-01" card_name="alsa_card.usb-RODE_Microphones_RODECaster_Pro_001A-01" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. The RODECaster shows up in the list of cards that ALSA knows about, but PulseAudio can't find a working profile and gives up. -- 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/1877726 Title: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Please see https://askubuntu.com/questions/1229085/ubuntu-with-rodecaster-pro-usb-soundcard/1236257#1236257 for most background. tl;dr: - The Rodecaster Pro is a USB audio standard compliant device - lsusb sees it, but alsa cannot use it - trying the exact same setup with a Scarlett 2i2 USB device works (with some caveats, see the mentioned post) Somehow the Rodecaster is ignored by Alsa. I am more than happy to help debug. Alsa info is at http://alsa-project.org/db/?f=94fd609fa23912ab0a39b67676a026fd163f3f3b and also attached. nils@blackbox:~/tmp/soundtest$ aplay -l List of PLAYBACK Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 nils@blackbox:~/tmp/soundtest$ arecord --list-devices List of CAPTURE Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 2: ALC887-VD Alt Analog [ALC887-VD Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nils 90077 F pulseaudio /dev/snd/controlC0: nils 90077 F pulseaudio /dev/snd/controlC1: nils 90077 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:45:20 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-23 (1354 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AudioUsers: pulse Symptom_Card: Family 17h (Models 10h-1fh) HD
[Touch-packages] [Bug 1884366] [NEW] package libkrb5-3 1.16-2build1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3' before installing new version: In
Public bug reported: Unable to update or upgrade libkrb5-3:i386 at 18.04 i386 $ sudo apt install libkrb5-3:i386 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libgssapi-krb5-2 libkrb5support0 Suggested packages: krb5-doc krb5-user The following packages will be upgraded: libgssapi-krb5-2 libkrb5-3 libkrb5support0 3 upgraded, 0 newly installed, 0 to remove and 723 not upgraded. Need to get 467 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://security.ubuntu.com/ubuntu bionic-security/main i386 libkrb5support0 i386 1.16-2ubuntu0.1 [32.5 kB] Get:2 http://security.ubuntu.com/ubuntu bionic-security/main i386 libgssapi-krb5-2 i386 1.16-2ubuntu0.1 [132 kB] Get:3 http://security.ubuntu.com/ubuntu bionic-security/main i386 libkrb5-3 i386 1.16-2ubuntu0.1 [303 kB] Fetched 467 kB in 2s (300 kB/s) (Reading database ... 250947 files and directories currently installed.) Preparing to unpack .../libkrb5support0_1.16-2ubuntu0.1_i386.deb ... Unpacking libkrb5support0:i386 (1.16-2ubuntu0.1) over (1.16-2build1) ... Preparing to unpack .../libgssapi-krb5-2_1.16-2ubuntu0.1_i386.deb ... Unpacking libgssapi-krb5-2:i386 (1.16-2ubuntu0.1) over (1.16-2build1) ... Preparing to unpack .../libkrb5-3_1.16-2ubuntu0.1_i386.deb ... Unpacking libkrb5-3:i386 (1.16-2ubuntu0.1) over (1.16-2build1) ... dpkg: error processing archive /var/cache/apt/archives/libkrb5-3_1.16-2ubuntu0.1_i386.deb (--unpack): unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3' before installing new version: Input/output error Errors were encountered while processing: /var/cache/apt/archives/libkrb5-3_1.16-2ubuntu0.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libkrb5-3 1.16-2build1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: libkrb5support0:i386: Install libgssapi-krb5-2:i386: Install libkrb5-3:i386: Install NULL: ConfigurePending Architecture: i386 CasperVersion: 1.394 Date: Sat Jun 20 13:02:48 2020 ErrorMessage: unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3' before installing new version: Input/output error LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: krb5 Title: package libkrb5-3 1.16-2build1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1884366 Title: package libkrb5-3 1.16-2build1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3' before installing new version: Input/output error Status in krb5 package in Ubuntu: New Bug description: Unable to update or upgrade libkrb5-3:i386 at 18.04 i386 $ sudo apt install libkrb5-3:i386 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libgssapi-krb5-2 libkrb5support0 Suggested packages: krb5-doc krb5-user The following packages will be upgraded: libgssapi-krb5-2 libkrb5-3 libkrb5support0 3 upgraded, 0 newly installed, 0 to remove and 723 not upgraded. Need to get 467 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://security.ubuntu.com/ubuntu bionic-security/main i386 libkrb5support0 i386 1.16-2ubuntu0.1 [32.5 kB] Get:2 http://security.ubuntu.com/ubuntu bionic-security/main i386 libgssapi-krb5-2 i386 1.16-2ubuntu0.1 [132 kB] Get:3 http://security.ubuntu.com/ubuntu bionic-security/main i386 libkrb5-3 i386 1.16-2ubuntu0.1 [303 kB] Fetched 467 kB in 2s (300 kB/s) (Reading database ... 250947 files and directories currently installed.) Preparing to unpack .../libkrb5support0_1.16-2ubuntu0.1_i386.deb ... Unpacking libkrb5support0:i386 (1.16-2ubuntu0.1) over (1.16-2build1) ... Preparing to unpack .../libgssapi-krb5-2_1.16-2ubuntu0.1_i386.deb ... Unpacking libgssapi-krb5-2:i386 (1.16-2ubuntu0.1) over (1.16-2build1) ... Preparing to unpack .../libkrb5-3_1.16-2ubuntu0.1_i386.deb ... Unpacking libkrb5-3:i386 (1.16-2
[Touch-packages] [Bug 1884367] [NEW] The display is flickering
Public bug reported: For flickering display, I tried to update intel display drivers, and this bug report came during the process ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 18:39:54 2020 DistUpgraded: 2020-06-10 01:24:34,201 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2018-01-23 (878 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LAB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=5b2de4e2-596a-412f-b22c-5aa72fb9234a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-06-09 (10 days ago) dmi.bios.date: 08/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.503 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Aug 16 15:18:06 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1249 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884367 Title: The display is flickering Status in xorg package in Ubuntu: New Bug description: For flickering display, I tried to update intel display drivers, and this bug report came during the process ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 18:39:54 2020 DistUpgraded: 2020-06-10 01:24:34,201 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2018-01-23 (878 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 13d3:3423 IMC Networks Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. USB Camera Bus 001 Devi
[Touch-packages] [Bug 1881943] Re: [Inspiron 5391, Realtek ALC3204] Sound stopped to work, "error : DSP panic!" in dmesg
I have the same problem with mainline 5.7 kernel. ** Summary changed: - [Inspiron 5391, Realtek ALC3204] Sound stopped to work, errors in dmesg + [Inspiron 5391, Realtek ALC3204] Sound stopped to work, "error : DSP panic!" in dmesg ** Description changed: Sound worked, but accidentally stopped to work at all. Just before it I had plugged and unplugged HDMI display (but without sound via HDMI). Only restart helped. Here is dmesg output while the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND - /dev/snd/controlC0: tenikeev 4612 F pulseaudio - /dev/snd/pcmC0D0p: tenikeev 4612 F...m pulseaudio - /dev/snd/pcmC0D6c: tenikeev 4612 F...m pulseaudio + /dev/snd/controlC0: username 4612 F pulseaudio + /dev/snd/pcmC0D0p: username 4612 F...m pulseaudio + /dev/snd/pcmC0D6c: username 4612 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 3 20:42:33 2020 InstallationDate: Installed on 2020-05-28 (5 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: - июн 03 20:04:56 tenikeev-5391 dbus-daemon[3386]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=114 pid=4302 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") - июн 03 20:04:59 tenikeev-5391 systemd[4295]: pulseaudio.service: Succeeded. - июн 03 20:05:09 tenikeev-5391 systemd[4295]: pulseaudio.socket: Succeeded. + июн 03 20:04:56 username-5391 dbus-daemon[3386]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=114 pid=4302 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") + июн 03 20:04:59 username-5391 systemd[4295]: pulseaudio.service: Succeeded. + июн 03 20:05:09 username-5391 systemd[4295]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5391, Realtek ALC3204, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 07DM2C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5391 dmi.product.sku: 096E dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1881943 Title: [Inspiron 5391, Realtek ALC3204] Sound stopped to work, "error : DSP panic!" in dmesg Status in alsa-driver package in Ubuntu: New Bug description: Sound worked, but accidentally stopped to work at all. Just before it I had plugged and unplugged HDMI display (but without sound via HDMI). Only restart helped. Here is dmesg output while the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 4612 F pulseaudio /dev/snd/pcmC0D0p: username 4612 F...m pulseaudio /dev/snd/pcmC0D6c: username 4612 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 3 20:42:33 2020 InstallationDate: Installed on 2020-05-28 (5 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: июн 03 20:04:56 username-5391 dbus-daemon[3386]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=114 pid=4302 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") июн 03 20:04:59 username-5391 systemd[4295]: pulseaudio.service: Succeeded. июн 03 20:05:09 username-5391 systemd[4295]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5391, Realtek A
[Touch-packages] [Bug 1880541] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1
This bug was fixed in the package systemd - 245.6-1ubuntu1 --- systemd (245.6-1ubuntu1) groovy; urgency=medium [ Balint Reczey ] * Merge to Ubuntu from Debian unstable - Dropped changes: * Don't try calling NULL callback in bus_wait_for_units_clear. * test: Skip test-boot-timestamps on permission denied. * From journald: stream pid change newline fix - debian/patches/lp1875708/journald-Increase-stdout-buffer-size-sooner-when-almost-f.patch * meson: initialize time-epoch to reproducible builds compatible value * dhclient-exit-hooks.d/timesyncd: Act only when systemd-timesyncd is enabled (LP: #1873031) File: debian/extra/dhclient-exit-hooks.d/timesyncd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7d5a31fb7523d1ecef0d2932df5efa3b99322919 * debian/udev.postinst: Allow kvm to be an already present non-system group (LP: #1880541) File: debian/udev.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8b5c31828d4323ddb719326b1316c179b7cdbdef * Cherry-pick reversion of detecting WSL by the presence of "microsoft" in osrelease File: debian/patches/Revert-detect-virt-also-detect-microsoft-as-WSL.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e13f4452698b84ecb0ca6b7950b5f0c42c02c2cf [ Ryan Harper ] * Skip over by-uuid/by-label symlinks for bcache backing and cache devices (LP: #1861941) File: debian/patches/lp1861941-dont-generate-disk-byuuid-for-bcache-uuid.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4b9a0e888ca40eaed561ec48aece23218fab18ff systemd (245.6-1) unstable; urgency=medium [ Michael Biebl ] * New upstream version 245.6 * Rebase patches [ Balint Reczey ] * debian/tests/boot-and-services: Handle missing fstab (LP: #1877078) -- Balint Reczey Thu, 11 Jun 2020 12:54:02 +0200 ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1880541 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Bug description: During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to configure interrupting the upgrade. dpkg complained that kvm already exist but it is not a system group. From what I saw my user was the only member of kvm group I don't recall installing kvm manually but I do have Android emulator installed so it is possible that it is related. Removing kvm group via groupdel kvm allowed dpkg --configure -a to succeed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 56-hpmud.rules 70-snap.core.rules Date: Mon May 25 11:01:36 2020 ErrorMessage: podproces zainstalowany pakiet udev skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2017-10-18 (949 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=1c3374a5-d07b-4588-8159-7607318eb2c9 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: Upgraded to focal on 2020-05-25 (0 days ago) dmi.bios.date: 07/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.80 dmi.board.name: X370 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.80:bd07/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to:
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
This bug was fixed in the package systemd - 245.6-1ubuntu1 --- systemd (245.6-1ubuntu1) groovy; urgency=medium [ Balint Reczey ] * Merge to Ubuntu from Debian unstable - Dropped changes: * Don't try calling NULL callback in bus_wait_for_units_clear. * test: Skip test-boot-timestamps on permission denied. * From journald: stream pid change newline fix - debian/patches/lp1875708/journald-Increase-stdout-buffer-size-sooner-when-almost-f.patch * meson: initialize time-epoch to reproducible builds compatible value * dhclient-exit-hooks.d/timesyncd: Act only when systemd-timesyncd is enabled (LP: #1873031) File: debian/extra/dhclient-exit-hooks.d/timesyncd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7d5a31fb7523d1ecef0d2932df5efa3b99322919 * debian/udev.postinst: Allow kvm to be an already present non-system group (LP: #1880541) File: debian/udev.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8b5c31828d4323ddb719326b1316c179b7cdbdef * Cherry-pick reversion of detecting WSL by the presence of "microsoft" in osrelease File: debian/patches/Revert-detect-virt-also-detect-microsoft-as-WSL.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e13f4452698b84ecb0ca6b7950b5f0c42c02c2cf [ Ryan Harper ] * Skip over by-uuid/by-label symlinks for bcache backing and cache devices (LP: #1861941) File: debian/patches/lp1861941-dont-generate-disk-byuuid-for-bcache-uuid.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4b9a0e888ca40eaed561ec48aece23218fab18ff systemd (245.6-1) unstable; urgency=medium [ Michael Biebl ] * New upstream version 245.6 * Rebase patches [ Balint Reczey ] * debian/tests/boot-and-services: Handle missing fstab (LP: #1877078) -- Balint Reczey Thu, 11 Jun 2020 12:54:02 +0200 ** Changed in: systemd (Ubuntu Groovy) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Invalid Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchp
[Touch-packages] [Bug 1873031] Re: 245.4-2ubuntu1 throws stderr messages on timesyncd restart in its dhcp hook
This bug was fixed in the package systemd - 245.6-1ubuntu1 --- systemd (245.6-1ubuntu1) groovy; urgency=medium [ Balint Reczey ] * Merge to Ubuntu from Debian unstable - Dropped changes: * Don't try calling NULL callback in bus_wait_for_units_clear. * test: Skip test-boot-timestamps on permission denied. * From journald: stream pid change newline fix - debian/patches/lp1875708/journald-Increase-stdout-buffer-size-sooner-when-almost-f.patch * meson: initialize time-epoch to reproducible builds compatible value * dhclient-exit-hooks.d/timesyncd: Act only when systemd-timesyncd is enabled (LP: #1873031) File: debian/extra/dhclient-exit-hooks.d/timesyncd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7d5a31fb7523d1ecef0d2932df5efa3b99322919 * debian/udev.postinst: Allow kvm to be an already present non-system group (LP: #1880541) File: debian/udev.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8b5c31828d4323ddb719326b1316c179b7cdbdef * Cherry-pick reversion of detecting WSL by the presence of "microsoft" in osrelease File: debian/patches/Revert-detect-virt-also-detect-microsoft-as-WSL.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e13f4452698b84ecb0ca6b7950b5f0c42c02c2cf [ Ryan Harper ] * Skip over by-uuid/by-label symlinks for bcache backing and cache devices (LP: #1861941) File: debian/patches/lp1861941-dont-generate-disk-byuuid-for-bcache-uuid.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4b9a0e888ca40eaed561ec48aece23218fab18ff systemd (245.6-1) unstable; urgency=medium [ Michael Biebl ] * New upstream version 245.6 * Rebase patches [ Balint Reczey ] * debian/tests/boot-and-services: Handle missing fstab (LP: #1877078) -- Balint Reczey Thu, 11 Jun 2020 12:54:02 +0200 ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1873031 Title: 245.4-2ubuntu1 throws stderr messages on timesyncd restart in its dhcp hook Status in chrony package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: systemd has broken this by the split of timesyncd. On a system that installed chrony (or other NTP servers) you'll have: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-=-==--=== ii chrony3.5-6ubuntu3 amd64Versatile implementation of the Network Time Protocol rc systemd-timesyncd 245.4-4ubuntu1 amd64minimalistic service to synchronize local time with NTP servers That left this behind: /etc/dhcp/dhclient-exit-hooks.d/timesyncd And if you now run a dhcp based time server push it will fail very badly. P.S. This is triggered by the chrony autopkgtests but not an issue in chrony yet it is in systemd. But due to that one can use [1] as easy reproducer, I wonder how systemd slipped by this issue in autopkgtest? It contains: systemctl try-restart systemd-timesyncd.service || true Which in the setup the system now has will trigger: sudo dhclient dummy0 Failed to try-restart systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. P.S. I'll harden the chrony test to not stumble over this but it should be revisited for systemd to provide a better fix than causing this message every time (maybe pre-check if it is enabled and unmasked)? [1]: https://git.launchpad.net/ubuntu/+source/chrony/tree/debian/tests /time-sources-from-dhcp-servers?h=ubuntu/focal-devel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1873031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Hello, i'm back to this issue. I reinstalled Ubuntu 20.04 on the same laptop and i'm still having sound related issues, as other seems to also feedback. Main issue is the stability of the computer with default settings. It happens on a random (but high ratio) basis that the computer gets completely frozen at the login page. Only way to pass throught this is to force a poweroff with a long press on power button. When this issue does not accur, the system is pretty stable, but those random freeze still do occur and are seems related to sound system because for example the fact that I receive a call on some instant messaging app do cause the freeze ! Stability gets even worse when the laptop is hooked to the HP G2 thunderbolt dock. Under those condition, the login page freeze is systematic (but it's possible to boot without the dock and to hook the dock after which get the system back to usable mic but unstable system) If I add the options snd-hda-intel dmic_detect=0 (either in the modprobe.d rules or with the kernel command line version) then I have a perfectly stable computer, but without microphone. System is running kernel Linux ZBook15G6 5.4.0-38-lowlatency #42-Ubuntu SMP PREEMPT Mon Jun 8 17:28:37 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux but behaviour has been the same with generic version of the kernel, and also with previous versions. If there are any tests or logs I can provide to try getting this sorted out, please let me know. -- 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/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873562] Re: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installi
To proceed with upgrade, for every error dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_19.2.8-0ubuntu0~18.04.3_i386.deb (--unpack): unable to make backup link of './usr/lib/i386-linux-gnu/dri/vmwgfx_dri.so' before installing new version: Input/output error Reinstalling /etc/drirc that was moved away Errors were encountered while processing: /var/cache/apt/archives/libgl1-mesa-dri_19.2.8-0ubuntu0~18.04.3_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) remove the referenced file, i.e., $ sudo rm -rf /usr/lib/i386-linux-gnu/dri/vmwgfx_dri.so -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1873562 Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux- gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error Status in mesa package in Ubuntu: New Bug description: After running $ sudo apt full-upgrade Could be contributing factor to Chromium crashing tabs randomly. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 NonfreeKernelModules: overlay ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CompositorRunning: None Date: Sat Apr 18 03:59:22 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Inc. Latitude E7440 ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/dri/kms_swrast_dri.so' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 03HFCG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1873562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884366] Re: package libkrb5-3 1.16-2build1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3' before installing new version: Inpu
For every error when executing sudo apt upgrade unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3' before installing new version: Input/output error remove the referenced file sudo rm -rf /usr/lib/i386-linux-gnu/libkrb5.so.3.3 then proceed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1884366 Title: package libkrb5-3 1.16-2build1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3' before installing new version: Input/output error Status in krb5 package in Ubuntu: New Bug description: Unable to update or upgrade libkrb5-3:i386 at 18.04 i386 $ sudo apt install libkrb5-3:i386 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libgssapi-krb5-2 libkrb5support0 Suggested packages: krb5-doc krb5-user The following packages will be upgraded: libgssapi-krb5-2 libkrb5-3 libkrb5support0 3 upgraded, 0 newly installed, 0 to remove and 723 not upgraded. Need to get 467 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://security.ubuntu.com/ubuntu bionic-security/main i386 libkrb5support0 i386 1.16-2ubuntu0.1 [32.5 kB] Get:2 http://security.ubuntu.com/ubuntu bionic-security/main i386 libgssapi-krb5-2 i386 1.16-2ubuntu0.1 [132 kB] Get:3 http://security.ubuntu.com/ubuntu bionic-security/main i386 libkrb5-3 i386 1.16-2ubuntu0.1 [303 kB] Fetched 467 kB in 2s (300 kB/s) (Reading database ... 250947 files and directories currently installed.) Preparing to unpack .../libkrb5support0_1.16-2ubuntu0.1_i386.deb ... Unpacking libkrb5support0:i386 (1.16-2ubuntu0.1) over (1.16-2build1) ... Preparing to unpack .../libgssapi-krb5-2_1.16-2ubuntu0.1_i386.deb ... Unpacking libgssapi-krb5-2:i386 (1.16-2ubuntu0.1) over (1.16-2build1) ... Preparing to unpack .../libkrb5-3_1.16-2ubuntu0.1_i386.deb ... Unpacking libkrb5-3:i386 (1.16-2ubuntu0.1) over (1.16-2build1) ... dpkg: error processing archive /var/cache/apt/archives/libkrb5-3_1.16-2ubuntu0.1_i386.deb (--unpack): unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3' before installing new version: Input/output error Errors were encountered while processing: /var/cache/apt/archives/libkrb5-3_1.16-2ubuntu0.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libkrb5-3 1.16-2build1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: libkrb5support0:i386: Install libgssapi-krb5-2:i386: Install libkrb5-3:i386: Install NULL: ConfigurePending Architecture: i386 CasperVersion: 1.394 Date: Sat Jun 20 13:02:48 2020 ErrorMessage: unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3' before installing new version: Input/output error LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: krb5 Title: package libkrb5-3 1.16-2build1 failed to install/upgrade: unable to make backup link of './usr/lib/i386-linux-gnu/libkrb5.so.3.3' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1884366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884384] [NEW] in high contrast mode the calendar display uncomfortable
Public bug reported: in high contrast mode the calendar display uncomfortable i.e. the weekends and the column with the number of week are very hard to comprehend :( ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 21:33:05 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:241a Syntek EasyCamera Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 002: ID 093a:2533 Pixart Imaging, Inc. Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FL ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=5c5e4d9a-db2e-49a9-8392-07091e531b13 ro quiet splash resume=UUID=f15ed6b9-9e79-4114-af6b-1797d024ff44 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-17ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN29WW:bd10/24/2018:svnLENOVO:pn81FL:pvrLenovoideapad330-17ICH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-17ICH: dmi.product.family: ideapad 330-17ICH dmi.product.name: 81FL dmi.product.sku: LENOVO_MT_81FL_BU_idea_FM_ideapad 330-17ICH dmi.product.version: Lenovo ideapad 330-17ICH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1884384 Title: in high contrast mode the calendar display uncomfortable Status in xorg package in Ubuntu: New Bug description: in high contrast mode the calendar display uncomfortable i.e. the weekends and the column with the number of week are very hard to comprehend :( ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 21:33:05 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:38eb] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:241a Syntek EasyCamera Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 002: ID 093a:2533 Pixart Imaging, Inc. Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FL ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=5c5e4d9a-db2e-49a9-8392-07091e531b13 ro quiet splash resume=UUID=f15ed6b9-9e79-4114-af6b-1797d024ff44 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-17ICH dmi.
[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours
Looking at the history around isc-dhcp, it appears if i read it properly that isc-dhcp sever for Ubuntu has been abandoned. If this is the case should it even be in the focal build -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872118 Title: DHCP Cluster crashes after a few hours Status in isc-dhcp package in Ubuntu: Confirmed Bug description: I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked perfectly until recently, when they started stopping with code=killed, status=6/ABRT. This is being fixed by https://bugs.launchpad.net/bugs/1870729 However now one stops after a few hours with the following errors. One can stay on line but not both. Syslog shows Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ?? nothing in kern.log apport.log shows ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid with dump mode of 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf") ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report /var/crash/_usr_sbin_dhcpd.0.crash /var/crash/_usr_sbin_dhcpd.0.crash shows ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Fri Apr 10 17:20:15 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/sbin/dhcpd ExecutableTimestamp: 1586210315 ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' ProcStatus: Name: dhcpd Umask: 0022 State: D (disk sleep) Tgid: 6828 Ngid: 0 Pid: 6828 PPid: 1 TracerPid: 0 Uid: 113 113 113 113 Gid: 118 118 118 118 FDSize:128 Groups: NStgid:6828 NSpid: 6828 NSpgid:6828 NSsid: 6828 VmPeak: 236244 kB VmSize: 170764 kB VmLck:0 kB VmPin:0 kB VmHWM:12064 kB VmRSS:12064 kB RssAnon: 5940 kB RssFile: 6124 kB RssShmem: 0 kB VmData: 30792 kB VmStk: 132 kB VmExe: 592 kB VmLib: 5424 kB VmPTE: 76 kB VmSwap: 0 kB HugetlbPages: 0 kB CoreDumping: 1 THP_enabled: 1 Threads: 4 SigQ: 0/7609 SigPnd: ShdPnd: SigBlk: SigIgn:1000 SigCgt:00018000 CapInh: CapPrm: CapEff: CapBnd:003f CapAmb: NoNewPrivs:0 Seccomp: 0 Speculation_Store_Bypass: thread vulnerable Cpus_allowed: 3 Cpus_allowed_list: 0-1 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,0001 Mems_allowed_list: 0 voluntary_ctxt_switches: 111 nonvoluntary_ctxt_switches:144 Signal: 6 Uname: Linux 5.4.0-21-generic x86_64 UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884392] [NEW] Clock does not remain in center when auto-hide the dock setting is disabled from gnome settings
Public bug reported: BUG condition: Gnome Settings>Appearance> disable "auto hide the dock" You will see clock gets displaced to a bit right from the center from the screen & this looks bad. WORKAROUND: Enable "auto hide the dock" from gnome settings ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 01:56:40 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2019-12-13 (190 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210) MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-10 (41 days ago) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.4.0 dmi.board.name: 0880CR dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: NN_PC_NB0 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0880CR:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "displaced" https://bugs.launchpad.net/bugs/1884392/+attachment/5385675/+files/Screenshot%20from%202020-06-21%2002-02-24.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/1884392 Title: Clock does not remain in center when auto-hide the dock setting is disabled from gnome settings Status in xorg package in Ubuntu: New Bug description: BUG condition: Gnome Settings>Appearance> disable "auto hide the dock" You will see clock gets displaced to a bit right from the center from the screen & this looks bad. WORKAROUND: Enable "auto hide the dock" from gnome settings ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 01:56:40 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2019-12-13 (190 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210) MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-10 (41 days ago) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.v
[Touch-packages] [Bug 1884391] [NEW] PCI/internal sound card not detected
Public bug reported: My sound card stopped being recognized suddenly today. lspci shows the card, but alsa and pulseaudio don't see it. I verified that the kernel modules are installed. I noticed this today when I logged on and the only audio device was the dummy device. I tried the various fixes I found online for this, but nothing worked. I haven't made any changes to any audio packages manually, but I have had automatic updates over the last few days which may have caused this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 15:29:04 2020 InstallationDate: Installed on 2020-03-14 (98 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/26/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1884391 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: My sound card stopped being recognized suddenly today. lspci shows the card, but alsa and pulseaudio don't see it. I verified that the kernel modules are installed. I noticed this today when I logged on and the only audio device was the dummy device. I tried the various fixes I found online for this, but nothing worked. I haven't made any changes to any audio packages manually, but I have had automatic updates over the last few days which may have caused this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 15:29:04 2020 InstallationDate: Installed on 2020-03-14 (98 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/26/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1884391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884392] Re: Clock does not remain in center when auto-hide the dock setting is disabled from gnome settings
** Description changed: BUG condition: Gnome Settings>Appearance> disable "auto hide the dock" You will see clock gets displaced to a bit right from the center from the screen & this looks bad. WORKAROUND: Enable "auto hide the dock" from gnome settings + + //this is probably a logical error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 01:56:40 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:0794] + Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2019-12-13 (190 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210) MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: - LANGUAGE=en_IN:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_IN - SHELL=/bin/bash + LANGUAGE=en_IN:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IN + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-10 (41 days ago) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.4.0 dmi.board.name: 0880CR dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: NN_PC_NB0 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0880CR:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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 -- 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/1884392 Title: Clock does not remain in center when auto-hide the dock setting is disabled from gnome settings Status in xorg package in Ubuntu: New Bug description: BUG condition: Gnome Settings>Appearance> disable "auto hide the dock" You will see clock gets displaced to a bit right from the center from the screen & this looks bad. WORKAROUND: Enable "auto hide the dock" from gnome settings //this is probably a logical error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 01:56:40 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2019-12-13 (190 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210) MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7 SourcePack
[Touch-packages] [Bug 1884391] Re: PCI/internal sound card not detected
Here's what I've tried (that I can remember): - Reinstalling all the ALSA packages - Rebooting, turning off the sound devices in the BIOS, letting it boot, then reboot, turn the sound devices back on, and let it boot - rm -rf ~/.config/pulseaudio && pulseaudio -k - sudo alsa force-reload - Remove and reinstall pulseaudio packages - sudo apt purge alsa-base pulseaudio && sudo apt install ubuntu-gnome-desktop && sudo alsa force-reload -- 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/1884391 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: My sound card stopped being recognized suddenly today. lspci shows the card, but alsa and pulseaudio don't see it. I verified that the kernel modules are installed. I noticed this today when I logged on and the only audio device was the dummy device. I tried the various fixes I found online for this, but nothing worked. I haven't made any changes to any audio packages manually, but I have had automatic updates over the last few days which may have caused this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 15:29:04 2020 InstallationDate: Installed on 2020-03-14 (98 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/26/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1884391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable
Over time and several reboots later, the issue has reappeared, so the workaround above is definitely not a permanent solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1787867 Title: Ubuntu 18.04 LTS bluetooth left discoverable Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays discoverable which opens up unnecessary vulnerability surface. There should be a separate UI switch for discoverability with auto timeout. Leaving bluetooth on (using a Bluetooth mouse) should not leave the computer always discoverable. Current behavior does not match documentation https://help.ubuntu.com/stable/ubuntu-help/bluetooth- visibility.html.en, even without Bluetooth panel open, the computer is still discoverable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884393] [NEW] With Auto-hide dock enabled, icons get hidden behind dock & dock does not hide untill there's an app near it
Public bug reported: Gnome Settings>Appearance> auto hide dock //enable it automatically you might see icons getting hidden behind dock (keep windows away from dock). Not only desktop getting hidden under dock looks unaesthetic, But don't you think dock should remain hidden till the user points mouse at it? Other wise we won't be able to use left side of the desktop to keep icons. Dock never hides till an app is near it, so desktop icons may get under it. So that we can use the entire left side of desktop to keep icons, with the auto hide dock option enabled, don't you think dock should remain hidden until user points mouse near it? //probably a logical error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 02:14:32 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2019-12-13 (190 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210) MachineType: Dell Inc. Vostro 15-3568 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-10 (41 days ago) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.4.0 dmi.board.name: 0880CR dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: NN_PC_NB0 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0880CR:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 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.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "icon getting hidden under dock & dock not hiding as no window near it" https://bugs.launchpad.net/bugs/1884393/+attachment/5385694/+files/Screenshot%20from%202020-06-21%2002-26-26.png ** Description changed: Gnome Settings>Appearance> auto hide dock //enable it automatically you might see icons getting hidden behind dock (keep windows away from dock). Not only desktop getting hidden under dock looks unaesthetic, But don't you think dock should remain hidden till the user points mouse at it? Other wise we won't be able to use left side of the desktop to keep icons. Dock never hides till an app is near it, so desktop icons may get under it. So that we can use the entire left side of desktop to keep icons, with the auto hide dock option enabled, don't you think dock should remain hidden until user points mouse near it? + //probably a logical error + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 02:14:32 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028
[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 I had the same issue with my BOSE QC35 II on Ubuntu 20.04 recently updated from 19 . My config: Asus VivoBook S15 . To correct this issue i only had to enable this line in /etc/pulse/daemon.conf flat-volumes = no then restart pulseaudio as user : systemctl --user restart pulseaudio -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884396] [NEW] Ubuntu freezing intermittently
Public bug reported: I had similar issues when 20.04 was released, then it disappeared with an upgrade - but sadly it's back. I have short intermittent freezings of the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg when writing this description, the OS freezes every second word. When the freeze goes away the OS is snappy. I have tried switching between Wayland and Xorg - but the problem persists. If I write something when it freezes up the last character will be replicated many times - like what happened jut now. This problem did not show up in ubuntu 18.04 through 19.10. Hope U can fix this soon - using my laptop in unbearable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 23:54:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04] InstallationDate: Installed on 2020-05-12 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HD Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI MACH-WX9 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a2cbbb7f-c619-418a-a98f-9a9cc31b42fa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.28 dmi.board.name: MACH-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M13 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M13 dmi.modalias: dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13: dmi.product.family: MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C189 dmi.product.version: M13 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 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 wayland-session -- 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/1884396 Title: Ubuntu freezing intermittently Status in xorg package in Ubuntu: New Bug description: I had similar issues when 20.04 was released, then it disappeared with an upgrade - but sadly it's back. I have short intermittent freezings of the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg when writing this description, the OS freezes every second word. When the freeze goes away the OS is snappy. I have tried switching between Wayland and Xorg - but the problem persists. If I write something when it freezes up the last character will be replicated many times - like what happened jut now. This problem did not show up in ubuntu 18.04 through 19.10. Hope U can fix this soon - using my laptop in unbearable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 23:54:52 2020 DistUpgrad
[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Finally , i h -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Finally, i have the same problem on Vivobook S15 and Headset QC35 II that worked perfectly before upgrade to 20.04. It's very annoying issue in this period of containment and remote calls. Don't push me to switch on Windows -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
The underlying issue is that i_cal_timezone_get_builtin_timezone_from_tzid and i_cal_timezone_get_builtin_timezone included from /usr/include/libical- glib/i-cal-timezone.h (libical-dev) fail to determine the timezone for "Etc/Utc" or "Etc/UTC". ** Also affects: libical3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1848969 Title: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Status in indicator-datetime package in Ubuntu: Confirmed Status in libical3 package in Ubuntu: New Bug description: After upgrading to Ubuntu 19.10, indicator-datetime 15.10+19.10.20190819.1-0ubuntu1 crashes right from the start: $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized TZID: 'Etc/Utc' (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed [...] (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed ** Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Bail out! Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
Correction: Applying following patch does not solve this assertion
failure:
diff --git a/src/engine-eds.cpp b/src/engine-eds.cpp
index 153a9ea..8e2674f 100644
--- a/src/engine-eds.cpp
+++ b/src/engine-eds.cpp
@@ -879,6 +879,11 @@ private:
if (tzid == nullptr)
return nullptr;
+// Workaround: Etc/Utc is not known to
i_cal_timezone_get_builtin_timezone_from_tzid/i_cal_timezone_get_builtin_timezone
+if (strcmp("Etc/Utc", tzid) == 0) {
+return g_time_zone_new("Z");
+}
+
auto itz = i_cal_timezone_get_builtin_timezone_from_tzid(tzid); //
usually works
if (itz == nullptr) // fallback
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1848969
Title:
src/date-time.cpp:171:GDateTime*
unity::indicator::datetime::DateTime::get() const: assertion failed:
(m_dt)
Status in indicator-datetime package in Ubuntu:
Confirmed
Status in libical3 package in Ubuntu:
New
Bug description:
After upgrading to Ubuntu 19.10, indicator-datetime
15.10+19.10.20190819.1-0ubuntu1 crashes right from the start:
$ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
(process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized
TZID: 'Etc/Utc'
(process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized
TZID: 'Etc/Utc'
(process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized
TZID: 'Etc/Utc'
(process:17641): libecal-CRITICAL **: 01:46:35.457:
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libecal-CRITICAL **: 01:46:35.457:
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet:
assertion 'I_CAL_IS_TIME (tt)' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet:
assertion 'I_CAL_IS_TIME (tt)' failed
[...]
(process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet:
assertion 'I_CAL_IS_TIME (tt)' failed
(process:17641): libecal-CRITICAL **: 01:46:35.458:
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libecal-CRITICAL **: 01:46:35.458:
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet:
assertion 'I_CAL_IS_TIME (tt)' failed
(process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet:
assertion 'I_CAL_IS_TIME (tt)' failed
**
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
Bail out!
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884101] Re: jackdbus produces high cpu load
Did that already, got rid of the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1884101 Title: jackdbus produces high cpu load Status in jackd2 package in Ubuntu: Incomplete Bug description: if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd tends to take all availabl CPU power bringing the system to slow down remarkably. Killing jackd and jackdbus frees cpu and system load drops from 100%/per CPU down to ~4% overall. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sct-muc1800 F pulseaudio /dev/snd/pcmC0D0c: sct-muc1800 F...m pulseaudio /dev/snd/pcmC0D0p: sct-muc1800 F...m pulseaudio /dev/snd/timer: sct-muc1800 f pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 18 18:08:25 2020 InstallationDate: Installed on 2019-09-09 (282 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1884101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client
Hi all, I'm using ubuntu 20.04 on a raspberry pi (64bit version). And
the problem is still present. My netplan:
root@rbpi3-002:/etc/netplan# cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0
search sismonda.local cpe.telecentro.net.ar
root@rbpi3-002:/etc/netplan# cat 50-cloud-init.yaml
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
dhcp4: true
dhcp6: false
dhcp4-overrides:
use-dns: false
nameservers:
search: [sismonda.local]
addresses: [10.0.0.31,10.0.0.10,10.0.0.62]
The output of "systemd-resolve --status"
root@rbpi3-002:/etc/netplan# systemd-resolve --status
Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test
Link 3 (wlan0)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 2 (eth0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 10.0.0.31
10.0.0.10
10.0.0.62
10.0.0.3
DNS Domain: sismonda.local
cpe.telecentro.net.ar
root@rbpi3-002:/etc/netplan#
I found an extra dns and the domain search of my ISP!
--
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/1759014
Title:
Netplan has no way to control DHCP client
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in netplan.io source package in Bionic:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in netplan.io source package in Cosmic:
Fix Released
Status in systemd source package in Cosmic:
Fix Released
Status in netplan.io source package in Disco:
Fix Released
Status in systemd source package in Disco:
Fix Released
Bug description:
[Impact]
DHCP configurations where custom settings (routes, nameservers, etc.) need to
be applied.
[Test case]
1) Configure netplan for the particulars of the network by configuring an
appropriate dhcp{4,6}-override stanza:
network:
version: 2
ethernets:
engreen:
dhcp4: true
dhcp4-overrides:
use-dns: false
use-routes: false
route-metric:
Additionally, if so required, add a custom DNS / routes to the
configuration. e.g.
nameservers:
search: [lab, kitchen]
addresses: [8.8.8.8]
(See https://netplan.io/reference#dhcp-overrides for the available
options)
2) Run 'netplan apply' or reboot to have the configuration applied.
3) Vali
[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
Maybe different machines have different root cause for this issue, for
my case:
I have 3 laptops: 1 dell laptop with intel BT 8087:0aaa, 1 dell laptop
with Atheros BT 0cf3:e007 and 1 lenovo laptop with intel BT 8087:0029. I
have 4 BT headsets: 1 QC35 II, 1 harman kardon soho wireless, 1 sony wl-
1000x and 1 plantronics Go2.
After freshly installing the ubuntu 20.04, those 4 headsets work well on
both Dell laptops, in the hsp/hfp mode, both playback and recording work
well.
But on the Lenovo machine, I reproduced the issue, all headsets could
work in A2DP mode, couldn't output and record in hsp/hfp mode.
I ran $sudo btmon, found after switch to Synchronous connection
successfully (HCI Event: Synchronous Connect Complete), the dell
machines could receive the sco packets from headsets, while the lenovo
machine couldn't. The difference between Lenovo and Dell machines is
they have different BT host controllers. Then I debugged the bt kernel
driver, found on that lenovo machine, the btusb driver could not receive
the usb_isoc packets from headsets (length always equals 0).
So on my LENOVO laptop, it is highly possible this is a kernel driver or
BT firmware/WiFi firmware's bug.
So if possible, you could plug in an external USB BT dongle to redo the
test, let headsets connect to that dongle instead of BT hci on your
laptop. Or you could run sudo btmon to check the log, if it is a
synchronous connection failure or TX/RX on SCO packets failure.
This is a example log captured on my Dell machine (without hsp/hfp
issue), starting capture when manually switch to hsp/hfp mode:
Bluetooth monitor ver 5.48
= Note: Linux version 5.3.0-56-generic (x86_64)
0.694655
= Note: Bluetooth subsystem version 2.22
0.694662
= New Index: 18:1D:EA:86:BE:E6 (Primary,USB,hci0)
[hci0] 0.694666
= Open Index: 18:1D:EA:86:BE:E6
[hci0] 0.694667
= Index Info: 18:1D:EA:86:BE:E6 (Intel Corp.)
[hci0] 0.694668
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0002} 0.694673
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.694674
@ MGMT Open: btmon (privileged) version 1.14
{0x0003} 0.694731
< HCI Command: Exit Sniff Mode (0x02|0x0004) plen 2
#1 [hci0] 6.574419
Handle: 256
> HCI Event: Command Status (0x0f) plen 4
>
>#2 [hci0] 6.688939
Exit Sniff Mode (0x02|0x0004) ncmd 1
Status: Success (0x00)
> HCI Event: Mode Change (0x14) plen 6
>
>#3 [hci0] 6.829008
Status: Success (0x00)
Handle: 256
Mode: Active (0x00)
Interval: 0.000 msec (0x)
< HCI Command: Setup Synchronous Connection (0x01|0x0028) plen 17
#4 [hci0] 6.829108
Handle: 256
Transmit bandwidth: 8000
Receive bandwidth: 8000
Max latency: 10
Setting: 0x0060
Input Coding: Linear
Input Data Format: 2's complement
Input Sample Size: 16-bit
# of bits padding at MSB: 0
Air Coding Format: CVSD
Retransmission effort: Optimize for power consumption (0x01)
Packet type: 0x0380
3-EV3 may not be used
2-EV5 may not be used
3-EV5 may not be used
> HCI Event: Command Status (0x0f) plen 4
>
[Touch-packages] [Bug 1874107] Re: qt theming issue: error 6 in libgdk-x11-2.0.so
[Expired for gtk+2.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtk+2.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874107 Title: qt theming issue: error 6 in libgdk-x11-2.0.so Status in gtk+2.0 package in Ubuntu: Expired Bug description: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1874003] Re: cant log into network
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1874003 Title: cant log into network Status in network-manager package in Ubuntu: Expired Bug description: Running Ubuntu Mate 20.04 2020-04-20 ISO live session, sometimes i'm not able to log into detected wireless networks. See screenshot for error message. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: MATE Date: Tue Apr 21 05:29:48 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200420) ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 c072d14c-3f17-3a1d-9679-9929ecc4d6cb ethernet 0 never yes -999 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- ---- enp4s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 disconnected started none enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872917] Re: Laptop does not recognize it's charging
[Expired for upower (Ubuntu) because there has been no activity for 60 days.] ** Changed in: upower (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1872917 Title: Laptop does not recognize it's charging Status in upower package in Ubuntu: Expired Bug description: I'm using a pretty new Lenovo Thinkpad X1 Extreme G2. Since a few days, the laptop does not recognize that its charging all the time. It's showing the battery icon and a percent number. This must be broken a couple of days or weeks ago, this was working when I installed Ubuntu 19.10. It does not depend from dock or directly connecting the AC adapter. Incredibly long battery life time is shown, see screenshot. (laptop was connected to AC during this) This is a problem because for example firmware upgrades does not work because they require "AC-connected state". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1872917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 597056] Re: HP Touchsmart 600-1005xt No sound from Internal Speakers
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/597056 Title: HP Touchsmart 600-1005xt No sound from Internal Speakers Status in alsa-driver package in Ubuntu: Expired Bug description: Found there is no internal speaker output from hp touchsmart 600-1005xt in all releases of Ubuntu 8.04 to 10.04LTS (64bit) with updated alsa-base (on 1.0.22.1 in Lucid now). All outputs & inputs work except the Internal speakers. I Checked all alsamixer levels, I have also noticed the nodeid's it seem to be mapped 0x15 - 0x0d - 0x03 (21 - 13 - 3) for internal speakers which gives same results (no audio) in osx Applehda.kext. The Headphone nodeid's of 0x14 - 0x0c - 0x02 (20 - 12 - 2) seem to work in all Ubuntu Dists & OSx as well. Windows 7 Driver everything works of course. Is Bios sending wrong pin configs for internal audio? if so what would the resolution be? here is my alsa-information from alsa-info.sh attached, My only guess is the pin configs how do you change them in alsa driver & how could I get the correct ones if the bios was sending wrong pathmaps? I should also note I've tried most of the model flags in alsa-base.conf in the alc888 documentation & rebooted countless times, model=auto shows the internal speaker but sound comes out headphones plug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/597056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884410] [NEW] I was watching a live video on YouTube..Soon after the programme is over, I'm seeing volume icon popping up on the screen
Public bug reported: I'm using Ubuntu 19.10 installed yesterday... ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1884410 Title: I was watching a live video on YouTube..Soon after the programme is over, I'm seeing volume icon popping up on the screen Status in pulseaudio package in Ubuntu: New Bug description: I'm using Ubuntu 19.10 installed yesterday... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1884410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884414] [NEW] package libframe6:amd64 2.5.0daily13.06.05+16.10.20160809-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it
Public bug reported: getting update failed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libframe6:amd64 2.5.0daily13.06.05+16.10.20160809-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 21 11:33:09 2020 DuplicateSignature: package:libframe6:amd64:2.5.0daily13.06.05+16.10.20160809-0ubuntu2 Setting up dbus-x11 (1.12.16-2ubuntu2.1) ... dpkg: error processing package libframe6:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-22 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: frame Title: package libframe6:amd64 2.5.0daily13.06.05+16.10.20160809-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: frame (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 frame in Ubuntu. https://bugs.launchpad.net/bugs/1884414 Title: package libframe6:amd64 2.5.0daily13.06.05+16.10.20160809-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in frame package in Ubuntu: New Bug description: getting update failed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libframe6:amd64 2.5.0daily13.06.05+16.10.20160809-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 21 11:33:09 2020 DuplicateSignature: package:libframe6:amd64:2.5.0daily13.06.05+16.10.20160809-0ubuntu2 Setting up dbus-x11 (1.12.16-2ubuntu2.1) ... dpkg: error processing package libframe6:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-22 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: frame Title: package libframe6:amd64 2.5.0daily13.06.05+16.10.20160809-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/frame/+bug/1884414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884414] Re: package libframe6:amd64 2.5.0daily13.06.05+16.10.20160809-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it b
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to frame in Ubuntu. https://bugs.launchpad.net/bugs/1884414 Title: package libframe6:amd64 2.5.0daily13.06.05+16.10.20160809-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in frame package in Ubuntu: New Bug description: getting update failed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libframe6:amd64 2.5.0daily13.06.05+16.10.20160809-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jun 21 11:33:09 2020 DuplicateSignature: package:libframe6:amd64:2.5.0daily13.06.05+16.10.20160809-0ubuntu2 Setting up dbus-x11 (1.12.16-2ubuntu2.1) ... dpkg: error processing package libframe6:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-22 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: frame Title: package libframe6:amd64 2.5.0daily13.06.05+16.10.20160809-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/frame/+bug/1884414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
