[Desktop-packages] [Bug 1882610] Re: Lenovo E590 Graphics problems using standard Ubuntu/Budgie install
It sounds like you experienced bug 1867668. Please explain in more detail what, if any, issue remains. Please also be careful to only discuss one issue per bug report. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1882610 Title: Lenovo E590 Graphics problems using standard Ubuntu/Budgie install Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Ive had major problems (seg errors and various) stopping several apps which were all working a couple of months ago, on my new Lenovo E590 Thinkpad notebook. sudo lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) What helped me sort it was the following command: sudo lshw -C display which showed the driver was xserver-xorg-video-intel which is not recommended; its older and problematic. Aptitude recommends use system default which is driver=i915). After removing this errant driver, its solved my applications crashing problems and more. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Jun 9 12:42:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:5072] InstallationDate: Installed on 2020-01-23 (137 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) LightdmDisplayLog: (EE) event4 - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded. See https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html for details (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-1435ms), your system is too slow (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-821ms), your system is too slow (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-204ms), your system is too slow Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:2130 Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 008: ID 14cd:6600 Super Top M110E PATA bridge Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=fab243f0-09ed-4b95-8ed6-995ffdde426c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET42W(1.25):bd01/13/2020:svnLENOVO:pn20NBCTO1WW:pvrThinkPadE590:rvnLENOVO:rn20NBCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E590 dmi.product.name: 20NBCTO1WW dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590 dmi.product.version: ThinkPad E590 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1882610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882631] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: amdgpu ** Summary changed: - Xorg crash + [amdgpu] Xorg crash ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1882631 Title: [amdgpu] Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: many time system hangs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 9 10:50:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H 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.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.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882607] Re: One of the updates in the last week broke super key on external usb keyboard
Please install 'evtest' and then run: sudo evtest and select the keyboard. Now tap the Super key and tell us what 'evtest' reports for it. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1882607 Title: One of the updates in the last week broke super key on external usb keyboard Status in mutter package in Ubuntu: Incomplete Bug description: Worked fine until recent reboot. Now the super key on the external keyboard connected to a dock via thunderbolt port does not work. It still works on internal laptop keyboard. Tried switching to a few different languages but had no effect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b: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) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 18:41:32 2020 DistUpgraded: 2020-03-26 17:17:00,893 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 DkmsStatus: nvidia, 440.64, 5.4.0-31-generic, x86_64: installed nvidia, 440.64, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39ab] Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39ab] InstallationDate: Installed on 2019-04-08 (427 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 81CU ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=06db1321-d690-4a95-b79d-258351c53f9d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-26 (74 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7KCN31WW(V1.12) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-15IKB dmi.modalias: dmi:bvnLENOVO:bvr7KCN31WW(V1.12):bd11/08/2019:svnLENOVO:pn81CU:pvrLenovoYOGA730-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-15IKB: dmi.product.family: YOGA 730-15IKB dmi.product.name: 81CU dmi.product.sku: LENOVO_MT_81CU_BU_idea_FM_YOGA 730-15IKB dmi.product.version: Lenovo YOGA 730-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882607/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882631] [NEW] Xorg crash
Public bug reported: many time system hangs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 9 10:50:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H 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.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.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic crash ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1882631 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: many time system hangs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 9 10:50:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H 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.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.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1882525] Re: [amdgpu] Display is corrupted upon login on Ryzen APU
Please try selecting 'Ubuntu on Wayland' from the login screen and tell us if that avoids the problem. ** Summary changed: - Display is corrupted upon login on Ryzen APU + [amdgpu] Display is corrupted upon login on Ryzen APU ** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Tags added: amdgpu ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] Display is corrupted upon login on Ryzen APU Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu boots normally to the display manager (login screen) as expected. But once I log in, everything on the screen is cut up into horizontal slices, with each slice offset farther right than the slice above, and squares of random colors running diagonally across the screen. I've attached a picture of my monitor showing the issue for reference. My hardware is a home-built PC with an ASUS Prime B450M motherboard, a Ryzen 3 2200G APU, and using that APU's integrated graphics. In terms of software I'm running Ubuntu 20.04, which I just upgraded to and did a software update on. I have Linux 5.4.0-33-generic, X.Org 1.20.8, and Mesa 20.0.4. Before I upgraded Ubuntu, I was affected by Bug #1880041 but it seems fixed in the new kernel. I don't believe they're related but I figure it's worth mentioning. I tried adding the nomodeset kernel option at boot, and it's an effective workaround. Also, I tried booting from an Ubuntu Mate 20.04 live USB to see if this was caused by some quirk of my particular software setup, and successfully reproduced the bug, proving it wasn't. If you'd like me to, I can provide log files, system information, etc. or help narrow it down by testing workarounds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Jun 8 06:41:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1043:876b] InstallationDate: Installed on 2019-10-20 (231 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=43189257-cc94-4e98-ac1d-e16336dd152e ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2006 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go
[Desktop-packages] [Bug 1882531] Re: desktop context not localized
The screenshot in comment #1 appears to be nautilus-desktop. Not gnome- shell-extension-desktop-icons ** Package changed: gnome-shell-extension-desktop-icons (Ubuntu) => nautilus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1882531 Title: desktop context not localized Status in Ubuntu Translations: New Status in nautilus package in Ubuntu: Incomplete Bug description: Hi, at least in german environment the rightclick menu is not localized (and also the home-link). see screenshot attached regards Frank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1882531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882587] Re: Truncated audio frequency response on snd-aloop device
** Tags added: bionic ** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/915 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882587 Title: Truncated audio frequency response on snd-aloop device Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1882587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882342] Re: Ubuntu 20 Charging Indicator Blinks
I think the issue persisted a week ago. I tried to research the solution but couldn't find much. Before that, my laptop battery was working fine. Even the battery has lasted for 4-5 hours. But now, it's not behaving as expected. After a full charge, it takes less than an hour to drop the battery percentage (nearly 45%) and then suddenly to 5% giving notification that "The laptop will be hibernated". I don't know whether it's the problem of my battery or a charging adapter. I've also attached the screencast showing my power statistics. The videos show blinking of the indicator as well as a change of percentage(%) in App Indicators. When the blinking stops, it means that the charge is 100% full and vice-versa. Hoping to get a quick response from you back soon. Thanks. ** Attachment added: "Ubuntu Power Indicator.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1882342/+attachment/5381847/+files/Ubuntu%20Power%20Indicator.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882342 Title: Ubuntu 20 Charging Indicator Blinks Status in gnome-power-manager package in Ubuntu: Incomplete Bug description: https://askubuntu.com/questions/1240326/charging-indicator-blinks- unexpectedly-on-tecno-winpad-10a-ubuntu-20-04 I'd the same problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 15:00:10 2020 InstallationDate: Installed on 2020-05-04 (32 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1882342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882587] Re: Truncated audio frequency response on snd-aloop device
Here it is: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/915 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #915 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/915 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882587 Title: Truncated audio frequency response on snd-aloop device Status in pulseaudio package in Ubuntu: New Bug description: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882585] Re: gnome crashes when trying to lock session
Note this is *probably* bug 184. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882585 Title: gnome crashes when trying to lock session Status in gnome-shell package in Ubuntu: Invalid Bug description: When trying to lock session, either through key combination or clicking 'lock' in the top right menu, gnome unexpectedly freezes. During the time it's freezed I can move the mouse freely, but everything stops (even the clock). After some time it seems to restart because it flashes and everything goes back to normal. After the crash if I try to relock it again it works, but if I try after that the cycle repeats. Sometimes after the crash a crash report window launches accusing a SIGSEGV in gnome-shell. Looking at Logs I can see that the main process was exited and that the core was dumped. Note that at the time it freezes gnome unexpectedly switches the active window. I'm running Ubuntu 20.04 LTS with gnome-shell version 3.36.2-1ubuntu1~20.04.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 17:49:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-06 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882585/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882558] Re: desktop - missing templates to create new files
** Summary changed: - desktop - missing templates + desktop - missing templates to create new files ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1882558 Title: desktop - missing templates to create new files Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: Hi, in nautilus i can create new files by templates in (german) directory ~/Vorlagen i miss the option to create files on desktop this way regards Frank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1882558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871501] Re: Ubuntu accepts headset without asking me what it was when I plugged my Microsoft headset into my PC.
** Changed in: gnome-control-center (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1871501 Title: Ubuntu accepts headset without asking me what it was when I plugged my Microsoft headset into my PC. Status in gnome-control-center package in Ubuntu: New Bug description: Ubuntu registers the USB Headset as a speaker too, as one an see when the volume button is pushed and the volume is modified. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Tue Apr 7 18:01:01 2020 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870435] Re: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870435 Title: Terminal window flickers when I hover another window over it, especially a window that appeared because of a terminal command Status in gnome-shell package in Ubuntu: Expired Bug description: When I ran ubuntu-bug, and the ubuntu-bug window appeared, I noticed the ubuntu terminal window flickering between a white filter on it, and the terminal's normal appearance. This happens whenever I run "ubuntu-bug" and the window asking me for more information appears. The bug is with terminal, or xorg on Terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 17:24:05 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. 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.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-04-01 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5570 Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=170bf9d5-483d-4e3a-97c1-85f8d0ff5cec ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Tags: bionic ubuntu Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570
[Desktop-packages] [Bug 1871707] Re: Ubuntu fails to take screenshot of Firefox when I select "Current Window"
[Expired for gnome-screenshot (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-screenshot (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1871707 Title: Ubuntu fails to take screenshot of Firefox when I select "Current Window" Status in gnome-screenshot package in Ubuntu: Expired Bug description: I have to try three times before it works, and this is when I am using Firefox and compiling gcc from my terminal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screenshot 3.25.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Wed Apr 8 16:49:37 2020 InstallationDate: Installed on 2020-04-04 (4 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Package: gnome-screenshot 3.25.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1871707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871673] Re: error: ubuntu-20.04 version is not supported, so all dependencies may not be installed.
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1871673 Title: error: ubuntu-20.04 version is not supported, so all dependencies may not be installed. Status in hplip package in Ubuntu: Expired Bug description: printing very faint ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hplip 3.20.3+dfsg0-2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CupsErrorLog: CurrentDesktop: Budgie:GNOME Date: Wed Apr 8 12:54:47 2020 InstallationDate: Installed on 2020-02-05 (63 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK Computer INC. CM6330_CM6630_CM6730_CM6830_M11AA-8 Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=4a427cd0-ff55-4f29-8385-d92924457201 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6330_CM6630_CM6730_CM6830_M11AA 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.:bvr0904:bd01/08/2014:svnASUSTeKComputerINC.:pnCM6330_CM6630_CM6730_CM6830_M11AA-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6330_CM6630_CM6730_CM6830_M11AA:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: CM6330_CM6630_CM6730_CM6830_M11AA-8 dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1871673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871501] Re: Ubuntu accepts headset without asking me what it was when I plugged my Microsoft headset into my PC.
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1871501 Title: Ubuntu accepts headset without asking me what it was when I plugged my Microsoft headset into my PC. Status in gnome-control-center package in Ubuntu: Expired Bug description: Ubuntu registers the USB Headset as a speaker too, as one an see when the volume button is pushed and the volume is modified. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Tue Apr 7 18:01:01 2020 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873777] Re: Update to 2.64.2
I need help!!! I'm trying to build this repair but having a hard time running the build. I'm not very good at building from the provided fix. Please help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1873777 Title: Update to 2.64.2 Status in glib-networking package in Ubuntu: Fix Released Status in glib-networking source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes https://gitlab.gnome.org/GNOME/glib-networking/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that GNOME web still works correctly * Regression potential The update restore the TLS 1.0/1.1 protocols due to COVID-19, try to browse one of those websites from the GNOME browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882602] Re: Desktop functions not working - Ubuntu 20.04 LTS
*** This bug is a duplicate of bug 1855711 *** https://bugs.launchpad.net/bugs/1855711 Thanks for the bug report. These issues have already been reported so please use the existing bugs: - Keyboard does not work on desktop e.g: F2 - Arrows - Enter... etc. bug 1855711 - Can't drag and drop files from or into desktop. - Can't drag from browser to save on desktop e.g: images. bug 1813441 ** This bug has been marked a duplicate of bug 1855711 Add keyboard navigation to desktop icons -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1882602 Title: Desktop functions not working - Ubuntu 20.04 LTS Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: - Keyboard does not work on desktop e.g: F2 - Arrows - Enter... etc. - Can't drag and drop files from or into desktop. - Can't drag from browser to save on desktop e.g: images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1882602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882527] Re: mysql timeoutsec results in killing mysql process
** Package changed: xorg-server (Ubuntu) => mysql-8.0 (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1882527 Title: mysql timeoutsec results in killing mysql process Status in mysql-8.0 package in Ubuntu: New Bug description: MySQL on 20.04 has TimeoutSec set to 600 (IIRC) in the systemd script. This has the effect of killing the MySQL process if this timeout is reached. IMHO this is a Very Bad Idea. A database server process should only be force killed by a user action. I would prefer that the server had unlimited time to cleanly shutdown and startup (eg if recovering). Our DB is about 500GB with some very large tables (for us at least) eg. 250GB and we've had more than a few unfortunate delays as a result of delayed startup caused by recoveries because MySQL was killed prematurely. Because MySQL 8.0 has reduced the default logging level, it was not clear to me that the process was being force killed. I believe the MySQL team are of the same view as me per https://bugs.mysql.com/bug.php?id=91423: ``` [12 Jul 2019 15:57] Paul Dubois Posted by developer: Fixed in 8.0.18. On Debian, long InnoDB recovery times at startup could cause systemd service startup failure. The default systemd service timeout is now disabled (consistent with RHEL) to prevent this from happening. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1882527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882362] Re: Focus not where it should be
Note this is Unity on xenial. The gnome-shell package is not involved. ** Package changed: gnome-shell (Ubuntu) => nautilus (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Package changed: xorg-server (Ubuntu) => compiz (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882362 Title: Focus not where it should be Status in compiz package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: 0. Make sure you have an image file in your desktop, and that you have a folder somewhere in your filesystem that contains at least one file of any kind. Make also sure you have no window open, or otherwise do Show Desktop so that your desktop is visible. 1. Open a nautilus window and navigate to the a folder that has some files in it. So now a Nautilus window is in foreground with a folder open showing the contents of the folder 2. Make sure this window is not maximized, and move it around so that, on the background, you can see your desktop, and specifically, an image file that is in your desktop. Remember, at this stage the Nautilus window with the folder is in the foreground, focused. 3. Click on some file within the nautilus window to select it. 4. Click on the desktop background. Then click on some file on the desktop. Then on another one. Then finally on one particular image file that you have in your desktop. Now the desktop has focus and something in it is selected. NOTE: you can skip step 4, and you would observe the issue allthesame and it would still be bad. But the fact that explicitly including this step 4 you can observe the issue, makes it even more egregious. 5. Double ckick on the image file in the desktop, so as to open it in the default image viewer Now the image viewer window is in the foreground. 6. Close the image viewer window 7. Hit the Delete key. ** EXPECTED ** After step 6, focus should return to the desktop, where the image file was selected. Hence, hitting the Delete key should delete it ** OBSERVED ** For some random nonsensical reason, after step 6, the Nautilus window with the folder is focused, and hence, when you hit the delete key you delete whatever file was selected in it. This is a HUGE issue which may cause you to delete the wrong content without even realising it. And if you don't realise soon enough, you may be unable to undelete it. Just one more of a gazillion bugs that make Nautilus not only unusable, but also DANGEROUS. One of the most essential components of a Desktop operating system and yet one of the most broken ones. Fucking pathetic. I'm done with this crap, I will get rid of Ubuntu and install some other distro. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 6 15:45:50 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1464x887+768+660'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2429 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1882362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878275] Re: [qxl] wayland session hard freezes on login from GDM (X11 session works fine)
Thanks. Those both show gnome-shell is idle and not frozen in any
obvious way. So that gives me two ideas:
* I wonder if this is one of those rare cases where it's starting on
the wrong VT. Please try: Ctrl+Alt+F4, Ctrl+Alt+F2 etc and see if you
can find the missing session when it appears to freeze.
* I wonder if the 'qxl' kernel graphics driver is failing to report
(virtual) presentation events with correct timestamps. That would cause
the apparently idle symptoms we are seeing and is also a bug we've seen
in the VMware kernel driver (fixed a long time ago).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1878275
Title:
[qxl] wayland session hard freezes on login from GDM (X11 session
works fine)
Status in mutter package in Ubuntu:
Confirmed
Bug description:
When I login to my laptop running Ubuntu 20.04, after entering my
username, when I choose the "gear" button and select Ubuntu on Wayland
as the session type, my laptop freezes hard. Mouse and keyboard do not
respond, and the first three times I hit this issue I had to forcibly
power off. The normal (X11) Ubuntu session works fine.
However, I realized that I could still ping and ssh in, and doing that
gave me some clues to the issue.
I have keychain installed for password-less SSH, and my bash_profile has:
---
#!/bin/bash
# Get the aliases and functions
if [ -f $HOME/.bashrc ] ; then
source $HOME/.bashrc
fi
# Setup password-less SSH
[ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
keychain $HOME/.ssh/id_rsa
source $HOME/.keychain/${HOSTNAME}-sh
---
When I login via SSH from another machine after hitting the issue, I get:
[johnjaco@johnjaco-m-v02f: ~/Downloads] ssh john@192.168.1.10
Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support:https://ubuntu.com/advantage
0 updates can be installed immediately.
0 of these updates are security updates.
Your Hardware Enablement Stack (HWE) is supported until April 2025.
Last login: Mon Apr 27 19:41:17 2020 from 192.168.1.3
* keychain 2.8.5 ~ http://www.funtoo.org
* Waiting 5 seconds for lock...
* Found existing ssh-agent: 2086
* Adding 1 ssh key(s): /home/john/.ssh/id_rsa
Enter passphrase for /home/john/.ssh/id_rsa:
* ssh-add: Identities added: /home/john/.ssh/id_rsa
[john@andromeda: ~] pstree
systemd─┬─NetworkManager───2*[{NetworkManager}]
├─accounts-daemon───2*[{accounts-daemon}]
├─acpid
├─avahi-daemon───avahi-daemon
├─bluetoothd
├─boltd───2*[{boltd}]
├─colord───2*[{colord}]
├─containerd───13*[{containerd}]
├─cron
├─cups-browsed───2*[{cups-browsed}]
├─cupsd
├─dbus-daemon
├─dnsmasq───dnsmasq
├─gdm3─┬─gdm-session-wor─┬─gdm-wayland-ses─┬─gnome-session-b───3*[{gnom+
│ │ │ └─2*[{gdm-wayland-ses}]
│ │ └─2*[{gdm-session-wor}]
│ ├─gdm-session-wor─┬─gdm-wayland-ses─┬─bash───keychain───ssh-add
│ │ │ └─2*[{gdm-wayland-ses}]
│ │ └─2*[{gdm-session-wor}]
│ └─2*[{gdm3}]
├─gnome-keyring-d───2*[{gnome-keyring-d}]
├─iio-sensor-prox───2*[{iio-sensor-prox}]
├─irqbalance───{irqbalance}
├─2*[kerneloops]
├─libvirtd───16*[{libvirtd}]
├─networkd-dispat
├─packagekitd───2*[{packagekitd}]
├─polkitd───2*[{polkitd}]
├─rsyslogd───3*[{rsyslogd}]
├─rtkit-daemon───2*[{rtkit-daemon}]
├─ssh-agent
├─sshd───sshd───sshd───bash───pstree
├─switcheroo-cont───2*[{switcheroo-cont}]
├─systemd─┬─(sd-pam)
│ ├─at-spi-bus-laun─┬─dbus-daemon
│ │ └─3*[{at-spi-bus-laun}]
│ ├─at-spi2-registr───2*[{at-spi2-registr}]
│ ├─dbus-daemon
│ ├─dconf-service───2*[{dconf-service}]
│ ├─gjs───10*[{gjs}]
│ ├─gnome-keyring-d───3*[{gnome-keyring-d}]
│ ├─gnome-session-b───3*[{gnome-session-b}]
│ ├─gnome-session-c───{gnome-session-c}
│ ├─gnome-shell─┬─Xwayland───20*[{Xwayland}]
│ │ ├─ibus-daemon─┬─ibus-dconf───3*[{ibus-dconf}]
│ │ │
├─ibus-engine-sim───2*[{ibus-engi+
│ │ │ └─2*[{ibus-daemon}]
│ │ └─16*[{gnome-shell}]
│ ├─goa-daemon───3*[{goa-daemon}]
│ ├─goa-identity-se───2*[{goa-identity-se}]
│
[Desktop-packages] [Bug 1882368] Re: Sound is louder after resume from suspend or logging in Ubuntu 20.04
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New ** Summary changed: - Sound is louder after resume from suspend or logging in Ubuntu 20.04 + [OMEN by HP Obelisk Desktop 875-0xxx] Sound is louder after resume from suspend or logging in Ubuntu 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882368 Title: [OMEN by HP Obelisk Desktop 875-0xxx] Sound is louder after resume from suspend or logging in Ubuntu 20.04 Status in pulseaudio package in Ubuntu: New Bug description: I'm running Ubuntu 20.04 and have noticed that after logging back on to a machine either after its been asleep/suspended or logged out due to inactivity the sound is much louder at the same volume. I haven't enabled amplification or any other sound feature. To duplicate, boot machine with volume at say 50% and listen to some music. Let it either log out or suspend/sleep and then log back in, start music/sound and it will be much louder. In fact this louder sound at the volume sounds correct, because the windows boot sounds the same at that level. When ubuntu boots the volume is much softer. The sound post logging in after a suspend or lock out is what it should be from the get go. Soundcard details 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) DeviceName: Onboard - Sound Subsystem: Hewlett-Packard Company Cannon Lake PCH cAVS Flags: bus master, fast devsel, latency 32, IRQ 143 Memory at a351 (64-bit, non-prefetchable) [size=16K] Memory at a310 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kashif 2925 F pulseaudio /dev/snd/controlC0: kashif 2925 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-04-20 (414 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-08 (30 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/19/2019 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.name: 84FD dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.25:bd11/19/2019:svnHP:pnOMENbyHPObeliskDesktop875-0xxx:pvr:rvnHP:rn84FD:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Omen dmi.product.name: OMEN by HP Obelisk Desktop 875-0xxx dmi.product.sku: 4NM65AA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882481] Re: A dialog box stays on desktop and does not go away
*** This bug is a duplicate of bug 1824874 *** https://bugs.launchpad.net/bugs/1824874 Thanks. That confirms this is a duplicate of bug 1824874. ** This bug has been marked a duplicate of bug 1824874 undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882481 Title: A dialog box stays on desktop and does not go away Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon rebooting, I get dialog box Authentication Required Authentication is required to start 'cups.service'. I can type in the password and click Authenticate, but then nothing happens. I can't see under the box. I can't move the box, can't cancel the dialog. But, I can click on where I know the underneath icon to be and that click is accepted and the program in question runs. It appears the display manager does not remove the image after it is done with the dialog. I have recently done a clean install of 20.04. There is a screenshot in this Stack Exchange post: https://askubuntu.com/questions/1242999/dialog-box-does-not-accept-input-stays-on-top-and-hides-everything-under-it-ub ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 23:10:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 3.3-19, 5.4.0-31-generic, x86_64: installed amdgpu, 3.3-19, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 [1462:8a92] InstallationDate: Installed on 2020-05-12 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=ebb08f84-7501-4461-a5c4-c69c3c25d9b0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0804 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME 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.:bvr0804:bd11/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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 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 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/1882481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882042] Re: [SRU] Linux, Ubuntu, 18.4, CI, OLP15, PRTS, Audio/video is out of sync/lag when enter Suspend during playback
** Changed in: pulseaudio (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882042 Title: [SRU] Linux,Ubuntu,18.4,CI,OLP15,PRTS, Audio/video is out of sync/lag when enter Suspend during playback Status in HWE Next: New Status in pulseaudio package in Ubuntu: New Status in pulseaudio source package in Bionic: New Bug description: [Impact] Users reported the audio and video is out of sync when entering suspend during playback on bionic. [Fix] The mainline pulseaudio already has the fix for this issue, and the fix is already in the eoan, focal and groovy, but it is not in the bionic. [Test Case] open a online video on the firefox, while it is playing, suspend the system, wait for 30 seconds, resume the system, the audio and video is still on the sync. [Regression Risk] Low, these 2 patches are already in the mainline pulseaudio, and already in the eoan, focal and groovy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882610] [NEW] Lenovo E590 Graphics problems using standard Ubuntu/Budgie install
Public bug reported: Ive had major problems (seg errors and various) stopping several apps which were all working a couple of months ago, on my new Lenovo E590 Thinkpad notebook. sudo lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) What helped me sort it was the following command: sudo lshw -C display which showed the driver was xserver-xorg-video-intel which is not recommended; its older and problematic. Aptitude recommends use system default which is driver=i915). After removing this errant driver, its solved my applications crashing problems and more. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Jun 9 12:42:39 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:5072] InstallationDate: Installed on 2020-01-23 (137 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) LightdmDisplayLog: (EE) event4 - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded. See https://wayland.freedesktop.org/libinput/doc/1.15.5/touchpad-jumping-cursors.html for details (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-1435ms), your system is too slow (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-821ms), your system is too slow (EE) client bug: timer event4 keyboard: scheduled expiry is in the past (-204ms), your system is too slow Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:2130 Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 008: ID 14cd:6600 Super Top M110E PATA bridge Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=fab243f0-09ed-4b95-8ed6-995ffdde426c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0YET42W(1.25):bd01/13/2020:svnLENOVO:pn20NBCTO1WW:pvrThinkPadE590:rvnLENOVO:rn20NBCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E590 dmi.product.name: 20NBCTO1WW dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590 dmi.product.version: ThinkPad E590 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1882610 Title: Lenovo E590 Graphics problems using standard Ubuntu/Budgie install Status in xorg package in Ubuntu: New Bug description: Ive had major problems (seg errors and various) stopping several apps which were all working a couple of months ago, on my new Lenovo E590 Thinkpad notebook. sudo lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey Lake) (rev 02) What helped me sort it was the following command: sudo lshw -C display which showed the driver was xserver-xorg-video-intel which is not recommended; its older and problematic. Aptitude recommends use system default which is driver=i915). After removing this errant driver, its solved my applications crashing problems and more. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2
[Desktop-packages] [Bug 1882607] [NEW] One of the updates in the last week broke super key on external usb keyboard
Public bug reported: Worked fine until recent reboot. Now the super key on the external keyboard connected to a dock via thunderbolt port does not work. It still works on internal laptop keyboard. Tried switching to a few different languages but had no effect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b: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) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 18:41:32 2020 DistUpgraded: 2020-03-26 17:17:00,893 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 DkmsStatus: nvidia, 440.64, 5.4.0-31-generic, x86_64: installed nvidia, 440.64, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39ab] Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39ab] InstallationDate: Installed on 2019-04-08 (427 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 81CU ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=06db1321-d690-4a95-b79d-258351c53f9d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-26 (74 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7KCN31WW(V1.12) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-15IKB dmi.modalias: dmi:bvnLENOVO:bvr7KCN31WW(V1.12):bd11/08/2019:svnLENOVO:pn81CU:pvrLenovoYOGA730-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-15IKB: dmi.product.family: YOGA 730-15IKB dmi.product.name: 81CU dmi.product.sku: LENOVO_MT_81CU_BU_idea_FM_YOGA 730-15IKB dmi.product.version: Lenovo YOGA 730-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1882607 Title: One of the updates in the last week broke super key on external usb keyboard Status in xorg package in Ubuntu: New Bug description: Worked fine until recent reboot. Now the super key on the external keyboard connected to a dock via thunderbolt port does not work. It still works on internal laptop keyboard. Tried switching to a few different languages but had no effect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b: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) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied:
[Desktop-packages] [Bug 1818549] Re: Can't use the extensions provided by the webext-* packages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ublock-origin (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1818549 Title: Can't use the extensions provided by the webext-* packages Status in browserpass package in Ubuntu: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in ublock-origin package in Ubuntu: Confirmed Bug description: chromium-browser seems to ignore the extensions installed using the webext-* packages, e.g. webext-ublock-origin webext-browserpass The extensions simply do not show up anywhere in Chromium, while they work fine in Firefox. These webext packages are syncs from Debian, and on Debian systems they correctly show up both in Firefox and Chromium (installed using the 'chromium' Debian package). I'm running an up-to-date disco, with chromium-browser 72.0.3626.96-0ubuntu1. I didn't try with any previous version, so I don't know if the problem is a regression. Paride To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/browserpass/+bug/1818549/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818549] Re: Can't use the extensions provided by the webext-* packages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: browserpass (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1818549 Title: Can't use the extensions provided by the webext-* packages Status in browserpass package in Ubuntu: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in ublock-origin package in Ubuntu: Confirmed Bug description: chromium-browser seems to ignore the extensions installed using the webext-* packages, e.g. webext-ublock-origin webext-browserpass The extensions simply do not show up anywhere in Chromium, while they work fine in Firefox. These webext packages are syncs from Debian, and on Debian systems they correctly show up both in Firefox and Chromium (installed using the 'chromium' Debian package). I'm running an up-to-date disco, with chromium-browser 72.0.3626.96-0ubuntu1. I didn't try with any previous version, so I don't know if the problem is a regression. Paride To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/browserpass/+bug/1818549/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882602] [NEW] Desktop functions not working - Ubuntu 20.04 LTS
Public bug reported: - Keyboard does not work on desktop e.g: F2 - Arrows - Enter... etc. - Can't drag and drop files from or into desktop. - Can't drag from browser to save on desktop e.g: images. ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Tags: desktop gnom kernel-bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1882602 Title: Desktop functions not working - Ubuntu 20.04 LTS Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: - Keyboard does not work on desktop e.g: F2 - Arrows - Enter... etc. - Can't drag and drop files from or into desktop. - Can't drag from browser to save on desktop e.g: images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1882602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882362] Re: Focus not where it should be
Importance low??? Have you fucking read the report? This can cause you to ACCIDENTALLY DELETE stuff. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882362 Title: Focus not where it should be Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: 0. Make sure you have an image file in your desktop, and that you have a folder somewhere in your filesystem that contains at least one file of any kind. Make also sure you have no window open, or otherwise do Show Desktop so that your desktop is visible. 1. Open a nautilus window and navigate to the a folder that has some files in it. So now a Nautilus window is in foreground with a folder open showing the contents of the folder 2. Make sure this window is not maximized, and move it around so that, on the background, you can see your desktop, and specifically, an image file that is in your desktop. Remember, at this stage the Nautilus window with the folder is in the foreground, focused. 3. Click on some file within the nautilus window to select it. 4. Click on the desktop background. Then click on some file on the desktop. Then on another one. Then finally on one particular image file that you have in your desktop. Now the desktop has focus and something in it is selected. NOTE: you can skip step 4, and you would observe the issue allthesame and it would still be bad. But the fact that explicitly including this step 4 you can observe the issue, makes it even more egregious. 5. Double ckick on the image file in the desktop, so as to open it in the default image viewer Now the image viewer window is in the foreground. 6. Close the image viewer window 7. Hit the Delete key. ** EXPECTED ** After step 6, focus should return to the desktop, where the image file was selected. Hence, hitting the Delete key should delete it ** OBSERVED ** For some random nonsensical reason, after step 6, the Nautilus window with the folder is focused, and hence, when you hit the delete key you delete whatever file was selected in it. This is a HUGE issue which may cause you to delete the wrong content without even realising it. And if you don't realise soon enough, you may be unable to undelete it. Just one more of a gazillion bugs that make Nautilus not only unusable, but also DANGEROUS. One of the most essential components of a Desktop operating system and yet one of the most broken ones. Fucking pathetic. I'm done with this crap, I will get rid of Ubuntu and install some other distro. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 6 15:45:50 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1464x887+768+660'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2429 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen
I actually have no gnome extensions installed other than the ones that come preinstalled with Ubuntu. (Screenshot attached.) I also didn't change any settings concerning extensions. ** Attachment added: "extensions.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1882353/+attachment/5381771/+files/extensions.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: This is a very serious security issue: When I lock my desktop with SUPER (windows) + L my screen gets locked and goes to black. Sometimes when I return to my PC and move my mouse to turn my screen back on I notice that the Ubuntu Dock + the Top Bar are accessible from the lockscreen. I unfortunately can't remember if they were accessible from the moment I locked the screen or became accessible after returning from fade to black. (This is not the first time this issue happened.) I was able to open the settings menu from the top bar and use all indicators. You can actually start the programs in the Ubuntu Dock and give keyboard inputs to them. For example I was able to start the terminal emulator from the lock screen and run firefox and other applications. So an attacker could run arbitrary commands with user privileges from the lockscreen! The indicators drop down menus were fully visible on the lock screen while the Dock applications remained hidden "behind" the lockscreen (however still accessible via keyboard as described above). I have attached a screenshot of the bug. I unfortunately had no camera at hand to film me running terminal commands. Please contact me if you need additional information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 13:35:28 2020 InstallationDate: Installed on 2015-12-22 (1627 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1882353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
** Description changed: + [Impact] + + Users trying to install chromium-browser with apt in a chroot will see the preinst script hang for 30min, and eventually fail. + This use case is important as chroots are used by sysadmins to prepare installers. + + [Test Case] + + Create a focal chroot (for example using "pcreate -a amd64 -d focal focal-amd64"), enter the chroot and run "apt install chromium-browser". + Expected outcome: the installation succeeds, even though the chromium snap is not being installed because snapd cannot run in the chroot. + Incorrect (current) outcome: the installation hangs during 30 minutes while trying to contact the snap store, and eventually fails. + + [Regression Potential] + + As this change modifies the chromium-browser preinstallation script, it + should be verified that installing the package on systems that are + capable of running snapd (e.g. virtual machines or bare metal) still + works as expected. + + [Original Description] + Since snapd integration, chromium-browser package fails to install in a post kickstart chroot. As APT obfuscate snap installation, I worry about auto installation off any other snap package. - - - === When a user is running the installer, and instructs to install chromium- browser with apt in the /target chroot the experience is extremely bad. There are timeouts, there is critical debconf prompt, and no explanation as to what is happening. This is not an upgrade, and no conversion from deb2snap is needed. It is in a chroot, because this is how installers work. It feels like as if on fresh install of chromium-browser it should try "snap install --now-or-schedule-for-later chromium-browser" such that if snapd is running and available install it now, otherwise record a task for snapd to execute if and when it comes up (on first boot). Or like for example, it should call snap prepare-image --classic instead. Overall, imho on new installations of the package, if there is no snapd running, it should be skipped without asking any questions or popping up any dialogues. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1882232 Title: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot) Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: In Progress Bug description: [Impact] Users trying to install chromium-browser with apt in a chroot will see the preinst script hang for 30min, and eventually fail. This use case is important as chroots are used by sysadmins to prepare installers. [Test Case] Create a focal chroot (for example using "pcreate -a amd64 -d focal focal-amd64"), enter the chroot and run "apt install chromium-browser". Expected outcome: the installation succeeds, even though the chromium snap is not being installed because snapd cannot run in the chroot. Incorrect (current) outcome: the installation hangs during 30 minutes while trying to contact the snap store, and eventually fails. [Regression Potential] As this change modifies the chromium-browser preinstallation script, it should be verified that installing the package on systems that are capable of running snapd (e.g. virtual machines or bare metal) still works as expected. [Original Description] Since snapd integration, chromium-browser package fails to install in a post kickstart chroot. As APT obfuscate snap installation, I worry about auto installation off any other snap package. When a user is running the installer, and instructs to install chromium-browser with apt in the /target chroot the experience is extremely bad. There are timeouts, there is critical debconf prompt, and no explanation as to what is happening. This is not an upgrade, and no conversion from deb2snap is needed. It is in a chroot, because this is how installers work. It feels like as if on fresh install of chromium-browser it should try "snap install --now-or-schedule-for-later chromium-browser" such that if snapd is running and available install it now, otherwise record a task for snapd to execute if and when it comes up (on first boot). Or like for example, it should call snap prepare-image --classic instead. Overall, imho on new installations of the package, if there is no snapd running, it should be skipped without asking any questions or popping up any dialogues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
Thanks Sebastien. I'm beginning to suspect a faulty WiFi card. Wish there was some way to determine if that is the culprit. On Mon, Jun 8, 2020 at 4:30 PM Sebastien Bacher <1882...@bugs.launchpad.net> wrote: > The update mentioned fixes the iptables path on systemd not having > usrmerged, it's probably not the issue there > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1882242 > > Title: > June 4th network-manager update kills wireless networking > > Status in network-manager package in Ubuntu: > Incomplete > > Bug description: > network-manager problems > > June 4, 2020 apt update installed two networking packages: > network-manager_1.14.6-2+deb10u1_amd64.deb > libnm0_1.14.6-2+deb10u1_amd64.deb > > System: > Kernel: 5.4.0-33-generic x86_64 > Desktop: MATE 1.24.0 > Distro: Ubuntu 20.04 LTS (Focal Fossa) > Machine: > Type: Laptop System: Dell product: Latitude E6530 v: 01 > > After rebooting the laptop, the wireless access point(s) are no longer > available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- > Fi Networks" is grayed out. > > Network: > Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl > IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b > > $ sudo ip addr > > wlp2s0: mtu 1500 qdisc > fq_codel state DORMANT group default qlen 1000 > link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff > > $ sudo nmcli > wlp2s0: disconnected > "Broadcom and subsidiaries BCM43228" > wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 > > $ sudo nmcli device show > GENERAL.DEVICE: wlp2s0 > GENERAL.TYPE: wifi > GENERAL.HWADDR: 3C:77:E6:7C:5D:7B > GENERAL.MTU:1500 > GENERAL.STATE: 30 (disconnected) > GENERAL.CONNECTION: -- > GENERAL.CON-PATH: -- > > $ sudo nmcli radio wifi > enabled > > $ sudo iwlist wlp2s0 scanning > wlp2s0No scan results > > $ sudo iwlist wlp2s0 accesspoints > wlp2s0Interface doesn't have a list of Peers/Access-Points > > $ sudo iwlist wlp2s0 ap > wlp2s0Interface doesn't have a list of Peers/Access-Points > > $ sudo iwlist wlp2s0 wpakeys > wlp2s02 key sizes : 40, 104bits > 4 keys available : > Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported > > $ sudo iwconfig wlp2s0 > wlp2s0IEEE 802.11 ESSID:off/any > Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm > > Retry short limit:7 RTS thr:off Fragment thr:off > Encryption key:off > Power Management:on > > $ sudo rfkill list > 1: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > 2: brcmwl-0: Wireless LAN > Soft blocked: no > Hard blocked: no > 3: dell-wifi: Wireless LAN > Soft blocked: no > Hard blocked: no > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1882242/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo
[Desktop-packages] [Bug 1882242] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381769/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381767/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381763/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381770/+files/nmcli-con.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381768/+files/RfKill.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] NetDevice.wlp2s0.txt
apport information ** Attachment added: "NetDevice.wlp2s0.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381764/+files/NetDevice.wlp2s0.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381766/+files/PciNetwork.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381765/+files/NetworkManager.conf.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381758/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] NetDevice.eno1.txt
apport information ** Attachment added: "NetDevice.eno1.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381762/+files/NetDevice.eno1.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] IfupdownConfig.txt
apport information ** Attachment added: "IfupdownConfig.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381759/+files/IfupdownConfig.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381761/+files/IwConfig.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381760/+files/IpAddr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-04 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true NonfreeKernelModules: wl Package: network-manager 1.22.10-1ubuntu2.1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
apport information ** Tags added: apport-collected focal ** Description changed: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi-Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.2 + Architecture: amd64 + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-06-04 (4 days ago) + InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IpRoute: + default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp2s0 scope link metric 1000 + 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.4 metric 600 + NetworkManager.state: + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + NonfreeKernelModules: wl + Package: network-manager 1.22.10-1ubuntu2.1 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 + Tags: focal + Uname: Linux 5.4.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + nmcli-dev: + DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH + wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Drone 914c67d5-7b8c-41b2-89d0-0ce7bce3c858 /org/freedesktop/NetworkManager/ActiveConnection/1 + eno1ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- + lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1882242/+attachment/5381757/+files/CRDA.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems
[Desktop-packages] [Bug 1882362] Re: Focus not where it should be
** Package changed: nautilus (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882362 Title: Focus not where it should be Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: 0. Make sure you have an image file in your desktop, and that you have a folder somewhere in your filesystem that contains at least one file of any kind. Make also sure you have no window open, or otherwise do Show Desktop so that your desktop is visible. 1. Open a nautilus window and navigate to the a folder that has some files in it. So now a Nautilus window is in foreground with a folder open showing the contents of the folder 2. Make sure this window is not maximized, and move it around so that, on the background, you can see your desktop, and specifically, an image file that is in your desktop. Remember, at this stage the Nautilus window with the folder is in the foreground, focused. 3. Click on some file within the nautilus window to select it. 4. Click on the desktop background. Then click on some file on the desktop. Then on another one. Then finally on one particular image file that you have in your desktop. Now the desktop has focus and something in it is selected. NOTE: you can skip step 4, and you would observe the issue allthesame and it would still be bad. But the fact that explicitly including this step 4 you can observe the issue, makes it even more egregious. 5. Double ckick on the image file in the desktop, so as to open it in the default image viewer Now the image viewer window is in the foreground. 6. Close the image viewer window 7. Hit the Delete key. ** EXPECTED ** After step 6, focus should return to the desktop, where the image file was selected. Hence, hitting the Delete key should delete it ** OBSERVED ** For some random nonsensical reason, after step 6, the Nautilus window with the folder is focused, and hence, when you hit the delete key you delete whatever file was selected in it. This is a HUGE issue which may cause you to delete the wrong content without even realising it. And if you don't realise soon enough, you may be unable to undelete it. Just one more of a gazillion bugs that make Nautilus not only unusable, but also DANGEROUS. One of the most essential components of a Desktop operating system and yet one of the most broken ones. Fucking pathetic. I'm done with this crap, I will get rid of Ubuntu and install some other distro. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 6 15:45:50 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1464x887+768+660'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2429 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882367] Re: fail to add printer
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1882367 Title: fail to add printer Status in cups package in Ubuntu: Incomplete Bug description: lsusb Bus 002 Device 005: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader) Bus 002 Device 004: ID 147a:e018 Formosa Industrial Computing, Inc. eHome Infrared Receiver Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 002: ID 03f0:0f0c HP, Inc Wireless Keyboard and Optical Mouse receiver Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 04b8:0812 Seiko Epson Corp. MFP Composite Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ls -l /dev/usb/lp* /dev/bus/usb/*/* crw-rw-r-- 1 root root 189, 0 Jun 6 13:43 /dev/bus/usb/001/001 crw-rw-r-- 1 root lp 189, 2 Jun 6 15:40 /dev/bus/usb/001/003 crw-rw-r-- 1 root root 189, 128 Jun 6 13:43 /dev/bus/usb/002/001 crw-rw-r-- 1 root root 189, 129 Jun 6 13:43 /dev/bus/usb/002/002 crw-rw-r-- 1 root root 189, 131 Jun 6 13:43 /dev/bus/usb/002/004 crw-rw-r-- 1 root root 189, 132 Jun 6 13:43 /dev/bus/usb/002/005 crw-rw-r-- 1 root root 189, 256 Jun 6 13:43 /dev/bus/usb/003/001 crw-rw-r-- 1 root root 189, 384 Jun 6 13:43 /dev/bus/usb/004/001 crw-rw-r-- 1 root root 189, 512 Jun 6 13:43 /dev/bus/usb/005/001 crw-rw-r-- 1 root root 189, 640 Jun 6 13:43 /dev/bus/usb/006/001 crw-rw-r-- 1 root root 189, 768 Jun 6 13:43 /dev/bus/usb/007/001 crw-rw-r-- 1 root root 189, 896 Jun 6 13:43 /dev/bus/usb/008/001 crw-rw-r-- 1 root root 189, 897 Jun 6 13:43 /dev/bus/usb/008/002 crw-rw 1 root lp 180, 2 Jun 6 15:40 /dev/usb/lp2 sudo usb_printerid /dev/usb/lp2 GET_DEVICE_ID string: MFG:EPSON;CMD:ESCPL2,BDC,D4;MDL:Stylus Photo R320;CLS:PRINTER;DES:EPSON Stylus Photo R320; sudo lpinfo -v file cups-brf:/ direct canon:/dev/usb/lp2 network http direct epson:/dev/usb/lp2 direct hp network https network ipp network ipps direct usb://EPSON/Stylus%20Photo%20R320?serial=L17P20504140921110=1 network beh network socket network lpd direct hpfax ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 15:48:44 2020 InstallationDate: Installed on 2020-03-31 (66 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lpstat: device for EpsonR320: usb://EPSON/Stylus%20Photo%20R320?serial=L17P20504140921110 device for Stylus-Photo-R320: usb://EPSON/Stylus%20Photo%20R320?serial=L17P20504140921110=1 MachineType: HP-Pavilion NF398AA-ABU m9565uk Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Stylus-Photo-R320.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Stylus-Photo-R320.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=6516a65a-169c-45a6-831e-5f71f0bdbcfa ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-05-12 (25 days ago) dmi.bios.date: 12/16/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.35 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard
[Desktop-packages] [Bug 1882380] Re: package firefox 77.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: fim de ficheiro em stdin na prompt do ficheiro de configuração
Hello Felipe, it looks like you may have changed
/etc/apparmor.d/usr.bin.firefox causing the automatic updates to fail.
Running this in a terminal will probably fix things:
sudo apt update
sudo apt install -f
sudo apt upgrade
Thanks
** Information type changed from Private Security to Public Security
** Changed in: firefox (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1882380
Title:
package firefox 77.0.1+build1-0ubuntu0.20.04.1 failed to
install/upgrade: fim de ficheiro em stdin na prompt do ficheiro de
configuração
Status in firefox package in Ubuntu:
Won't Fix
Bug description:
Pacote Firefox com erro ao carregar a página
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: firefox 77.0.1+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.2
AptOrdering:
firefox:amd64: Install
NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: felipe 2466 F pulseaudio
BuildID: 2020060727
CasperMD5CheckResult: skip
Channel: Unavailable
Date: Thu Jun 4 20:00:09 2020
ErrorMessage: fim de ficheiro em stdin na prompt do ficheiro de configuração
ForcedLayersAccel: False
InstallationDate: Installed on 2020-05-10 (27 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.2, unpackaged
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 77.0.1+build1-0ubuntu0.20.04.1 failed to
install/upgrade: fim de ficheiro em stdin na prompt do ficheiro de configuração
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 01MCMN
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn01MCMN:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6320
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.apport.blacklist.d.firefox:
/usr/lib/firefox/firefox
/usr/lib/firefox/plugin-container
modified.conffile..etc.apport.native-origins.d.firefox:
LP-PPA-ubuntu-mozilla-daily
LP-PPA-ubuntu-mozilla-daily-firefox-aurora
LP-PPA-mozillateam-firefox-next
modified.conffile..etc.firefox.syspref.js:
// This file can be used to configure global preferences for Firefox
// Example: Homepage
//pref("browser.startup.homepage", "http://www.weebls-stuff.com/wab/;);
mtime.conffile..etc.apparmor.d.usr.bin.firefox: 2020-04-30T08:04:06
mtime.conffile..etc.apport.blacklist.d.firefox: 2020-04-03T16:34:46
mtime.conffile..etc.apport.native-origins.d.firefox: 2020-04-03T16:34:46
mtime.conffile..etc.firefox.syspref.js: 2019-10-21T09:24:29
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1882380/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882342] Re: Ubuntu 20 Charging Indicator Blinks
Could you maybe do a screencast or video showing the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882342 Title: Ubuntu 20 Charging Indicator Blinks Status in gnome-power-manager package in Ubuntu: Incomplete Bug description: https://askubuntu.com/questions/1240326/charging-indicator-blinks- unexpectedly-on-tecno-winpad-10a-ubuntu-20-04 I'd the same problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 15:00:10 2020 InstallationDate: Installed on 2020-05-04 (32 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1882342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
The update mentioned fixes the iptables path on systemd not having usrmerged, it's probably not the issue there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1882242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority
It would be best to work with upstream to get it merged, what is blocking? Is upstream not responding? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882161 Title: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority Status in HWE Next: New Status in pulseaudio package in Ubuntu: Incomplete Status in pulseaudio source package in Focal: Incomplete Status in pulseaudio source package in Groovy: Incomplete Bug description: This bug originates from an OEM private bug #1875597, then ubuntu users reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 and the 1st issue of #1881659 have the same root cause as #1875597 [Impact] On the Dell machines with multi function audio jack, after installing the ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the headphone/headset can't output sound automatically after users plug in a headphone/headset. This is different from ubuntu 18.04, on the 18.04, the headphone/headset could output sound automatically after plugging in the audio jack. [Fix] The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, finally the audio jack is set to Mic2 mode, this make the audio jack can't output sound anymore. To fix it, let the audio jack set to Headset MIC mode by default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the device event to module-switch-on-port-available by the order of priority in the umc2. [Test Case] applying the fix patch to pulseaudio, plug a headset/headphone to the multi function audio jack, play sound from headset/headphone, the sound could be heard from headset/headphone. [Regression Risk] Low, just do a small change to store the ucm devices by their priority. This fix is not accepted by upstream yet. Maybe we could apply this fix to ubuntu specific part, if the upstream has a solution for this issue in the future, we could revert this fix and merge the uptream's solution then. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882258] Re: XRDP to Ubuntu 19.10 request many popup dialog for creating a colorprofile
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: policykit-1-gnome (Ubuntu) Importance: Undecided => Low ** Changed in: policykit-1-gnome (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1882258 Title: XRDP to Ubuntu 19.10 request many popup dialog for creating a colorprofile Status in policykit-1-gnome package in Ubuntu: Incomplete Bug description: While searching abougt a solution I found this Blogpost which was able to help me in this case: https://c-nergy.be/blog/?p=12073 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/1882258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882267] Re: nautilus Find function stuck in 'full text' search mode
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1882267 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1882267 Title: nautilus Find function stuck in 'full text' search mode Status in nautilus package in Ubuntu: Incomplete Bug description: After searching in "Full Text" mode in Nautilus, then changing to "Filename" search mode, Nautilus continues to return results based on "Full Text" mode. Example: I opened Files program, clicked on Find, then clicked the drop-down and selected "File Name". I then searched for the word "atlantic." The results returned not only file names with "atlantic" in them, but file names that did not contain "atlantic" in the file title, but where the word "atlantic" could be found in the body of the file's text. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1882267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882340] Re: Alert sounds are captured by the microphone
Thank you for your bug report, what would you expect exactly? A video call to automatically mute sound effects on your computer? What software do you use for the video call? It should probably be the one handling such changes Also would you expect only effects to be muted or any sound? ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1882340 Title: Alert sounds are captured by the microphone Status in alsa-driver package in Ubuntu: Incomplete Bug description: On my Fossa the system sounds (e.g., the alert sound) are also captured by my microphone. Thus, if I press backspace in an empty terminal, my contacts in a video-call can hear the default bell sound making *pling*. When opening the System > Audio on Gnome I can see a rise on the volume bar as well. A workaround exists by disabling the alert sounds as described in the docs: https://help.ubuntu.com/stable/ubuntu-help/sound-alert.html.en This has been the default since installation for me and drives my contacts crazy. :-) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jl 3027 F pulseaudio /dev/snd/controlC0: jl 3027 F pulseaudio /dev/snd/pcmC0D0p: jl 3027 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 10:53:55 2020 InstallationDate: Installed on 2020-04-24 (42 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad Thunderbolt 3 Dock USB Audio - ThinkPad Thunderbolt 3 Dock USB Symptom_PulseAudioLog: Jun 05 20:03:08 x1c dbus-daemon[1617]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=125 pid=2067 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Jun 05 20:03:24 x1c systemd[2021]: pulseaudio.service: Succeeded. Jun 05 20:03:34 x1c systemd[2021]: pulseaudio.socket: Succeeded. Symptom_Type: Volume slider, or mixer problems Title: [sof-hda-dsp - sof-hda-dsp, recording] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET47W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QES01L00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QES01L00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QES01L00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QES01L00 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1882340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882242] Re: June 4th network-manager update kills wireless networking
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1882242 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882242 Title: June 4th network-manager update kills wireless networking Status in network-manager package in Ubuntu: Incomplete Bug description: network-manager problems June 4, 2020 apt update installed two networking packages: network-manager_1.14.6-2+deb10u1_amd64.deb libnm0_1.14.6-2+deb10u1_amd64.deb System: Kernel: 5.4.0-33-generic x86_64 Desktop: MATE 1.24.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Laptop System: Dell product: Latitude E6530 v: 01 After rebooting the laptop, the wireless access point(s) are no longer available in the Network Manager. The "Enable Wi-Fi" is checked. "Wi- Fi Networks" is grayed out. Network: Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl IF: wlp2s0 state: dormant mac: 3c:77:e6:7c:5d:7b $ sudo ip addr wlp2s0: mtu 1500 qdisc fq_codel state DORMANT group default qlen 1000 link/ether 3c:77:e6:7c:5d:7b brd ff:ff:ff:ff:ff:ff $ sudo nmcli wlp2s0: disconnected "Broadcom and subsidiaries BCM43228" wifi (wl), 3C:77:E6:7C:5D:7B, hw, mtu 1500 $ sudo nmcli device show GENERAL.DEVICE: wlp2s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 3C:77:E6:7C:5D:7B GENERAL.MTU:1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- $ sudo nmcli radio wifi enabled $ sudo iwlist wlp2s0 scanning wlp2s0No scan results $ sudo iwlist wlp2s0 accesspoints wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 ap wlp2s0Interface doesn't have a list of Peers/Access-Points $ sudo iwlist wlp2s0 wpakeys wlp2s02 key sizes : 40, 104bits 4 keys available : Error reading wpa keys (SIOCGIWENCODEEXT): Operation not supported $ sudo iwconfig wlp2s0 wlp2s0IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on $ sudo rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: brcmwl-0: Wireless LAN Soft blocked: no Hard blocked: no 3: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1882242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882342] Re: Ubuntu 20 Charging Indicator Blinks
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: gnome-power-manager (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-power-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882342 Title: Ubuntu 20 Charging Indicator Blinks Status in gnome-power-manager package in Ubuntu: Incomplete Bug description: https://askubuntu.com/questions/1240326/charging-indicator-blinks- unexpectedly-on-tecno-winpad-10a-ubuntu-20-04 I'd the same problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 15:00:10 2020 InstallationDate: Installed on 2020-05-04 (32 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1882342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 306673] Re: autofs timeout
** Changed in: nautilus (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/306673 Title: autofs timeout Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: Binary package hint: nautilus OS: Ubuntu 8.10 Intrepid, upgraded from Hardy Software: SSHFS, AutoFS, no changes concerning Nautilus I'm using SSHFS with AutoFS to mount remote shares, which I must have unmounted after some time because of security concerns. This has had me set a timeout on the AutoFS mounts. The problem is that when opening a remote folder in Nautilus, the timeout countdown starts as soon as I stop clicking on folders/files. When it's down, I get a password prompt. This is buggy behaviour to me, because if I set the timeout to 10 seconds, there is a password prompt every 10 seconds if I just have a remote folder open in Nautilus, doing nothing else. Of course I've got a bigger timeout, but it's still quite annoying. I think that it should either: 1. Start the timeout as soon as I don't browse around or poll the file system manually in any other way. Then ask for a password only if user interaction occurs. 2. Don't time out as long as I have an open remote folder (after closing the last remote directory, let AutoFS time out and unmount). This is how KDE's Konqueror and gnome-terminal behave. There is already a bug filed at the GNOME bugzilla about this. But it originates from 2002 and the last comment is from 2006... which is about the issue still not being resolved. That's why I'm reporting here. If anyone has a better idea who to harass into fixing this, speak up ;) Here's the GNOME bug: http://bugzilla.gnome.org/show_bug.cgi?id=101673 I've also started a thread at the ubuntuforums.org: http://ubuntuforums.org/showthread.php?t=1003656 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/306673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882587] Re: Truncated audio frequency response on snd-aloop device
Thank you for your bug report, could you sent it also upstream on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues ? ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882587 Title: Truncated audio frequency response on snd-aloop device Status in pulseaudio package in Ubuntu: New Bug description: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882585] Re: gnome crashes when trying to lock session
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882585 Title: gnome crashes when trying to lock session Status in gnome-shell package in Ubuntu: Invalid Bug description: When trying to lock session, either through key combination or clicking 'lock' in the top right menu, gnome unexpectedly freezes. During the time it's freezed I can move the mouse freely, but everything stops (even the clock). After some time it seems to restart because it flashes and everything goes back to normal. After the crash if I try to relock it again it works, but if I try after that the cycle repeats. Sometimes after the crash a crash report window launches accusing a SIGSEGV in gnome-shell. Looking at Logs I can see that the main process was exited and that the core was dumped. Note that at the time it freezes gnome unexpectedly switches the active window. I'm running Ubuntu 20.04 LTS with gnome-shell version 3.36.2-1ubuntu1~20.04.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 17:49:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-06 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882585/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen
Hello, the usual cause of this with gnome is extensions -- try disabling all the extensions, see if you reproduce, and enable them one at a time, etc. You may find one that causes the screen lock to not work as you expect. Thanks ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: This is a very serious security issue: When I lock my desktop with SUPER (windows) + L my screen gets locked and goes to black. Sometimes when I return to my PC and move my mouse to turn my screen back on I notice that the Ubuntu Dock + the Top Bar are accessible from the lockscreen. I unfortunately can't remember if they were accessible from the moment I locked the screen or became accessible after returning from fade to black. (This is not the first time this issue happened.) I was able to open the settings menu from the top bar and use all indicators. You can actually start the programs in the Ubuntu Dock and give keyboard inputs to them. For example I was able to start the terminal emulator from the lock screen and run firefox and other applications. So an attacker could run arbitrary commands with user privileges from the lockscreen! The indicators drop down menus were fully visible on the lock screen while the Dock applications remained hidden "behind" the lockscreen (however still accessible via keyboard as described above). I have attached a screenshot of the bug. I unfortunately had no camera at hand to film me running terminal commands. Please contact me if you need additional information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 13:35:28 2020 InstallationDate: Installed on 2015-12-22 (1627 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-04-25 (42 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-12-23T12:07:53.769719 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1882353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882136] Re: I can't connect to 5GHz wifi
The log suggests it's a kernel issue kernel: Call Trace: kernel: dump_stack+0x6d/0x9a kernel: iwl_pcie_send_hcmd_sync+0x382/0x390 [iwlwifi] kernel: ? wait_woken+0x80/0x80 kernel: iwl_trans_pcie_send_hcmd+0x34/0xf0 [iwlwifi] kernel: iwl_trans_send_cmd+0x55/0xc0 [iwlwifi] kernel: iwl_mvm_send_cmd+0x1f/0x40 [iwlmvm] kernel: iwl_mvm_send_cmd_pdu+0x51/0x70 [iwlmvm] ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882136 Title: I can't connect to 5GHz wifi Status in linux package in Ubuntu: New Bug description: After updating the NetworkManager I can't connect to 5GHz wifi. The router is a mikrotik hap ac2.The notebook is a Dell Latitude 5580. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 22:20:15 2020 InstallationDate: Installed on 2020-05-15 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882158] Re: nm-applet /usr/lib/libnma.so.0: version `libnma_1_8_22' not found (required by nm-applet)
Thank you for your bug report, the issue was there $ ldd `which nm-applet` ... libnm.so.0 => /usr/local/lib/libnm.so.0 (0x7f465ad1e000) That's a local installation taking over the Ubuntu version of the library and probably outdated ** Changed in: network-manager-applet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1882158 Title: nm-applet /usr/lib/libnma.so.0: version `libnma_1_8_22' not found (required by nm-applet) Status in network-manager-applet package in Ubuntu: Invalid Bug description: 1) The release of Ubuntu you are using $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 2) The version of the package you are using $ apt-cache policy network-manager-gnome network-manager-gnome: Installed: 1.8.24-1ubuntu2 Candidate: 1.8.24-1ubuntu2 Version table: *** 1.8.24-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy libnma0 libnma0: Installed: 1.8.24-1ubuntu2 Candidate: 1.8.24-1ubuntu2 Version table: *** 1.8.24-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen nm-applet runs and shows the tray applet. 4) What happened instead nm-applet does not run with the following error: $ nm-applet nm-applet: /usr/lib/libnma.so.0: version `libnma_1_8_22' not found (required by nm-applet) More information: $ ldd `which nm-applet` /usr/bin/nm-applet: /usr/lib/libnma.so.0: version `libnma_1_8_22' not found (required by /usr/bin/nm-applet) linux-vdso.so.1 (0x7fffd428e000) libnma.so.0 => /usr/lib/libnma.so.0 (0x7f465b084000) libnm.so.0 => /usr/local/lib/libnm.so.0 (0x7f465ad1e000) libsecret-1.so.0 => /usr/lib/x86_64-linux-gnu/libsecret-1.so.0 (0x7f465acbd000) libnotify.so.4 => /usr/lib/x86_64-linux-gnu/libnotify.so.4 (0x7f465acb2000) libmm-glib.so.0 => /usr/lib/x86_64-linux-gnu/libmm-glib.so.0 (0x7f465abd3000) libappindicator3.so.1 => /usr/lib/x86_64-linux-gnu/libappindicator3.so.1 (0x7f465abc1000) libgtk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (0x7f465a412000) libgdk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 (0x7f465a30d000) libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x7f465a2fb000) libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x7f465a2ac000) libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x7f465a282000) libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x7f465a15f000) libgdk_pixbuf-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7f465a135000) libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7f4659f54000) libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7f4659ef4000) libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7f4659dcb000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f4659da8000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4659bb6000) libnss3.so => /usr/lib/x86_64-linux-gnu/libnss3.so (0x7f4659a65000) libsmime3.so => /usr/lib/x86_64-linux-gnu/libsmime3.so (0x7f4659a35000) libnspr4.so => /usr/lib/x86_64-linux-gnu/libnspr4.so (0x7f46599f5000) libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x7f46599ef000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f46599e6000) libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f46599ba000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f46599b2000) /lib64/ld-linux-x86-64.so.2 (0x7f465b328000) libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7f4659894000) libdbusmenu-gtk3.so.4 => /usr/lib/x86_64-linux-gnu/libdbusmenu-gtk3.so.4 (0x7f465987d000) libdbusmenu-glib.so.4 => /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4 (0x7f465985d000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7f465972) libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x7f465970c000) libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x7f4659704000) libcairo-gobject.so.2 => /usr/lib/x86_64-linux-gnu/libcairo-gobject.so.2 (0x7f46596f8000) libatk-bridge-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 (0x7f46596c1000) libepoxy.so.0 => /usr/lib/x86_64-linux-gnu/libepoxy.so.0
[Desktop-packages] [Bug 1882587] Re: Truncated audio frequency response on snd-aloop device
** Summary changed: - Truncated audio frequency response on monitor device + Truncated audio frequency response on snd-aloop device -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882587 Title: Truncated audio frequency response on snd-aloop device Status in pulseaudio package in Ubuntu: New Bug description: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 640418] Re: Please add support for bash highlight in gedit
Thanks, closing ** Changed in: gedit (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/640418 Title: Please add support for bash highlight in gedit Status in gedit package in Ubuntu: Fix Released Bug description: Binary package hint: gedit There is no highlight mode for bash in gedit. It has support for a lot of other scripts IMHO gedit should come with support for bash and other scripts. I know i use gedit for most things, ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gedit 2.30.3-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Sep 16 07:56:10 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) ProcEnviron: PATH=(custom, user) LANG=C SHELL=/bin/bash SourcePackage: gedit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/640418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881482] Re: adding fingerprints not possible
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1881482 Title: adding fingerprints not possible Status in gnome-control-center package in Ubuntu: New Bug description: hi, after getting my fingerprint-reader working, i wonder why i can only define 1 fungerprint in gnome-settings dialog (system->users->fingerprint login add finger). i have defined one, fingerprint-usage is activated, if i click on the setting i will be asked about deleting the fingerprints to disable. here i can delete or cancel...as i do not want to delete i click cancel and expect the dialog for adding additional fingers...but this does not happen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Sun May 31 16:20:32 2020 InstallationDate: Installed on 2020-04-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1881482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882531] Re: desktop context not localized
Could you also try if you get the issue in a GNOME or Ubuntu session or is that specific to fallback? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1882531 Title: desktop context not localized Status in Ubuntu Translations: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Hi, at least in german environment the rightclick menu is not localized (and also the home-link). see screenshot attached regards Frank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1882531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881712] Re: gnome-software says connection is metered while is not
Could someone having the issue report it upstream on https://gitlab.gnome.org/GNOME/gnome-software/issues ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1881712 Title: gnome-software says connection is metered while is not Status in gnome-software package in Ubuntu: Confirmed Bug description: I open gnome-software and i see a message 'automatic updates paused' for my connection is metered but my connection is NOT metered. see attached screenshot. corrado@corrado-HP-x4-gg-0525ebook-PC:~$ inxi -Fx System:Host: corrado-HP-x4-gg-0525ebook-PC Kernel: 5.4.0-26-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.2 Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC v: 0991100600087 serial: Mobo: Hewlett-Packard model: 2211 v: 86.49 serial: UEFI: Insyde v: F.36 date: 12/18/2014 Battery: ID-1: BAT1 charge: 10.2 Wh condition: 16.4/16.4 Wh (100%) model: 13-42 OA03031 status: Charging CPU: Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: Haswell rev: 1 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156 Speed: 1696 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1697 2: 1696 3: 1696 4: 1697 Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Suyin type: USB driver: uvcvideo bus ID: 1-1.5:3 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 20.0.7 direct render: Yes Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:03.0 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.4.0-26-generic Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus ID: 08:00.0 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 port: 3000 bus ID: 09:00.0 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d Drives:Local Storage: total: 689.33 GiB used: 6.76 GiB (1.0%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB ID-2: /dev/sdb vendor: SanDisk model: SSD PLUS 240GB size: 223.57 GiB Partition: ID-1: / size: 31.25 GiB used: 6.75 GiB (21.6%) fs: ext4 dev: /dev/sdb5 Swap: ID-1: swap-1 type: partition size: 4.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 39.0 C mobo: 39.0 C Fan Speeds (RPM): N/A Info: Processes: 236 Uptime: 49m Memory: 3.78 GiB used: 1.39 GiB (36.7%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.16 inxi: 3.1.00 corrado@corrado-HP-x4-gg-0525ebook-PC:~$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 08:57:28 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2020-05-26 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200525) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-21 (41 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200420) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 Package: gnome-software 3.36.0-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to:
[Desktop-packages] [Bug 1882531] Re: desktop context not localized
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1882531 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1882531 Title: desktop context not localized Status in Ubuntu Translations: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Hi, at least in german environment the rightclick menu is not localized (and also the home-link). see screenshot attached regards Frank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1882531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880806] Re: Gedit unable to save preferences on 20.04
Weird, do you start gedit with your user? Do changes to other applications (e.g nautilus) are correctly stored? Could you maybe try with another user account on the same computer to see if that has the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1880806 Title: Gedit unable to save preferences on 20.04 Status in gedit package in Ubuntu: Incomplete Bug description: Hi, Since upgrading to Ubuntu 20.04, Gedit is unable to save preferences. By default, it came with the following: Display line numbers: on Display right margin: off Highlight current line: on Text wrapping: on I wanted to disable the first and third option, so I did. It works as long as gedit is open, but if I close and reopen it, the settings were reverted. Repro steps: 1. Open gedit 2. Toggle the "Highlight current line" preference 3. Close gedit 4. Open gedit again 5. Observe that the "Highlight current line" preference is reverted to the original value Expected behavior Gedit persists preferences after closing & reopening Actual behavior: Gedit does not persist preferences after closing & reopening Workaround: Using gsettings seemed to do the trick. I've run: gsettings set org.gnome.gedit.preferences.editor highlight-current-line false gsettings set org.gnome.gedit.preferences.editor display-line-numbers false This persists the settings correctly, so I believe the bug is related to the UI. Additional information: OS: Ubuntu 20.04 Package: /usr/bin/gedit Version: 3.36.2-0ubuntu1 Thanks, Balazs ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 27 06:37:36 2020 InstallationDate: Installed on 2018-11-05 (568 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-05-22 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1880806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881115] Re: shift-delete not handled
> btw. is there a way to find out right package if it is not a simple application-package like here? Not really sorry -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1881115 Title: shift-delete not handled Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: Hi, i've noticed 2 problems on desktop (gnome-flashback), which is imho handled by nautilus... - contextmenu (rightclick) is not localized (german environment, menu is english) - shift-delete does nothing, in menu there is only "move to trash" (+open +properties), no way to delete files without trash regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Thu May 28 14:12:30 2020 GsettingsChanges: b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-04-27 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1881115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
The patch doesn't sound like something we would like to carry as a distro patch, also the depends of ofono mentioned sounds suboptimal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864558] Re: Printer adds automatically at boot with notification or if printer deleted
the midnight notification issue is reported as bug #1869981 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1864558 Title: Printer adds automatically at boot with notification or if printer deleted Status in cups package in Ubuntu: Confirmed Bug description: When booting 20.04 I get a notification on the logon screen each time advising that my wireless printer has been setup. If I remove the printer via settings, then as soon as it's removed, it gets re-added and I see the same notification as I do on the logon screen about the printer having been setup. I've attached a screenshot of this notification. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 21:49:43 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1864558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794194] Re: missing archive files in library
Thanks, there is a similar request in Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=962363 ** Changed in: openjpeg2 (Ubuntu) Importance: Undecided => Low ** Bug watch added: Debian Bug tracker #962363 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962363 ** Changed in: openjpeg2 (Ubuntu) Status: Confirmed => Triaged ** Also affects: openjpeg2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962363 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openjpeg2 in Ubuntu. https://bugs.launchpad.net/bugs/1794194 Title: missing archive files in library Status in openjpeg2 package in Ubuntu: Triaged Status in openjpeg2 package in Debian: Unknown Bug description: archive files are missing from dev openjp library: /usr/lib/x86_64-linux-gnu/libopenjpip_local.a /usr/lib/x86_64-linux-gnu/libopenjpip_server.a /usr/lib/x86_64-linux-gnu/libopenjp2.a on both 16.04 and 18.04 Binaries: jpip_to_jp2 jpip_to_j2k addXMLinJP2 that are provided in package 'openjpip-dec-server' on Ubuntu 16.04, miss on 18.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libopenjpip-server 2.1.2-1.1+deb9u2build0.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_4_0_78_99_generic_34 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Sep 24 23:24:50 2018 SourcePackage: openjpeg2 UpgradeStatus: Upgraded to xenial on 2017-05-05 (507 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjpeg2/+bug/1794194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
** Also affects: chromium-browser (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: chromium-browser (Ubuntu Focal) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: chromium-browser (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: chromium-browser (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1882232 Title: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot) Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: In Progress Bug description: Since snapd integration, chromium-browser package fails to install in a post kickstart chroot. As APT obfuscate snap installation, I worry about auto installation off any other snap package. === When a user is running the installer, and instructs to install chromium-browser with apt in the /target chroot the experience is extremely bad. There are timeouts, there is critical debconf prompt, and no explanation as to what is happening. This is not an upgrade, and no conversion from deb2snap is needed. It is in a chroot, because this is how installers work. It feels like as if on fresh install of chromium-browser it should try "snap install --now-or-schedule-for-later chromium-browser" such that if snapd is running and available install it now, otherwise record a task for snapd to execute if and when it comes up (on first boot). Or like for example, it should call snap prepare-image --classic instead. Overall, imho on new installations of the package, if there is no snapd running, it should be skipped without asking any questions or popping up any dialogues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
The GTK fix is about wayland, are the reports specific about wayland there? The changes also are in 3.24.17 which is included in focal so if it's still an issue there then it's probably not the right fix for the issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1570227] Re: Open Recent Items show as always empty in Gedit
** Changed in: gedit (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1570227 Title: Open Recent Items show as always empty in Gedit Status in gedit: New Status in gedit package in Ubuntu: Triaged Bug description: Gedit doesn't show the recently opened files under File -> Open Recent. In Open Recent it only shows Reopen Closed Tabs but that is also not active (i.e not clickable). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic i686 ApportVersion: 2.20.1-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Thu Apr 14 13:16:33 2016 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1570227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1668309] Re: Scaling on xps13 means only a part of the screen is visible at any time.
** Changed in: vino (Ubuntu) Importance: Undecided => High ** Changed in: vino (Ubuntu) Status: Confirmed => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/vino/-/issues #9 https://gitlab.gnome.org/GNOME/vino/-/issues/9 ** Also affects: vino via https://gitlab.gnome.org/GNOME/vino/-/issues/9 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1668309 Title: Scaling on xps13 means only a part of the screen is visible at any time. Status in vino: Unknown Status in vino package in Ubuntu: Triaged Bug description: STEPS: 1. On a 4K system 2. Do a default install of the current iso for Zesty 3. Make sure scalling is set to 2 4. Once in the user session activate desktop-sharing 5. Connect from another machine EXPECTED: I expect to see the whole screen or for the screen to scroll to allow access to the whole screen ACTUAL: Top left hand quarter is the only thing visible and no changes to remina make it better. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2016-11-09 (109 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161109) Package: vino 3.8.1-0ubuntu12 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Tags: zesty Uname: Linux 4.10.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/1668309/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 119899] Re: After-the-fact Filters on custom header won't match for IMAP messages
** Changed in: thunderbird (Ubuntu) Importance: Medium => Low ** Changed in: thunderbird (Ubuntu) Assignee: Mozilla Bugs (mozilla-bugs) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/119899 Title: After-the-fact Filters on custom header won't match for IMAP messages Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird Message filtering appears to be broken on Thunderbird 2.0.0.4~rc1-0ubuntu1 in Gutsy with IMAP. I created a filter for the warthogs list and it would not move the messages from my inbox to the folder I had created. It also did not put anything into the filter log. I tried using the Thunderbird on Feisty with my laptop and it worked fine when using the same settings. Chris Jones mentioned he also noticed the same or perhaps a similar issue today. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/119899/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
As for me this advertised feature of 20.04 was the main factor to install this OS on my hardware, because previous 3 years the lack of this feature prevented me from using Ubuntu. Sadly, this bug affects me too - I am using Nvidia RTX 2070 Super together with Asrock X570 Taichi and Ryzen 3600. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882587] [NEW] Truncated audio frequency response on monitor device
Public bug reported: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: chirp testcase ** Attachment added: "The files used for testing" https://bugs.launchpad.net/bugs/1882587/+attachment/5381754/+files/sound_files.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1882587 Title: Truncated audio frequency response on monitor device Status in pulseaudio package in Ubuntu: New Bug description: Hi. I've found something strange happening when I record the output of a sound card through loopback device audio monitor. If I load the snd-aloop module, then setup a player to play a chirp sound that spans a sine wave between 10Hz and 22kHz through it, and then record the virtual monitor device through Audacity it drops the frequencies something over 16kHz like it have a low pass filter on it. The sampling rate is 44100 or 48000, it doesn't matters, the result is the same. Also in some cases I found that the signal path between channels doesn't have correct syncing. A chirp sound is ideal for testing, because if there is some delay between channels, it would produce a comb filter like frequency response on the mono mix. It also happens with real sound cards, not virtual ones. The question is about how to narrow down the issue. I think it's not ALSA related, because it happens both on the hardware device and the virtual loop one. Attached I put my chirp test sound. I played it on the command line with: $ ffplay -loop 1000 chirp_test.flac Then I setup the recording path with pavucontrol, to target the Audacity input My versions: pulseaudio 12.2-2 linux kernel 5.6.13 $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installed: 1:12.2-9~bionic1 Candidate: 1:12.2-9~bionic1 Version table: *** 1:12.2-9~bionic1 500 500 http://ppa.launchpad.net/mikhailnov/pulseeffects/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7.8 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 1:11.1-1ubuntu7.7 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1:11.1-1ubuntu7 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Attached on this there is a .tar.gz containing both .flac files chirp_test.flac is the original file. chirp_loopback_recorded.flac is the recorded file from the loopback device. Thank You. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1877075] Re: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed
This bug was fixed in the package mutter - 3.36.3-1ubuntu1 --- mutter (3.36.3-1ubuntu1) groovy; urgency=medium * Merge with debian, including new stable upstream release * debian/control: BD on adwaita-icon-theme 3.36.1-2ubuntu3. This version includes all the window decoration icons that mutter uses * Remaining changes with debian: - debian/control: + Update VCS flags to point to ubuntu salsa branch - debian/gbp.conf: update branch to point to ubuntu/master - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr mutter (3.36.3-1) unstable; urgency=medium * New upstream release (LP: #1881971) - Broadcast clipboard/primary offers - Fix monitor screen cast on X11 - Implement touch-mode detecation for the X11 backend (LP: #1880596) - Drop external keyboard detection from touch-mode heuristics - Fix leaked DMA buffers in screencasts - Fixed crashes mutter (3.36.2+12+gb425f1153-1) experimental; urgency=medium * Team upload * New upstream snapshot from the gnome-3-36 branch * d/p/backend-x11-Reintroduce-XInitThreads.patch: Drop patch, applied upstream -- Marco Trevisan (Treviño) Thu, 04 Jun 2020 21:46:56 +0200 ** Changed in: mutter (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1877075 Title: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: In Progress Status in mutter source package in Groovy: Fix Released Bug description: [Impact] This is the #1 crasher of gnome-shell in Ubuntu 20.04, though it's duplicated across multiple problem reports according to locale: https://errors.ubuntu.com/problem/4de3d315d9df1c9699bda54beafa8d52053c https://errors.ubuntu.com/problem/2251b638f7a6167772f922dc5916740522c5c22b https://errors.ubuntu.com/problem/943838b8a80c1da4f8df584b7d2ad3a13361fdd7 https://errors.ubuntu.com/problem/4b78bc9730e8681f0c42fc2ecea14d03544394f0 [Test Case] None known. The plan is to just continue monitoring crash reports. Still, we are confident this is the fix because: * The offending source code in libx11 tells us it is :) and * The crash only started in Ubuntu with gnome-shell 3.34, which is the exact release in which XInitThreads was removed from mutter. [Regression Potential] Low. We add a single function call that tells libX11 to enable thread safety. This same function call as one we had in bionic, cosmic and disco. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1877075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881971] Re: Update to 3.36.3 and SRU it
This bug was fixed in the package mutter - 3.36.3-1ubuntu1 --- mutter (3.36.3-1ubuntu1) groovy; urgency=medium * Merge with debian, including new stable upstream release * debian/control: BD on adwaita-icon-theme 3.36.1-2ubuntu3. This version includes all the window decoration icons that mutter uses * Remaining changes with debian: - debian/control: + Update VCS flags to point to ubuntu salsa branch - debian/gbp.conf: update branch to point to ubuntu/master - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: + X11: Add support for fractional scaling using Randr mutter (3.36.3-1) unstable; urgency=medium * New upstream release (LP: #1881971) - Broadcast clipboard/primary offers - Fix monitor screen cast on X11 - Implement touch-mode detecation for the X11 backend (LP: #1880596) - Drop external keyboard detection from touch-mode heuristics - Fix leaked DMA buffers in screencasts - Fixed crashes mutter (3.36.2+12+gb425f1153-1) experimental; urgency=medium * Team upload * New upstream snapshot from the gnome-3-36 branch * d/p/backend-x11-Reintroduce-XInitThreads.patch: Drop patch, applied upstream -- Marco Trevisan (Treviño) Thu, 04 Jun 2020 21:46:56 +0200 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1881971 Title: Update to 3.36.3 and SRU it Status in mutter package in Ubuntu: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been updates to the clipboard and X11 updates in screencasting and touch-interaction, so ensure there are no problems with those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1881971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
This bug was fixed in the package mutter - 3.36.3-1ubuntu1
---
mutter (3.36.3-1ubuntu1) groovy; urgency=medium
* Merge with debian, including new stable upstream release
* debian/control: BD on adwaita-icon-theme 3.36.1-2ubuntu3.
This version includes all the window decoration icons that mutter uses
* Remaining changes with debian:
- debian/control:
+ Update VCS flags to point to ubuntu salsa branch
- debian/gbp.conf: update branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
+ X11: Add support for fractional scaling using Randr
mutter (3.36.3-1) unstable; urgency=medium
* New upstream release (LP: #1881971)
- Broadcast clipboard/primary offers
- Fix monitor screen cast on X11
- Implement touch-mode detecation for the X11 backend (LP: #1880596)
- Drop external keyboard detection from touch-mode heuristics
- Fix leaked DMA buffers in screencasts
- Fixed crashes
mutter (3.36.2+12+gb425f1153-1) experimental; urgency=medium
* Team upload
* New upstream snapshot from the gnome-3-36 branch
* d/p/backend-x11-Reintroduce-XInitThreads.patch:
Drop patch, applied upstream
-- Marco Trevisan (Treviño) Thu, 04 Jun 2020
21:46:56 +0200
** Changed in: mutter (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible laptops in tablet mode when physical
keyboard disabled
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Focal:
In Progress
Bug description:
[ Impact ]
OSK doesn't appear in X11 when disabling physical keyboard
[ Test case ]
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this
disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search:
- The OSK appear
4. Swipe from bottom of screen in order to summon OSK on demand:
- occurred on Ubuntu 18.04 through 19.10)
[ Regression potential ]
The OSK shows when not needed in setup with no touch-screen or with
touch screen but when not required.
---
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
for the other and then Launchpad somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04.
Only the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under
Xorg, but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said
to have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173
[Desktop-packages] [Bug 1882232] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
This bug was fixed in the package chromium-browser - 83.0.4103.97-0ubuntu1 --- chromium-browser (83.0.4103.97-0ubuntu1) groovy; urgency=medium * New upstream release: 83.0.4103.97 * Do not attempt to install the snap on systems where snapd isn't running (including chroots and WSL) (LP: #1882232) -- Olivier Tilloy Mon, 08 Jun 2020 17:49:24 +0200 ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1882232 Title: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot) Status in chromium-browser package in Ubuntu: Fix Released Bug description: Since snapd integration, chromium-browser package fails to install in a post kickstart chroot. As APT obfuscate snap installation, I worry about auto installation off any other snap package. === When a user is running the installer, and instructs to install chromium-browser with apt in the /target chroot the experience is extremely bad. There are timeouts, there is critical debconf prompt, and no explanation as to what is happening. This is not an upgrade, and no conversion from deb2snap is needed. It is in a chroot, because this is how installers work. It feels like as if on fresh install of chromium-browser it should try "snap install --now-or-schedule-for-later chromium-browser" such that if snapd is running and available install it now, otherwise record a task for snapd to execute if and when it comes up (on first boot). Or like for example, it should call snap prepare-image --classic instead. Overall, imho on new installations of the package, if there is no snapd running, it should be skipped without asking any questions or popping up any dialogues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882585] [NEW] gnome crashes when trying to lock session
Public bug reported: When trying to lock session, either through key combination or clicking 'lock' in the top right menu, gnome unexpectedly freezes. During the time it's freezed I can move the mouse freely, but everything stops (even the clock). After some time it seems to restart because it flashes and everything goes back to normal. After the crash if I try to relock it again it works, but if I try after that the cycle repeats. Sometimes after the crash a crash report window launches accusing a SIGSEGV in gnome-shell. Looking at Logs I can see that the main process was exited and that the core was dumped. Note that at the time it freezes gnome unexpectedly switches the active window. I'm running Ubuntu 20.04 LTS with gnome-shell version 3.36.2-1ubuntu1~20.04.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 17:49:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-06 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882585 Title: gnome crashes when trying to lock session Status in gnome-shell package in Ubuntu: New Bug description: When trying to lock session, either through key combination or clicking 'lock' in the top right menu, gnome unexpectedly freezes. During the time it's freezed I can move the mouse freely, but everything stops (even the clock). After some time it seems to restart because it flashes and everything goes back to normal. After the crash if I try to relock it again it works, but if I try after that the cycle repeats. Sometimes after the crash a crash report window launches accusing a SIGSEGV in gnome-shell. Looking at Logs I can see that the main process was exited and that the core was dumped. Note that at the time it freezes gnome unexpectedly switches the active window. I'm running Ubuntu 20.04 LTS with gnome-shell version 3.36.2-1ubuntu1~20.04.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 17:49:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-06 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882585/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878275] Re: [qxl] wayland session hard freezes on login from GDM (X11 session works fine)
** Attachment added: ""thread apply all bt" from GDB on the core generated on
the VM."
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878275/+attachment/5381745/+files/gdb_vm.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1878275
Title:
[qxl] wayland session hard freezes on login from GDM (X11 session
works fine)
Status in mutter package in Ubuntu:
Confirmed
Bug description:
When I login to my laptop running Ubuntu 20.04, after entering my
username, when I choose the "gear" button and select Ubuntu on Wayland
as the session type, my laptop freezes hard. Mouse and keyboard do not
respond, and the first three times I hit this issue I had to forcibly
power off. The normal (X11) Ubuntu session works fine.
However, I realized that I could still ping and ssh in, and doing that
gave me some clues to the issue.
I have keychain installed for password-less SSH, and my bash_profile has:
---
#!/bin/bash
# Get the aliases and functions
if [ -f $HOME/.bashrc ] ; then
source $HOME/.bashrc
fi
# Setup password-less SSH
[ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
keychain $HOME/.ssh/id_rsa
source $HOME/.keychain/${HOSTNAME}-sh
---
When I login via SSH from another machine after hitting the issue, I get:
[johnjaco@johnjaco-m-v02f: ~/Downloads] ssh john@192.168.1.10
Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support:https://ubuntu.com/advantage
0 updates can be installed immediately.
0 of these updates are security updates.
Your Hardware Enablement Stack (HWE) is supported until April 2025.
Last login: Mon Apr 27 19:41:17 2020 from 192.168.1.3
* keychain 2.8.5 ~ http://www.funtoo.org
* Waiting 5 seconds for lock...
* Found existing ssh-agent: 2086
* Adding 1 ssh key(s): /home/john/.ssh/id_rsa
Enter passphrase for /home/john/.ssh/id_rsa:
* ssh-add: Identities added: /home/john/.ssh/id_rsa
[john@andromeda: ~] pstree
systemd─┬─NetworkManager───2*[{NetworkManager}]
├─accounts-daemon───2*[{accounts-daemon}]
├─acpid
├─avahi-daemon───avahi-daemon
├─bluetoothd
├─boltd───2*[{boltd}]
├─colord───2*[{colord}]
├─containerd───13*[{containerd}]
├─cron
├─cups-browsed───2*[{cups-browsed}]
├─cupsd
├─dbus-daemon
├─dnsmasq───dnsmasq
├─gdm3─┬─gdm-session-wor─┬─gdm-wayland-ses─┬─gnome-session-b───3*[{gnom+
│ │ │ └─2*[{gdm-wayland-ses}]
│ │ └─2*[{gdm-session-wor}]
│ ├─gdm-session-wor─┬─gdm-wayland-ses─┬─bash───keychain───ssh-add
│ │ │ └─2*[{gdm-wayland-ses}]
│ │ └─2*[{gdm-session-wor}]
│ └─2*[{gdm3}]
├─gnome-keyring-d───2*[{gnome-keyring-d}]
├─iio-sensor-prox───2*[{iio-sensor-prox}]
├─irqbalance───{irqbalance}
├─2*[kerneloops]
├─libvirtd───16*[{libvirtd}]
├─networkd-dispat
├─packagekitd───2*[{packagekitd}]
├─polkitd───2*[{polkitd}]
├─rsyslogd───3*[{rsyslogd}]
├─rtkit-daemon───2*[{rtkit-daemon}]
├─ssh-agent
├─sshd───sshd───sshd───bash───pstree
├─switcheroo-cont───2*[{switcheroo-cont}]
├─systemd─┬─(sd-pam)
│ ├─at-spi-bus-laun─┬─dbus-daemon
│ │ └─3*[{at-spi-bus-laun}]
│ ├─at-spi2-registr───2*[{at-spi2-registr}]
│ ├─dbus-daemon
│ ├─dconf-service───2*[{dconf-service}]
│ ├─gjs───10*[{gjs}]
│ ├─gnome-keyring-d───3*[{gnome-keyring-d}]
│ ├─gnome-session-b───3*[{gnome-session-b}]
│ ├─gnome-session-c───{gnome-session-c}
│ ├─gnome-shell─┬─Xwayland───20*[{Xwayland}]
│ │ ├─ibus-daemon─┬─ibus-dconf───3*[{ibus-dconf}]
│ │ │
├─ibus-engine-sim───2*[{ibus-engi+
│ │ │ └─2*[{ibus-daemon}]
│ │ └─16*[{gnome-shell}]
│ ├─goa-daemon───3*[{goa-daemon}]
│ ├─goa-identity-se───2*[{goa-identity-se}]
│ ├─gsd-a11y-settin───3*[{gsd-a11y-settin}]
│ ├─gsd-color───3*[{gsd-color}]
│ ├─gsd-keyboard───3*[{gsd-keyboard}]
│ ├─gsd-media-keys───3*[{gsd-media-keys}]
│ ├─gsd-power───3*[{gsd-power}]
│ ├─gsd-print-notif───2*[{gsd-print-notif}]
│ ├─gsd-printer───2*[{gsd-printer}]
│
[Desktop-packages] [Bug 1878275] Re: [qxl] wayland session hard freezes on login from GDM (X11 session works fine)
** Attachment added: ""thread apply all bt" from GDB on the core generated on
the laptop."
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878275/+attachment/5381746/+files/gdb_laptop.log
** Changed in: mutter (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1878275
Title:
[qxl] wayland session hard freezes on login from GDM (X11 session
works fine)
Status in mutter package in Ubuntu:
Confirmed
Bug description:
When I login to my laptop running Ubuntu 20.04, after entering my
username, when I choose the "gear" button and select Ubuntu on Wayland
as the session type, my laptop freezes hard. Mouse and keyboard do not
respond, and the first three times I hit this issue I had to forcibly
power off. The normal (X11) Ubuntu session works fine.
However, I realized that I could still ping and ssh in, and doing that
gave me some clues to the issue.
I have keychain installed for password-less SSH, and my bash_profile has:
---
#!/bin/bash
# Get the aliases and functions
if [ -f $HOME/.bashrc ] ; then
source $HOME/.bashrc
fi
# Setup password-less SSH
[ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
keychain $HOME/.ssh/id_rsa
source $HOME/.keychain/${HOSTNAME}-sh
---
When I login via SSH from another machine after hitting the issue, I get:
[johnjaco@johnjaco-m-v02f: ~/Downloads] ssh john@192.168.1.10
Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support:https://ubuntu.com/advantage
0 updates can be installed immediately.
0 of these updates are security updates.
Your Hardware Enablement Stack (HWE) is supported until April 2025.
Last login: Mon Apr 27 19:41:17 2020 from 192.168.1.3
* keychain 2.8.5 ~ http://www.funtoo.org
* Waiting 5 seconds for lock...
* Found existing ssh-agent: 2086
* Adding 1 ssh key(s): /home/john/.ssh/id_rsa
Enter passphrase for /home/john/.ssh/id_rsa:
* ssh-add: Identities added: /home/john/.ssh/id_rsa
[john@andromeda: ~] pstree
systemd─┬─NetworkManager───2*[{NetworkManager}]
├─accounts-daemon───2*[{accounts-daemon}]
├─acpid
├─avahi-daemon───avahi-daemon
├─bluetoothd
├─boltd───2*[{boltd}]
├─colord───2*[{colord}]
├─containerd───13*[{containerd}]
├─cron
├─cups-browsed───2*[{cups-browsed}]
├─cupsd
├─dbus-daemon
├─dnsmasq───dnsmasq
├─gdm3─┬─gdm-session-wor─┬─gdm-wayland-ses─┬─gnome-session-b───3*[{gnom+
│ │ │ └─2*[{gdm-wayland-ses}]
│ │ └─2*[{gdm-session-wor}]
│ ├─gdm-session-wor─┬─gdm-wayland-ses─┬─bash───keychain───ssh-add
│ │ │ └─2*[{gdm-wayland-ses}]
│ │ └─2*[{gdm-session-wor}]
│ └─2*[{gdm3}]
├─gnome-keyring-d───2*[{gnome-keyring-d}]
├─iio-sensor-prox───2*[{iio-sensor-prox}]
├─irqbalance───{irqbalance}
├─2*[kerneloops]
├─libvirtd───16*[{libvirtd}]
├─networkd-dispat
├─packagekitd───2*[{packagekitd}]
├─polkitd───2*[{polkitd}]
├─rsyslogd───3*[{rsyslogd}]
├─rtkit-daemon───2*[{rtkit-daemon}]
├─ssh-agent
├─sshd───sshd───sshd───bash───pstree
├─switcheroo-cont───2*[{switcheroo-cont}]
├─systemd─┬─(sd-pam)
│ ├─at-spi-bus-laun─┬─dbus-daemon
│ │ └─3*[{at-spi-bus-laun}]
│ ├─at-spi2-registr───2*[{at-spi2-registr}]
│ ├─dbus-daemon
│ ├─dconf-service───2*[{dconf-service}]
│ ├─gjs───10*[{gjs}]
│ ├─gnome-keyring-d───3*[{gnome-keyring-d}]
│ ├─gnome-session-b───3*[{gnome-session-b}]
│ ├─gnome-session-c───{gnome-session-c}
│ ├─gnome-shell─┬─Xwayland───20*[{Xwayland}]
│ │ ├─ibus-daemon─┬─ibus-dconf───3*[{ibus-dconf}]
│ │ │
├─ibus-engine-sim───2*[{ibus-engi+
│ │ │ └─2*[{ibus-daemon}]
│ │ └─16*[{gnome-shell}]
│ ├─goa-daemon───3*[{goa-daemon}]
│ ├─goa-identity-se───2*[{goa-identity-se}]
│ ├─gsd-a11y-settin───3*[{gsd-a11y-settin}]
│ ├─gsd-color───3*[{gsd-color}]
│ ├─gsd-keyboard───3*[{gsd-keyboard}]
│ ├─gsd-media-keys───3*[{gsd-media-keys}]
│ ├─gsd-power───3*[{gsd-power}]
│ ├─gsd-print-notif───2*[{gsd-print-notif}]
[Desktop-packages] [Bug 1878275] Re: [qxl] wayland session hard freezes on login from GDM (X11 session works fine)
I used apport-unpack to extract the coredump from the crash file, and
then ran gdb on it. The two attachments gdb_laptop.log and gdb_vm.log
are from gdb in the laptop and in the VM, respectively. Without debug
symbols, the backtraces are not complete.
I tried to install debug symbols in the VM, as detailed at
https://wiki.ubuntu.com/Debug%20Symbol%20Packages , but it failed due
to:
john@ubuntu-test:~/Downloads/core$ sudo apt install gnome-shell-dbgsym
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
gnome-shell-dbgsym : Depends: gnome-shell (= 3.36.1-5ubuntu1) but
3.36.2-1ubuntu1~20.04.1 is to be installed
E: Unable to correct problems, you have held broken packages.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1878275
Title:
[qxl] wayland session hard freezes on login from GDM (X11 session
works fine)
Status in mutter package in Ubuntu:
Confirmed
Bug description:
When I login to my laptop running Ubuntu 20.04, after entering my
username, when I choose the "gear" button and select Ubuntu on Wayland
as the session type, my laptop freezes hard. Mouse and keyboard do not
respond, and the first three times I hit this issue I had to forcibly
power off. The normal (X11) Ubuntu session works fine.
However, I realized that I could still ping and ssh in, and doing that
gave me some clues to the issue.
I have keychain installed for password-less SSH, and my bash_profile has:
---
#!/bin/bash
# Get the aliases and functions
if [ -f $HOME/.bashrc ] ; then
source $HOME/.bashrc
fi
# Setup password-less SSH
[ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
keychain $HOME/.ssh/id_rsa
source $HOME/.keychain/${HOSTNAME}-sh
---
When I login via SSH from another machine after hitting the issue, I get:
[johnjaco@johnjaco-m-v02f: ~/Downloads] ssh john@192.168.1.10
Welcome to Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support:https://ubuntu.com/advantage
0 updates can be installed immediately.
0 of these updates are security updates.
Your Hardware Enablement Stack (HWE) is supported until April 2025.
Last login: Mon Apr 27 19:41:17 2020 from 192.168.1.3
* keychain 2.8.5 ~ http://www.funtoo.org
* Waiting 5 seconds for lock...
* Found existing ssh-agent: 2086
* Adding 1 ssh key(s): /home/john/.ssh/id_rsa
Enter passphrase for /home/john/.ssh/id_rsa:
* ssh-add: Identities added: /home/john/.ssh/id_rsa
[john@andromeda: ~] pstree
systemd─┬─NetworkManager───2*[{NetworkManager}]
├─accounts-daemon───2*[{accounts-daemon}]
├─acpid
├─avahi-daemon───avahi-daemon
├─bluetoothd
├─boltd───2*[{boltd}]
├─colord───2*[{colord}]
├─containerd───13*[{containerd}]
├─cron
├─cups-browsed───2*[{cups-browsed}]
├─cupsd
├─dbus-daemon
├─dnsmasq───dnsmasq
├─gdm3─┬─gdm-session-wor─┬─gdm-wayland-ses─┬─gnome-session-b───3*[{gnom+
│ │ │ └─2*[{gdm-wayland-ses}]
│ │ └─2*[{gdm-session-wor}]
│ ├─gdm-session-wor─┬─gdm-wayland-ses─┬─bash───keychain───ssh-add
│ │ │ └─2*[{gdm-wayland-ses}]
│ │ └─2*[{gdm-session-wor}]
│ └─2*[{gdm3}]
├─gnome-keyring-d───2*[{gnome-keyring-d}]
├─iio-sensor-prox───2*[{iio-sensor-prox}]
├─irqbalance───{irqbalance}
├─2*[kerneloops]
├─libvirtd───16*[{libvirtd}]
├─networkd-dispat
├─packagekitd───2*[{packagekitd}]
├─polkitd───2*[{polkitd}]
├─rsyslogd───3*[{rsyslogd}]
├─rtkit-daemon───2*[{rtkit-daemon}]
├─ssh-agent
├─sshd───sshd───sshd───bash───pstree
├─switcheroo-cont───2*[{switcheroo-cont}]
├─systemd─┬─(sd-pam)
│ ├─at-spi-bus-laun─┬─dbus-daemon
│ │ └─3*[{at-spi-bus-laun}]
│ ├─at-spi2-registr───2*[{at-spi2-registr}]
│ ├─dbus-daemon
│ ├─dconf-service───2*[{dconf-service}]
│ ├─gjs───10*[{gjs}]
│ ├─gnome-keyring-d───3*[{gnome-keyring-d}]
│ ├─gnome-session-b───3*[{gnome-session-b}]
│ ├─gnome-session-c───{gnome-session-c}
[Desktop-packages] [Bug 1882583] [NEW] [SRU] Enable support for Victoria Cloud Archive
Public bug reported: Please add support for: cloud-archive:victoria cloud-archive:victoria-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the victoria cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:victoria sudo add-apt-repository cloud-archive:victoria-proposed [Regression potential] Limited - just a data item addition ** Affects: software-properties (Ubuntu) Importance: High Status: Triaged ** Affects: software-properties (Ubuntu Focal) Importance: High Status: Triaged ** Affects: software-properties (Ubuntu Groovy) Importance: High Status: Triaged ** Also affects: software-properties (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Focal) Status: New => Triaged ** Changed in: software-properties (Ubuntu Groovy) Status: New => Triaged ** Changed in: software-properties (Ubuntu Focal) Importance: Undecided => High ** Changed in: software-properties (Ubuntu Groovy) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1882583 Title: [SRU] Enable support for Victoria Cloud Archive Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Focal: Triaged Status in software-properties source package in Groovy: Triaged Bug description: Please add support for: cloud-archive:victoria cloud-archive:victoria-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the victoria cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:victoria sudo add-apt-repository cloud-archive:victoria-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1882583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
It looks like some fixes were merged in GNOME/gtk: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/1606 . Waiting for them to be merged into ubuntu too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
I have this issue as well with drivers 440.64, it is really annoying. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1882481] Re: A dialog box stays on desktop and does not go away
Thank you, attached is a screenshot and also journal.txt. Regards, Joe On 6/8/20 12:11 AM, Daniel van Vugt wrote: > This sounds like bug 1824874. To help us check that please: > > 1. Provide a screenshot or photo of the problem; and > > 2. After the dialog has appeared run: > >journalctl -b0 > journal.txt > >or if you had to reboot then run: > >journalctl -b-1 > prevboot.txt > >and attach the resulting text file here. > > > ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > ** Attachment added: "Screenshot from 2020-06-08 14-02-35.png" https://bugs.launchpad.net/bugs/1882481/+attachment/5381742/+files/Screenshot%20from%202020-06-08%2014-02-35.png ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1882481/+attachment/5381743/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882481 Title: A dialog box stays on desktop and does not go away Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon rebooting, I get dialog box Authentication Required Authentication is required to start 'cups.service'. I can type in the password and click Authenticate, but then nothing happens. I can't see under the box. I can't move the box, can't cancel the dialog. But, I can click on where I know the underneath icon to be and that click is accepted and the program in question runs. It appears the display manager does not remove the image after it is done with the dialog. I have recently done a clean install of 20.04. There is a screenshot in this Stack Exchange post: https://askubuntu.com/questions/1242999/dialog-box-does-not-accept-input-stays-on-top-and-hides-everything-under-it-ub ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 23:10:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 3.3-19, 5.4.0-31-generic, x86_64: installed amdgpu, 3.3-19, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 [1462:8a92] InstallationDate: Installed on 2020-05-12 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=ebb08f84-7501-4461-a5c4-c69c3c25d9b0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0804 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME 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.:bvr0804:bd11/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx: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 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 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/1882481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1881923] Re: No icons in file picker
How do I find this out? I didn't change anything design related in Ubuntu or chromium - so it should be the standard that comes with a fresh installation of 20.04. But if you tell me how I'll make sure and check it... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1881923 Title: No icons in file picker Status in chromium-browser package in Ubuntu: Incomplete Bug description: I installed chromium via snap on Ubuntu 20.04. When the file picker is opend (for example to upload some files) all icons are missing. Files and folders have no icon (see attached screenshot). Ubuntu 20.04 LTS Chromium Version 83.0.4103.61 (Official Build) snap (64-bit) Maybe it is a problem with the apparmor-profile? [27780.715573] audit: type=1400 audit(1591194917.741:3258): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [27780.737385] audit: type=1400 audit(1591194917.761:3259): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [27781.003139] audit: type=1400 audit(1591194918.029:3260): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [27781.012869] audit: type=1107 audit(1591194918.037:3261): pid=1073 uid=100 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.285" pid=5553 label="snap.chromium.chromium" peer_pid=156208 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=100 hostname=? addr=? terminal=?' [27784.173782] audit: type=1400 audit(1591194921.197:3262): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1881923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882440] Re: BadLength (poly request too large or internal Xlib length error) when using xfreerdp
Yes, sure: https://github.com/FreeRDP/FreeRDP/issues/6264# ** Bug watch added: freerdp-issues #6264 https://github.com/FreeRDP/FreeRDP/issues/6264 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1882440 Title: BadLength (poly request too large or internal Xlib length error) when using xfreerdp Status in freerdp2 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: when using xfreerdp with Windows 10 and using the a screen capture tool on the remote host (windows 10) xfreerdp consistently fails with BadLength X error. I reported this also to xfreerdp, where it was designated as potential internal error in X/Xlib. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 18:27:46 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Radeon RX 570 Pulse 4GB [1da2:e353] InstallationDate: Installed on 2020-05-14 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4022b63e-4e73-4175-99a6-641a1284aeb3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.70:bd04/21/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International 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.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1882440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882309] Re: Cutted off font on Facebook in Firefox
Launchpad has imported 2 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1644178. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-06-08T16:21:44+00:00 Konrad Kołodziejczyk wrote: Created attachment 9154965 Zrzut-ekranu-z-2020-06-06-00-07-36.png User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0 Steps to reproduce: I've opening Facebook site in Firefox on Ubuntu 20.04, Ubuntu MATE 20.04 and Xubuntu 20.04. Actual results: The domain of site is cutted off on Facebook site as it is seen on attached screenshot. https://i.postimg.cc/44Bt3H7j/Zrzut-ekranu-z-2020-06-06-00-07-36.png I've seen this problem in Ubuntu 20.04, Ubuntu Mate 20.04, Xubuntu 20.04 and I haven't seen in Ubuntu 19.10 and Windows 10. This issue is merely in Firefox. Facebook site in Google Chrome looks ok. I've reported this issue also on launchpad. https://bugs.launchpad.net/bugs/1882309 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1882309/comments/3 On 2020-06-08T17:17:42+00:00 Release-mgmt-account-bot wrote: [Bugbug](https://github.com/mozilla/bugbug/) thinks this bug should belong to this component, but please revert this change in case of error. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1882309/comments/5 ** Changed in: firefox Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1882309 Title: Cutted off font on Facebook in Firefox Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: The domain of site is cutted off on Facebook site as it is seen on this screenshot. https://i.postimg.cc/44Bt3H7j/Zrzut-ekranu-z-2020-06-06-00-07-36.png I've seen this problem in Ubuntu 20.04 and I haven't seen in Ubuntu 19.10. This issue is merely in Firefox. Facebook site in Google Chrome looks ok. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 77.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: konrad 1159 F pulseaudio /dev/snd/pcmC1D0p: konrad 1159 F...m pulseaudio /dev/snd/controlC0: konrad 1159 F pulseaudio BuildID: 2020060727 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: MATE Date: Sat Jun 6 00:05:28 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2020-06-05 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.8 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:731 Profile0PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=77.0.1/2020060727 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 0V8RX3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1882531] Re: desktop context not localized
you can set language to german and see german context-menu on right- clicking the desktop? and your home-icon is named "Persönlicher Ordner" like in gnome-panel? for me it looks like on desktop the language-"file" is not loaded/used. i tried your step with Parts of the Context-Menu-Entries and most of them are not translated frank@frank-G5-U20:~ $ echo $(gettext -d desktop-icons 'Home') Home frank@frank-G5-U20:~ $ echo $(gettext -d desktop-icons 'New Folder') Neuer Ordner frank@frank-G5-U20:~ $ echo $(gettext -d desktop-icons 'Placement') Placement frank@frank-G5-U20:~ $ echo $(gettext -d desktop-icons 'Sort by') Sort by frank@frank-G5-U20:~ $ echo $(gettext -d desktop-icons 'Open Terminal') Open Terminal maybe "Display Settings" is used from another application? but context- menu is also not translated...like the "New Folder" where gettext shows translation -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1882531 Title: desktop context not localized Status in Ubuntu Translations: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: Hi, at least in german environment the rightclick menu is not localized (and also the home-link). see screenshot attached regards Frank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1882531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882531] Re: desktop context not localized
So your German language packs seem to be in order (I would have been surprised otherwise). I'm out of ideas for now, unfortunately. It may be a subtle configuration issue. It would be good if you could describe step by step how to reproduce the issue. I for one cannot reproduce it on my Ubuntu 20.04. ** Changed in: ubuntu-translations Status: Incomplete => New ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1882531 Title: desktop context not localized Status in Ubuntu Translations: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: Hi, at least in german environment the rightclick menu is not localized (and also the home-link). see screenshot attached regards Frank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1882531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882531] Re: desktop context not localized
frank@frank-G5-U20:~ $ echo $(gettext -d desktop-icons 'Display Settings') Anzeigeeinstellungen frank@frank-G5-U20:~ $ so correctly translated -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1882531 Title: desktop context not localized Status in Ubuntu Translations: Incomplete Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: Hi, at least in german environment the rightclick menu is not localized (and also the home-link). see screenshot attached regards Frank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1882531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
