[Desktop-packages] [Bug 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
Let us see if the HDMI sound card or analogue sound card introduced this problem, please edit /etc/modprobe.d/alsa-base.conf, add "options snd- hda-intel enable=0,1", reboot, this will disable the hdmi audio sound card (please check if the hdmi sound card is disabled successfully by pacmd list-cards). If the hdmi audio is disabled, please see if the problem still happens or not. If the problem still happens, please change enable=0,1 to enable=1,0, this will disable analog sound card, and let us see if the problem happens or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 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.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0: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/1881432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866923] Re: Wifi connection says it's connected but this is not true after the computer goes into a sleep status
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1866923 Title: Wifi connection says it's connected but this is not true after the computer goes into a sleep status Status in network-manager package in Ubuntu: Expired Bug description: The wifi is connected and working correctly when powered on, however when I close the laptop lid, which I think puts it to sleep, and then reopen it, it says it's connected according to the icon but this is not true. A workaround is turning on Airplane mode and then switching it back on again. It then reconnects and is then fine again. Unless I close the lid and then the process repeats again. I guess this is to do with the wifi driver but I don't know what package it is so I just picked network-manager, sorry - I'm trying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 19:29:03 2020 InstallationDate: Installed on 2020-03-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.68.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.68.0/24 dev wlp1s0 proto kernel scope link src 192.168.68.18 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1866923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881458] [NEW] Playback aborts when a download is started, printing "server does not support seeking"
Public bug reported: Whenever heavy traffic starts on my network, Rhythmbox will abruptly stop playing audio streams. The traffic in question may be local data transfer or (mostly large) downloads. The same happens to local audio streams managed by pulseaudio. A data transfer starts and the stream very much immediately cuts out. Typically, rhythmbox will pops up a dialog saying "server does not support seeking". I can usually resume playback but during longer data transfers/downloads, it will frequently cut out again. I have tried replacing the onboard audio chip with a discrete ASUS DX card. This does not make any difference. What does work is manually restricting download speeds using a download manager. However,, not all network traffic is controlled by such a manager. Something trivial - say, installing a firefox or a gnome-shell plug-in - has been enough for an audio stream to die instantly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 05:06:56 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-04-05 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Description changed: Whenever heavy traffic starts on my network, Rhythmbox will abruptly stop playing audio streams. The traffic in question may be local data transfer or (mostly large) downloads. The same happens to local audio streams managed by pulseaudio. A data transfer starts and the stream very much immediately cuts out. Typically, rhythmbox will pops up a dialog saying "server does not support seeking". I can usually resume playback but during longer data transfers/downloads, it will frequently cut out again. I have tried replacing the onboard audio chip with a discrete ASUS DX card. This does not make any difference. What does work is manually restricting download speeds using a download manager. However,, not all network traffic is controlled by such a - manager. Something trivial like installing a firefox or a gnome-shell - plug-in can be enough to interrupt playback. + manager. Something trivial - say, installing a firefox or a gnome-shell + plug-in - has been enough for an audio stream to die instantly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 05:06:56 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-04-05 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1881458 Title: Playback aborts when a download is started, printing "server does not support seeking" Status in rhythmbox package in Ubuntu: New Bug description: Whenever heavy traffic starts on my network, Rhythmbox will abruptly stop playing audio streams. The traffic in question may be local data transfer or (mostly large) downloads. The same happens to local audio streams managed by pulseaudio. A data transfer starts and the stream very much immediately cuts out. Typically, rhythmbox will pops up a dialog saying "server does not support seeking". I can usually resume playback but during longer data transfers/downloads, it will frequently cut out again. I have tried replacing the onboard audio chip with a discrete ASUS DX card. This does not make any difference. What does work is manually restricting download speeds using a download manager. However,, not all network traffic is controlled by such a manager. Something trivial - say, installing a firefox or a gnome-shell plug-in - has been enough for an audio stream to die instantly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun
[Desktop-packages] [Bug 1881453] Re: Screen corruption on resize (Android Studio start screen)
** Attachment added: "Captura de pantalla de 2020-05-31 04-40-56.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881453/+attachment/5378936/+files/Captura%20de%20pantalla%20de%202020-05-31%2004-40-56.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1881453 Title: Screen corruption on resize (Android Studio start screen) Status in xorg package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) (not installed from software center) Android Studio 4.0 Build #AI-193.6911.18.40.6514223, built on May 20, 2020 Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Linux 5.4.0-33-generic GC: ParNew, ConcurrentMarkSweep Memory: 1981M Cores: 8 Registry: ide.new.welcome.screen.force=true Non-Bundled Plugins: 3) It should resize without problems 4) Resizing the window corrupts the image ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/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: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 04:41:37 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:380a] Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b] InstallationDate: Installed on 2020-04-23 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 5986:0670 Acer, Inc Lenovo EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=5b998715-8d22-4261-a707-c6958e6eeb81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN63WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN63WW:bd06/14/2018:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881453] [NEW] Screen corruption on resize (Android Studio start screen)
Public bug reported: 1) Description:Ubuntu 20.04 LTS Release:20.04 2) (not installed from software center) Android Studio 4.0 Build #AI-193.6911.18.40.6514223, built on May 20, 2020 Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Linux 5.4.0-33-generic GC: ParNew, ConcurrentMarkSweep Memory: 1981M Cores: 8 Registry: ide.new.welcome.screen.force=true Non-Bundled Plugins: 3) It should resize without problems 4) Resizing the window corrupts the image ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/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: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 04:41:37 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:380a] Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b] InstallationDate: Installed on 2020-04-23 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 5986:0670 Acer, Inc Lenovo EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=5b998715-8d22-4261-a707-c6958e6eeb81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN63WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN63WW:bd06/14/2018:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1881453 Title: Screen corruption on resize (Android Studio start screen) Status in xorg package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) (not installed from software center) Android Studio 4.0 Build #AI-193.6911.18.40.6514223, built on May 20, 2020 Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Linux 5.4.0-33-generic GC: ParNew, ConcurrentMarkSweep Memory: 1981M Cores: 8 Registry: ide.new.welcome.screen.force=true Non-Bundled Plugins: 3) It should resize without problems 4) Resizing the window corrupts the image ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume
[Desktop-packages] [Bug 1881435] Re: Xorg freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1881435 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Screen freezes randomly. Keyboard and mouse do not work at that time. I am not able to ssh to the computer or access tty. I am able to do only a hard reset. I tried some troubleshooting myself, but with my novice expertise with ubuntu. The freeze is more or less random. But it is possibly more frequent when running a video, like a youtube video in a browser. Freeze is more frequenty when going full screen with a video, a VM machine or a remote desktop through vnc4server. 1. Tried removing some software like chrome, dropbox, virtualbox, etc. That did not help. 2. Tried reverting back to an older version of Ubuntu, like 16.04 with a 4.15 kernel. That did not help either. 3. Tried other distros like Mint and Fedora. Still had problem. 4. Tried running with NVidia driver and xserver-xorg. The problem occured with both. 5. Tried NVidia as well as Integrated Intel graphics cards. Problem occured in both. 6. Tried all the suggestions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 that were applicable. None of the suggestions helped. 7. Finally tried Windows 7 and there was no problem. Tested for 12 hours and experienced no crash/freeze with youtube running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 12:36:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2651] InstallationDate: Installed on 2020-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series 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-33-generic root=UUID=4b614f0e-95f5-4cc7-8157-bf617c9b1571 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 1881435] [NEW] Xorg freeze
You have been subscribed to a public bug: Screen freezes randomly. Keyboard and mouse do not work at that time. I am not able to ssh to the computer or access tty. I am able to do only a hard reset. I tried some troubleshooting myself, but with my novice expertise with ubuntu. The freeze is more or less random. But it is possibly more frequent when running a video, like a youtube video in a browser. Freeze is more frequenty when going full screen with a video, a VM machine or a remote desktop through vnc4server. 1. Tried removing some software like chrome, dropbox, virtualbox, etc. That did not help. 2. Tried reverting back to an older version of Ubuntu, like 16.04 with a 4.15 kernel. That did not help either. 3. Tried other distros like Mint and Fedora. Still had problem. 4. Tried running with NVidia driver and xserver-xorg. The problem occured with both. 5. Tried NVidia as well as Integrated Intel graphics cards. Problem occured in both. 6. Tried all the suggestions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 that were applicable. None of the suggestions helped. 7. Finally tried Windows 7 and there was no problem. Tested for 12 hours and experienced no crash/freeze with youtube running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 12:36:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2651] InstallationDate: Installed on 2020-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series 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-33-generic root=UUID=4b614f0e-95f5-4cc7-8157-bf617c9b1571 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/1881435 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1628925] Re: gvfsd[1722]: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount()
No explanation on why is invalid. Also Can't (do not want to) use the "dirty" solution provided in https://askubuntu.com/questions/883355/disabling-gvfs-directory-monitoring-on-specific-share. system: 4.15.0-101-generic #102~16.04.1-Ubuntu SMP Mon May 11 11:38:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (updated) cinnamon desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1628925 Title: gvfsd[1722]: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount() Status in gvfs package in Ubuntu: Invalid Bug description: From journalctl: oem@u64:~$ journalctl | grep gvfsd Sep 29 12:52:29 u64 gvfsd[1722]: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Failed to retrieve share list from server: Connection refused Sep 29 12:52:29 u64 gvfsd-network[3760]: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted This is met on a single desktop with a gnome-shell session & a default yakkety 64 installation (but there is no remote connection nor network) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gvfs 1.28.2-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 29 15:19:21 2016 SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881380] Re: fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB UPEK reader
** Bug watch added: Red Hat Bugzilla #1832229 https://bugzilla.redhat.com/show_bug.cgi?id=1832229 ** Also affects: fprintd via https://bugzilla.redhat.com/show_bug.cgi?id=1832229 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1881380 Title: fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB UPEK reader Status in fprintd: Unknown Status in fprintd package in Ubuntu: New Bug description: The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It was working fine with ubuntu 16.04 and 18.04. lsusb shows: 0483:2016 STMicroelectronics Fingerprint Reader user@xubuntu:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: transfer timed out user@xubuntu:~$ fprintd-list user found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 User user has no fingers enrolled for UPEK TouchStrip. This bug is probably the same as: https://bugzilla.redhat.com/show_bug.cgi?id=1832229 To manage notifications about this bug go to: https://bugs.launchpad.net/fprintd/+bug/1881380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working
Reproduced on Ubuntu 20.04 with Intel Corporation Wireless 3165, as also mentioned in this comment - https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1859308/comments/14 with the same message, but with disabled buttons "Apply Changes" and "Revert". Please check this link for issue details - https://ubuntuforums.org/showthread.php?t=2443894=13959817=1 Host machine - Dell Inspiron 7559, multiboot. Details: - Kernel version(`uname -r`): 5.4.0-31-generic - OS: Ubuntu 20.04 LTS Desktop - Wifi card - Intel 3165AC + BT4.2 [802.11ac + Bluetooth 4.2, Dual Band 2. 4&5 GHz, 1x1] @osomon(Olivier Tilloy): Will the fix of this bug: 1) allow to use some of manual installed compatible(non-trigerring "...not working" message) driver*? Or 2) just enable "Apply changes" button(see this screen for details - https://imgur.com/7ILFptF and the issue - https://ubuntuforums.org/showthread.php?t=2443894=13959817=1)? *eg: of different from default shipped driver version due to some relatively-old-hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1859308 Title: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-drivers-common source package in Groovy: Confirmed Bug description: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software-properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? EDIT: bug confirmed as affecting the following Intel wireless adapter cards, and assumedly more to come: Intel Wi-Fi 6 AX200 Intel Dual Band Wireless-AC 3165 Intel Dual Band Wireless-AC 7260 Intel Dual Band Wireless-AC 8260 Intel Wireless-AC 9260 Also for reference here are the specs of Intel adapter cards: ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1859308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881437] [NEW] IBus right click on system tray shows in top left corner hindering screen edges on KDE desktop
Public bug reported: Right-clicking IBus on system tray shows options on the top left corner of the desktop taking up space and hindering screen edges to be executed on KDE desktop. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: kde -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1881437 Title: IBus right click on system tray shows in top left corner hindering screen edges on KDE desktop Status in ibus package in Ubuntu: New Bug description: Right-clicking IBus on system tray shows options on the top left corner of the desktop taking up space and hindering screen edges to be executed on KDE desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1881437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881434] [NEW] PCI/internal sound card not detected
Public bug reported: In my PC is a Intel Corporation Device 2284 (rev 35). When I open the sound preferences, I only see a dummy output. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat May 30 22:38:22 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2019-02-13 (471 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 0M08DC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1881434 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: In my PC is a Intel Corporation Device 2284 (rev 35). When I open the sound preferences, I only see a dummy output. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat May 30 22:38:22 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2019-02-13 (471 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.0.9 dmi.board.name: 0M08DC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.0.9:bd06/02/2016:svnDellInc.:pnInspiron15-3552:pvr4.0.9:rvnDellInc.:rn0M08DC:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 15-3552 dmi.product.version: 4.0.9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1881434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881432] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378825/+files/PulseList.txt ** Description changed: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- - - DistroRelease: Ubuntu 20.04 - InstallationDate: Installed on 2020-04-01 (59 days ago) - InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) - ApportVersion: 2.20.11-0ubuntu27.2 - Architecture: amd64 - ProcCpuinfoMinimal: - processor: 3 - vendor_id: AuthenticAMD - cpu family : 23 - model: 24 - model name : AMD Ryzen 3 3200G with Radeon Vega Graphics - stepping : 1 - microcode: 0x8108109 - cpu MHz : 1782.484 - cache size : 512 KB - physical id : 0 - siblings : 4 - core id : 3 - cpu cores: 4 - apicid : 3 - initial apicid : 3 - fpu : yes - fpu_exception: yes - cpuid level : 13 - wp : yes - ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: pulseaudio - Tags: focal - Uname: Linux 5.4.0-33-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - _MarkForUpload: True - dmi.bios.date: 11/14/2019 - dmi.bios.vendor: American Megatrends Inc. - dmi.bios.version: P3.70 - dmi.board.name: B450M-HDV R4.0 - 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.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0: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-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 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.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0: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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description:
[Desktop-packages] [Bug 1881432] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378823/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 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.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0: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/1881432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881432] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378824/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 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.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0: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/1881432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881432] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378821/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 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.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0: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/1881432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881432] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378822/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: wl Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 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.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0: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/1881432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
apport information ** Tags added: apport-collected focal ** Description changed: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ProcCpuinfoMinimal: processor: 3 vendor_id: AuthenticAMD cpu family : 23 model: 24 model name : AMD Ryzen 3 3200G with Radeon Vega Graphics stepping : 1 microcode: 0x8108109 cpu MHz : 1782.484 cache size : 512 KB physical id : 0 siblings : 4 core id : 3 cpu cores: 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception: yes cpuid level : 13 wp : yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 11/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: B450M-HDV R4.0 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.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0: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-0ubuntu27.2 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-01 (59 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + NonfreeKernelModules: wl + Package: pulseaudio 1:13.99.1-1ubuntu3.2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 + Tags: focal + Uname: Linux 5.4.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/14/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P3.70 + dmi.board.name: B450M-HDV R4.0 + 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.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0: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. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1881432/+attachment/5378820/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message:
[Desktop-packages] [Bug 1817912] Re: alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily large: 370196 bytes (2098 мс).
*** This bug is a duplicate of bug 1881432 *** https://bugs.launchpad.net/bugs/1881432 ** This bug has been marked a duplicate of bug 1881432 System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1817912 Title: alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily large: 370196 bytes (2098 мс). Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-utils package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: An old issue with ALSA is still present in Ubuntu 16.04.6. The system became extraordinarily slow and hangs at total in around a minute while playing a music (around a few hours in my case). [15:38:51] [root@ThinkPad/var/log]#grep "alsa-sink-CX20751/2 Analog" syslog Feb 27 14:58:50 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily large: 370196 bytes (2098 мс). Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Most likely this is a bug in the ALSA driver «snd_hda_intel». Please report this issue to the ALSA developers. Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: snd_pcm_dump(): Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Soft volume PCM Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Control: PCM Playback Volume Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: min_dB: -51 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: max_dB: 0 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: resolution: 256 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Its setup is: Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: stream : PLAYBACK Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: access : MMAP_INTERLEAVED Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: format : S16_LE Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: subformat: STD Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: channels : 2 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: rate : 44100 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: exact rate : 44100 (44100/1) Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: msbits : 16 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: buffer_size : 16384 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: period_size : 8192 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: period_time : 185759 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: tstamp_mode : ENABLE Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: tstamp_type : MONOTONIC Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: period_step : 1 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: avail_min: 15680 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: period_event : 0 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: start_threshold : -1 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: stop_threshold : 4611686018427387904 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: silence_threshold: 0 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: silence_size : 0 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: boundary : 4611686018427387904 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Slave: Hardware PCM card 1 'HDA Intel PCH' device 0 subdevice 0 Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: Its setup is: Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] alsa-util.c: stream : PLAYBACK Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog]
[Desktop-packages] [Bug 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
** Description changed: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. + + --- + + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-01 (59 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + ProcCpuinfoMinimal: + processor: 3 + vendor_id: AuthenticAMD + cpu family : 23 + model: 24 + model name : AMD Ryzen 3 3200G with Radeon Vega Graphics + stepping : 1 + microcode: 0x8108109 + cpu MHz : 1782.484 + cache size : 512 KB + physical id : 0 + siblings : 4 + core id : 3 + cpu cores: 4 + apicid : 3 + initial apicid : 3 + fpu : yes + fpu_exception: yes + cpuid level : 13 + wp : yes + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + SourcePackage: pulseaudio + Tags: focal + Uname: Linux 5.4.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + _MarkForUpload: True + dmi.bios.date: 11/14/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P3.70 + dmi.board.name: B450M-HDV R4.0 + 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.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0: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. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. --- DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ProcCpuinfoMinimal: processor: 3 vendor_id: AuthenticAMD cpu family : 23 model: 24 model name : AMD Ryzen 3 3200G with Radeon Vega Graphics stepping : 1 microcode: 0x8108109 cpu MHz : 1782.484 cache size : 512 KB physical id : 0 siblings : 4 core id : 3 cpu cores: 4 apicid : 3 initial apicid : 3 fpu : yes fpu_exception: yes cpuid level : 13 wp : yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Desktop-packages] [Bug 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877269] Re: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large)
*** This bug is a duplicate of bug 1881432 *** https://bugs.launchpad.net/bugs/1881432 ** This bug has been marked a duplicate of bug 1881432 System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877269 Title: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installé : 1:11.1-1ubuntu7.5 Candidat : 1:11.1-1ubuntu7.5 Table de version : *** 1:11.1-1ubuntu7.5 500 500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The OS freezes when using in normal conditions, usually VS Code, Discord app and Spotify in browser. When it does, I need to hard reboot by holding power button. I checked journalctl to confirm it was due to pulseaudio. alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large The above line is always the last to prompt in the boot journal. It does not freeze instantly, it progressively freezes down, but sometime Mozilla Firefox crashes and it freezes no more. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 Uname: Linux 5.1.15-surface-linux-surface x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saravanane 2071 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 7 11:00:37 2020 InstallationDate: Installed on 2019-10-01 (218 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 108.2706.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr108.2706.768:bd04/18/2019:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B09F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.sku: Surface_Pro_4 dmi.product.version: D:0B:09F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877269/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
** Attachment added: "System hang event @ timestamp 01:45:23 while playing video game" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+attachment/5378819/+files/syslog.5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: New Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881432] [NEW] System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"
Public bug reported: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "See @ timestamp 13:52:49 for beginning of system hang event" https://bugs.launchpad.net/bugs/1881432/+attachment/5378818/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881432 Title: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)" Status in pulseaudio package in Ubuntu: New Bug description: This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version: 1:13.99.1-1ubuntu3.2. Description: At random intervals, pulseaudio gives the following error message: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)," after which the system slows down to a crawl. It has occurred in two instances: while playing a video game, and while working in two different workspaces with a zoom client and Spotify open (though not actively playing any audio). The system is recoverable with the SysRq key. I have not been able to duplicate it on command, but it is recurrent. Possible duplicates: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The patch committed to fix this bug was reverted to fix a subsequent bug, https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881430] [NEW] After wake up all the Activities escape above screen and disappeared
Public bug reported: I move lounch pad to left. After sleep and wake up all the Activities escape above screen and disappeared. The problem repeats after every ubuntu sleep. After full reboot Activities is visible. I use extention "Dash to panel". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 30 21:27:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-25 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Снимок экрана от 2020-05-30 21-39-31.png" https://bugs.launchpad.net/bugs/1881430/+attachment/5378812/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-05-30%2021-39-31.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1881430 Title: After wake up all the Activities escape above screen and disappeared Status in gnome-shell package in Ubuntu: New Bug description: I move lounch pad to left. After sleep and wake up all the Activities escape above screen and disappeared. The problem repeats after every ubuntu sleep. After full reboot Activities is visible. I use extention "Dash to panel". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 30 21:27:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-25 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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/1881430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849399] Re: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key
I submitted a patch to the upstream repository that fixes the invalid parsing in ibus: https://github.com/ibus/ibus/pull/2227 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1849399 Title: ibus in 19.10 misinterprets ~/.XCompose, somehow maps to the Delete key Status in ibus package in Ubuntu: Triaged Bug description: After upgrade to 19.10, I found that my Delete key was not working as a Delete key, but that instead if I hit Delete twice it would print the character ☭. Since others were not reporting this issue, I had a look around at my input config and remembered that I had ibus configured from a long time ago in order to support Chinese input. If I disable ibus (either by unsetting the environment variables; or by killing ibus-daemon), then the Delete key works again as expected. This is a regression in behavior since Ubuntu 19.04, where I had the same input setup on my desktop but the Delete key worked without problems. I'm also not sure how to disable ibus, now that I am in this situation; or if ibus is expected to always be running. The problem persists if I run ibus-setup and remove Chinese SunPinyin from the list of input methods, leaving only "English - English (US)". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1849399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Also experiencing this bug with an RTX 2070 Super -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881423] [NEW] error channel closing too late to send/recv
Public bug reported: I saw the following in my logs on a fresh install of 18.04.4: May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Sat May 30 12:57:41 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1881423 Title: error channel closing too late to send/recv Status in gnome-shell package in Ubuntu: New Bug description: I saw the following in my logs on a fresh install of 18.04.4: May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Sat May 30 12:57:41 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1881423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881421] [NEW] Thinkpad T440s trackpad and trackpoint stop working after resume from suspend
Public bug reported: Hi, this is a sporadic issue that sometimes appears, sometimes not. Usually once it starts happening it occurs on every suspend/resume cycle until the system is rebooted. The trackpad and the red trackpoint nub stop working after resume. This is on a Thinkpad T440s laptop currently running a fresh install of Ubuntu 20.04 with Gnome and no major modifications. Usually the trackpad can be fixed by unloading/loading the `psmouse` module. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libinput10 1.15.5-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat May 30 11:39:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20AR006RUS ProcEnviron: LANGUAGE=es_EC:es TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-33-generic root=UUID=9ed61bc7-d832-4808-908a-05704b574781 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: GJETA4WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AR006RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJETA4WW(2.54):bd03/27/2020:svnLENOVO:pn20AR006RUS:pvrThinkPadT440s:rvnLENOVO:rn20AR006RUS:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AR006RUS dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1881421 Title: Thinkpad T440s trackpad and trackpoint stop working after resume from suspend Status in libinput package in Ubuntu: New Bug description: Hi, this is a sporadic issue that sometimes appears, sometimes not. Usually once it starts happening it occurs on every suspend/resume cycle until the system is rebooted. The trackpad and the red trackpoint nub stop working after resume. This is on a Thinkpad T440s laptop currently running a fresh install of Ubuntu 20.04 with Gnome and no major modifications. Usually the trackpad can be fixed by unloading/loading the `psmouse` module. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libinput10 1.15.5-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat May 30 11:39:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20AR006RUS ProcEnviron: LANGUAGE=es_EC:es TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-33-generic root=UUID=9ed61bc7-d832-4808-908a-05704b574781 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: GJETA4WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name:
[Desktop-packages] [Bug 1855889] Re: cannot perform operation: mount --rbind /root /tmp/snap.rootfs_vWwNbw//root: Permission denied
Just for completeness, I've found the solution. I googled some more as none of my other snaps were working and found a little tidbit I hadn’t come across before. It mentioned something about using the mount system for /root. My /root was a symlink to /home/root. I deleted the symlink Created a new /root folder Created a mount entry in /etc/fstab: /data/home/root /root none rbind Now my snaps are working. The full thread where I got this from is here: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1729576 the comment in question is #13. Thank you again for your help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: cannot perform operation: mount --rbind /root /tmp/snap.rootfs_vWwNbw//root: Permission denied Status in chromium-browser package in Ubuntu: Expired Status in snapd package in Ubuntu: New Bug description: Hi, I try to run Chromium from the menu and nothing happens. If I run it from the CLI I get: cannot perform operation: mount --rbind /root /tmp/snap.rootfs_vWwNbw//root: Permission denied I tried uninstalling and reinstalling. I tried uninstalling and reinstalling snapd. Tried anything related I could find on-line, but nothing works. Upgrade snap to the latest version on the pre-release channel. For some reason Chromium does not show up in the Software centre either. Thanks for any help. $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 78.0.3904.108 958 stablecanonicalâ - $ apt-cache policy chromium-browser chromium-browser: Installed: 77.0.3865.120-0ubuntu1.19.10.1 Candidate: 77.0.3865.120-0ubuntu1.19.10.1 Version table: *** 77.0.3865.120-0ubuntu1.19.10.1 500 500 http://mirror.overthewire.com.au/ubuntu eoan-updates/universe amd64 Packages 100 /var/lib/dpkg/status 77.0.3865.120-0ubuntu1~snap1 500 500 http://mirror.overthewire.com.au/ubuntu eoan/universe amd64 Packages $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 78.0.3904.108 958 stablecanonicalâ - $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonicalâ contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: stable refresh-date: today at 23:00 ACST channels: stable:78.0.3904.108 2019-11-25 (958) 160MB - candidate: 78.0.3904.108 2019-11-22 (952) 160MB - beta: 79.0.3945.74 2019-12-06 (966) 155MB - edge: 80.0.3983.2 2019-12-05 (964) 156MB - installed: 78.0.3904.108(958) 160MB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880396] Re: Traditional Chinese option not survived after reboot
Ok, I closed this bug. But if you have found that the behavior you experience is due to a conflict between ibus-libpinyin and ibus-pinyin, that is a bug in itself which you may want to submit. It's worth mentioning, though, that ibus- pinyin is deprecated and will probably be removed from Debian/Ubuntu soon. ** Changed in: ibus-libpinyin (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1880396 Title: Traditional Chinese option not survived after reboot Status in ibus-libpinyin package in Ubuntu: Invalid Bug description: Ubuntu 20.04 LTS, ibus-libpinyin 1.11.1-3 expect: after changing from simplified chinese to traditional chinese, the setting should survive after reboot. phenomenon: option got reset to simplified chinese after reboot. using ibus pinyin input method, ticked 'Traditional' option for 'Chinese' label. The setting works but not kept after reboot. After reboot, the input mode turned back to simplified chinese. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1880396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
I had time today to test 20.0.4-2ubuntu1~18.04.2 proposed bionic It's working , wow what a long stuff.. Happy end -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: Fix Released Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870776] Re: No smooth scrolling on Firefox (and Chrome)
*** This bug is a duplicate of bug 1697122 *** https://bugs.launchpad.net/bugs/1697122 Jerky scrolling in 20.04 both with 2-finger scrolling on touchpad or using the wireless mouse. Doesn't matter if only one is plugged ing. AMD-4130 CPU, GeForce Gt 720/PCIe/SSE2, Ubu 20.04. M5A97 LE R2.0 motherboard. Smooth scrolling on 16.04, 18.04 with same hw above. How to Fix? Happy to try anything (well, almost) you'd like. Thanks, Ken -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1870776 Title: No smooth scrolling on Firefox (and Chrome) Status in firefox package in Ubuntu: Incomplete Bug description: I'm on Ubuntu Beta 20.04 and I observe that smooth scrolling is not working in Firefox or Chrome, while it works well in other apps, like Nautilus/Files GNOME settings or within GNOME shell applications listing. I tried with Firefox in safe mode (so without any extension) with the same result. I also tried with a completely new GNOME user account (without any customization), with the same result. While I'm not so used to Chrome, it seems that smooth scrolling is not working with it either. Another test I did is to boot from a Fedora Workstation 32 Beta USB stick (with GNOME) and the smooth scrolling was working well in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
I have this issue. kbd_mode -s fixes it but then gnome session restarts when I hit enter anywhere. Ubuntu 20.04 LTS Linux 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: Won't Fix Status in xorg-server source package in Xenial: Confirmed Status in console-setup source package in Bionic: Fix Released Status in kbd source package in Bionic: Won't Fix Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Released Status in kbd source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Released Status in kbd source package in Disco: Won't Fix Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: Fix Released Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (kbd) [Impact] * kbd_mode -u is documented to break keyboards in modes other than xlate and unicode, while it is still called by some scripts. Those scripts are called transitively by maintainer scripts such as the one already fixed in console-setup. * To avoid accidentally breaking keyboards a -f option is added to force such breaking mode changes. Without -f only the safe mode changes are performed and an error is printed when the requested mode change is not safe. Next upstream version will also exit with error, but the cherry-picked fix makes kbd_mode return success even when the mode switch is not performed to avoid regressions of scripts. [Test case] * Verify that safe mode switches work and dangerous ones are skipped without -f. Please note that the test will temporarily break the system's keyboard and it is recommended to run the test in a VM. rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $? The keyboard is in Unicode (UTF-8) mode 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in xlate (8-bit) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in some unknown mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in raw (scancode) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in raw (scancode) mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 [Regression Potential] * kbd_mode stops performing breaking mode switches and this may make scripts ineffective when trying to perform a breaking change. This is the intention of the change and the emitter error helps in finding the offending script. The following packages found to call kbd_mode directly: console-setup xinit console-cyrillic initramfs-tools dracut console-tools xview ubiquity's embedded console-setup copy console-data vnc4 The console related packages are expected to execute only safe mode changes because they should operate on consoles only and the rest seem to be safe, too. (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $
[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
Please reopen the bug it is not working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in gnome-shell package in Ubuntu: Expired Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It may take few login attempts to actually login back. I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is always ON but tv is ON amd OFF as needed. Every time I turn tv ON and try to do something and use ctrl + c it would restart gnome session. After login it seem to work fine and ctrl+c does not break anything. Then the next day the similar thing happens. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-07-21 (213 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
I think this is exactly my problem: https://bugs.launchpad.net/ubuntu/+source/console- setup/+bug/520546/comments/1 >From time to time my keyboard switches to a mode when alt + f1 starts to >switch me to console. The bug comment also mentions Ctrl+C killing the GUI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in gnome-shell package in Ubuntu: Expired Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It may take few login attempts to actually login back. I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is always ON but tv is ON amd OFF as needed. Every time I turn tv ON and try to do something and use ctrl + c it would restart gnome session. After login it seem to work fine and ctrl+c does not break anything. Then the next day the similar thing happens. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-07-21 (213 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1880396] Re: Traditional Chinese option not survived after reboot
After some trying, looks like there is some conflicts between ibus-libpinyin and ibus-pinyin. Things works fine after I removed ibus-pinyin and re-added the pinyin input method in the setting panel. Thanks you for leaving those comments. Since the problem is resolved, I'd like to close this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1880396 Title: Traditional Chinese option not survived after reboot Status in ibus-libpinyin package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS, ibus-libpinyin 1.11.1-3 expect: after changing from simplified chinese to traditional chinese, the setting should survive after reboot. phenomenon: option got reset to simplified chinese after reboot. using ibus pinyin input method, ticked 'Traditional' option for 'Chinese' label. The setting works but not kept after reboot. After reboot, the input mode turned back to simplified chinese. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1880396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872501] Re: Modifications ALT R mapping at xmodmap not taking effect
*** This bug is a duplicate of bug 1867548 *** https://bugs.launchpad.net/bugs/1867548 @anna: The bug, which this bug was marked as a duplicate of, is about a specific gnome-control-center issue with the Right Alt/AltGr key. Your problem seems to be unrelated to that. If you think your problem is a bug, you should submit a new bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1872501 Title: Modifications ALT R mapping at xmodmap not taking effect Status in x11-xserver-utils package in Ubuntu: New Bug description: How to map ALT Gr key as ALT R on Ubuntu 20.04? As described in an Ask Ubuntu post, I've executed xev at Ubuntu 20.04 in order to discover ALT L and ALT R keycodes: - ALT L: keycode 64 (keysym 0xffe9, Alt_L) - ALT R: keycode 108 (keysym 0xfe03, ISO_Level3_Shift) Running xmodmap -pke > ~/.Xmodmap, the following configuration was saved: keycode 64 = Alt_L Meta_L Alt_L Meta_L Alt_L Meta_L keycode 108 = ISO_Level3_Shift NoSymbol ISO_Level3_Shift NoSymbol ISO_Level3_Shift Theoretically re-mapping 108 at ~/.Xmodmap should be enough: keycode 108 = Alt_R Meta_R Alt_R Meta_R Alt_R Meta_R However, even running xmodmap ~/.Xmodmap and also saving this command at ~/.xinitrc, the modifications did not take effect immediately or after login again at Ubuntu. Thus it is not possible to execute extensible commands in Emacs using ALT R + X at Emacs So what is the proper way of changing ALT R behavior? Or is it a bug at 20.04 release? References: - https://askubuntu.com/questions/1226777/ubuntu1-how-to-map-alt-gr-key-as-alt-r-on-ubuntu-20-04 - https://askubuntu.com/questions/254424/how-can-i-change-what-keys-on-my-keyboard-do-how-can-i-create-custom-keyboard - https://askubuntu.com/questions/813332/how-to-enable-alt-gr-key-as-alt-r-for-emacs-on-ubuntu-16-04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: x11-xserver-utils 7.7+8 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 13:18:33 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 5.1.26: added virtualbox, 6.1.4, 5.4.0-24-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:082a] InstallationDate: Installed on 2018-01-29 (805 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: x11-xserver-utils UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 02PG84 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 082A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2003140730.b93a19~oibaf~e version.libgl1-mesa-glx: libgl1-mesa-glx 20.1~git2003140730.b93a19~oibaf~e version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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/x11-xserver-utils/+bug/1872501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881401] [NEW] HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base
Public bug reported: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install HPLIP with `sudo apt-get install hplip-gui` 3. Install all stuff to satisfy `hp-doctor` requirements by: sudo apt-get build-dep hplip sudo apt-get install build-essential libtool libtool-bin libcups2-dev cups-bsd cups-client avahi-utils gtk2-engines-pixbuf xsane python3-notify2 4. Run `hp-doctor` and `hp-check` Expected results: * `hp-doctor` ran successfully without errors * `hp-check` ran successfully without errors Actual results: ``` $ hp-doctor HP Linux Imaging and Printing System (ver. 3.20.3) Self Diagnse Utility and Healing Utility ver. 1.0 ... Checking for Dependencies warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... ... -- | PERMISSION | -- Missing Required Dependencies - error: 'libcups2' package is missing or 'cups' service is not running. error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible ... $ hp-check Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 ... --- | SUMMARY | --- Missing Required Dependencies - error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies - error: 'python3-dbus.mainloop.qt' package is missing/incompatible Total Errors: 3 Total Warnings: 0 Done. ``` Note: many mentioned packages are already installed, Qt4 related packages are not installable: ``` $ sudo apt-get install libcups2 libcups2-dev Reading package lists... Done Building dependency tree Reading state information... Done libcups2 is already the newest version (2.3.1-9ubuntu1.1). libcups2-dev is already the newest version (2.3.1-9ubuntu1.1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install gtk2-engines-pixbuf Reading package lists... Done Building dependency tree Reading state information... Done gtk2-engines-pixbuf is already the newest version (2.24.32-4ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $ sudo apt-get install python3-pyqt4 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-pyqt4 $ sudo apt-get install python3-dbus.mainloop.qt Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package python3-dbus.mainloop.qt E: Couldn't find any package by glob 'python3-dbus.mainloop.qt' E: Couldn't find any package by regex 'python3-dbus.mainloop.qt' ``` Please consider to fix HPLIP package and support 20.04 LTS package base before 20.04.1 release! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 30 12:25:39 2020 InstallationDate: Installed on 2020-04-23 (36 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=3947d85c-2c09-420b-802f-edf59648248a ro quiet splash SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: hplip Importance: Undecided Status: New ** Affects: hplip (Ubuntu)
[Desktop-packages] [Bug 1872501] Re: Modifications ALT R mapping at xmodmap not taking effect
*** This bug is a duplicate of bug 1867548 *** https://bugs.launchpad.net/bugs/1867548 I'm having the exact same problem on Ubuntu 20.04 and gnome-control- center version 3.36.2 with the assumed duplicate bug fixed. I follow the same steps as in the original description to exchange the Control_L key and XF86WakeUp key (Fn on German keyboards): I executed xev to discover the Control_L and XF86WakeUp keycodes: KeyRelease event, serial 37, synthetic NO, window 0x461, root 0x5dd, subw 0x0, time 4165720, (668,636), root:(902,854), state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 37, synthetic NO, window 0x461, root 0x5dd, subw 0x0, time 4166218, (668,636), root:(902,854), state 0x0, keycode 151 (keysym 0x1008ff2b, XF86WakeUp), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False Then, I run $ xmodmap -e "keycode 37 = XF86WakeUp" and $ xmodmap -e "keycode 151 = Control_L" After which xev shows: KeyRelease event, serial 37, synthetic NO, window 0x3c1, root 0x5fd, subw 0x0, time 1691367, (1390,1888), root:(1584,2066), state 0x0, keycode 151 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 37, synthetic NO, window 0x3c1, root 0x5fd, subw 0x0, time 1692110, (1390,1888), root:(1584,2066), state 0x0, keycode 37 (keysym 0x1008ff2b, XF86WakeUp), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False Saving this to a .Xmodmap file and looking at the content correctly shows the change: $ xmodmap -pke ~./Xmodmap $ cat ~/.Xmodmap -- snip -- keycode 37 = XF86WakeUp NoSymbol XF86WakeUp keycode 151 = Control_L NoSymbol Control_L -- snip-- However, the system still treats key 37 as Control_L, and key 151 as XF86WakeUp. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1872501 Title: Modifications ALT R mapping at xmodmap not taking effect Status in x11-xserver-utils package in Ubuntu: New Bug description: How to map ALT Gr key as ALT R on Ubuntu 20.04? As described in an Ask Ubuntu post, I've executed xev at Ubuntu 20.04 in order to discover ALT L and ALT R keycodes: - ALT L: keycode 64 (keysym 0xffe9, Alt_L) - ALT R: keycode 108 (keysym 0xfe03, ISO_Level3_Shift) Running xmodmap -pke > ~/.Xmodmap, the following configuration was saved: keycode 64 = Alt_L Meta_L Alt_L Meta_L Alt_L Meta_L keycode 108 = ISO_Level3_Shift NoSymbol ISO_Level3_Shift NoSymbol ISO_Level3_Shift Theoretically re-mapping 108 at ~/.Xmodmap should be enough: keycode 108 = Alt_R Meta_R Alt_R Meta_R Alt_R Meta_R However, even running xmodmap ~/.Xmodmap and also saving this command at ~/.xinitrc, the modifications did not take effect immediately or after login again at Ubuntu. Thus it is not possible to execute extensible commands in Emacs using ALT R + X at Emacs So what is the proper way of changing ALT R behavior? Or is it a bug at 20.04 release? References: - https://askubuntu.com/questions/1226777/ubuntu1-how-to-map-alt-gr-key-as-alt-r-on-ubuntu-20-04 - https://askubuntu.com/questions/254424/how-can-i-change-what-keys-on-my-keyboard-do-how-can-i-create-custom-keyboard - https://askubuntu.com/questions/813332/how-to-enable-alt-gr-key-as-alt-r-for-emacs-on-ubuntu-16-04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: x11-xserver-utils 7.7+8 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 13:18:33 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 5.1.26: added virtualbox, 6.1.4, 5.4.0-24-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:082a] InstallationDate: Installed on 2018-01-29 (805 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: x11-xserver-utils UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 02PG84
[Desktop-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again
If there is no log from pulseaudio, it means the pulseaudio does not join the connection process yet. The pulseaudio needs to receive a Dbus message (connection request) from bluez first, then it starts to processing bluetooth connection. So in your case, the connection failed in the bluez. Could you connect other bluetooth heapdhones to your laptop? Let's see if it is the problem on your laptop (bluetooth hci controller). If it is, it is highly possible that it is bluetooth driver or firmware's problem. Could you connect your redmi headphone to other laptops? If yes, you could capture bt packages during the reconnection and compare them: close gnome bluetooth applet, $sudo btmon -w good.cap $btmon -r good.cap on the machine with problem: $sudo btmon -w bad.cap $btmon -r bad.cap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879582 Title: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again Status in alsa-driver package in Ubuntu: New Bug description: I can connect to my bluetooth phone only the first time after pair the device. It works until disconnecting, (whether by turning off the phone, or putting into the case, or disconnecting in ubuntu settings), and then i turn on the phone again (or remove from the case), i cannot connect until I manually remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. If the Ubuntu/Gnome Settings is opened, i can see the status "connected" blinks, and fastly change to "disconnected". My bluetooth phone works fine with another devices. Ubuntu 20.04 LTS Laptop Acer Aspire Nitro 5 (AN515-52-5771). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: felipe 2149 F pulseaudio /dev/snd/controlC0: felipe 2149 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 19:10:35 2020 InstallationDate: Installed on 2020-04-29 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redmi AirDots_R Symptom_Type: None of the above Title: [Redmi AirDots_R, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717466] Re: Proxy settings are missing in apt.conf
I am facing the same problem in Ubuntu 20.04 LTS ( 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) , Gnome-control-center 3.36.2 . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1717466 Title: Proxy settings are missing in apt.conf Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 When proxies are set via network settings dialog this does not affect apt.conf. This results in software installation and upgrade problems. I had to specify proxies by adding "Acquire" in apt.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1717466/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 290313] Re: system-wide proxy does not apply to synaptic
Im facing the problem described above in Ubuntu 20.04 LTS. Should i open a new bug or just add here? Trying to report bug using apport-bug is showing this as a similar case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/290313 Title: system-wide proxy does not apply to synaptic Status in gnome-control-center package in Ubuntu: Invalid Status in ubuntu-system-service package in Ubuntu: Invalid Bug description: Binary package hint: ubuntu-system-service On a fresh Intrepid RC install I have to use proxy settings within my network. So when I configure proxy settings via System->Preferences->Network Proxy I fill in the Manual Proxy configuration and press the "Apply System Wide ... " button. When I start Firefox it asks me for proxy login credentials. When I start Synaptic and try to update my packages I get a failed on all sources. I checked the proxy settings via Settings->Preferences->Network, but there was nothing there. After adding the proxy settings to the Network tab I am able to update my packages repository via Synaptic. ubuntu-system-service-1.0.10 linux-image-2.6.27-7-generic Ubuntu-system-services uses dbus to apply system wide settings. Tux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/290313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844808] Re: Can't delete file from desktop by clicking it and hitting delete key
** Also affects: gnome-shell-extension-desktop-icons (Baltix) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-desktop-icons (Baltix) Status: New => In Progress ** Changed in: gnome-shell-extension-desktop-icons (Baltix) Assignee: (unassigned) => Mantas Kriaučiūnas (mantas) ** Changed in: gnome-shell-extension-desktop-icons (Baltix) Milestone: None => baltix-18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1844808 Title: Can't delete file from desktop by clicking it and hitting delete key Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: Fix Committed Status in gnome-shell-extension-desktop-icons package in Baltix: In Progress Bug description: Just upgraded to 19.10 today. Previously, in 19.04, I could delete a file from the desktop by clicking on it and hitting the delete key. That no longer works. It's probably relevant that it doesn't appear to be possible to direct keyboard focus to the desktop itself any longer. When I click on an icon on the desktop and then hit the delete key, the keystroke is sent to the window that had focus before I clicked. This appears to be true regardless of what window focus mode I'm using (Click to Focus, Focus on Hover, or Secondary-Click). Note that the description of Secondary- Click, "Window is focused when hovered with the pointer. Hovering the desktop removes focus from the previous window," does not appear to be true. When I select that focus mode and hover my mouse over the desktop I remain focused on the previously focused window. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.4-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 11:12:42 2019 InstallationDate: Installed on 2019-09-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1844808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
