[Bug 1968792] Re: After F10 menu Enter key opens file instead of menu action
Same thing on Nautilus 42.1 running on Manjaro Testing. So must be upstream. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1968792 Title: After F10 menu Enter key opens file instead of menu action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
This bug was fixed in the package gnome-control-center - 1:41.4-1ubuntu11 --- gnome-control-center (1:41.4-1ubuntu11) jammy; urgency=medium * debian/patches/ubuntu/sharing-rdp/*.path: - Backport RDP support (LP: #1968518) * debian/patches/ubuntu/update-vnc-key.patch: - Dropped as fixed in the above backport. -- Robert Ancell Wed, 13 Apr 2022 11:38:18 +1200 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968747] Re: Cherry-pick fixes from the gnome-42 branch
This bug was fixed in the package epiphany-browser - 42.1-1 --- epiphany-browser (42.1-1) unstable; urgency=medium * New upstream release (LP: #1968747) -- Jeremy Bicha Tue, 12 Apr 2022 15:07:56 -0400 ** Changed in: epiphany-browser (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1968747 Title: Cherry-pick fixes from the gnome-42 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1968747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
This bug was fixed in the package gnome-user-docs - 41.5-1ubuntu2 --- gnome-user-docs (41.5-1ubuntu2) jammy; urgency=medium * debian/patches/update_sharing-desktop.page.patch: - Update to the GNOME 42 version to reflect significant changes to the gnome-remote-desktop and gnome-control-center packages (LP: #1968518). -- Gunnar Hjalmarsson Tue, 12 Apr 2022 21:48:35 +0200 ** Changed in: gnome-user-docs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968812] [NEW] email content display blank
Public bug reported: The mail preview and if double click opening the email in a seperate window are both blank, all other toolbars and panes seem fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 19:56:50 2022 InstallationDate: Installed on 2022-04-02 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "evolution_broken.png" https://bugs.launchpad.net/bugs/1968812/+attachment/5580269/+files/evolution_broken.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1968812 Title: email content display blank To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1968812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
Uploaded as 1:41.4-1ubuntu11 ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968663] Re: [impish] Screen freeze when unsuspending and entering password
** Summary changed: - Screen freeze when unsuspending and entering password + [impish] Screen freeze when unsuspending and entering password -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968663 Title: [impish] Screen freeze when unsuspending and entering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968663/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968099] Re: gnome shell crashes after disconnecting external monitors
If you have any unexplained crash that doesn't leave a crash file then please: 1. When the crash occurs, wait 10 seconds and then reboot. 2. Run: journalctl -b-1 > prevboot.txt 3. Attach the resulting text file here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968099 Title: gnome shell crashes after disconnecting external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961747] Re: [nvidia] Black screen (with grey squares) after resume from sleep
Nvidia mentioned that driver 510.60 fixes a bug that sounds like this one... https://www.nvidia.com/download/driverResults.aspx/187162/en-us But don't download it from there. Please use the 'Additional Drivers' app instead. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961747 Title: [nvidia] Black screen (with grey squares) after resume from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961747] Re: [nvidia] Black screen (with grey squares) after resume from sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1961747 Title: [nvidia] Black screen (with grey squares) after resume from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961747] Re: Black screen after resume from sleep
Sounds like an extreme case of bug 1876632. ** Tags added: jammy nvidia suspend-resume ** Summary changed: - Black screen after resume from sleep + [nvidia] Black screen after resume from sleep ** Summary changed: - [nvidia] Black screen after resume from sleep + [nvidia] Black screen (with grey squares) after resume from sleep -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1961747 Title: [nvidia] Black screen (with grey squares) after resume from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967452] Re: [nvidia] When resume from suspend, monitor keep blinking and don't show the whole desktop.
*** This bug is a duplicate of bug 1961747 *** https://bugs.launchpad.net/bugs/1961747 ** This bug has been marked a duplicate of bug 1961747 [nvidia] Black screen (with grey squares) after resume from sleep -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1967452 Title: [nvidia] When resume from suspend, monitor keep blinking and don't show the whole desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967452/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968792] Re: After F10 menu Enter key opens file instead of menu action
Filed upstream on your behalf. https://gitlab.gnome.org/GNOME/nautilus/-/issues/2225 ** Also affects: nautilus (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2225 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2225 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1968792 Title: After F10 menu Enter key opens file instead of menu action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968705] Re: one external monitor unresponsive after suspend
*** This bug is a duplicate of bug 1964120 *** https://bugs.launchpad.net/bugs/1964120 ** This bug is no longer a duplicate of private bug 1968712 ** This bug has been marked a duplicate of bug 1964120 gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968705 Title: one external monitor unresponsive after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy
Yes, details were minimal because I just wanted to get a block-proposed bug in so we could discuss more. Initial thinking is that we should remove the 440d6f9ecc151fbcf8c852d500c5cc5add168b94 patch. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1968809 Title: Verify that the gdm cherry-picks are wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968792] Re: After F10 menu Enter key opens file instead of menu action
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1968792 Title: After F10 menu Enter key opens file instead of menu action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy
This bug probably needs more details. If you're referring to disabling Wayland GDM for some GPUs then: VMs: yes GPUless server chips: yes Nvidia: no Hybrid: no (because bug 1964037 / bug 1959888 fixes those) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1968809 Title: Verify that the gdm cherry-picks are wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968809] [NEW] Verify that the gdm cherry-picks are wanted for jammy
Public bug reported: I need to check to make sure that we do in fact want the gdm3 cherry- picks for Jammy so filing this bug to hold things for a moment. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1968809 Title: Verify that the gdm cherry-picks are wanted for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1738838 Title: Bluetooth icon shows "Off" and the only option given below it is "Turn Off" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968780] Re: evolution crashes at startup
*** This bug is a duplicate of bug 1966418 *** https://bugs.launchpad.net/bugs/1966418 ** This bug has been marked a duplicate of bug 1966418 [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1968780 Title: evolution crashes at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1968780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968792] [NEW] After F10 menu Enter key opens file instead of menu action
Public bug reported: When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate the menu, but when pressing Enter, does not execute the selected menu action. IE: if folder is selected, press F10, menu pops down arrow to choose "open in terminal", press enter, Nautilus navigates to the selected folder instead of opening terminal in the current location. Also with files: if text (or any) file is selected, press F10, menu pops, choose any action with arrows, press enter, gedit (or whatever) opens selected file. Tested all actions then selecting files or folders, same result. Expected behavior: After pressing F10, focus should be on the menu that just pops up, until ESC is pressed or mouse clicks somewhere else or focus is shifted by other means, so when pressing ENTER action gets performed. IE: file or folder is selected, press F10, down arrow to select PROPERTIES, press ENTER, PROPERTIES of selected item are shown. Also tried with SPACEBAR (just in case), but the result is the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 23:08:24 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Menu shown" https://bugs.launchpad.net/bugs/1968792/+attachment/5580221/+files/Screenshot%20from%202022-04-12%2023-26-59.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1968792 Title: After F10 menu Enter key opens file instead of menu action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Hello Yao, or anyone else affected, Accepted iio-sensor-proxy into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iio-sensor- proxy/2.8-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1963628 Title: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966178] Re: Screen-privacy couldn't work
Ok, got it... It was due to the triple-buffering patch that was ignoring the pending update, see https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1428961 ** Changed in: gnome-control-center (Ubuntu) Status: New => Won't Fix ** Changed in: mutter (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966178 Title: Screen-privacy couldn't work To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
** Changed in: gnome-user-docs (Ubuntu) Status: Triaged => Fix Committed ** Changed in: gnome-user-docs (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968780] [NEW] evolution crashes at startup
Public bug reported: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 evolution: Installiert: 3.44.0-1 Installationskandidat: 3.44.0-1 Versionstabelle: *** 3.44.0-1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Evolution crashes at startup with the following error: Speicherzugriffsfehler (Speicherabzug geschrieben) Expected behaviour: Evolution starts. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 21:41:44 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-04-12 (0 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1968780 Title: evolution crashes at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1968780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968778] [NEW] epiphany-browser does not start
Public bug reported: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 epiphany-browser: Installiert: 42.0-1 Installationskandidat: 42.0-1 Versionstabelle: *** 42.0-1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Tried to start epiphany, it crashes during startup. Expected: Starts without problems. ###:~$ epiphany-browser Speicherzugriffsfehler (Speicherabzug geschrieben) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: epiphany-browser 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 21:30:51 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: epiphany-browser UpgradeStatus: Upgraded to jammy on 2022-04-12 (0 days ago) ** Affects: epiphany-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1968778 Title: epiphany-browser does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1968778/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968359] Crash report cannot be processed
*** This bug is a duplicate of bug 1964120 *** https://bugs.launchpad.net/bugs/1964120 Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for libjpeg-turbo8 no debug symbol package found for libcrypt1 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968359/+attachment/5578292/+files/CoreDump.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968359 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968359/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968359] ThreadStacktrace.txt
*** This bug is a duplicate of bug 1964120 *** https://bugs.launchpad.net/bugs/1964120 ** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968359/+attachment/5580096/+files/ThreadStacktrace.txt ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968359 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968359/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968359] gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964120 *** https://bugs.launchpad.net/bugs/1964120 Stacktrace: #0 0x7f6f10b36a7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffe867583a0 StacktraceSource: #0 0x7f6f10b36a7c in ?? () StacktraceTop: ?? () -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968359 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968359/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961747] Re: Black screen after resume from sleep
Updated today to 22.04 beta with latest updates. Same problem. ** Package changed: nvidia-graphics-drivers (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1961747 Title: Black screen after resume from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961747] [NEW] Black screen after resume from sleep
You have been subscribed to a public bug: Problem: Screen is black when resuming from sleep. Only a few grey squares are shown. Software: Latest Ubuntu 22.04 (updated 21st of february). Nvidia 495 drivers. Hardware: Ryzen 5900x, Nvidia 3080ti GPU. Configuration: Wayland at login screen. Analysis: Maybe Video RAM is purged during sleep and then it is not restored when resuming. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Black screen after resume from sleep https://bugs.launchpad.net/bugs/1961747 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967853] Crash report cannot be processed
*** This bug is a duplicate of bug 1964458 *** https://bugs.launchpad.net/bugs/1964458 Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for libcrypt1 no debug symbol package found for libjpeg-turbo8 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1967853/+attachment/5577311/+files/CoreDump.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967853 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967853/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967853] ThreadStacktrace.txt
*** This bug is a duplicate of bug 1964458 *** https://bugs.launchpad.net/bugs/1964458 ** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1967853/+attachment/5580036/+files/ThreadStacktrace.txt ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967853 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967853/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967853] gnome-shell crashed with SIGSEGV
*** This bug is a duplicate of bug 1964458 *** https://bugs.launchpad.net/bugs/1964458 Stacktrace: #0 0x7ff155766f44 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0 StacktraceSource: #0 0x7ff155766f44 in ?? () StacktraceTop: ?? () -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967853 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967853/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968099] Re: gnome shell crashes after disconnecting external monitors
Just happened again. Disconnecting external monitors lead to crash in which after log in the session was lost. I do not see a related crash in /var/crash/... nor anything at https://errors.ubuntu.com/user/ID -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968099 Title: gnome shell crashes after disconnecting external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968390] Re: JS ERROR: TypeError: this.window_container is null
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968390 Title: JS ERROR: TypeError: this.window_container is null To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968747] [NEW] Cherry-pick fixes from the gnome-42 branch
Public bug reported: I'm cherry-picking some fixes from the gnome-42 branch since epiphany 42.1 won't be released before 22.04 LTS. Uploading directly to jammy instead of to unstable to not further delay Epiphany 42.0 reaching Testing. ** Affects: epiphany-browser (Ubuntu) Importance: Undecided Status: In Progress ** Tags: jammy upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1968747 Title: Cherry-pick fixes from the gnome-42 branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1968747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968364] Re: [FFe] Switch gnome-shell to use gnome-bluetooth3
MIR Team approved at today's meeting so I'm setting to Triaged. ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: gnome-bluetooth (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1968364 Title: [FFe] Switch gnome-shell to use gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1968364/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968743] [NEW] Rhythmbox Close & Quit shortcuts not working (Ctrl+W / Ctrl+Q) in Xubuntu
Public bug reported: Very simple to repro. Starting Xubuntu 20.04 (bug still present in 22.04): 1. Open rhythmbox 2. Hit Ctrl+Q (Quit) or Ctrl+W (Close window) 3. Nothing happens This was working fine in Xubuntu 18.04 This bug can be reproduced in the Live USB version (i.e. "Try Xubuntu") Upstream claims it should be working and it works under GNOME: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1961 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 Uname: Linux 5.13.7+ x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Apr 12 11:39:22 2022 InstallationDate: Installed on 2017-12-22 (1572 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: rhythmbox UpgradeStatus: Upgraded to focal on 2022-04-07 (4 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1968743 Title: Rhythmbox Close & Quit shortcuts not working (Ctrl+W / Ctrl+Q) in Xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1968743/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968364] Re: [FFe] Switch gnome-shell to use gnome-bluetooth3
Is the MIR ready to go? If the MIR team is fine with moving gnome- bluetooth3 into main as it is right now, consider this FFe approved - but the deadline for any of this is, let's say, end of the day before Final Freeze. So yeah, consider it a conditional +1 - if MIR team is +1 and the package goes to main, this is instantly 'Triaged'. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1968364 Title: [FFe] Switch gnome-shell to use gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1968364/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
Okay, thank you. In that case, please proceed o/ ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: gnome-user-docs (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968364] Re: [FFe] Switch gnome-shell to use gnome-bluetooth3
** Description changed: Why It's Needed --- This will fix LP: #1738838 gnome-shell 42 stable release updates for Ubuntu 22.04 will be easier since we don't have to revert all the bluetooth-related commits. Why, More Details - GNOME Shell 42 uses API from the new gnome-bluetooth library to fix LP: #1738838 The API changes were not practical to forward-port (switch to a new GListModel API). Ubuntu's gnome-shell packaging had to revert ~6 commits to keep using the older gnome-bluetooth library, which is more awkward to maintain. Because of how GNOME Shell extensions work, if an extension tries to modify the bluetooth part of the system status menu in the top right corner of the screen, the extension may not work because Ubuntu's GNOME Shell 42 is different than what every other distro provides. I assess this concern as very low since extensions are "use at your own risk" and there aren't many working bluetooth extensions. The new gnome-bluetooth3 series has an expanded build test suite and has received lots of fixes that won't be ported to the older gnome-bluetooth series. Why It Wasn't Done Before - We needed to get a MIR to allow gnome-bluetooth3 in to main while the old gnome-bluetooth is still in main. See https://launchpad.net/bugs/1964600 . Sorry this is a bit late. Still about a week before Final Freeze to revert these changes is issues are identified but we're feeling confident this will be a worthwhile improvement. Other Change If this FFE is approved, we'd like to go ahead and drop the gir package built by the old gnome-bluetooth since nothing is using it. It is believed that gnome-shell is the only user of the gnome-bluetooth gir bindings. + + https://tracker.debian.org/media/packages/g/gnome- + bluetooth/changelog-3.34.5-8 + + Build Log for gnome-shell + - + This is from our git master so it includes a few other pending changes + + https://launchpad.net/~ubuntu- + desktop/+archive/ubuntu/ppa/+sourcepub/13423631/+listing-archive-extra -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1968364 Title: [FFe] Switch gnome-shell to use gnome-bluetooth3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1968364/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
Yes, it is buildable. I was running it yesterday. It was just missing one build-dependency so I added it and have done a PPA build for you: https://launchpad.net/~ubuntu- desktop/+archive/ubuntu/ppa/+sourcepub/13423577/+listing-archive-extra -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968099] Re: gnome shell crashes after disconnecting external monitors
So far so good, will keep an eye and report back in case I experience a bad crash again. I do sometimes get logged out after messing with monitors still but after log in all applications are still there. Don't know if this is expected, I'd say not, but as the work is not lost it does not seem "critical". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968099 Title: gnome shell crashes after disconnecting external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968705] Re: one external monitor unresponsive after suspend
*** This bug is a duplicate of bug 1968712 *** https://bugs.launchpad.net/bugs/1968712 ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of private bug 1968712 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968705 Title: one external monitor unresponsive after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1562140] Re: When importing raw+jpg files shotwell needlessly creates _embedded.jpg files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shotwell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1562140 Title: When importing raw+jpg files shotwell needlessly creates _embedded.jpg files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1562140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968705] Re: one external monitor unresponsive after suspend
It just happened after booting with monitors disconnected and then connecting the monitor. Ubuntu offered to file a bug with more information https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968712 collected on its own so I will try to close this one and we can follow there. Edit: apologies, it seems I don't know how to close the bug here, none of options seems appropriate -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968705 Title: one external monitor unresponsive after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
New fix proposed in: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360 ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1967274 Title: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968709] Re: gjs-console assert failure: free(): invalid pointer
*** This bug is a duplicate of bug 1946165 *** https://bugs.launchpad.net/bugs/1946165 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1946165, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968709/+attachment/5579897/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968709/+attachment/5579899/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968709/+attachment/5579903/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968709/+attachment/5579904/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968709/+attachment/5579905/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968709/+attachment/5579906/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968709/+attachment/5579907/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1946165 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1968709 Title: gjs-console assert failure: free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1968709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968705] [NEW] one external monitor unresponsive after suspend
Public bug reported: Ubuntu 22.04 Beta, Gnome, Wayland. Intel graphic Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel Device-2: Acer Integrated Camera type: USB driver: uvcvideo Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1 compositor: gnome-shell v: 42.0 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1: 1920x1080~60Hz 2: 2560x1440~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 22.0.1 Laptop connected to two external monitors: laptop -> USB C / DisplayPort -> First monitor -> DisplayPort chain -> Second monitor After putting laptop to sleep (while monitors are connected) and waking it up the second monitor is unresponsive: - in Settings -> Display Gnome reports it as being on and working - turning it off and on does not bring it back - after switching it on in settings it for a moment appears in the overview (Drag displays to match physical display setup ...) but then instantly disappear. After experiencing the "error" now I see following in /var/crash ll /var/crash/ .rw-r- 4.2M rskolasinski 12 Apr 10:37 _usr_libexec_gsd-xsettings.1000.crash .rw-rw-r--0 rskolasinski 12 Apr 10:37 _usr_libexec_gsd-xsettings.1000.upload .rw--- 37 whoopsie 12 Apr 10:37 _usr_libexec_gsd-xsettings.1000.uploaded .rw-r- 1.8M rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.crash .rw-rw-r--0 rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.upload .rw--- 37 whoopsie 12 Apr 10:53 _usr_libexec_ibus-x11.1000.uploaded One auto-reported itself to https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1968695 but seems unrelated to this specific issue. Second one system suggest it may be https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1968478 so I am not sure any are related to the issue I am trying to report. Happy to provide any required information as this would potentially be blocking from using this once it reach stable. Last bit of information: it also happens on live usb of 22.04 beta (tested yesterday) and does not happen on live usb of fedora 36 beta (wanted to check as it also has gnome 42). All tested under wayland. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968705 Title: one external monitor unresponsive after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968099] Re: gnome shell crashes after disconnecting external monitors
Please check to see if the problem still occurs when the standard Ubuntu extensions are enabled. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968099 Title: gnome shell crashes after disconnecting external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968099] Re: gnome shell crashes after disconnecting external monitors
This one seems not to happen any more after removing the said extensions (system-monitor-next...) but I also disabled dash and icon desktop. I am still experiencing another issue related to monitors but it is probably separate so will follow in another report. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968099 Title: gnome shell crashes after disconnecting external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968698] [NEW] Desktop portal's file chooser displays disabled 'Save' button after switching directory
Public bug reported: ## System Ubuntu 22.04 xdg-desktop-portal-gtk 1.14.0-1build1 ## How to reproduce 1. Open confined app, snap or flatpak, e.g. Firefox 2. Open file chooser, e.g. by pressing Ctrl + S 3. In the opened file chooser: Enter a subdirectory by clicking on it in the central file list widget 4. Observe the 'Save' button turning to a disabled state (see the attached screenshot) ## How to work around You can work around the issue by editing the file name in the text input at the top of the window. E.g. by adding and then removing a single character. ## Expected results No such problem should occur. There's probably some state management issue going on. Ubuntu 21.10 did not show such behavior for me. ## Misc observations A flatpak app showed the same problem. ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1968698 Title: Desktop portal's file chooser displays disabled 'Save' button after switching directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1968698/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968402] Re: Ubuntu 20.04.3 boots to black screen, no TTY available
Thanks for the bug report. Please be careful to report only one issue per bug report. When you have trouble with the USB not booting, that's usually a bad copy of the ISO on the USB or a slightly faulty thumb drive. Very common. Always have a different thumb drive handy to try. I suggest the best place to start is with Ubuntu 22.04 (http://cdimage.ubuntu.com/daily-live/current/). If you have trouble with that then we would like to know ASAP. If you want to stick with 20.04 instead then please try 20.04.4 (https://ubuntu.com/download/desktop) and choose a single issue to discuss, presumably the first issue you face. ** No longer affects: xorg-server (Ubuntu) ** No longer affects: nvidia-graphics-drivers-450 (Ubuntu) ** Package changed: mutter (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968402 Title: Ubuntu 20.04.3 boots to black screen, no TTY available To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1968402/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968402] Re: Ubuntu 20.04.3 boots to black screen, no TTY available
** No longer affects: wayland (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** No longer affects: xorg (Ubuntu) ** No longer affects: grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968402 Title: Ubuntu 20.04.3 boots to black screen, no TTY available To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1968402/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968694] Re: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()
*** This bug is a duplicate of bug 1965897 *** https://bugs.launchpad.net/bugs/1965897 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1965897, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1968694/+attachment/5579799/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1968694/+attachment/5579801/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1968694/+attachment/5579805/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1968694/+attachment/5579806/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1968694/+attachment/5579807/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1968694/+attachment/5579810/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1968694/+attachment/5579811/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1965897 gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) from meta_window_actor_queue_destroy() from meta_compositor_real_remove_window() from meta_window_unmanage() from meta_display_unmanage_windows() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968694 Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968694/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966808] Re: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument)
Fixed upstream in: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2359 ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Committed ** No longer affects: gnome-shell (Ubuntu) ** Tags added: fixed-in-42.1 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966808/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966808] Re: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument)
The fix is also coming in the next Ubuntu update: https://salsa.debian.org/gnome-team/mutter/-/commit/c0222e9b -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966808 Title: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966808/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967826] Re: Text entry borders are malformed (but only when using Yaru theme)
** Summary changed: - Search entry border is jagged and clipped (when using Yaru theme) + Text entry borders are malformed (but only when using Yaru theme) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1967826 Title: Text entry borders are malformed (but only when using Yaru theme) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1967826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
Ok, thank you for all the great context everyone! I am still worried that all of this lands so late and just a few days before Final Freeze. That being said, as I see that Gunnar seems to be +1 on having this change in jammy, I would generally be fine with this FFe. However, I see that the build FTBFS in the PPA that Robert provided?! https://launchpad.net/~robert-ancell/+archive/ubuntu/gnome-control-center This does feel great I must say. Have these changes not been tested before then? Can it be made buildable and testable before we accept the FFe and UIFe? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968395] Re: [impish] Wayland is with the black screen when I share it
What are you using to share the screen? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968395 Title: [impish] Wayland is with the black screen when I share it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968395/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968513] Re: GNOME login fails to stay in the overview if DING is enabled
I think we might need to improve on a related fix that went in 8 months ago: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1925 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968513 Title: GNOME login fails to stay in the overview if DING is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968513/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968663] Re: Screen freeze when unsuspending and entering password
After the problem happens next, please: 1. Reboot. 2. Run: journalctl -b-1 > prevboot.txt 3. Attach the resulting text file here. 4. Check for crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968663 Title: Screen freeze when unsuspending and entering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968663/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968451] Re: GNOME launcher folder icons and labels very small
Upstream bugs: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5097 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3450 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5097 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5097 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3450 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3450 ** Tags added: quality visual ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968451 Title: GNOME launcher folder icons and labels very small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968451/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968663] [NEW] Screen freeze when unsuspending and entering password
You have been subscribed to a public bug: Sometimes after unsuspending and entering the login screen password, the right spinning icon stops and the whole system hangs. I am able to SSH into the machine and look at the logs, but everything seems pretty normal and I can't find relevant errors. Do note that my internal webcam connection is kinda wonky but I don't know if that's related. Pressing Alt+F# to switch to a TTY doesn't work. I have to force power down every time by holding the power button. This happens once in a while. I'm using Wayland and Gnome. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.54 Tue Feb 8 04:42:21 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 20:05:34 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Hewlett-Packard Company TU117M [GeForce GTX 1650 Mobile / Max-Q] [103c:8601] InstallationDate: Installed on 2021-10-15 (178 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgroot-lvroot--ubuntu--21.10 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 018W12 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn018W12:rvrA02:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.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-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug freeze impish ubuntu wayland-session -- Screen freeze when unsuspending and entering password https://bugs.launchpad.net/bugs/1968663 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968428] Re: AMD HD7970 Error: no ums support in radeon modual
It sounds like "nomodeset" is actually causing the newest error: no UMS support in Radeon module That's expected with nomodeset and probably not a bug. So we should instead find out why you had a hang with only a cursor at the top left of the screen. Please: 1. Remove "nomodeset". 2. Reboot (expecting it to fail). 3. Reboot again with "nomodeset" and run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Summary changed: - AMD HD7970 Error: no ums support in radeon modual + After installation it just hangs with a cursor at the top left of the screen ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968428 Title: After installation it just hangs with a cursor at the top left of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1968428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968425] Re: Workspace switching interruptible with trackpad overview gesture
I wonder if this is related to an old bug 1878408 (different GNOME version). ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968425 Title: Workspace switching interruptible with trackpad overview gesture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968425/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
Some more upstream reasoning for switching from VNC to RDP: Some releases ago an RDP backend was added to gnome-remote-desktop, using the FreeRDP's RDP implementation, while the VNC backend uses the LibVNCServer project's implementation. Over time, the RDP backend significantly surpassed the abilities of the VNC backend, both in terms of features and performance, and we had contemplated switching the default backend in the past already. It's also worth noting that the RDP protocol doesn't have awkward limitations on password length in the commonly used authentication mechanism. Also, from an "outsiders" point of view, FreeRDP feels like a much more active project than LibVNCServer, and RDP is simply a more capable protocol. A side note about security of the VNC backend: the original intention with the VNC backend was to more or less mimic the functionality of vino, which had an out-dated fork of LibVNCServer bundled with it. Having a fork of a library that tends to get its fair share of CVE's didn't feel like a good idea, so the upstream library was used directly. However, to get the same level of encryption (anon-tls), LibVNCServer still needed to be patched. Patches were originally contributed in 2018, but has not landed yet, thus to get anon-tls encryption, distributions needs downstream patching. With the RDP backend, we both moved away from non-verifiable anon-tls as well as downstream patching. One thing that has stopped us from switching the backend in the past has been the need to re-design the settings dialog. It had been planned to change the design of said dialog for some time already, but it was a non-trivial task, since it involved more complicated steps, such as TLS key/cert generation, management and verification. For GNOME 42, however, we managed to both get designs as well as implement them in Settings, thus it made us feel like it was a good opportunity to make the switch. Originally we intended to have a "blue bar" with a note about the VNC backend being enabled, with the option of disabling it. This blue bar was disabled, after dropping the plan to try to automatically enable the VNC backend on upgrade. The primary reason for dropping this was that any risk of enabling the VNC backend by accident was too big of a risk, given the security implications of unknowingly running a VNC remote desktop server. It was also discussed whether it should be possible to configure the VNC backend as well as the RDP backend, but the design team decided against it; instead we added the command line utility 'grdctl' that allows configuration the VNC backend. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968390] Re: JS ERROR: TypeError: this.window_container is null
Looks similar to https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4324 but that was fixed in GNOME 41. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968390 Title: JS ERROR: TypeError: this.window_container is null To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968390] Re: JS ERROR: TypeError: this.window_container is null
Thanks for the bug report. I have removed most of the log messages because they are already covered by bug 1968383. So now this bug is only about: JS ERROR: TypeError: this.window_container is null ** Description changed: Ubuntu 22.04 Development A 3 finger touchpad swipe up/down gesture with 1 application open outputs a lot of JS errors and stacks to the journal. This issue may be the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1968383 but the output is somewhat different when you have more than 1 app open. This also happens with all extensions disabled, does not happen in Fedora 36. To reproduce 1. login and open terminal and watch the journal 2. perform the 3 finger swipe up gesture until the app grid displays then swipe down to go back to the desktop. 3. See journal 4. If nothing happens try opening an app, closing it and try again. - Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Button (0x56219f5b8060), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. - Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == - Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:566 (4ce0bb0ac40 @ 10) - Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == - Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:567 (4ce0bb0ac40 @ 36) - Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == - Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:570 (4ce0bb0ac40 @ 77) - Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == - Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:638 (4ce0bb0ae20 @ 23) - Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:353 (4ce0bb0a5b0 @ 62) - Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) - Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == - Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:357 (4ce0bb0a5b0 @ 87) - Apr 08 21:18:49 x1c gnome-shell[21675]: #1 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) - Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == - Apr 08 21:18:49 x1c gnome-shell[21675]: #0 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:364 (4ce0bb0a600 @ 8) - Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) - Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) - Apr 08 21:18:49 x1c gnome-shell[21675]: #3 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) - Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == - Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:160 (330c4e3cc560 @ 43) - Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a9a70 b resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23) - Apr 08 21:18:49 x1c gnome-shell[21675]: #2 56219e7257f0 i resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109) - Apr 08 21:18:49 x1c gnome-shell[21675]: #3 7ffc4c0aa640 I self-hosted:205 (330c4e3bed80 @ 272) - Apr 08 21:18:49 x1c gnome-shell[21675]: #4 56219e725750 i resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222) - Apr 08 21:18:49 x1c gnome-shell[21675]: #5 56219e7256c8 i resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105) - Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 0x56219d5b9180 == - Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Label (0x56219f5a8440), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. - Apr 08 21:18:49 x1c gnome-shell[21675]: #0 7ffc4c0a98b0 b resource:///org/gnome/shell/ui/environment.js:361 (330c4e3ccc90 @ 43) - Apr 08 21:18:49 x1c gnome-shell[21675]: #1 7ffc4c0a99a0 b resource:///org/gnome/shell/ui/environment.js:163 (330c4e3cc560 @ 91) - Apr 08 21:18:49 x1c gnome-shell[21675]: #2 7ffc4c0a9a70 b resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23) - Apr 08
[Bug 1968357] Re: While logginto unity session the message that'the system has crashed and cannot be recovered. the extentions have been disabled"
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: gnome-session (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1968357 Title: While logginto unity session the message that'the system has crashed and cannot be recovered. the extentions have been disabled" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1968357/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having b
** Summary changed: - Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. + Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566] -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
