[Touch-packages] [Bug 1274857] Re: wi-fi continually fails to connect (after previous success)
Is this still a problem on bionic or later? ** Changed in: network-manager (Ubuntu) Status: Confirmed => Incomplete -- 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/1274857 Title: wi-fi continually fails to connect (after previous success) Status in network-manager package in Ubuntu: Incomplete Bug description: Wi-fi had been working fine, but this morning, nothing doing. syslog shows many instances of: Activation (wlan0/wireless): association took too long, failing activation. Some info which may or may not be relevant: Removing the network and adding it made no difference. Deactivating, then reactivating the hardware wi-fi network switch made no difference. This was happening on two independent wi-fi networks (my hotel and the bluefin office) Rebooting fixed the issue. Closing the laptop did not reliably send it to sleep last night. Two competent Canonical engineers were unable to diagnose the problem. % lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 % uname -a Linux rog-ThinkPad-X220 3.13.0-2-generic #17-Ubuntu SMP Fri Jan 10 12:14:30 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux % lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04) 03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak] 0d:00.0 System peripheral: Ricoh Co Ltd MMC/SD Host Controller (rev 07) % I have attached my syslog starting just before the most recent successful connection until just before I rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1274857/+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 1368147] Re: Lenovo Thinkpad Twist: Mobile Broadbad not working any more
Is this still a problem on bionic or later? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1368147 Title: Lenovo Thinkpad Twist: Mobile Broadbad not working any more Status in network-manager package in Ubuntu: Incomplete Bug description: It seems that something has changed and now the functionality for mobile broadband support got completely lost. I can create a new connection, enteringtheoperator and so on, but I cannot establish a connection. First, I click "Enable Mobile Broadband" in the network manager menu. Then I open the meu again and click the entry for my operator. Then I get a pop-up window saying "Connection activation failed, (32) The connection was not supportedby oFono". I am using Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368147/+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 1867496] [NEW] Thinkpad X220 internal ethernet identified as T520
Public bug reported: This is a very minor bug, only cosmetic in nature, but likely easy to fix. The internal ethernet adapter on my Thinkpad X220 is identified as from the T520 by network-manager. See attached screenshot. This is on an up-to-date bionic system. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "screenshot demonstrating the problem" https://bugs.launchpad.net/bugs/1867496/+attachment/5337120/+files/misidentified-ethernet.png -- 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/1867496 Title: Thinkpad X220 internal ethernet identified as T520 Status in network-manager package in Ubuntu: New Bug description: This is a very minor bug, only cosmetic in nature, but likely easy to fix. The internal ethernet adapter on my Thinkpad X220 is identified as from the T520 by network-manager. See attached screenshot. This is on an up-to-date bionic system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1867496/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
The silence regarding this problem is a bit disconcerting. After jumping through many hoops, I managed to resolve this with the help of this answer: https://forum.manjaro.org/t/weird-dns-issue-over-vpn/78092/11 I deleted the /etc/resolv.conf symlink and disabled systemd-resolved as instructed, then rebooted. After start up, NetworkManager re-created a file at /etc/resolv.conf (not a symlink this time). Although I could connect to the Internet, I coulnd't access any website. I inferred some DNS issues and I simply re-enabled systemd-resolved. $ sudo systemctl enable systemd-resolved.service I recreated the symlink pointing /etc/resolv.conf to /run/resolvconf/resolv.conf $ sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf then I rebooted once again. Next time I connected to the VPN, I could access its resources with no further issues. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1586528] Re: Avahi-daemon withdraws address record
I am also seeing this same problem on a Raspberry Pi4 4GB. I purchased the Pi last November and installed from the then-available 2019-09-26-raspbian-buster.zip but routinely keep it updated (apt update / apt upgrade). The Pi was rock solid and did not exhibit any problems until 2020-02-24 when I applied some updates followed by a "sudo reboot" but the boot process did not complete. The Pi runs headless so I don't know whether it never actually completed the shutdown, or failed to reboot. I power- cycled the device and it came back OK. Another set of updates were applied on 2020-03-11 and the subsequent reboot completed without incident so I assumed the earlier problem was a one-off. Then, on 2020-03-14 the Pi froze. Wouldn't respond to pings, ssh or vnc. It is Ethernet-connected but the WiFi interface is active and it did not occur to me to try connecting via WiFi. I just did another power-cycle and then started nosing around through the logs. Which brought me to: Mar 14 12:48:16 iot-hub avahi-daemon[361]: Withdrawing address record for 192.168.132.60 on eth0. Mar 14 12:48:16 iot-hub avahi-daemon[361]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.132.60. Mar 14 12:48:16 iot-hub avahi-daemon[361]: Interface eth0.IPv4 no longer relevant for mDNS. and, from there, to this post. The main reasons I'm adding a comment to this post are (a) as a "me too" as of March 2020, and (b) in case the pattern of the RPi being perfectly OK until 2020-02-24 causes someone to say "ahah!" The updates in question were (from the history log): Upgrade: libpython3.7-minimal:armhf (3.7.3-2, 3.7.3-2+deb10u1), libraspberrypi- bin:armhf (1.20200114-1, 1.20200212-1), libopenjp2-7:armhf (2.3.0-2, 2.3.0-2+deb10u1), rc-gui:armhf (1.34, 1.36), libcom-err2:armhf (1.44.5-1+deb10u2, 1.44.5-1+deb10u3), libcups2:armhf (2.2.10-6+deb10u1, 2.2.10-6+deb10u2), libraspberrypi-dev:armhf (1.20200114-1, 1.20200212-1), libraspberrypi-doc:armhf (1.20200114-1, 1.20200212-1), python3.7-venv:armhf (3.7.3-2, 3.7.3-2+deb10u1), raspberrypi-ui- mods:armhf (1.20200127, 1.20200218), qt5-gtk-platformtheme:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libfm4:armhf (1.3.1-1+rpt12, 1.3.1-1+rpt13), libsystemd0:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), raspi-config:armhf (20200205, 20200207), libfm- modules:armhf (1.3.1-1+rpt12, 1.3.1-1+rpt13), libfm-extra4:armhf (1.3.1-1+rpt12, 1.3.1-1+rpt13), mariadb-common:armhf (1:10.3.17-0+deb10u1, 1:10.3.22-0+deb10u1), binutils:armhf (2.31.1-16+rpi1, 2.31.1-16+rpi2), e2fsprogs:armhf (1.44.5-1+deb10u2, 1.44.5-1+deb10u3), sudo:armhf (1.8.27-1+deb10u1, 1.8.27-1+deb10u2), libqt5dbus5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libqt5sql5-sqlite:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), python3-pil:armhf (5.4.1-2, 5.4.1-2+deb10u1), libpython3.7:armhf (3.7.3-2, 3.7.3-2+deb10u1), python3.7:armhf (3.7.3-2, 3.7.3-2+deb10u1), openssh-sftp-server:armhf (1:7.9p1-10+deb10u1, 1:7.9p1-10+deb10u2), libqt5widgets5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libfm-gtk4:armhf (1.3.1-1+rpt12, 1.3.1-1+rpt13), udev:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), python3.7-dev:armhf (3.7.3-2, 3.7.3-2+deb10u1), binutils-arm-linux-gnueabihf:armhf (2.31.1-16+rpi1, 2.31.1-16+rpi2), libpython3.7-stdlib:armhf (3.7.3-2, 3.7.3-2+deb10u1), libudev1:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), python3.7-minimal:armhf (3.7.3-2, 3.7.3-2+deb10u1), libqt5xml5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libqt5printsupport5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), raspberrypi- kernel:armhf (1.20200114-1, 1.20200212-1), libss2:armhf (1.44.5-1+deb10u2, 1.44.5-1+deb10u3), libqt5concurrent5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libext2fs2:armhf (1.44.5-1+deb10u2, 1.44.5-1+deb10u3), raspberrypi-bootloader:armhf (1.20200114-1, 1.20200212-1), libexif12:armhf (0.6.21-5.1, 0.6.21-5.1+deb10u1), libqt5gui5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libimobiledevice6:armhf (1.2.1~git20181030.92c5462-1, 1.2.1~git20181030.92c5462-2), gldriver- test:armhf (0.4, 0.5), ssh:armhf (1:7.9p1-10+deb10u1, 1:7.9p1-10+deb10u2), systemd-sysv:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), guile-2.2-libs:armhf (2.2.4+1-2, 2.2.4+1-2+deb10u1), realvnc-vnc-server:armhf (6.6.0.41949, 6.7.1.42348), libpython3.7-dev:armhf (3.7.3-2, 3.7.3-2+deb10u1), libpam-systemd:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), libmatroska6v5:armhf (1.4.9-1, 1.4.9-1+deb10u1), systemd:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), libwebkit2gtk-4.0-37:armhf (2.26.3-1~deb10u1+rpi1, 2.26.4-1~deb10u1+rpi1), libqt5core5a:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), piwiz:armhf (0.8, 0.9), libraspberrypi0:armhf (1.20200114-1, 1.20200212-1), openssh-server:armhf (1:7.9p1-10+deb10u1, 1:7.9p1-10+deb10u2), openssh-client:armhf (1:7.9p1-10+deb10u1, 1:7.9p1-10+deb10u2), libmysofa0:armhf (0.6~dfsg0-3, 0.6~dfsg0-3+deb10u1), rpi-chromium-mods:armhf
[Touch-packages] [Bug 1867479] Re: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
*** This bug is a duplicate of bug 1867474 *** https://bugs.launchpad.net/bugs/1867474 Solution given in https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1867474/comments/3 does not resolve issue on my install. I've attached the dmesg ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+attachment/5337110/+files/dmesg -- 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/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: Confirmed Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+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 1867474] Re: PCI/internal sound card not detected
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/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) 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: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+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 1867479] Re: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
*** This bug is a duplicate of bug 1867474 *** https://bugs.launchpad.net/bugs/1867474 Please refer to https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1867474/comments/3 ** This bug has been marked a duplicate of bug 1867474 PCI/internal sound card not detected -- 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/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: Confirmed Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+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 1867479] Re: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
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/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: Confirmed Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+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 1867488] [NEW] APT::Sandbox::Seccomp prevents connect, sendto, socket syscalls on Focal
Public bug reported: # Steps to reproduce: $ lxc launch images:ubuntu/focal fa1 $ lxc shell fa1 root@fa1:~# echo 'APT::Sandbox::Seccomp "true";' > /etc/apt/apt.conf.d/01apt-seccomp root@fa1:~# rm /var/lib/apt/lists/*Release # makes sure we fetch stuff from the network root@fa1:~# apt-get update Hit:1 http://security.ubuntu.com/ubuntu focal-security InRelease Get:2 http://archive.ubuntu.com/ubuntu focal InRelease [255 kB] Hit:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease Get:4 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [976 kB] Get:5 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [8,623 kB] 30% [4 Packages store 0 B] [5 Packages 100 kB/8,623 kB 1%] Seccomp prevented execution of syscall 41 on architecture amd64 Reading package lists... Done E: Method store has died unexpectedly! E: Sub-process store returned an error code (31) This was tested in a container as well as inside a VM, same issue. This used to work with Bionic. # Workaround Fortunately, apt supports manual whitelisting of syscalls. A workaround is to allow 3 more syscalls. root@fa1:~# echo 'APT::Sandbox::Seccomp::Allow "connect,sendto,socket";' >> /etc/apt/apt.conf.d/01apt-seccomp # Additional information root@fa1:~# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 root@fa1:~# uname -a Linux fa1 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@fa1:~# apt-cache policy apt libc-bin apt: Installed: 1.9.10 Candidate: 1.9.10 Version table: *** 1.9.10 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status libc-bin: Installed: 2.31-0ubuntu5 Candidate: 2.31-0ubuntu5 Version table: *** 2.31-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Description changed: # Steps to reproduce: $ lxc launch images:ubuntu/focal fa1 $ lxc shell fa1 root@fa1:~# echo 'APT::Sandbox::Seccomp "true";' > /etc/apt/apt.conf.d/01apt-seccomp root@fa1:~# rm /var/lib/apt/lists/*Release # makes sure we fetch stuff from the network root@fa1:~# apt-get update Hit:1 http://security.ubuntu.com/ubuntu focal-security InRelease Get:2 http://archive.ubuntu.com/ubuntu focal InRelease [255 kB] Hit:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease Get:4 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [976 kB] Get:5 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [8,623 kB] 30% [4 Packages store 0 B] [5 Packages 100 kB/8,623 kB 1%] - Seccomp prevented execution of syscall 41 on architecture amd64 - Reading package lists... Done + Seccomp prevented execution of syscall 41 on architecture amd64 + Reading package lists... Done E: Method store has died unexpectedly! E: Sub-process store returned an error code (31) This was tested in a container as well as inside a VM, same issue. This used to work with Bionic. - # Workaround Fortunately, apt supports manual whitelisting of syscalls. A workaround - is to allow the socket and connect syscalls as simply allowing socket - fails with: + is to allow 3 more syscalls. - Seccomp prevented execution of syscall 42 on architecture - amd64 - - root@fa1:~# echo 'APT::Sandbox::Seccomp::Allow "socket,connect";' >> - /etc/apt/apt.conf.d/01apt-seccomp - + root@fa1:~# echo 'APT::Sandbox::Seccomp::Allow "connect,sendto,socket";' + >> /etc/apt/apt.conf.d/01apt-seccomp # Additional information root@fa1:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@fa1:~# uname -a Linux fa1 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@fa1:~# apt-cache policy apt libc-bin apt: - Installed: 1.9.10 - Candidate: 1.9.10 - Version table: - *** 1.9.10 500 - 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.9.10 + Candidate: 1.9.10 + Version table: + *** 1.9.10 500 + 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status libc-bin: - Installed: 2.31-0ubuntu5 - Candidate: 2.31-0ubuntu5 - Version table: - *** 2.31-0ubuntu5 500 - 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 2.31-0ubuntu5 + Candidate: 2.31-0ubuntu5 + Version table: + *** 2.31-0ubuntu5 500 + 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status ** Summary changed: - APT::Sandbox::Seccomp prevents socket syscall on Focal + APT::Sandbox::Seccomp prevents
[Touch-packages] [Bug 1867474] Re: PCI/internal sound card not detected
enabled the -proposed. Then install the latest kernel (maybe 5.4.0-18), latest linux-firmware and latest pulseaudio, then install alsa-ucm-conf manually, reboot. your audio should work, if not please upload the dmesg. thx. -- 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/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) 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: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+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 1855514] Re: ibus preferences do not show up in search or indicator bar
Thanks for your report! It's not a bug, though. $ cat /usr/share/applications/org.freedesktop.IBus.Setup.desktop | grep '# GNOME' -A 1 # GNOME uses its own "input source" settings instead NotShowIn=GNOME;Unity; IBus is integrated into the GNOME desktop, and normally the UI provided by Settings -> Region & Language is sufficient. Closing. ** Changed in: ibus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1855514 Title: ibus preferences do not show up in search or indicator bar Status in ibus package in Ubuntu: Invalid Bug description: This might be two separate bugs. But I feel like they have the same root, so I reported them as one. Remarks: [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] https://launchpad.net/bugs/1854610 [2] This report might be related to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm not sure. Someone with more technical knowledge should look into this. 1 --- steps to reproduce: 1) Have a fresh ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) press windows key to open all applications 4) type in ibus Actual: 5) ibus settings will not show up Expected: 5) ibus settings show up Workaround: 6) open Software center 7) search for ibus 8) click "launch there" 2 -- steps to reproduce: 1) Have a fresh Ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) Set input method to "ibus" 4) restart Actual: 5) ibus preferences do not show up in the top bar at the indicators Expected 6) "ibus preferences" is visible at the top bar inside the indicators area. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus 1.5.21-1~exp2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 13:10:27 2019 SourcePackage: ibus UpgradeStatus: no upgrade log present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+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 1867479] [NEW] PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
Public bug reported: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: New Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected
[Touch-packages] [Bug 1867474] Re: PCI/internal sound card not detected
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) 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: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+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 1867474] [NEW] PCI/internal sound card not detected
You have been subscribed to a public bug: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) 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: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- PCI/internal sound card not detected https://bugs.launchpad.net/bugs/1867474 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 1866996] Re: apport-retrace can not be used with https mirrors in sources.list
** Description changed:
- Here I collect a couple of issues regarding apport-retrace with "-S
- system".
+ If /etc/apt/sources.list only contains https mirrors (and not a single
+ http:// entry), then apport-retrace fails to determine the default
+ mirror:
- 1. apport-retrace does not work for https mirros in sources.list
- 2. If the sandbox is built successfully the stack-trace of generated does
even contain less info than simply calling "apport-retrace -v -s -R" without
the sandbox.
- 3. I have found fixes / workaround for issue 1. and 2., see the attached
patches, however in the end I'm still not satisfied with the quality of the
results:
+ apport-retrace -v -s -R -S system ./crash/_usr_bin_gnome-shell.1000.crash
+ Ign http://ddebs.ubuntu.com focal InRelease
+ Get:1 http://ppa.launchpad.net/saiarcot895/chromium-dev/ubuntu focal
InRelease [20.8 kB]
+ Get:2 http://ddebs.ubuntu.com focal Release [34.7 kB]
+ Get:3 https://mirror.init7.net/ubuntu focal InRelease [255 kB]
+ Get:4 http://ddebs.ubuntu.com focal Release.gpg [819 B]
+ Get:5 http://ddebs.ubuntu.com focal/main amd64 Packages [526 kB]
+ Get:6 http://ppa.launchpad.net/saiarcot895/chromium-dev/ubuntu focal/main
amd64 Packages [1604 B]
+ Get:7 https://mirror.init7.net/ubuntu focal-updates InRelease [79.7 kB]
+ Get:8 http://ppa.launchpad.net/saiarcot895/chromium-dev/ubuntu focal/main
Translation-en [1084 B]
+ Get:9 https://mirror.init7.net/ubuntu focal-backports InRelease [79.7 kB]
+ Get:10 https://mirror.init7.net/ubuntu focal-security InRelease [79.7 kB]
+ Get:11 https://mirror.init7.net/ubuntu focal/multiverse Sources [175 kB]
+ Get:12 http://ddebs.ubuntu.com focal/universe amd64 Packages [4435 kB]
+ Get:13 https://mirror.init7.net/ubuntu focal/restricted Sources [7032 B]
+ Get:14 https://mirror.init7.net/ubuntu focal/universe Sources [9784 kB]
+ Get:15 http://ddebs.ubuntu.com focal/multiverse amd64 Packages [67.0 kB]
+ Get:16 https://mirror.init7.net/ubuntu focal/main Sources [839 kB]
+ Get:17 https://mirror.init7.net/ubuntu focal/main amd64 Packages [976 kB]
+ Get:18 https://mirror.init7.net/ubuntu focal/main Translation-en [503 kB]
+ Get:19 https://mirror.init7.net/ubuntu focal/main amd64 DEP-11 Metadata [517
kB]
+ Get:20 https://mirror.init7.net/ubuntu focal/main DEP-11 48x48 Icons [93.7
kB]
+ Get:21 https://mirror.init7.net/ubuntu focal/main DEP-11 64x64 Icons [164 kB]
+ Get:22 https://mirror.init7.net/ubuntu focal amd64 Contents (deb) [41.2 MB]
+ Get:23 https://mirror.init7.net/ubuntu focal/restricted amd64 Packages [21.5
kB]
+ Get:24 https://mirror.init7.net/ubuntu focal/restricted Translation-en [6136
B]
+ Get:25 https://mirror.init7.net/ubuntu focal/universe amd64 Packages [8623
kB]
+ Get:26 https://mirror.init7.net/ubuntu focal/universe Translation-en [5154
kB]
+ Get:27 https://mirror.init7.net/ubuntu focal/universe amd64 DEP-11 Metadata
[3619 kB]
+ Get:28 https://mirror.init7.net/ubuntu focal/universe DEP-11 48x48 Icons
[3005 kB]
+ Get:29 https://mirror.init7.net/ubuntu focal/universe DEP-11 64x64 Icons
[7981 kB]
+ Get:30 https://mirror.init7.net/ubuntu focal/multiverse amd64 Packages [145
kB]
+ Get:31 https://mirror.init7.net/ubuntu focal/multiverse Translation-en [105
kB]
+ Get:32 https://mirror.init7.net/ubuntu focal/multiverse amd64 DEP-11 Metadata
[45.0 kB]
+ Get:33 https://mirror.init7.net/ubuntu focal/multiverse DEP-11 48x48 Icons
[17.6 kB]
+ Get:34 https://mirror.init7.net/ubuntu focal/multiverse DEP-11 64x64 Icons
[195 kB]
+ Fetched 88.8 MB in 6s (1341 kB/s)
+ Fetched 0 B in 0s (0 B/s)
+ Extracting downloaded debs...
+ Traceback (most recent call last):
+ File "/usr/bin/apport-retrace", line 322, in
+ sandbox, cache, outdated_msg = apport.sandboxutils.make_sandbox(
+ File "/usr/lib/python3/dist-packages/apport/sandboxutils.py", line 220, in
make_sandbox
+ pkgs = needed_runtime_packages(report, sandbox_dir, pkgmap_cache_dir,
pkg_versions, verbose)
+ File "/usr/lib/python3/dist-packages/apport/sandboxutils.py", line 92, in
needed_runtime_packages
+ pkg = apport.packaging.get_file_package(l, True, pkgmap_cache_dir,
+ File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 490,
in get_file_package
+ return self._search_contents(file, map_cachedir, release, arch)
+ File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 1296,
in _search_contents
+ url = '%s/dists/%s%s/Contents-%s.gz' % (self._get_mirror(), release,
pocket, arch)
+ File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 1252,
in _get_mirror
+ self._mirror =
self._get_primary_mirror_from_apt_sources('/etc/apt/sources.list')
+ File
[Touch-packages] [Bug 1768026] Re: echo message hides cursor
1 for adding the fix to 18.04 LTS. When will it be fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1768026 Title: echo message hides cursor Status in vim: Fix Released Status in vim package in Ubuntu: Confirmed Bug description: https://github.com/w0rp/ale/issues/1536#issuecomment-385056702 upstream bug https://github.com/vim/vim/issues/2612 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:16:35 2018 InstallationDate: Installed on 2017-05-17 (347 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-04-26 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1768026/+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 1850820] Re: idhclient
This bug was fixed in the package isc-dhcp - 4.4.1-2.1ubuntu3
---
isc-dhcp (4.4.1-2.1ubuntu3) focal; urgency=medium
* debian/apparmor/sbin.dhclient: also properly confine /usr/sbin/dhclient
(LP: #1850820)
-- Marc Deslauriers Wed, 11 Mar 2020
09:16:03 -0400
** Changed in: isc-dhcp (Ubuntu Focal)
Status: In Progress => Fix Released
--
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/1850820
Title:
idhclient
Status in isc-dhcp package in Ubuntu:
Fix Released
Status in isc-dhcp source package in Eoan:
New
Status in isc-dhcp source package in Focal:
Fix Released
Bug description:
In eon dhclient is running without confinement
$ ps aux -Z | grep dhclient
unconfined root 1004 0.0 0.1 9604 5796 ?
Ss 16:48 0:00 dhclient
This is because the profile is defined with
/sbin/dhclient flags=(attach_disconnected) {
but the binary is now at
/usr/sbin/dhclient
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1850820/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
Issue also exists on Debian Buster with 5.4 backports kernel and bluez 5.50-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
or a link to the most up-to-date bluez package ... most current version for Ubuntu 18.04 if any Em qui, 12 de mar de 2020 22:09, Daniel van Vugt < daniel.van.v...@canonical.com> escreveu: > ** Changed in: bluez (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1490349 > > Title: > 15:10 and 16.04: bluetoothd "Failed to start discovery: > org.bluez.Error.NotReady" after bluetoothd restarted > > Status in bluez package in Ubuntu: > Invalid > > Bug description: > On 15:10 after the bluetooth service has been stopped and restarted it > is not possible to scan or connect to devices: > > $ sudo systemctl restart bluetooth > > $ bluetoothctl > [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] > [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard > [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse > [bluetooth]# scan on > Failed to start discovery: org.bluez.Error.NotReady > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions > -- 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/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
** Tags removed: utopic vivid
** Tags added: bionic focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Triaged
Status in wpa package in Ubuntu:
Triaged
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+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 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends
** Changed in: hundredpapercuts Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: Add chrome-gnome-shell to ubuntu-desktop recommends Status in One Hundred Papercuts: New Status in chrome-gnome-shell package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Please, consider adding the chrome-gnome-shell package as a recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The chrome-gnome-shell package provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers that is necessary for users to be able to manage GNOME Shell extensions using a extensions.gnome.org website. Since the Shell Extensions support was removed from gnome-software since 3.36 and the replacement Extensions application cannot be used to find and install new extensions, there is not any user friendly way to install new Shell Extensions without having the chrome-gnome-shell package installed. More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+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 1867425] [NEW] Update tracker to 2.3.4 and tracker-miners to 2.3.3
Public bug reported: The 2.3.x branch receives bug fixes only since big, new development now goes to the master branch. tracker https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS NEW in 2.3.4 - 2020-03-10 = * Brown paper bag release, fix NULL check. NEW in 2.3.3 - 2020-03-09 = * Fix race condition during tracker-store shutdown maybe leading to warnings and missed writeback events. * Made fts:offsets stronger against corrupt FTS tables Translations: ja tracker-miners https://gitlab.gnome.org/GNOME/tracker-miners/-/blob/tracker-miners-2.3/NEWS NEW in 2.3.3 - 2020-03-09 = * The secure sandbox for tracker-extract now permits clock_nanosleep() calls, fixing crashes on some systems. * Miners now set nice/scheduler priorities in a way that placates glib. The sched_setscheduler syscall is as a side effect also allowed by the tracker-extract sandbox. Translations: ja NEW in 2.3.2 - 2020-02-18 = * Blocked parsing of image/x-dds image files, which were previously being passed to GStreamer and triggering system lockups for some people * Fixed incorrect MIME type for .raw images, which were previously being passed to GStreamer and triggering system lockups for some people * Improved how the MP3 extractor calculates durations of variable bitrate MP3s, which fixes incorrect durations being shown in GNOME Music. * Fixed a bug in the GStreamer writeback module. * Fix race condition that might leave tracker-miner-fs paused after a writeback operation. Translations: ms ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Tags: focal upgrade-software-version ** Also affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Description changed: - The 2.3.x branch receives bug-fixes only since big, new development now + The 2.3.x branch receives bug fixes only since big, new development now goes to the master branch. tracker https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS NEW in 2.3.4 - 2020-03-10 = - * Brown paper bag release, fix NULL check. + * Brown paper bag release, fix NULL check. NEW in 2.3.3 - 2020-03-09 = - * Fix race condition during tracker-store shutdown maybe leading to - warnings and missed writeback events. - * Made fts:offsets stronger against corrupt FTS tables + * Fix race condition during tracker-store shutdown maybe leading to warnings and missed writeback events. + * Made fts:offsets stronger against corrupt FTS tables Translations: ja - tracker-miners https://gitlab.gnome.org/GNOME/tracker-miners/-/blob/tracker-miners-2.3/NEWS NEW in 2.3.3 - 2020-03-09 = - - * The secure sandbox for tracker-extract now permits clock_nanosleep() calls, - fixing crashes on some systems. - * Miners now set nice/scheduler priorities in a way that placates glib. The - sched_setscheduler syscall is as a side effect also allowed by the - tracker-extract sandbox. + * The secure sandbox for tracker-extract now permits clock_nanosleep() calls, fixing crashes on some systems. + * Miners now set nice/scheduler priorities in a way that placates glib. The sched_setscheduler syscall is as a side effect also allowed by the tracker-extract sandbox. Translations: ja NEW in 2.3.2 - 2020-02-18 = - - * Blocked parsing of image/x-dds image files, which were previously - being passed to GStreamer and triggering system lockups for some people - * Fixed incorrect MIME type for .raw images, which were previously - being passed to GStreamer and triggering system lockups for some people - * Improved how the MP3 extractor calculates durations of variable bitrate - MP3s, which fixes incorrect durations being shown in GNOME Music. - * Fixed a bug in the GStreamer writeback module. - * Fix race condition that might leave tracker-miner-fs paused after a - writeback operation. + * Blocked parsing of image/x-dds image files, which were previously being passed to GStreamer and triggering system lockups for some people + * Fixed incorrect MIME type for .raw images, which were previously being passed to GStreamer and triggering system lockups for some people + * Improved how the MP3 extractor calculates durations of variable bitrate MP3s, which fixes incorrect durations being shown in GNOME Music. + * Fixed a bug in the GStreamer writeback module. + * Fix race condition that might leave tracker-miner-fs paused after a writeback operation. Translations: ms -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1867425 Title: Update tracker to 2.3.4
[Touch-packages] [Bug 1867421] Re: Microsoft Classic IntelliMouse moves way too fast
Upstream fix: https://github.com/systemd/systemd/pull/10880 ** Tags added: fixed-in-systemd-240 fixed-upstream ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867421 Title: Microsoft Classic IntelliMouse moves way too fast Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: Microsoft Classic IntelliMouse moves way too fast to be usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 17:12:25 2020 InstallationDate: Installed on 2019-01-02 (436 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:0823 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060531 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+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 1867421] [NEW] Microsoft Classic IntelliMouse moves way too fast
Public bug reported: Microsoft Classic IntelliMouse moves way too fast to be usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 17:12:25 2020 InstallationDate: Installed on 2019-01-02 (436 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:0823 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060531 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Eoan) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Focal) Importance: Undecided Status: Fix Released ** Tags: amd64 apport-bug bionic fixed-in-systemd-240 fixed-upstream ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867421 Title: Microsoft Classic IntelliMouse moves way too fast Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Bug description: Microsoft Classic IntelliMouse moves way too fast to be usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.39 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 17:12:25 2020 InstallationDate: Installed on 2019-01-02 (436 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:0823 Microsoft Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 10M7CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO
[Touch-packages] [Bug 1867352] Re: Xorg freeze after boot if use xorg.conf generated by nvidia-xconfig
Please reproduce the crash/freeze again, and then on the very next reboot collect a log of the previous boot where it was happening: journalctl -b-1 > prevboot.txt And then attach the file 'prevboot.txt' here. Please also check /var/crash/ for any files and if you find some then follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Incomplete -- 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/1867352 Title: Xorg freeze after boot if use xorg.conf generated by nvidia-xconfig Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: Hello! I have constant X crash if use xorg.conf generated by nvidia-xconfig. Currently my xorg.conf is absent. Only if I have an empty conf file or it is absent I can start X. The problem exists in 19.10 and 20.04 development version Also I have strange messages if I run nvidia-xconfig: $ sudo nvidia-xconfig WARNING: Unable to locate/open X configuration file. Package xorg-server was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-server.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-server' found New X configuration file written to '/etc/X11/xorg.conf' Here is my xorg.conf generated by nvidia: # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 440.64 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 SubSection "Display" Depth 24 EndSubSection EndSection ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.2.1 20200304 (Ubuntu 9.2.1-31ubuntu1) ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 16:44:45 2020 DistUpgraded: 2020-03-13 00:50:36,699 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: I don't know GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 3rd Gen Core processor Graphics Controller [104d:90b7] Subsystem: Sony Corporation GK208M [GeForce GT 735M] [104d:90b7] MachineType: Sony Corporation SVF15A1S9RB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=81c8a442-a191-4c83-b415-ee0f1f2b0b81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus:
[Touch-packages] [Bug 784055] Re: compiz CPU usage increases dramatically when running indicator-multiload
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - compiz CPU usage increases dramatically when running indicator-multiload + CPU usage increases dramatically when running indicator-multiload ** Also affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Confirmed ** Project changed: indicator-multiload => ubuntu ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+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 1867337] Re: even after login the login page was displaying everywhere.
Please run this command (sorry I know you already used ubuntu-bug but it collected info for the wrong package): apport-collect 1867337 Also, if there are any files in /var/crash then please follow: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1867337 Title: even after login the login page was displaying everywhere. Status in gnome-shell package in Ubuntu: Incomplete Bug description: I logged into Ubuntu and the system crashed and the login screen was a frozen screen with login page on it. All the apps were not as responsive as the expected login screen won't go. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 17:20:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa] InstallationDate: Installed on 2020-03-11 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 229.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-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/gnome-shell/+bug/1867337/+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 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends
** Changed in: chrome-gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: Add chrome-gnome-shell to ubuntu-desktop recommends Status in One Hundred Papercuts: New Status in chrome-gnome-shell package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Please, consider adding the chrome-gnome-shell package as a recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The chrome-gnome-shell package provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers that is necessary for users to be able to manage GNOME Shell extensions using a extensions.gnome.org website. Since the Shell Extensions support was removed from gnome-software since 3.36 and the replacement Extensions application cannot be used to find and install new extensions, there is not any user friendly way to install new Shell Extensions without having the chrome-gnome-shell package installed. More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+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 1867304] Re: LG OLED TV screen resolution not properly detected
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1867304 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1867304 Title: LG OLED TV screen resolution not properly detected Status in xorg-server package in Ubuntu: Incomplete Bug description: When I connect my LG OLED B9 TV to my computer, black bars appear at the top and bottom. The desktop won't scale to the full screen. Here's some basic info: Ubuntu 19.10 AMD 560 graphics card LG OLED B9 TV I tried changing the display settings, but the black bars won't go away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1867304/+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 1856884] Re: When I insert or take out my headphones the system doesn't send signal on my headphones, I need to switch by hand.
Thanks. Please also ensure the bug title and description describes the problem you are facing. And to log a new separate bug for each different problem. ** Summary changed: - not proper sound device + When I insert or take out my headphones the system doesn't send signal on my headphones, I need to switch by hand. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1856884 Title: When I insert or take out my headphones the system doesn't send signal on my headphones, I need to switch by hand. Status in pulseaudio package in Ubuntu: New Bug description: when i insert or take out my headphones , the system doesn't send signal on my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1929 F pulseaudio /dev/snd/controlC1: rob1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (326 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (411 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (128 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+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 1525628] Re: tracker needs to be killed on every boot
To update: Per the Gnome team this is finally fixed in version 2.3.2, https://gitlab.gnome.org/GNOME/tracker/issues/95 I cannot verify as as this version is not avialable for any current version of Ubuntu, including Focal. Please update the tracker version in supported channels. ** Bug watch added: gitlab.gnome.org/GNOME/tracker/issues #95 https://gitlab.gnome.org/GNOME/tracker/issues/95 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1525628 Title: tracker needs to be killed on every boot Status in tracker package in Ubuntu: Confirmed Bug description: At every boot, tacker-miner-fs and tracker-extract uses all of the processor and needs to be killed manually for computer to work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tracker 1.6.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 13 13:02:58 2015 InstallationDate: Installed on 2015-04-24 (232 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1525628/+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 1866681] Re: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)
So, I ran `uname -or` on my Ubuntu 18.04, which gave: `5.3.0-40-generic GNU/Linux` I find this strange because it doesn't do it on this edition. The problem is definitely somehow connected to the Ubuntu/Debian layer on top of the kernel, and not the actual kernel itself. I'm certain of this now. -- 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/1866681 Title: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+) Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp- pavilion-dv9000/specs/) built many years ago. Whenever I'm using any distro that's based on Ubuntu which was published from Version 19.04 onwards, I've been having a major issue with the mute button toggling on and off whenever I have something plugged into the audio out jack. I know that it's not the fault of XFCE, because I also use the latest version of Manjaro with XFCE on this same computer, and it works fine. I also know it's not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 6) also on this exact same computer, and it also works fine. Qubes, Mageia, and Fedora 31 also work perfectly fine and don't have this issue. My "lsb-release" is: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.10 DISTRIB_CODENAME=eoan DISTRIB_DESCRIPTION="Ubuntu 19.10" and "apt-cache policy pulseaudio" outputs: pulseaudio: Installed: 1:13.0-1ubuntu1.1 Candidate: 1:13.0-1ubuntu1.1 Version table: *** 1:13.0-1ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages I've uploaded a short video of the problem that I recorded with my phone here: https://www.youtube.com/watch?v=GXaHXQA-5uQ The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, Xubuntu 19.04, and Sparky 5.10 and 2020.02. I've checked pretty much everything I can think of. There's a log for my ALSA help diagnostics results on my current computer (which works properly with 18.04) at: http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829 the result output of lspci is: [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2) 00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3) 00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3) 00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1) 00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1) 00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1) 00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g WLAN (rev 01) 05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] (rev a1) 07:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller 07:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 07:05.2 System peripheral: Ricoh
