[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Confirmed => 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/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+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 1883174] Re: Some desktop icons disappear
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => Confirmed ** Also affects: gnome-shell-extension-desktop-icons via https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/200 Importance: Unknown Status: Unknown -- 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/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+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 1883174] Re: Some desktop icons disappear
This has already been reported by another person there. ID: https://gitlab.gnome.org/World/ShellExtensions/desktop- icons/-/issues/200 ** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues #200 https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/200 -- 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/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1883174/+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 1883206] Re: Persistent high CPU load (~80%)
Also if you have indicator-multiload then please remove it (bug 784055). ** Description changed: - gnome shell has a persistent high CPI load that make using the PC + gnome shell has a persistent high CPU load that make using the PC painful. - PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND + PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2184 stefan20 0 5129188 435472 137572 R 78.2 1.1 176:22.98 gnome-shell Don't have much more to report here. Will try to disable some extensions I use, to see if they are the cause. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 20:49:44 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-28 (227 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1883206 Title: Persistent high CPU load (~80%) Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome shell has a persistent high CPU load that make using the PC painful. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2184 stefan20 0 5129188 435472 137572 R 78.2 1.1 176:22.98 gnome-shell Don't have much more to report here. Will try to disable some extensions I use, to see if they are the cause. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 20:49:44 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-28 (227 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/1883206/+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 1883206] Re: Persistent high CPU load (~80%)
Yes please remove all extensions and then tell us if the problem persists. I expect it won't. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: performance -- 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/1883206 Title: Persistent high CPU load (~80%) Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome shell has a persistent high CPU load that make using the PC painful. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2184 stefan20 0 5129188 435472 137572 R 78.2 1.1 176:22.98 gnome-shell Don't have much more to report here. Will try to disable some extensions I use, to see if they are the cause. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 20:49:44 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-28 (227 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/1883206/+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 1883206] [NEW] Persistent high CPU load (~80%)
Public bug reported: gnome shell has a persistent high CPI load that make using the PC painful. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2184 stefan20 0 5129188 435472 137572 R 78.2 1.1 176:22.98 gnome-shell Don't have much more to report here. Will try to disable some extensions I use, to see if they are the cause. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 20:49:44 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-28 (227 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/1883206 Title: Persistent high CPU load (~80%) Status in gnome-shell package in Ubuntu: New Bug description: gnome shell has a persistent high CPI load that make using the PC painful. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2184 stefan20 0 5129188 435472 137572 R 78.2 1.1 176:22.98 gnome-shell Don't have much more to report here. Will try to disable some extensions I use, to see if they are the cause. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 20:49:44 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-28 (227 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/1883206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
not before the last of the series, 20.0.8, is tested.. I'll upload it today -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: Fix Released Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883192] Re: Video mode is missing
It looks like the problem might be confined to the "nouveau" Xorg driver. Actually I don't think we recommend that driver anymore. We recommend "modesetting" instead. Please look in /usr/share/X11/xorg.conf.d and tell us if you can find the config file that's telling Xorg to use "nouveau". If you find it then please remove that file and reboot. It looks like the offending config file also contains "". ** Package changed: xorg (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu) ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New => Incomplete ** Summary changed: - Video mode is missing + [nouveau] Video mode 1600x1200 is missing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1883192 Title: [nouveau] Video mode 1600x1200 is missing Status in xserver-xorg-video-nouveau package in Ubuntu: Incomplete Bug description: Video mode 1600x1200 is not present. In the file Xorglog.txt, we can see that it's extracted from the EDID but not present in the list of "modeline". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CompositorRunning: None CurrentDesktop: XFCE Date: Fri Jun 12 02:17:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation NV41M [GeForce Go 6800] [10de:00c8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions NV41M [GeForce Go 6800] [1734:107c] InstallationDate: Installed on 2020-04-17 (55 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: FUJITSU SIEMENS Amilo M3438 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=f910d7c1-f499-455a-ade2-472c22149dcd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10C dmi.board.name: P71EN0 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10C:bd10/05/2005:svnFUJITSUSIEMENS:pnAmiloM3438Series:pvr:rvn:rnP71EN0:rvr:cvnFUJITSUSIEMENS:ct10:cvr: dmi.product.name: Amilo M3438 Series dmi.sys.vendor: FUJITSU SIEMENS 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 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1883192/+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%
This affects me too, external monitors only work when using the Nvidia card exclusively on my laptop, so fractional scaling is a must, but it just flickers and selects 200% instead. -- 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 1883134] Re: Xorg Nvidia problem-freeze at login
Please run these commands: lspci -k > lspcik.txt journal -b0 > journal.txt and then attach the resulting text files here. Also if you can please try Ubuntu 20.04 instead: https://releases.ubuntu.com/20.04/ ** 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-server in Ubuntu. https://bugs.launchpad.net/bugs/1883134 Title: Xorg Nvidia problem-freeze at login Status in xorg-server package in Ubuntu: Incomplete Bug description: I've got a problem,where nvidia drivers cannot work with Xorg,but im ok with Wayland. I tried different things. Im trying now to reinstall xorg and use nouvaeu drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 18:19:02 2020 InstallationDate: Installed on 2019-12-30 (163 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1883134/+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 1838838] Re: username is not saved in openconnect connection dialog
Here's a workaround from the RedHat folks. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2105 nmcli con mod VPNNAME vpn.secrets 'form:main:username=USERNAME','save_passwords=yes' ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2105 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2105 -- 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/1838838 Title: username is not saved in openconnect connection dialog Status in GNOME Shell: New Status in NetworkManager: New Status in gnome-shell package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Bug description: Same issue as https://bugs.launchpad.net/ubuntu/+source/network- manager-openconnect/+bug/1609700 This was marked resolved. The report of its reappearance in Ubuntu 19.04 and 19.10 has not been acknowledged. This was working for me in 18.10, but a fresh install of 19.04 and 19.10 show that it is back. The password is saved when the option to save passwords is selected, but the username must be entered manually upon connection. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838838/+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 1883174] Re: Some desktop icons disappear
Please report the issue to the developer here: https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues and then tell us the new issue ID. ** Tags added: focal ** 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/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1883174/+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 1883197] Re: Headset not working
Great, it is a regression in the 3.2, and fixed in the 3.3. -- 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/1883197 Title: Headset not working Status in alsa-driver package in Ubuntu: New Bug description: When I plug the headset in and when the gnome "Select Audio Devices" pop-up and select "Headset" (rather than Headphones), the sound doesn't go through. But when I select "Headphones" it does. The only way I can get sound coming through the Headset is by choosing "Headphones" and manually select the Headset mic in the sound settings to have my headset working properly. This issue appears in 20.04. I didn't have this issue before I upgrade from 19.10 (and previous releases). 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal274918 F pulseaudio /dev/snd/pcmC0D0c: pascal274918 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Thu Jun 11 19:50:11 2020 InstallationDate: Installed on 2019-05-14 (394 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-18 (25 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0NFGCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0NFGCT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883197/+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 1883197] Re: Headset not working
I just upgrade to pulseaudio:amd64 1:13.99.1-1ubuntu3.3 and I don't have the issue anymore :) -- 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/1883197 Title: Headset not working Status in alsa-driver package in Ubuntu: New Bug description: When I plug the headset in and when the gnome "Select Audio Devices" pop-up and select "Headset" (rather than Headphones), the sound doesn't go through. But when I select "Headphones" it does. The only way I can get sound coming through the Headset is by choosing "Headphones" and manually select the Headset mic in the sound settings to have my headset working properly. This issue appears in 20.04. I didn't have this issue before I upgrade from 19.10 (and previous releases). 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal274918 F pulseaudio /dev/snd/pcmC0D0c: pascal274918 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Thu Jun 11 19:50:11 2020 InstallationDate: Installed on 2019-05-14 (394 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-18 (25 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0NFGCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0NFGCT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883197/+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 1883197] Re: Headset not working
When running `alasactl monitor` and plugging the headset and choose "Headphones", I see the following logs line ``` node hw:0, #21 (0,0,0,Headphone Mic Jack,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE ``` and when I plug it and select "Headset" I see the following log lines ``` node hw:0, #21 (0,0,0,Headphone Mic Jack,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE ``` The only difference is when selecting "Headphones" 3 more lines are added ``` node hw:0, #15 (2,0,0,Headphone Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE node hw:0, #16 (2,0,0,Internal Mic Boost Volume,0) VALUE ``` But after several plugin/plugout (about a dozen of time) I only see the following log lines regardless of choosing "Headphones" or "Headset" but still no audio coming out to the Headset when choosing "Headset". ```node hw:0, #21 (0,0,0,Headphone Mic Jack,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #4 (2,0,0,Speaker Playback Switch,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #3 (2,0,0,Speaker Playback Volume,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #2 (2,0,0,Headphone Playback Switch,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #1 (2,0,0,Headphone Playback Volume,0) VALUE node hw:0, #11 (2,0,0,Capture Source,0) VALUE node hw:0, #11 (2,0,0,Capture Source,0) VALUE ``` ** Description changed: - When I plug the headset in and when the gnome "Select Audio Devices" - popup and select "Headset" (rather than Headphones), the sound doesn't - go through. But when I select "Headphones" it does. But I then need to - manually select the Headset mic in the sound settings to have my headset - working properly. This issue appear in 20.04. I didn't had this issue - before I upgrade from 19.10 (and previous releases). + When I plug the headset in and when the gnome "Select Audio Devices" pop-up and select "Headset" (rather than Headphones), the sound doesn't go through. But when I select "Headphones" it does. + The only way I can get sound coming through the Headset is by choosing "Headphones" and manually select the Headset mic in the sound settings to have my headset working properly. This issue appears in 20.04. I didn't have this issue before I upgrade from 19.10 (and previous releases). 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: pascal274918 F pulseaudio - /dev/snd/pcmC0D0c: pascal274918 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: pascal274918 F pulseaudio + /dev/snd/pcmC0D0c: pascal274918 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Thu Jun 11 19:50:11 2020 InstallationDate: Installed on 2019-05-14 (394 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left]
[Desktop-packages] [Bug 1883130] Re: Icons overlay at top bar
** Package changed: xorg (Ubuntu) => gnome-shell-extension-appindicator (Ubuntu) ** Summary changed: - Icons overlay at top bar + Icons overlay the clock ** Summary changed: - Icons overlay the clock + Icons overlay the clock in the panel ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #423 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/423 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/423 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1883130 Title: Icons overlay the clock in the panel Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-appindicator package in Ubuntu: Triaged Bug description: When I open some apps, some of them displays a top bar icon. At some point, there is so many icons than they overlay the clock, as shown in attachment. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-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: ubuntu:GNOME Date: Thu Jun 11 11:54:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:139d] InstallationDate: Installed on 2020-05-26 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. S451LA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=85895dc0-0f4c-4998-9659-78a68fab28cd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S451LA.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S451LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS451LA.403:bd01/17/2014:svnASUSTeKCOMPUTERINC.:pnS451LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS451LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: S dmi.product.name: S451LA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/gnome-shell/+bug/1883130/+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 1883092] Re: Xorg freeze
If the mouse is still moving then it's the gnome-shell process that's frozen, not Xorg. Please run this command: gsettings list-recursively org.gnome.shell > settings.txt and then attach the resulting text file. ** Summary changed: - Xorg freeze + Gnome Shell freeze ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1883092 Title: Gnome Shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: the computer will freeze everything but mouse and fail to boot back up for around 30 minutes after 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] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 11:57:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2020-05-29 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 2325CJ0 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=84df2c1d-136c-448c-b0a6-8483339655b3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325CJ0 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2325CJ0:pvrThinkPadX230:rvnLENOVO:rn2325CJ0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2325CJ0 dmi.product.sku: LENOVO_MT_2325 dmi.product.version: ThinkPad X230 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.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/gnome-shell/+bug/1883092/+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 1883092] Re: Gnome Shell freeze
Please also wait until the freeze happens again and then when it is "back up for around 30 minutes after" run: journalctl -b0 > journal.txt and attach the resulting text file here. -- 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/1883092 Title: Gnome Shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: the computer will freeze everything but mouse and fail to boot back up for around 30 minutes after 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] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 11:57:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2020-05-29 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 2325CJ0 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=84df2c1d-136c-448c-b0a6-8483339655b3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325CJ0 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2325CJ0:pvrThinkPadX230:rvnLENOVO:rn2325CJ0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2325CJ0 dmi.product.sku: LENOVO_MT_2325 dmi.product.version: ThinkPad X230 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.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/gnome-shell/+bug/1883092/+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 1883062] Re: [Intel Core 2 Duo T5750 / 965GM] gnome lagging in opening apps and video playing
** Summary changed: - [Intel Core 2 Duo T5750] gnome lagging in opening apps and video playing + [Intel Core 2 Duo T5750 / 965GM] gnome lagging in opening apps and video playing -- 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/1883062 Title: [Intel Core 2 Duo T5750 / 965GM] gnome lagging in opening apps and video playing Status in gnome-shell package in Ubuntu: Incomplete Bug description: apps lagging in opening and operation. video in browser lags a lot. 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: wl ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 13:05:16 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-29 (12 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/1883062/+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 1882857] Re: [amdgpu] Black screen when switching users
** Package changed: ubuntu => kwin (Ubuntu) ** Summary changed: - [amdgpu] Black screen when switching users + [amdgpu] [KDE] Black screen when switching users ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: kwin (Ubuntu) Status: Incomplete => New -- 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/1882857 Title: [amdgpu] [KDE] Black screen when switching users Status in kwin package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: When i use in the menu "switch user" I go to the login dialog, cohose different user, enter the password (or use fingerprint reader) then the screen gets black and nothing happens. I cannot login and must reboot the laptop to login again. 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] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jun 10 01:23:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-05-17 (23 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=ed4f23e0-6712-4e26-a125-0da798c01065 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 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:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 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.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/kwin/+bug/1882857/+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
Gnome Tweaks is completely wrong, which is bug 1718850. And yes I agree this is concerning: org.gnome.shell enabled-extensions ['update- extensi...@franglais125.gmail.com', 'move_cl...@rmy.pobox.com'] To address that you might want to delete ~/.local/share/gnome- shell/extensions and then restart. -- 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/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell package in Ubuntu: Incomplete 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/+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 1880365] Re: Dell Vostro 5391 trackpad loses functionality after sleep
** No longer affects: xserver-xorg-input-libinput (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1880365 Title: Dell Vostro 5391 trackpad loses functionality after sleep Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: On 18.04 and 19.10, the Dell Vostro 5391 would lose the trackpad cursor control completely, manifesting as a frozen cursor. On 20.04, it comes back from sleep as a regular mouse, but tracks motion differently and doesn't recognize any normal gestures or the right- click. Plugging a USB mouse in is a workaround, but having the trackpad: DELL096F:00 27C6:01F0 Mouse: Applying InputClass "libinput pointer catchall" work properly through sleep/wake cycles would be ideal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun May 24 02:29:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed nvidia, 440.64, 5.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:096f] Subsystem: Dell GP108M [GeForce MX250] [1028:096f] InstallationDate: Installed on 2020-04-06 (48 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 5391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgubuntu--budgie-root ro mitigations=off transparent_hugepage=always SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 055C5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/25/2020:svnDellInc.:pnVostro5391:pvr:rvnDellInc.:rn055C5P:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5391 dmi.product.sku: 096F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1880365/+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 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side Status in gnome-shell package in Ubuntu: Confirmed Bug description: When clock changes value, it doesn't displaying time properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882291/+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 1882291] Re: Displaying time issue before login
Yes indeed. I'm also seeing this bug in the gnome-shell top panel. ** Tags added: focal ** Summary changed: - Displaying time issue before login + Gnome Shell clock is truncated/corrupt on the right side -- 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/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side Status in gnome-shell package in Ubuntu: Confirmed Bug description: When clock changes value, it doesn't displaying time properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882291/+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 1880365] Re: Dell Vostro 5391 trackpad loses functionality after sleep
OK. I'm running Ubuntu under Wayland now, and after the laptop wakes up, the mouse cursor tracks -really- quickly on the trackpad and I lose multitouch and right-click. I can still mouse-around and click, but no more context menus or two-finger scrolling. A restart fixes it. I guess it runs deeper than Xorg. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1880365 Title: Dell Vostro 5391 trackpad loses functionality after sleep Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Incomplete Bug description: On 18.04 and 19.10, the Dell Vostro 5391 would lose the trackpad cursor control completely, manifesting as a frozen cursor. On 20.04, it comes back from sleep as a regular mouse, but tracks motion differently and doesn't recognize any normal gestures or the right- click. Plugging a USB mouse in is a workaround, but having the trackpad: DELL096F:00 27C6:01F0 Mouse: Applying InputClass "libinput pointer catchall" work properly through sleep/wake cycles would be ideal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun May 24 02:29:48 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed nvidia, 440.64, 5.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:096f] Subsystem: Dell GP108M [GeForce MX250] [1028:096f] InstallationDate: Installed on 2020-04-06 (48 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 5391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/vgubuntu--budgie-root ro mitigations=off transparent_hugepage=always SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 055C5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/25/2020:svnDellInc.:pnVostro5391:pvr:rvnDellInc.:rn055C5P:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5391 dmi.product.sku: 096F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1880365/+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 1838838] Re: username is not saved in openconnect connection dialog
Still present after upgrading 19.10 -> 20.04. -- 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/1838838 Title: username is not saved in openconnect connection dialog Status in GNOME Shell: New Status in NetworkManager: New Status in gnome-shell package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Bug description: Same issue as https://bugs.launchpad.net/ubuntu/+source/network- manager-openconnect/+bug/1609700 This was marked resolved. The report of its reappearance in Ubuntu 19.04 and 19.10 has not been acknowledged. This was working for me in 18.10, but a fresh install of 19.04 and 19.10 show that it is back. The password is saved when the option to save passwords is selected, but the username must be entered manually upon connection. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838838/+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 1883197] Re: Headset not working
What is the pulseaudio version on your machine? Please upgrade the pulesaudio to ubuntu3.3 version and redo the test. -- 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/1883197 Title: Headset not working Status in alsa-driver package in Ubuntu: New Bug description: When I plug the headset in and when the gnome "Select Audio Devices" popup and select "Headset" (rather than Headphones), the sound doesn't go through. But when I select "Headphones" it does. But I then need to manually select the Headset mic in the sound settings to have my headset working properly. This issue appear in 20.04. I didn't had this issue before I upgrade from 19.10 (and previous releases). 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal274918 F pulseaudio /dev/snd/pcmC0D0c: pascal274918 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Thu Jun 11 19:50:11 2020 InstallationDate: Installed on 2019-05-14 (394 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-18 (25 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0NFGCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0NFGCT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883197/+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 1882023] Re: Notifications are pointlessly truncated even on ultrawide monitors
*** This bug is a duplicate of bug 1871868 *** https://bugs.launchpad.net/bugs/1871868 Bug 1871868 is tracking the same kind of issue in the same code already. So let's use that for now. ** This bug has been marked a duplicate of bug 1871868 Shell dialog text is truncated and ellipsized -- 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/1882023 Title: Notifications are pointlessly truncated even on ultrawide monitors Status in gnome-shell package in Ubuntu: New Bug description: I tried to use ubuntu-bug -w to identify the component for this bug by clicking on a notification, but it failed with "xprop failed to determine process ID of the window". Sorry. The bug is that notifications of adding/removing icons to Favorites in the taskbar, are truncated for no good reason. I have a dual monitor setup ridiculous amounts of horizontal space, yet the notification is fixed size - which is fine, if it wrapped the text inside it. But it doesn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882023/+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 1878666] Re: Firefox is very slow (30 sec) to start
** Changed in: firefox (Ubuntu) Status: New => Fix Released -- 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/1878666 Title: Firefox is very slow (30 sec) to start Status in firefox package in Ubuntu: Fix Released Bug description: Firefox snap is very slow, when i start it ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 19:53:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-25 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 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/firefox/+bug/1878666/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
It's not that much "action". We can make this the main bug... ** This bug is no longer a duplicate of bug 1878194 [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+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 1882383] Re: bluetooth hsp/hfp didn't work anymore after updates. works fine before 2020 june 01
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 ** This bug is no longer a duplicate of bug 1878194 [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa ** This bug has been marked a duplicate of bug 1871794 [Bluetooth] No audio output/input in HSP/HFP mode -- 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/1882383 Title: bluetooth hsp/hfp didn't work anymore after updates. works fine before 2020 june 01 Status in pulseaudio package in Ubuntu: New Bug description: after updates no sound input/output in hsp/hfp profile, works fine in a2dp for playing hq music annoying when having a lot of remote meeting, got to switch to a crappy headset with wire juste for meetings please correct it, I miss using my bt headset all day :) https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878194 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: drub4n 1812 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 19:21:00 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0T8KGX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd05/11/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0T8KGX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1882383/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 ** This bug has been marked a duplicate of bug 1871794 [Bluetooth] No audio output/input in HSP/HFP mode -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1883197] [NEW] Headset not working
Public bug reported: When I plug the headset in and when the gnome "Select Audio Devices" popup and select "Headset" (rather than Headphones), the sound doesn't go through. But when I select "Headphones" it does. But I then need to manually select the Headset mic in the sound settings to have my headset working properly. This issue appear in 20.04. I didn't had this issue before I upgrade from 19.10 (and previous releases). 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal274918 F pulseaudio /dev/snd/pcmC0D0c: pascal274918 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Thu Jun 11 19:50:11 2020 InstallationDate: Installed on 2019-05-14 (394 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-18 (25 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0NFGCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0NFGCT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1883197 Title: Headset not working Status in alsa-driver package in Ubuntu: New Bug description: When I plug the headset in and when the gnome "Select Audio Devices" popup and select "Headset" (rather than Headphones), the sound doesn't go through. But when I select "Headphones" it does. But I then need to manually select the Headset mic in the sound settings to have my headset working properly. This issue appear in 20.04. I didn't had this issue before I upgrade from 19.10 (and previous releases). 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal274918 F pulseaudio /dev/snd/pcmC0D0c: pascal274918 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Thu Jun 11 19:50:11 2020 InstallationDate: Installed on 2019-05-14 (394 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to focal on 2020-05-18 (25 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0NFGCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0NFGCT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883197/+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 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
It's completely random. Works most days but fails once or twice a week. Even though I open a fresh Chrome every day. And yes reinstalling fonts-noto-color-emoji fixes the problem every time. ** Summary changed: - [snap] color emoji not rendered; many bw emoji rendered as boxes + color emoji not rendered; many bw emoji rendered as boxes -- 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/1858636 Title: color emoji not rendered; many bw emoji rendered as boxes Status in chromium-browser package in Ubuntu: Confirmed Bug description: I’ve recently noticed that Chromium no longer can display emoji. All I get are square boxes and some black & white symbols. E.g. https://getemoji.com renders like the screenshot I posted to https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb- to-snap-transition/11179/237. I'm like 95% sure that this is a recent problem, and that I didn't have it when I first upgraded to Ubuntu 19.10 and to the snapified Chromium. Note that I don't have fonts-symbola installed, and I do have fonts- not-color-emoji installed. I've also noticed a bunch of saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: Cannot load default config file saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: Cannot load default config file saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: Cannot load default config file saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: Cannot load default config file messages in journalctl when I first launch chromium. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: enabled dpms: On status: connected edid-base64: AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg== modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 DRM.card0-DP-4: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-DP-5: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA= modes: 1920x1080 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p5 ext4 284G 241G 29G 90% / tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm /dev/nvme0n1p5 ext4 284G 241G 29G 90% / DistroRelease: Ubuntu 19.10 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (208 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20Q0CTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 (29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916}) Snap.ChromiumVersion: Chromium 79.0.3945.79 snap Tags: eoan wayland-session snap Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET73W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q0CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10
[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority
Upstream just merged the patch, and I changed the description on the commits for ubuntu-focal and ubuntu branch, pushed them to ubuntu pulseaudio repo. ** Description changed: 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. + 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. + Low, just do a small change to store the ucm devices by their priority. and upstream just merged this patch. -- 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. and upstream just merged this patch. 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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
@Hui Sure, will do. -- 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/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: Triaged Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-wip 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
@Kai-Chuan, To be safe, could you please apply the change to a LENOVO machine and test if it works or not. Dell DMIC machines depends on the soundcard's name to work while Lenovo DMIC machines depends on soundcard's long name or BIOS Rev string to work. I remember there is a LENOVO X1C7 in Taipei office, and a couple of weeks ago this machine was kept by Kaiheng. If your change could work on LENOVO X1C7, it means all LENOVO DMIC machines could work. thx. -- 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/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: Triaged Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-wip 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1883192] [NEW] Video mode is missing
Public bug reported: Video mode 1600x1200 is not present. In the file Xorglog.txt, we can see that it's extracted from the EDID but not present in the list of "modeline". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CompositorRunning: None CurrentDesktop: XFCE Date: Fri Jun 12 02:17:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation NV41M [GeForce Go 6800] [10de:00c8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions NV41M [GeForce Go 6800] [1734:107c] InstallationDate: Installed on 2020-04-17 (55 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: FUJITSU SIEMENS Amilo M3438 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=f910d7c1-f499-455a-ade2-472c22149dcd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10C dmi.board.name: P71EN0 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10C:bd10/05/2005:svnFUJITSUSIEMENS:pnAmiloM3438Series:pvr:rvn:rnP71EN0:rvr:cvnFUJITSUSIEMENS:ct10:cvr: dmi.product.name: Amilo M3438 Series dmi.sys.vendor: FUJITSU SIEMENS 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 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 resolution 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/1883192 Title: Video mode is missing Status in xorg package in Ubuntu: New Bug description: Video mode 1600x1200 is not present. In the file Xorglog.txt, we can see that it's extracted from the EDID but not present in the list of "modeline". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CompositorRunning: None CurrentDesktop: XFCE Date: Fri Jun 12 02:17:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation NV41M [GeForce Go 6800] [10de:00c8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions NV41M [GeForce Go 6800] [1734:107c] InstallationDate: Installed on 2020-04-17 (55 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: FUJITSU SIEMENS Amilo M3438 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=f910d7c1-f499-455a-ade2-472c22149dcd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10C dmi.board.name: P71EN0 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10C:bd10/05/2005:svnFUJITSUSIEMENS:pnAmiloM3438Series:pvr:rvn:rnP71EN0:rvr:cvnFUJITSUSIEMENS:ct10:cvr: dmi.product.name: Amilo M3438 Series dmi.sys.vendor: FUJITSU SIEMENS 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 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 968213] Re: Too many icons in Gnome Shell Activities Overview require ellipses
So another LTS got released with this issue... :-( If upstream Gnome is dragging its feet to solve this, would I be asking too much if I suggested Ubuntu to bundle the "Applications Overview Tooltip" in the distro? At least users won't have to mess with browser extensions. That looks like a pretty obvious solution to me. -- 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/968213 Title: Too many icons in Gnome Shell Activities Overview require ellipses Status in GNOME Shell: Confirmed Status in One Hundred Papercuts: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: Several apps in the default Ubuntu 17.04 or 17.10 install have Ellipses when shown in GNOME Shell's Activities Overview. This was made worse by switching GNOME Shell to use the Ubuntu font because the Ubuntu font is a bit wider than GNOME's default Cantarell font so some apps that didn't require ellipses in 17.04 require them now in 17.10 Alpha. The upstream GNOME bug proposes that apps names be allowed to use 2 lines. This is similar to what the Settings app (gnome-control-center) does. This is also really bad for languages that use more characters than English. Original Bug Title -- Gnome Shell Activities Overview should show full names on mouse hover Original Bug Report --- The title says it all --- especially when choosing recent documents, if they start with the same say 12 or 14 letters, it's impossible to differentiate them (see attached screenshot). When mouse is hovering an icon, the full name of the application/document should be shown. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/968213/+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
So, something that is surprising me is that nobody has asked for any type of report. I would love to share any diagnostic information I have, just give me a terminal command or path to a text file and I will share it. -- 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 1869981] Re: Printer notification every day at midnight
This is still occuring in 20.04 along with the notification at bootup. It has not been fixed. -- 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/1869981 Title: Printer notification every day at midnight Status in cups package in Ubuntu: Triaged Bug description: Every day, all my 20.04 machines get a notification that the printer in my house has been detected. The printer works fine and is already added. So not sure why I need to be told repeatedly that I have a printer on the network? (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 00:00:31 2020 InstallationDate: Installed on 2020-03-01 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/ MachineType: LENOVO 20BV001BUK Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1869981/+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 1883116] Re: SRU the current 3.36.3 stable update
** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Low ** Changed in: evolution-data-server (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1883116 Title: SRU the current 3.36.3 stable update Status in evolution-data-server package in Ubuntu: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1883116/+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 1878666] Re: Firefox is very slow (30 sec) to start
Hi, with Firefox 77.0.1 (64 bit), for Ubuntu Canonical 1.0, now 6 sec less to start. Thank you so much. Tommaso Il giorno gio 11 giu 2020 alle ore 15:31 Olivier Tilloy < 1878...@bugs.launchpad.net> ha scritto: > firefox was updated to 77.0.1 since the bug was initially reported. Does > the problem persist? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1878666 > > Title: > Firefox is very slow (30 sec) to start > > Status in firefox package in Ubuntu: > New > > Bug description: > Firefox snap is very slow, when i start it > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-shell 3.36.1-5ubuntu2 > ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 > Uname: Linux 5.4.0-29-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Thu May 14 19:53:08 2020 > DisplayManager: gdm3 > InstallationDate: Installed on 2020-04-25 (18 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=it_IT.UTF-8 >SHELL=/bin/bash > RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 > 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/firefox/+bug/1878666/+subscriptions > -- Tommaso Trombetta -- 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/1878666 Title: Firefox is very slow (30 sec) to start Status in firefox package in Ubuntu: New Bug description: Firefox snap is very slow, when i start it ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 19:53:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-25 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 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/firefox/+bug/1878666/+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 1883177] [NEW] Double menu-bar in LibreOffice 6.4.3.2 only with installed addon languagetool
Public bug reported: Hello, I had the problem already with 18.04. Now I have reinstalled Ubuntu 20.04 64bit, automatically with LibreOffice 6.4.3.2. If I open at first within LO a saved or a recently used document, another menu-bar appears. (This doesn't happen if i open the document from Nautilus.) Test: First delete the whole user profile under .config/libreoffice. After that: If I use LO without Languagetool, the problem does not appear. After installing languagetool 4.8 as an addon, when opening a file for the first time, a double menu line is immediately visible. Further Oberservation / workaround: If I open the 1st file from Nautilus and then open the next file either in LO with 'ctrl+o' or with File > last used ... there are no further menu lines. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: languagetool libreoffice ** Attachment added: "menu.png" https://bugs.launchpad.net/bugs/1883177/+attachment/5383100/+files/menu.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1883177 Title: Double menu-bar in LibreOffice 6.4.3.2 only with installed addon languagetool Status in libreoffice package in Ubuntu: New Bug description: Hello, I had the problem already with 18.04. Now I have reinstalled Ubuntu 20.04 64bit, automatically with LibreOffice 6.4.3.2. If I open at first within LO a saved or a recently used document, another menu-bar appears. (This doesn't happen if i open the document from Nautilus.) Test: First delete the whole user profile under .config/libreoffice. After that: If I use LO without Languagetool, the problem does not appear. After installing languagetool 4.8 as an addon, when opening a file for the first time, a double menu line is immediately visible. Further Oberservation / workaround: If I open the 1st file from Nautilus and then open the next file either in LO with 'ctrl+o' or with File > last used ... there are no further menu lines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1883177/+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 1883174] [NEW] Some desktop icons disappear
Public bug reported: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2020-06-12 01-12-03.png" https://bugs.launchpad.net/bugs/1883174/+attachment/5383099/+files/Screenshot%20from%202020-06-12%2001-12-03.png -- 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/1883174 Title: Some desktop icons disappear Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: OS: Ubuntu 20.04 GNOME: 3.36.2 Extension: 3.36.2 Sometimes, some icons in my Desktop folder just don't appear on the desktop. The missing icons aren't invisible, it's like they're not in the folder. Clicking on the empty space where they should be does nothing. Mousing over the empty space does nothing. See attached screenshot. As you can see, there are many missing. Not consistently reproducible, but frequent. This isn't great info, I know. Let me know what else I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1883174/+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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
This bug was fixed in the package wpa - 2:2.9-1ubuntu8 --- wpa (2:2.9-1ubuntu8) groovy; urgency=medium * debian/patches/Check-for-FT-support-when-selecting-FT-suites.patch: - Backport upstream fix "Check for FT support when selecting FT suites" to fix drivers without FT support (lp: #1881549). -- Kai-Heng Feng Wed, 10 Jun 2020 11:48:39 +0800 ** Changed in: wpa (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Invalid Status in wpa package in Ubuntu: Fix Released Status in linux source package in Focal: Invalid Status in wpa source package in Focal: Confirmed Status in linux source package in Groovy: Invalid Status in wpa source package in Groovy: Fix Released Bug description: [Impact] * A driver supports FT (IEEE 802.11r-2008 or fast BSS transition (FT), also called fast roaming) if it either supports SME or the NL80211_CMD_UPDATE_FT_IES command. When selecting AKM suites, wpa_supplicant currently doesn't take into account whether or not either of those conditions are met. This can cause association failures, e.g., when an AP supports both WPA-EAP and FT-EAP but the driver doesn't support FT (wpa_supplicant will decide to do FT-EAP since it is unaware the driver doesn't support it). * This is known to affect users at least users with popular chip-sets, such as BCM20703A1 or BCM4350 (notably present in the popular XPS 13/15 laptops). * The upload fixes the bug by allowing an FT suite to be selected only when the driver also supports FT. [Test Case] * requires affected hardware and wpa_supplicant built with CONFIG_IEEE80211R and connecting to an AP supporting WPA-EAP and FT-EAP [Regression Potential] * a driver not advertising correctly its support for SME or the NL80211_CMD_UPDATE_FT_IES command via the drv_flags would be prevented from using FT but would still be able to connect to APs [Other Info] * Upstream fix: https://w1.fi/cgit/hostap/commit/?id=23dc196fde951b3d508f367a603cddffbd053490 * Initial report: https://bugs.archlinux.org/task/63397 --- Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1861280] Re: Desktop icons reshuffle themselves
Affects me on Ubuntu 20.04, GNOME 3.36.2 + Extensions 3.36.2 -- 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/1861280 Title: Desktop icons reshuffle themselves Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: It may be a bad habit, but for years I have saved temporary files (stuff I don't intend to keep long & some work in progress) to my desktop, where I won't forget them & they are immediately available. For years there was no problem - icons on the desktop stayed where they were. Since 19.10 things have gone crazy (might have started with 19.04 but I can't check that now). Nearly every time a new item is added or removed, some or all of the other items get reshuffled on the desk! I raised this issue on Ubuntu Forum, with details & screenshots (PLEASE LOOK) here: https://ubuntuforums.org/showthread.php?t=2435768 I have run comparison tests, using SHA-verified Live USB stick versions of Ubuntu 18.04.3 & 19.10, which I suppose anybody else can duplicate. My test was to successively "Save-as to desktop" 32 tiny LibO files called 01, 02, 03 etc in that order. With 18.04.3, each item was positioned top-to-bottom in a column at left, then in the next columns to the right after each column was full. Once positioned, no icon moved. With 19.10, icons were positioned clustered top-left but new columns were started before previous columns were full. Nearly every addition caused previous icons to be reshuffled. Frequently the number of columns DIMINISHED when a new icon was added. With 19.10, removing icons causes other items to reshuffle. With 18.04.3, removing icons leaves a gap, which is filled by the next item added. I think the behaviour of 18.04.3 is perfect & the behaviour of 19.10 is an unacceptable regression. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 29 14:03:30 2020 InstallationDate: Installed on 2014-10-23 (1923 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-11-04T18:03:11.954726 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1861280/+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: Statusbar preferences options aren't stored
Thanks. I've opened https://gitlab.gnome.org/GNOME/gedit/-/issues/330. I am actually a bit confused by your answer, could you please help me understand a few things? 1. How is the statusbar different from the preferences dialog? Why isn't it supposed to edit gedit preferences? 2. I'm relatively new to the Linux world, I don't quite understand why you refer to Gnome as "upstream". Is it because Gnome is used by Ubuntu, so you build on top of what Gnome offers? And the statusbar problem is in Gnome's remit? Although to be honest I'm still confused as to why, from a user's perspective they are the same application, just different ways to trigger the same option. ** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #330 https://gitlab.gnome.org/GNOME/gedit/-/issues/330 -- 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: Statusbar preferences options aren't stored Status in gedit package in Ubuntu: Confirmed 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 1881040] Re: [snap] chromedriver does not download where configured
Thanks for the replies. The main issue for me was that chromedriver - by design as I understand it - does not have Chromium use the normal ~/Downloads folder, but one that has to be configured when initialising chromedriver. I cannot easily share the code, but here is an extract (code like this is widely shared on the web): self.driver.command_executor._commands["send_command"] = ( "POST", '/session/$sessionId/chromium/send_command' ) self.driver.execute("send_command", { 'cmd': 'Page.setDownloadBehavior', 'params': {'behavior': 'allow', 'downloadPath': /a/place/}} ) The issue is that the snap setup ignores this location. So tests which are expecting file to end up under "/a/place" don't find them. Now, while investigating this, I may have mistakenly thought that the lack of the ~/snap/.../Downloads was the problem. Though with hindsight, it might have been because the directory did not exist rather than, as you say, the directory not being writeable if created. At any rate I suspect that, as above, chromedriver will set up Chromium not to use this folder in any event. In other words, this is likely a red-herring. -- 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/1881040 Title: [snap] chromedriver does not download where configured Status in chromium-browser package in Ubuntu: Incomplete Bug description: I've recently been forced to upgrade to the SNAP based chromium setup. After being required to work through reconfiguring my $HOME, learn of the need to set up $XAUTHORITY I just now discovered that none of my Selenium based download tests work because the SNAP setup insists on downloading to: /home/xxx/snap/chromium/1165/Downloads rather than where the chromederiver download settings have been configured. Is there a way to override this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1881040/+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
** Attachment added: "settings.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+attachment/5383087/+files/settings.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/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell package in Ubuntu: Incomplete 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/+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 1882353] Re: Ubuntu Dock and Top bar accessible from lockscreen
(Thanks to everyone who is taking the time out of their day to look into this.) I think I should note that I can't replicate this issue reliably. It happened "at random" and it didn't happen again since I filed this report. It's just that it wasn't the first time it happened and I saw others have similar issues. That is why I reported it. Again I want to preface that the extensions shown in the list are the once which came pre-installed with Ubuntu 18.04 (iirc) and I never touched them. (I have some indicator apps but I assume you don't mean them.) I also don't understand why I should disable stock Ubuntu extensions that provide basic functionality like the dock. Would you consider disabling the dock a solution or do you simply try to pin down the culprit? With that said I can explain the seemingly contractionary pictures. The gnome Tweaks app shows a wrong state. The extensions app shows the correct state. Screenshot attached. This must be a bug in gnome Tweaks. The gsettings file shows something interesting: According to the file I have two extensions active that I can't remember ever installing and that do not show up anywhere: org.gnome.shell enabled-extensions ['update-extensi...@franglais125.gmail.com', 'move_cl...@rmy.pobox.com'] File attached. Could it be that there are extensions active that I or someone living with me installed in the past but don't show up in the extensions settings? If yes how do I remove them for further bug testing? ** Attachment added: "Screenshot from 2020-06-11.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882353/+attachment/5383086/+files/Screenshot%20from%202020-06-11.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882353 Title: Ubuntu Dock and Top bar accessible from lockscreen Status in gnome-shell package in Ubuntu: Incomplete 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/+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 1883160] [NEW] [XPS 15 7590, Realtek ALC3266, Black Headphone Out, Left] Playback problem
Public bug reported: My headphones stopped playing sound a few days ago, except for the occasional 'pop' when I select them as output. The laptop speakers still work when they're select as output. I've tried unplugging other devices, rebooting, plugging my headphone jack out and back in. When I plug my headphone into a different laptop running 18.04 they work fine. What's odd to me is that Ubuntu seems eager to select my Yeti Microphone as the output device. The bars under 'Output' and 'Input' both light up when I play sound or snap my fingers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathijs2185 F pulseaudio /dev/snd/pcmC0D0c: mathijs2185 F...m pulseaudio /dev/snd/pcmC0D0p: mathijs2185 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 10:46:20 2020 InstallationDate: Installed on 2020-04-27 (45 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [XPS 15 7590, Realtek ALC3266, Black Headphone Out, Left] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0T8KGX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd05/11/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0T8KGX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1883160 Title: [XPS 15 7590, Realtek ALC3266, Black Headphone Out, Left] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: My headphones stopped playing sound a few days ago, except for the occasional 'pop' when I select them as output. The laptop speakers still work when they're select as output. I've tried unplugging other devices, rebooting, plugging my headphone jack out and back in. When I plug my headphone into a different laptop running 18.04 they work fine. What's odd to me is that Ubuntu seems eager to select my Yeti Microphone as the output device. The bars under 'Output' and 'Input' both light up when I play sound or snap my fingers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathijs2185 F pulseaudio /dev/snd/pcmC0D0c: mathijs2185 F...m pulseaudio /dev/snd/pcmC0D0p: mathijs2185 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 10:46:20 2020 InstallationDate: Installed on 2020-04-27 (45 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [XPS 15 7590, Realtek ALC3266, Black Headphone Out, Left] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0T8KGX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd05/11/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0T8KGX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
Re: [Desktop-packages] [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
it need the no-sandbox to work. On 6/11/20 10:57 AM, Olivier Tilloy wrote: > Thanks for the upstream report Mike. I see it has been marked as a > duplicate of > https://bugs.chromium.org/p/chromium/issues/detail?id=1035803, and > comment #19 there suggests the following: > > tldr; manually turn off shared memory by using the "--no-xshm" flag, > setting the environment variable "QT_X11_NO_MITSHM=1" or > "J2D_USE_MITSHM=0". > > Does this address your crash? > -- 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/1877173 Title: Chromium 81.0.4044.122 crashes on remote ssh connection Status in chromium-browser package in Ubuntu: New Bug description: Chromium crash on a ssh x forwarding connection It crashes on both 18.04 and 16.04 with the same message. The X forwarding is working for other programs just fine. It was working until last update. Here is the message from the console on the crash [22765:22781:0506/144206.193243:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye. Trace/breakpoint trap (core dumped) Steps to repeat: ssh ltcd-prod chromum-browser ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 81.0.4044.122-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: btrfs xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid veth iptable_filter bpfilter bridge stp llc binfmt_misc intel_powerclamp coretemp kvm_intel kvm irqbypass zfs zunicode zavl icp ipmi_ssif gpio_ich crct10dif_pclmul crc32_pclmul ghash_clmulni_intel zcommon znvpair spl zlua aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate ast drm_vram_helper ttm drm_kms_helper lpc_ich drm joydev input_leds fb_sys_fops syscopyarea sysfillrect sysimgblt ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel lp parport nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 hid_generic igb uas usbhid ahci i2c_algo_bit hid libahci usb_storage dca i2c_ismt ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: modes: 1024x768 800x600 800x600 640x480 Date: Wed May 6 14:37:46 2020 Desktop-Session: 'None' 'None' 'None' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: Load-Avg-1min: 0.55 Load-Processes-Running-Percent: 0.1% Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: Supermicro A1SAi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=UUID=c75e8c2a-b85d-444e-b278-16fd90c327e7 ro usb_storage.quirks=0bc2:331a:u,0bc2:ab31:u,0bc2:ab34:u SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1a dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A1SRi dmi.board.vendor: Supermicro dmi.board.version: 123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 18 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1a:bd08/27/2015:svnSupermicro:pnA1SAi:pvr123456789:rvnSupermicro:rnA1SRi:rvr123456789:cvnToBeFilledByO.E.M.:ct18:cvrToBeFilledByO.E.M.: dmi.product.family: SMC X10 dmi.product.name: A1SAi dmi.product.sku: 081315D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877173/+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 1883155] Re: Vi advertises TLS even when require-encryption is false
** Package changed: ubuntu => vino (Ubuntu) ** Tags added: focal ** Summary changed: - Vi advertises TLS even when require-encryption is false + Vino advertises TLS even when require-encryption is false -- 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/1883155 Title: Vino advertises TLS even when require-encryption is false Status in vino package in Ubuntu: New Bug description: I have an old Xubuntu system which I administer remotely from a Windows machine using UltraVNC. This doesn't support encryption, but since it's on a local net this is acceptable, and it has worked fine for years. I have just installed Xubuntu 20.04 on a new machine, and have installed Vino from the repository and configured it using gsettings to the same values as on my old system. The settings are as follows: org.gnome.Vino prompt-enabled false org.gnome.Vino require-encryption false org.gnome.Vino use-alternative-port false org.gnome.Vino disable-background false org.gnome.Vino disable-xdamage false org.gnome.Vino alternative-port uint16 5900 org.gnome.Vino icon-visibility 'client' org.gnome.Vino authentication-methods ['vnc'] org.gnome.Vino network-interface '' org.gnome.Vino notify-on-connect true org.gnome.Vino mailto '' org.gnome.Vino lock-screen-on-disconnect false org.gnome.Vino use-upnp false org.gnome.Vino vnc-password 'xx==' org.gnome.Vino view-only false When I start the server, this is what I see: 10/06/2020 20:25:40 WARNING: Width (1366) is not a multiple of 4. VncViewer has problems with that. 10/06/2020 20:25:40 Autoprobing TCP port in (all) network interface 10/06/2020 20:25:40 Listening IPv6://[::]:5900 10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900 10/06/2020 20:25:40 Autoprobing selected port 5900 10/06/2020 20:25:40 Advertising security type: 'TLS' (18) 10/06/2020 20:25:40 Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 10/06/2020 20:25:40 Listening IPv6://[::]:5900 10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900 10/06/2020 20:25:40 Clearing securityTypes 10/06/2020 20:25:40 Advertising security type: 'TLS' (18) 10/06/2020 20:25:40 Clearing securityTypes 10/06/2020 20:25:40 Advertising security type: 'TLS' (18) 10/06/2020 20:25:40 Advertising authentication type: 'No Authentication' (1) 10/06/2020 20:25:40 Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 10/06/2020 20:25:40 Listening IPv6://[::]:5900 10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900 10/06/2020 20:25:40 Clearing securityTypes 10/06/2020 20:25:40 Clearing authTypes 10/06/2020 20:25:40 Advertising security type: 'TLS' (18) 10/06/2020 20:25:40 Advertising authentication type: 'VNC Authentication' (2) 10/06/2020 20:28:21 [IPv4] Got connection from client xxx 10/06/2020 20:28:21 other clients: 10/06/2020 20:28:21 WARNING: New width (1366) is not a multiple of 4. 10/06/2020 20:28:21 Client Protocol Version 3.4 10/06/2020 20:28:21 Ignoring minor version mismatch 10/06/2020 20:28:21 rfbClientConnFailed("No security type suitable for RFB 3.3 supported") 10/06/2020 20:28:21 Client xxx gone Note that it says "Advertising security type: 'TLS' (18)" even though I have set "org.gnome.Vino require-encryption" to false. And as a result, I can't connect from my Windows box. Can anyone tell me what to do to fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1883155/+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 1868085] Re: Bug related to the new kernel version 5.3.0-42-generic
Thanks Loic, this worked for me on xubuntu 19.10 running kernel 5.3.0.59.53 -- 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/1868085 Title: Bug related to the new kernel version 5.3.0-42-generic Status in alsa-driver package in Ubuntu: New Bug description: Hi all, After an update of Ubuntu kernel (version 5.3.0-42-generic) I can't have sound any more. No soundcards are detected any I have a "dummy output" in the sound pannel in settings. Furthermore I can't resume from sleep anymore. Output of ALSA Information script: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Wed Mar 18 14:46:19 UTC 2020 !!Linux Distribution !!-- Ubuntu 18.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: HP Product Name: HP ZBook 15u G6 Product Version: Firmware Version: R70 Ver. 01.03.04 Board Vendor: HP Board Name:8549 !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/HPIC000C:00/status 15 /sys/bus/acpi/devices/HPQ6001:00/status15 /sys/bus/acpi/devices/IFX0785:00/status15 /sys/bus/acpi/devices/INT3400:00/status15 /sys/bus/acpi/devices/INT3403:00/status15 /sys/bus/acpi/devices/INT3403:01/status15 /sys/bus/acpi/devices/INT340E:00/status15 /sys/bus/acpi/devices/INT34BB:00/status15 /sys/bus/acpi/devices/INT3F0D:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 15 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0B00:00/status15 /sys/bus/acpi/devices/PNP0C02:00/status3 /sys/bus/acpi/devices/PNP0C02:01/status3 /sys/bus/acpi/devices/PNP0C02:05/status3 /sys/bus/acpi/devices/PNP0C09:00/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PRP1:00/status 11 /sys/bus/acpi/devices/SYNA3092:00/status 15 /sys/bus/acpi/devices/USBC000:00/status15 /sys/bus/acpi/devices/device:04/status 15 /sys/bus/acpi/devices/device:27/status 15 /sys/bus/acpi/devices/device:28/status 15 /sys/bus/acpi/devices/device:4c/status 15 !!Kernel Information !!-- Kernel release:5.3.0-42-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-42-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- --- no soundcards --- !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:9dc8] (rev 11) Subsystem: Hewlett-Packard Company Device [103c:8549] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!ALSA Device nodes !!- crw-rw 1 root audio 116, 1 Mar 18 14:45 /dev/snd/seq crw-rw 1 root audio 116, 33 Mar 18 14:44 /dev/snd/timer !!Aplay/Arecord output !! APLAY aplay: device_list:270: no soundcards found... ARECORD arecord:
[Desktop-packages] [Bug 1883155] [NEW] Vi advertises TLS even when require-encryption is false
You have been subscribed to a public bug: I have an old Xubuntu system which I administer remotely from a Windows machine using UltraVNC. This doesn't support encryption, but since it's on a local net this is acceptable, and it has worked fine for years. I have just installed Xubuntu 20.04 on a new machine, and have installed Vino from the repository and configured it using gsettings to the same values as on my old system. The settings are as follows: org.gnome.Vino prompt-enabled false org.gnome.Vino require-encryption false org.gnome.Vino use-alternative-port false org.gnome.Vino disable-background false org.gnome.Vino disable-xdamage false org.gnome.Vino alternative-port uint16 5900 org.gnome.Vino icon-visibility 'client' org.gnome.Vino authentication-methods ['vnc'] org.gnome.Vino network-interface '' org.gnome.Vino notify-on-connect true org.gnome.Vino mailto '' org.gnome.Vino lock-screen-on-disconnect false org.gnome.Vino use-upnp false org.gnome.Vino vnc-password 'xx==' org.gnome.Vino view-only false When I start the server, this is what I see: 10/06/2020 20:25:40 WARNING: Width (1366) is not a multiple of 4. VncViewer has problems with that. 10/06/2020 20:25:40 Autoprobing TCP port in (all) network interface 10/06/2020 20:25:40 Listening IPv6://[::]:5900 10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900 10/06/2020 20:25:40 Autoprobing selected port 5900 10/06/2020 20:25:40 Advertising security type: 'TLS' (18) 10/06/2020 20:25:40 Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 10/06/2020 20:25:40 Listening IPv6://[::]:5900 10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900 10/06/2020 20:25:40 Clearing securityTypes 10/06/2020 20:25:40 Advertising security type: 'TLS' (18) 10/06/2020 20:25:40 Clearing securityTypes 10/06/2020 20:25:40 Advertising security type: 'TLS' (18) 10/06/2020 20:25:40 Advertising authentication type: 'No Authentication' (1) 10/06/2020 20:25:40 Re-binding socket to listen for VNC connections on TCP port 5900 in (all) interface 10/06/2020 20:25:40 Listening IPv6://[::]:5900 10/06/2020 20:25:40 Listening IPv4://0.0.0.0:5900 10/06/2020 20:25:40 Clearing securityTypes 10/06/2020 20:25:40 Clearing authTypes 10/06/2020 20:25:40 Advertising security type: 'TLS' (18) 10/06/2020 20:25:40 Advertising authentication type: 'VNC Authentication' (2) 10/06/2020 20:28:21 [IPv4] Got connection from client xxx 10/06/2020 20:28:21 other clients: 10/06/2020 20:28:21 WARNING: New width (1366) is not a multiple of 4. 10/06/2020 20:28:21 Client Protocol Version 3.4 10/06/2020 20:28:21 Ignoring minor version mismatch 10/06/2020 20:28:21 rfbClientConnFailed("No security type suitable for RFB 3.3 supported") 10/06/2020 20:28:21 Client xxx gone Note that it says "Advertising security type: 'TLS' (18)" even though I have set "org.gnome.Vino require-encryption" to false. And as a result, I can't connect from my Windows box. Can anyone tell me what to do to fix this? ** Affects: vino (Ubuntu) Importance: Undecided Status: New -- Vi advertises TLS even when require-encryption is false https://bugs.launchpad.net/bugs/1883155 You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Very annoying bug as when selecting on-demand some things don't work (don't ask, my kid plays Minecraft on this laptop) which fails in on- demand mode. Selecting Nvidia as the main GPU I lose fractional scaling... -- 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 1883154] [NEW] Nautilus should focus newly created file's name
Public bug reported: - What is expected: After you create a file from context menu (right-click -> New Document -> New XXX file), its name should be focused and ready to be edited - so that it's possible to rename it right away. - What is actually happening: After you create a file, you have to manually invoke its context menu and select "Rename". - Why? This feature (one click create-and-rename folders and files) exists in most OS-es (including older Ubuntu versions) and file managers (including console ones). This is basic functionality that you would expect from a file manager. Description:Ubuntu 20.04 LTS Release:20.04 nautilus: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Description changed: - What is expected: After you create a file from context menu (right-click -> New Document -> New XXX file), its name should be focused and ready to be edited - so that it's possible to rename it right away. - - What is actually happening: After you create a file, you have to manually invoke its context menu and select "Rename". - - Why? This feature (one click create-and-rename folders and files) exists in most OS-es (including older Ubuntu versions) and file managers (including console ones). This is basic functionality that you would expect from a file manager. + Description: Ubuntu 20.04 LTS + Release: 20.04 + nautilus: - Installed: 1:3.36.2-0ubuntu1 - Candidate: 1:3.36.2-0ubuntu1 + Installed: 1:3.36.2-0ubuntu1 + Candidate: 1:3.36.2-0ubuntu1 -- 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/1883154 Title: Nautilus should focus newly created file's name Status in nautilus package in Ubuntu: New Bug description: - What is expected: After you create a file from context menu (right-click -> New Document -> New XXX file), its name should be focused and ready to be edited - so that it's possible to rename it right away. - What is actually happening: After you create a file, you have to manually invoke its context menu and select "Rename". - Why? This feature (one click create-and-rename folders and files) exists in most OS-es (including older Ubuntu versions) and file managers (including console ones). This is basic functionality that you would expect from a file manager. Description: Ubuntu 20.04 LTS Release: 20.04 nautilus: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1883154/+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 am affected by this bug as well. My setup: - Ubuntu 20.04 fresh install - Nvidia drivers 435 & 440 (multiple re-installs) - Nvidia GeForce GTX 1050 Ti - Philips 328P6JV 4K 32" monitor Strange enough, fractional scaling works fine when I run Ubuntu 20.04 as a virtual machine (VMware) on the same Windows 10 PC. -- 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 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_chang
Oh no my favourite ext must go off :( Thanks for tip! -- 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/184 Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking the screen] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: In Progress Bug description: [ Impact ] GNOME shell crashes on extensions loading / updates [ Test case ] - No clear test case, normally may happen during screen locking/unlocking - But crashes should be monitored at https://errors.ubuntu.com/problem/4127e7e714fd28c090da0220de2ff06e71274eda [ Regression potential ] Stylesheet memory could be leaked --- Seems to be reproducible Suspend the computer Start the computer from suspend Start chrome gmail. Has happened two times ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat May 9 20:00:47 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-04-16 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415.2) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7fe1b40c4252 <_st_theme_node_ensure_background+226>: mov(%rax),%r12 PC (0x7fe1b40c4252) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%r12" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: _st_theme_node_ensure_background () from /usr/lib/gnome-shell/libst-1.0.so st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so ?? () from /usr/lib/gnome-shell/libst-1.0.so Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/184/+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 1883000] Re: screengrab window remain open, without icon in launcher, hence impossible to find
Hopefully gnome-screenshot is the right package -- 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/1883000 Title: screengrab window remain open, without icon in launcher, hence impossible to find Status in gnome-screenshot package in Ubuntu: New Bug description: Sometimes, after taking a screenshot, when you click to close the gnome-screenshot window, it fails to close and remains open, but in the background, behind everything else. What is much worse, is that the icon in launcher does disappear. So, you have a "ghost" window left open, behind every other window, that you have NO WAY TO REACH except by minimizing or closing EVERY SINGLE other window one by one, until the only one that remains is screengrab. This makes bug 1526082 even more annoying, as sometimes, even after you (think you) have closed all screengrab's windows, there is still a rectanguar area of the screen that is slightly dimmed. The first time it happened to me, I thought bug 1526082 had got worse and that the screengrabbed area would now remain dimmed forever even after closing screengrab. But then I found out the window was still there. This is fucking pathetic. Please drop Gnome for good and pick an alternative that is decently maintained, by non-idiots. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: screengrab (not installed) 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: Wed Jun 10 19:54:46 2020 InstallationDate: Installed on 2013-10-11 (2434 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: screengrab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1883000/+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 1883000] Re: screengrab window remain open, without icon in launcher, hence impossible to find
I guess I marked the wrong package, as Ubuntu doesn't provide any easy mechanism for the end user to figure out which fucking package a given application belongs to, so one has to guess. I am using standard Ubuntu 16.04, not Lubuntu, and this is about the default screenshot grabber that appears as "Screenshot" and that is launched by pressing the PrintScreen key. I think the executable is /usr/bin/gnome-screenshot ** Package changed: screengrab (Ubuntu) => gnome-screenshot (Ubuntu) ** Changed in: gnome-screenshot (Ubuntu) Status: Incomplete => New -- 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/1883000 Title: screengrab window remain open, without icon in launcher, hence impossible to find Status in gnome-screenshot package in Ubuntu: New Bug description: Sometimes, after taking a screenshot, when you click to close the gnome-screenshot window, it fails to close and remains open, but in the background, behind everything else. What is much worse, is that the icon in launcher does disappear. So, you have a "ghost" window left open, behind every other window, that you have NO WAY TO REACH except by minimizing or closing EVERY SINGLE other window one by one, until the only one that remains is screengrab. This makes bug 1526082 even more annoying, as sometimes, even after you (think you) have closed all screengrab's windows, there is still a rectanguar area of the screen that is slightly dimmed. The first time it happened to me, I thought bug 1526082 had got worse and that the screengrabbed area would now remain dimmed forever even after closing screengrab. But then I found out the window was still there. This is fucking pathetic. Please drop Gnome for good and pick an alternative that is decently maintained, by non-idiots. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: screengrab (not installed) 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: Wed Jun 10 19:54:46 2020 InstallationDate: Installed on 2013-10-11 (2434 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: screengrab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1883000/+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 1883000] [NEW] screengrab window remain open, without icon in launcher, hence impossible to find
You have been subscribed to a public bug: Sometimes, after taking a screenshot, when you click to close the gnome- screenshot window, it fails to close and remains open, but in the background, behind everything else. What is much worse, is that the icon in launcher does disappear. So, you have a "ghost" window left open, behind every other window, that you have NO WAY TO REACH except by minimizing or closing EVERY SINGLE other window one by one, until the only one that remains is screengrab. This makes bug 1526082 even more annoying, as sometimes, even after you (think you) have closed all screengrab's windows, there is still a rectanguar area of the screen that is slightly dimmed. The first time it happened to me, I thought bug 1526082 had got worse and that the screengrabbed area would now remain dimmed forever even after closing screengrab. But then I found out the window was still there. This is fucking pathetic. Please drop Gnome for good and pick an alternative that is decently maintained, by non-idiots. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: screengrab (not installed) 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: Wed Jun 10 19:54:46 2020 InstallationDate: Installed on 2013-10-11 (2434 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: screengrab UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug xenial -- screengrab window remain open, without icon in launcher, hence impossible to find https://bugs.launchpad.net/bugs/1883000 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working
I have the same issue with 20.04 and Intel AX200. It works quite well but I'm unable to authorize with some 2.4GHz hotspots. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1859308 Title: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-drivers-common source package in Groovy: Confirmed Bug description: On Ubuntu 20.04 (development branch), as of today, Additional Drivers (software-properties-gtk 0.98.6) reports that the device "Intel Corporation: Wireless-AC 9260" is not working, and suggests using a manually installed driver (cf. screenshot). However the device is working correctly: * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show that its driver iwlwifi is in use * ls /lib/firmware/*9260* show that the appropriate firmware files are present And I am indeed writing this bug report connected to an ac (5 GHz) wifi network, where I can verify a ~130-160 Mbps download speed, so software-properties-gtk shouldn't report the device as not working and suggest manually installing a driver. Not sure why it says so? EDIT: bug confirmed as affecting the following Intel wireless adapter cards, and assumedly more to come: Intel Wi-Fi 6 AX200 Intel Dual Band Wireless-AC 3165 Intel Dual Band Wireless-AC 7260 Intel Dual Band Wireless-AC 8260 Intel Wireless-AC 9260 Also for reference here are the specs of Intel adapter cards: ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 00:53:43 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1859308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
** Description changed: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. - I tried with noveau drivers and I have the same results btw. + I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) -- 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/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel
[Desktop-packages] [Bug 1883144] [NEW] Can't connect to ProtonVPN (probably VPN in general)
Public bug reported: Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-37-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15,6 GiB network-manager version: 1.22.10-1ubuntu2.1 What happens? I want to connect to VPN, no matter how I am doing so, be it using Plasma applet or via terminal (nmcli connection up se.protonvpn.com.udp), I can't. On the 4th June 2020 there was a network-manager update, and probably since this day I can't connect to VPN. Previously I could do so. Of course I have network-manager-openvpn installed, and ProtonVPN uses this method. When I try to connect using terminal command, I have message to run "journalctl -xe NM_CONNECTION=59f16a8e-7dcb-4638-a810-8d07efe00fde + NM_DEVICE=wlp7s0". When I run this, I've got warnings, which I have included in attachment "bug.txt". What I expect? I want to connect to VPN, like I used to earlier. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jun 11 18:07:41 2020 InstallationDate: Installed on 2020-02-05 (126 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp7s0 proto dhcp metric 600 169.254.0.0/16 dev wlp7s0 scope link metric 1000 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.17 metric 600 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-05-04 (38 days ago) 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 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "bug.txt" https://bugs.launchpad.net/bugs/1883144/+attachment/5383013/+files/bug.txt ** Description changed: Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-37-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15,6 GiB network-manager version: 1.22.10-1ubuntu2.1 What happens? I want to connect to VPN, no matter how I am doing so, be it using Plasma applet or via terminal (nmcli connection up se.protonvpn.com.udp), I can't. On the 4th June 2020 there was a network-manager update, and probably since this day I can't connect to VPN. Previously I could do so. Of course I have network-manager-openvpn installed, and ProtonVPN uses this method. When I try to connect using terminal command, I have message to run "journalctl -xe NM_CONNECTION=59f16a8e-7dcb-4638-a810-8d07efe00fde + NM_DEVICE=wlp7s0". - When I run this, I've got warnings, which I have included in attachment. - + When I run this, I've got warnings, which I have included in attachment "bug.txt". What I expect? I want to connect to VPN, like I used to earlier. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jun 11 18:07:41 2020 InstallationDate: Installed on 2020-02-05 (126 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: - default via 192.168.1.1 dev wlp7s0 proto dhcp metric 600 - 169.254.0.0/16 dev wlp7s0 scope link metric 1000 - 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.17 metric 600 + default via 192.168.1.1 dev wlp7s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp7s0 scope link metric 1000 + 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.17 metric 600 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-05-04 (38 days ago) 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 + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.22.10 connected started full enabled enabled enabled enabled enabled -- 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/1883144 Title: Can't connect to ProtonVPN (probably VPN in general) Status in network-manager package in Ubuntu: New Bug description: Operating System:
[Desktop-packages] [Bug 1882023] Re: Notifications are pointlessly truncated even on ultrawide monitors
** Package changed: ubuntu => gnome-shell (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/1882023 Title: Notifications are pointlessly truncated even on ultrawide monitors Status in gnome-shell package in Ubuntu: New Bug description: I tried to use ubuntu-bug -w to identify the component for this bug by clicking on a notification, but it failed with "xprop failed to determine process ID of the window". Sorry. The bug is that notifications of adding/removing icons to Favorites in the taskbar, are truncated for no good reason. I have a dual monitor setup ridiculous amounts of horizontal space, yet the notification is fixed size - which is fine, if it wrapped the text inside it. But it doesn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882023/+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 1881040] Re: [snap] chromedriver does not download where configured
I'm not sure I understand the problem. How is ~/snap/chromium/1165/Downloads a read-only location? Chromium (at least when not run headless) should default to your XDG Downloads directory, what does chrome://settings/downloads show? Can you share one of your Selenium-based download tests so that I can reproduce and investigate the problem? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1881040 Title: [snap] chromedriver does not download where configured Status in chromium-browser package in Ubuntu: Incomplete Bug description: I've recently been forced to upgrade to the SNAP based chromium setup. After being required to work through reconfiguring my $HOME, learn of the need to set up $XAUTHORITY I just now discovered that none of my Selenium based download tests work because the SNAP setup insists on downloading to: /home/xxx/snap/chromium/1165/Downloads rather than where the chromederiver download settings have been configured. Is there a way to override this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1881040/+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 1882291] Re: Displaying time issue before login
** Package changed: ubuntu => gnome-shell (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/1882291 Title: Displaying time issue before login Status in gnome-shell package in Ubuntu: New Bug description: When clock changes value, it doesn't displaying time properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882291/+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 1870450] Re: Firefox takes a moment before being reactive after launch
Indeed, the Ubuntu patch to enable global menu integration in Firefox was removed in 20.04 (see https://bazaar.launchpad.net/~mozillateam/firefox/firefox.focal/revision/1340). -- 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/1870450 Title: Firefox takes a moment before being reactive after launch Status in firefox package in Ubuntu: New Bug description: Description from duplicate bug report: Hi, on a freshly installed Ubuntu Budgie 19.10, I've noticed Firefox is kind of slow at start : ⋅ I can launch Firefox but it’s unresponsive for a moment ( no blinking cursor anywhere ) ⋅ then cursor eventually appears in address bar but blinking slowly and not usable, ⋅ still, clicking anywhere has no effect, or effect delayed much later, ⋅ a moment later, cursor blinks at its usual pace and Firefox becomes responsive as expected. The whole process takes 30 seconds to 1 minute and Firefox runs rather ok later on with some slow moments though ( sometimes tabs are slow to react, or any interactions with buttons in FF menu ). Same behavior in safe-mode ( without any FF addons ) Same without any Budgie applets regarding app-menu ( such as pixel- saver or global-menu applets ). see also : ⋅ https://discourse.ubuntubudgie.org/t/firefox-in-19-10-is-kind-of-slow-to-start/3265 ⋅ https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/813775 = Hi, sorry for duplicata, I did not know how to add info on the other same bug, see https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1869597 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 74.0+build3-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: django 6230 F pulseaudio /dev/snd/controlC1: django 6230 F pulseaudio /dev/snd/pcmC1D0p: django 6230 F...m pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: Budgie:GNOME Date: Fri Apr 3 02:04:06 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:732 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-03-22 (11 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.254 dev enp3s0 proto static metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.99 metric 100 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:732 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=74.0/20200309095159 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870450/+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 1882457] Re: ALSA error
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1882457 Title: ALSA error Status in alsa-driver package in Ubuntu: New Bug description: After launching some applications (e.g. the stepmania game), ALSA will restart. Then the system sounds work, but the application has no sound. They still work with the 5.3.0-19 kernel, but none with the following. I tried everything all the way through. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1882457/+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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
for a sound card, there is a short-name and long-name. I only adjust the short name which the pulseaudio utilize to identify the ucm config. old short name: sofsklhdacard new short name: sofhdadsp may I know how you grepping it? what command you use would be enough. Thanks, -- 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/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: Triaged Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-wip 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1882556] Re: Sometimes taking a screenshot will crash gnome-shell
Thanks for pointing out those instructions. I wasn't entirely sure where that stuff was. Unfortunately, it seems that there's no useful crash logs in /var/crash, and nothing is showing up online either. The best I can do is give you a short video of the symptoms, in hopes that something can help. https://photos.app.goo.gl/NuXQqPsxdK7z7zs68 -- 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/1882556 Title: Sometimes taking a screenshot will crash gnome-shell Status in gnome-screenshot package in Ubuntu: Invalid Bug description: When taking a screenshot, sometimes my whole GNOME desktop will crash. It feels like about a quarter of the time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 11:30:15 2020 InstallationDate: Installed on 2020-05-05 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1882556/+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 1882023] [NEW] Notifications are pointlessly truncated even on ultrawide monitors
You have been subscribed to a public bug: I tried to use ubuntu-bug -w to identify the component for this bug by clicking on a notification, but it failed with "xprop failed to determine process ID of the window". Sorry. The bug is that notifications of adding/removing icons to Favorites in the taskbar, are truncated for no good reason. I have a dual monitor setup ridiculous amounts of horizontal space, yet the notification is fixed size - which is fine, if it wrapped the text inside it. But it doesn't. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Notifications are pointlessly truncated even on ultrawide monitors https://bugs.launchpad.net/bugs/1882023 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882291] [NEW] Displaying time issue before login
You have been subscribed to a public bug: When clock changes value, it doesn't displaying time properly ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: clock display login -- Displaying time issue before login https://bugs.launchpad.net/bugs/1882291 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882457] [NEW] ALSA error
You have been subscribed to a public bug: After launching some applications (e.g. the stepmania game), ALSA will restart. Then the system sounds work, but the application has no sound. They still work with the 5.3.0-19 kernel, but none with the following. I tried everything all the way through. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- ALSA error https://bugs.launchpad.net/bugs/1882457 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881040] Re: SNAP chromedriver does not download where configured
** Tags added: snap ** Summary changed: - SNAP chromedriver does not download where configured + [snap] chromedriver does not download where configured -- 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/1881040 Title: [snap] chromedriver does not download where configured Status in chromium-browser package in Ubuntu: New Bug description: I've recently been forced to upgrade to the SNAP based chromium setup. After being required to work through reconfiguring my $HOME, learn of the need to set up $XAUTHORITY I just now discovered that none of my Selenium based download tests work because the SNAP setup insists on downloading to: /home/xxx/snap/chromium/1165/Downloads rather than where the chromederiver download settings have been configured. Is there a way to override this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1881040/+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 1815289] Re: Please add Provides: gnome-www-browser
Confirmed fixed with chromium-browser 81.0.4044.129-0ubuntu0.19.10.1 from eoan-proposed. I verified chromium-browser didn't appear in the list of reverse provides for x-www-browser and gnome-www-browser in a fully up-to-date eoan VM, then I enabled eoan-proposed for universe, ran "apt update", and verified that it did appear for both. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1815289 Title: Please add Provides: gnome-www-browser Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: Fix Committed Status in chromium-browser source package in Focal: Fix Released Bug description: [Impact] Low. Some Debian packages depend on gnome-www-browser, and chromium- browser should be marked as providing it (similarly, it should provide x-www-browser). For instance, cinnamon-desktop-environment depends on gnome-www- browser and it doesn't have the chromium-browser name in the alternates (it has Debian's chromium name instead). [Test case] The output of `apt-cache showpkg gnome-www-browser` after the "Reverse Provides:" line should contain a chromium-browser entry. Similarly for `apt-cache showpkg x-www-browser`. [Regression potential] This is adding a couple of "provides" entries to the control file. Regressions could happen if other packages depending on or recommending gnome-www-browser (or x-www-browser) were implicitly relying on the fact that chromium-browser wasn't a candidate, but that sounds unlikely, and in any case something that should be fixed in thoses packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1815289/+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 1870640] Re: Does not register as x-www-browser alternative
s/focal-proposed/eoan-proposed/ in the above comment, obviously… ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1870640 Title: Does not register as x-www-browser alternative Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: Fix Committed Status in chromium-browser source package in Focal: Fix Released Bug description: [Impact] Low. When installing chromium-browser in eoan/focal (which is a transitional package that installs the chromium snap), update- alternatives cannot be used to set it as x-www-browser or gnome-www- browser. This is a regression compared to the version of chromium- browser in bionic. [Test case] # update-alternatives --set x-www-browser /usr/bin/chromium-browser update-alternatives: error: alternative /usr/bin/chromium-browser for x-www-browser not registered; not setting [Regression potential] This is fixing a regression by adding back a code snippet that was in the package in bionic and previous releases. If the snippet has incorrect syntax, it could possibly prevent installation of the package. If the package installs fine, it's unlikely that anything could have regressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1870640/+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 1870640] Re: Does not register as x-www-browser alternative
Confirmed fixed with chromium-browser 81.0.4044.129-0ubuntu0.19.10.1 from focal-proposed. I verified update-alternatives couldn't be used to set the default value of [x-www-browser|gnome-www-browser] to /usr/bin/chromium-browser in a fully up-to-date focal VM, then I enabled focal-proposed for universe, ran "apt update" and "apt dist-upgrade" to install the updated chromium- browser package, and I verified that update-alternatives now accepted to set the default x-www-browser|gnome-www-browser. I also verified that running x-www-browser|gnome-www-browser did launch chromium-browser, as expected. -- 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/1870640 Title: Does not register as x-www-browser alternative Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: Fix Committed Status in chromium-browser source package in Focal: Fix Released Bug description: [Impact] Low. When installing chromium-browser in eoan/focal (which is a transitional package that installs the chromium snap), update- alternatives cannot be used to set it as x-www-browser or gnome-www- browser. This is a regression compared to the version of chromium- browser in bionic. [Test case] # update-alternatives --set x-www-browser /usr/bin/chromium-browser update-alternatives: error: alternative /usr/bin/chromium-browser for x-www-browser not registered; not setting [Regression potential] This is fixing a regression by adding back a code snippet that was in the package in bionic and previous releases. If the snippet has incorrect syntax, it could possibly prevent installation of the package. If the package installs fine, it's unlikely that anything could have regressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1870640/+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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
I can try to help with the grepping but I don't understand what were the old names and what are the new ones, maybe you could give some details on the changes? -- 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/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: Triaged Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-wip 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/
You're right Oliver, the patch should be adjusted to look for policies in $SNAP_DATA. ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: chromium-browser (Ubuntu) Importance: Low => Medium -- 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/1714244 Title: [snap] apparmor denials on /etc/chromium-browser/policies/ Status in chromium-browser package in Ubuntu: Triaged Bug description: [1565519.440403] audit: type=1400 audit(1504185084.568:68574811): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/managed/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [1565519.440527] audit: type=1400 audit(1504185084.568:68574812): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/recommended/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Those denials don't appear to prevent the app from running. Still, they should be investigated and fixed if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+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 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/
And for migration purposes, ideally the existing policies in /etc /chromium-browser/policies would be copied over to $SNAP_DATA/. -- 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/1714244 Title: [snap] apparmor denials on /etc/chromium-browser/policies/ Status in chromium-browser package in Ubuntu: Triaged Bug description: [1565519.440403] audit: type=1400 audit(1504185084.568:68574811): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/managed/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [1565519.440527] audit: type=1400 audit(1504185084.568:68574812): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/recommended/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Those denials don't appear to prevent the app from running. Still, they should be investigated and fixed if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
*** This bug is a duplicate of bug 1878194 *** https://bugs.launchpad.net/bugs/1878194 Correct. This is not a duplicate of #1576559. #1878194 is a duplicate of this one. But all the action is on #1878194, so let's make that one the original bug. ** This bug is no longer a duplicate of bug 1576559 Refused to switch profile to headset_head_unit: Not connected ** This bug has been marked a duplicate of bug 1878194 [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in pulseaudio package in Ubuntu: New Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
@Sebstien Could you help to indicate how to do the archive search? I'll try to finish it to lower the regression risk. Sorry that I have less experience about it, it would be nice if you can give me more insight. Thanks, -- 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/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: Triaged Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-wip 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1883134] [NEW] Xorg Nvidia problem-freeze at login
Public bug reported: I've got a problem,where nvidia drivers cannot work with Xorg,but im ok with Wayland. I tried different things. Im trying now to reinstall xorg and use nouvaeu drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 18:19:02 2020 InstallationDate: Installed on 2019-12-30 (163 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- 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/1883134 Title: Xorg Nvidia problem-freeze at login Status in xorg package in Ubuntu: New Bug description: I've got a problem,where nvidia drivers cannot work with Xorg,but im ok with Wayland. I tried different things. Im trying now to reinstall xorg and use nouvaeu drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 18:19:02 2020 InstallationDate: Installed on 2019-12-30 (163 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883134/+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 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
Reverted in https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from- source/commit/?id=d3a863f6e544867e6596601c4f5f5373539e56af. -- 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/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Fix Released Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+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 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
I can confirm both Roman's observation in comment #25, and Nick's in comment #27. Seeing that there are real problems with the implementation, I'm going to revert it for now, until I can work out a better solution (or, ideally, a better mechanism is implemented in snapd itself). -- 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/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Fix Released Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+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 1883130] [NEW] Icons overlay at top bar
Public bug reported: When I open some apps, some of them displays a top bar icon. At some point, there is so many icons than they overlay the clock, as shown in attachment. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-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: ubuntu:GNOME Date: Thu Jun 11 11:54:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:139d] InstallationDate: Installed on 2020-05-26 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. S451LA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=85895dc0-0f4c-4998-9659-78a68fab28cd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S451LA.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S451LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS451LA.403:bd01/17/2014:svnASUSTeKCOMPUTERINC.:pnS451LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS451LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: S dmi.product.name: S451LA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 ** Attachment added: "Screenshot from 2020-06-11 12-01-13.png" https://bugs.launchpad.net/bugs/1883130/+attachment/5382960/+files/Screenshot%20from%202020-06-11%2012-01-13.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1883130 Title: Icons overlay at top bar Status in xorg package in Ubuntu: New Bug description: When I open some apps, some of them displays a top bar icon. At some point, there is so many icons than they overlay the clock, as shown in attachment. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-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: ubuntu:GNOME Date: Thu Jun 11 11:54:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:139d] InstallationDate: Installed on 2020-05-26 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. S451LA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=85895dc0-0f4c-4998-9659-78a68fab28cd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S451LA.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S451LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS451LA.403:bd01/17/2014:svnASUSTeKCOMPUTERINC.:pnS451LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS451LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: S
[Desktop-packages] [Bug 1877173] Re: Chromium 81.0.4044.122 crashes on remote ssh connection
Thanks for the upstream report Mike. I see it has been marked as a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=1035803, and comment #19 there suggests the following: tldr; manually turn off shared memory by using the "--no-xshm" flag, setting the environment variable "QT_X11_NO_MITSHM=1" or "J2D_USE_MITSHM=0". Does this address your crash? -- 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/1877173 Title: Chromium 81.0.4044.122 crashes on remote ssh connection Status in chromium-browser package in Ubuntu: New Bug description: Chromium crash on a ssh x forwarding connection It crashes on both 18.04 and 16.04 with the same message. The X forwarding is working for other programs just fine. It was working until last update. Here is the message from the console on the crash [22765:22781:0506/144206.193243:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye. Trace/breakpoint trap (core dumped) Steps to repeat: ssh ltcd-prod chromum-browser ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 81.0.4044.122-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: btrfs xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid veth iptable_filter bpfilter bridge stp llc binfmt_misc intel_powerclamp coretemp kvm_intel kvm irqbypass zfs zunicode zavl icp ipmi_ssif gpio_ich crct10dif_pclmul crc32_pclmul ghash_clmulni_intel zcommon znvpair spl zlua aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate ast drm_vram_helper ttm drm_kms_helper lpc_ich drm joydev input_leds fb_sys_fops syscopyarea sysfillrect sysimgblt ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel lp parport nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 hid_generic igb uas usbhid ahci i2c_algo_bit hid libahci usb_storage dca i2c_ismt ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: modes: 1024x768 800x600 800x600 640x480 Date: Wed May 6 14:37:46 2020 Desktop-Session: 'None' 'None' 'None' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: Load-Avg-1min: 0.55 Load-Processes-Running-Percent: 0.1% Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: Supermicro A1SAi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-40-generic root=UUID=c75e8c2a-b85d-444e-b278-16fd90c327e7 ro usb_storage.quirks=0bc2:331a:u,0bc2:ab31:u,0bc2:ab34:u SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.1a dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A1SRi dmi.board.vendor: Supermicro dmi.board.version: 123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 18 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.1a:bd08/27/2015:svnSupermicro:pnA1SAi:pvr123456789:rvnSupermicro:rnA1SRi:rvr123456789:cvnToBeFilledByO.E.M.:ct18:cvrToBeFilledByO.E.M.: dmi.product.family: SMC X10 dmi.product.name: A1SAi dmi.product.sku: 081315D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877173/+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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
@Kai, is there any archive search or similar that could be done to ensure nothing is relying on the old naming? could it break existing user configurations? -- 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/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: Triaged Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-wip 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881423] Re: error channel closing too late to send/recv
Do those messages appear to be associated to unwanted behaviour/side effects (crashes, browser not functioning)? -- 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/1881423 Title: error channel closing too late to send/recv Status in firefox package in Ubuntu: New Bug description: I saw the following in my logs on a fresh install of 18.04.4: May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Sat May 30 12:57:41 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1881423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881923] Re: No icons in file picker
Can you run the following command in a terminal, after closing chromium: rm -rf ~/snap/chromium/common/.cache Then run chromium again, and let us know whether the problem persist. Thanks! -- 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 1883116] [NEW] SRU the current 3.36.3 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1883116 Title: SRU the current 3.36.3 stable update Status in evolution-data-server package in Ubuntu: New Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1883116/+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: Statusbar preferences options aren't stored
Thanks, confirming the issue with the statusbar menu items. Those options aren't supposed to be editing gedit preferences though but they should apply to the current document and be stored for it. Could you maybe report the issue upstream on https://gitlab.gnome.org/GNOME/gedit/-/issues to get their feedback on the intended behaviour? ** Summary changed: - Gedit unable to save preferences on 20.04 + Statusbar preferences options aren't stored ** Changed in: gedit (Ubuntu) Status: Incomplete => Confirmed -- 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: Statusbar preferences options aren't stored Status in gedit package in Ubuntu: Confirmed 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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic
@seb128 it is just a potential worry, I've verified on three different CPU platforms Cometlake, Coffeelake, and Whiskylake. They work both on old kernel and the 5.4-edge-kernel. I don't know If my description is appropriate, it is nice if you can give me some input, thanks. -- 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/1881094 Title: Support kernel 5.4 Intel sound driver on bionic Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Invalid Status in pulseaudio source package in Bionic: Triaged Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function 1. enable Pre-released updates in Developer Options Software & Updates > Developer Options > Pre-released updates (bionic-proposed) 2. $ sudo apt update 3. $ sudo apt install linux-generic-hwe-18.04-wip 4. $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
@François, thanks a lot! I've copied your description at the top of the report now ** Description changed: - * Impact - connecting to wifi fails with some drivers + [Impact] - * Test case - try to connect to wifi, it should work + * A driver supports FT (IEEE 802.11r-2008 or fast BSS transition (FT), +also called fast roaming) if it either supports SME or the +NL80211_CMD_UPDATE_FT_IES command. When selecting AKM suites, +wpa_supplicant currently doesn't take into account whether or not either +of those conditions are met. This can cause association failures, e.g., +when an AP supports both WPA-EAP and FT-EAP but the driver doesn't +support FT (wpa_supplicant will decide to do FT-EAP since it is unaware +the driver doesn't support it). - * Regression potential - ? + * This is known to affect users at least users with popular chip-sets, +such as BCM20703A1 or BCM4350 (notably present in the popular XPS 13/15 +laptops). + * The upload fixes the bug by allowing an FT suite to be selected only +when the driver also supports FT. + + [Test Case] + + * requires affected hardware and wpa_supplicant built with CONFIG_IEEE80211R +and connecting to an AP supporting WPA-EAP and FT-EAP + + [Regression Potential] + + * a driver not advertising correctly its support for SME or the +NL80211_CMD_UPDATE_FT_IES command via the drv_flags would be prevented from +using FT but would still be able to connect to APs + + [Other Info] + + * Upstream fix: https://w1.fi/cgit/hostap/commit/?id=23dc196fde951b3d508f367a603cddffbd053490 + * Initial report: https://bugs.archlinux.org/task/63397 --- Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Invalid Status in wpa package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in wpa source package in Focal: Confirmed Status in linux source package in Groovy: Invalid Status in wpa source package in Groovy: Fix Committed Bug description: [Impact] * A driver supports FT (IEEE 802.11r-2008 or fast BSS transition (FT), also called fast roaming) if it either supports SME or the NL80211_CMD_UPDATE_FT_IES command. When selecting AKM suites, wpa_supplicant currently doesn't take into account whether or not either of those conditions are met. This can cause association failures, e.g., when an AP supports both WPA-EAP and FT-EAP but the driver doesn't support FT (wpa_supplicant will decide to do FT-EAP since it is unaware the driver doesn't support it). * This is known to affect users at least users with popular chip-sets, such as BCM20703A1 or BCM4350 (notably present in the popular XPS 13/15 laptops). * The upload fixes the bug by allowing an FT suite to be selected only when the driver also supports FT. [Test Case] * requires affected hardware and wpa_supplicant built with CONFIG_IEEE80211R and connecting to an AP supporting WPA-EAP and FT-EAP [Regression Potential] * a driver
[Desktop-packages] [Bug 1880411] Re: Support both Super keys simultaneously on org.gnome.mutter overlay-key
It happens the same with the Spanish (International) layout. This is a highly requested feature! -- 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/1880411 Title: Support both Super keys simultaneously on org.gnome.mutter overlay-key Status in Mutter: Unknown Status in gnome-tweaks package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: The right super key doesn't show the overlay. Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880411/+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 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
(sorry, previous comment is a misclick) @seb128, as I dealt with it first hand a few month ago with upstream packages (see https://bugs.archlinux.org/task/63397 ) maybe I can shed some light on it and help you write the SRU. This would be my suggestion: [Impact] * A driver supports FT (IEEE 802.11r-2008 or fast BSS transition (FT), also called fast roaming) if it either supports SME or the NL80211_CMD_UPDATE_FT_IES command. When selecting AKM suites, wpa_supplicant currently doesn't take into account whether or not either of those conditions are met. This can cause association failures, e.g., when an AP supports both WPA-EAP and FT-EAP but the driver doesn't support FT (wpa_supplicant will decide to do FT-EAP since it is unaware the driver doesn't support it). * This is known to affect users at least users with popular chip-sets, such as BCM20703A1 or BCM4350 (notably present in the popular XPS 13/15 laptops). * The upload fixes the bug by allowing an FT suite to be selected only when the driver also supports FT. [Test Case] * requires affected hardware and wpa_supplicant built with CONFIG_IEEE80211R and connecting to an AP supporting WPA-EAP and FT-EAP [Regression Potential] * a driver not advertising correctly its support for SME or the NL80211_CMD_UPDATE_FT_IES command via the drv_flags would be prevented from using FT but would still be able to connect to APs [Other Info] * Upstream fix: https://w1.fi/cgit/hostap/commit/?id=23dc196fde951b3d508f367a603cddffbd053490 * Initial report: https://bugs.archlinux.org/task/63397 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Invalid Status in wpa package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in wpa source package in Focal: Confirmed Status in linux source package in Groovy: Invalid Status in wpa source package in Groovy: Fix Committed Bug description: * Impact connecting to wifi fails with some drivers * Test case try to connect to wifi, it should work * Regression potential ? --- Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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