[Desktop-packages] [Bug 1811724] Re: libbd_mdraid.so.2: cannot open shared object file
Same on Ubuntu 20.04 both GA and HWE kernel. Sure, it just takes this command to find which package has it: $ apt-file search libbd_mdraid.so.2 And get "libblockdev-mdraid2", which does "fix" it, but I DON'T need it. Depends on packages I don't need, MOST don't need: $ apt show libblockdev-mdraid2 Depends: libblockdev-utils2 (>= 2.20), libbytesize1 (>= 2.1), libc6 (>= 2.27), libglib2.0-0 (>= 2.42.2), mdadm (>= 3.3.2) However it's the same on Raspbian for the Raspberry Pi, so it's more of a Debian problem. And installing that package then wants exim4 and all... A mail server?? For a library? -- 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/1811724 Title: libbd_mdraid.so.2: cannot open shared object file Status in udisks2 package in Ubuntu: Confirmed Bug description: Had some (probably unrelated?) trouble typing input into login console, and went looking through /var/log/syslog : found Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' libblockdev plugin Seems to give this warning every time I boot. udisks2: Installed: 2.8.1-3 Candidate: 2.8.1-3 ubuntu: 19.04 disco ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: udisks2 2.8.1-3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Mon Jan 14 21:31:52 2019 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Red Hat KVM ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash SourcePackage: udisks2 UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.modalias: dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr: dmi.product.family: Red Hat Enterprise Linux dmi.product.name: KVM dmi.product.version: RHEL 6.6.0 PC dmi.sys.vendor: Red Hat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1811724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939186] [NEW] Wayland causes arrow key scroll lock behavior when using Japanese or US-intl keyboard layouts
Public bug reported: After upgrading to Ubuntu 21.04 with Wayland as default, the arrow keys on my Japanese 108-key USB keyboard scroll in LibreOffice Calc as though scroll lock is toggled on (even though the scroll lock light is not on) instead of moving the cell in focus. (This happens with the US-intl keyboard layout too.) The arrow keys work as expected in other programs though, including LibreOffice Writer. If I switch to the default US keyboard layout, the arrow keys on the same keyboard work properly: moving the cell in focus. I tried removing grp_led:scroll from XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" in /etc/default/keyboard, but that did not fix it. I also tried uninstalling LibreOffice and removing the config files as explained here, but that didn't fix it either. This was not a problem in Ubuntu 20.10 and the Japanese USB keyboard arrow keys work correctly in LibreCalc on Windows, so the issue appears to be specific to Ubuntu 21.04, not LibreOffice, nor this keyboard. As a workaround, if I start the session with Xorg instead, the arrow keys work as expected with any keyboard layout. Therefore, this bug appears to be related to Wayland. I was encouraged to file this bug report for gnome-shell in the comments on this AskUbuntu post: https://askubuntu.com/questions/1356052/why-do- japanese-keyboard-arrow-keys-scroll-in-libreoffice-calc-but-move-cell- wit/1356059?noredirect=1#comment2321519_1356059 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 12:18:23 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (548 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-07-06T20:58:08.463515 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1939186 Title: Wayland causes arrow key scroll lock behavior when using Japanese or US-intl keyboard layouts Status in gnome-shell package in Ubuntu: New Bug description: After upgrading to Ubuntu 21.04 with Wayland as default, the arrow keys on my Japanese 108-key USB keyboard scroll in LibreOffice Calc as though scroll lock is toggled on (even though the scroll lock light is not on) instead of moving the cell in focus. (This happens with the US-intl keyboard layout too.) The arrow keys work as expected in other programs though, including LibreOffice Writer. If I switch to the default US keyboard layout, the arrow keys on the same keyboard work properly: moving the cell in focus. I tried removing grp_led:scroll from XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" in /etc/default/keyboard, but that did not fix it. I also tried uninstalling LibreOffice and removing the config files as explained here, but that didn't fix it either. This was not a problem in Ubuntu 20.10 and the Japanese USB keyboard arrow keys work correctly in LibreCalc on Windows, so the issue appears to be specific to Ubuntu 21.04, not LibreOffice, nor this keyboard. As a workaround, if I start the session with Xorg instead, the arrow keys work as expected with any keyboard layout. Therefore, this bug appears to be related to Wayland. I was encouraged to file this bug report for gnome-shell in the comments on this AskUbuntu post: https://askubuntu.com/questions/1356052/why-do-japanese-keyboard- arrow-keys-scroll-in-libreoffice-calc-but-move-cell- wit/1356059?noredirect=1#comment2321519_1356059 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 12:18:23 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (548 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-07-06T20:58:08.463515 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1939185] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Public bug reported: Automatically generated while sudo apt upgrade --> sudo apt upgrade MacBook Pro 5,5 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Fri Aug 6 22:25:14 2021 InstallationDate: Installed on 2021-05-15 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1939185 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Automatically generated while sudo apt upgrade --> sudo apt upgrade MacBook Pro 5,5 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Fri Aug 6 22:25:14 2021 InstallationDate: Installed on 2021-05-15 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1939185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939183] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Public bug reported: I don't know why this is being generated. The system did it automatically. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Wed Aug 4 21:05:46 2021 InstallationDate: Installed on 2020-05-18 (445 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1939183 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I don't know why this is being generated. The system did it automatically. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Wed Aug 4 21:05:46 2021 InstallationDate: Installed on 2020-05-18 (445 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1939183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939182] [NEW] Title bar is black and unrendered when turned off
Public bug reported: After creating the value browser.tabs.drawInTitlebar and setting it to true, the tabs are moved up to a bar with the window controls, but the title bar is black and still present. This black bar is still draggable. Also, enabling the flag makes firefox render strangely on startup. These issues only happen in fullscreen mode, windowed mode does not have the black bar, although windowed mode does have a blank spot in the top left corner which I don't know is intentional or not. Mint 20.2, but I'm using the ubuntu firefox next PPA at https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next, cinnamon 5.0.5. 750M GPU, Driver Version: 418.113 An imgur link provided for illustration: https://imgur.com/a/Yj9RFIL ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1939182 Title: Title bar is black and unrendered when turned off Status in firefox package in Ubuntu: New Bug description: After creating the value browser.tabs.drawInTitlebar and setting it to true, the tabs are moved up to a bar with the window controls, but the title bar is black and still present. This black bar is still draggable. Also, enabling the flag makes firefox render strangely on startup. These issues only happen in fullscreen mode, windowed mode does not have the black bar, although windowed mode does have a blank spot in the top left corner which I don't know is intentional or not. Mint 20.2, but I'm using the ubuntu firefox next PPA at https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next, cinnamon 5.0.5. 750M GPU, Driver Version: 418.113 An imgur link provided for illustration: https://imgur.com/a/Yj9RFIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1939182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.
When I switched off and on google calendar in gnome-calendar, this happened: GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Aborted (core dumped) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1938658 Title: Week view goes blank when changing weeks or when user screen focus changes. Status in gnome-calendar package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938915] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build, this is happening while using Ubuntu 20.04
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug is no longer a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- 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/1938915 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build, this is happening while using Ubuntu 20.04 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: I do not know if it is a bug or not. I just installed Ubuntu 20.04 two days ago on Aug 2, 2021 and installed the Nvidia drivers yesterday on Aug 3, 2021 and today I keep getting this pop up saying that system crashed. I just hit send. Do not know about why it is happening. I installed the driver because Firefox kept crashing my computer, so I thought that maybe it was the driver. Maybe I should revert to the Nuveau driver. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Wed Aug 4 11:09:19 2021 InstallationDate: Installed on 2021-08-01 (2 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938981] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug is no longer a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- 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/1938981 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: weather applet crashed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Wed Aug 4 20:45:39 2021 InstallationDate: Installed on 2020-07-19 (381 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938951] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug is no longer a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- 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/1938951 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: ProblemType: Package DKMSBuildLog: DKMS make.log for nvidia-340-340.108 for kernel 5.11.0-25-generic (x86_64) Mi 4. Aug 15:52:26 CEST 2021 NVIDIA: calling KBUILD... make[1]: Verzeichnis „/usr/src/linux-headers-5.11.0-25-generic“ wird betreten test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia-340/340.108/build \ single-build= \ need-builtin=1 need-modorder=1 Occurred during automatic upgrade of UBUNTU 20.04 causing a not startable system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Wed Aug 4 15:53:08 2021 InstallationDate: Installed on 2021-03-08 (148 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938984] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug is no longer a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- 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/1938984 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 08:33:49 2021 InstallationDate: Installed on 2020-08-09 (360 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938930] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- 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/1938930 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After auto upgrading to the new Nvidia driver, I keep getting the "system crashed" message. The linux kernel 5.11.00-generic doesn't boot at all with this new nvidia driver. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Wed Aug 4 21:42:36 2021 InstallationDate: Installed on 2021-06-30 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939003] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug is no longer a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- 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/1939003 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: After installing this update, there were problems with booting the ubuntu. I tried to recover using grub menu and it worked. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 10:24:38 2021 InstallationDate: Installed on 2021-05-31 (66 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1939003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939039] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug is no longer a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- 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/1939039 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: System nofification of bug. I don't know anything more. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 06:39:04 2021 InstallationDate: Installed on 2021-03-11 (147 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1939039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938980] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug is no longer a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- 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/1938980 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: nil ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 09:25:01 2021 InstallationDate: Installed on 2021-08-01 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938991] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug is no longer a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- 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/1938991 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 12:30:00 2021 InstallationDate: Installed on 2021-04-21 (106 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939069] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug is no longer a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- 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/1939069 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: nvidia 340 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 19:11:35 2021 InstallationDate: Installed on 2021-06-25 (40 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1939069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.
I just tried it out: if I switch off google calendar (set up in Settings/Online accounts), everything is working as it should be. But I need google calendar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1938658 Title: Week view goes blank when changing weeks or when user screen focus changes. Status in gnome-calendar package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937247] Re: Difficulty closing the Dialog Preferences in Nautilus
** Attachment added: "Screenshot from 2021-08-07 00-47-46.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1937247/+attachment/5516418/+files/Screenshot%20from%202021-08-07%2000-47-46.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/1937247 Title: Difficulty closing the Dialog Preferences in Nautilus Status in nautilus package in Ubuntu: New Bug description: Dear maintainer, in Nautilus 40.2 the upper bar of the Preferences Dialog does not appear, so it is only possible to close the Preferences Dialog by pressing the ESC key on the keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1937247/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719143] Re: Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample]
** Attachment added: "journalctl -b 0" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1719143/+attachment/5516417/+files/journalctl.log -- 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/1719143 Title: Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample] Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Fresh install of Artful, using gnome-session to access vanilla GNOME session on Wayland (also tried on xorg). Attempting to calibrate monitors through Gnome Control Center->Devices->Color. All attempts ended at the point where I was asked to put the device onto the monitor, with the error: Calibration failed! An internal error occurred that could not be recovered. You can remove the calibration device. Syslog: Sep 24 12:19:31 desktop kernel: [ 262.849675] usb 3-6: new full-speed USB device number 7 using xhci_hcd Sep 24 12:19:32 desktop kernel: [ 262.990880] usb 3-6: New USB device found, idVendor=0971, idProduct=2007 Sep 24 12:19:32 desktop kernel: [ 262.990882] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 24 12:19:32 desktop kernel: [ 262.990884] usb 3-6: Product: colormunki Sep 24 12:19:32 desktop kernel: [ 262.990885] usb 3-6: Manufacturer: X-Rite Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop gnome-shell[876]: drmModeSetCursor2 failed with (Permission denied), drawing cursor with OpenGL from now on Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) I attempted to fix the permissions error for /dev/dri/card0. Current permissions: rwh@desktop:~$ ls -l /dev/dri/card0 crw-rw+ 1 root video 226, 0 Sep 24 12:15 /dev/dri/card0 Tried adding my user to video group, which made no difference. Then made file world r/w: rwh@desktop:~$ sudo chmod o+rw /dev/dri/card0 Which fixed that problem. Now, in the calibrate wizard, on the second step (Display Type) I am offered three options (LCD, CRT, Projector) where I only saw LCD previously. However, the calibration step failed the same as before. Syslog: Sep 24 12:36:46 desktop kernel: [ 1298.430546] usb 3-6: new full-speed USB device number 12 using xhci_hcd Sep 24 12:36:46 desktop kernel: [ 1298.571756] usb 3-6: New USB device found, idVendor=0971, idProduct=2007 Sep 24 12:36:46 desktop kernel: [ 1298.571759] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 24 12:36:46 desktop kernel: [ 1298.571760] usb 3-6: Product: colormunki Sep 24 12:36:46 desktop kernel: [ 1298.571762] usb 3-6: Manufacturer: X-Rite Sep 24 12:36:46 desktop pulseaudio[953]: message repeated 3 times: [ W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.] Sep 24 12:36:47 desktop gnome-control-c[5206]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. Sep 24 12:36:47 desktop gnome-control-c[5201]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. Sep 24 12:36:47 desktop gnome-control-c[5201]: Error 71 (Protocol error) dispatching to Wayland display. Sep 24 12:36:47 desktop gnome-control-c[5206]: Error 71 (Protocol error) dispatching to Wayland display. Sep 24 12:37:21 desktop dbus-daemon[4121]: Activating via systemd: service name='org.freedesktop.ColorHelper' unit='colord-session.service' Sep 24 12:37:21 desktop systemd[3601]: Starting Color management helper... Sep 24 12:37:21 desktop dbus-daemon[4121]: Successfully activated service
[Desktop-packages] [Bug 1719143] Re: Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample]
can confirm under Ubuntu 20.04 with Spyder 3 express as well. Hope the attached log messages from 'dmesg' and 'journalctl -b 0' help. Shell output: $ gnome-control-center (gnome-control-center:6495): color-cc-panel-WARNING **: 23:54:00.320: calibration failed with code 1: no sensor->get_sample (gnome-control-center:6495): color-cc-panel-WARNING **: 23:54:11.074: failed to start calibrate: failed to calibrate (gnome-control-center:6495): libcolord-CRITICAL **: 00:00:02.301: cd_profile_has_access: assertion 'CD_IS_PROFILE (profile)' failed (gnome-control-center:6495): libcolord-CRITICAL **: 00:00:02.301: cd_profile_get_filename: assertion 'CD_IS_PROFILE (profile)' failed (gnome-control-center:6495): libcolord-CRITICAL **: 00:00:02.301: cd_profile_get_id: assertion 'CD_IS_PROFILE (profile)' failed (gnome-control-center:6495): color-cc-panel-WARNING **: 00:00:02.301: (null) is not usable by this user (gnome-control-center:6495): libcolord-CRITICAL **: 00:00:02.348: cd_profile_has_access: assertion 'CD_IS_PROFILE (profile)' failed (gnome-control-center:6495): libcolord-CRITICAL **: 00:00:02.348: cd_profile_get_filename: assertion 'CD_IS_PROFILE (profile)' failed (gnome-control-center:6495): libcolord-CRITICAL **: 00:00:02.348: cd_profile_get_id: assertion 'CD_IS_PROFILE (profile)' failed (gnome-control-center:6495): color-cc-panel-WARNING **: 00:00:02.348: (null) is not usable by this user (gnome-control-center:6495): libcolord-CRITICAL **: 00:00:02.961: cd_profile_has_access: assertion 'CD_IS_PROFILE (profile)' failed (gnome-control-center:6495): libcolord-CRITICAL **: 00:00:02.961: cd_profile_get_filename: assertion 'CD_IS_PROFILE (profile)' failed (gnome-control-center:6495): libcolord-CRITICAL **: 00:00:02.961: cd_profile_get_id: assertion 'CD_IS_PROFILE (profile)' failed (gnome-control-center:6495): color-cc-panel-WARNING **: 00:00:02.961: (null) is not usable by this user (gnome-control-center:6495): color-cc-panel-CRITICAL **: 00:27:07.688: cc_color_calibrate_setup: assertion 'calibrate->device_kind != CD_SENSOR_CAP_UNKNOWN' failed Speicherzugriffsfehler (Speicherabzug geschrieben) ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1719143/+attachment/5516416/+files/dmesg.log -- 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/1719143 Title: Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample] Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Fresh install of Artful, using gnome-session to access vanilla GNOME session on Wayland (also tried on xorg). Attempting to calibrate monitors through Gnome Control Center->Devices->Color. All attempts ended at the point where I was asked to put the device onto the monitor, with the error: Calibration failed! An internal error occurred that could not be recovered. You can remove the calibration device. Syslog: Sep 24 12:19:31 desktop kernel: [ 262.849675] usb 3-6: new full-speed USB device number 7 using xhci_hcd Sep 24 12:19:32 desktop kernel: [ 262.990880] usb 3-6: New USB device found, idVendor=0971, idProduct=2007 Sep 24 12:19:32 desktop kernel: [ 262.990882] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 24 12:19:32 desktop kernel: [ 262.990884] usb 3-6: Product: colormunki Sep 24 12:19:32 desktop kernel: [ 262.990885] usb 3-6: Manufacturer: X-Rite Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop gnome-shell[876]: drmModeSetCursor2 failed with (Permission denied), drawing cursor with OpenGL from now on Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error:
[Desktop-packages] [Bug 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.
Does anyone else experience this, or just me? With this issue the calendar is unusable, but I couldn't find any bug report about this. But this bug has been around for a long time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1938658 Title: Week view goes blank when changing weeks or when user screen focus changes. Status in gnome-calendar package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP
** Changed in: snapd (Ubuntu) Assignee: Samuele Pedroni (pedronis) => Ian Johnson (anonymouse67) ** Changed in: snapd (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: In Progress Bug description: The last few background updates of chromium have made some old tabs suddenly crash with SIGTRAP and it also makes it impossible to open new tabs, those die instantly with a SIGTRAP as well. This is incredibly destructive to whatever might be the dying tabs' unsaved state and there's no warning about it. Yet again a snap- related change rolled out to users with absolutely amateur-tier testing. Ubuntu: 20.04.2 Snap: 2.48+20.04 Chromium: 88.0.4324.150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938658] Re: Week view goes blank when changing weeks or when user screen focus changes.
When launching gnome-calendar, the week view (current week) appears for a second and disappear when the header (days of the week) is being written. After switching to previous and next weeks the week view is normal again. Returnig to the current week the week view is blank again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1938658 Title: Week view goes blank when changing weeks or when user screen focus changes. Status in gnome-calendar package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Week view goes blank when changing weeks or when user screen focus changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1938658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939173] Re: Screen flickering white vertical lines
** Description changed: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. + Flickering seems to be consistent to screen refresh state (~60Hz). + Changing refresh rate does not affect in to amount of flickering. - Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. + Same thing not happening in Windows nor BIOS. Even though this looks a + LOT like a hardware/wiring issue. Best regards, korho. - $ lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy xorg xorg: - Installed: 1:7.7+19ubuntu14 - Candidate: 1:7.7+19ubuntu14 - Version table: - *** 1:7.7+19ubuntu14 500 - 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:7.7+19ubuntu14 + Candidate: 1:7.7+19ubuntu14 + Version table: + *** 1:7.7+19ubuntu14 500 + 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 23:04:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2021-08-06 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard 120-1100eo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=bf3dba7e-429f-455e-ac68-c016e272a4d9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 100 dmi.chassis.asset.tag: CZC2128RP3 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-1100eo:pvr:rvnQuanta:rn2AC5:rvr100:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-1100eo dmi.product.sku: H1E79EA#UUW dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Description changed: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. Same thing not happening in Windows nor BIOS. Even though this looks a LOT like a hardware/wiring issue. + + Also the problem is visible in Ubuntu installer, but not in graphic safe + one. Best regards, korho. $ lsb_release -rd: Description: Ubuntu 20.04.2 LTS
[Desktop-packages] [Bug 1939173] [NEW] Screen flickering white vertical lines
Public bug reported: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. Same thing not happening in Windows nor BIOS. Even though this looks a LOT like a hardware/wiring issue. Also the problem is visible in Ubuntu installer, but not in graphic safe one. Best regards, korho. $ lsb_release -rd: Description:Ubuntu 20.04.2 LTS Release:20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 6 23:04:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2021-08-06 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard 120-1100eo ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=bf3dba7e-429f-455e-ac68-c016e272a4d9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 100 dmi.chassis.asset.tag: CZC2128RP3 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-1100eo:pvr:rvnQuanta:rn2AC5:rvr100:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-1100eo dmi.product.sku: H1E79EA#UUW dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1939173 Title: Screen flickering white vertical lines Status in xorg package in Ubuntu: New Bug description: The screen on my HP AIO computer flickers. I'm able to browse the computer, but it's giving me headache. Flickering consists pattern of 2cm height white vertical pixel lines (1*Wpx white and 1*Wpx transparent lines) and 2cm transparent section. Flicker also has 1px lines with dashes ending them about 10cm from left of the screen and 2cm from right of the screen. Mathematically letter W being 100% of screen width in above description. Flickering seems to be consistent to screen refresh state (~60Hz). Changing refresh rate does not affect in to amount of flickering. Same thing not happening in Windows nor BIOS. Even though this looks a LOT like a hardware/wiring issue. Also the problem is visible in Ubuntu installer, but not in graphic safe one. Best regards, korho. $ lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package:
[Desktop-packages] [Bug 540826] Re: Rename "Suspend" to "Sleep"
Looking at all of the comments and with nothing added for over 10 years I'm closing this now with a status of 'Opinion'. No doubt Ubuntu and its various flavours will follow upstream design decisions. ** Changed in: hundredpapercuts Status: Triaged => Opinion ** Changed in: gnome-power-manager (Ubuntu) Status: Triaged => Opinion ** Changed in: indicator-session (Ubuntu) Status: Triaged => Incomplete ** Changed in: gnome-session (Ubuntu) Status: Confirmed => Opinion ** Changed in: indicator-session Status: Confirmed => Opinion ** Changed in: indicator-session (Ubuntu) Status: Incomplete => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/540826 Title: Rename "Suspend" to "Sleep" Status in One Hundred Papercuts: Opinion Status in Session Menu: Opinion Status in gnome-power-manager package in Ubuntu: Opinion Status in gnome-session package in Ubuntu: Opinion Status in indicator-session package in Ubuntu: Opinion Bug description: In the Power Menu, "Suspend" should be renamed to "Sleep" because sleep falls on a continuum with hibernation/"Hibernate", and "sleep" is a more intuitive term for new users (you can verify this by asking ten people who have not used Ubuntu what it means to "suspend" a computer, then ask another ten people who have not used Ubuntu what it means to "sleep" a computer). - Specifically in Power Management Preferences, both words "sleep" and "suspend" are used and mean the same thing. Under Actions is "Put computer to sleep when inactive for:" while the drop-down selection boxes have "Suspend" as an option. Also: http://live.gnome.org/GnomePowerManager/SleepNames https://lists.ubuntu.com/archives/ubuntu-devel/2006-May/017718.html bug 531491, about changing "Suspend" to "Sleep" *and* "Shut Down" to "Switch Off". To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/540826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1540941] Re: character map font viewer package adwaita-icon-theme 3.18.0-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/Adwaita/256x256/status/securi
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. I'm setting this bug to "Incomplete" as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: adwaita-icon-theme (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adwaita-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1540941 Title: character map font viewer package adwaita-icon-theme 3.18.0-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/Adwaita/256x256/status/security-low.png', which is also in package adwaita-icon-theme-full 3.18.0-2ubuntu1 Status in One Hundred Papercuts: Incomplete Status in adwaita-icon-theme package in Ubuntu: Incomplete Bug description: no further information ProblemType: Package DistroRelease: Ubuntu 16.04 Package: adwaita-icon-theme 3.18.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 2 11:03:53 2016 DuplicateSignature: Unpacking adwaita-icon-theme (3.18.0-2ubuntu2) over (3.18.0-2ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/adwaita-icon-theme_3.18.0-2ubuntu2_all.deb (--unpack): trying to overwrite '/usr/share/icons/Adwaita/256x256/status/security-low.png', which is also in package adwaita-icon-theme-full 3.18.0-2ubuntu1 ErrorMessage: trying to overwrite '/usr/share/icons/Adwaita/256x256/status/security-low.png', which is also in package adwaita-icon-theme-full 3.18.0-2ubuntu1 InstallationDate: Installed on 2016-02-02 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160201) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: adwaita-icon-theme Title: package adwaita-icon-theme 3.18.0-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/Adwaita/256x256/status/security-low.png', which is also in package adwaita-icon-theme-full 3.18.0-2ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1540941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1591785] Re: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. I'm setting this bug to "Incomplete" as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: hundredpapercuts Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-361 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1591785 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build when gcc and g++ are set to v4.8 instead of default v5.3 Status in One Hundred Papercuts: Incomplete Status in nvidia-graphics-drivers-361 package in Ubuntu: Incomplete Bug description: after a routine system update, Linux kernel was upgraded to 4.4.0-24-generic. Since then, the nvidia graphic drivers simply refuses to build: > Building initial module for 4.4.0-24-generic > Error! Bad return status for module build on kernel: 4.4.0-24-generic (x86_64) > Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 DKMSKernelVersion: 4.4.0-24-generic Date: Sun Jun 12 19:45:40 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:cc: error: unrecognized command line option ‘-fstack-protector-strong’ InstallationDate: Installed on 2015-10-31 (225 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-05-04 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1591785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1080108] Re: Amazon name and descriptions need improvement
webb-apps-applications is no longer included in any currently supported release of Ubuntu. I'm closing this bug report with a status of "Invalid" in order to tidy the list of outstanding '100 Papercuts' issues. ** Changed in: hundredpapercuts Status: Confirmed => Invalid ** Changed in: webapps-applications (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webapps-applications in Ubuntu. https://bugs.launchpad.net/bugs/1080108 Title: Amazon name and descriptions need improvement Status in One Hundred Papercuts: Invalid Status in webapps-applications package in Ubuntu: Invalid Bug description: Amazon is a collection of example scripts for integration of webapps into Unity's Launcher, or at least this is what I understand reading the actual description and looking into the Launchpad page. https://launchpad.net/webapps-applications Looking at the icon, the name, and reading the brief description, an average user could think that this package is an official Amazon webapp, which, as far as I understand, its not. If all of the above is correct, the description, the name, and the icon should state clear that this package is intended for developers or advanced users. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1080108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1084643] Re: Colour casting on black text using the default renderer pdftops (workaround: use gs)
Official support for Ubuntu 12.04.5 ended on April 28, 2017. Official support for Ubuntu 12.10 ended on May 16, 2014. Does this problem still occur on Ubuntu 21.04? ** Changed in: poppler (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1084643 Title: Colour casting on black text using the default renderer pdftops (workaround: use gs) Status in poppler package in Ubuntu: Incomplete Bug description: For some time now (I think the bug is not specific to Ubuntu 12.10 but also present in 12.04), I am having trouble when printing black text with an HP Color LaserJet CP1515n, that worked fine on previous Ubuntu releases and from other Operating Systems. The output is kind of ok, but black text does has a slight red cast, making it look fuzzy. The problem exists when printing from LibreOffice, Firefox and Evince. Trying different settings and drivers to debug the problem, I came to the conclusion that the problem is on the pdftops default renderer. On LibreOffice, I went to File - Printer Settings - Properties - Device - Printer Language Type and chose Postscript (Level from driver). For Firefox and Evince I just used this command from the command line: $ lpadmin -p "HP-Color-LaserJet-cp1515n" -o pdftops-renderer- default=gs (use "pdftops-renderer-default=pdftops" to restore the default) Using this settings (gs), the printing results are fine. $ dpkg -l poppler-utils hplip cups Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii cups 1.6.1-0ubunt amd64Common UNIX Printing System(tm) - ii hplip 3.12.6-3ubun amd64HP Linux Printing and Imaging Sys ii poppler-utils 0.20.4-0ubun amd64PDF utilities (based on Poppler) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1084643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1310564] Re: pdftops can't handle mixed portrait/landscape documents
(Official support for Ubuntu 14.04 ended in April 2019). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1310564 Title: pdftops can't handle mixed portrait/landscape documents Status in poppler package in Ubuntu: Fix Released Bug description: I am trying to convert (parts of) a PDF document containing mixed portrait and landscape pages to ps with fixed page sizes (so I can feed it to psbook ... | psnup -2 ...), but pdftops can't handle that: 1. wget http://www.st.com/web/en/resource/technical/document/datasheet/DM00102166.pdf 2. evince DM00102166.pdf Note that pages 44ff contain tables in landscape mode 3. pdftops -paper A4 DM00102166.pdf 4. evince DM00102166.ps Note that pages 44ff are now empty, with: (evince:6788): Gdk-CRITICAL **: gdk_pixbuf_get_from_surface: assertion 'width > 0 && height > 0' failed This may or may not be related to https://bugs.freedesktop.org/show_bug.cgi?id=72312 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: poppler-utils 0.24.5-2ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 21 12:56:08 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) SourcePackage: poppler UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1310564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1310564] Re: pdftops can't handle mixed portrait/landscape documents
This is now working correctly on Ubuntu 18.04.5 LTS with poppler-utils 0.62.0-2ubuntu2.12 ** Changed in: poppler (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1310564 Title: pdftops can't handle mixed portrait/landscape documents Status in poppler package in Ubuntu: Fix Released Bug description: I am trying to convert (parts of) a PDF document containing mixed portrait and landscape pages to ps with fixed page sizes (so I can feed it to psbook ... | psnup -2 ...), but pdftops can't handle that: 1. wget http://www.st.com/web/en/resource/technical/document/datasheet/DM00102166.pdf 2. evince DM00102166.pdf Note that pages 44ff contain tables in landscape mode 3. pdftops -paper A4 DM00102166.pdf 4. evince DM00102166.ps Note that pages 44ff are now empty, with: (evince:6788): Gdk-CRITICAL **: gdk_pixbuf_get_from_surface: assertion 'width > 0 && height > 0' failed This may or may not be related to https://bugs.freedesktop.org/show_bug.cgi?id=72312 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: poppler-utils 0.24.5-2ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 21 12:56:08 2014 InstallationDate: Installed on 2014-04-14 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) SourcePackage: poppler UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1310564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1583881] Re: package texlive-latex-base-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in p
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. This bug was reported some time ago and there have been many changes in Ubuntu since that time. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: texlive-base (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1583881 Title: package texlive-latex-base-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive- doc/latex/url/url.tex.gz', which is also in package texlive-latex- recommended-doc 2013.20140215-1 Status in One Hundred Papercuts: Incomplete Status in texlive-base package in Ubuntu: Incomplete Bug description: This is occurred after upgrading to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: texlive-latex-base-doc (not installed) ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu May 19 11:06:01 2016 ErrorMessage: trying to overwrite '/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package texlive-latex-recommended-doc 2013.20140215-1 InstallationDate: Installed on 2015-12-26 (145 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: texlive-base Title: package texlive-latex-base-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package texlive-latex-recommended-doc 2013.20140215-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1583881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1182814] Re: [saucy] usb-modeswitch-data bad packaging forces removal of usb-modeswitch
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: usb-modeswitch-data (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch-data in Ubuntu. https://bugs.launchpad.net/bugs/1182814 Title: [saucy] usb-modeswitch-data bad packaging forces removal of usb- modeswitch Status in One Hundred Papercuts: Incomplete Status in usb-modeswitch-data package in Ubuntu: Incomplete Bug description: Ubuntu saucy has usb-modeswitch-data-20120815-1. Attempting to upgrade to the latest version usb-modeswitch-data-20121109-3 is impossible because of bad packaging which forces removal of usb-modeswitch!!! To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1182814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939163] [NEW] Screen splash when suspend or resume on I+N platform
Public bug reported: [Summary] 1.when clicking the the "Suspend" from the "shutdown" menu,The screen will refresh and then sleep 2.when resuming ,the desktop in buffer will appear first, and then the lock screen will appear [Reproduce] On Intel + Nvidia platform, do suspend and resume. [Expected result] 1. It should show the screen without splash. [Actual result] 1. the screen display abnormal after suspend or before resume. [Additional information] Kernel Version: 5.10.0-1038-oem Ubuntu Version: 20.04.2 LTS Image: Ubuntu Linux 20.04.2 system-manufacturer: LENOVO Platform: ThinkPad L14, P15v or T14. Nvidia: 460.91.03-0ubuntu0.20.04.1 or 470.57.02-0ubuntu0.20.04.1 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Record the suspend and resume" https://bugs.launchpad.net/bugs/1939163/+attachment/5516363/+files/suspend.mp4 -- 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/1939163 Title: Screen splash when suspend or resume on I+N platform Status in gdm3 package in Ubuntu: New Bug description: [Summary] 1.when clicking the the "Suspend" from the "shutdown" menu,The screen will refresh and then sleep 2.when resuming ,the desktop in buffer will appear first, and then the lock screen will appear [Reproduce] On Intel + Nvidia platform, do suspend and resume. [Expected result] 1. It should show the screen without splash. [Actual result] 1. the screen display abnormal after suspend or before resume. [Additional information] Kernel Version: 5.10.0-1038-oem Ubuntu Version: 20.04.2 LTS Image: Ubuntu Linux 20.04.2 system-manufacturer: LENOVO Platform: ThinkPad L14, P15v or T14. Nvidia: 460.91.03-0ubuntu0.20.04.1 or 470.57.02-0ubuntu0.20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1939163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 882522] Re: shortcut key win+D for Show desktop has changed in oneiric
Much has changed in the 10+ years since this issue was reported. Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013. In my "impish" installation of Ubuntu both "Ctrl+Alt+D" and "Super+D" show the desktop as expected. I'm closing this as "Invalid" as the issue is for a release that is so long EOL is not worth investigating. ** Changed in: hundredpapercuts Status: Confirmed => Invalid ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid -- 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/882522 Title: shortcut key win+D for Show desktop has changed in oneiric Status in One Hundred Papercuts: Invalid Status in gnome-control-center package in Ubuntu: Invalid Bug description: ubuntu 11.10 has changed the default show desktop shortcut keys from win+D to Ctrl+Alt+D To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/882522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 411964] Re: Dialog error is somewhat obtrusive in ubuntusounds
Closing as fixed, the "Yaru" theme sounds in recent releases of Ubuntu are definitely less obtrusive than in the much older releases of Ubuntu. ** Changed in: hundredpapercuts Status: Triaged => Fix Released ** Changed in: ubuntu-sounds (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-sounds in Ubuntu. https://bugs.launchpad.net/bugs/411964 Title: Dialog error is somewhat obtrusive in ubuntusounds Status in One Hundred Papercuts: Fix Released Status in ubuntu-sounds package in Ubuntu: Fix Released Bug description: The dialog error is somewhat obstrusive and loud when in deep concetration on a project. Could this be changed to be more subtle less obstrusive sound like the sound incorporated in the freedesktop sound theme? To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/411964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916341] Re: poppler-utils/pdfimages list function names the wrong color in output table
This bug report is missing system information and log files that will assist in diagnosing the cause of the problem. Please run apport- collect 1916341 to add that information to this bug report. Please also attach a file with which this problem can be reproduced. ** Changed in: poppler (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1916341 Title: poppler-utils/pdfimages list function names the wrong color in output table Status in poppler package in Ubuntu: Incomplete Bug description: When running: $ pdfimages -list grayscale-document.pdf the output is: ``` page num type width height color comp bpc enc interp object ID x-ppi y-ppi size ratio 1 0 image2556 3288 rgb 3 8 jpeg no 7 0 301 300 200K 0.8% 2 1 image2556 3288 rgb 3 8 jpeg no12 0 301 300 275K 1.5% 3 2 image2556 3288 rgb 3 8 jpeg no17 0 301 300 395K 0.8% 4 3 image2556 3288 rgb 3 8 jpeg no22 0 301 300 583K 2.8% 5 4 image2556 3288 rgb 3 8 jpeg no27 0 301 300 317K 1.3% ... ``` "rgb" is incorrect, which is evident after running: 'pdfimages -all -f 1 -l 1 grayscale-document.pdf foo && identify -format "%[type]" foo-000.jpg', which correctly outputs "Grayscale". Strangely, when "pdfimages -list" is fed a bilevel document, it states that every page has color "gray". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1916341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 508220] Re: Lucid alpha 2: first 21 characters of Synaptic "Applying changes" status line are italic
This issue is for Lucid Lynx, which reached EOL in 2013 for desktop packages. I vote we close this issue as WONTFIX (I don't have permission to set WONTFIX status on this issue). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/508220 Title: Lucid alpha 2: first 21 characters of Synaptic "Applying changes" status line are italic Status in gtk+2.0 package in Ubuntu: New Status in synaptic package in Ubuntu: Fix Released Bug description: Lucid alpha 2: first 21 characters of Synaptic "Applying changes" status line (e.g. Preparing blahpackage0-dev) are italic, while the rest of the characters are not. This isn't a major issue, and is purely cosmetic. Screenshots: http://azabani.com/images/lucid-synaptic-italic-1 http://azabani.com/images/lucid-synaptic-italic-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/508220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 192508] Re: mouse keys too easy to accidently turn on
There seems to be something missing from my edit of comment #111 so Although the shortcut of Shift+NumLock still exists in the current development release (impish) there has been no comment from anyone affected by this issue in the last eight days since my comment #111. Also, as there has been no discussion regarding this issue for over seven years now I'm closing this bug report with a status of "Opinion" as it is not something that seems to have affected any users in that time. ** No longer affects: hundredpapercuts ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Opinion ** Changed in: vino Status: Incomplete => Opinion ** Changed in: gnome-control-center Status: Incomplete => Opinion ** Changed in: xorg-server Status: Incomplete => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/192508 Title: mouse keys too easy to accidently turn on Status in gnome-control-center: Opinion Status in vino: Opinion Status in X.Org X server: Opinion Status in xorg-server package in Ubuntu: Opinion Bug description: I am using Hardy Heron and several times now I have tried to use my number pad only to discover that they now move the mouse. I don't know if there is a short cut key I am hitting on accident, but it is rather annoying. Then sometimes when I disable mouse keys, the numlock becomes switched so that the system thinks numlock is on when the light is off and vice-versa. Update: the shortcut is: shift+num-lock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/192508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938930] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Boot Kernel 5.8.0-63 works. -- 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/1938930 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After auto upgrading to the new Nvidia driver, I keep getting the "system crashed" message. The linux kernel 5.11.00-generic doesn't boot at all with this new nvidia driver. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Wed Aug 4 21:42:36 2021 InstallationDate: Installed on 2021-06-30 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939003] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938930 *** https://bugs.launchpad.net/bugs/1938930 ** This bug has been marked a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build -- 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/1939003 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: After installing this update, there were problems with booting the ubuntu. I tried to recover using grub menu and it worked. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 10:24:38 2021 InstallationDate: Installed on 2021-05-31 (66 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1939003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939069] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938930 *** https://bugs.launchpad.net/bugs/1938930 ** This bug has been marked a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build -- 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/1939069 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: nvidia 340 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 19:11:35 2021 InstallationDate: Installed on 2021-06-25 (40 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1939069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939039] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938930 *** https://bugs.launchpad.net/bugs/1938930 ** This bug has been marked a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build -- 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/1939039 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: System nofification of bug. I don't know anything more. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 06:39:04 2021 InstallationDate: Installed on 2021-03-11 (147 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1939039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938980] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938930 *** https://bugs.launchpad.net/bugs/1938930 ** This bug has been marked a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build -- 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/1938980 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: nil ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 09:25:01 2021 InstallationDate: Installed on 2021-08-01 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938980/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938981] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938930 *** https://bugs.launchpad.net/bugs/1938930 ** This bug has been marked a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build -- 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/1938981 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: weather applet crashed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Wed Aug 4 20:45:39 2021 InstallationDate: Installed on 2020-07-19 (381 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938984] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938930 *** https://bugs.launchpad.net/bugs/1938930 ** This bug has been marked a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build -- 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/1938984 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 08:33:49 2021 InstallationDate: Installed on 2020-08-09 (360 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938991] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938930 *** https://bugs.launchpad.net/bugs/1938930 ** This bug has been marked a duplicate of bug 1938930 nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build -- 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/1938991 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 12:30:00 2021 InstallationDate: Installed on 2021-04-21 (106 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938984] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
** Description changed: - System crash report popped up when using Firefox. - No other visible sign of the problem. - ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 08:33:49 2021 InstallationDate: Installed on 2020-08-09 (360 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: - dpkg 1.19.7ubuntu3 - apt 2.0.6 + dpkg 1.19.7ubuntu3 + apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1938984 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 08:33:49 2021 InstallationDate: Installed on 2020-08-09 (360 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build 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/1938984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
Hi, Since a few weeks, I have a problem with Thunderbird (current version 78.12) and Ubuntu Dock / Dash to Dock in Ubuntu 21.10 : When I write a new message and send it, after the message window has closed, its red dot remains near Thunderbird button on the Ubuntu dock - there are 2 dots: the one of main TB window (receipt box) and a second one as if there was another window still opened. But if I switch to another application - Firefox, Gedit, Nautilus, no matter… - and then with the mouse (left button) click on Thunderbird icon, desktop freezes completely, I have to manually close the computer and restart it. All is frozen, mouse nor Alt-Tab don't work, but if for example Radiotray was active, I can still hear the audio program live. If I just roll the middle button on the mouse to switch on Thunderbird and not click, it doesn't freeze. But to be back on TB main window, I must before minimize all other applications, then run somewhere in TB interface (not on Dash button), or roll is useless and doesn't show Thunderbird. If I open a window for a new message, don't send it and just close it, only one red dot stays and no freeze, even with a left button click. I also report the bug upstream. Crash logs : Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: Object St.Bin (0x55c216acf060), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: == Stack trace for context 0x55c213c2c1d0 == Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: #0 7ffe8ca71020 b /home/valeryan24/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (4f2dda5e470 @ 208) Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: Object St.Bin (0x55c216acf060), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: == Stack trace for context 0x55c213c2c1d0 == Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: Object St.Bin (0x55abc2039d10), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: == Stack trace for context 0x55abc1b471d0 == Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: #0 7ffc34c41bd0 b /home/valeryan24/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (329752c5e470 @ 208) Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: Object St.Bin (0x55abc2039d10), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: == Stack trace for context 0x55abc1b471d0 == Jul 16 10:17:15 valeryan24-desktop systemd[2161]: app-gnome-firefox-6287.scope: Deactivated successfully. \00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00Jul Thanks for the help above, hope it will be resolved soon ! -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
Problem till present after upgrade to 78,13,0 -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938832] Re: After sending a message, 2 red dots stay on Ubuntu dock and clicking on Thunderbird icon freezes everything
*** This bug is a duplicate of bug 1932328 *** https://bugs.launchpad.net/bugs/1932328 ** This bug has been marked a duplicate of bug 1932328 Thunderbird under Wayland does not correctly close (or manage) windows -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1938832 Title: After sending a message, 2 red dots stay on Ubuntu dock and clicking on Thunderbird icon freezes everything Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Hi, Since a few weeks, I have a problem with Thunderbird (current version 78.12) and Ubuntu Dock / Dash to Dock in Ubuntu 21.10 : When I write a new message and send it, after the message window has closed, its red dot remains near Thunderbird button on the Ubuntu dock - there are 2 dots: the one of main TB window (receipt box) and a second one as if there was another window still opened. But if I switch to another application - Firefox, Gedit, Nautilus, no matter… - and then with the mouse (left button) click on Thunderbird icon, desktop freezes completely, I have to manually close the computer and restart it. All is frozen, mouse nor Alt-Tab don't work, but if for example Radiotray was active, I can still hear the audio program live. If I just roll the middle button on the mouse to switch on Thunderbird and not click, it doesn't freeze. If I open a window for a new message, don't send it and just close it, only one red dot stays and no freeze, even with a left button click. I also report the bug upstream. Crash logs : Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: Object St.Bin (0x55c216acf060), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: == Stack trace for context 0x55c213c2c1d0 == Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: #0 7ffe8ca71020 b /home/valeryan24/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (4f2dda5e470 @ 208) Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: Object St.Bin (0x55c216acf060), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: == Stack trace for context 0x55c213c2c1d0 == Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: Object St.Bin (0x55abc2039d10), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: == Stack trace for context 0x55abc1b471d0 == Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: #0 7ffc34c41bd0 b /home/valeryan24/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (329752c5e470 @ 208) Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: Object St.Bin (0x55abc2039d10), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: == Stack trace for context 0x55abc1b471d0 == Jul 16 10:17:15 valeryan24-desktop systemd[2161]: app-gnome-firefox-6287.scope: Deactivated successfully. \00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00Jul Thanks for your help ! To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1938832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938832] Re: After sending a message, 2 red dots stay on Ubuntu dock and clicking on Thunderbird icon freezes everything
*** This bug is a duplicate of bug 1932328 *** https://bugs.launchpad.net/bugs/1932328 Exactly same problem as bug #1932328. See discussion and provisional solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1938832 Title: After sending a message, 2 red dots stay on Ubuntu dock and clicking on Thunderbird icon freezes everything Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Hi, Since a few weeks, I have a problem with Thunderbird (current version 78.12) and Ubuntu Dock / Dash to Dock in Ubuntu 21.10 : When I write a new message and send it, after the message window has closed, its red dot remains near Thunderbird button on the Ubuntu dock - there are 2 dots: the one of main TB window (receipt box) and a second one as if there was another window still opened. But if I switch to another application - Firefox, Gedit, Nautilus, no matter… - and then with the mouse (left button) click on Thunderbird icon, desktop freezes completely, I have to manually close the computer and restart it. All is frozen, mouse nor Alt-Tab don't work, but if for example Radiotray was active, I can still hear the audio program live. If I just roll the middle button on the mouse to switch on Thunderbird and not click, it doesn't freeze. If I open a window for a new message, don't send it and just close it, only one red dot stays and no freeze, even with a left button click. I also report the bug upstream. Crash logs : Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: Object St.Bin (0x55c216acf060), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: == Stack trace for context 0x55c213c2c1d0 == Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: #0 7ffe8ca71020 b /home/valeryan24/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (4f2dda5e470 @ 208) Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: Object St.Bin (0x55c216acf060), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: == Stack trace for context 0x55c213c2c1d0 == Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: Object St.Bin (0x55abc2039d10), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: == Stack trace for context 0x55abc1b471d0 == Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: #0 7ffc34c41bd0 b /home/valeryan24/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (329752c5e470 @ 208) Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: Object St.Bin (0x55abc2039d10), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: == Stack trace for context 0x55abc1b471d0 == Jul 16 10:17:15 valeryan24-desktop systemd[2161]: app-gnome-firefox-6287.scope: Deactivated successfully. \00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00Jul Thanks for your help ! To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1938832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938832] Re: After sending a message, 2 red dots stay on Ubuntu dock and clicking on Thunderbird icon freezes everything
*** This bug is a duplicate of bug 1932328 *** https://bugs.launchpad.net/bugs/1932328 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1938832 Title: After sending a message, 2 red dots stay on Ubuntu dock and clicking on Thunderbird icon freezes everything Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Hi, Since a few weeks, I have a problem with Thunderbird (current version 78.12) and Ubuntu Dock / Dash to Dock in Ubuntu 21.10 : When I write a new message and send it, after the message window has closed, its red dot remains near Thunderbird button on the Ubuntu dock - there are 2 dots: the one of main TB window (receipt box) and a second one as if there was another window still opened. But if I switch to another application - Firefox, Gedit, Nautilus, no matter… - and then with the mouse (left button) click on Thunderbird icon, desktop freezes completely, I have to manually close the computer and restart it. All is frozen, mouse nor Alt-Tab don't work, but if for example Radiotray was active, I can still hear the audio program live. If I just roll the middle button on the mouse to switch on Thunderbird and not click, it doesn't freeze. If I open a window for a new message, don't send it and just close it, only one red dot stays and no freeze, even with a left button click. I also report the bug upstream. Crash logs : Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: Object St.Bin (0x55c216acf060), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: == Stack trace for context 0x55c213c2c1d0 == Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: #0 7ffe8ca71020 b /home/valeryan24/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (4f2dda5e470 @ 208) Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: Object St.Bin (0x55c216acf060), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: == Stack trace for context 0x55c213c2c1d0 == Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: Object St.Bin (0x55abc2039d10), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: == Stack trace for context 0x55abc1b471d0 == Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: #0 7ffc34c41bd0 b /home/valeryan24/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (329752c5e470 @ 208) Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: Object St.Bin (0x55abc2039d10), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: == Stack trace for context 0x55abc1b471d0 == Jul 16 10:17:15 valeryan24-desktop systemd[2161]: app-gnome-firefox-6287.scope: Deactivated successfully. \00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00Jul Thanks for your help ! To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1938832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938683] Re: Thunderbird still running after being closed
Same problem as bug #1932328 -- 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/1938683 Title: Thunderbird still running after being closed Status in thunderbird package in Ubuntu: Confirmed Bug description: The "number of windows" indicator in the Ubuntu Dash (the orange dots to the left of the app icon) is not cleared for Thunderbird, when a new e-mail is written in a new window. Ultimately, the indicators stay visible even after Thunderbird is closed completely, and it's no longer possible to launch thunderbird by left-clicking of the dash icon (middle-click works okay). Steps to reproduce: 1. Launch Thunderbird. There is one orange dot to the left of the thunderbird icon. 2. Write an e-mail and close the e-mail window 3. Observe that there are now two orange dots to the left of the thunderbird icon. Please see the screenshot for more details. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 2 11:41:47 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-03-24 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1938683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938832] Re: After sending a message, 2 red dots stay on Ubuntu dock and clicking on Thunderbird icon freezes everything
*** This bug is a duplicate of bug 1932328 *** https://bugs.launchpad.net/bugs/1932328 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1938832 Title: After sending a message, 2 red dots stay on Ubuntu dock and clicking on Thunderbird icon freezes everything Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Hi, Since a few weeks, I have a problem with Thunderbird (current version 78.12) and Ubuntu Dock / Dash to Dock in Ubuntu 21.10 : When I write a new message and send it, after the message window has closed, its red dot remains near Thunderbird button on the Ubuntu dock - there are 2 dots: the one of main TB window (receipt box) and a second one as if there was another window still opened. But if I switch to another application - Firefox, Gedit, Nautilus, no matter… - and then with the mouse (left button) click on Thunderbird icon, desktop freezes completely, I have to manually close the computer and restart it. All is frozen, mouse nor Alt-Tab don't work, but if for example Radiotray was active, I can still hear the audio program live. If I just roll the middle button on the mouse to switch on Thunderbird and not click, it doesn't freeze. If I open a window for a new message, don't send it and just close it, only one red dot stays and no freeze, even with a left button click. I also report the bug upstream. Crash logs : Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: Object St.Bin (0x55c216acf060), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: == Stack trace for context 0x55c213c2c1d0 == Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: #0 7ffe8ca71020 b /home/valeryan24/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (4f2dda5e470 @ 208) Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: Object St.Bin (0x55c216acf060), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 2 18:41:14 valeryan24-desktop gnome-shell[2311]: == Stack trace for context 0x55c213c2c1d0 == Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: Object St.Bin (0x55abc2039d10), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: == Stack trace for context 0x55abc1b471d0 == Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: #0 7ffc34c41bd0 b /home/valeryan24/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036 (329752c5e470 @ 208) Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: Object St.Bin (0x55abc2039d10), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jul 9 00:00:10 valeryan24-desktop gnome-shell[2445]: == Stack trace for context 0x55abc1b471d0 == Jul 16 10:17:15 valeryan24-desktop systemd[2161]: app-gnome-firefox-6287.scope: Deactivated successfully. \00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00Jul Thanks for your help ! To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1938832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938683] Re: Thunderbird still running after being closed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- 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/1938683 Title: Thunderbird still running after being closed Status in thunderbird package in Ubuntu: Confirmed Bug description: The "number of windows" indicator in the Ubuntu Dash (the orange dots to the left of the app icon) is not cleared for Thunderbird, when a new e-mail is written in a new window. Ultimately, the indicators stay visible even after Thunderbird is closed completely, and it's no longer possible to launch thunderbird by left-clicking of the dash icon (middle-click works okay). Steps to reproduce: 1. Launch Thunderbird. There is one orange dot to the left of the thunderbird icon. 2. Write an e-mail and close the e-mail window 3. Observe that there are now two orange dots to the left of the thunderbird icon. Please see the screenshot for more details. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 2 11:41:47 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-03-24 (130 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1938683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939058] Re: autopkgtest failure "stacking/override-redirect.metatest" on armhf
Also seems to be failing occasionally upstream: https://gitlab.gnome.org/vanvugt/mutter/-/jobs/1440204 -- 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/1939058 Title: autopkgtest failure "stacking/override-redirect.metatest" on armhf Status in mutter package in Ubuntu: New Bug description: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/m/mutter/20210805_091629_afb25@/log.gz Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x43 not ok 18 stacking/override-redirect.metatest 15: stacking: expected='1/2 | 1/1', actual='| 1/1 1/2' From the test history on armhf, it appears this particular test case intermittently passes or fails about half the time. Other architectures have been passing all tests reliably without errors. Presumably the stacking order is non-deterministic on armhf for some reason? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1939058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU
** Description changed: - [Steps to reproduce] + [Impact] + Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes. + + [Fix] + Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total. + + [Test case] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. - 3. Run below command to launch glxgear + 3. Run below command to launch glxgears Cmd> DRI_PRIME=1 glxgears -info - [Expected result] - The image is not distrorted while running the glxgears + * Expected result + The image is not distorted while running the glxgears - [Actual result] - The image is distrorted while running the glxgears + * Actual result + The image is distorted while running the glxgears + + [Where things might go wrong] + This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms. + --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1937988 Title: The image is distorted while use iGPU rendering and output via AMD GPU Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Status in mesa source package in Focal: New Status in mesa source package in Hirsute: New Bug description: [Impact] Image is distorted with PRIME, caused by mismatch in stride alignment between intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes. [Fix] Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits in total. [Test case] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgears Cmd> DRI_PRIME=1 glxgears -info * Expected result The image is not distorted while running the glxgears * Actual result The image is distorted while running the glxgears [Where things might go wrong] This is a regression caused by the intel driver, so the backports merely fix what got broken. Regressions would only manifest on hybrid graphics platforms. --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
