[Touch-packages] [Bug 1896371] Re: [ZenBook UX334FL_UX334FL, Realtek ALC294, Speaker, Internal] No sound at all
You may want to try the workaround described here: https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX534 -- 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/1896371 Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Both the internal speaker and the plugged in headphones cannot play any sound. However, when I connected it to the external display device, with the HDMI connection, it sounds good. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuhsinchan 1473 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 16:39:05 2020 InstallationDate: Installed on 2020-08-14 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: 內部音效 - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuhsinchan 1473 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX334FL.303:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896371/+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 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
This bug happens to me in x11, Wayland fixes the glitch. I have i5-8250u ,intel uhd 620 graphics.I had the issue in both ubuntu and pop os -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+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 1896377] Re: My Dell wireless mouse disconnects from USB
** Summary changed: - My Dell wireless mouse stops after a while. + My Dell wireless mouse disconnects from USB ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - My Dell wireless mouse disconnects from USB + My Dell wireless mouse dongle disconnects from USB -- 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/1896377 Title: My Dell wireless mouse dongle disconnects from USB Status in linux package in Ubuntu: Confirmed Bug description: My Dell wireless mouse stops working after a while. Sometimes it does not work at all. I have to unplug dongle and put again to work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 16:17:16 2020 DistUpgraded: 2018-09-02 08:57:59,590 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f9] InstallationDate: Installed on 2017-02-26 (1301 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=80dcea6d-1a75-47ed-ba9d-48393d1219fa ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-02 (749 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0XJGC1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0XJGC1:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896377/+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 1896257] Re: Xorg freeze
Next time a freeze happens, please reboot and then immediately run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Please also tell us if you have any files in /var/crash/ ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze + Screen freeze -- 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/1896257 Title: Screen freeze Status in Ubuntu: Incomplete Bug description: Another freeze will playing videogames. I was playing MotoGP19 via Steam Proton, and the complete operating system froze. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 18 18:02:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-37-generic, x86_64: installed nvidia, 440.100, 5.4.0-45-generic, x86_64: installed nvidia, 440.100, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: No GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: I don't know GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP102 [GeForce GTX 1080 Ti] [1458:3752] InstallationDate: Installed on 2020-04-24 (146 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS GAMING 7 WIFI ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=de8f79b3-6f06-4293-9d8c-ed2a147342a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS GAMING 7 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSGAMING7WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSGAMING7WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS GAMING 7 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1896257/+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 1896385] Re: Xorg freeze
*** This bug is a duplicate of bug 1896257 *** https://bugs.launchpad.net/bugs/1896257 ** This bug has been marked a duplicate of bug 1896257 Xorg freeze -- 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/1896385 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: When I was playing Desperado III in Steam, the game closed and I went back to desktop. I typed this command to try to help you. I think that the problem is Geoclue, that finish the process and next restart the process but I don't know. I haven't got any GPS localization system in my PC. pitx@Pitx-PC:~$ journalctl -e sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 5 threads of 2 processe> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Successfully made thread 13242 of p> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:13:05 Pitx-PC systemd[1]: systemd-hostnamed.service: Succeeded. sep 20 16:13:09 Pitx-PC geoclue[11042]: Service not used for 60 seconds. Shutti> sep 20 16:13:09 Pitx-PC systemd[1]: geoclue.service: Succeeded. sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:13:49 Pitx-PC systemd[1704]: Started Application launched by gnome-sh> sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] Activati> sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps.slice. sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps-org.gnome.Terminal.sl> sep 20 16:13:49 Pitx-PC systemd[1704]: Starting GNOME Terminal Server... sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] Successf> sep 20 16:13:49 Pitx-PC systemd[1704]: Started GNOME Terminal Server. sep 20 16:13:49 Pitx-PC systemd[1704]: Started VTE child process 13515 launched> sep 20 16:13:49 Pitx-PC systemd[1704]: gnome-launched-org.gnome.Terminal.deskto> lines 986-1008/1008 (END) sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 5 threads of 2 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Successfully made thread 13242 of process 13161 owned by '1000' RT at priority 10. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:13:05 Pitx-PC systemd[1]: systemd-hostnamed.service: Succeeded. sep 20 16:13:09 Pitx-PC geoclue[11042]: Service not used for 60 seconds. Shutting down.. sep 20 16:13:09 Pitx-PC systemd[1]: geoclue.service: Succeeded. sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:13:49 Pitx-PC systemd[1704]: Started Application launched by gnome-shell. sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.1031' (uid=1000 pid=13505> sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps.slice. sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps-org.gnome.Terminal.slice. sep 20 16:13:49 Pitx-PC systemd[1704]: Starting GNOME Terminal Server... sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] Successfully activated service 'org.gnome.Terminal' sep 20 16:13:49 Pitx-PC systemd[1704]: Started GNOME Terminal Server. sep 20 16:13:49 Pitx-PC systemd[1704]: Started VTE child process 13515 launched by gnome-terminal-server process 13508. sep 20 16:13:49 Pitx-PC systemd[1704]: gnome-launched-org.gnome.Terminal.desktop-13502.scope: Succeeded. ~ ~ ~ ~ ~ lines 986-1008/1008 (END) sep 20
[Touch-packages] [Bug 1896309] Re: apport-bug xorg
** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1896309 Title: apport-bug xorg Status in Ubuntu: Incomplete Bug description: $ Gtk-Message: 08:56:49.280: Failed to load module "canberra-gtk-module" Gtk-Message: 08:56:49.280: Failed to load module "canberra-gtk-module" Opening in existing browser session ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 08:54:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:0502] InstallationDate: Installed on 2020-09-15 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron N4050 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 02JCHC dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd08/03/2012:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn02JCHC:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N4050 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1896309/+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 1896349] Re: PCI/internal sound card not detected
Please test this: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1892714/comments/46 -- 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/1896349 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 I can select my default audio hardware When I test it, doesn't work. When watching a Youtube video, for example, audio doesn't work as well. Thru the command lspci, this shows up: 00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03) 00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB Controller (rev 03) 00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30) 00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) (rev 30) 00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #0 (rev 30) 00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #1 (rev 30) 00:16.0 Communication controller: Intel Corporation Management Engine Interface (rev 30) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 30) 00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #5 (rev 30) 00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 (rev 30) 00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30) 00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30) 00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30) 00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound Technology Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI Controller (rev 30) 01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 (rev 03) 04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 19:24:38 2020 InstallationDate: Installed on 2020-09-19 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: 02/13/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875C dmi.board.vendor: HP dmi.board.version: 10.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd02/13/2020:svnHP:pnHPENVYLaptop17m-cg0xxx:pvrType1ProductConfigId:rvnHP:rn875C:rvr10.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 17m-cg0xxx dmi.product.sku: 9XM78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896349/+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 1896333] Re: [Dell Inspiron 5548] "Select an audio" menu when user have not even inserted headphone jack.
** Summary changed: - "Select an audio" menu when user have not even inserted headphone jack. + [Dell Inspiron 5548] "Select an audio" menu when user have not even inserted headphone jack. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1896333 Title: [Dell Inspiron 5548] "Select an audio" menu when user have not even inserted headphone jack. Status in pulseaudio package in Ubuntu: Incomplete Bug description: GNOME 3.36.3 | Ubuntu 20.04.1 It has been a month and I have been experiencing this weird behavior. Earphone option like this 3 while unlocking the laptop as if I have inserted earphones. Some details this issue: I have to wait like 10 min or so after the lock of the screen. This will trigger something and when I open the lid or touch mouse pad to unlock, I get earphone options to chooose in the screen as if I have inserted headphone jack. Something is wrong. I want to know why. This didn't used to happen a month ago. I waited a month to report this issue thinking it will get resolved in upcoming updates but sadly no changes so far. I think some Ubuntu's GNOME update might have something to do this. This is my wild guess. But very certain about it. Let me know. Although the issue might seems really small issue but very annoying to go throw this EVERYDAY. I would love to know what is causing this? When its fixed? Is there something wrong on my side? Note: This happens ONLY when I try to unlock the screen after like >10 min or so. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pranav 3554 F pulseaudio /dev/snd/controlC0: pranav 3554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 20:54:36 2020 InstallationDate: Installed on 2020-02-16 (216 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-08 (134 days ago) dmi.bios.date: 05/28/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896333/+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 1896333] Re: "Select an audio" menu when user have not even inserted headphone jack.
Yes, it could record the jack status. And you could also run sudo evtest-->choose headphone event in a terminal, let evtest monitor the jack status. -- 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/1896333 Title: [Dell Inspiron 5548] "Select an audio" menu when user have not even inserted headphone jack. Status in pulseaudio package in Ubuntu: Incomplete Bug description: GNOME 3.36.3 | Ubuntu 20.04.1 It has been a month and I have been experiencing this weird behavior. Earphone option like this 3 while unlocking the laptop as if I have inserted earphones. Some details this issue: I have to wait like 10 min or so after the lock of the screen. This will trigger something and when I open the lid or touch mouse pad to unlock, I get earphone options to chooose in the screen as if I have inserted headphone jack. Something is wrong. I want to know why. This didn't used to happen a month ago. I waited a month to report this issue thinking it will get resolved in upcoming updates but sadly no changes so far. I think some Ubuntu's GNOME update might have something to do this. This is my wild guess. But very certain about it. Let me know. Although the issue might seems really small issue but very annoying to go throw this EVERYDAY. I would love to know what is causing this? When its fixed? Is there something wrong on my side? Note: This happens ONLY when I try to unlock the screen after like >10 min or so. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pranav 3554 F pulseaudio /dev/snd/controlC0: pranav 3554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 20:54:36 2020 InstallationDate: Installed on 2020-02-16 (216 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-08 (134 days ago) dmi.bios.date: 05/28/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896333/+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 1569068] Re: mate-settings-daemon: ERROR: pulse/glib-mainloop.c:407: glib_defer_free: assertion failed: (!e->dead)
The most recent crashes were in 19.04 so consider it fixed. ** Changed in: mate-settings-daemon (Ubuntu) Status: Incomplete => Fix Released ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Fix Released -- 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/1569068 Title: mate-settings-daemon: ERROR: pulse/glib-mainloop.c:407: glib_defer_free: assertion failed: (!e->dead) Status in mate-settings-daemon package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-settings-daemon. This problem was most recently seen with version 1.12.1-2build1, the problem page at https://errors.ubuntu.com/problem/1b3afc018f02173501b79b75651ec747d69300b7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-settings-daemon/+bug/1569068/+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 1896402] Re: comp starts with error
Please explain what kind of problem you are experiencing. If it's just an error message then please run: sudo rm /var/crash/* and reboot. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1896402 Title: comp starts with error Status in Ubuntu: Incomplete Bug description: Computer after start up has to sent an error message. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: i386 CompositorRunning: None Date: Sun Sep 20 16:22:14 2020 DistUpgraded: 2019-10-24 14:09:39,726 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Foxconn International, Inc. 82G33/G31 Express Integrated Graphics Controller [105b:0df7] InstallationDate: Installed on 2019-09-13 (373 days ago) InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) MachineType: OEM OEM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=b408071f-56d9-440d-bdc4-aa1d2ae658b4 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-10-24 (332 days ago) dmi.bios.date: 07/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: G31MX Series dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/07/2008:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jan 3 14:44:05 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1896402/+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 1896395] Re: lid closure behavior unpredictable
Using systemctl status systemd-logind, I see that lid events are no longer being detected. This behavior persists even after restarting the service. This is *not* what is requested in logind.conf, where HandleLidSwitch=suspend and HandleLidSwitchDocked=suspend. -- 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/1896395 Title: lid closure behavior unpredictable Status in systemd package in Ubuntu: New Bug description: in 20.04.01 LTS (release 20.04), suspend on lid closure works for a while, then one day stops working, with no error message in syslog. The event is not even registered. The problem seems to start when the system has been inactive for long enough so that the screen is blanked. systemd: Installed: 245.4-4ubuntu3.2 Candidate: 245.4-4ubuntu3.2 Version table: *** 245.4-4ubuntu3.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages seems similar to bug #1840784, even though no error message is generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896395/+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 1896402] Re: comp starts with error
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1896402 Title: comp starts with error Status in xorg package in Ubuntu: New Bug description: Computer after start up has to sent an error message. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: i386 CompositorRunning: None Date: Sun Sep 20 16:22:14 2020 DistUpgraded: 2019-10-24 14:09:39,726 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Foxconn International, Inc. 82G33/G31 Express Integrated Graphics Controller [105b:0df7] InstallationDate: Installed on 2019-09-13 (373 days ago) InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) MachineType: OEM OEM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=b408071f-56d9-440d-bdc4-aa1d2ae658b4 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-10-24 (332 days ago) dmi.bios.date: 07/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: G31MX Series dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/07/2008:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jan 3 14:44:05 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1896402/+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 1896402] [NEW] comp starts with error
You have been subscribed to a public bug: Computer after start up has to sent an error message. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-117.118-generic 4.15.18 Uname: Linux 4.15.0-117-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: i386 CompositorRunning: None Date: Sun Sep 20 16:22:14 2020 DistUpgraded: 2019-10-24 14:09:39,726 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Foxconn International, Inc. 82G33/G31 Express Integrated Graphics Controller [105b:0df7] InstallationDate: Installed on 2019-09-13 (373 days ago) InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) MachineType: OEM OEM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-117-generic root=UUID=b408071f-56d9-440d-bdc4-aa1d2ae658b4 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-10-24 (332 days ago) dmi.bios.date: 07/07/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: G31MX Series dmi.board.vendor: Foxconn dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/07/2008:svnOEM:pnOEM:pvrOEM:rvnFoxconn:rnG31MXSeries:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jan 3 14:44:05 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- comp starts with error https://bugs.launchpad.net/bugs/1896402 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1896395] [NEW] lid closure behavior unpredictable
Public bug reported: in 20.04.01 LTS (release 20.04), suspend on lid closure works for a while, then one day stops working, with no error message in syslog. The event is not even registered. The problem seems to start when the system has been inactive for long enough so that the screen is blanked. systemd: Installed: 245.4-4ubuntu3.2 Candidate: 245.4-4ubuntu3.2 Version table: *** 245.4-4ubuntu3.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages seems similar to bug #1840784, even though no error message is generated. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1896395 Title: lid closure behavior unpredictable Status in systemd package in Ubuntu: New Bug description: in 20.04.01 LTS (release 20.04), suspend on lid closure works for a while, then one day stops working, with no error message in syslog. The event is not even registered. The problem seems to start when the system has been inactive for long enough so that the screen is blanked. systemd: Installed: 245.4-4ubuntu3.2 Candidate: 245.4-4ubuntu3.2 Version table: *** 245.4-4ubuntu3.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages seems similar to bug #1840784, even though no error message is generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896395/+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 1891016] Re: [Keyboard Layouts] No actual keyboard layouts for many languages
Update regarding keyboard layouts. [Ubuntu 20.04.01] I noticed relevant keyboard layouts available now but i couldn't track versions or updates. I guess this may or may not applicable to other languages. However there is still an issue; even newly appeared keyboard layouts are correct and working properly but when click each layouts 'show keyboard layout' eye icon then it still display english characters and not the particular language own characters. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1891016 Title: [Keyboard Layouts] No actual keyboard layouts for many languages Status in console-setup package in Ubuntu: New Bug description: Ubuntu 20.4.1 LTS gsettings set org.gnome.desktop.input-sources show-all-sources true (done) On ubuntu, proper keyboard layouts not available for many languages. Below few examples - Chinese (Available layouts: Chinese, Hanyu Pinyin(altgr) - Sinhala (Available layouts: US, with sinhala letters, Sinhala (phonetic) and many other languages According above two examples, it's better to not add above mentioned layouts because no useful at all. See the windows 10, it has exact proper keyboard layouts for nearly all popular languages. Review them and implement the same for ubuntu Furthermore, there're huge amount of keyboard layouts available with english characters for many languages.(eg: japanese, thai and more) it's better remove them and basically duplicate with english keyboard layouts (or you may able to merge into english keyboards list if necessary) Read the conversation as well https://answers.launchpad.net/ubuntu/+question/692310 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1891016/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
I use Ubuntu 20.04.1, and I have the same problem. I confirm this bug. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1896385] [NEW] Xorg freeze
Public bug reported: When I was playing Desperado III in Steam, the game closed and I went back to desktop. I typed this command to try to help you. I think that the problem is Geoclue, that finish the process and next restart the process but I don't know. I haven't got any GPS localization system in my PC. pitx@Pitx-PC:~$ journalctl -e sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 5 threads of 2 processe> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Successfully made thread 13242 of p> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:13:05 Pitx-PC systemd[1]: systemd-hostnamed.service: Succeeded. sep 20 16:13:09 Pitx-PC geoclue[11042]: Service not used for 60 seconds. Shutti> sep 20 16:13:09 Pitx-PC systemd[1]: geoclue.service: Succeeded. sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processe> sep 20 16:13:49 Pitx-PC systemd[1704]: Started Application launched by gnome-sh> sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] Activati> sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps.slice. sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps-org.gnome.Terminal.sl> sep 20 16:13:49 Pitx-PC systemd[1704]: Starting GNOME Terminal Server... sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] Successf> sep 20 16:13:49 Pitx-PC systemd[1704]: Started GNOME Terminal Server. sep 20 16:13:49 Pitx-PC systemd[1704]: Started VTE child process 13515 launched> sep 20 16:13:49 Pitx-PC systemd[1704]: gnome-launched-org.gnome.Terminal.deskto> lines 986-1008/1008 (END) sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 5 threads of 2 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Successfully made thread 13242 of process 13161 owned by '1000' RT at priority 10. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:39 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:13:05 Pitx-PC systemd[1]: systemd-hostnamed.service: Succeeded. sep 20 16:13:09 Pitx-PC geoclue[11042]: Service not used for 60 seconds. Shutting down.. sep 20 16:13:09 Pitx-PC systemd[1]: geoclue.service: Succeeded. sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:13:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:13:49 Pitx-PC systemd[1704]: Started Application launched by gnome-shell. sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.1031' (uid=1000 pid=13505> sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps.slice. sep 20 16:13:49 Pitx-PC systemd[1704]: Created slice apps-org.gnome.Terminal.slice. sep 20 16:13:49 Pitx-PC systemd[1704]: Starting GNOME Terminal Server... sep 20 16:13:49 Pitx-PC dbus-daemon[1716]: [session uid=1000 pid=1716] Successfully activated service 'org.gnome.Terminal' sep 20 16:13:49 Pitx-PC systemd[1704]: Started GNOME Terminal Server. sep 20 16:13:49 Pitx-PC systemd[1704]: Started VTE child process 13515 launched by gnome-terminal-server process 13508. sep 20 16:13:49 Pitx-PC systemd[1704]: gnome-launched-org.gnome.Terminal.desktop-13502.scope: Succeeded. ~ ~ ~ ~ ~ lines 986-1008/1008 (END) sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 5 threads of 2 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Successfully made thread 13242 of process 13161 owned by '1000' RT at priority 10. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]: Supervising 6 threads of 3 processes of 2 users. sep 20 16:12:38 Pitx-PC rtkit-daemon[1257]:
[Touch-packages] [Bug 1569068] Re: mate-settings-daemon: ERROR: pulse/glib-mainloop.c:407: glib_defer_free: assertion failed: (!e->dead)
** Changed in: mate-settings-daemon (Ubuntu) Status: New => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1569068 Title: mate-settings-daemon: ERROR: pulse/glib-mainloop.c:407: glib_defer_free: assertion failed: (!e->dead) Status in mate-settings-daemon package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-settings-daemon. This problem was most recently seen with version 1.12.1-2build1, the problem page at https://errors.ubuntu.com/problem/1b3afc018f02173501b79b75651ec747d69300b7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-settings-daemon/+bug/1569068/+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 1896377] [NEW] My Dell wireless mouse stops after a while.
Public bug reported: My Dell wireless mouse stops working after a while. Sometimes it does not work at all. I have to unplug dongle and put again to work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 16:17:16 2020 DistUpgraded: 2018-09-02 08:57:59,590 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f9] InstallationDate: Installed on 2017-02-26 (1301 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=80dcea6d-1a75-47ed-ba9d-48393d1219fa ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-02 (749 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0XJGC1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0XJGC1:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1896377 Title: My Dell wireless mouse stops after a while. Status in xorg package in Ubuntu: New Bug description: My Dell wireless mouse stops working after a while. Sometimes it does not work at all. I have to unplug dongle and put again to work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 16:17:16 2020 DistUpgraded: 2018-09-02 08:57:59,590 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f9] InstallationDate: Installed on 2017-02-26 (1301 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=80dcea6d-1a75-47ed-ba9d-48393d1219fa ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-02 (749 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0XJGC1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn0XJGC1:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A
[Touch-packages] [Bug 896688] Re: avahi provides incorrect IP address to pulseaudio
Yes. This issue seems to be limited to Airport devices for me too. While they are quite old now, any chance this incompatibility can be resolved in Avahi? Correct resolution is helpful to access a Time Capsule's network drive. Anything we can do to help debug and test? Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/896688 Title: avahi provides incorrect IP address to pulseaudio Status in avahi package in Ubuntu: Confirmed Bug description: Ubuntu 10.04 Packages avahi-daemon 0.6.25-1ubuntu6.2 I'm using an airport express with pulse audio and I believe avahi- daemon is providing/resolving the wrong IP address to pulse audio. Using the following command, avahi-browse -r _raop._tcp I get: + eth1 IPv4 00254B09A042@Base Station 09a043 AirTunes Remote Audio local = eth1 IPv4 00254B09A042@Base Station 09a043 AirTunes Remote Audio local hostname = [Base-Station-09a043.local] address = [169.254.135.173] port = [5000] txt = ["sf=0x5" "fv=74200.9" "am=AirPort4,107" "vs=101.9" "tp=TCP,UDP" "vn=65537" "pw=false" "ss=16" "sr=44100" "da=true" "sv=false" "et=0,1" "ek=1" "cn=0,1" "ch=2" "txtvers=1"] where the address (169.254.135.173) is incorrect. It should be a 192.168.1.X address which is already assigned to the APEX from the router using DHCP. I've had to specify the correct IP address to pulseaudio when I manually load the module_raop_sink module in order for it to properly stream music to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/896688/+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 1887919] Re: autopkgtest failure with libselinux 3.1
This bug was fixed in the package glibc - 2.32-0ubuntu3 --- glibc (2.32-0ubuntu3) groovy; urgency=medium * Fix cross-toolchain-base. Use ${Depends:foo=foo} magic to not create cross packages for libnss-nis*, rpcsvc-proto, libtirpc-dev and libnsl-dev (LP: #1895632) * XFAIL time/tst-cpuclock1 (LP: #1895687) glibc (2.32-0ubuntu2) groovy; urgency=medium * Merge from Debian unstable * Refresh patches * debian/watch: Use HTTPS and download xz-compressed tarball * debian/watch: Use upstream's signing key to verify the tarball * Don't build and ship libnsl.a and Sun RPC static library and header files * XFAIL stdlib/tst-getrandom (LP: #1891403) * debian/symbols.wildcards: Update versions * Make libc-dev depend on rpcsvc-proto and libtirpc-dev. They replace development files for the Sun RPC library removed in glibc 32. * Make libc-dev depend on libnsl-dev. It replaces the development files for the new libnsl library replacing the one shipped by glibc. * Don't check symbols of libnss_nis.so and libnss_nisplus.so libraries. They are not shipped in glibc 2.32 * Depend on libnss-nis and libnss-nisplus shipping the libraries dropped in 2.32 * debian/patches/git-updates.diff: update from upstream stable branch: - x86-64: Fix FMA4 detection in ifunc * debian/testsuite-xfail-debian.mk: XFAIL unsupported tests failing in autopkgtest glibc (2.31-3) unstable; urgency=medium [ Aurelien Jarno ] * debian/control.in/libc: add a Breaks: against openarena (<< 0.8.8+dfsg-4~) due to bug#966150. * debian/control.in/libc: add a Breaks: against ioquake3 (<< 1.36+u20200211.f2c61c1~dfsg-2~) as previous versions are not correctly linked with libm. * debian/patches/git-updates.diff: update from upstream stable branch: - Fix an infinite loop in the iconv program (CVE-2016-10228). Closes: #856503. - debian/patches/any/submitted-selinux-deprecations.diff: upstreamed. - debian/patches/x32/submitted-fix-nptl-setgroups-x32.diff: upstreamed. * debian/rules.d/build.mk: install in the multiarch path. Closes: #962457. [ Samuel Thibault ] * debian/libc0.3.symbols.hurd-i386: Fix dependency of __errno_location and __h_errno_location symbols in libpthread. * patches/hurd-i386/unsubmitted-sbrk-_end.diff: Fix _end symbol appearance by reworking sbrk. * patches/hurd-i386/unsubmitted-sched_sets.diff: Add sched_set/getscheduler. * patches/hurd-i386/git-pthread_atfork-hidden.diff: Hide pthread_atfork symbols imported to applications, to avoid leaking them. glibc (2.31-2ubuntu1) groovy; urgency=medium [ Michael Hudson-Doyle ] * Mark tst-getpw as XFAIL on arm64. (LP: #1869364) [ Balint Reczey ] * Merge from Debian unstable - debian/patches/any/submitted-selinux-deprecations.diff: proposed patch to ignore the selinux deprecations introduced in libselinux (>= 3.1), fixing an FTBFS. (LP: #1887919) Remaining changes: - Enable libc6{,-dev}-armel on armhf and libc6{-dev}-armhf on armel. - Heavily mangle the way we do service restarting on major upgrades. - Build amd64 with -O3, and build ppc64 variants (both 64-bit and 32-bit) with -O3 -fno-tree-vectorize. - Build generic i386 flavour with -mno-tls-direct-seg-refs for Xen. - Drop the libc6-xen flavour, as the above change covers Xen's needs. - Enable systemtap support, which is currently disabled in Debian. - Don't build libc-l10n, its contents get stripped for language-packs. - Drop libc-bin manpages Recommends to Suggests to keep it in standard. - Revert dropping the ldconfig wrapper, as we still have a lot of packages that don't ship a trigger but instead call in postinst. - Use DH_COMPAT=8 for dh_strip to fix debug sections for valgrind. - Mangle locales package to support Ubuntu language packs seamlessly. - Relax some expected test failures for our infrastructure's quirks. - Let nptl/tst-stack4 fail, as it's been racing on several architectures. - Copy the fully conditionalized x86 variant for math-vector-fortran.h to /usr/include/finclude. On all architectures. - Backport x86 CET patches from the trunk. - Ship arm64 variant with LSE support in libc6-lse - debian/sysdeps/{amd64/i386/x32}.mk: Enable Intel Control Flow Dropped changes: - Build i386 variants as -march=i686 - debian/patches/git-updates.diff: update from upstream stable branch. * debian/gbp.conf: Add initial configuration * debian/debhelper.in/libc.preinst: Fix setting LDCONFIG_NOTRIGGER (LP: #1889190) * Build-depend again on g++-10-multilib on armel and armhf which were lost in the merge (LP: #1889069) * debian/control.in/main: Add Vcs-* pointing to Ubuntu packaging repository * Don't handle false positive stringop-overflow warnings as errors on ppc64el * Fall back to calling nanosleep syscall when __clock_nanosleep returns EINVAL (LP: #1871240) *
[Touch-packages] [Bug 1896372] [NEW] systemd (sbin/init/ splash) consumes 12% CPU and doesn't stop
Public bug reported: Right after login, the process systemd (sbin/init/ splash), which is run by root, consumes 12% CPU and doesn't stop. The CPU fan is always on for that reason. That doesn't happen in Focal on the same laptop, which has both Focal and Groovy, and they both share the same /home partition. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Sep 20 10:50:27 2020 InstallationDate: Installed on 2020-09-16 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0461:4e57 Primax Electronics, Ltd HID compliant device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20LTS01800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=301ac90f-9a29-425d-9b75-b6b2a43bf00a ro quiet splash SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET60W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LTS01800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.37 dmi.modalias: dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:br1.37:efr1.37:svnLENOVO:pn20LTS01800:pvrThinkPadL480:rvnLENOVO:rn20LTS01800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LTS01800 dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session -- 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/1896372 Title: systemd (sbin/init/ splash) consumes 12% CPU and doesn't stop Status in systemd package in Ubuntu: New Bug description: Right after login, the process systemd (sbin/init/ splash), which is run by root, consumes 12% CPU and doesn't stop. The CPU fan is always on for that reason. That doesn't happen in Focal on the same laptop, which has both Focal and Groovy, and they both share the same /home partition. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Sep 20 10:50:27 2020 InstallationDate: Installed on 2020-09-16 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0461:4e57 Primax Electronics, Ltd HID compliant device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20LTS01800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=301ac90f-9a29-425d-9b75-b6b2a43bf00a ro quiet splash SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET60W (1.37 )
[Touch-packages] [Bug 1896371] [NEW] [ZenBook UX334FL_UX334FL, Realtek ALC294, Speaker, Internal] No sound at all
Public bug reported: Both the internal speaker and the plugged in headphones cannot play any sound. However, when I connected it to the external display device, with the HDMI connection, it sounds good. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuhsinchan 1473 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 16:39:05 2020 InstallationDate: Installed on 2020-08-14 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: 內部音效 - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuhsinchan 1473 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX334FL.303:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** 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/1896371 Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Both the internal speaker and the plugged in headphones cannot play any sound. However, when I connected it to the external display device, with the HDMI connection, it sounds good. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuhsinchan 1473 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 16:39:05 2020 InstallationDate: Installed on 2020-08-14 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: 內部音效 - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuhsinchan 1473 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX334FL.303:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896371/+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 115016] Re: man page of ps is incomplete
While it took some time, DRS and TRS are now included in the list of fields in the manpage in Ubuntu 16.04 and later. (http://manpages.ubuntu.com/manpages/xenial/en/man1/ps.1.html) ** Changed in: procps (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/115016 Title: man page of ps is incomplete Status in procps package in Ubuntu: Fix Released Bug description: Binary package hint: procps ps axv displays (including others) the following fields: DRS, TRS while the man page of ps describes most of the fields displayed (e.g. RSS, TIME) , the description of DRS and TRS is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/115016/+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 772121] Re: typo in pam_tally manpage
"Don't use .fail_locktime filed in /var/log/faillog for this user." is still present in 1.3.1-5ubuntu4 on Ubuntu 20.04 (http://manpages.ubuntu.com/manpages/focal/en/man8/pam_tally.8.html) ** Tags added: bonic focal xenial ** Tags removed: bonic ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/772121 Title: typo in pam_tally manpage Status in pam package in Ubuntu: Confirmed Status in pam package in Debian: New Bug description: The pam_tally manpage says "filed" where it should say "field". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/772121/+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