[Touch-packages] [Bug 1876659] [NEW] Unhandled exception in run_hang()
Public bug reported: ## Description When we start apport-cli without PID, an unhandled exception in apport 2.20.11 and earlier may allow an authenticated user to potentially enable a denial of service via local access. The following command may cause an application crash due to an unhandled exception. $ apport-cli --hanging *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (24.0 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): K Problem report file: /tmp/apport.apport.uc0_znhj.apport Traceback (most recent call last): File "/usr/bin/apport-cli", line 387, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv self.run_hang(self.options.pid) File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang os.kill(int(pid), signal.SIGKILL) TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' Above command generates the following application crash file in /var/crash/ directory. ProblemType: Crash CurrentDesktop: ubuntu:GNOME Date: Sun May 3 19:09:41 2020 ExecutablePath: /usr/bin/apport-cli ExecutableTimestamp: 1585099033 InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli --hanging ProcCwd: /home/user/apport/bin ProcEnviron: ... ProcMaps: ... ProcStatus: ... PythonArgs: ['/usr/bin/apport-cli', '--hanging'] Traceback: Traceback (most recent call last): File "/usr/bin/apport-cli", line 387, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv self.run_hang(self.options.pid) File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang os.kill(int(pid), signal.SIGKILL) TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _LogindSession: 6 Many thanks. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1876659 Title: Unhandled exception in run_hang() Status in apport package in Ubuntu: New Bug description: ## Description When we start apport-cli without PID, an unhandled exception in apport 2.20.11 and earlier may allow an authenticated user to potentially enable a denial of service via local access. The following command may cause an application crash due to an unhandled exception. $ apport-cli --hanging *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (24.0 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): K Problem report file: /tmp/apport.apport.uc0_znhj.apport Traceback (most recent call last): File "/usr/bin/apport-cli", line 387, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv self.run_hang(self.options.pid) File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang os.kill(int(pid), signal.SIGKILL) TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' Above command generates the following application crash file in /var/crash/ directory. ProblemType: Crash CurrentDesktop: ubuntu:GNOME Date: Sun May 3 19:09:41 2020 ExecutablePath: /usr/bin/apport-cli ExecutableTimestamp: 1585099033 InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli --hanging ProcCwd: /home/user/apport/bin ProcEnviron: ... ProcMaps: ... ProcStatus: ... PythonArgs: ['/usr/bin/apport-cli', '--hanging'] Traceback: Traceback (most recent call last): File "/usr/bin/apport-cli", line 387, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 690, in run_argv self.run_hang(self.options.pid) File "/usr/lib/python3/dist-packages/apport/ui.py", line 410, in run_hang os.kill(int(pid), signal.SIGKILL) TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType' UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _LogindSession: 6 Many thanks. To manage notifications about this bug go to:
[Touch-packages] [Bug 1876519] Re: Screens black: scaling to 125% for both monitors
*** This bug is a duplicate of bug 1873403 *** https://bugs.launchpad.net/bugs/1873403 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1873403, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1873403 [nvidia] Screen turns off when trying to set some fractional scaling values -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876519 Title: Screens black: scaling to 125% for both monitors Status in xorg package in Ubuntu: New Bug description: If I set the scaling of my two QHD monitors to 125%, they remain black when saved. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 22:23:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1070] [3842:6276] InstallationDate: Installed on 2020-05-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=54c03160-c1bb-40d5-8d7f-27e961fd8ee8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4101 dmi.board.asset.tag: Default string dmi.board.name: X99-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd07/10/2019:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: 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 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/1876519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876632] Re: [nvidia] Corrupted fonts in display output when using multiple users
** Summary changed: - Corrupted fonts in display output when using multiple users + [nvidia] Corrupted fonts in display output when using multiple users ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted fonts in display output when using multiple users Status in mutter package in Ubuntu: New Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 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/mutter/+bug/1876632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]
This is the second time I've seen this issue reported against XFCE recently but I can't find the other report right now. Please try: 1. Log out. 2. Ctrl+Alt+F4 and log into the text console. 3. rm -rf .config/pulse 4. Ctrl+Alt+F1 and log in again. Has that fixed it? ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and "Build-in speaker" appears "unplugged/unavaiable". I can change it in volume control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and sound does play, but after each reboot computer changes to Digital Stereo IEC985 and do not play sound until changed again. I did reinstall of alsa and pulse according to some forums but this didn't work. Before upgrade everything always worked out of the box since 2009 on this computer. I know it's a little old but it works excellent! Please help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 30 09:25:27 2020 InstallationDate: Installed on 2020-02-25 (64 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876369] Re: garbled/frozen screen after waking from sleep mode
*** This bug is a duplicate of bug 1855757 *** https://bugs.launchpad.net/bugs/1855757 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1855757, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1855757 [nvidia] Background image corrupted after standby -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876369 Title: garbled/frozen screen after waking from sleep mode Status in xorg package in Ubuntu: New Bug description: Computer boots and runs normally until it goes into sleep mode. wehen trying to wake from sleep mode, screen is filled with what looks like frozen static on an old TV, then it locks up. I have to force power- off the computer and reboot to make it work again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 1 14:45:37 2020 DistUpgraded: 2020-04-28 09:50:34,578 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G96CM [GeForce 9650M GT] [10de:064c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96CM [GeForce 9650M GT] [1043:1912] InstallationDate: Installed on 2018-04-28 (734 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK Computer Inc. M70Vn ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d4a14cd2-2bf0-4a55-a605-f421a799c4eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (3 days ago) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M70Vn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd12/21/2009:svnASUSTeKComputerInc.:pnM70Vn:pvr1.0:rvnASUSTeKComputerInc.:rnM70Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M70Vn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri May 1 14:38:54 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876530] Re: Screen scales to grandma very unfriendly mode
Please run 'xrandr' in a Terminal both before and after the problem and paste the output from the command here. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: xrandr-scaling ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876530 Title: Screen scales to grandma very unfriendly mode Status in mutter package in Ubuntu: Incomplete Bug description: When fractional scaling is active and set to 125% (I only tested this with 125%) and then the switch for fractional scaling is deactivated again, the screen scales well beyond the standard (and selected) 100%. Feels like 50% or less. This issue is removed when rebooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 00:35:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:16a1] InstallationDate: Installed on 2020-04-30 (2 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 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 13d3:56dc IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX392FA_UX392FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=cbcf9a35-a5f8-429f-adad-ad8f21bff5df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX392FA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX392FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX392FA.301:bd07/17/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX392FA_UX392FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX392FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX392FA_UX392FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 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/mutter/+bug/1876530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876487] Re: The screen is blinking at a random time
Please try: 1. Disabling visual bell in Settings > Universal Access > Hearing > Visual Alerts = Off 2. Select 'Ubuntu on Wayland' from the login screen. Does that avoid the issue? 3. Next time the problem starts happening run: journalctl -b0 > journal.txt and then attach the resulting file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876487 Title: The screen is blinking at a random time Status in Ubuntu: Incomplete Bug description: I've seen this error on Dell Latitude E7270 (with an internal video card) as well as Dell Precision 7540 (with NVidia card). I've seen this error on Ubuntu 18.04 and now on 20.04 I've never reported it yet but I think the time has come. In a random time (~ once a couple of weeks) I see a blinking screen. Today I've recorded a video on my phone to show you how it looks. You can see it here: https://youtu.be/JiUu7Ydg6uM This is bug finishes when I do logout from my desktop. Could you help me eliminate this error? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 2 19:28:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-21-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-25-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06db] InstallationDate: Installed on 2020-04-09 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Latitude E7270 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=9427d12e-3c69-4eb4-aa23-52bfe8bd2641 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 0T0V7J dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn0T0V7J:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7270 dmi.product.sku: 06DB dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1876487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876531] Re: Dynamic desktop background when TearFree is true
If you are using the 'intel' driver then this would be a duplicate of bug 1867668, but the attached logs show you're not using that driver (which is good in theory). To verify which it is, please wait until the problem happens again and then run: journalctl -b0 > journal.txt and attach the file 'journal.txt' here. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876531 Title: Dynamic desktop background when TearFree is true Status in xorg-server package in Ubuntu: Incomplete Bug description: In my 20-intel.conf file in either /etc/X11/xorg.conf.d/ or /usr/share/X11/xorg.conf.d/ when I set Option TearFree to true, the pixel on my desktop go wild, see attachment (dynamic because those stripes vary from boot to boot). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 00:34:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:16a1] InstallationDate: Installed on 2020-04-30 (2 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 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 13d3:56dc IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX392FA_UX392FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=cbcf9a35-a5f8-429f-adad-ad8f21bff5df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX392FA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX392FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX392FA.301:bd07/17/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX392FA_UX392FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX392FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX392FA_UX392FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 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-server/+bug/1876531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876608] Re: [Lenovo IdeaPad P400 Touch] display brightness control do not working and touch screen is also not working
** Summary changed: - display bright ness controlles do not working and touch screen is also not working + [Lenovo IdeaPad P400 Touch] display brightness control do not working and touch screen is also not working ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876608 Title: [Lenovo IdeaPad P400 Touch] display brightness control do not working and touch screen is also not working Status in linux package in Ubuntu: New Bug description: Unable to increase or decrease the Display brightness is not work and touch screen is also not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 23:03:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20211 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=1162f9cd-5236-4def-aa6c-42bd3d241968 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad P400 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20211:pvrLenovoIdeaPadP400Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadP400Touch: dmi.product.family: IDEAPAD dmi.product.name: 20211 dmi.product.sku: LENOVO_MT_20211 dmi.product.version: Lenovo IdeaPad P400 Touch 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876608/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876529] Re: Massive screen tearing using fractional scaling
*** This bug is a duplicate of bug 1846398 *** https://bugs.launchpad.net/bugs/1846398 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1846398, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1846398 Fractional scaling has significant visible tearing in Xorg sessions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876529 Title: Massive screen tearing using fractional scaling Status in xorg package in Ubuntu: New Bug description: The tearing appears when fractional scaling is active and set to 125% (I only tested it with 125%) AND only when the mouse cursor is moved. The tearing does not appear, when the cursor is not moved. The tearing does also not appear when the display is scaled to 100 or 200% no matter if fractional scaling is active or the cursor is moved. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 00:37:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:16a1] InstallationDate: Installed on 2020-04-30 (2 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 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 13d3:56dc IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX392FA_UX392FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=cbcf9a35-a5f8-429f-adad-ad8f21bff5df ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX392FA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX392FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX392FA.301:bd07/17/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX392FA_UX392FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX392FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX392FA_UX392FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 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/1876529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876238] Re: [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to 20.04 LTS Focal
*** This bug is a duplicate of bug 1875252 *** https://bugs.launchpad.net/bugs/1875252 Yes, it could be. There are two audio jacks and an internal microphone in my laptop, as said in that bug. 1869819 affects at least only two people; however, its regression/SRU affects many, Dell puters in particular! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876238 Title: [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to 20.04 LTS Focal Status in alsa-driver package in Ubuntu: New Bug description: Internal speakers were working fine until I upgraded the system from 19.10 LTS to 20.04 LTS on April 23, 2020. Uninstalled and reinstalled alsamixer and pavucontrol, but of no use. Killed pavucontrol and reloaded alsamixer numerous times, but of no use. (`pulseaudio -k && sudo alsa force-reload`) Waited for two kernel updates, but of no use. Presently on 5.4.0-29. Tried upgrading the kernel even up to 5.6, but of no use. The Intel sound card is not getting detected. Tried every trick like adding "options snd-hda-intel dmic_detect=0" in the /etc/modprobe.d/alsa-base.conf, but of no use. Out of the two external audio output sockets for headphone, one is working. So I can either connect a headphone or an external speaker to this jack to tide over the crisis for the time being. 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: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raj 10952 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 09:54:23 2020 InstallationDate: Installed on 2016-12-20 (1227 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raj 10952 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-26T17:25:43.583147 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875369] Re: recording device won't change
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1875369 Title: recording device won't change Status in pulseaudio package in Ubuntu: New Bug description: installed from lubuntu .iso fully updated as of yesterday fresh boot this morning some of these details are most likely irrelevant, but it's what i do to keep things simple: ignore graphical login screen, change to VT2 startx /usr/bin/xterm in the xterm: /opt/firefox/firefox& #(nightly) openbox& pavucontrol-qt& pavucontrolresults are the same regardless which of the pavucontrols is invoked in firefox: voice.google.com start a call in either of the pavucontrols: try to change the recording device: the menu opens, select the desired device, but it just doesn't change. doesn't matter which of the two pavucontrols was invoked ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 27 07:49:12 2020 InstallationDate: Installed on 2020-03-15 (42 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860483] Re: [nouveau, GeForce 6/7] screen background overlaid with scan type artifact in red
Actually I just realised the duplicates of this bug are closer related to each other than to this one. So I will separate them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860483 Title: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1875712 Title: Unusable graphics, nouveau + G73 (GEForce 7600) Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: This is an older card, but it worked well on ubuntu 12.x :) Booting "Try Ubuntu" on 20.04 get the correct resolution and 2 displays, but the video glitches and shows all sorts of noise. It is largely unusable (which makes filing this bug very hard). Safe Graphics works in low-res. The nvidia proprietary driver seems to not support this device any more. I like this card because it has no fan (and I don't do a lot of graphics-intense stuff). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 18:13:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd --- priority=low SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: X58 Extreme6 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.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6: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. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)
Actually there's a new bug 1876379 that looks more similar to this, and it's the same Ubuntu release. So let's handle them both here. ** Tags added: nouveau ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1875712 Title: Unusable graphics, nouveau + G73 (GEForce 7600) Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: This is an older card, but it worked well on ubuntu 12.x :) Booting "Try Ubuntu" on 20.04 get the correct resolution and 2 displays, but the video glitches and shows all sorts of noise. It is largely unusable (which makes filing this bug very hard). Safe Graphics works in low-res. The nvidia proprietary driver seems to not support this device any more. I like this card because it has no fan (and I don't do a lot of graphics-intense stuff). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 18:13:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd --- priority=low SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: X58 Extreme6 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.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6: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. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)
** This bug is no longer a duplicate of bug 1860483 [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1875712 Title: Unusable graphics, nouveau + G73 (GEForce 7600) Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: This is an older card, but it worked well on ubuntu 12.x :) Booting "Try Ubuntu" on 20.04 get the correct resolution and 2 displays, but the video glitches and shows all sorts of noise. It is largely unusable (which makes filing this bug very hard). Safe Graphics works in low-res. The nvidia proprietary driver seems to not support this device any more. I like this card because it has no fan (and I don't do a lot of graphics-intense stuff). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 18:13:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd --- priority=low SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: X58 Extreme6 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.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6: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. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876379] Re: Screen is broken into triangles
*** This bug is a duplicate of bug 1875712 *** https://bugs.launchpad.net/bugs/1875712 That reminds me of some screenshots from bug 1875712, which is now a duplicate of bug 1860483 so let's use that. ** This bug has been marked a duplicate of bug 1875712 Unusable graphics, nouveau + G73 (GEForce 7600) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876379 Title: Screen is broken into triangles Status in xorg package in Ubuntu: New Bug description: After a new install of 20.04 the console display is broken into odd distortions and triangles and weird colours. I'm guessing the window manager is not working well with the graphic card, since it was fine up to the point of the automatic login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 16:28:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV43 [GeForce 6600 GT] [10de:0140] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: stem manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=23a40263-d349-4d43-af42-f18938d91ff9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd06/01/2007:svnstemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: stem manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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/1876379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876382] Re: Ubuntu 20.04 Fractional scaling
*** This bug is a duplicate of bug 1873403 *** https://bugs.launchpad.net/bugs/1873403 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1873403, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1873403 [nvidia] Screen turns off when trying to set some fractional scaling values -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876382 Title: Ubuntu 20.04 Fractional scaling Status in xorg package in Ubuntu: New Bug description: I have 2 screens 1 x 1440 x 2560 (2k) 1 x 3840 x 2160 (4k) I just upgraded to ubuntu 20.04 (From 19.10). I have tried to use the fractional scaling option and it seem its not working. When setting the fractional scaling on the 4k monitor (to 125% or 150%) it glitches out (Goes black) and when it comes back it has set the scaling to 200% and changed the screen positions to be on top of one another, Seems there is no way for me to set the correct scaling. Just for information purposes I am currently using the nvidia-435 driver (I have also tried with the nvidia-440-driver) to no avail ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 22:00:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-28-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6183] InstallationDate: Installed on 2020-01-15 (106 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:0892 Logitech, Inc. OrbiCam Bus 001 Device 003: ID 1b1c:1b20 Corsair Corsair STRAFE RGB Gaming Keyboard Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370P D3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=bd37a70e-316f-4716-a253-481f8f785d18 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: Z370P D3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ370PD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370PD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370P D3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 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:
[Touch-packages] [Bug 1876474] Re: Dock disappears
** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876474 Title: Dock disappears Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: The Dock does not appear after the system went into "Blank Screen" (Standby) if I had a fullscreen Youtube Video paused while it went into standby. Pressing the super key twice brings the dock back. Probably related to me using multiple monitors, with firefox fullscreen on one of them. I hope I somewhat correctly categorized the bug, never did this before. If I should write firefox instead please let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.4.0 (Ubuntu 8.4.0-1ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 17:28:46 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-96-generic, x86_64: installed nvidia, 390.116, 4.15.0-99-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1070 Ti] [3842:6678] InstallationDate: Installed on 2019-05-10 (358 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Z390 UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=fcde5350-6206-d501-90d2-53506206d501 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10c dmi.board.asset.tag: Default string dmi.board.name: Z390 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10c:bd12/18/2019:svnGigabyteTechnologyCo.,Ltd.:pnZ390UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z390 UD dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1876474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
** Changed in: util-linux (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Released Status in util-linux source package in Bionic: Fix Released Status in util-linux source package in Disco: Won't Fix Status in util-linux source package in Eoan: Fix Released Status in util-linux source package in Focal: Fix Released Status in util-linux package in Debian: Fix Released Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
Looks like we have a new regression in the focal introduced by this fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874465 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876238 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876238] Re: [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to 20.04 LTS Focal
*** This bug is a duplicate of bug 1875252 *** https://bugs.launchpad.net/bugs/1875252 OK, it is highly possible that this is a regression introduced by the fix of https://bugs.launchpad.net/oem-priority/+bug/1869819 We will fix it in the ubuntu pulseaudio. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876238 Title: [Dell Inspiron 1525, SigmaTel STAC9228] No sound at all. Internal Speaker Not Detected. Dummy Output. After Upgrading From 19.10 to 20.04 LTS Focal Status in alsa-driver package in Ubuntu: New Bug description: Internal speakers were working fine until I upgraded the system from 19.10 LTS to 20.04 LTS on April 23, 2020. Uninstalled and reinstalled alsamixer and pavucontrol, but of no use. Killed pavucontrol and reloaded alsamixer numerous times, but of no use. (`pulseaudio -k && sudo alsa force-reload`) Waited for two kernel updates, but of no use. Presently on 5.4.0-29. Tried upgrading the kernel even up to 5.6, but of no use. The Intel sound card is not getting detected. Tried every trick like adding "options snd-hda-intel dmic_detect=0" in the /etc/modprobe.d/alsa-base.conf, but of no use. Out of the two external audio output sockets for headphone, one is working. So I can either connect a headphone or an external speaker to this jack to tide over the crisis for the time being. 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: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raj 10952 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 09:54:23 2020 InstallationDate: Installed on 2016-12-20 (1227 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raj 10952 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-26T17:25:43.583147 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876621] Re: Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876621 Title: Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes Status in xorg package in Ubuntu: New Bug description: In my configuration, the main monitor is landscape and the secondary monitor, to the right, is portrait. The most common result appears to be the primary display as seen by the DE being far wider than the actual monitor, and the second monitor being disabled entirely. Hitting "revert changes" usually doesn't actually change things back. Further, the xrandr CLI tool behaves strangely until the side monitor is removed from the layout entirely. Things behave as expected if the side monitor is set to landscape. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-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 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sun May 3 15:11:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6393] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=216c25da-8351-4944-9308-cf9b4ec2ba88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 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.:bvr2004:bd08/07/2014: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 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/1876621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876637] [NEW] I use the buttons on the keyboard to adjust sound (F1 mute, F2 decrease, F3 increase). More often than not, I push two to four times until the sound gets to the le
Public bug reported: alsa-driver was selected automatically. I don't know if that's the problem. I'm newbie. I just want to understand when it will be triggered (if it's a feature) so I can avoid increasing the volume to the max accidentally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mert 1026 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 02:57:08 2020 InstallationDate: Installed on 2020-05-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulseAudioLog: May 03 12:18:43 V330 dbus-daemon[841]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=1000 pid=1026 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [81AX, Intel Kabylake HDMI, Digital Out, HDMI] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN49WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN49WW:bd02/18/2020:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876637 Title: I use the buttons on the keyboard to adjust sound (F1 mute, F2 decrease, F3 increase). More often than not, I push two to four times until the sound gets to the level I want. Sometimes it gets automatic after I press, and takes it all the way up, or all the way down. I'm not sure if this is a feature or bug but I can't figure out when it will be triggered, thus I end up pumping the music at very loud, uncomfortable levels until I get back my control from panic and decrease the volume to somewhere acceptable. There are times it automatically goes to complete silent from there which is still annoying although not as much as the first one. [81AX, Intel Kabylake HDMI, Digital Out, HDMI] volume slider problem Status in alsa-driver package in Ubuntu: New Bug description: alsa-driver was selected automatically. I don't know if that's the problem. I'm newbie. I just want to understand when it will be triggered (if it's a feature) so I can avoid increasing the volume to the max accidentally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mert 1026 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 02:57:08 2020 InstallationDate: Installed on 2020-05-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulseAudioLog: May 03 12:18:43 V330 dbus-daemon[841]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=1000 pid=1026 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [81AX, Intel Kabylake HDMI, Digital Out, HDMI] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN49WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias:
[Touch-packages] [Bug 1873489] Re: lscpu cache information is incorrect with focal on arm 64-bit platform (ThunderX2)
Hi Mauricio, thank you for providing the information that I was not aware of. It's very clear and helpful for me. Because the ThunderX2 is unavailable for me currently, I verified the output format with Focal on an arm d06 cpu, which is able to reproduce the "issue" (my own host name "scobee"). It is exactly what you have said. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1873489 Title: lscpu cache information is incorrect with focal on arm 64-bit platform (ThunderX2) Status in util-linux package in Ubuntu: Invalid Bug description: Platform: Cavium Sabre Marvell ThunderX2 The L1/L2/L3 cache output by "lscpu" is incorrect, and differes from the output with bionic. [Steps to Reproduce] 1. Install ubuntu server (focal) on Sabre 2. lspci [Expected Result] L1d cache: 32K L1i cache: 32K L2 cache:256K L3 cache:32768K [Actual Result] L1d cache: 1.8 MiB L1i cache: 1.8 MiB L2 cache:14 MiB L3 cache:64 MiB [More Information] 1. eoan could reproduce this issue. 2. bionic-hwe could not reproduce this issue (5.3.0-46-generic #38~18.04.1-Ubuntu) 3. with focal, check the cpu cache directly from the virtual devices and the cache information looks good: $ cat /sys/devices/system/cpu/cpu0/cache/index0/level /sys/devices/system/cpu/cpu0/cache/index0/size 1 32K 4. More information about the system which could reproduce the issue: ubuntu@apollo:~$ cat /sys/devices/system/cpu/cpu0/cache/index0/level /sys/devices/system/cpu/cpu0/cache/index0/size 1 32K ubuntu@apollo:~$ uname -a Linux apollo 5.4.0-24-generic #28-Ubuntu SMP Thu Apr 9 22:17:51 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ubuntu@apollo:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal ubuntu@apollo:~$ dpkg -l util-linux Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii util-linux 2.34-0.1ubuntu9 arm64miscellaneous system utilities ubuntu@apollo:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: util-linux 2.34-0.1ubuntu9 ProcVersionSignature: User Name 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic aarch64 ApportVersion: 2.20.11-0ubuntu26 Architecture: arm64 CasperMD5CheckResult: skip Date: Fri Apr 17 16:00:13 2020 SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1873489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876621] [NEW] Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes
You have been subscribed to a public bug: In my configuration, the main monitor is landscape and the secondary monitor, to the right, is portrait. The most common result appears to be the primary display as seen by the DE being far wider than the actual monitor, and the second monitor being disabled entirely. Hitting "revert changes" usually doesn't actually change things back. Further, the xrandr CLI tool behaves strangely until the side monitor is removed from the layout entirely. Things behave as expected if the side monitor is set to landscape. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-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 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sun May 3 15:11:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6393] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=216c25da-8351-4944-9308-cf9b4ec2ba88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 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.:bvr2004:bd08/07/2014: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 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution ubuntu -- Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes https://bugs.launchpad.net/bugs/1876621 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage
Confirmed, I get the message in #1 every boot. 20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1873614 Title: Definition of add_mountroot_fail_hook doesnt match lvm2's usage Status in initramfs-tools: New Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Package lvm2 contains a init-premount script named /usr/share /initramfs-tools/scripts/init-premount/lvm2 In this script there is the function call: add_mountroot_fail_hook "20-lvm2" Which is defined in /usr/share/initramfs-tools/scripts/functions In focal's 0.136ubuntu6 , this is defined as: add_mountroot_fail_hook() { mkdir -p /tmp/mountroot-fail-hooks.d ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0" } The final line of the function will execute as ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2" And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does not exist. It is clear from lvm2's invocation that it expects the symlink to be named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is the case: add_mountroot_fail_hook() { mkdir -p /tmp/mountroot-fail-hooks.d ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1" } focal's version needs to be updated to either support the "$1" argument or strip the directory from "$0". To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1873614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876632] [NEW] Corrupted fonts in display output when using multiple users
Public bug reported: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 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 focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: Corrupted fonts in display output when using multiple users Status in xorg package in Ubuntu: New Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version:
[Touch-packages] [Bug 1876629] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound output/recording at all
Public bug reported: Updating the kernel from 4.15.0-91-generic to 4.15.0-99-generic caused all audio playback and recording to stop. Reverting to the old kernel corrects the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: etzhaim1677 F...m pulseaudio /dev/snd/controlC0: etzhaim1677 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 23:59:43 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-08 (815 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: etzhaim1677 F...m pulseaudio /dev/snd/controlC0: gdm1245 F pulseaudio etzhaim1677 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-08 (726 days ago) dmi.bios.date: 05/09/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 09NT72 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd05/09/2019:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn09NT72:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876629 Title: [HDA-Intel - HDA Intel PCH, playback] No sound output/recording at all Status in alsa-driver package in Ubuntu: New Bug description: Updating the kernel from 4.15.0-91-generic to 4.15.0-99-generic caused all audio playback and recording to stop. Reverting to the old kernel corrects the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: etzhaim1677 F...m pulseaudio /dev/snd/controlC0: etzhaim1677 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 23:59:43 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-08 (815 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: etzhaim1677 F...m pulseaudio /dev/snd/controlC0: gdm1245 F pulseaudio etzhaim1677 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-08 (726 days ago) dmi.bios.date: 05/09/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 09NT72 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd05/09/2019:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn09NT72:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875577] Re: Encrypted swap won't load on 20.04 with zfs root
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1875577 Title: Encrypted swap won't load on 20.04 with zfs root Status in systemd package in Ubuntu: Confirmed Bug description: root@eu1:/var/log# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal root@eu1:/var/log# apt-cache policy cryptsetup cryptsetup: Installed: (none) Candidate: 2:2.2.2-3ubuntu2 Version table: 2:2.2.2-3ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages OTHER BACKGROUND INFO: == 1. machine has 2 drives. each drive is partitioned into 2 partitions, zfs and swap 2. Ubuntu 20.04 installed on ZFS root using debootstrap (debootstrap_1.0.118ubuntu1_all) 3. The ZFS root pool is a 2 partition mirror (the first partition of each disk) 4. /etc/crypttab is set up as follows: swap /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 /dev/urandom swap,cipher=aes-xts-plain64,size=256 swap /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2 /dev/urandom swap,cipher=aes-xts-plain64,size=256 WHAT I EXPECTED === I expected machine would reboot and have encrypted swap that used two devices under /dev/mapper WHAT HAPPENED INSTEAD = On reboot, swap setup fails with the following messages in /var/log/syslog: Apr 28 17:13:01 eu1 kernel: [5.360793] systemd[1]: cryptsetup.target: Found ordering cycle on systemd-cryptsetup@swap.service/start Apr 28 17:13:01 eu1 kernel: [5.360795] systemd[1]: cryptsetup.target: Found dependency on systemd-random-seed.service/start Apr 28 17:13:01 eu1 kernel: [5.360796] systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Apr 28 17:13:01 eu1 kernel: [5.360797] systemd[1]: cryptsetup.target: Found dependency on zfs-load-module.service/start Apr 28 17:13:01 eu1 kernel: [5.360798] systemd[1]: cryptsetup.target: Found dependency on cryptsetup.target/start Apr 28 17:13:01 eu1 kernel: [5.360799] systemd[1]: cryptsetup.target: Job systemd-cryptsetup@swap.service/start deleted to break ordering cycle starting with cryptsetup.target/start . . . . . . Apr 28 17:13:01 eu1 kernel: [5.361082] systemd[1]: Unnecessary job for /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2 was removed Also, /dev/mapper does not contain any swap devices: root@eu1:/var/log# ls -l /dev/mapper total 0 crw--- 1 root root 10, 236 Apr 28 17:13 control root@eu1:/var/log# And top shows no swap: MiB Swap: 0.0 total, 0.0 free, 0.0 used. 63153.6 avail Mem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1875577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876610] Re: Thinkpad T480 Touchpad gets locked in scroll mode
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876610 Title: Thinkpad T480 Touchpad gets locked in scroll mode Status in xorg package in Ubuntu: New Bug description: My bug seems to be very similar to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635?comments=all at least in terms of perceptible problems. 1. Occasionally, some type of interaction with the touchpad puts it into a mode where it barely works. Seems it gets stuck in "scroll mode" or something similar. 2. Happens a couple times a week. 3. In my case, it seems to happen by brushing my left palm in the upper left corner of the touchpad. 4. Symptom: gliding my finger across the touchpad like normal does not work. The middle and right side of the touchpad seem to be in scroll mode, i.e. I can scroll a browser window up & down but I can't move the pointer around. If I use the upper and left borders, the pointer seems to work as normal. Physical clicking works, right click in the lower right quadrant doesn't work. It's almost like the middle and right side of the touchpad are operating as if every touch is a two finger touch. 5. In the past, it seemed as if nothing but a restart would get it out of this mode. However, while filing this bug report, I just realized that repeated two finger scrolls in the middle of the touchpad seemed to unlock it from scroll mode. Then again, this could be a fluke of time or something, since I usually restart before I let the problem go on this long. I'll test more and report back here the next time it happens. Happy to run commands to help troubleshoot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sun May 3 13:50:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6: added ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] MachineType: LENOVO 20L5CTO1WW ProcKernelCmdLine: \\vmlinuz-5.4.0-26-generic rw root=ZFS=sampro/ubuntu/root initrd=\initrd.img-5.4.0-26-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5CTO1WW dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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/1876610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876610] [NEW] Thinkpad T480 Touchpad gets locked in scroll mode
You have been subscribed to a public bug: My bug seems to be very similar to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635?comments=all at least in terms of perceptible problems. 1. Occasionally, some type of interaction with the touchpad puts it into a mode where it barely works. Seems it gets stuck in "scroll mode" or something similar. 2. Happens a couple times a week. 3. In my case, it seems to happen by brushing my left palm in the upper left corner of the touchpad. 4. Symptom: gliding my finger across the touchpad like normal does not work. The middle and right side of the touchpad seem to be in scroll mode, i.e. I can scroll a browser window up & down but I can't move the pointer around. If I use the upper and left borders, the pointer seems to work as normal. Physical clicking works, right click in the lower right quadrant doesn't work. It's almost like the middle and right side of the touchpad are operating as if every touch is a two finger touch. 5. In the past, it seemed as if nothing but a restart would get it out of this mode. However, while filing this bug report, I just realized that repeated two finger scrolls in the middle of the touchpad seemed to unlock it from scroll mode. Then again, this could be a fluke of time or something, since I usually restart before I let the problem go on this long. I'll test more and report back here the next time it happens. Happy to run commands to help troubleshoot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sun May 3 13:50:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6: added ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] MachineType: LENOVO 20L5CTO1WW ProcKernelCmdLine: \\vmlinuz-5.4.0-26-generic rw root=ZFS=sampro/ubuntu/root initrd=\initrd.img-5.4.0-26-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5CTO1WW dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Thinkpad T480 Touchpad gets locked in scroll mode https://bugs.launchpad.net/bugs/1876610 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Same problem with my OneAudio headset. I try to enable HSP/FSP profile and it says unavailable. It worked OK in 18.04 then I upgraded to 20.04 and it stopped working. 4 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA NVidia" alsa.long_card_name = "HDA NVidia at 0xf608 irq 65" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:07:00.1" sysfs.path = "/devices/pci:00/:00:03.1/:07:00.1/sound/card0" device.bus = "pci" device.vendor.id = "10de" device.vendor.name = "NVIDIA Corporation" device.product.id = "10f8" device.product.name = "TU104 HD Audio Controller" device.string = "0" device.description = "TU104 HD Audio Controller" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no) output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.pci-_07_00.1.hdmi-stereo/#5: TU104 HD Audio Controller Digital Stereo (HDMI) sources: alsa_output.pci-_07_00.1.hdmi-stereo.monitor/#7: Monitor of TU104 HD Audio Controller Digital Stereo (HDMI) ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: yes) properties: device.icon_name = "video-display" device.product.name = "34GL750 " hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-3: HDMI / DisplayPort 4 (priority 5600, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "2" alsa.card_name = "Valve VR Radio & HMD Mic" alsa.long_card_name = "Valve Corporation Valve VR Radio & HMD Mic at usb-:08:00.3-1.3.3, full spee" alsa.driver_name = "snd_usb_audio" device.bus_path = "pci-:08:00.3-usb-0:1.3.3:1.1" sysfs.path = "/devices/pci:00/:00:07.1/:08:00.3/usb5/5-1/5-1.3/5-1.3.3/5-1.3.3:1.1/sound/card2" udev.id = "usb-Valve_Corporation_Valve_VR_Radio___HMD_Mic_0F1B3BE619-LYM-01" device.bus = "usb" device.vendor.id = "28de" device.vendor.name = "Valve Software" device.product.id = "2102" device.product.name = "Valve VR Radio & HMD Mic" device.serial = "Valve_Corporation_Valve_VR_Radio___HMD_Mic_0F1B3BE619-LYM" device.string = "2" device.description = "Valve VR Radio & HMD Mic" module-udev-detect.discovered = "1" device.icon_name = "audio-card-usb" profiles: input:mono-fallback: Mono Input (priority 1, available: unknown) input:multichannel-input: Multichannel Input (priority 1, available: unknown) off: Off (priority 0, available: unknown)
[Touch-packages] [Bug 1876562] Re: Upgrade to 20.04 LTS errors - mkinitramfs failure cpio
This fixed my problem: sudo apt purge linux-image-4.15.0-99-generic from: https://askubuntu.com/questions/1207958/error-24-write-error-cannot-write-compressed-block Usually if it's a freespace thing, I'll get a popup about /boot not having enough space. That happened during upgrade process, but I wasn't able to purge old space, and it hasn't happened since finishing the upgrade. There is usually enough space for the current and previous kernel in /boot as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876562 Title: Upgrade to 20.04 LTS errors - mkinitramfs failure cpio Status in initramfs-tools package in Ubuntu: New Bug description: At the end of the upgrade process to 20.04 I got a message about mkinitramfs. It said I should consider submitting a bug. Now after a re-boot I get: $ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up initramfs-tools (0.136ubuntu6) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.136ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-28-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned erro r exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.136ubuntu6 Candidate: 0.136ubuntu6 Version table: *** 0.136ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 02:11:32 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-16 (1994 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876608] [NEW] display bright ness controlles do not working and touch screen is also not working
Public bug reported: Unable to increase or decrease the Display brightness is not work and touch screen is also not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 23:03:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20211 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=1162f9cd-5236-4def-aa6c-42bd3d241968 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad P400 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20211:pvrLenovoIdeaPadP400Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadP400Touch: dmi.product.family: IDEAPAD dmi.product.name: 20211 dmi.product.sku: LENOVO_MT_20211 dmi.product.version: Lenovo IdeaPad P400 Touch 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: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876608 Title: display bright ness controlles do not working and touch screen is also not working Status in xorg package in Ubuntu: New Bug description: Unable to increase or decrease the Display brightness is not work and touch screen is also not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 23:03:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20211 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=1162f9cd-5236-4def-aa6c-42bd3d241968 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad P400 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20211:pvrLenovoIdeaPadP400Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadP400Touch: dmi.product.family: IDEAPAD dmi.product.name: 20211 dmi.product.sku: LENOVO_MT_20211 dmi.product.version: Lenovo IdeaPad P400 Touch 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
[Touch-packages] [Bug 1712442] Re: Underscore not shown at some DejaVu mono fonts
Same here on a brand new xubuntu 20.04. I like the way text is condensed and the lines are sitting tight but missing underscores are a deal breaker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1712442 Title: Underscore not shown at some DejaVu mono fonts Status in fonts-dejavu package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.3 LTS, fonts-dejavu 2.35-1, mono underscore character is shown as space, issue seen: * first noticed at Tcl/Tk applications, see this https://core.tcl.tk/tk/tktview/6386ce66a48d530747763d5fa97d3c96f8584f73 (14pixel-sized mono font) and this https://core.tcl.tk/tk/tktview/d4e20ca3dc tickets there; * then I've met this font bug at Geany: DejaVu Sans Mono: 14, 17, all styles, and alike for Bitstream Vera Sans Mono at 14/17 sizes; set editor fonts (in preferences/interface) to these fonts, underscore disappears. Since it is both at a Gtk application (Geany) and Tcl/Tk applications, it should be a font issue. It seems that DejaVu Sans Mono have generally issues, thus setting some another font as the system default Mono font would be reasonable (Liberation Mono seems to work properly). Notice that mono fonts are commonly used for programming, and underscores are common in code, thus it is quite a problem to have spaces instead of underscores in system default mono font. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1712442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875796] Re: HP Envy 5530 printer/scanner does not work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1875796 Title: HP Envy 5530 printer/scanner does not work Status in cups package in Ubuntu: Confirmed Bug description: ubuntu 20.04 LTS see troubleshoot.txt please ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 29 08:15:00 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for ENVY_5530_series_CN4A5310HJ067B_: implicitclass://ENVY_5530_series_CN4A5310HJ067B_/ device for HP-ENVY-5530-series: hp:/usb/ENVY_5530_series?serial=CN4A5310HJ067B Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52e Logitech, Inc. MK260 Wireless Combo Receiver Bus 001 Device 003: ID 03f0:c311 HP, Inc ENVY 5530 series Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-ENVY-5530-series.ppd', '/etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-ENVY-5530-series.ppd: Permission denied grep: /etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd: Permission denied ProcEnviron: LANGUAGE=nl_BE:nl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=77c5fdfc-4b0d-48ce-93d9-8aba51f17f9b ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1875796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1712442] Re: Underscore not shown at some DejaVu mono fonts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fonts-dejavu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1712442 Title: Underscore not shown at some DejaVu mono fonts Status in fonts-dejavu package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.3 LTS, fonts-dejavu 2.35-1, mono underscore character is shown as space, issue seen: * first noticed at Tcl/Tk applications, see this https://core.tcl.tk/tk/tktview/6386ce66a48d530747763d5fa97d3c96f8584f73 (14pixel-sized mono font) and this https://core.tcl.tk/tk/tktview/d4e20ca3dc tickets there; * then I've met this font bug at Geany: DejaVu Sans Mono: 14, 17, all styles, and alike for Bitstream Vera Sans Mono at 14/17 sizes; set editor fonts (in preferences/interface) to these fonts, underscore disappears. Since it is both at a Gtk application (Geany) and Tcl/Tk applications, it should be a font issue. It seems that DejaVu Sans Mono have generally issues, thus setting some another font as the system default Mono font would be reasonable (Liberation Mono seems to work properly). Notice that mono fonts are commonly used for programming, and underscores are common in code, thus it is quite a problem to have spaces instead of underscores in system default mono font. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1712442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876606] [NEW] colord erros in varlog which causes display to fail
Public bug reported: Sometime I experience that I'm not able to login my Virutal Ubuntu Machine. Couldn't see any error pop-up. In varlog I see below errors at similar timings: 1049 May 3 18:53:10 KUMAR-PC colord[1135]: failed to get edid data: EDID length is too small 1054 May 3 18:53:11 KUMAR-PC gsd-color[1067]: failed to get edid: unable to get EDID for output 1055 May 3 18:53:11 KUMAR-PC gnome-shell[975]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation 1056 May 3 18:53:12 KUMAR-PC gsd-color[1067]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output Let me know if more info is needed. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: colord 1.3.3-2build1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 3 19:25:47 2020 InstallationDate: Installed on 2020-04-07 (26 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1876606 Title: colord erros in varlog which causes display to fail Status in colord package in Ubuntu: New Bug description: Sometime I experience that I'm not able to login my Virutal Ubuntu Machine. Couldn't see any error pop-up. In varlog I see below errors at similar timings: 1049 May 3 18:53:10 KUMAR-PC colord[1135]: failed to get edid data: EDID length is too small 1054 May 3 18:53:11 KUMAR-PC gsd-color[1067]: failed to get edid: unable to get EDID for output 1055 May 3 18:53:11 KUMAR-PC gnome-shell[975]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation 1056 May 3 18:53:12 KUMAR-PC gsd-color[1067]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output Let me know if more info is needed. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: colord 1.3.3-2build1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 3 19:25:47 2020 InstallationDate: Installed on 2020-04-07 (26 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1876606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876604] Re: The shortcut keys for paste does not work most of the times in Terminal. Shift+Ctrl+V for the given text.
Also, from other applications like chrome: when I try to open an incognito window using ctrl+shift+N, I can see similar behavior. Seems like the issue is with the Ctrl+Shift key combination. When I open a new tab, using Ctrl+n, it works flawlessly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1876604 Title: The shortcut keys for paste does not work most of the times in Terminal. Shift+Ctrl+V for the given text. Status in bash package in Ubuntu: New Bug description: The paste shortcut keys in terminal works sometimes. Please check the below use case: ~~ubuntu-bugVubuntu-bugvubuntu-bugvVvvubuntu-bug -Inspiron-553-Inspiron-553-Inspiron-553-Inspiron-553^V-Inspiron-553 ^Vv-Inspiron-553^Vvv-Inspiron-553-Inspiron-553VV- Inspiron-553-Inspiron-553-Inspiron-553vvVVVv-Inspiron-553 -Inspiron-553vVVV-Inspiron-553-Inspiron-553-Inspiron- 553vvv V or v: these cases it did not work. The paste works from the mouse right-click menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 22:36:39 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1876604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876604] [NEW] The shortcut keys for paste does not work most of the times in Terminal. Shift+Ctrl+V for the given text.
Public bug reported: The paste shortcut keys in terminal works sometimes. Please check the below use case: ~~ubuntu-bugVubuntu-bugvubuntu-bugvVvvubuntu-bug -Inspiron-553-Inspiron-553-Inspiron-553-Inspiron-553^V-Inspiron-553^Vv- Inspiron-553^Vvv-Inspiron-553-Inspiron-553VV-Inspiron-553-Inspiron-553 -Inspiron-553vvVVVv-Inspiron-553-Inspiron-553vVVV- Inspiron-553-Inspiron-553-Inspiron-553vvv V or v: these cases it did not work. The paste works from the mouse right-click menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 22:36:39 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1876604 Title: The shortcut keys for paste does not work most of the times in Terminal. Shift+Ctrl+V for the given text. Status in bash package in Ubuntu: New Bug description: The paste shortcut keys in terminal works sometimes. Please check the below use case: ~~ubuntu-bugVubuntu-bugvubuntu-bugvVvvubuntu-bug -Inspiron-553-Inspiron-553-Inspiron-553-Inspiron-553^V-Inspiron-553 ^Vv-Inspiron-553^Vvv-Inspiron-553-Inspiron-553VV- Inspiron-553-Inspiron-553-Inspiron-553vvVVVv-Inspiron-553 -Inspiron-553vVVV-Inspiron-553-Inspiron-553-Inspiron- 553vvv V or v: these cases it did not work. The paste works from the mouse right-click menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 22:36:39 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1876604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876600] [NEW] cookie overruns cause org.freedesktop.systemd1 dbus to hang
Public bug reported: [Impact] Long-running services overflow the sd_bus->cookie counter, causing further communication with org.freedesktop.systemd1 to stall. [Description] Systemd dbus messages usually include a "cookie" value to uniquely identify them in their bus context. For services that run for longer periods of time and keep communicating through dbus, it's possible to overflow the cookie value, causing further messages to the org.freedesktop.systemd1 dbus to hang. This has been fixed upstream by the commit below: - sd-bus: deal with cookie overruns (1f82f5bb4237) $ git describe --contains 1f82f5bb4237 v242-rc1~228 $ rmadison systemd systemd | 229-4ubuntu4 | xenial | source, ... systemd | 229-4ubuntu21.27 | xenial-security | source, ... systemd | 229-4ubuntu21.27 | xenial-updates | source, ... systemd | 229-4ubuntu21.28 | xenial-proposed | source, ... systemd | 237-3ubuntu10| bionic | source, ... systemd | 237-3ubuntu10.38 | bionic-security | source, ... systemd | 237-3ubuntu10.39 | bionic-updates | source, ... systemd | 237-3ubuntu10.40 | bionic-proposed | source, ... < systemd | 242-7ubuntu3 | eoan| source, ... Releases starting with Eoan already have this fix. [Test Case] There doesn't seem to be an easy test case for this, as the cookie values start at zero and won't overflow until (1<<32). There have been reports from users hitting this on Kubernetes clusters continuously running for longer periods (~5 months). ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1876600 Title: cookie overruns cause org.freedesktop.systemd1 dbus to hang Status in systemd package in Ubuntu: New Bug description: [Impact] Long-running services overflow the sd_bus->cookie counter, causing further communication with org.freedesktop.systemd1 to stall. [Description] Systemd dbus messages usually include a "cookie" value to uniquely identify them in their bus context. For services that run for longer periods of time and keep communicating through dbus, it's possible to overflow the cookie value, causing further messages to the org.freedesktop.systemd1 dbus to hang. This has been fixed upstream by the commit below: - sd-bus: deal with cookie overruns (1f82f5bb4237) $ git describe --contains 1f82f5bb4237 v242-rc1~228 $ rmadison systemd systemd | 229-4ubuntu4 | xenial | source, ... systemd | 229-4ubuntu21.27 | xenial-security | source, ... systemd | 229-4ubuntu21.27 | xenial-updates | source, ... systemd | 229-4ubuntu21.28 | xenial-proposed | source, ... systemd | 237-3ubuntu10| bionic | source, ... systemd | 237-3ubuntu10.38 | bionic-security | source, ... systemd | 237-3ubuntu10.39 | bionic-updates | source, ... systemd | 237-3ubuntu10.40 | bionic-proposed | source, ... < systemd | 242-7ubuntu3 | eoan| source, ... Releases starting with Eoan already have this fix. [Test Case] There doesn't seem to be an easy test case for this, as the cookie values start at zero and won't overflow until (1<<32). There have been reports from users hitting this on Kubernetes clusters continuously running for longer periods (~5 months). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876577] Re: fullscreen in browser and video player with fractional scaling(150%) enabled corrupted display
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876577 Title: fullscreen in browser and video player with fractional scaling(150%) enabled corrupted display Status in xorg package in Ubuntu: New Bug description: when fractional scaling is enabled for example 150%, trying to fullscreen the video playing in the browser or in the video player, display suddenly goes black, and then video resolution size is reduced to 1/4 of the actual screen size, with a still frame from the video as background and every app opened in the bacground becomes so large that it goes out of the window. also the mouse cursor stuck on the screen if auto login is disabled ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:20:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XL/XT [Radeon RX Vega 56/64] [1043:04c4] InstallationDate: Installed on 2020-04-24 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=a12e4265-d2f1-4a68-b9f4-840dc9e18df1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876577] [NEW] fullscreen in browser and video player with fractional scaling(150%) enabled corrupted display
You have been subscribed to a public bug: when fractional scaling is enabled for example 150%, trying to fullscreen the video playing in the browser or in the video player, display suddenly goes black, and then video resolution size is reduced to 1/4 of the actual screen size, with a still frame from the video as background and every app opened in the bacground becomes so large that it goes out of the window. also the mouse cursor stuck on the screen if auto login is disabled ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:20:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XL/XT [Radeon RX Vega 56/64] [1043:04c4] InstallationDate: Installed on 2020-04-24 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=a12e4265-d2f1-4a68-b9f4-840dc9e18df1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- fullscreen in browser and video player with fractional scaling(150%) enabled corrupted display https://bugs.launchpad.net/bugs/1876577 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
** Changed in: wpa (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Released Status in wpa package in Debian: New Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: New Status in gtk+3.0 package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gtk/issues/2457 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855350] Re: Will not logout or shutdown form guest-session
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1855350 Title: Will not logout or shutdown form guest-session Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: This is in Xubuntu 19.10, a regression from 18.04. xfce4-session 4.14.0-0ubuntu1. I enabled guest-session and logged in that. But there I can not log out or even shut down using the graphical way at least unless put Action Buttons on the panel and choose Switch User. If I run "xfce4-session-logout -l" I get error dialog saying: Received error while trying to log out GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs:Type of message, "(yb)", does not match expected type"(b)" And in standard output there is: "Received error while trying to log out, error was GDBus.Error:org.xfce.SessionManager.Error.Failed: Session manager must be in idle state when requesting a shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1855350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855350] Re: Will not logout or shutdown form guest-session
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xfce4-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1855350 Title: Will not logout or shutdown form guest-session Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: This is in Xubuntu 19.10, a regression from 18.04. xfce4-session 4.14.0-0ubuntu1. I enabled guest-session and logged in that. But there I can not log out or even shut down using the graphical way at least unless put Action Buttons on the panel and choose Switch User. If I run "xfce4-session-logout -l" I get error dialog saying: Received error while trying to log out GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs:Type of message, "(yb)", does not match expected type"(b)" And in standard output there is: "Received error while trying to log out, error was GDBus.Error:org.xfce.SessionManager.Error.Failed: Session manager must be in idle state when requesting a shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1855350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855350] Re: Will not logout or shutdown form guest-session
** Tags added: eoan focal ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1855350 Title: Will not logout or shutdown form guest-session Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: This is in Xubuntu 19.10, a regression from 18.04. xfce4-session 4.14.0-0ubuntu1. I enabled guest-session and logged in that. But there I can not log out or even shut down using the graphical way at least unless put Action Buttons on the panel and choose Switch User. If I run "xfce4-session-logout -l" I get error dialog saying: Received error while trying to log out GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs:Type of message, "(yb)", does not match expected type"(b)" And in standard output there is: "Received error while trying to log out, error was GDBus.Error:org.xfce.SessionManager.Error.Failed: Session manager must be in idle state when requesting a shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1855350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876197] Re: Xubuntu 20.04 Guest Session Logout Fails
*** This bug is a duplicate of bug 1855350 *** https://bugs.launchpad.net/bugs/1855350 ** This bug has been marked a duplicate of bug 1855350 Will not logout or shutdown form guest-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1876197 Title: Xubuntu 20.04 Guest Session Logout Fails Status in lightdm package in Ubuntu: New Bug description: I've edited "/usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf" so that it now has "allow-guest=true". And I'm now able to login to a Guest Session. But when I attempt to logout I get: Receiver error while trying to log out GDBus.Error.org .. Type of message "(yb)", does not match expected type "(b)" This occurs on both of the Xubuntu 20.04 machines I have, and also on a Virtualbox guest. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu3.1 Candidate: 1.30.0-0ubuntu3.1 Version table: *** 1.30.0-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1876197/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
sudo apt-get remove timidity I guess this affect the result. I remember I met the similar cases before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876516] Re: Mouse cursor lagging (or freezing) when moving over system tray when wayland session
** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1876516 Title: Mouse cursor lagging (or freezing) when moving over system tray when wayland session Status in gnome-shell package in Ubuntu: New Bug description: Cursor lagging when using wayland session. It happens on edge of something new, for example: - between clock menu and keyboard langugge - between app window and left launch panel Xorg session has no mouse lagging over this edges. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwayland-client0 1.18.0-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 23:10:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 6320] [144d:c600] InstallationDate: Installed on 2020-04-26 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=b242dbf0-fbe1-4cf8-a5a6-57dd5d749833 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 03PS.M505.20110929.LEO dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 305U1A/305U1A dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 03PS dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr03PS.M505.20110929.LEO:bd09/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr03PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr03PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: 305U1A dmi.product.sku: To be filled by O.E.M. dmi.product.version: 03PS dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Another correction. For the one workaround, switching to discrete graphics in the BIOS only seemed to get past the initial gnome login. But resuming from DPMS off/suspend, the same error loop happens even when hybrid graphics is disabled in the BIOS. Even worse, seems hardware acceleration ends up being disabled: $ journalctl --no-hostname -b -p warning _COMM=gnome-shell -- Logs begin at Wed 2019-02-06 14:13:52 SAST, end at Sun 2020-05-03 16:09:45 SAST. -- May 03 14:51:40 org.gnome.Shell.desktop[2284]: glamor: 'wl_drm' not supported May 03 14:51:40 org.gnome.Shell.desktop[2284]: Missing Wayland requirements for glamor GBM backend May 03 14:51:40 org.gnome.Shell.desktop[2284]: Failed to initialize glamor, falling back to sw ... May 03 14:53:25 gnome-shell[6549]: setup_framebuffers: assertion 'width > 0' failed The "EGL failed to allocate resources" error stops happening probably because gnome-shell isn't even using hardware acceleration now. I've also disabled all gnome shell extensions to avoid noise/errors in the logs and will try weed out the problem better. I checked `grep -C2 -E '(EE)|(WW)' /var/log/Xorg.0.log` and things seem fine: [45.181] (II) NVIDIA dlloader X Driver 440.59 Thu Jan 30 01:08:17 UTC 2020 [45.181] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs -- [45.182] (II) LoadModule: "ramdac" [45.182] (II) Module "ramdac" already built-in [45.183] (WW) Falling back to old probe method for modesetting [45.183] (II) NVIDIA(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 -- [46.392] (==) NVIDIA(0): Silken mouse enabled [46.392] (==) NVIDIA(0): DPMS enabled [46.393] (WW) NVIDIA(0): Option "PrimaryGPU" is not used [46.393] (II) Loading sub module "dri2" [46.393] (II) LoadModule: "dri2" Note, I've done no customisation to X config - trying to stick to defaults. xrandr confirms only one provider / hybrid is indeed off and Intel not in use: $ xrandr --listproviders Providers: number : 1 Provider 0: id: 0x218 cap: 0x1, Source Output crtcs: 4 outputs: 6 associated providers: 0 name:NVIDIA-0 I'm guessing the Lenovo P53 impliments a mux/switch to connect the laptop panel to the NVidia card so that Intel is disabled in this mode. And double checking, also no i915 modules are loaded: $ lsmod | grep '^drm' drm_kms_helper180224 1 nvidia_drm drm 491520 10 drm_kms_helper,nvidia_drm So there seems to be, on current Ubuntu 18.04.4 LTS (fully up to date as of today), a 4K / UHD 60Hz issue with Nvidia, as seen in X log [45.228] (II) NVIDIA GLX Module 440.59 Thu Jan 30 01:05:38 UTC 2020 Lastly, I think due to `needs_root_rights=yes` in /etc/X11/Xwrapper.config, X logs to /var/log/Xorg.0.log again instead of the X without root which used to log at ~/.local/share/xorg/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Apologies, continuing the comment above (mistakenly posted when adding the log attachment). Let me retry. Failure loop observed: - Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. - Failed to set CRTC mode 3840x2160: No such file or directory To summarise and share my experience of it on a Lenovo P53 and some quirks/workarounds: - `sudo ubuntu-drivers autoinstall` got Nvidia 440.59 drivers installed. - However, Nvidia modeset was not enabled as yet. $ sudo cat /sys/module/nvidia_drm/parameters/modeset N - Blank external screen occurs with modeset=0 (disabled) - Then, using `prime-select nvidia`, I tried to ensure nvidia was primary - `prime-select nvidia` sets `options nvidia-drm modeset=1` but it's not effective, even after I rebooted ~$ cat /lib/modprobe.d/nvidia-kms.conf # This file was generated by nvidia-prime # Set value to 0 to disable modesetting options nvidia-drm modeset=1 - To make it effective, because modeset is done during initramfs part of boot, I ran `sudo update-initramfs -u -k all`. - It seems the prime-select option fails to trigger a intiramfs update (probably should be filed as a separate bug) - Regardless, the blank screen issue occured on my Lenovo P53 with or without Nvidia KMS modeset enabled - But one benefit of KMS modeset for Nvida is now the external display gets properly recognised. /sys/class/drm/card1-HDMI-A-1/ now exists (was missing with Ubuntu 18.04.4 LTS default proprietary install) including the EDID data being read properly and X getting the actual DPI of the screen correctly. Without nvidia modeset, as seen in `journalctl -b _COMM=gdm-x-session | grep -C2 -E '(EE)|(WW)'`: (WW) NVIDIA(0): Unable to get display device for DPI computation. With nvidia modeset: (II) NVIDIA(0): Validated MetaModes: (II) NVIDIA(0): "DFP-3:nvidia-auto-select" (II) NVIDIA(0): Virtual screen size determined to be 3840 x 2160 (--) NVIDIA(0): DPI set to (139, 140); computed from "UseEdidDpi" X config I've also found two workarounds to my issue. 1. Run a script that sets the frequency to 30HZ and then back to 60HZ 2. Switch to discrete only graphics in the BIOS In most cases, when one is using a 2nd display, there's usually a powersource available so the complexity of hybrid graphics isn't worth it and I went with simply disabling hybrid graphics in the BIOS. It's quite interesting that toggling the display refresh rate down to 30HZ and then back up to 60HZ seems to work around the problem of gnome- shell mutter's "EGL failed to allocate resources for the requested operation" bug. To conclude, even with the root access workaround in place: $ tail -n 2 /etc/X11/Xwrapper.config # Added by xserver-xorg-video-nvidia-440 needs_root_rights=yes I still had external display connection issues with 4K 60Hz. This might need to be logged as different bug? I'm unsure it's GDM3s fault given the root workaround was in place, but it's highly related/similar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Here's the script I run to workaround the intital failure of gnome to use the external display after unlocking or resuming from DPMS suspend/off. ** Attachment added: "fix-hdmi-uhd.sh" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365719/+files/fix-hdmi-uhd.sh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
** Bug watch added: Debian Bug tracker #954457 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954457 ** Also affects: wpa (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954457 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Released Status in wpa package in Debian: Unknown Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Hi, thanks to everyone, especially Daniel for unpacking this issue. I have had a very similar issue, where gnome shell fails to run my external 4K/UHD display at 60HZ and I see the following failure loop triggered in `journalctl -b -p warning _COMM=gnome-shell`: May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to flip: Device or resource busy May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory ... While not sure it's exactly the same, it should still inform the overall discussion about dealing with GDM3 + Mutter + proprietary Nvidia drivers modeset problems. To summarise and share my experience of it on a Lenovo P53 and some quirks/workarounds: - `sudo ubuntu-drivers autoinstall` got Nvidia 440.59 drivers installed. - However, Nvidia modeset was not enabled as yet. $ sudo cat /sys/module/nvidia_drm/parameters/modeset N - - Using prime-select - For laptops like mine, seems the external port is connected to the Nvidia GPU. - Using the proprietary Nvidia drivers seems to then bump into a ** Attachment added: "gnome-shell_journal_warnings_egl_resource_failed.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365716/+files/gnome-shell_journal_warnings_egl_resource_failed.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876570] Re: Could not resume from hibernation when swap is specified as device
The attachment "resume.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: New Bug description: I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
Reply to #12. Lenovo ThinkPad T400 has an internal sound card. So unplugging it sounds a bit challenging. Removed all the music software installations AND I CAN HEAR MUSIC! CASE SOLVED! Thanks!! === sudo apt-get remove lmms sudo apt-get remove ardour sudo apt-get remove qsynth sudo apt-get remove guitarix sudo apt-get remove timidity sudo apt-get update sudo apt-get upgrade sudo apt-get dist-update sudo apt-get autoremove reboot === -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876534] Re: ThinkPad P72 - Very serious issues with external monitors on Thunderbolt dock
** Description changed: I'm running Ubuntu 20.04 LTS on a ThinkPad P72 with a Quadro P5200. I recently purchased the ThinkPad Workstation Dock Gen2 and have been having issues with external displays on it. There are a multitude of issues with this. Sometimes you can plug in displays and both will show up fine after running xrandr --auto. Sometimes only one will appear and the other will stay black. There is a chance for any of these things to happen after making a display configuration change: - Nothing (displays work fine) - One display stays black - All displays including laptop internal display freeze, which is recoverable only by physically disconnecting the displays from the dock - Displays flicker on and off rapidly before every one goes dark including the laptop's internal display, requiring a hard reset. I have tried: - Upgrading to a newer kernel version (5.6.7) via mainline - Upgrading all system firmware, including dock, to latest via Lenovo Vantage in Windows dual boot - Downgrading the dock firmware from 3166 to 3164 - despite suggestions by people in this thread in the Lenovo community https://forums.lenovo.com/t5/Ubuntu/Thinkpad-P1-Gen2-amp-Thunderbolt-3-Workstation-Dock-amp-Linux-Ubuntu-Monitor-s-black/m-p/4575709?page=3 - this did not work - Downgrading the NVIDIA driver version to both 435 and 390 - neither worked + Downgrading to an older kernel (4.19) appears to work, but it still has + some issues with locking up while repositioning displays using xrandr. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 + GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun May 3 00:37:27 2020 DistUpgraded: 2020-03-04 19:48:20,592 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - acpi-call, 1.1.0, 5.4.0-28-generic, x86_64: installed - nvidia, 440.64, 5.4.0-28-generic, x86_64: installed - v4l2loopback, 0.12.3, 5.4.0-28-generic, x86_64: installed - wireguard, 1.0.20200413, 5.4.0-28-generic, x86_64: installed (WARNING! Diff between built and installed module!) + acpi-call, 1.1.0, 5.4.0-28-generic, x86_64: installed + nvidia, 440.64, 5.4.0-28-generic, x86_64: installed + v4l2loopback, 0.12.3, 5.4.0-28-generic, x86_64: installed + wireguard, 1.0.20200413, 5.4.0-28-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: - Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:2269] - NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269] + Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:2269] + NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269] InstallationDate: Installed on 2019-10-19 (196 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20MCS08200 ProcEnviron: - LANGUAGE=en_GB:en - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=on default_hugepagesz=1G hugepagesz=1G hugepages=32 transparent_hugepage=never vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-03-04 (59 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2CET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MCS08200
[Touch-packages] [Bug 1876570] [NEW] Could not resume from hibernation when swap is specified as device
Public bug reported: I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. >From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Patch added: "resume.patch" https://bugs.launchpad.net/bugs/1876570/+attachment/5365684/+files/resume.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: New Bug description: I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742804] Re: Failed to add PIDs to scope's control group
> status: Unknown → Fix Released Still affects me too. I don't see fix released for Bionic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1742804 Title: Failed to add PIDs to scope's control group Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Bug description: [impact] systemd-run --user --scope fails [test case] $ systemd-run --user --scope echo hello Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed. See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and "journalctl -xe" for details. [regression potential] large. this is fixed upstream by a large sequence of patches, and would need careful attention applying them all to make sure no regressions were introduced. If I, or anyone else, attempts this backport, they definitely need to add more detail to this section. [scope] This is fixed upstream by this large PR: https://github.com/systemd/systemd/pull/8125 That's included starting in systemd v238, so just missed the Bionic version. This is fixed already in all releases after Bionic, and needed only for Bionic. [original description] When I launch applications with flatpak, "journalctl -f" shows the following: Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: Failed to add PIDs to scope's control group: Permission denied Jan 11 22:44:13 localhost systemd[1244]: Failed to start flatpak-org.kde.krita-8134.scope. Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: Unit entered failed state. I explicitly mentioned "Kubuntu" in the summary, because I experience this only under Kubuntu (17.10 and 18.04), NOT under the regular Gnome-based Ubuntu Desktop (17.10). At first this error message seemed harmless, because it looked like it had no effect. But now I noticed that with certain flatpak apps, the file open dialog would not pop up. And I too experienced this only under Kubuntu, not Ubuntu or Fedora (all tested). So there might be a connection. I first reported this to flatpak: https://github.com/flatpak/flatpak/issues/1216 There it was suggested to try the following command: $ systemd-run --user --scope echo hello Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed. See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and "journalctl -xe" for details. ...and this one also fails. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1742804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]
I have the same issue with Ubuntu 20.04 on arm64 (RaspberryPi 4 B). I have even tried to uninstall the apparmor* packages to ensure that its not an apparmor issue. Primary DHCP configuration: root@dexter:~# grep -E -v "^#|^$" /etc/dhcp/dhcpd-common.conf ddns-update-style none; option all-subnets-local true; option domain-name "se.lemche.net"; option domain-name-servers 192.168.1.3, 192.168.1.4; default-lease-time 600; max-lease-time 7200; authoritative; subnet 192.168.1.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option routers 192.168.1.254; option domain-name "pc.se.lemche.net"; option domain-search "pc.se.lemche.net","se.lemche.net","lemche.net"; pool { failover peer "dhcp-failover"; range 192.168.1.94 192.168.1.126; } } root@dexter:~# grep -E -v "^#|^$" /etc/dhcp/dhcpd.conf server-name "dexter"; failover peer "dhcp-failover" { primary; address 192.168.1.3; port 520; peer address 192.168.1.4; peer port 520; max-response-delay 60; max-unacked-updates 10; load balance max seconds 3; mclt 3600; split 128; } include "/etc/dhcp/dhcpd-common.conf"; root@dexter:~# grep -E -v "^#|^$" /etc/default/isc-dhcp-server OPTIONS="-4" INTERFACESv4="inside" INTERFACESv6="" root@dexter:~# dpkg -l isc-dhcp-server Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ii isc-dhcp-server 4.4.1-2.1ubuntu5 arm64ISC DHCP server for automatic IP address assignment root@dexter:~# Secondary DHCP configuration: root@didi:~# grep -E -v "^#|^$" /etc/dhcp/dhcpd-common.conf ddns-update-style none; option all-subnets-local true; option domain-name "se.lemche.net"; option domain-name-servers 192.168.1.3, 192.168.1.4; default-lease-time 600; max-lease-time 7200; authoritative; subnet 192.168.1.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option routers 192.168.1.254; option domain-name "pc.se.lemche.net"; option domain-search "pc.se.lemche.net","se.lemche.net","lemche.net"; pool { failover peer "dhcp-failover"; range 192.168.1.94 192.168.1.126; } } root@didi:~# grep -E -v "^#|^$" /etc/dhcp/dhcpd.conf server-name "didi"; failover peer "dhcp-failover" { secondary; address 192.168.1.4; port 520; peer address 192.168.1.3; peer port 520; max-response-delay 60; max-unacked-updates 10; load balance max seconds 3; } include "/etc/dhcp/dhcpd-common.conf"; root@didi:~# grep -E -v "^#|^$" /etc/default/isc-dhcp-server OPTIONS="-4" INTERFACESv4="inside" INTERFACESv6="" root@didi:~# dpkg -l isc-dhcp-server Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ii isc-dhcp-server 4.4.1-2.1ubuntu5 arm64ISC DHCP server for automatic IP address assignment Messages on my loghost when I first start the primary, and then the secondary: May 3 12:23:59 dexter systemd[1]: Started ISC DHCP IPv4 server. May 3 12:23:59 dexter dhcpd[1797]: Internet Systems Consortium DHCP Server 4.4.1 May 3 12:23:59 dexter sh[1797]: Internet Systems Consortium DHCP Server 4.4.1 May 3 12:23:59 dexter sh[1797]: Copyright 2004-2018 Internet Systems Consortium. May 3 12:23:59 dexter sh[1797]: All rights reserved. May 3 12:23:59 dexter sh[1797]: For info, please visit https://www.isc.org/software/dhcp/ May 3 12:23:59 dexter dhcpd[1797]: Copyright 2004-2018 Internet Systems Consortium. May 3 12:23:59 dexter dhcpd[1797]: All rights reserved. May 3 12:23:59 dexter dhcpd[1797]: For info, please visit https://www.isc.org/software/dhcp/ May 3 12:23:59 dexter dhcpd[1797]: Config file: /etc/dhcp/dhcpd.conf May 3 12:23:59 dexter sh[1797]: Config file: /etc/dhcp/dhcpd.conf May 3 12:23:59 dexter sh[1797]: Database file: /var/lib/dhcp/dhcpd.leases May 3 12:23:59 dexter sh[1797]: PID file: /run/dhcp-server/dhcpd.pid May 3 12:23:59 dexter dhcpd[1797]: Database file: /var/lib/dhcp/dhcpd.leases May 3 12:23:59 dexter sh[1797]: Wrote 0 leases to leases file. May 3 12:23:59 dexter dhcpd[1797]: PID file: /run/dhcp-server/dhcpd.pid May 3 12:23:59 dexter dhcpd[1797]: Wrote 0 leases to leases file. May 3 12:23:59 dexter dhcpd[1797]: Listening on LPF/inside/dc:a6:32:86:5f:84/192.168.1.0/24 May 3 12:23:59 dexter sh[1797]: Listening on LPF/inside/dc:a6:32:86:5f:84/192.168.1.0/24 May 3 12:23:59 dexter sh[1797]: Sending on LPF/inside/dc:a6:32:86:5f:84/192.168.1.0/24 May 3 12:23:59 dexter sh[1797]: No subnet declaration for management (192.168.0.3). May 3 12:23:59 dexter sh[1797]: **
[Touch-packages] [Bug 1876562] [NEW] Upgrade to 20.04 LTS errors - mkinitramfs failure cpio
Public bug reported: At the end of the upgrade process to 20.04 I got a message about mkinitramfs. It said I should consider submitting a bug. Now after a re-boot I get: $ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up initramfs-tools (0.136ubuntu6) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.136ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-28-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned erro r exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 $ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.136ubuntu6 Candidate: 0.136ubuntu6 Version table: *** 0.136ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 02:11:32 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-16 (1994 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-03 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot of error I saw during upgrade process" https://bugs.launchpad.net/bugs/1876562/+attachment/5365616/+files/upgrade_error_screenshot.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876562 Title: Upgrade to 20.04 LTS errors - mkinitramfs failure cpio Status in initramfs-tools package in Ubuntu: New Bug description: At the end of the upgrade process to 20.04 I got a message about mkinitramfs. It said I should consider submitting a bug. Now after a re-boot I get: $ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up initramfs-tools (0.136ubuntu6) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.136ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-28-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned erro r exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.136ubuntu6 Candidate: 0.136ubuntu6 Version table: *** 0.136ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 02:11:32 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-16 (1994 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to focal on 2020-05-03 (0 days ago) To manage notifications about this bug go to:
[Touch-packages] [Bug 1876555] Re: Apps cannot retrieve internal mic input
Some additional info for bug report: $ ls /lib/modules/5.3.0-51-generic/kernel/sound/drivers mpu401 snd-aloop.ko snd-mts64.ko snd-virmidi.ko opl3snd-dummy.ko snd-portman2x4.ko vx pcspsnd-mtpav.ko snd-serial-u16550.ko ~$ ls /lib/firmware/cs46xx/ ba1 cwc4630 cwcasync cwcbinhack cwcdma cwcsnoop ~$ modinfo snd-cs46xx filename: /lib/modules/5.3.0-51-generic/kernel/sound/pci/cs46xx/snd-cs46xx.ko license:GPL description:Cirrus Logic Sound Fusion CS46XX author: Jaroslav Kysela firmware: cs46xx/cwcdma firmware: cs46xx/cwcbinhack firmware: cs46xx/cwcsnoop firmware: cs46xx/cwcasync firmware: cs46xx/cwc4630 srcversion: 11FF4360F4C97088F132FB1 alias: pci:v1013d6004sv*sd*bc*sc*i* alias: pci:v1013d6003sv*sd*bc*sc*i* alias: pci:v1013d6001sv*sd*bc*sc*i* depends:snd-pcm,snd-ac97-codec,snd,snd-rawmidi,gameport retpoline: Y intree: Y name: snd_cs46xx vermagic: 5.3.0-51-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: index:Index value for the CS46xx soundcard. (array of int) parm: id:ID string for the CS46xx soundcard. (array of charp) parm: enable:Enable CS46xx soundcard. (array of bool) parm: external_amp:Force to enable external amplifier. (array of bool) parm: thinkpad:Force to enable Thinkpad's CLKRUN control. (array of bool) parm: mmap_valid:Support OSS mmap. (array of bool) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876555 Title: Apps cannot retrieve internal mic input Status in alsa-driver package in Ubuntu: New Bug description: Could be pulseaudio, alsa-driver, or ~$ /usr/bin/gnome-control-center sound input Dell Vostro 2520 dual-boot laptop Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 2- Cirrus Logic High Definition Audio, model CS4213 Ubuntu 18.04.4 LTS Windows 10 Home, v. 1903, bld 18362.778 Skype 8.59 (Ubu & Win) Zoom (cloud meetings) 5.0.3x (Ubu), 5.0.1x (Win) pulseaudio 1:11.1-1ubuntu7.5 alsa-driver -- package could not be found: ~$ apt-cache policy alsa-driver N: Unable to locate package alsa-driver Does this help? /lib/modules/5.3.0-51-generic/kernel/sound/drivers In Settings > Sound > Input, the On/Off [unmute/mute] setting *appearance* is preserved over reboots and awakenings from sleep, but the mic input sound is always muted despite the control still being set to On (unmute). Clicking mute (Off), then unmute (On) restores mic input, as shown by the level meter tracking input sounds. However, Skype 8.59x and Zoom 5.0.3x cannot receive sound inputs *despite* their sound level meters (in their respective sound settings) registering changing input levels. The Skype test call does not work. I opened a Zoom meeting with my wife on her Win 10 computer. I could see and hear her, and she could see but not hear me. On this dual-boot laptop, Skype 8.59x fails the test call under Windows 10 Home. The Sound Recorder app can successfully record mic input and play it back. pavucontrol shows input on its level meter. Notes: + ~$ /usr/bin/gnome-control-center sound input (gnome-control-center:17284): sound-cc-panel-WARNING **: 16:48:28.795: Couldn't find a stream from the active input + Many days searching the internet and AskUbuntu have not produced a solution that works. (For what it is worth, many posters have reported that sound became dysfunctional after upgrading to 18.04 or 18.04.4.) + I have added the snd-cs46xx kernel module and firmware to get around driver licensing issues following the instructions at https://wiki.debian.org/snd-cs46xx, Debian 8. + I have added these lines to /etc/modprobe.d/alsa-base.conf : options snd-hda-intel model=dell-vostro-2520 options snd-hda-intel dmic_detect=0 + In PulseAudio Volume Control I have set the following: Input Devices Port: Internal Microphone Output Devices Port: Speakers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hfinger4047 F pulseaudio /dev/snd/pcmC0D0c: hfinger4047 F...m pulseaudio /dev/snd/pcmC0D0p: hfinger4047 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 16:52:35 2020 InstallationDate: Installed on 2020-04-15 (17 days ago)
[Touch-packages] [Bug 1876555] Re: Apps cannot retrieve internal mic input
Did the internal mic work before? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876555 Title: Apps cannot retrieve internal mic input Status in alsa-driver package in Ubuntu: New Bug description: Could be pulseaudio, alsa-driver, or ~$ /usr/bin/gnome-control-center sound input Dell Vostro 2520 dual-boot laptop Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 2- Cirrus Logic High Definition Audio, model CS4213 Ubuntu 18.04.4 LTS Windows 10 Home, v. 1903, bld 18362.778 Skype 8.59 (Ubu & Win) Zoom (cloud meetings) 5.0.3x (Ubu), 5.0.1x (Win) pulseaudio 1:11.1-1ubuntu7.5 alsa-driver -- package could not be found: ~$ apt-cache policy alsa-driver N: Unable to locate package alsa-driver Does this help? /lib/modules/5.3.0-51-generic/kernel/sound/drivers In Settings > Sound > Input, the On/Off [unmute/mute] setting *appearance* is preserved over reboots and awakenings from sleep, but the mic input sound is always muted despite the control still being set to On (unmute). Clicking mute (Off), then unmute (On) restores mic input, as shown by the level meter tracking input sounds. However, Skype 8.59x and Zoom 5.0.3x cannot receive sound inputs *despite* their sound level meters (in their respective sound settings) registering changing input levels. The Skype test call does not work. I opened a Zoom meeting with my wife on her Win 10 computer. I could see and hear her, and she could see but not hear me. On this dual-boot laptop, Skype 8.59x fails the test call under Windows 10 Home. The Sound Recorder app can successfully record mic input and play it back. pavucontrol shows input on its level meter. Notes: + ~$ /usr/bin/gnome-control-center sound input (gnome-control-center:17284): sound-cc-panel-WARNING **: 16:48:28.795: Couldn't find a stream from the active input + Many days searching the internet and AskUbuntu have not produced a solution that works. (For what it is worth, many posters have reported that sound became dysfunctional after upgrading to 18.04 or 18.04.4.) + I have added the snd-cs46xx kernel module and firmware to get around driver licensing issues following the instructions at https://wiki.debian.org/snd-cs46xx, Debian 8. + I have added these lines to /etc/modprobe.d/alsa-base.conf : options snd-hda-intel model=dell-vostro-2520 options snd-hda-intel dmic_detect=0 + In PulseAudio Volume Control I have set the following: Input Devices Port: Internal Microphone Output Devices Port: Speakers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hfinger4047 F pulseaudio /dev/snd/pcmC0D0c: hfinger4047 F...m pulseaudio /dev/snd/pcmC0D0p: hfinger4047 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 16:52:35 2020 InstallationDate: Installed on 2020-04-15 (17 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [Vostro 2520, Cirrus Logic CS4213, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0FWKV7 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd01/25/2013:svnDellInc.:pnVostro2520:pvrNotSpecified:rvnDellInc.:rn0FWKV7:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 2520 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-01T13:58:36.978996 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876555] Re: Apps cannot retrieve internal mic input
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876555 Title: Apps cannot retrieve internal mic input Status in alsa-driver package in Ubuntu: New Bug description: Could be pulseaudio, alsa-driver, or ~$ /usr/bin/gnome-control-center sound input Dell Vostro 2520 dual-boot laptop Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 2- Cirrus Logic High Definition Audio, model CS4213 Ubuntu 18.04.4 LTS Windows 10 Home, v. 1903, bld 18362.778 Skype 8.59 (Ubu & Win) Zoom (cloud meetings) 5.0.3x (Ubu), 5.0.1x (Win) pulseaudio 1:11.1-1ubuntu7.5 alsa-driver -- package could not be found: ~$ apt-cache policy alsa-driver N: Unable to locate package alsa-driver Does this help? /lib/modules/5.3.0-51-generic/kernel/sound/drivers In Settings > Sound > Input, the On/Off [unmute/mute] setting *appearance* is preserved over reboots and awakenings from sleep, but the mic input sound is always muted despite the control still being set to On (unmute). Clicking mute (Off), then unmute (On) restores mic input, as shown by the level meter tracking input sounds. However, Skype 8.59x and Zoom 5.0.3x cannot receive sound inputs *despite* their sound level meters (in their respective sound settings) registering changing input levels. The Skype test call does not work. I opened a Zoom meeting with my wife on her Win 10 computer. I could see and hear her, and she could see but not hear me. On this dual-boot laptop, Skype 8.59x fails the test call under Windows 10 Home. The Sound Recorder app can successfully record mic input and play it back. pavucontrol shows input on its level meter. Notes: + ~$ /usr/bin/gnome-control-center sound input (gnome-control-center:17284): sound-cc-panel-WARNING **: 16:48:28.795: Couldn't find a stream from the active input + Many days searching the internet and AskUbuntu have not produced a solution that works. (For what it is worth, many posters have reported that sound became dysfunctional after upgrading to 18.04 or 18.04.4.) + I have added the snd-cs46xx kernel module and firmware to get around driver licensing issues following the instructions at https://wiki.debian.org/snd-cs46xx, Debian 8. + I have added these lines to /etc/modprobe.d/alsa-base.conf : options snd-hda-intel model=dell-vostro-2520 options snd-hda-intel dmic_detect=0 + In PulseAudio Volume Control I have set the following: Input Devices Port: Internal Microphone Output Devices Port: Speakers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hfinger4047 F pulseaudio /dev/snd/pcmC0D0c: hfinger4047 F...m pulseaudio /dev/snd/pcmC0D0p: hfinger4047 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 16:52:35 2020 InstallationDate: Installed on 2020-04-15 (17 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [Vostro 2520, Cirrus Logic CS4213, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0FWKV7 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd01/25/2013:svnDellInc.:pnVostro2520:pvrNotSpecified:rvnDellInc.:rn0FWKV7:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 2520 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-01T13:58:36.978996 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1876555] [NEW] Apps cannot retrieve internal mic input
You have been subscribed to a public bug: Could be pulseaudio, alsa-driver, or ~$ /usr/bin/gnome-control-center sound input Dell Vostro 2520 dual-boot laptop Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 2- Cirrus Logic High Definition Audio, model CS4213 Ubuntu 18.04.4 LTS Windows 10 Home, v. 1903, bld 18362.778 Skype 8.59 (Ubu & Win) Zoom (cloud meetings) 5.0.3x (Ubu), 5.0.1x (Win) pulseaudio 1:11.1-1ubuntu7.5 alsa-driver -- package could not be found: ~$ apt-cache policy alsa-driver N: Unable to locate package alsa-driver Does this help? /lib/modules/5.3.0-51-generic/kernel/sound/drivers In Settings > Sound > Input, the On/Off [unmute/mute] setting *appearance* is preserved over reboots and awakenings from sleep, but the mic input sound is always muted despite the control still being set to On (unmute). Clicking mute (Off), then unmute (On) restores mic input, as shown by the level meter tracking input sounds. However, Skype 8.59x and Zoom 5.0.3x cannot receive sound inputs *despite* their sound level meters (in their respective sound settings) registering changing input levels. The Skype test call does not work. I opened a Zoom meeting with my wife on her Win 10 computer. I could see and hear her, and she could see but not hear me. On this dual-boot laptop, Skype 8.59x fails the test call under Windows 10 Home. The Sound Recorder app can successfully record mic input and play it back. pavucontrol shows input on its level meter. Notes: + ~$ /usr/bin/gnome-control-center sound input (gnome-control-center:17284): sound-cc-panel-WARNING **: 16:48:28.795: Couldn't find a stream from the active input + Many days searching the internet and AskUbuntu have not produced a solution that works. (For what it is worth, many posters have reported that sound became dysfunctional after upgrading to 18.04 or 18.04.4.) + I have added the snd-cs46xx kernel module and firmware to get around driver licensing issues following the instructions at https://wiki.debian.org/snd-cs46xx, Debian 8. + I have added these lines to /etc/modprobe.d/alsa-base.conf : options snd-hda-intel model=dell-vostro-2520 options snd-hda-intel dmic_detect=0 + In PulseAudio Volume Control I have set the following: Input Devices Port: Internal Microphone Output Devices Port: Speakers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hfinger4047 F pulseaudio /dev/snd/pcmC0D0c: hfinger4047 F...m pulseaudio /dev/snd/pcmC0D0p: hfinger4047 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 16:52:35 2020 InstallationDate: Installed on 2020-04-15 (17 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [Vostro 2520, Cirrus Logic CS4213, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0FWKV7 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd01/25/2013:svnDellInc.:pnVostro2520:pvrNotSpecified:rvnDellInc.:rn0FWKV7:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 2520 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-01T13:58:36.978996 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa amd64 apport-bug bionic internal-microphone pulseaudio sound -- Apps cannot retrieve internal mic input https://bugs.launchpad.net/bugs/1876555 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1874812] Re: package mime-support 3.64ubuntu1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mime-support (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1874812 Title: package mime-support 3.64ubuntu1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 Status in mime-support package in Ubuntu: Confirmed Bug description: just appeared when i booted my ubuntu 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 15:16:53 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2019-12-10 (135 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: mime-support Title: package mime-support 3.64ubuntu1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1874812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp