[Desktop-packages] [Bug 1893311] Re: Add libcurl4-openssl-dev build-dep for lumix camlib
This is now fixed in Debian as of 2.5.26-1 https://salsa.debian.org /debian-phototools-team/libgphoto2/-/merge_requests/3 ** Changed in: libgphoto2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgphoto2 in Ubuntu. https://bugs.launchpad.net/bugs/1893311 Title: Add libcurl4-openssl-dev build-dep for lumix camlib Status in libgphoto2 package in Ubuntu: Fix Released Bug description: The lumix camlib is in a somewhat usable state (https://github.com/gphoto/libgphoto2/issues/409) and I have been successfully using it for a few months. It would be good to add the libcurl4-openssl-dev to Build-Depends to enable building the lumix camlib. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1893311/+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 1899731] [NEW] Yaru gtk and icon update for focal backported from groovy
Public bug reported: [Impact] * Focal users will soon have their yaru themes mismatched in snaps and debs * yaru-theme-gtk and yaru-theme-icon includes changes for button sizes in groovy, gtk-common-themes will be updated with the updated yaru- theme-gtk so groovies debs and snaps look consistent but this will leave focal deb and snaps incosistent, so focals debs also need an update. * Backporting the yaru gtk theme from groovy to focal will fix this, the SHELL theme (yaru-theme-gnome-shell) however should NOT be backported, because the gnome shell version is different and thus the JavaScript components of gnome-shell would then not match the theme any more. The icon theme however, can also be backported if wanted [Test Case] * Update gtk-common-themes from https://gitlab.gnome.org/Community/Ubuntu/gtk-common- themes/-/jobs/937763/artifacts/browse in focal and see how gtk debs like nautilus look different in button sizing than snap-store aka ubuntu software * install the https://github.com/ubuntu/yaru/releases/tag/20.10.6.1 and see how now the deb and snaps look the same [Regression Potential] * no regression potential unless the gnome shell theme is also backported which should NOT happen [Other Info] * The updates were necessary for groovy, because having gtk3 themes with different button sizes than adwaita creates issues with sizes, see https://github.com/ubuntu/yaru/pull/2361 for further issues linked ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1899731 Title: Yaru gtk and icon update for focal backported from groovy Status in yaru-theme package in Ubuntu: New Bug description: [Impact] * Focal users will soon have their yaru themes mismatched in snaps and debs * yaru-theme-gtk and yaru-theme-icon includes changes for button sizes in groovy, gtk-common-themes will be updated with the updated yaru-theme-gtk so groovies debs and snaps look consistent but this will leave focal deb and snaps incosistent, so focals debs also need an update. * Backporting the yaru gtk theme from groovy to focal will fix this, the SHELL theme (yaru-theme-gnome-shell) however should NOT be backported, because the gnome shell version is different and thus the JavaScript components of gnome-shell would then not match the theme any more. The icon theme however, can also be backported if wanted [Test Case] * Update gtk-common-themes from https://gitlab.gnome.org/Community/Ubuntu/gtk-common- themes/-/jobs/937763/artifacts/browse in focal and see how gtk debs like nautilus look different in button sizing than snap-store aka ubuntu software * install the https://github.com/ubuntu/yaru/releases/tag/20.10.6.1 and see how now the deb and snaps look the same [Regression Potential] * no regression potential unless the gnome shell theme is also backported which should NOT happen [Other Info] * The updates were necessary for groovy, because having gtk3 themes with different button sizes than adwaita creates issues with sizes, see https://github.com/ubuntu/yaru/pull/2361 for further issues linked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1899731/+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 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers
Hi Daniel, so I deleted the pulse config, and rebooted, but amazingly my stupid BIOS doesn't have an option to disable the sound. Now regardless of the kernel I go into for the output device it shows "dummy output" and the sound doesn't work. I guess the config is broken from the "rm -r ~/.config/pulse*" command. Any idea how to fix or reset things without using BIOS? Now not able to use any sound at all regardless of kernel -- 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/1898603 Title: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound output is detected as "headphones" instead of Speakers when this laptop doesn't even have any headphones connected at all... reverting to a prior kernel fixes the problem and then the output is correctly Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and the Mint Linux support chat said I should file a bug for this because this kernel broke something. See attached detailed log reports for more info... Thanks team!!! Best Regards, -Avery Tarasov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chr0meice2 2656 F pulseaudio /dev/snd/controlC0: chr0meice2 2656 F pulseaudio /dev/snd/pcmC0D0c: chr0meice2 2656 F...m pulseaudio /dev/snd/pcmC0D0p: chr0meice2 2656 F...m pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-10-05 (0 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-driver (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: ulyana Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898603/+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 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
Wolf, Most likely the staggered rollout of mutter 3.36.6 has not reached you yet. Just check the version of package libmutter-6-0 you have installed. If it is 3.36.6 or higher then perhaps open a new bug by running: ubuntu-bug mutter And please open a separate bug for each issue. -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+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 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
nvidia 340 driver, GT218M / 3100NVS card on HP 8440p laptop, System: focal Have still the "corrupted desktop" problem; changing to "proposed" made that I could no longer resume from hibernate. With "proposed", screen would power on back light for a few seconds and then remain dark. Unticking the "proposed" box with update luckily led to a resuming system again. -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+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 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers
Hey Daniel, Re-testing on Linux frozenkeep 5.4.0-51-generic #56-Ubuntu SMP Mon Oct 5 14:28:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux and still have the problem... I'm double checking the above and seeing if still have same issue but looks like it still is broken -- 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/1898603 Title: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound output is detected as "headphones" instead of Speakers when this laptop doesn't even have any headphones connected at all... reverting to a prior kernel fixes the problem and then the output is correctly Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and the Mint Linux support chat said I should file a bug for this because this kernel broke something. See attached detailed log reports for more info... Thanks team!!! Best Regards, -Avery Tarasov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chr0meice2 2656 F pulseaudio /dev/snd/controlC0: chr0meice2 2656 F pulseaudio /dev/snd/pcmC0D0c: chr0meice2 2656 F...m pulseaudio /dev/snd/pcmC0D0p: chr0meice2 2656 F...m pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-10-05 (0 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-driver (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: ulyana Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898603/+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 1899720] Re: Gnome takes MORE THAN 20 SECONDS to open a folder
It sounds like nautilus is blocked waiting for one or more slow mounts. Most likely that's a network mount, so try removing any of those temporarily. Less likely it's a local disk failure. Please also check that the problem is not high CPU by running 'top'. If you can't find the source of the problem then please: 1. Reboot to create a fresh system log. 2. Reproduce the problem once. 3. Immediately run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Package changed: gnome-shell (Ubuntu) => nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1899720 Title: Gnome takes MORE THAN 20 SECONDS to open a folder Status in nautilus package in Ubuntu: Incomplete Bug description: After upgrading from 18.04 to 20.04, Ubuntu has become UNUSABLE. When I try to open e.g. my home folder, or "New Window" from the file tool in the app bar, it can take 15, 20 or 30 seconds for anything to happen. Then sometimes the response is instant. Something is seriously seriously wrong with your software. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 13:31:10 2020 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-31 (1231 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 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/nautilus/+bug/1899720/+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 1899720] [NEW] Gnome takes MORE THAN 20 SECONDS to open a folder
Public bug reported: After upgrading from 18.04 to 20.04, Ubuntu has become UNUSABLE. When I try to open e.g. my home folder, or "New Window" from the file tool in the app bar, it can take 15, 20 or 30 seconds for anything to happen. Then sometimes the response is instant. Something is seriously seriously wrong with your software. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 13:31:10 2020 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-31 (1231 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 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/1899720 Title: Gnome takes MORE THAN 20 SECONDS to open a folder Status in gnome-shell package in Ubuntu: New Bug description: After upgrading from 18.04 to 20.04, Ubuntu has become UNUSABLE. When I try to open e.g. my home folder, or "New Window" from the file tool in the app bar, it can take 15, 20 or 30 seconds for anything to happen. Then sometimes the response is instant. Something is seriously seriously wrong with your software. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 13:31:10 2020 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-31 (1231 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 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/1899720/+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 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()
I'm still not sure what to make of this bug. The fix linked upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/1345 is supposedly in mutter 3.35.2 but there are plenty of these crashes after that: https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa So it seems like at least one of those should not be linked here. That said, if we don't see any more crashes in 3.36.6 and 3.38.1 then there's nothing left to do and resolving the confusion is not required. -- 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/1558886 Title: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] Using Ubuntu 16.04 and 20.04 LTS Beta release. Was using gnome-shell and using Chrome web browser when computer became unresponsive to any commands or mouse clicks. About 3-4 minutes later a crash report popped up on my screen. I clicked report and now I am reporting this as a new bug as I have never had this happen before on previous versions of Ubuntu. I was attempting to copy and save an image from Google Chrome when this happened. Similar crash still happening, as per https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa [ Test case ] Run xinput and figure device IDs for your mouse. Run this evil script with 9 changed (be sure to change both) to your id: for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo Enabled; done While the script runs, open some context menu in some program. It may require a few clicks due to evil script enabling/disabling mouse. This will sometimes crash GTK programs due to a mirror bug in GTK. GNOME Shell should not crash [ Regression potential ] Devices might be not be properly recognized when plugged and unplugged Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable google-chrome-stable: Installed: 49.0.2623.75-1 Candidate: 49.0.2623.75-1 Version table: *** 49.0.2623.75-1 100 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 17 22:20:56 2016 DisplayManager: lightdm ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-24 (22 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax PC (0x7f634ba78320) ok source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/libmutter.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event() UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1558886/+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 1892486] Re: gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from cc_sound_panel_init
I know and I agree. Comments #8 and #9 were hours apart and I just forgot to remove the tag. -- 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/1892486 Title: gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from cc_sound_panel_init Status in gnome-control-center package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170 --- Not sure yet. Wait for the retrace. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 21 18:19:17 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-07-16 (36 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f8657e0f611 <__strstr_sse2_unaligned+81>: movdqu (%rdi),%xmm3 PC (0x7f8657e0f611) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm3" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV 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/ubuntu/+source/gnome-control-center/+bug/1892486/+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 1892486] Re: gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from cc_sound_panel_init
I known and I agree. Comments #8 and #9 were hours apart and I just forgot to remove the tag. -- 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/1892486 Title: gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from cc_sound_panel_init Status in gnome-control-center package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170 --- Not sure yet. Wait for the retrace. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 21 18:19:17 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-07-16 (36 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f8657e0f611 <__strstr_sse2_unaligned+81>: movdqu (%rdi),%xmm3 PC (0x7f8657e0f611) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm3" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV 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/ubuntu/+source/gnome-control-center/+bug/1892486/+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 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()
** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1558886 Title: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] Using Ubuntu 16.04 and 20.04 LTS Beta release. Was using gnome-shell and using Chrome web browser when computer became unresponsive to any commands or mouse clicks. About 3-4 minutes later a crash report popped up on my screen. I clicked report and now I am reporting this as a new bug as I have never had this happen before on previous versions of Ubuntu. I was attempting to copy and save an image from Google Chrome when this happened. Similar crash still happening, as per https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa [ Test case ] Run xinput and figure device IDs for your mouse. Run this evil script with 9 changed (be sure to change both) to your id: for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo Enabled; done While the script runs, open some context menu in some program. It may require a few clicks due to evil script enabling/disabling mouse. This will sometimes crash GTK programs due to a mirror bug in GTK. GNOME Shell should not crash [ Regression potential ] Devices might be not be properly recognized when plugged and unplugged Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable google-chrome-stable: Installed: 49.0.2623.75-1 Candidate: 49.0.2623.75-1 Version table: *** 49.0.2623.75-1 100 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 17 22:20:56 2016 DisplayManager: lightdm ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-24 (22 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax PC (0x7f634ba78320) ok source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/libmutter.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event() UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1558886/+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 1880086] Re: [nvidia+xorg] High latency while running gtk4 demos like Fishbowl
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1291 https://gitlab.gnome.org/GNOME/mutter/-/issues/1291 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1291 Importance: Unknown Status: Unknown ** Summary changed: - [nvidia+xorg] High latency while running gtk4 demos like Fishbowl + High latency when using the Nvidia-Xorg driver -- 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/1880086 Title: High latency when using the Nvidia-Xorg driver Status in Mutter: Unknown Status in mutter package in Ubuntu: In Progress Bug description: High latency while running gtk4 demos like Fishbowl, using the Nvidia driver (on Xorg) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880086/+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 1899675] Re: Desktop background image is corrupted after suspend
*** This bug is a duplicate of bug 1855757 *** https://bugs.launchpad.net/bugs/1855757 Looks like bug 1855757. This should be fixed by the latest libmutter-6-0 3.36.6 update. Please update your system by running: sudo apt update sudo apt full-upgrade and then reboot. ** Tags added: nvidia ** This bug has been marked a duplicate of bug 1855757 [nvidia] Background image corrupted after standby or resume from suspend -- 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/1899675 Title: Desktop background image is corrupted after suspend Status in gnome-shell package in Ubuntu: New Bug description: Immediately after resuming from suspend, any desktop background image is corrupted. Expected desktop image to be shown as set in Settings > Background. Notes: * Happens since day 0 of installation. * Does not happen after restart; only after suspend mode. Details: Description: Ubuntu 20.04.1 LTS Release: 20.04 possible alternate application: Gnome-control-center nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899675/+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 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
** Changed in: mutter (Ubuntu Focal) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+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 1899619] Re: [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds
** Tags added: a2dp -- 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/1899619 Title: [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds Status in pulseaudio package in Ubuntu: New Bug description: Hello! I'm not really sure if is pulseaudio of bluez issue. Playback (from Gnome Settings sound test and Firefox), volume change, mute/resume is delayed for 2sec or bit more. I've verified this on two Ubuntu 20.04 laptops. To verify the AV receiver, I've paired MBP 2019 with OS X Catalina 10.15.7 and there are no audible delay. Here is sink information: * index: 16 name: driver: flags: HARDWARE DECIBEL_VOLUME LATENCY state: RUNNING suspend cause: (none) priority: 9550 volume: front-left: 46512 / 71% / -8,93 dB, front-right: 46512 / 71% / -8,93 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 56,81 ms max request: 4 KiB max rewind: 0 KiB monitor source: 18 sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 1 linked by: 4 fixed latency: 48,22 ms card: 17 module: 45 properties: bluetooth.protocol = "a2dp_sink" device.description = "Denon AVR-S650H" device.string = "00:05:CD:DF:C4:DD" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "speaker" bluez.path = "/org/bluez/hci0/dev_00_05_CD_DF_C4_DD" bluez.class = "0x240414" bluez.alias = "Denon AVR-S650H" device.icon_name = "audio-speakers-bluetooth" ports: speaker-output: Speaker (priority 0, latency offset 0 usec, available: yes) properties: active port: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.5-050805-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bogdan82720 F pulseaudio /dev/snd/controlC1: bogdan82720 F pulseaudio /dev/snd/controlC0: bogdan82720 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 13 13:46:35 2020 InstallationDate: Installed on 2020-08-05 (68 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Denon AVR-S650H Symptom_Type: None of the above Title: [Denon AVR-S650H, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 2.1 dmi.bios.vendor: HP dmi.bios.version: S79 Ver. 01.02.01 dmi.board.name: 8730 dmi.board.vendor: HP dmi.board.version: KBC Version 13.1C.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 19.28 dmi.modalias: dmi:bvnHP:bvrS79Ver.01.02.01:bd07/02/2020:br2.1:efr19.28:svnHP:pnHPProBook455G7:pvr:rvnHP:rn8730:rvrKBCVersion13.1C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 455 G7 dmi.product.sku: 2D242EA#ACB dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899619/+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 1879968] Re: Copy/paste still sometimes fails in LibreOffice and Wine apps
David, this bug is now closed. Please open new bugs for any further problems by running: ubuntu-bug mutter ** Changed in: mutter (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1879968 Title: Copy/paste still sometimes fails in LibreOffice and Wine apps Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Changed in: pam (Ubuntu Bionic) Status: New => Invalid ** Changed in: pam (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in gdm3 package in Ubuntu: Confirmed Status in pam package in Ubuntu: Invalid Status in gdm3 source package in Bionic: New Status in pam source package in Bionic: Invalid Status in gdm3 source package in Focal: Confirmed Status in pam source package in Focal: Invalid Status in gdm3 source package in Groovy: Confirmed Status in pam source package in Groovy: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+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 1899683] Re: Screen auto rotates orientation only when screen is locked
** Package changed: ubuntu => iio-sensor-proxy (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1899683 Title: Screen auto rotates orientation only when screen is locked Status in iio-sensor-proxy package in Ubuntu: New Bug description: Ran 'monitor-sensor' in terminal and all looks well. When I boot up to login and then rotate my laptop the screen changes orientation as it should. But once I'm logged in I lose auto rotate. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: iio-sensor-proxy 3.0-1 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:01:58 2020 InstallationDate: Installed on 2020-07-22 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iio-sensor-proxy UpgradeStatus: Upgraded to groovy on 2020-10-11 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1899683/+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 1899683] [NEW] Screen auto rotates orientation only when screen is locked
You have been subscribed to a public bug: Ran 'monitor-sensor' in terminal and all looks well. When I boot up to login and then rotate my laptop the screen changes orientation as it should. But once I'm logged in I lose auto rotate. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: iio-sensor-proxy 3.0-1 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:01:58 2020 InstallationDate: Installed on 2020-07-22 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iio-sensor-proxy UpgradeStatus: Upgraded to groovy on 2020-10-11 (2 days ago) ** Affects: iio-sensor-proxy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- Screen auto rotates orientation only when screen is locked https://bugs.launchpad.net/bugs/1899683 You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy 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 1897281] Re: evince suicides in 20.04 but not in 18.04
@Sebastien Bacher: > ...worth reporting upstream ... I would, but I am not allowed to: https://gitlab.gnome.org/users/sign_in "Please note that due to spam, new user registrations are disabled. Please use 3rd party logins for logging in if you don't have an existing account." Where would I find a 3rd party who would be willing to sign in for me? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1897281 Title: evince suicides in 20.04 but not in 18.04 Status in evince package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Evince does a suicide trip after unsuccessfully trying to open a CBR file. After a while it is killed. Here is my terminal output: $ evince TheCartoons.cbr Killed $ And between the line "$ evince TheCartoons.cbr" and the final "Killed", are passing many minutes. Please note that I started my report in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060 not knowing exactly what "expired" there means. I did "apport-collect 1785060" there, too. Please note also that my error message (see above) is quite different from seb128 in bug 1785060. In fact, there is no error message just the statement "Killed". What gets me is that in 18.04 it is working so smooth and fast and that in 20.04 it is such a mess! P.S. I do not know whether this helps, but with Debian 11 Xfce (Buster sid, testing), evince loads and opens this CBR file correctly, albeit slowly, but okular (installed in Buster sid) yields a similar error message like that of seb128 with evince in bug 1785060: "Could not open file TheCartoons.cbr. The version of unrar on your system is not suitable for opening comicbooks" Inverted world ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897281/+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 1899675] Re: Desktop background image is corrupted after suspend
** Package changed: nautilus (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/1899675 Title: Desktop background image is corrupted after suspend Status in gnome-shell package in Ubuntu: New Bug description: Immediately after resuming from suspend, any desktop background image is corrupted. Expected desktop image to be shown as set in Settings > Background. Notes: * Happens since day 0 of installation. * Does not happen after restart; only after suspend mode. Details: Description: Ubuntu 20.04.1 LTS Release: 20.04 possible alternate application: Gnome-control-center nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899675/+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 1848731] Re: Audio output device changes upon unlock/login
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Ubuntu needs a lock feature in the gnome sound settings, because each time a device is detected the output/input will change automatically. Sometimes this feature is wanted (I plug-in a headphone) sometimes it's not (I don't want the sound output to switch to my monitor when I power it since no speakers are plugged to it) -- 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/1848731 Title: Audio output device changes upon unlock/login Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a ThinkPad X250 and updated To Ubuntu 19.10 today from 19.04. Locking/Suspending and logging in changes my audio output device. This did not happen in 19.04. How to reproduce When I lock my session with key combination "Win+L" and then unlock it again, the sound that's been playing through my headphones/speakers stops playing. When I check the audio settings, "HDMI/DisplayPort 2 - Built-in audio" is selected. When I select "Headphones - Built-in audio", sound continues playing. There is no related log output in dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848731/+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 1899473] Re: gpg migration is stuck (gpg running at 100%)
Not sure if it's the same setup, but I'm getting it stuck at times when
running gpg inside a groovy schroot of a focal host, although might be
unrelated.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1899473
Title:
gpg migration is stuck (gpg running at 100%)
Status in thunderbird package in Ubuntu:
New
Bug description:
after the focal to groovy update, the gpg migration is stuck, no progress,
and gpg running at 100%.
---
ProblemType: Bug
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: doko 8824 F pulseaudio
/dev/snd/controlC1: doko 8824 F pulseaudio
BuildID: 20201006011220
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.10
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@thunderbird.mozilla.org
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-01-12 (638 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
IpRoute:
default via 192.168.178.1 dev enp0s31f6 proto dhcp metric 100
169.254.0.0/16 dev enp0s31f6 scope link metric 1000
192.168.178.0/24 dev enp0s31f6 proto kernel scope link src 192.168.178.21
metric 100
MostRecentCrashID: bp-5c7565c6-7621-45b3-a192-3dcee0180531
NonfreeKernelModules: nvidia_modeset nvidia
Package: thunderbird 1:78.3.2+build1-0ubuntu1
PackageArchitecture: amd64
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:732
PrefSources: prefs.js
ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
Profiles: Profile0 (Default) - LastVersion=78.3.2/20201006011220 (In use)
RunningIncompatibleAddons: True
Tags: groovy
Uname: Linux 5.8.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
_MarkForUpload: True
dmi.bios.date: 10/28/2019
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: N2EET43W (1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrN2EET43W(1.25):bd10/28/2019:br1.25:efr1.13:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme
dmi.product.name: 20MFCTO1WW
dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
dmi.product.version: ThinkPad X1 Extreme
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899473/+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 1897553] Re: [ALPS i2c Touchpads] Palm detect pressure is too easy to trigger so that the cursor stalled
This bug was fixed in the package libinput - 1.15.5-1ubuntu0.1 --- libinput (1.15.5-1ubuntu0.1) focal; urgency=medium * quirks: Customize ALPS i2c touchpad palm detect pressure threshold (LP: #1897553) -- Kai-Chuan Hsieh Mon, 28 Sep 2020 18:29:24 +0800 ** Changed in: libinput (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1897553 Title: [ALPS i2c Touchpads] Palm detect pressure is too easy to trigger so that the cursor stalled Status in OEM Priority Project: Fix Committed Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Focal: Fix Released Bug description: [Impact] * ALPS new i2c touchpads have capabilities for reporting ABS_PRESSURE and ABS_MT_PRESSURE event, However, it is very easy to over the default palm detect by pressure threshold 130. When the threshold is achieved, the cursor will be stalled, and not be able to keep following the finger's movement. [Test Case] * For touchpad vid 0488, and have pressure capabilities. The pressure capability can be easily obtain by evtest tool, there should be ABS_PRESSURE and ABS_MT_PRESSURE event in ABS event type. Test step: Install libinput-tools 1. $ sudo apt install libinput-tools 2. $ sudo libinput measure touchpad-pressure 3. Generally move the finger, the pressure max should not exceed the palm pressure detect threshold [Regression Potential] * It only impacts ALPS i2c models * It won't impact the touchpad without capability to report pressure event. * For those touchpad with pressure capability will make the palm detect pressure be less sensitive. However, ALPS said its firmware can support firmware labeling palm detection, so it is okay that the palm detect pressure become less sensitive. [Other Info] * The upstream commit has merged https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/505 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1897553/+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 1899675] [NEW] Desktop background image is corrupted after suspend
Public bug reported: Immediately after resuming from suspend, any desktop background image is corrupted. Expected desktop image to be shown as set in Settings > Background. Notes: * Happens since day 0 of installation. * Does not happen after restart; only after suspend mode. Details: Description:Ubuntu 20.04.1 LTS Release:20.04 possible alternate application: Gnome-control-center nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: background desktop image ** Attachment added: "Desktop after resume" https://bugs.launchpad.net/bugs/1899675/+attachment/5421793/+files/bug-background-after-return-from-sleep.png -- 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/1899675 Title: Desktop background image is corrupted after suspend Status in nautilus package in Ubuntu: New Bug description: Immediately after resuming from suspend, any desktop background image is corrupted. Expected desktop image to be shown as set in Settings > Background. Notes: * Happens since day 0 of installation. * Does not happen after restart; only after suspend mode. Details: Description: Ubuntu 20.04.1 LTS Release: 20.04 possible alternate application: Gnome-control-center nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages gnome-control-center: Installed: 1:3.36.4-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: *** 1:3.36.4-0ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://il.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1899675/+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 1899673] Re: gdm 3.38 with nvidia drivers breaks Wayland support (once nvidia drivers are disabled)
Upstream issue: https://gitlab.gnome.org/GNOME/gdm/-/issues/641 ** Also affects: gdm via https://gitlab.gnome.org/GNOME/gdm/-/issues/641 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1899673 Title: gdm 3.38 with nvidia drivers breaks Wayland support (once nvidia drivers are disabled) Status in gdm: Unknown Status in gdm3 package in Ubuntu: In Progress Bug description: In a groovy setup - Install nvidia drivers - Restart your session - Uninstall nvidia drivers - Go back to gdm and try to login with "Wayland". No ubuntu wayland session will be shown as available and the /etc/gdm3/custom.conf file will just contain: [daemon] WaylandEnabled=false To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1899673/+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 1899673] [NEW] gdm 3.38 with nvidia drivers breaks Wayland support (once nvidia drivers are disabled)
Public bug reported: In a groovy setup - Install nvidia drivers - Restart your session - Uninstall nvidia drivers - Go back to gdm and try to login with "Wayland". No ubuntu wayland session will be shown as available and the /etc/gdm3/custom.conf file will just contain: [daemon] WaylandEnabled=false ** Affects: gdm Importance: Unknown Status: Unknown ** Affects: gdm3 (Ubuntu) Importance: Critical Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Tags: groovy ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #641 https://gitlab.gnome.org/GNOME/gdm/-/issues/641 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1899673 Title: gdm 3.38 with nvidia drivers breaks Wayland support (once nvidia drivers are disabled) Status in gdm: Unknown Status in gdm3 package in Ubuntu: In Progress Bug description: In a groovy setup - Install nvidia drivers - Restart your session - Uninstall nvidia drivers - Go back to gdm and try to login with "Wayland". No ubuntu wayland session will be shown as available and the /etc/gdm3/custom.conf file will just contain: [daemon] WaylandEnabled=false To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1899673/+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 1899667] Re: LO can't send email, probably an apparmour problem
[] audit: type=1400 audit(): apparmor="DENIED" operation="file_inherit"
profile="libreoffice-senddoc" name="x" pid=8106 comm="senddoc"
requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[] audit: type=1400 audit(): apparmor="DENIED" operation="exec" profile
="libreoffice-senddoc" name="/usr/bin/kmail" pid=8116 comm="senddoc"
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
cat /etc/apparmor.d/usr.lib.libreoffice.program.senddoc
#include
profile libreoffice-senddoc /usr/lib/libreoffice/program/senddoc {
#include
#include
/{usr/,}bin/shrmix,
/{usr/,}bin/bash rmix,
/{usr/,}bin/dash rmix,
/{usr/,}bin/sed rmix,
/usr/bin/dirname rmix,
/usr/bin/basename rmix,
/{usr/,}bin/grep rmix,
/{usr/,}bin/uname rmix,
/usr/bin/xdg-open rPUx,
/usr/bin/xdg-emailrPUx,
/dev/null rw,
/usr/lib/libreoffice/program/uri-encode rmpux,
/usr/share/libreoffice/share/config/* r,
owner @{HOME}/.config/libreoffice{,dev}/?/user/uno_packages/cache/log.txt rw,
}
** Also affects: kmail (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-release-upgrader (Ubuntu)
--
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/1899667
Title:
LO can't send email, probably an apparmour problem
Status in kmail package in Ubuntu:
New
Status in libreoffice package in Ubuntu:
New
Bug description:
LO can't send email:
LibreOffice was unable to find a working email configuration.
I'm pretty sure this is an apparmour profile problem since LO seems to
want RW perms on something and AA seems not to want to give it. There
lies the full extent on mu debugging expertise in this area.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Tue Oct 13 17:01:43 2020
InstallationDate: Installed on 2017-03-26 (1297 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to focal on 2020-10-08 (4 days ago)
VarLogDistupgradeXorgFixuplog:
INFO:root:/usr/bin/do-release-upgrade running
INFO:root:No xorg.conf, exiting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1899667/+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 1899479] Re: folders window in v78 has excessive vertical spacing
I can confirm what you observe. Upstream builds exhibit the same visual aspect though, so it seems it's an upstream design decision. Would you mind filing an upstream bug at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CThunderbird and sharing the link to it here? ** Summary changed: - folders window in v78 has excessive vertival spacing + folders window in v78 has excessive vertical spacing ** Summary changed: - folders window in v78 has excessive vertical spacing + folders pane in v78 has excessive vertical spacing ** Changed in: thunderbird (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1899479 Title: folders pane in v78 has excessive vertical spacing Status in thunderbird package in Ubuntu: Opinion Bug description: comparing the folders window between the versions in focal and groovy, the folders window has an excessive amount of vertical spacing. Is there a way to reset that to the previous settings? I see this as a regression, not seeing the amount of folders on the screen as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899479/+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 1899619] Re: [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds
Could you try reporting it upstream on https://gitlab.freedesktop.org/pulseaudio/pulseaudio/ ? Ubuntu doesn't have a dedicated maintainer for those components at the moment and it's not likely that will get traction on launchpad ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899619 Title: [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds Status in pulseaudio package in Ubuntu: New Bug description: Hello! I'm not really sure if is pulseaudio of bluez issue. Playback (from Gnome Settings sound test and Firefox), volume change, mute/resume is delayed for 2sec or bit more. I've verified this on two Ubuntu 20.04 laptops. To verify the AV receiver, I've paired MBP 2019 with OS X Catalina 10.15.7 and there are no audible delay. Here is sink information: * index: 16 name: driver: flags: HARDWARE DECIBEL_VOLUME LATENCY state: RUNNING suspend cause: (none) priority: 9550 volume: front-left: 46512 / 71% / -8,93 dB, front-right: 46512 / 71% / -8,93 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 56,81 ms max request: 4 KiB max rewind: 0 KiB monitor source: 18 sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 1 linked by: 4 fixed latency: 48,22 ms card: 17 module: 45 properties: bluetooth.protocol = "a2dp_sink" device.description = "Denon AVR-S650H" device.string = "00:05:CD:DF:C4:DD" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "speaker" bluez.path = "/org/bluez/hci0/dev_00_05_CD_DF_C4_DD" bluez.class = "0x240414" bluez.alias = "Denon AVR-S650H" device.icon_name = "audio-speakers-bluetooth" ports: speaker-output: Speaker (priority 0, latency offset 0 usec, available: yes) properties: active port: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.5-050805-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bogdan82720 F pulseaudio /dev/snd/controlC1: bogdan82720 F pulseaudio /dev/snd/controlC0: bogdan82720 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 13 13:46:35 2020 InstallationDate: Installed on 2020-08-05 (68 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Denon AVR-S650H Symptom_Type: None of the above Title: [Denon AVR-S650H, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 2.1 dmi.bios.vendor: HP dmi.bios.version: S79 Ver. 01.02.01 dmi.board.name: 8730 dmi.board.vendor: HP dmi.board.version: KBC Version 13.1C.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 19.28 dmi.modalias: dmi:bvnHP:bvrS79Ver.01.02.01:bd07/02/2020:br2.1:efr19.28:svnHP:pnHPProBook455G7:pvr:rvnHP:rn8730:rvrKBCVersion13.1C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 455 G7 dmi.product.sku: 2D242EA#ACB dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899619/+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 1881943] Re: [Inspiron 5391, Realtek ALC3204] Sound stopped to work, "error : DSP panic!" in dmesg
Seems to be fixed in sof v.1.6: https://github.com/thesofproject/sof/issues/2828 Can you add new SOF to linux-firmware? ** Bug watch added: github.com/thesofproject/sof/issues #2828 https://github.com/thesofproject/sof/issues/2828 ** Package changed: alsa-driver (Ubuntu) => linux-firmware (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/1881943 Title: [Inspiron 5391, Realtek ALC3204] Sound stopped to work, "error : DSP panic!" in dmesg Status in linux-firmware package in Ubuntu: New Bug description: Sound worked, but accidentally stopped to work at all. Just before it I had plugged and unplugged HDMI display (but without sound via HDMI). Only restart helped. Here is dmesg output while the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 4612 F pulseaudio /dev/snd/pcmC0D0p: username 4612 F...m pulseaudio /dev/snd/pcmC0D6c: username 4612 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Jun 3 20:42:33 2020 InstallationDate: Installed on 2020-05-28 (5 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: июн 03 20:04:56 username-5391 dbus-daemon[3386]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=114 pid=4302 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") июн 03 20:04:59 username-5391 systemd[4295]: pulseaudio.service: Succeeded. июн 03 20:05:09 username-5391 systemd[4295]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5391, Realtek ALC3204, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 07DM2C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/21/2019:svnDellInc.:pnInspiron5391:pvr:rvnDellInc.:rn07DM2C:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5391 dmi.product.sku: 096E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1881943/+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 1899603] Re: Can't upgrade on Manjaro 20.1.1
Thank you but Manjaro isn't an Ubuntu version, you should report the issue to the distribution you are using ** Changed in: fontconfig (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1899603 Title: Can't upgrade on Manjaro 20.1.1 Status in fontconfig package in Ubuntu: Invalid Bug description: Ubuntu release: Manjaro 20.1.1 using KDE+Plasma installed package version: fontconfig-ubuntu 2.13.0-2 What you expected to happen: It upgraded successfully to 2.13.1-1. What happens: It fails one of the tests during the build(when using the UI package manager) Output from build is attached in a file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1899603/+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 1899329] Re: symbol U+240e seems to misrepresent the `Shift Out' character by `SS' instead of `SO'
Thank yoi for your bug report, the issue is probably rather one with the font than one from the browser utility ** Package changed: gucharmap (Ubuntu) => fonts-freefont (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-freefont in Ubuntu. https://bugs.launchpad.net/bugs/1899329 Title: symbol U+240e seems to misrepresent the `Shift Out' character by `SS' instead of `SO' Status in fonts-freefont package in Ubuntu: New Bug description: Hallo, A similar bug has been described (and repaired) earlier. See https://bugs.launchpad.net/ubuntu/+source/fonts-freefont/+bug/1070669. I first encountered this typographical error on the website of Wikipedia (using the Firefox web browser) https://en.wikipedia.org/wiki/C0_and_C1_control_codes when looking at the table representing ASCII control characters. U+240e ␎ Shift Out should probably be represented by `SO' and not `SS'. See for reference (as in the report referred to above) the following document on the Unicode website http://www.unicode.org/charts/PDF/U2400.pdf. This typographical error also seems to appear in other programs such as Libre Office Calc, the xfc4-terminal, chromium-browser. I am guessing it is visible in most, and possibly in all programs. Kind regards, Michael ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gucharmap 1:10.0.4-1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Oct 11 10:55:22 2020 InstallationDate: Installed on 2019-02-17 (601 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gucharmap UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-freefont/+bug/1899329/+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 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
This bug was fixed in the package ubuntu-drivers-common - 1:0.8.6 --- ubuntu-drivers-common (1:0.8.6) groovy; urgency=medium [ Alberto Milone ] * share/hybrid/json-parser, debian/copyright: - Include json-parser (just C file and header). * gpu-manager.c: - Add json parsing code to detect support for runtimepm on NVIDIA (LP: #1895855). - Check that RTD3 is enabled, and write that to a file in /run. - Make on-demand mode the default when no settings are available. - Add support for AMD+NVIDIA hybrid systems. - Add support for checking PME capabilities for runtimepm, so that, if the GPU is not boot_vga, and it is not listed in the json database, we can at least check whether d3hot is supported, and enable runtimepm in the NVIDIA driver. * gpu-manager.py: - Adjust the test suite to match the changes in gpu-manager.c. * UbuntuDrivers/detect.py, ubuntu-drivers: - Catch apt exceptions. - Catch failure when modinfo is not available. - Introduce the concept of LTSB (long term support branch), NFB (new feature branch), Legacy, and Beta, which the driver packages can specify. - Use package support to pick the nvidia driver: o Desktop case: pick the latest non-server driver, when available (this preserves the current behaviour). o Server case: pick the LTSB -server driver, when available. * NvidiaDetector/nvidiadetector.py: - Use regex to parse package names (LP: #1891183). * ubuntu-drivers: - Select on-demand mode if runtimepm is supported. - Check RTD3 support for NVIDIA, and enable it when available. - Show the package support level, when available, when using "ubuntu-drivers debug". * debian/control: - Replace build-dep on libpciaccess-dev with libpci-dev. * debian/rules: make sure to call the clean target of the Makefile [ Cyrus Lien ] * gpu-manager.c: - Fix segmentation fault in json_find_feature_in_array. -- Alberto Milone Mon, 12 Oct 2020 16:00:18 +0200 ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) Status in OEM Priority Project: New Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: The work that went into ubuntu-drivers-common and nvidia-prime is meant to enable RTD3 support on Intel/NVIDIA or AMD/NVIDIA hybrid systems, introduced by the NVIDIA 450 driver series. This allows the supported systems to make use of the integrated GPU (Intel or AMD) and to keep the discrete NVIDIA GPU powered down until needed. While powered down, the NVIDIA GPU can still detect any events, should external displays be plugged in. This brings hybrid graphics on Linux on par with Windows. Only the supported GPUs will be able to benefit from this change. This is why NVIDIA provides a hardware database (included in the nvidia packages), which gpu-manager can now parse. The ubuntu-drivers tool relies on that detection to enable this new feature when installing the NVIDIA driver. Another improvement is the ability of ubuntu-drivers to detect LTSB (Long term support branch), NFB (New feature branch), Legacy, Beta flags, which the NVIDIA drivers can have, and make informed detection choices. This work also includes a number of bug fixes reported on errors.ubuntu.com. Requirements: The new ubuntu-drivers-common: The new nvidia-prime: Changes to the NVIDIA drivers: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+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 1891183] Re: the new -server drivers break nvidia-detector
This bug was fixed in the package ubuntu-drivers-common - 1:0.8.6 --- ubuntu-drivers-common (1:0.8.6) groovy; urgency=medium [ Alberto Milone ] * share/hybrid/json-parser, debian/copyright: - Include json-parser (just C file and header). * gpu-manager.c: - Add json parsing code to detect support for runtimepm on NVIDIA (LP: #1895855). - Check that RTD3 is enabled, and write that to a file in /run. - Make on-demand mode the default when no settings are available. - Add support for AMD+NVIDIA hybrid systems. - Add support for checking PME capabilities for runtimepm, so that, if the GPU is not boot_vga, and it is not listed in the json database, we can at least check whether d3hot is supported, and enable runtimepm in the NVIDIA driver. * gpu-manager.py: - Adjust the test suite to match the changes in gpu-manager.c. * UbuntuDrivers/detect.py, ubuntu-drivers: - Catch apt exceptions. - Catch failure when modinfo is not available. - Introduce the concept of LTSB (long term support branch), NFB (new feature branch), Legacy, and Beta, which the driver packages can specify. - Use package support to pick the nvidia driver: o Desktop case: pick the latest non-server driver, when available (this preserves the current behaviour). o Server case: pick the LTSB -server driver, when available. * NvidiaDetector/nvidiadetector.py: - Use regex to parse package names (LP: #1891183). * ubuntu-drivers: - Select on-demand mode if runtimepm is supported. - Check RTD3 support for NVIDIA, and enable it when available. - Show the package support level, when available, when using "ubuntu-drivers debug". * debian/control: - Replace build-dep on libpciaccess-dev with libpci-dev. * debian/rules: make sure to call the clean target of the Makefile [ Cyrus Lien ] * gpu-manager.c: - Fix segmentation fault in json_find_feature_in_array. -- Alberto Milone Mon, 12 Oct 2020 16:00:18 +0200 ** Changed in: ubuntu-drivers-common (Ubuntu) Status: In Progress => Fix Released -- 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/1891183 Title: the new -server drivers break nvidia-detector Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Bug description: Calling nvidia-detector, fails when the new -server series are available in the archive: nvidia-detector Traceback (most recent call last): File "/usr/bin/nvidia-detector", line 8, in a = NvidiaDetection(printonly=True, verbose=False) File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 73, in __init__ self.getData() File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 163, in getData driver_version = self.__get_value_from_name(stripped_package_name) File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 92, in __get_value_from_name v = int(name) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1891183/+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 1878553] Re: Ubuntu could not install Virtualbox Guest addons
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1878553 ** Tags added: iso-testing -- 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/1878553 Title: Ubuntu could not install Virtualbox Guest addons Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-drivers-common source package in Groovy: Confirmed Bug description: It seems that Ubuntu is not able to install the VirtualBox Guest add- ons even Ubuntu is able to detect it. See Attachement. Ubuntu 20.04 Basic install after Reboot, Update and Reboot again. Similar Tickets in Launchpad but really old: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1878553/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Changed in: gdm3 (Ubuntu Groovy) Importance: Medium => High ** Also affects: pam (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pam (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Focal) Status: New => Confirmed ** Changed in: gdm3 (Ubuntu Focal) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in gdm3 package in Ubuntu: Confirmed Status in pam package in Ubuntu: Invalid Status in gdm3 source package in Bionic: New Status in pam source package in Bionic: New Status in gdm3 source package in Focal: Confirmed Status in pam source package in Focal: New Status in gdm3 source package in Groovy: Confirmed Status in pam source package in Groovy: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+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 1899473] Re: gpg migration is stuck (gpg running at 100%)
I've tested the GPG import wizard a few times, including doing a full
dist upgrade from focal to groovy in a VM, and have never seen it stuck
as described.
Let's keep the bug open and see if others hit it and can provide further
insights to help reproduce.
** Changed in: thunderbird (Ubuntu)
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1899473
Title:
gpg migration is stuck (gpg running at 100%)
Status in thunderbird package in Ubuntu:
New
Bug description:
after the focal to groovy update, the gpg migration is stuck, no progress,
and gpg running at 100%.
---
ProblemType: Bug
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: doko 8824 F pulseaudio
/dev/snd/controlC1: doko 8824 F pulseaudio
BuildID: 20201006011220
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.10
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@thunderbird.mozilla.org
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-01-12 (638 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
IpRoute:
default via 192.168.178.1 dev enp0s31f6 proto dhcp metric 100
169.254.0.0/16 dev enp0s31f6 scope link metric 1000
192.168.178.0/24 dev enp0s31f6 proto kernel scope link src 192.168.178.21
metric 100
MostRecentCrashID: bp-5c7565c6-7621-45b3-a192-3dcee0180531
NonfreeKernelModules: nvidia_modeset nvidia
Package: thunderbird 1:78.3.2+build1-0ubuntu1
PackageArchitecture: amd64
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:732
PrefSources: prefs.js
ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
Profiles: Profile0 (Default) - LastVersion=78.3.2/20201006011220 (In use)
RunningIncompatibleAddons: True
Tags: groovy
Uname: Linux 5.8.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
_MarkForUpload: True
dmi.bios.date: 10/28/2019
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: N2EET43W (1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrN2EET43W(1.25):bd10/28/2019:br1.25:efr1.13:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme
dmi.product.name: 20MFCTO1WW
dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
dmi.product.version: ThinkPad X1 Extreme
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899473/+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 1894417] Re: Firefox opens window with false size
Thanks for the report Matthias.
Given that this hasn't happened again, I'll mark the bug incomplete to let it
auto-expire in 60 days. If the problem happens again in the meantime, please
comment here and we can look into it.
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
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/1894417
Title:
Firefox opens window with false size
Status in firefox package in Ubuntu:
Incomplete
Bug description:
Happens only the first time after a restart. See picture.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 80.0.1+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
Uname: Linux 5.4.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matthias 1278 F pulseaudio
/dev/snd/controlC0: matthias 1278 F pulseaudio
BrokenPermissions:
gmp-gmpopenh264/1.5.3/gmpopenh264.info (0o500)
gmp-gmpopenh264/1.5.3/libgmpopenh264.so (0o500)
BuildID: 20200831163820
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 6 07:24:38 2020
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IncompatibleExtensions:
FRITZ!Box AddOn - fb_add...@avm.de
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-05-23 (105 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 192.168.178.1 dev enp3s0 proto dhcp metric 100
169.254.0.0/16 dev enp3s0 scope link metric 1000
192.168.178.0/24 dev enp3s0 proto kernel scope link src 192.168.178.20
metric 100
MostRecentCrashID: bp-775fc658-fb84-423c-af9e-7a35a2160612
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:730
PrefSources: prefs.js
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=80.0.1/20200831163820 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs:
bp-775fc658-fb84-423c-af9e-7a35a2160612
bp-82bd88c5-a3c2-4400-ac13-bdf4e2150528
bp-a636b6f6-8af2-4f53-a0c0-7e2ec2150217
bp-998ce658-7a0f-4cc6-bbac-9193b2140828
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11a
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77-DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF11a:bd11/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1894417/+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 1892486] Re: gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from cc_sound_panel_init
@Daniel, we use the rls-nn-incoming tag for issues we beliece are important enough to be rls targetted, as you said that one is low priority and not going to impact a normal session so doesn't qualify, tagging rls-ff-notfixing ** Tags removed: rls-ff-incoming ** Tags added: rls-ff-notfixing -- 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/1892486 Title: gnome-control-center crashed with SIGSEGV in strstr(NULL, "ubuntu") from cc_sound_panel_init Status in gnome-control-center package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/504c7e1b5a27636a5f560077df098c1a64b7c170 --- Not sure yet. Wait for the retrace. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 21 18:19:17 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-07-16 (36 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f8657e0f611 <__strstr_sse2_unaligned+81>: movdqu (%rdi),%xmm3 PC (0x7f8657e0f611) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm3" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV 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/ubuntu/+source/gnome-control-center/+bug/1892486/+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 1899473] Re: gpg migration is stuck (gpg running at 100%)
Thanks, setting as rls-ff-notfixing since we don't even have the 78
serie on focal yet. Also assigning to Olivier who said would have a look
for the Groovy serie (but we don't believe it's a rls issue at this
point since there was only one report so far)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1899473
Title:
gpg migration is stuck (gpg running at 100%)
Status in thunderbird package in Ubuntu:
New
Bug description:
after the focal to groovy update, the gpg migration is stuck, no progress,
and gpg running at 100%.
---
ProblemType: Bug
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: doko 8824 F pulseaudio
/dev/snd/controlC1: doko 8824 F pulseaudio
BuildID: 20201006011220
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.10
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@thunderbird.mozilla.org
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-01-12 (638 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
IpRoute:
default via 192.168.178.1 dev enp0s31f6 proto dhcp metric 100
169.254.0.0/16 dev enp0s31f6 scope link metric 1000
192.168.178.0/24 dev enp0s31f6 proto kernel scope link src 192.168.178.21
metric 100
MostRecentCrashID: bp-5c7565c6-7621-45b3-a192-3dcee0180531
NonfreeKernelModules: nvidia_modeset nvidia
Package: thunderbird 1:78.3.2+build1-0ubuntu1
PackageArchitecture: amd64
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:732
PrefSources: prefs.js
ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
Profiles: Profile0 (Default) - LastVersion=78.3.2/20201006011220 (In use)
RunningIncompatibleAddons: True
Tags: groovy
Uname: Linux 5.8.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
_MarkForUpload: True
dmi.bios.date: 10/28/2019
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: N2EET43W (1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrN2EET43W(1.25):bd10/28/2019:br1.25:efr1.13:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme
dmi.product.name: 20MFCTO1WW
dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
dmi.product.version: ThinkPad X1 Extreme
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899473/+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 1899645] [NEW] It's not possible to enable the VMware SVGA II Adapter after installation from UI
Public bug reported: I've installed ubuntu groovy in a VMware machine without selecting the easy install mode, and without requesting to install drivers automatically during setup. Once logged in, I tried to install the vmware drivers from software updates, but this is not enabled: https://i.imgur.com/MyESY7P.png If I launch `sudo ubuntu-drivers install` from a terminal, the drivers gets correctly installed (and working) instead (and UI adapts things well afterwards https://i.imgur.com/BLMk5Og.png): $ sudo ubuntu-drivers install [sudo] password for marco: Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools zerofree Suggested packages: cloud-init The following NEW packages will be installed: ethtool libmspack0 libxmlsec1-openssl net-tools open-vm-tools open-vm-tools-desktop zerofree 0 upgraded, 7 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/1.191 kB of archives. After this operation, 4.849 kB of additional disk space will be used. Selecting previously unselected package ethtool. (Reading database ... 146927 files and directories currently installed.) Preparing to unpack .../0-ethtool_1%3a5.8-1_amd64.deb ... Unpacking ethtool (1:5.8-1) ... Selecting previously unselected package libmspack0:amd64. Preparing to unpack .../1-libmspack0_0.10.1-2_amd64.deb ... Unpacking libmspack0:amd64 (0.10.1-2) ... Selecting previously unselected package libxmlsec1-openssl:amd64. Preparing to unpack .../2-libxmlsec1-openssl_1.2.28-2_amd64.deb ... Unpacking libxmlsec1-openssl:amd64 (1.2.28-2) ... Selecting previously unselected package net-tools. Preparing to unpack .../3-net-tools_1.60+git20180626.aebd88e-1ubuntu2_amd64.deb ... Unpacking net-tools (1.60+git20180626.aebd88e-1ubuntu2) ... Selecting previously unselected package open-vm-tools. Preparing to unpack .../4-open-vm-tools_2%3a11.1.5-1ubuntu1_amd64.deb ... Unpacking open-vm-tools (2:11.1.5-1ubuntu1) ... Selecting previously unselected package open-vm-tools-desktop. Preparing to unpack .../5-open-vm-tools-desktop_2%3a11.1.5-1ubuntu1_amd64.deb ... Unpacking open-vm-tools-desktop (2:11.1.5-1ubuntu1) ... Selecting previously unselected package zerofree. Preparing to unpack .../6-zerofree_1.1.1-1build1_amd64.deb ... Unpacking zerofree (1.1.1-1build1) ... Setting up zerofree (1.1.1-1build1) ... Setting up net-tools (1.60+git20180626.aebd88e-1ubuntu2) ... Setting up libxmlsec1-openssl:amd64 (1.2.28-2) ... Setting up libmspack0:amd64 (0.10.1-2) ... Setting up open-vm-tools (2:11.1.5-1ubuntu1) ... Failed to restart open-vm-tools.service: Unit vgauth.service is masked. Setting up ethtool (1:5.8-1) ... Setting up open-vm-tools-desktop (2:11.1.5-1ubuntu1) ... Processing triggers for libc-bin (2.32-0ubuntu3) ... Processing triggers for systemd (246.6-1ubuntu1) ... Processing triggers for man-db (2.9.3-2) ... marco@marco-virtual-machine:~$ $ ubuntu-drivers devices == /sys/devices/pci:00/:00:0f.0 == modalias : pci:v15ADd0405sv15ADsd0405bc03sc00i00 vendor : VMware model: SVGA II Adapter driver : open-vm-tools-desktop - distro free So, ProblemType: BugDistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 15:19:54 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: allSourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) Update: once installed, if you select "Do not use the device", then close "Software & updates" and open it again, it will be in broken state again, so it should be easy to test. ** Affects: software-properties (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1899645 Title: It's not possible to enable the VMware SVGA II Adapter after installation from UI Status in software-properties package in Ubuntu: New Bug description: I've installed ubuntu groovy in a VMware machine without selecting the easy install mode, and without requesting to install drivers automatically during setup. Once logged in, I tried to install the vmware drivers from software updates, but this is not enabled: https://i.imgur.com/MyESY7P.png If I launch `sudo ubuntu-drivers install` from a terminal, the drivers gets correctly installed (and working) instead (and UI adapts things well afterwards https://i.imgur.com/BLMk5Og.png): $ sudo ubuntu-drivers install
[Desktop-packages] [Bug 1899473] Re: gpg migration is stuck (gpg running at 100%)
** Tags removed: rls-ff-incoming
** Tags added: rls-ff-notfixing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1899473
Title:
gpg migration is stuck (gpg running at 100%)
Status in thunderbird package in Ubuntu:
New
Bug description:
after the focal to groovy update, the gpg migration is stuck, no progress,
and gpg running at 100%.
---
ProblemType: Bug
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: doko 8824 F pulseaudio
/dev/snd/controlC1: doko 8824 F pulseaudio
BuildID: 20201006011220
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.10
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@thunderbird.mozilla.org
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-01-12 (638 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
IpRoute:
default via 192.168.178.1 dev enp0s31f6 proto dhcp metric 100
169.254.0.0/16 dev enp0s31f6 scope link metric 1000
192.168.178.0/24 dev enp0s31f6 proto kernel scope link src 192.168.178.21
metric 100
MostRecentCrashID: bp-5c7565c6-7621-45b3-a192-3dcee0180531
NonfreeKernelModules: nvidia_modeset nvidia
Package: thunderbird 1:78.3.2+build1-0ubuntu1
PackageArchitecture: amd64
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:732
PrefSources: prefs.js
ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
Profiles: Profile0 (Default) - LastVersion=78.3.2/20201006011220 (In use)
RunningIncompatibleAddons: True
Tags: groovy
Uname: Linux 5.8.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
_MarkForUpload: True
dmi.bios.date: 10/28/2019
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: N2EET43W (1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrN2EET43W(1.25):bd10/28/2019:br1.25:efr1.13:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme
dmi.product.name: 20MFCTO1WW
dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
dmi.product.version: ThinkPad X1 Extreme
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899473/+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 1880508] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
*** This bug is a duplicate of bug 1768499 *** https://bugs.launchpad.net/bugs/1768499 ** This bug has been marked a duplicate of bug 1768499 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1880508 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Status in nvidia-graphics-drivers-440 source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Groovy: Confirmed Status in nvidia-graphics-drivers-440 source package in Groovy: Confirmed Bug description: I can not connect my MackBook Pro to monitor and I need some feedback ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) 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 Date: Mon May 25 08:10:28 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-05-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1880508/+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 1889974] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
*** This bug is a duplicate of bug 1768499 *** https://bugs.launchpad.net/bugs/1768499 ** This bug is no longer a duplicate of bug 1880508 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ** This bug has been marked a duplicate of bug 1768499 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1889974 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Kernel doesn't have any module available to install this driver. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) Uname: Linux 5.7.0-050700-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jul 31 22:55:29 2020 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 InstallationDate: Installed on 2020-07-31 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1889974/+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 1884404] Re: package nvidia-340 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-
*** This bug is a duplicate of bug 1768499 *** https://bugs.launchpad.net/bugs/1768499 ** This bug is no longer a duplicate of bug 1880508 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ** This bug has been marked a duplicate of bug 1768499 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1884404 Title: package nvidia-340 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: startx don't came up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) 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 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 20 23:36:09 2020 ErrorMessage: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-06-21 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: a tentar sobre-escrever '/lib/udev/rules.d/71-nvidia.rules', que também está no pacote nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1884404/+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 1865577] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
*** This bug is a duplicate of bug 1768499 *** https://bugs.launchpad.net/bugs/1768499 ** This bug is no longer a duplicate of bug 1880508 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ** This bug has been marked a duplicate of bug 1768499 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1865577 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: While updating my system running Focal (20.04), my nvidia drivers are not working and now I cannot install the updates (ubuntu-drivers autoinstall). I tried to purge everything installed and named nvidia and after autoinstalling the correct driver for my system. Thanks for helping out. 1) aurion@w540:~$ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2) aurion@w540:~$ apt-cache policy nvidia-340 nvidia-340: Installed: (none) Candidate: 340.108-0ubuntu2 Version table: 340.108-0ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 3) I would like to be able to install this version of nvidia driver since I have a dockstation and I use the thunderbolt connection for my external monitor 4) I got an error message that the script could not install the drivers. I also had a look into the synaptic additional drivers and the nvidia is selected as installed. However the rendering of my screen is very slow and when I switch to another screen, I can see the window been reloaded. Also I am unable to connect my external monitor via thunderbolt. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Sun Mar 1 21:36:20 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.12 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.59-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1865577/+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 1896129] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
*** This bug is a duplicate of bug 1768499 *** https://bugs.launchpad.net/bugs/1768499 ** This bug is no longer a duplicate of bug 1880508 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ** This bug has been marked a duplicate of bug 1768499 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1896129 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia -340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', whi ch is also in package nvidia-kernel-common-440 440.100-0ubunt u0.20.04.1 dpkg-deb: error: paste subprocess was killed by signal (Broke n pipe) Errors were encountered while processing: /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.de b E: Sub-process /usr/bin/dpkg returned an error code (1) I'm in ubuntu 20.04. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 17 14:14:06 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 InstallationDate: Installed on 2020-07-18 (61 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896129/+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 1887565] Re: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-k
*** This bug is a duplicate of bug 1768499 *** https://bugs.launchpad.net/bugs/1768499 ** This bug is no longer a duplicate of bug 1880508 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 ** This bug has been marked a duplicate of bug 1768499 package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1887565 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: no puedo descargar este tipo de driver, para instalar en un sistema de ryze, la tarjeta de video. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 14 13:27:04 2020 ErrorMessage: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 InstallationDate: Installed on 2020-07-08 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-440 440.100-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1887565/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I had the same issue (with both Ubuntu 20.04 and 20.10). It does seem to be resolved after installing a 5.9 Kernel with the above patch applied (from @coiby https://www.spinics.net/lists/linux-input/msg69458.html. I have scripted the process I used (download, patch, compile and install the kernel) for anyone else that's eager to get a working Touchpad on a Ubuntu 20 installation on Lenovo Legion 5 (Obviously there may be unwanted side effects of doing this). This will probably require Secure Boot to be disabled in the BIOS. See GitHub Gist here: https://gist.github.com/jbuncle/7dacde983b3c33b3b816b10e2fd2308a Command for convenience: `bash <(curl https://gist.githubusercontent.com/jbuncle/7dacde983b3c33b3b816b10e2fd2308a/raw/build-patched-kernel.sh)` Note the need for updating GRUB_CMDLINE_LINUX_DEFAULT with i2c- hid.polling_mode=1 (First time I've built the Linux Kernel myself or even commented on here!) Thanks to @Coiby Xu (coiby) -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A
[Desktop-packages] [Bug 1899630] Re: Nvidia driver is marked as "free" on first installation before "apt update"
** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1899630 Title: Nvidia driver is marked as "free" on first installation before "apt update" Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: This may be a duplicate of bug #1514057 (close it in case), but without any PPA and just after installing Ubuntu in a new partition. Followed this ISO testing script (so installed without connection): - http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/221687/testcases/1718/results Once installed, I noticed the nvidia driver was marked as "free": https://i.imgur.com/RTA1VmD.png More detailed report from ubuntu-drivers was: $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1C91sv103Csd8640bc03sc00i00 vendor : NVIDIA Corporation model: GP107M [GeForce GTX 1050 3 GB Max-Q] driver : nvidia-driver-450 - third-party free recommended driver : xserver-xorg-video-nouveau - distro free builtin Once I did an "apt update", this got fixed. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-drivers-common 1:0.8.5.4 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:26:55 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) SourcePackage: ubuntu-drivers-common 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/1899630/+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 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
I think this may be related to https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1371 I will look into this -- 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/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which seems to have been introduced within the past couple of weeks. I have a couple custom keyboard settings configured in Tweaktool "Additional Layout Options". These settings work great. I have a USB keyboard plugged into the machine. If I have the keyboard plugged in when I start my Gnome session, the customized keyboard layout options are correctly applied to the USB keyboard. If I unplug and reconnect the keyboard, the keyboard does will _NOT_ have the customized keyboard settings. If I restart my Gnome session (using Alt-F2 -> "r"), the customized settings are applied to the keyboard. I think this behavior is something new. Before, I was able to unplug/reconnect my keyboard and it would apply my customized keyboard settings on reconnect. Is there anything I can do to force the application of the custom keyboard tweaks on USB keyboard reconnect? Is anyone else able to reproduce this? I don't have any other machines with Ubuntu 20.04.1 to test with. Thanks! (This is also cross-posted at askubuntu: https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional- layout-options-not-working) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1899206/+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 1896919] Re: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c
** Changed in: oem-priority Status: Confirmed => Fix Committed -- 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/1896919 Title: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Committed Status in gnome-control-center source package in Groovy: Fix Released Bug description: [Impact] After we plugging a hdmi/dp monitor with audio capability, we could select hdmi audio as output device in the g-c-c, but after we do that, the profile combo list will show up in the g-c-c and this combo list is empty, it should be stereo-hdmi by default according to 18.04 [Fix] Backport a fix from g-c-c upstream, after applying this patch, the combo list update signals will be recevied after the pa finishes the changing active profile. [Test Case] Plug the hdmi/dp monitor with audio capability, then choose hdmi audio as active output device from g-c-c, we will find the profile combo list has hdmi-steoreo as the default profile. This is same as 18.04. [Regression Risk] It is possible to make the output and input device can't work after applying this patch, that is because the active profile is not set as our expected. But this possibility is very low, I tested this patch on 2 lenovo and 2 dell laptops, there is no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1896919/+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 1899473] Re: gpg migration is stuck (gpg running at 100%)
** Changed in: thunderbird (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1899473
Title:
gpg migration is stuck (gpg running at 100%)
Status in thunderbird package in Ubuntu:
New
Bug description:
after the focal to groovy update, the gpg migration is stuck, no progress,
and gpg running at 100%.
---
ProblemType: Bug
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: doko 8824 F pulseaudio
/dev/snd/controlC1: doko 8824 F pulseaudio
BuildID: 20201006011220
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.10
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@thunderbird.mozilla.org
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-01-12 (638 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
IpRoute:
default via 192.168.178.1 dev enp0s31f6 proto dhcp metric 100
169.254.0.0/16 dev enp0s31f6 scope link metric 1000
192.168.178.0/24 dev enp0s31f6 proto kernel scope link src 192.168.178.21
metric 100
MostRecentCrashID: bp-5c7565c6-7621-45b3-a192-3dcee0180531
NonfreeKernelModules: nvidia_modeset nvidia
Package: thunderbird 1:78.3.2+build1-0ubuntu1
PackageArchitecture: amd64
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:732
PrefSources: prefs.js
ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
Profiles: Profile0 (Default) - LastVersion=78.3.2/20201006011220 (In use)
RunningIncompatibleAddons: True
Tags: groovy
Uname: Linux 5.8.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
_MarkForUpload: True
dmi.bios.date: 10/28/2019
dmi.bios.release: 1.25
dmi.bios.vendor: LENOVO
dmi.bios.version: N2EET43W (1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrN2EET43W(1.25):bd10/28/2019:br1.25:efr1.13:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme
dmi.product.name: 20MFCTO1WW
dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
dmi.product.version: ThinkPad X1 Extreme
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899473/+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 1899456] Re: [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu)
** Changed in: libreoffice (Ubuntu) Status: Triaged => Fix Committed -- 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/1899456 Title: [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu) Status in libreoffice package in Ubuntu: Fix Committed Bug description: The yaru icon style is explicitly shipped within the ubuntu source package of libreoffice. libreoffice 7.0.2~rc2-0ubuntu1 includes yaru icon style "2020-09-28" The final libreoffice 7.0.2-0ubuntu1 is meant to include "2020-10-11" Upstream changes: https://github.com/ubuntu/libreoffice-style-yaru- fullcolor/compare/2020-09-28...2020-10-11 Most noticeable visual changes: * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/105 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/121 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/125 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/141 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1899456/+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 1899630] Re: Nvidia driver is marked as "free" on first installation before "apt update"
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1899630 ** Tags added: iso-testing -- 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/1899630 Title: Nvidia driver is marked as "free" on first installation before "apt update" Status in ubuntu-drivers-common package in Ubuntu: New Bug description: This may be a duplicate of bug #1514057 (close it in case), but without any PPA and just after installing Ubuntu in a new partition. Followed this ISO testing script (so installed without connection): - http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/221687/testcases/1718/results Once installed, I noticed the nvidia driver was marked as "free": https://i.imgur.com/RTA1VmD.png More detailed report from ubuntu-drivers was: $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1C91sv103Csd8640bc03sc00i00 vendor : NVIDIA Corporation model: GP107M [GeForce GTX 1050 3 GB Max-Q] driver : nvidia-driver-450 - third-party free recommended driver : xserver-xorg-video-nouveau - distro free builtin Once I did an "apt update", this got fixed. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-drivers-common 1:0.8.5.4 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:26:55 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) SourcePackage: ubuntu-drivers-common 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/1899630/+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 1879580] Re: Screencast interface missing
Chromimm output: [110445:110445:1013/141808.679718:ERROR:base_capturer_pipewire.cc(517)] Failed to create a screen cast session: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.ScreenCast” on object at path /org/freedesktop/portal/desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1879580 Title: Screencast interface missing Status in xdg-desktop-portal package in Ubuntu: Confirmed Bug description: The `org.freedesktop.portal.ScreenCast` inferface is missing in the version shipped with Ubuntu 20.04. This interface is needed for OBS no work in non-X11 environments. Further reading: https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.ScreenCast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1879580/+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 1879580] Re: Screencast interface missing
The build without `org.freedesktop.portal.ScreenCast` prevents e.g. Chrome/Chromium to share the desktop through MS teams when using Wayland, e.g. like it works on Fedora (https://uwot.eu/blog/microsoft- teams-on-fedora-and-wayland-with-screenshare/). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1879580 Title: Screencast interface missing Status in xdg-desktop-portal package in Ubuntu: Confirmed Bug description: The `org.freedesktop.portal.ScreenCast` inferface is missing in the version shipped with Ubuntu 20.04. This interface is needed for OBS no work in non-X11 environments. Further reading: https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.ScreenCast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1879580/+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 1899630] [NEW] Nvidia driver is marked as "free" on first installation before "apt update"
Public bug reported: This may be a duplicate of bug #1514057 (close it in case), but without any PPA and just after installing Ubuntu in a new partition. Followed this ISO testing script (so installed without connection): - http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/221687/testcases/1718/results Once installed, I noticed the nvidia driver was marked as "free": https://i.imgur.com/RTA1VmD.png More detailed report from ubuntu-drivers was: $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1C91sv103Csd8640bc03sc00i00 vendor : NVIDIA Corporation model: GP107M [GeForce GTX 1050 3 GB Max-Q] driver : nvidia-driver-450 - third-party free recommended driver : xserver-xorg-video-nouveau - distro free builtin Once I did an "apt update", this got fixed. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-drivers-common 1:0.8.5.4 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:26:55 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-bug groovy -- 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/1899630 Title: Nvidia driver is marked as "free" on first installation before "apt update" Status in ubuntu-drivers-common package in Ubuntu: New Bug description: This may be a duplicate of bug #1514057 (close it in case), but without any PPA and just after installing Ubuntu in a new partition. Followed this ISO testing script (so installed without connection): - http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/221687/testcases/1718/results Once installed, I noticed the nvidia driver was marked as "free": https://i.imgur.com/RTA1VmD.png More detailed report from ubuntu-drivers was: $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1C91sv103Csd8640bc03sc00i00 vendor : NVIDIA Corporation model: GP107M [GeForce GTX 1050 3 GB Max-Q] driver : nvidia-driver-450 - third-party free recommended driver : xserver-xorg-video-nouveau - distro free builtin Once I did an "apt update", this got fixed. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-drivers-common 1:0.8.5.4 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:26:55 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) SourcePackage: ubuntu-drivers-common 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/1899630/+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 1899624] [NEW] Des erreurs ont été rencontrées pendant l'exécution : emacs-gtk E: Sub-process /usr/bin/dpkg returned an error code (1)
Public bug reported: ando@ando-PC:~$ sudo apt-get install emacs-gtk Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Le paquet suivant a été installé automatiquement et n'est plus nécessaire : xaw3dg Veuillez utiliser « sudo apt autoremove » pour le supprimer. Paquets suggérés : emacs-common-non-dfsg Les paquets suivants seront ENLEVÉS : emacs-nox Les NOUVEAUX paquets suivants seront installés : emacs-gtk 0 mis à jour, 1 nouvellement installés, 1 à enlever et 12 non mis à jour. Il est nécessaire de prendre 0 o/3588 ko dans les archives. Après cette opération, 630 ko d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] o dpkg: emacs-nox : problème de dépendance, mais suppression comme demandé : emacs dépend de emacs-gtk (>= 1:26.3) | emacs-lucid (>= 1:26.3) | emacs-nox (>= 1:26.3) ; cependant : Le paquet emacs-gtk n'est pas installé. Le paquet emacs-lucid n'est pas installé. Le paquet emacs-nox doit être supprimé. (Lecture de la base de données... 291255 fichiers et répertoires déjà installés.) Suppression de emacs-nox (1:26.3+1-1ubuntu2) ... Remove elpa-magit for emacs remove/magit-2.90.1: Handling removal of emacsen flavor emacs dh-elpa: purging flavor specific files for emacs Remove elpa-git-commit for emacs remove/git-commit-2.90.1: Handling removal of emacsen flavor emacs dh-elpa: purging flavor specific files for emacs Remove elpa-magit-popup for emacs remove/magit-popup-2.13.2: Handling removal of emacsen flavor emacs dh-elpa: purging flavor specific files for emacs Remove elpa-ghub for emacs remove/ghub-3.3.0: Handling removal of emacsen flavor emacs dh-elpa: purging flavor specific files for emacs Remove dictionaries-common for emacs remove/dictionaries-common: Purging byte-compiled files for flavour emacs Remove elpa-with-editor for emacs remove/with-editor-2.6.0: Handling removal of emacsen flavor emacs dh-elpa: purging flavor specific files for emacs Remove elpa-dash for emacs remove/dash-2.17.0: Handling removal of emacsen flavor emacs dh-elpa: purging flavor specific files for emacs Remove elpa-let-alist for emacs remove/let-alist-1.0.6: Handling removal of emacsen flavor emacs dh-elpa: purging flavor specific files for emacs Remove elpa-treepy for emacs remove/treepy-0.1.1: Handling removal of emacsen flavor emacs dh-elpa: purging flavor specific files for emacs Remove git for emacs Remove emacsen-common for emacs emacsen-common: Handling removal of emacsen flavor emacs Remove cmake-data for emacs Sélection du paquet emacs-gtk précédemment désélectionné. (Lecture de la base de données... 291250 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../emacs-gtk_1%3a26.3+1-1ubuntu2_amd64.deb ... Dépaquetage de emacs-gtk (1:26.3+1-1ubuntu2) ... Paramétrage de emacs-gtk (1:26.3+1-1ubuntu2) ... update-alternatives: utilisation de « /usr/bin/emacs-gtk » pour fournir « /usr/bin/emacs » (emacs) en mode automatique tsort: - : l'entrée contient une boucle : tsort: elpa-dash tsort: emacsen-common Install git for emacs Install elpa-dash for emacs install/dash-2.17.0: Handling install of emacsen flavor emacs install/dash-2.17.0: byte-compiling for emacs emacs: error while loading shared libraries: libotf.so.0: cannot open shared object file: No such file or directory ERROR: install script from elpa-dash package failed dpkg: erreur de traitement du paquet emacs-gtk (--configure) : installed emacs-gtk package post-installation script subprocess returned error exit status 1 Traitement des actions différées (« triggers ») pour mime-support (3.64ubuntu1) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.36.0-1ubuntu1) ... Traitement des actions différées (« triggers ») pour man-db (2.9.1-1) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.24-1ubuntu3) ... Des erreurs ont été rencontrées pendant l'exécution : emacs-gtk E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: emacs (Ubuntu) Importance: Undecided Status: New ** Description changed: - Des erreurs ont été rencontrées pendant lexécution : + ando@ando-PC:~$ sudo apt-get install emacs-gtk + Lecture des listes de paquets... Fait + Construction de l'arbre des dépendances + Lecture des informations d'état... Fait + Le paquet suivant a été installé automatiquement et n'est plus nécessaire : + xaw3dg + Veuillez utiliser « sudo apt autoremove » pour le supprimer. + Paquets suggérés : + emacs-common-non-dfsg + Les paquets suivants seront ENLEVÉS : + emacs-nox + Les NOUVEAUX paquets suivants seront installés : + emacs-gtk + 0 mis à jour, 1 nouvellement installés, 1 à enlever et 12 non mis à jour. + Il est nécessaire de prendre 0 o/3588 ko dans les archives. + Après cette opération, 630 ko d'espace disque supplémentaires seront utilisés. + Souhaitez-vous continuer ? [O/n] o + dpkg: emacs-nox : problème de dépendance,
[Desktop-packages] [Bug 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
This bug was fixed in the package nvidia-prime - 0.8.15 --- nvidia-prime (0.8.15) groovy; urgency=medium [ Alberto Milone ] * prime-select: - Enable runtimepm in on-demand mode if supported (LP: #1895855). - Disable workaround for on-demand mode. - Enable KMS if runtimepm is supported. [ Kai-Heng Feng ] * prime-select: Remove udev rules -- Alberto Milone Fri, 09 Oct 2020 14:50:37 +0200 ** Changed in: nvidia-prime (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) Status in OEM Priority Project: New Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: The work that went into ubuntu-drivers-common and nvidia-prime is meant to enable RTD3 support on Intel/NVIDIA or AMD/NVIDIA hybrid systems, introduced by the NVIDIA 450 driver series. This allows the supported systems to make use of the integrated GPU (Intel or AMD) and to keep the discrete NVIDIA GPU powered down until needed. While powered down, the NVIDIA GPU can still detect any events, should external displays be plugged in. This brings hybrid graphics on Linux on par with Windows. Only the supported GPUs will be able to benefit from this change. This is why NVIDIA provides a hardware database (included in the nvidia packages), which gpu-manager can now parse. The ubuntu-drivers tool relies on that detection to enable this new feature when installing the NVIDIA driver. Another improvement is the ability of ubuntu-drivers to detect LTSB (Long term support branch), NFB (New feature branch), Legacy, Beta flags, which the NVIDIA drivers can have, and make informed detection choices. This work also includes a number of bug fixes reported on errors.ubuntu.com. Requirements: The new ubuntu-drivers-common: The new nvidia-prime: Changes to the NVIDIA drivers: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+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 1879968] Re: Copy/paste still sometimes fails in LibreOffice and Wine apps
I have a brand new install of Ubuntu 20.04 desktop which I am accessing remotely using a VNC connection. $ uname -a Linux 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux I am using x11vnc server and tightVNC on my win10 host $ x11vnc --version x11vnc: 0.9.16 lastmod: 2019-01-05 I'm seeing exactly the same problems as listed above, but when pasting to a Linux terminal in my remote TightVNC viewer. Sometimes, but not always, I can paste to a gedit text file. Mutter is already the newest version (3.36.6-1ubuntu0.20.04.2). I've never had the problem with 16.04 or 18.04. Is this the sstill part of the problem discussed on thsi thread? -- 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/1879968 Title: Copy/paste still sometimes fails in LibreOffice and Wine apps Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+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 1899456] Re: [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu)
** Changed in: libreoffice (Ubuntu) Status: Confirmed => Triaged -- 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/1899456 Title: [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu) Status in libreoffice package in Ubuntu: Triaged Bug description: The yaru icon style is explicitly shipped within the ubuntu source package of libreoffice. libreoffice 7.0.2~rc2-0ubuntu1 includes yaru icon style "2020-09-28" The final libreoffice 7.0.2-0ubuntu1 is meant to include "2020-10-11" Upstream changes: https://github.com/ubuntu/libreoffice-style-yaru- fullcolor/compare/2020-09-28...2020-10-11 Most noticeable visual changes: * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/105 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/121 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/125 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/141 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1899456/+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 1899619] [NEW] [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds
Public bug reported: Hello! I'm not really sure if is pulseaudio of bluez issue. Playback (from Gnome Settings sound test and Firefox), volume change, mute/resume is delayed for 2sec or bit more. I've verified this on two Ubuntu 20.04 laptops. To verify the AV receiver, I've paired MBP 2019 with OS X Catalina 10.15.7 and there are no audible delay. Here is sink information: * index: 16 name: driver: flags: HARDWARE DECIBEL_VOLUME LATENCY state: RUNNING suspend cause: (none) priority: 9550 volume: front-left: 46512 / 71% / -8,93 dB, front-right: 46512 / 71% / -8,93 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 56,81 ms max request: 4 KiB max rewind: 0 KiB monitor source: 18 sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 1 linked by: 4 fixed latency: 48,22 ms card: 17 module: 45 properties: bluetooth.protocol = "a2dp_sink" device.description = "Denon AVR-S650H" device.string = "00:05:CD:DF:C4:DD" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "speaker" bluez.path = "/org/bluez/hci0/dev_00_05_CD_DF_C4_DD" bluez.class = "0x240414" bluez.alias = "Denon AVR-S650H" device.icon_name = "audio-speakers-bluetooth" ports: speaker-output: Speaker (priority 0, latency offset 0 usec, available: yes) properties: active port: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.5-050805-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: bogdan82720 F pulseaudio /dev/snd/controlC1: bogdan82720 F pulseaudio /dev/snd/controlC0: bogdan82720 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 13 13:46:35 2020 InstallationDate: Installed on 2020-08-05 (68 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Denon AVR-S650H Symptom_Type: None of the above Title: [Denon AVR-S650H, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 2.1 dmi.bios.vendor: HP dmi.bios.version: S79 Ver. 01.02.01 dmi.board.name: 8730 dmi.board.vendor: HP dmi.board.version: KBC Version 13.1C.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 19.28 dmi.modalias: dmi:bvnHP:bvrS79Ver.01.02.01:bd07/02/2020:br2.1:efr19.28:svnHP:pnHPProBook455G7:pvr:rvnHP:rn8730:rvrKBCVersion13.1C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 455 G7 dmi.product.sku: 2D242EA#ACB dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Package changed: alsa-driver (Ubuntu) => pulseaudio (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/1899619 Title: [Denon AVR-S650H] Playback over Bluetooth is delayed for 2 seconds Status in pulseaudio package in Ubuntu: New Bug description: Hello! I'm not really sure if is pulseaudio of bluez issue. Playback (from Gnome Settings sound test and Firefox), volume change, mute/resume is delayed for 2sec or bit more. I've verified this on two Ubuntu 20.04 laptops. To verify the AV receiver, I've paired MBP 2019 with OS X Catalina 10.15.7 and there are no audible delay. Here is sink information: * index: 16 name: driver: flags: HARDWARE DECIBEL_VOLUME LATENCY state: RUNNING suspend cause: (none) priority: 9550 volume: front-left: 46512 / 71% / -8,93 dB, front-right: 46512 / 71% / -8,93 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 56,81 ms max request: 4 KiB max rewind: 0 KiB monitor source: 18 sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 1 linked by: 4 fixed latency: 48,22 ms card: 17 module: 45
[Desktop-packages] [Bug 1892634] Re: WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-prime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1892634 Title: WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead Status in nvidia-prime package in Ubuntu: Confirmed Bug description: File /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf contains "type=xlocal" but this gives "WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead" in lightdm.log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1892634/+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 1281588] Re: Disk standby timer is broken
I'm experiencing this bug on Ubuntu 20.04.1 It seems something is trying to access my disk, exactly every 10 minutes. I reported it as a new bug +bug 1899361 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1281588 Title: Disk standby timer is broken Status in udisks: Fix Released Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Trusty: Confirmed Bug description: udisks' / gnome-disk-utility's support for the drive standby timer is broken. If the standby timer is set to at least 10 minutes ( which is the minimum on many drives ), every 10 minutes udisks tries to update the smart status of the drive, which resets the standby timer. To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1281588/+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 1899603] [NEW] Can't upgrade on Manjaro 20.1.1
Public bug reported: Ubuntu release: Manjaro 20.1.1 using KDE+Plasma installed package version: fontconfig-ubuntu 2.13.0-2 What you expected to happen: It upgraded successfully to 2.13.1-1. What happens: It fails one of the tests during the build(when using the UI package manager) Output from build is attached in a file. ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Attachment added: "build output" https://bugs.launchpad.net/bugs/1899603/+attachment/5421647/+files/fontconfigubuntu-fail.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1899603 Title: Can't upgrade on Manjaro 20.1.1 Status in fontconfig package in Ubuntu: New Bug description: Ubuntu release: Manjaro 20.1.1 using KDE+Plasma installed package version: fontconfig-ubuntu 2.13.0-2 What you expected to happen: It upgraded successfully to 2.13.1-1. What happens: It fails one of the tests during the build(when using the UI package manager) Output from build is attached in a file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1899603/+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 1899588] Re: Stuck at "Add Printer" (in CUPS web interface) on Ubuntu 20.04
Not a solution, but at least a short-term solution. I edited /etc/cups/cupsd.conf and commented out the following lines: AuthType Default Require user @SYSTEM And it worked! -- 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/1899588 Title: Stuck at "Add Printer" (in CUPS web interface) on Ubuntu 20.04 Status in cups package in Ubuntu: New Bug description: I have a freshly installed Ubuntu 20.04.1 on my Lenovo ThinkPad X1 (8th gen). Whenever I go to http://localhost:631. I click on "Add Printer" and the status bar indicates that the page is loading. Nothing else happens. I'm stuck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: Unity Date: Tue Oct 13 10:01:26 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-08-24 (49 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 20U9004PFR Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=4a93b148-f388-4849-9a18-9e0e4d32c97a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET22W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9004PFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET22W(1.12):bd08/25/2020:svnLENOVO:pn20U9004PFR:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9004PFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9004PFR dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1899588/+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 1075196] Re: Rhythmbox never starts minimized
No reply received to comment #3 Ubuntu task expired over six years ago and no further comment since then So closing Papercuts task... ** Changed in: hundredpapercuts Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1075196 Title: Rhythmbox never starts minimized Status in One Hundred Papercuts: Invalid Status in rhythmbox package in Ubuntu: Expired Bug description: Hi! I'm on Quantal (12.10). What I expected: If I launch rhythmbox (2.97-1ubuntu6) from Dash, from Alt+F2, from terminal ecc it should show the main window. If i start it from the sound menu (by clicking the Play button, not the application name) it should start and start playing without showing me the main window. What I obtain: There's no actual way to start rhythmbox minimized. In old versions there was an option --hide to launch it without showing the main window. In newer versions there should be a gsetting key that remember the last state (minimized, normal, maximized). In the last verion it's simply impossible to launch it minimized. Way to replicate this: Open rhythmbox, then closed it (Ctrl+Q), then push "Play" in sound Menu. It does not start playing and, instead show the main window. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1075196/+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 1899456] Re: [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu)
(ricotz indicated on IRC that they had done some testing - usually I would like to see that detailed in the bug) ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1899456 Title: [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu) Status in libreoffice package in Ubuntu: Confirmed Bug description: The yaru icon style is explicitly shipped within the ubuntu source package of libreoffice. libreoffice 7.0.2~rc2-0ubuntu1 includes yaru icon style "2020-09-28" The final libreoffice 7.0.2-0ubuntu1 is meant to include "2020-10-11" Upstream changes: https://github.com/ubuntu/libreoffice-style-yaru- fullcolor/compare/2020-09-28...2020-10-11 Most noticeable visual changes: * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/105 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/121 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/125 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/141 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1899456/+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 1899456] Re: [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu)
No problem from the RT either. -- 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/1899456 Title: [UIFe] Update yaru icon style to 2010-10-11 (Ubuntu) Status in libreoffice package in Ubuntu: Confirmed Bug description: The yaru icon style is explicitly shipped within the ubuntu source package of libreoffice. libreoffice 7.0.2~rc2-0ubuntu1 includes yaru icon style "2020-09-28" The final libreoffice 7.0.2-0ubuntu1 is meant to include "2020-10-11" Upstream changes: https://github.com/ubuntu/libreoffice-style-yaru- fullcolor/compare/2020-09-28...2020-10-11 Most noticeable visual changes: * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/105 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/121 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/125 * https://github.com/ubuntu/libreoffice-style-yaru-fullcolor/pull/141 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1899456/+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 1899595] [NEW] PCI/internal sound card not detected
Public bug reported: The speaker used to work fine but the internal microphone was not showing in Settings -> Sound -> Input. I tried to purge alsa. $ sudo apt-get remove --purge alsa-base pulseaudio and then reinstall it $ sudo apt-get install ubuntu-desktop alsa-base pulseaudio After that even output sound is not working.it is showing "Dummy Output" in Settings -> Sound -> Output. After that i run this command $ cat /proc/asound/cards it is showing "--- no soundcards ---" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:01:16 2020 InstallationDate: Installed on 2020-10-08 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 02VYDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd08/26/2020:svnDellInc.:pnLatitude3410:pvr:rvnDellInc.:rn02VYDM:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3410 dmi.product.sku: 09EC dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Dmesg audio log" https://bugs.launchpad.net/bugs/1899595/+attachment/5421633/+files/dmesg_grep_audio.log -- 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/1899595 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: The speaker used to work fine but the internal microphone was not showing in Settings -> Sound -> Input. I tried to purge alsa. $ sudo apt-get remove --purge alsa-base pulseaudio and then reinstall it $ sudo apt-get install ubuntu-desktop alsa-base pulseaudio After that even output sound is not working.it is showing "Dummy Output" in Settings -> Sound -> Output. After that i run this command $ cat /proc/asound/cards it is showing "--- no soundcards ---" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:01:16 2020 InstallationDate: Installed on 2020-10-08 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 02VYDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd08/26/2020:svnDellInc.:pnLatitude3410:pvr:rvnDellInc.:rn02VYDM:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3410 dmi.product.sku: 09EC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899595/+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 1248720] Re: Bluetooth ON/OFF button switches OFF automatically
Further to comment #38, closing Papercuts task ** Changed in: hundredpapercuts Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1248720 Title: Bluetooth ON/OFF button switches OFF automatically Status in One Hundred Papercuts: Won't Fix Status in OEM Priority Project: Fix Released Status in gnome-control-center package in Ubuntu: Won't Fix Status in unity-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Trusty: Won't Fix Status in unity-control-center source package in Trusty: Fix Released Bug description: [Impact] * On trusty, we met this issue, you can't turn on/off bluetooth, it affected the other OEM project which needed by Lenovo, HP and Dell. [Test Case] * open the unity-control-center, and select 'Bluetooth', try to turn on/off in top checkbox. I am on ThinkPad T61 with Ubuntu 13.10 installed. I disabled bluetooth on startup by adding: "echo disable > /proc/acpi/ibm/bluetooth" to /etc/rc.local. When I open gnome-control-center -> Bluetooth and click on the "ON/OFF" switch button, it switches on for a fraction of a second and then switches back to off. Below are dmesg lines corresponding to this event: [ 94.028110] usb 3-1: new full-speed USB device number 5 using uhci_hcd [ 94.194320] usb 3-1: New USB device found, idVendor=0a5c, idProduct=2110 [ 94.194325] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 94.194328] usb 3-1: Product: BCM2045B [ 94.194330] usb 3-1: Manufacturer: Broadcom Corp [ 94.388169] usb 3-1: USB disconnect, device number 5 The workaround is to type "turn connectivity on/off" combination of my keyboard (FN+F5) -- then both wireless and bluetooth go off, and when I type it again, bluetooth comes back ON. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 6 20:41:45 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-18 (19 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 [Regression Potential] * The patch was already accepted in lp:unity-control-center, just cherry picked into trusty, so no potential regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1248720/+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 1892973] Re: [nvidia] Repeated screen freezes with GeForce GT 640 (GK107)
having same issues with gtx 650 ti, Kubuntu focal fossa, both with KDE and Gnome Most of times happens in the start of the session and i am forced to force reboot it. If i can start the session it's freezes in a few minutes -- 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/1892973 Title: [nvidia] Repeated screen freezes with GeForce GT 640 (GK107) Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia- driver-440. Both drivers expressly support the hardware. All varieties of desktop environment (Xorg, Gnome Classic, Ubuntu) Bug summary Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. Steps to reproduce 1. Install gnome-session. 2. Reboot. 3. Use graphical applications. What happened] The screen froze irretrievably. Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. A hard system reset and consequent reboot yields a variety of outcomes. Sometimes, a normal gdm login. Sometimes, a black screen with an inverted-black mouse cursor/pointer/arrow that moves. Sometimes an entirely black screen. Sometimes, not even a hard system reset is sufficient and the system has to be booted into recovery mode, the existing driver removed, and another installed, before rebooting again. With nvidia-driver-440, fewer hangs but the monitor resolution can't be set to its capacity. I don't get it. GNOME hangs have been extensively documented for ten years. The drivers expressly support the hardware. This package is part of an Ubuntu LTS release. Is gnome-session intended to be serious, functional, production software subjected to rigorous and competent quality control? This is a serious question because I have a business to run and can't be sucked down some random technical rabbit hole just to do daily work. Is GNOME just a cute code project intended as a resume line for people looking for real work? What kind of quality control processes are in place that allow ancient failures, extensively reported, to persist? Is anyone at GNOME able and willing to put on their big-boy pants to get a reliable package suitable for production deployments, released? The command cat /var/log/syslog | grep gnome-session reveals fundamental errors in implementing systemd syntax and references/calls to nonexistent binaries. See the gnome-sesion units in /usr/lib/systemd/user. Maybe getting this right would be a first step to helping the developers understand the environment better. Please see man systemd. Source is, astonishingly, a hybrid of C and Javascript, which doubtless presents a QC nightmare. Has anyone given this any thought? What does it take to get this package to work today? - What is the procedure? What commands must be run? - Why doesn't GNOME simply include these commands in a script, just to make it easier? Does anyone there know how? - Why doesn't GNOME simply compile these commands into the package so it works in the first place? - Will a different graphics card matter? - Which one? - Why, if the drivers support the existing hardware, according to the documentation if not the function? Can this package be made to work today? If not, will this package be ready for production use in the next Ubuntu release (i.e., 20.04.02)? If not, what alternatives exist for production use? These are all serious questions. It is astonishing that this package has been released to the public. It getting out the door poses an existential reputational threat to the GNOME project. Any help in getting this package to work would be most gratefully appreciated. What did you expect to happen I expected the screen not to freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892973/+subscriptions
[Desktop-packages] [Bug 1892973] Re: [nvidia] Repeated screen freezes with GeForce GT 640 (GK107)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (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/1892973 Title: [nvidia] Repeated screen freezes with GeForce GT 640 (GK107) Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia- driver-440. Both drivers expressly support the hardware. All varieties of desktop environment (Xorg, Gnome Classic, Ubuntu) Bug summary Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. Steps to reproduce 1. Install gnome-session. 2. Reboot. 3. Use graphical applications. What happened] The screen froze irretrievably. Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. A hard system reset and consequent reboot yields a variety of outcomes. Sometimes, a normal gdm login. Sometimes, a black screen with an inverted-black mouse cursor/pointer/arrow that moves. Sometimes an entirely black screen. Sometimes, not even a hard system reset is sufficient and the system has to be booted into recovery mode, the existing driver removed, and another installed, before rebooting again. With nvidia-driver-440, fewer hangs but the monitor resolution can't be set to its capacity. I don't get it. GNOME hangs have been extensively documented for ten years. The drivers expressly support the hardware. This package is part of an Ubuntu LTS release. Is gnome-session intended to be serious, functional, production software subjected to rigorous and competent quality control? This is a serious question because I have a business to run and can't be sucked down some random technical rabbit hole just to do daily work. Is GNOME just a cute code project intended as a resume line for people looking for real work? What kind of quality control processes are in place that allow ancient failures, extensively reported, to persist? Is anyone at GNOME able and willing to put on their big-boy pants to get a reliable package suitable for production deployments, released? The command cat /var/log/syslog | grep gnome-session reveals fundamental errors in implementing systemd syntax and references/calls to nonexistent binaries. See the gnome-sesion units in /usr/lib/systemd/user. Maybe getting this right would be a first step to helping the developers understand the environment better. Please see man systemd. Source is, astonishingly, a hybrid of C and Javascript, which doubtless presents a QC nightmare. Has anyone given this any thought? What does it take to get this package to work today? - What is the procedure? What commands must be run? - Why doesn't GNOME simply include these commands in a script, just to make it easier? Does anyone there know how? - Why doesn't GNOME simply compile these commands into the package so it works in the first place? - Will a different graphics card matter? - Which one? - Why, if the drivers support the existing hardware, according to the documentation if not the function? Can this package be made to work today? If not, will this package be ready for production use in the next Ubuntu release (i.e., 20.04.02)? If not, what alternatives exist for production use? These are all serious questions. It is astonishing that this package has been released to the public. It getting out the door poses an existential reputational threat to the GNOME project. Any help in getting this package to work would be most gratefully appreciated. What did you expect to happen I expected the screen not to freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1892973] Re: [nvidia] Repeated screen freezes with GeForce GT 640 (GK107)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-450 (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/1892973 Title: [nvidia] Repeated screen freezes with GeForce GT 640 (GK107) Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia- driver-440. Both drivers expressly support the hardware. All varieties of desktop environment (Xorg, Gnome Classic, Ubuntu) Bug summary Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. Steps to reproduce 1. Install gnome-session. 2. Reboot. 3. Use graphical applications. What happened] The screen froze irretrievably. Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. A hard system reset and consequent reboot yields a variety of outcomes. Sometimes, a normal gdm login. Sometimes, a black screen with an inverted-black mouse cursor/pointer/arrow that moves. Sometimes an entirely black screen. Sometimes, not even a hard system reset is sufficient and the system has to be booted into recovery mode, the existing driver removed, and another installed, before rebooting again. With nvidia-driver-440, fewer hangs but the monitor resolution can't be set to its capacity. I don't get it. GNOME hangs have been extensively documented for ten years. The drivers expressly support the hardware. This package is part of an Ubuntu LTS release. Is gnome-session intended to be serious, functional, production software subjected to rigorous and competent quality control? This is a serious question because I have a business to run and can't be sucked down some random technical rabbit hole just to do daily work. Is GNOME just a cute code project intended as a resume line for people looking for real work? What kind of quality control processes are in place that allow ancient failures, extensively reported, to persist? Is anyone at GNOME able and willing to put on their big-boy pants to get a reliable package suitable for production deployments, released? The command cat /var/log/syslog | grep gnome-session reveals fundamental errors in implementing systemd syntax and references/calls to nonexistent binaries. See the gnome-sesion units in /usr/lib/systemd/user. Maybe getting this right would be a first step to helping the developers understand the environment better. Please see man systemd. Source is, astonishingly, a hybrid of C and Javascript, which doubtless presents a QC nightmare. Has anyone given this any thought? What does it take to get this package to work today? - What is the procedure? What commands must be run? - Why doesn't GNOME simply include these commands in a script, just to make it easier? Does anyone there know how? - Why doesn't GNOME simply compile these commands into the package so it works in the first place? - Will a different graphics card matter? - Which one? - Why, if the drivers support the existing hardware, according to the documentation if not the function? Can this package be made to work today? If not, will this package be ready for production use in the next Ubuntu release (i.e., 20.04.02)? If not, what alternatives exist for production use? These are all serious questions. It is astonishing that this package has been released to the public. It getting out the door poses an existential reputational threat to the GNOME project. Any help in getting this package to work would be most gratefully appreciated. What did you expect to happen I expected the screen not to freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1899361] Re: udisk prevent disk from standby, standby timer is broken
I'm using smartmontools to check my drive every 30 minutes. It has an option to don't check if the drive is standby. Can't they at least do the same? And I had a question. Why does udisks checks smart data? Is it going to notify me if there's a problem, or ... ? P.S. My hard drive model number is TOSHIBA MQ04ABF100 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1899361 Title: udisk prevent disk from standby, standby timer is broken Status in udisks package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: It seems udisks tries to access my HDD every 10 minute. So when I set standby timer less than 10 minutes, It can't go to standby. Probably the disk shouldn't be checked when it's on standby. This bug has been reported before (+bug #1281588) and seems to be fixed, But I'm experiencing this again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE CustomUdevRuleFiles: wolfram-vernierlink-libusb.rules Date: Sun Oct 11 19:38:48 2020 InstallationDate: Installed on 2020-10-02 (8 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UF 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.:bvrX510UF.304:bd09/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S15 X510UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1899361/+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 1899588] [NEW] Stuck at "Add Printer" (in CUPS web interface) on Ubuntu 20.04
Public bug reported: I have a freshly installed Ubuntu 20.04.1 on my Lenovo ThinkPad X1 (8th gen). Whenever I go to http://localhost:631. I click on "Add Printer" and the status bar indicates that the page is loading. Nothing else happens. I'm stuck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: Unity Date: Tue Oct 13 10:01:26 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-08-24 (49 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 20U9004PFR Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=4a93b148-f388-4849-9a18-9e0e4d32c97a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET22W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9004PFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET22W(1.12):bd08/25/2020:svnLENOVO:pn20U9004PFR:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9004PFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9004PFR dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1899588 Title: Stuck at "Add Printer" (in CUPS web interface) on Ubuntu 20.04 Status in cups package in Ubuntu: New Bug description: I have a freshly installed Ubuntu 20.04.1 on my Lenovo ThinkPad X1 (8th gen). Whenever I go to http://localhost:631. I click on "Add Printer" and the status bar indicates that the page is loading. Nothing else happens. I'm stuck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: Unity Date: Tue Oct 13 10:01:26 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-08-24 (49 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 20U9004PFR Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=4a93b148-f388-4849-9a18-9e0e4d32c97a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET22W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9004PFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET22W(1.12):bd08/25/2020:svnLENOVO:pn20U9004PFR:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9004PFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9004PFR dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1899588/+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 1873052] Re: Showing two cursors after login when fractional scaling is enabled
Looks like we might have confused at least two different issues. For systems using the 'amdgpu' kernel driver, supposedly a fix is coming in kernels 5.9.0, 5.8.13 & 5.4.69. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Summary changed: - Showing two cursors after login when fractional scaling is enabled + Showing two cursors after login -- 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/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+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 1897563] Re: Zsys changes the canmount property of persistent bpool/grub dataset
** Changed in: zsys (Ubuntu Focal) Assignee: (unassigned) => Didier Roche (didrocks) ** No longer affects: zsys (Ubuntu Bionic) ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1897563 Title: Zsys changes the canmount property of persistent bpool/grub dataset Status in zsys package in Ubuntu: Fix Released Status in zsys source package in Focal: Fix Committed Bug description: [Impact] * People having personal layout, like a persistent dedicated dataset under /boot like /boot/grub will get it unmouted after a state revert. * Side effects: - those datasets are never marked as being part of the current machine, or any state. - bpool and bpool/BOOT are not listed in the unmanaged dataset list. [Test Case] * Install ZFS manually with a persistent bpool/bpool/grub dataset * Take a snapshot * Revert to this snapshot when rebooting * Check that the persistent grub dataset is still mounted * You can check as well with zsysctl show --full that you have this persistent dataset attached to the machine. [Regression Potential] * New datasets under /boot could appear to be attached by the machine (even if unlikely due to the huge testsuite which has been updated and checked) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1897563/+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 1899485] Re: cannot send message
Updating to the upstream 78 release solved the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1899485 Title: cannot send message Status in thunderbird package in Ubuntu: New Bug description: using 1:68.10.0+build1-0ubuntu0.18.04.1 When I try to send a message, nothing happens. In the console, I see this error message JavaScript error: chrome://messenger/content/messengercompose/MsgComposeCommands.js, line 6156: NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIMsgCompose.expandMailingLists] This currently makes thunderbird unuseable. Best regards Alexandre To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899485/+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 1899479] Re: folders window in v78 has excessive vertival spacing
** Summary changed: - folders window in v76 has excessive vertival spacing + folders window in v78 has excessive vertival spacing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1899479 Title: folders window in v78 has excessive vertival spacing Status in thunderbird package in Ubuntu: New Bug description: comparing the folders window between the versions in focal and groovy, the folders window has an excessive amount of vertical spacing. Is there a way to reset that to the previous settings? I see this as a regression, not seeing the amount of folders on the screen as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899479/+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 1883898] Re: version 3.20.6 turns off plugin requirement for most printers
I basically do the same in Fedora - reverting models.dat to its state in 3.20.5, because I don't have resource to actually test. I based my report on assumption you actually have a internal versioning system (git, svn, bazaar, gitlab, github...) so you can revert commits regarding the plugin change. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1883898 Title: version 3.20.6 turns off plugin requirement for most printers Status in HPLIP: In Progress Status in hplip package in Ubuntu: Incomplete Status in hplip package in Fedora: Confirmed Bug description: Hi, hplip-3.20.6 turns off plugin requirement for most devices which required the plugin at the past. This will make devices which really need it unable to print and most scanning will not work. Would you mind reverting the changes in models.dat? Thank you in advance! Zdenek To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1883898/+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
