[Touch-packages] [Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started Status in bluez package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started Status in bluez package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864280] Re: software-properties-gtk removes [arch=amd64]
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1864280 Title: software-properties-gtk removes [arch=amd64] Status in software-properties package in Ubuntu: Expired Bug description: When editing apt sources via software-properties-gtk, additional options like [arch=amd64] are removed. With more and more repositories deprecating i386, this problem becomes more and more important. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1864280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875323] Re: package libkrb5-26-heimdal:i386 7.5.0+dfsg-3build1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo
[Expired for heimdal (Ubuntu) because there has been no activity for 60 days.] ** Changed in: heimdal (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1875323 Title: package libkrb5-26-heimdal:i386 7.5.0+dfsg-3build1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. Status in heimdal package in Ubuntu: Expired Bug description: i found this problem when i try to install wine ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libkrb5-26-heimdal:i386 7.5.0+dfsg-3build1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Mon Apr 27 11:29:14 2020 ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. InstallationDate: Installed on 2020-04-22 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: i386 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: heimdal Title: package libkrb5-26-heimdal:i386 7.5.0+dfsg-3build1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1875323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875190] Re: Apt update takes around a full minute to read state information when I run it for the first time since boot even though there are no updates available.
[Expired for apt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1875190 Title: Apt update takes around a full minute to read state information when I run it for the first time since boot even though there are no updates available. Status in apt package in Ubuntu: Expired Bug description: When I ran "sudo apt update && sudo apt dist-upgrade", apt hit all the repositories. However, when it was reading state information, that process took a full minute even though there were no new updates. This is too slow, even though the subsequent time I ran the command, it was much faster. No, this was not the first time I ever ran the command on the current install, as I ran it the day before without reinstalling Ubuntu, on Ubuntu 20.04, and the process took less than 15 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 11:42:21 2020 InstallationDate: Installed on 2020-04-25 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: apt 2.0.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1875190/+subscriptions -- Mailing list: https://launchpad.net/~touch-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 @alcachi, On that problematic Lenovo machine, the kernel module used is btintel with device firmware: intel/ibt-20-1-3.sfi too. Let's wait for firmware or driver update from upstream. -- 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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Changed in: network-manager (Ubuntu) Importance: Undecided => Medium ** Tags added: focal groovy ** Tags added: rls-ff-incoming rls-gg-incoming -- 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/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Triaged Bug description: I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885334] [NEW] Crashes when running World of Warcrat with wine/vulkan
Public bug reported: Hi, while version 440.82-0ubuntu0~0.18.04.2 ran with out any problems 440.100-0ubuntu0.18.04.1 crashes after a while with the following errors: Jun 26 22:41:31 imobil2 kernel: [ 1548.518774] NVRM: GPU at PCI::01:00: GPU-059d1eda-0ee6-ba17-38a2-5e6330b325f1 Jun 26 22:41:31 imobil2 kernel: [ 1548.518779] NVRM: Xid (PCI::01:00): 31, pid=1108, Ch 0012, intr 1000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_PROP_0 faulted @ 0x1_12844000. Fault is of type FAULT_INFO_TYPE_UNSUPPORTED_KIND ACCESS_TYPE_WRITE Jun 26 22:47:32 imobil2 kernel: [ 1909.747689] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 1 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747698] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 2 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747704] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 3 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747708] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 5 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747713] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 9 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747718] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 10 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747723] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 18 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747728] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: Shader Program Header 19 Error Jun 26 22:47:32 imobil2 kernel: [ 1909.747735] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: ESR 0x405840=0x8e0c062e Jun 26 22:47:32 imobil2 kernel: [ 1909.748005] NVRM: Xid (PCI::01:00): 13, pid=1265, Graphics Exception: ChID 0008, Class a097, Offset 1614, Data Jun 26 22:47:33 imobil2 kernel: [ 1910.876226] NVRM: Xid (PCI::01:00): 62, pid=1265, 0110(25dc) 840008ce c415c455 This happend multiple times. Unfortunately the old driver version is not available anymore and I can't check if this is really caused by the driver update. Best regards, Matthias ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3 Date: Fri Jun 26 22:59:14 2020 DistUpgraded: 2020-04-09 19:50:27,912 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 4.15.0-106-generic, x86_64: installed nvidia, 440.100, 4.15.0-108-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK104 [GeForce GTX 770] [1462:2825] InstallationDate: Installed on 2013-12-15 (2384 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: MSI MS-7821 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic root=UUID=10f3ba43-ad16-4df4-b3b4-e86b64e9f96e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-04-09 (78 days ago) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-G45 GAMING (MS-7821) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd07/21/2014:svnMSI:pnMS-7821:pvr1.0:rvnMSI:rnZ87-G45GAMING(MS-7821):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7821 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core:
[Touch-packages] [Bug 1875708] Re: Truncated messages in journald since systemd v244
I'll upload early next week, sorry for the delay. -- 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/1875708 Title: Truncated messages in journald since systemd v244 Status in libvirt package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in libvirt source package in Focal: Confirmed Status in systemd source package in Focal: In Progress Status in libvirt source package in Groovy: Invalid Status in systemd source package in Groovy: Fix Released Bug description: [Impact] * since 09d0b46a "journal: refresh cached credentials of stdout streams" in ~244 output may be trincated. * Upstream has a fix in https://github.com/systemd/systemd/pull/15685 * Backporting the fix will avoid truncation of log output to journald [Test Case] * This could happen in any case, but is more likely when a program that has output going to journald is spawning short-lived sub-programs often. Therefore the test emphasizes on that: - Use a test service like /etc/systemd/system/test.service: [Unit] Description=Test Truncate After=network.target [Service] ExecStart=/usr/lib/test.sh long-test-for-start ExecStop=/usr/lib/test.sh long-test-for-stop Type=oneshot RemainAfterExit=yes StandardOutput=journal+console TimeoutStopSec=0 [Install] WantedBy=multi-user.target - And a test script like /usr/lib/test.sh: #!/bin/sh gettext "This will" echo gettext "usually fail" echo gettext "and be truncated" echo Start/Stopping that service without the fix will look like: Apr 30 18:56:40 f systemd[1]: Stopping Test Truncate... Apr 30 18:56:40 f test.sh[1165]: T Apr 30 18:56:40 f test.sh[1167]: T Apr 30 18:56:40 f test.sh[1167]: sually fai Apr 30 18:56:40 f test.sh[1165]: s Apr 30 18:56:40 f test.sh[1168]: s Apr 30 18:56:40 f test.sh[1168]: nd be truncate Apr 30 18:56:40 f test.sh[1165]: n Apr 30 18:56:40 f systemd[1]: test.service: Succeeded. Apr 30 18:56:40 f systemd[1]: Stopped Test Truncate. [Regression Potential] * The patches are rather small, but there might be a slightly increased memory consumption of journald for output buffers. * Issues (if any and I couldn't find any so far) should be only to journald output handling. Systemd is huge, this at least narrows down the potential places of a regression a lot. [Other Info] * n/a --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Originally reported against libvirt which happens to be one of the example-triggers Hi, when I shut down my machine I see messages from /usr/lib/libvirt /libvirt-guests.sh but there are 2 anomalies: - 3 libvirt-guests.sh processes are run - messages are truncated ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libvirt-daemon 6.0.0-0ubuntu8 Uname: Linux 5.6.7-050607-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Apr 28 19:42:56 2020 SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-multicast.xml']
[Touch-packages] [Bug 1856574] Re: removal of various autopilot packages
** Tags added: update-excuse ** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/1856574 Title: removal of various autopilot packages Status in autopilot-gtk package in Ubuntu: Triaged Status in autopilot-legacy package in Ubuntu: Fix Released Status in python-fixtures package in Ubuntu: Fix Released Status in python-testtools package in Ubuntu: Fix Released Bug description: python-fixtures and python-testtools are not built anymore in focal, but still referenced by some Ubuntu-only packages. We need to at least remove autopilot-legacy if we don't want to re-introduce those package, and modify autopilot-gtk to build witout the autopilot-legacy b-d. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1877088] Comment bridged from LTC Bugzilla
On Fri, 26 Jun 2020 at 15:01, bugproxy <1877...@bugs.launchpad.net> wrote: > > --- Comment From niklas.schne...@ibm.com 2020-06-26 09:45 EDT--- > (In reply to comment #17) > > Eoan and later d-i, new installer, curtin do not install > > /etc/kernel-img.conf. > > Upgraded systems keep having it (ie. installed with bionic or xenial, and > > upgraded). > > > > Can you please let me know if _removing_ /etc/kernel-img.conf breaks $ sudo > > make install, and if adding /etc/kernel-img.conf back fixes $ sudo make > > install? > > > > Cause the expectation is that `/etc/kernel-img.conf` should not be there, > > yet everything should still work correctly. > > > > I think somewhere something is reading "link_in_boot=yes" and was not > > updated with the new implicit default to always assume that on recent > > ubuntu. > > For me the installkernel script (including in the current case "sudo > make install" from a mainline Linux tree) doesn't update the > /boot/initrd.img symlink. > > Interestingly a package upgrade for linux-generic does overwrite this > symlink. .deb package uses very different maintainer scripts / codepath, and is not the same operation as "sudo make install". I personally always build my kernels as debs, and install debs, rather than doing "sudo make install". But I am a distribution developer, and I care for .debs to work right. Kernel developers, I guess, are inverse, and care for "upstream" $ sudo make install to work. > > Not with the /etc/kernel-img.conf[0] and not without it either. > As before the /boot/vmlinuz link is always updated. > That is slightly concerning, as to how $ sudo make install, ever worked before. Or what has changed since. Normally, $ sudo make install, should lookup if /sbin/installkernel is available, and call that to "do what it has to do, on a given distribution", and that script is shipped by the debianutils package which is required and must be installed always. And it hasn't been touched in ages. I wonder which arguments are passed to /sbin/installkernel by $ sudo make install. And whether the 4th argument is passed, and if it is empty, /, or /boot. It should be either empty, or /boot. -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Triaged Status in debianutils package in Ubuntu: New Status in linux-base package in Ubuntu: New Bug description: When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old
[Touch-packages] [Bug 1885309] Re: package lsb-security 9.20160110ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1885309 Title: package lsb-security 9.20160110ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in lsb package in Ubuntu: New Bug description: I leave only acknowledgement that I am not fully competent to discern linux issues. My hope is that the additional debug information will provide the details that I can't see. I am relatively competent and comfortable with sysadm-level unix activities, so I'm sure I can execute instructions if provided. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lsb-security 9.20160110ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Jun 26 12:17:52 2020 DuplicateSignature: package:lsb-security:9.20160110ubuntu0.2 Setting up libnss3:amd64 (2:3.28.4-0ubuntu0.16.04.11) ... dpkg: error processing package lsb-security (--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 2016-08-14 (1411 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: lsb Title: package lsb-security 9.20160110ubuntu0.2 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/lsb/+bug/1885309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885310] [NEW] Unable to add local printer. cups hanging
Public bug reported: Initially added epson c60 stylus but it installed with filter error. Deleted printer from cups , added new printer. Added the epson printer , selected the .ppd file that worked in 1904 and clicked add printer. Cups just sits and thinks. Same happens if I use the applications/System/printers menu. Thanks Peter ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups-daemon 2.3.1-9ubuntu1.1 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.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 26 18:16:57 2020 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2020-06-01 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: EPSON-Stylus-C60: Epson Stylus C60 - CUPS+Gutenprint v5.3.1 ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcEnviron: LANG=en_ZA.UTF-8 LANGUAGE=en_ZA:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=b750d723-abc0-43bf-bfd0-945d09637362 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41T-M LX3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1885310 Title: Unable to add local printer. cups hanging Status in cups package in Ubuntu: New Bug description: Initially added epson c60 stylus but it installed with filter error. Deleted printer from cups , added new printer. Added the epson printer , selected the .ppd file that worked in 1904 and clicked add printer. Cups just sits and thinks. Same happens if I use the applications/System/printers menu. Thanks Peter ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups-daemon 2.3.1-9ubuntu1.1 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.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 26 18:16:57 2020 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2020-06-01 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: EPSON-Stylus-C60: Epson Stylus C60 - CUPS+Gutenprint v5.3.1 ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcEnviron: LANG=en_ZA.UTF-8 LANGUAGE=en_ZA:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=b750d723-abc0-43bf-bfd0-945d09637362 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41T-M LX3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/16/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1885310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1885309] [NEW] package lsb-security 9.20160110ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
Public bug reported: I leave only acknowledgement that I am not fully competent to discern linux issues. My hope is that the additional debug information will provide the details that I can't see. I am relatively competent and comfortable with sysadm-level unix activities, so I'm sure I can execute instructions if provided. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lsb-security 9.20160110ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Jun 26 12:17:52 2020 DuplicateSignature: package:lsb-security:9.20160110ubuntu0.2 Setting up libnss3:amd64 (2:3.28.4-0ubuntu0.16.04.11) ... dpkg: error processing package lsb-security (--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 2016-08-14 (1411 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: lsb Title: package lsb-security 9.20160110ubuntu0.2 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: lsb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1885309 Title: package lsb-security 9.20160110ubuntu0.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in lsb package in Ubuntu: New Bug description: I leave only acknowledgement that I am not fully competent to discern linux issues. My hope is that the additional debug information will provide the details that I can't see. I am relatively competent and comfortable with sysadm-level unix activities, so I'm sure I can execute instructions if provided. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lsb-security 9.20160110ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Fri Jun 26 12:17:52 2020 DuplicateSignature: package:lsb-security:9.20160110ubuntu0.2 Setting up libnss3:amd64 (2:3.28.4-0ubuntu0.16.04.11) ... dpkg: error processing package lsb-security (--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 2016-08-14 (1411 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: lsb Title: package lsb-security 9.20160110ubuntu0.2 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/lsb/+bug/1885309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885111] Re: 3 ports disabled
Thank you very much, I have closed the bug now. ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid -- 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/1885111 Title: 3 ports disabled Status in cups package in Ubuntu: Invalid Bug description: The printer (which is now broken) we used seem to disable the ports. I don't know how to fix this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jun 25 09:53:44 2020 DistUpgraded: 2019-01-03 13:59:44,209 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a2a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation GT216M [GeForce GT 230M] [104d:905e] InstallationDate: Installed on 2016-12-22 (1281 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VPCCW1AGG ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=a904e50d-625f-4d72-929f-b72fcad907ef ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-01-03 (538 days ago) dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y5:bd09/22/2009:svnSonyCorporation:pnVPCCW1AGG:pvrC6031Z7V:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCCW1AGG dmi.product.version: C6031Z7V dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Thu Jan 3 08:58:12 2019 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1885111/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1883116] Re: SRU the current 3.36.3 stable update
3.36.3-0ubuntu1 works fine, evolution is behaving without issue with it, GNOME calendar integration is working, marking as verified ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1883116 Title: SRU the current 3.36.3 stable update Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1883116/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885272] Re: Re-logging occurs continuously during ubuntu operation
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1878193 -- 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/1885272 Title: Re-logging occurs continuously during ubuntu operation Status in xorg package in Ubuntu: New Bug description: completely impossible to work some errors constantly occur and then reboot the xorg (relogin occurs) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875435 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: 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: Fri Jun 26 14:48:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile] [103c:8603] InstallationDate: Installed on 2020-05-13 (43 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP OMEN by HP Laptop 17-cb0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5165ccf9-e9d6-457b-8152-e74b73fe461e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 5VX37AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1885272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1885111] Re: 3 ports disabled
Hi Sebastian, thank you so much for replying to my query. I am sorry to waste your time but the problem seems to have resolved itself. Our printer broke and seemed to block all the ports on the laptop. I then sent the request for help. Next morning switched on the laptop and the ports were working again. So you can close this problem. Thank you again. Melanie On Thu, 25 Jun 2020 at 12:55, Sebastien Bacher <1885...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and help make Ubuntu > better. Unfortunately, we cannot work on this bug because your > description didn't include enough information. You may find it helpful > to read 'How to report bugs effectively' > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem. > > We have instructions on debugging some types of problems at > http://wiki.ubuntu.com/DebuggingProcedures. > > At a minimum, we need: > 1. The specific steps or actions you took that caused you to encounter the > problem. > 2. The behavior you expected. > 3. The behavior you actually encountered (in as much detail as possible). > > Thanks! > > ** Package changed: xorg (Ubuntu) => cups (Ubuntu) > > ** Changed in: cups (Ubuntu) >Importance: Undecided => Low > > ** Changed in: cups (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1885111 > > Title: > 3 ports disabled > > Status in cups package in Ubuntu: > Incomplete > > Bug description: > The printer (which is now broken) we used seem to disable the ports. > I don't know how to fix this problem. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 > Uname: Linux 4.15.0-106-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7.15 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > Date: Thu Jun 25 09:53:44 2020 > DistUpgraded: 2019-01-03 13:59:44,209 DEBUG icon theme changed, > re-reading > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a2a] (rev a2) > (prog-if 00 [VGA controller]) > Subsystem: Sony Corporation GT216M [GeForce GT 230M] [104d:905e] > InstallationDate: Installed on 2016-12-22 (1281 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: Sony Corporation VPCCW1AGG > ProcEnviron: >LANGUAGE=en_ZA:en >PATH=(custom, no user) >LANG=en_ZA.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic > root=UUID=a904e50d-625f-4d72-929f-b72fcad907ef ro quiet splash > SourcePackage: xorg > UpgradeStatus: Upgraded to bionic on 2019-01-03 (538 days ago) > dmi.bios.date: 09/22/2009 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: R0190Y5 > dmi.board.asset.tag: N/A > dmi.board.name: VAIO > dmi.board.vendor: Sony Corporation > dmi.board.version: N/A > dmi.chassis.asset.tag: N/A > dmi.chassis.type: 10 > dmi.chassis.vendor: Sony Corporation > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrR0190Y5:bd09/22/2009:svnSonyCorporation:pnVPCCW1AGG:pvrC6031Z7V:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: > dmi.product.family: VAIO > dmi.product.name: VPCCW1AGG > dmi.product.version: C6031Z7V > dmi.sys.vendor: Sony Corporation > version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 > version.libdrm2: libdrm2 2.4.101-2~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.5-1ubuntu1 > 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 > xserver.bootTime: Thu Jan 3 08:58:12 2019 > xserver.configfile: default > xserver.errors: >Failed to load module "nvidia" (module does not exist, 0) >Failed to load module "nvidia" (module does not exist, 0) > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.18.4-0ubuntu0.3 > xserver.video_driver: nouveau > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1885111/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups
[Touch-packages] [Bug 1877590] Re: SRU the current 3.24.20 stable update
the emoji picker also works without issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877590 Title: SRU the current 3.24.20 stable update Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that GNOME Desktop and GTK software still work correctly * Regression potential The update has some fixes in the filechooser and the emoji picker, test those Check also that GUI elements in Adwaita and Yaru still look correct To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877590] Re: SRU the current 3.24.20 stable update
Using 3.24.20-0ubuntu1 there is no visible issue, neither in the desktop nor in the Ubuntu and upstream theme. The new version is also in the current Ubuntu and Debian serie without new issue reported. Setting as verified ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877590 Title: SRU the current 3.24.20 stable update Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that GNOME Desktop and GTK software still work correctly * Regression potential The update has some fixes in the filechooser and the emoji picker, test those Check also that GUI elements in Adwaita and Yaru still look correct To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Hi HP OMEN 17 cb (2019) with the same issue. Thanks to #63 and #65 I got somewhat working the audio but not the internal mics yet. What happens here is that the Mic is a digital array. Is not the simple analog mic that always we use. Intel SST mic array with the realtek alc285. This discussion maybe has the answer https://bugzilla.kernel.org/show_bug.cgi?id=201251 ** Bug watch added: Linux Kernel Bug Tracker #201251 https://bugzilla.kernel.org/show_bug.cgi?id=201251 -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875335] Re: evolution public certificate lookups in ldap fail
Thank you for your bug report. On what version of Ubuntu are you seeing the issue? ** Package changed: evolution (Ubuntu) => evolution-data-server (Ubuntu) ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Low ** Changed in: evolution-data-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1875335 Title: evolution public certificate lookups in ldap fail Status in evolution-data-server package in Ubuntu: Incomplete Bug description: Looking up user's public certificates in AD/LDAP fail while looking up with regular ldapsearch works without any issues. ldapsearch -LLL -b DC=company,DC=com -H ldap://ADDC.company.com -Q -N '(cn=username)' userCertificate -z 10 -o ldif-wrap=no dn: CN=username,OU=CA,OU=User,OU=OU1,OU=ID,OU=OU2,DC=company,DC=com userCertificate:: MII...truncated Evolution can't look up these certificates and evolution's address book processes hang even crash evolution. The same configuration work both with ldapsearch and in thunderbird, but thunderbird is not an alternative in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1875335/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
@Sebastien I installed ubuntu 19.10 in a VM, compared the file Michael refers to with the one in my system (20.04) and only the following lines are removed in 20.04: ### Automatically move streams to the default sink if the sink they are ### connected to dies, similar for sources load-module module-rescue-streams According to pulseaudio's release notes this is because this functionality is moved to the core and no longer needed. -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875335] [NEW] evolution public certificate lookups in ldap fail
You have been subscribed to a public bug: Looking up user's public certificates in AD/LDAP fail while looking up with regular ldapsearch works without any issues. ldapsearch -LLL -b DC=company,DC=com -H ldap://ADDC.company.com -Q -N '(cn=username)' userCertificate -z 10 -o ldif-wrap=no dn: CN=username,OU=CA,OU=User,OU=OU1,OU=ID,OU=OU2,DC=company,DC=com userCertificate:: MII...truncated Evolution can't look up these certificates and evolution's address book processes hang even crash evolution. The same configuration work both with ldapsearch and in thunderbird, but thunderbird is not an alternative in this case. ** Affects: evolution-data-server (Ubuntu) Importance: Low Status: Incomplete -- evolution public certificate lookups in ldap fail https://bugs.launchpad.net/bugs/1875335 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885287] Re: some minimum versions in the symbols file are not updated
Also, g_utf8_make_valid is introduced in 2.51.0, but changed from 2.51.4 to 2.51.5: //glib-2.51.4/glib/gunicode.h gchar *g_utf8_make_valid(const gchar *str); //glib-2.51.5/glib/gunicode.h gchar *g_utf8_make_valid(const gchar *str, gssize len); The minimum version should be 2.51.5, instead of 2.51.0 in the symbols file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1885287 Title: some minimum versions in the symbols file are not updated Status in glib2.0 package in Ubuntu: New Bug description: Hi, The signature of the following symbols changed from glib-2.39.1 to glib-2.39.2: //glib-2.39.1/glib/ghash.h void g_hash_table_insert(...); void g_hash_table_replace(...); void g_hash_table_add(...); //glib-2.39.2/glib/ghash.h gboolean g_hash_table_insert(...); gboolean g_hash_table_replace(...); gboolean g_hash_table_add(...); However, the minimum versions of these symbols in the symbols file are all 2.12.0. The minimum versions are supposed to be 2.39.2, or a client using a gboolean return value may be linked to an old version returning void. Best, Zhouyang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1885287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877726] Re: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working
I posted to the alsa-user list... here is the link to the archive thread: https://sourceforge.net/p/alsa/mailman/message/37009196/ The only answer I got so far was that the Rodecaster was apparently not completely class compliant. Hopefully someone can find more info. -- 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 Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: nils 90077 F pulseaudio /dev/snd/controlC0: nils 90077 F pulseaudio /dev/snd/controlC1: nils 90077 F pulseaudio Symptom_Jack: SPDIF Out, Internal Symptom_Type: Sound works for some users but not for others Title: [HDA-Intel - HD-Audio Generic, playback] sound not working for all users UpgradeStatus: Upgraded to focal on 2020-05-09 (0 days ago) dmi.bios.date: 10/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5222 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5222:bd10/14/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-09T11:23:29.080704 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885287] [NEW] some minimum versions in the symbols file are not updated
Public bug reported: Hi, The signature of the following symbols changed from glib-2.39.1 to glib-2.39.2: //glib-2.39.1/glib/ghash.h void g_hash_table_insert(...); void g_hash_table_replace(...); void g_hash_table_add(...); //glib-2.39.2/glib/ghash.h gboolean g_hash_table_insert(...); gboolean g_hash_table_replace(...); gboolean g_hash_table_add(...); However, the minimum versions of these symbols in the symbols file are all 2.12.0. The minimum versions are supposed to be 2.39.2, or a client using a gboolean return value may be linked to an old version returning void. Best, Zhouyang ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: file symbols -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1885287 Title: some minimum versions in the symbols file are not updated Status in glib2.0 package in Ubuntu: New Bug description: Hi, The signature of the following symbols changed from glib-2.39.1 to glib-2.39.2: //glib-2.39.1/glib/ghash.h void g_hash_table_insert(...); void g_hash_table_replace(...); void g_hash_table_add(...); //glib-2.39.2/glib/ghash.h gboolean g_hash_table_insert(...); gboolean g_hash_table_replace(...); gboolean g_hash_table_add(...); However, the minimum versions of these symbols in the symbols file are all 2.12.0. The minimum versions are supposed to be 2.39.2, or a client using a gboolean return value may be linked to an old version returning void. Best, Zhouyang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1885287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877088] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-06-26 09:45 EDT--- (In reply to comment #17) > Eoan and later d-i, new installer, curtin do not install > /etc/kernel-img.conf. > Upgraded systems keep having it (ie. installed with bionic or xenial, and > upgraded). > > Can you please let me know if _removing_ /etc/kernel-img.conf breaks $ sudo > make install, and if adding /etc/kernel-img.conf back fixes $ sudo make > install? > > Cause the expectation is that `/etc/kernel-img.conf` should not be there, > yet everything should still work correctly. > > I think somewhere something is reading "link_in_boot=yes" and was not > updated with the new implicit default to always assume that on recent ubuntu. For me the installkernel script (including in the current case "sudo make install" from a mainline Linux tree) doesn't update the /boot/initrd.img symlink. Interestingly a package upgrade for linux-generic does overwrite this symlink. Not with the /etc/kernel-img.conf[0] and not without it either. As before the /boot/vmlinuz link is always updated. [0] # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = yes do_initrd = yes link_in_boot = yes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Triaged Status in debianutils package in Ubuntu: New Status in linux-base package in Ubuntu: New Bug description: When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881554] Re: PCI/internal sound card not detected
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1881554 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No sound ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jun 1 15:11:24 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0DG5G3 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd05/14/2018:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0DG5G3:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-06-01T14:54:04.434257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1881554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885246] Re: Desktop freezes when moving window fast to other desktop
The AMD Open Source driver has the same problem, may even be worse. Also sometimes when rebooting through ssh the computer is locking up, so I have to hard reset it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1885246 Title: Desktop freezes when moving window fast to other desktop Status in lightdm package in Ubuntu: New Bug description: For a long time sometimes my desktop freezes suddenly and it took me a long time to find when. It turns out sometimes the desktop freezes when I move a window fast from one desktop to another, normally I would move it to the right. OS is Ubuntu 18.04 and the issue occurs (as far as I remember) with the Open Source drivers and the AMD drivers. When using some default setting/driver the issue does not occur, but then screen updates are very slow. I am using an MSI H81M-P33 motherboard, processor i5-4460, AMD Radeon HD 7700 Series (according to AMD driver). Monitor is AOC 1920x1080. I tried many things, like different kernal versions and different drivers. The currently installed AMD drivers don't work with the 5.3 kernel. I did not recently use something like kernel 5.0, so I don't know if the issue is solved in later kernels. I found some similar reports, but they all or mostly seem to relate to laptops. While writing this report my desktop crashed again and I was not moving a window, but just resizing it from the top down. I can access the system through ssh and just changed the drivers from AMD pro to AMD open source. Not sure what the effect is. More details available if needed. I would appreciate this would be solved, as it is pretty annoying to restart my computer several times a day and sometimes losing work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Jun 26 13:42:55 2020 InstallationDate: Installed on 2019-05-30 (392 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1885246/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885278] [NEW] Black screen after standby on Intel NUC
Public bug reported: I have Kubuntu 20.04 on an Intel NUC NUC7JY. When I go into standby and try to wake it up, the NUC wakes up but there is no picture only black screen. This can be reproduced every time I go into standby. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Fri Jun 26 15:07:18 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 605 [8086:2072] InstallationDate: Installed on 2020-06-25 (0 days ago) InstallationMedia: Kubuntu 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 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 03f0:034a HP, Inc Elite Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC7CJYH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=30399171-99ff-4cba-8ebe-26915e7b80c9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0050.2019.0418.1441 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67967-404 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrJYGLKCPX.86A.0050.2019.0418.1441:bd04/18/2019:svnIntel(R)ClientSystems:pnNUC7CJYH:pvrJ67971-405:rvnIntelCorporation:rnNUC7JYB:rvrJ67967-404:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: JY dmi.product.name: NUC7CJYH dmi.product.version: J67971-405 dmi.sys.vendor: Intel(R) Client Systems 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/1885278 Title: Black screen after standby on Intel NUC Status in xorg package in Ubuntu: New Bug description: I have Kubuntu 20.04 on an Intel NUC NUC7JY. When I go into standby and try to wake it up, the NUC wakes up but there is no picture only black screen. This can be reproduced every time I go into standby. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Fri Jun 26 15:07:18 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 605 [8086:2072] InstallationDate: Installed on 2020-06-25 (0 days ago) InstallationMedia: Kubuntu 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 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 03f0:034a HP, Inc Elite Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC7CJYH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=30399171-99ff-4cba-8ebe-26915e7b80c9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: JYGLKCPX.86A.0050.2019.0418.1441 dmi.board.name: NUC7JYB dmi.board.vendor: Intel Corporation dmi.board.version: J67967-404 dmi.chassis.type: 35
[Touch-packages] [Bug 1875708] Re: Truncated messages in journald since systemd v244
A SRU to Focal would be greatly appreciated as dehydrated (Let's Encrypt client) is also affected, probably because it's in essence just a bash script. Here are the logs where it seems to indicate the certificate doesn't need to to be renewed just yet: Jun 25 00:26:10 rproxy dehydrated[21256]: + Valid till Aug 4 03:20:48 2020 GMT Jun 25 00:26:10 rproxy dehydrated[21407]: + Valid till Aug 4 03:20:4 Jun 25 00:26:10 rproxy dehydrated[21256]: + Valid till Aug 4 03:20:4 Jun 25 00:26:10 rproxy dehydrated[21256]: Longer tha Having the full output would be nice :) Count on me for a focal-proposed verification if you agree on a SRU ;) -- 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/1875708 Title: Truncated messages in journald since systemd v244 Status in libvirt package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in libvirt source package in Focal: Confirmed Status in systemd source package in Focal: In Progress Status in libvirt source package in Groovy: Invalid Status in systemd source package in Groovy: Fix Released Bug description: [Impact] * since 09d0b46a "journal: refresh cached credentials of stdout streams" in ~244 output may be trincated. * Upstream has a fix in https://github.com/systemd/systemd/pull/15685 * Backporting the fix will avoid truncation of log output to journald [Test Case] * This could happen in any case, but is more likely when a program that has output going to journald is spawning short-lived sub-programs often. Therefore the test emphasizes on that: - Use a test service like /etc/systemd/system/test.service: [Unit] Description=Test Truncate After=network.target [Service] ExecStart=/usr/lib/test.sh long-test-for-start ExecStop=/usr/lib/test.sh long-test-for-stop Type=oneshot RemainAfterExit=yes StandardOutput=journal+console TimeoutStopSec=0 [Install] WantedBy=multi-user.target - And a test script like /usr/lib/test.sh: #!/bin/sh gettext "This will" echo gettext "usually fail" echo gettext "and be truncated" echo Start/Stopping that service without the fix will look like: Apr 30 18:56:40 f systemd[1]: Stopping Test Truncate... Apr 30 18:56:40 f test.sh[1165]: T Apr 30 18:56:40 f test.sh[1167]: T Apr 30 18:56:40 f test.sh[1167]: sually fai Apr 30 18:56:40 f test.sh[1165]: s Apr 30 18:56:40 f test.sh[1168]: s Apr 30 18:56:40 f test.sh[1168]: nd be truncate Apr 30 18:56:40 f test.sh[1165]: n Apr 30 18:56:40 f systemd[1]: test.service: Succeeded. Apr 30 18:56:40 f systemd[1]: Stopped Test Truncate. [Regression Potential] * The patches are rather small, but there might be a slightly increased memory consumption of journald for output buffers. * Issues (if any and I couldn't find any so far) should be only to journald output handling. Systemd is huge, this at least narrows down the potential places of a regression a lot. [Other Info] * n/a --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Originally reported against libvirt which happens to be one of the example-triggers Hi, when I shut down my machine I see messages from /usr/lib/libvirt /libvirt-guests.sh but there are 2 anomalies: - 3 libvirt-guests.sh processes are run - messages are truncated ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libvirt-daemon 6.0.0-0ubuntu8 Uname: Linux 5.6.7-050607-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Apr 28 19:42:56 2020 SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml:
[Touch-packages] [Bug 1875708] Re: Truncated messages in journald since systemd v244
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libvirt (Ubuntu Focal) Status: New => Confirmed -- 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/1875708 Title: Truncated messages in journald since systemd v244 Status in libvirt package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in libvirt source package in Focal: Confirmed Status in systemd source package in Focal: In Progress Status in libvirt source package in Groovy: Invalid Status in systemd source package in Groovy: Fix Released Bug description: [Impact] * since 09d0b46a "journal: refresh cached credentials of stdout streams" in ~244 output may be trincated. * Upstream has a fix in https://github.com/systemd/systemd/pull/15685 * Backporting the fix will avoid truncation of log output to journald [Test Case] * This could happen in any case, but is more likely when a program that has output going to journald is spawning short-lived sub-programs often. Therefore the test emphasizes on that: - Use a test service like /etc/systemd/system/test.service: [Unit] Description=Test Truncate After=network.target [Service] ExecStart=/usr/lib/test.sh long-test-for-start ExecStop=/usr/lib/test.sh long-test-for-stop Type=oneshot RemainAfterExit=yes StandardOutput=journal+console TimeoutStopSec=0 [Install] WantedBy=multi-user.target - And a test script like /usr/lib/test.sh: #!/bin/sh gettext "This will" echo gettext "usually fail" echo gettext "and be truncated" echo Start/Stopping that service without the fix will look like: Apr 30 18:56:40 f systemd[1]: Stopping Test Truncate... Apr 30 18:56:40 f test.sh[1165]: T Apr 30 18:56:40 f test.sh[1167]: T Apr 30 18:56:40 f test.sh[1167]: sually fai Apr 30 18:56:40 f test.sh[1165]: s Apr 30 18:56:40 f test.sh[1168]: s Apr 30 18:56:40 f test.sh[1168]: nd be truncate Apr 30 18:56:40 f test.sh[1165]: n Apr 30 18:56:40 f systemd[1]: test.service: Succeeded. Apr 30 18:56:40 f systemd[1]: Stopped Test Truncate. [Regression Potential] * The patches are rather small, but there might be a slightly increased memory consumption of journald for output buffers. * Issues (if any and I couldn't find any so far) should be only to journald output handling. Systemd is huge, this at least narrows down the potential places of a regression a lot. [Other Info] * n/a --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Originally reported against libvirt which happens to be one of the example-triggers Hi, when I shut down my machine I see messages from /usr/lib/libvirt /libvirt-guests.sh but there are 2 anomalies: - 3 libvirt-guests.sh processes are run - messages are truncated ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libvirt-daemon 6.0.0-0ubuntu8 Uname: Linux 5.6.7-050607-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Apr 28 19:42:56 2020 SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: [inaccessible: [Errno 13] Permission
[Touch-packages] [Bug 1875435] Re: Re-logging occurs continuously during ubuntu operation
*** This bug is a duplicate of bug 1878193 *** https://bugs.launchpad.net/bugs/1878193 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1885272 -- 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/1875435 Title: Re-logging occurs continuously during ubuntu operation Status in xorg package in Ubuntu: Incomplete Bug description: I thought that I had some kind of problem with the video driver and all the detailed logs are contained here https://forums.developer.nvidia.com/t/ubuntu-kernel-v5-6-v5-7-for-hp-omen-17t-bc000-gforce-rtx2080-unstable-driver-nvidia-linux-x86-64-440-82-run/120027/25 But I installed ubuntu 20.04 and the problem is repeated not only on new kernels ubuntu 5.6 and 5.7.0-rc but also on kernel 5.4 with the Nouveau driver The system constantly logs onto the standard screen and requires a password to close all current programs --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile] [103c:8603] InstallationDate: Installed on 2020-04-24 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP OMEN by HP Laptop 17-cb0xxx Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=c8a52116-acb9-4b90-b5b4-8f3641a10385 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Tags: focal possible-manual-nvidia-install ubuntu Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 5VX37AV dmi.sys.vendor: HP 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 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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile] [103c:8603] InstallationDate: Installed on 2020-04-24 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP OMEN by HP Laptop 17-cb0xxx Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=c8a52116-acb9-4b90-b5b4-8f3641a10385 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Tags: focal possible-manual-nvidia-install ubuntu Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.41:cvnHP:ct10:cvrChassisVersion:
[Touch-packages] [Bug 1885272] [NEW] Re-logging occurs continuously during ubuntu operation
Public bug reported: completely impossible to work some errors constantly occur and then reboot the xorg (relogin occurs) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875435 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: 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: Fri Jun 26 14:48:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile] [103c:8603] InstallationDate: Installed on 2020-05-13 (43 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP OMEN by HP Laptop 17-cb0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5165ccf9-e9d6-457b-8152-e74b73fe461e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 5VX37AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/1885272 Title: Re-logging occurs continuously during ubuntu operation Status in xorg package in Ubuntu: New Bug description: completely impossible to work some errors constantly occur and then reboot the xorg (relogin occurs) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875435 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: 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: Fri Jun 26 14:48:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation TU104BM [GeForce RTX 2080 Mobile] [10de:1ed0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU104BM [GeForce RTX 2080 Mobile] [103c:8603] InstallationDate: Installed on 2020-05-13 (43 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP OMEN by HP Laptop 17-cb0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5165ccf9-e9d6-457b-8152-e74b73fe461e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 1884846] Re: Can't connect to internet if second user session
Hello Sebastien, I'm admin, yes. `groups` gives me: facundo adm cdrom sudo dip plugdev lpadmin lxd sambashare I did not try to activate any specific connection: it's just NM trying to connect to one of its saved WiFis when starting the session. I don't have gnome to try it. -- 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/1884846 Title: Can't connect to internet if second user session Status in network-manager package in Ubuntu: Incomplete Bug description: My kid was using the laptop, connected to internet in his user session. I switched to my user (but his session was still active), and NetworkManager couldn't connect to internet. Error from syslog: Jun 23 19:30:15 tanquita NetworkManager[854]: [1592951415.1979] audit: op="connection-activate" uuid="a52379fa- 0a44-4013-93b6-b04e63515fb9" name="Voyager" pid=34278 uid=1000 result="fail" reason="Private connection already active on the device: uid 1000 has no permission to perform this operation" (uid 1000 is myself) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 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 CurrentDesktop: KDE Date: Tue Jun 23 19:40:19 2020 InstallationDate: Installed on 2020-06-20 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.100.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.100.0/24 dev wlp4s0 proto kernel scope link src 192.168.100.103 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1884846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884846] Re: Can't connect to internet if second user session
Data point: after several attempts in error, it ended up connecting to WiFi... maybe the other connection in the other session did some kind of timeout? -- 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/1884846 Title: Can't connect to internet if second user session Status in network-manager package in Ubuntu: Incomplete Bug description: My kid was using the laptop, connected to internet in his user session. I switched to my user (but his session was still active), and NetworkManager couldn't connect to internet. Error from syslog: Jun 23 19:30:15 tanquita NetworkManager[854]: [1592951415.1979] audit: op="connection-activate" uuid="a52379fa- 0a44-4013-93b6-b04e63515fb9" name="Voyager" pid=34278 uid=1000 result="fail" reason="Private connection already active on the device: uid 1000 has no permission to perform this operation" (uid 1000 is myself) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 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 CurrentDesktop: KDE Date: Tue Jun 23 19:40:19 2020 InstallationDate: Installed on 2020-06-20 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.100.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.100.0/24 dev wlp4s0 proto kernel scope link src 192.168.100.103 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1884846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 #lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal #uname -r 5.4.0-37-generic #pulseaudio --version pulseaudio 13.99.1 [B4:86:55:E1:8B:07] Name: FlyPods Lite Alias: FlyPods Lite [rw] Address: B4:86:55:E1:8B:07 Icon: audio-card Class: 0x2c0404 Paired: 1 Trusted: 1 [rw] Blocked: 0 [rw] Connected: 1 UUIDs: [AudioSource, AudioSink, AVRemoteControl, Handsfree, PnPInformation] bt-device -s B4:86:55:E1:8B:07 Discovering services... [RECORD:0x1] SrvClassIDList: "AudioSink" ProtocolDescList: "L2CAP", 0x19 "AVDTP", 0x103 BTProfileDescList: "AdvAudio", 0x103 SrvName: "Advanced Audio" ProviderName: "MtView" [RECORD:0x10002] SrvClassIDList: "Handsfree", "Audio" ProtocolDescList: "L2CAP" "RFCOMM", Channel: 1 BTProfileDescList: "Handsfree", 0x107 SrvName: "Hands-Free unit " [RECORD:0x10001] SrvClassIDList: "AVRemote", "VideoConf" ProtocolDescList: "L2CAP", 0x17 "AVCTP", 0x102 BTProfileDescList: "AVRemote", 0x105 SrvName: "MVIEW " ProviderName: "MVIEW " [RECORD:0x10003] SrvClassIDList: "AudioSource" ProtocolDescList: "L2CAP", 0x19 "AVDTP", 0x103 BTProfileDescList: "AdvAudio", 0x103 SrvName: "Advanced Audio" ProviderName: "MtView" -- 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/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+subscriptions -- Mailing list: https://launchpad.net/~touch-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 I replaced default.pa with the one extracted from the deb mentioned by @David but, in my case, it did not fixed the issue, so as @Hui said there can be several underlying issues causing the same problem. In my case (Dell XPS13 7390) the kernel module used is btintel with device firmware: intel/ibt-20-1-3.sfi. I have verified with btmon that when I switch from adsp to hsp/hfp it stops showing packages coming from the headset. @Corey to extract the file you just have to run something like: dpkg-deb -x pulseaudio_11.1-1ubuntu7_amd64.deb 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 1860549] Re: isc-dhcp server not use configuration file options
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: isc-dhcp (Ubuntu) Status: New => Confirmed -- 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/1860549 Title: isc-dhcp server not use configuration file options Status in isc-dhcp package in Ubuntu: Confirmed Bug description: in /etc/default/isc-dhcp-server describe two options # cat /etc/default/isc-dhcp-server # On what interfaces should the DHCP server (dhcpd) serve DHCP requests? # Separate multiple interfaces with spaces, e.g. "eth0 eth1". INTERFACESv4="" INTERFACESv6="" But in systemctl unit files used old option, without v4/v6 suffixes # systemctl cat isc-dhcp-server6.service . exec dhcpd -user dhcpd -group dhcpd -f -6 -pf /run/dhcp-server/dhcpd6.pid -cf $CONFIG_FILE $INTERFACES' Fix is very quick ;) s/INTERFACES/INTERFACESv4/ in isc-dhcp-server.service s/INTERFACES/INTERFACESv6/ in isc-dhcp-server6.service Or as workaround add old INTERFACES="" to /etc/default/isc-dhcp-server ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: isc-dhcp-server 4.4.1-2ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Jan 22 12:51:26 2020 InstallationDate: Installed on 2020-01-18 (3 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.dhcp.dhcpd.conf: [modified] modified.conffile..etc.dhcp.dhcpd6.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2020-01-19T14:25:59.040443 mtime.conffile..etc.dhcp.dhcpd6.conf: 2020-01-19T16:28:31.017125 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1860549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827957] Re: After unplugging HDMI, internal sound's balance is not center [Acer Swift 5 SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1827957 Title: After unplugging HDMI, internal sound's balance is not center [Acer Swift 5 SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: After unplugging HDMI which was selected to transmit sound (successfully) the internal sound is almost all (one from the most extreme position) on the left. Before that the balance was certainly in the center. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.19.21-041921-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lune 1908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 23:48:24 2019 InstallationDate: Installed on 2019-01-06 (120 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Grey Speaker, Internal Symptom_Type: Volume slider, or mixer problems Title: [Swift SF514-53T, Realtek ALC255, Grey Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604617] Re: dhclient does not send fqdn.fqdn for DHCPv6
Hi, This is not working for me. I have installed dhcpd4.4.2 and dhclient4.4.2. I am using centos7 for server and client. My dhclient6.conf has below entries in it: send fqdn.fqdn "hostname.domain.name"; send host-name "hostname"; But when I get a lease6 there is no any details about hostname/fqdn in the dhcpd.leases file on the dhcp server. Please help. -- 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/1604617 Title: dhclient does not send fqdn.fqdn for DHCPv6 Status in isc-dhcp package in Ubuntu: Confirmed Bug description: ISC DHCP's dynamic DNS updates rely on the fqdn.fqdn option being sent in order to work for DHCPv6. This used to be done in Ubuntu, as shown in bugs #991360 and #108862, and all my Windows hosts send it. However this was removed in Ubuntu due to a regression in IPv4 functionality. As IPv6 is more widely deployed these days, this regression in IPv6 should be fixed. This bug is current as of Ubuntu 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1604617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885246] Re: Desktop freezes when moving window fast to other desktop
** Package changed: ubuntu => lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1885246 Title: Desktop freezes when moving window fast to other desktop Status in lightdm package in Ubuntu: New Bug description: For a long time sometimes my desktop freezes suddenly and it took me a long time to find when. It turns out sometimes the desktop freezes when I move a window fast from one desktop to another, normally I would move it to the right. OS is Ubuntu 18.04 and the issue occurs (as far as I remember) with the Open Source drivers and the AMD drivers. When using some default setting/driver the issue does not occur, but then screen updates are very slow. I am using an MSI H81M-P33 motherboard, processor i5-4460, AMD Radeon HD 7700 Series (according to AMD driver). Monitor is AOC 1920x1080. I tried many things, like different kernal versions and different drivers. The currently installed AMD drivers don't work with the 5.3 kernel. I did not recently use something like kernel 5.0, so I don't know if the issue is solved in later kernels. I found some similar reports, but they all or mostly seem to relate to laptops. While writing this report my desktop crashed again and I was not moving a window, but just resizing it from the top down. I can access the system through ssh and just changed the drivers from AMD pro to AMD open source. Not sure what the effect is. More details available if needed. I would appreciate this would be solved, as it is pretty annoying to restart my computer several times a day and sometimes losing work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Jun 26 13:42:55 2020 InstallationDate: Installed on 2019-05-30 (392 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1885246/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861082] Re: [SRU] ubuntu-bug doesn't know how to file bugs against snaps
** Changed in: apport (Ubuntu Focal) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861082 Title: [SRU] ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store Server: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: In Progress Bug description: [Impact] Users of Ubuntu 20.04 are not able to easily report bugs against applications provided as a snap. [Test Case] Install subiquity snap: # sudo snap install subiquity --classic subiquity 20.06.1 aus Canonical✓ installiert # snap list | grep subiquity subiquity 20.06.1 1938 latest/stable canonical* classic ubuntu-bug subiquity results in message: # LANGUAGE="en_US" apport-cli subiquity *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ...dpkg-query: no packages found matching subiquity *** You are about to report a bug against the deb package, but you also a have snap published by canonical installed. You can contact them via https://bugs.launchpad.net/subiquity for help. Do you want to continue with the bug report against the deb? What would you like to do? Your options are: Y: Yes N: No C: Cancel === New/Expected Result === ubuntu-bug should ask the user if he/she wants to report the bug against the snap or deb package, if both are installed. If the snap is chosen, the "Snap" and "SnapSource" fields should be part of the report: # LANGUAGE="en_US" apport-cli subiquity *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ...dpkg-query: no packages found matching subiquity *** You have two versions of this application installed, which one do you want to report a bug against? Choices: 1: subiquity 20.06.1 (stable) snap 2: subiquity (1938) deb package C: Cancel Please choose (1/2/C): 1 . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (46.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): V Make sure the following two fields are part of the generated report: == Snap = subiquity 20.06.1 (stable) == SnapSource = subiquity [Regression Potential] Small; the change adds a new add_snap_info() method to report.py and is triggered in the ui.py logic only in cases which would have otherwise lead to an error message. Furthermore, the change has been uploaded to Groovy some while ago where it is being used and tested. [Original Bug Report] Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885246] [NEW] Desktop freezes when moving window fast to other desktop
You have been subscribed to a public bug: For a long time sometimes my desktop freezes suddenly and it took me a long time to find when. It turns out sometimes the desktop freezes when I move a window fast from one desktop to another, normally I would move it to the right. OS is Ubuntu 18.04 and the issue occurs (as far as I remember) with the Open Source drivers and the AMD drivers. When using some default setting/driver the issue does not occur, but then screen updates are very slow. I am using an MSI H81M-P33 motherboard, processor i5-4460, AMD Radeon HD 7700 Series (according to AMD driver). Monitor is AOC 1920x1080. I tried many things, like different kernal versions and different drivers. The currently installed AMD drivers don't work with the 5.3 kernel. I did not recently use something like kernel 5.0, so I don't know if the issue is solved in later kernels. I found some similar reports, but they all or mostly seem to relate to laptops. While writing this report my desktop crashed again and I was not moving a window, but just resizing it from the top down. I can access the system through ssh and just changed the drivers from AMD pro to AMD open source. Not sure what the effect is. More details available if needed. I would appreciate this would be solved, as it is pretty annoying to restart my computer several times a day and sometimes losing work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Jun 26 13:42:55 2020 InstallationDate: Installed on 2019-05-30 (392 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- Desktop freezes when moving window fast to other desktop https://bugs.launchpad.net/bugs/1885246 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2923 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2923 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2923 Importance: Unknown Status: Unknown ** Also affects: inkscape (Ubuntu) Importance: Undecided Status: New ** Changed in: inkscape (Ubuntu) Status: New => Confirmed ** Changed in: inkscape (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in Eye of GNOME: New Status in GNOME Shell: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808421] Re: gparted produces unusual results when ZFS partitios exist
** Tags added: zfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1808421 Title: gparted produces unusual results when ZFS partitios exist Status in GParted: New Status in gparted package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: New Bug description: Run gparted on a disk that has ZFS partitions. It shows one entire partition. Parted seems to display correctly. gparted image attached. hbarta@saugage:~$ sudo parted /dev/sda GNU Parted 3.2 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Model: ATA Samsung SSD 850 (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start EndSizeFile system Name Flags 1 1049kB 538MB 537MB fat32 boot, esp 2 538MB 555MB 16.8MB zfs Microsoft reserved partition msftres 3 555MB 105GB 105GB ntfs Basic data partition msftdata 4 105GB 420GB 315GB zfs rpool (parted) q hbarta@saugage:~$ hbarta@saugage:~$ sudo sgdisk -p /dev/sda Disk /dev/sda: 1953525168 sectors, 931.5 GiB Model: Samsung SSD 850 Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): EBA09D2E-0F70-4D11-8E37-C1C170CFD9DD Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 1953525134 Partitions will be aligned on 2048-sector boundaries Total free space is 1133243757 sectors (540.4 GiB) Number Start (sector)End (sector) Size Code Name 12048 1050623 512.0 MiB EF00 2 1050624 1083391 16.0 MiB0C01 Microsoft reserved ... 3 1083392 205883391 97.7 GiB0700 Basic data partition 4 205883392 820283391 293.0 GiB 8300 rpool hbarta@saugage:~$ hbarta@saugage:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 hbarta@saugage:~$ Reproduce: 1) Configure (perhaps install) Ubuntu on a drive with a ZFS partition. 2) Open gparted. Note: Same issue happens with gparted on the 18.04.1 desktop install USB. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gparted 0.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 13 15:05:13 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash SourcePackage: gparted UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago) mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693 To manage notifications about this bug go to: https://bugs.launchpad.net/gparted/+bug/1808421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884455] Re: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- 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/1884455 Title: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset Status in pulseaudio package in Ubuntu: Invalid Bug description: I use 'zfs' and have /root as its own dataset which is mounted during startup by 'zfs-mount.service'. At one of the latest upgrades, the 'zfsutils-linux' package failed to update because the service 'zfs-mount' service had an issue and could not mount the '/root' dataset because the '/root' directory was not empty (temporary solution was to rename /root and call 'zfs mount' again). Further investigation shows that everytime at startup, the /root directory is created before the 'zfs-mount.service' has a chance to mount the 'root' dataset. The culprit seems to be something pulseaudio related: the content of /root folder after startup is as follows: - root@minighost:~# tree -a /root . ├── .cache └── .config └── pulse └── fe1417537ae0451abdb60c5df28fe825-runtime -> /tmp/pulse-PKdhtXMmr18n 4 directories, 0 files root@minighost:~# - Extra details: - Ubuntu release: - root@minighost:~# lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 - - status of 'zfs-mount.service' is the following: - root@minighost:~# systemctl status zfs-mount ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-06-21 12:56:08 CEST; 6h ago Docs: man:zfs(8) Process: 2062 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 2062 (code=exited, status=1/FAILURE) Jun 21 12:56:08 minighost systemd[1]: Starting Mount ZFS filesystems... Jun 21 12:56:08 minighost zfs[2062]: cannot mount '/root': directory is not empty Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Jun 21 12:56:08 minighost systemd[1]: Failed to start Mount ZFS filesystems. root@minighost:~# - - software versions: - root@minighost:~# apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.3 Candidate: 1:13.99.1-1ubuntu3.3 Version table: *** 1:13.99.1-1ubuntu3.3 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@minighost:~# apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.1 Candidate: 0.8.3-1ubuntu12.1 Version table: *** 0.8.3-1ubuntu12.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dumi 2419 F pulseaudio CasperMD5CheckResult: skip Date: Sun Jun 21 19:17:20 2020 InstallationDate: Installed on 2018-09-08 (651 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-04-24 (57 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1884455/+subscriptions -- Mailing list:
