[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
#23 yes. My laptop is a Nvidia+Intel hybrid laptop. Internal screen now wakes up (although the lockscreen blurred background is shown black, but that's a minor issue for me), and external one works perfectly. I never had performance issues, and once I get past the lockscreen it just works. Again, on Fedora I simply did not have such a problem. I wonder what did Canonical do on Ubuntu for this bug to appear. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977776] Re: Update gnome-shell to 42.2
This bug was fixed in the package gnome-shell - 42.2-0ubuntu1 --- gnome-shell (42.2-0ubuntu1) kinetic; urgency=medium * New upstream release (LP: #196) -- Jeremy Bicha Mon, 06 Jun 2022 20:30:49 -0400 ** Changed in: gnome-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/196 Title: Update gnome-shell to 42.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/196/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976354] Re: Jetbrains IDE doesn't focus when click from overview
*** This bug is a duplicate of bug 1969574 *** https://bugs.launchpad.net/bugs/1969574 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1969574, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1969574 [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace -- 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/1976354 Title: Jetbrains IDE doesn't focus when click from overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976354/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962630] Re: Video playback crashes with SIGSEGV in KernelDll_AllocateStates (intel-media-driver)
Upstream fix proposed: https://github.com/intel/media-driver/pull/1423 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1962630 Title: Video playback crashes with SIGSEGV in KernelDll_AllocateStates (intel-media-driver) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1962630/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977776] Re: Update gnome-shell to 42.2
** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed ** Changed in: gnome-shell (Ubuntu Jammy) Status: Triaged => In Progress -- 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/196 Title: Update gnome-shell to 42.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/196/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977655] Re: Nautilus Open Files and Save File... dialogs keep growing
Related: https://askubuntu.com/questions/1405901/ubuntu-22-04-ui-issues-in-app-file-selector-save-prompt-saving-files-and-new-w Possibly Related: https://gitlab.gnome.org/GNOME/gtk/-/issues/4136 ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4136 https://gitlab.gnome.org/GNOME/gtk/-/issues/4136 -- 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/1977655 Title: Nautilus Open Files and Save File... dialogs keep growing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1977655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1972034] Re: On browser download/save dialog, filename in name box is highlighted as if it is active, but typing doesn't edit name unless you click into the box
Works as expected in Gedit <-- Name is highlighted, starting to type changes name. Does not work: Firefox <-- Name is highlighted, starting to type does nothing. Does not work: Brave Works: VSCode Interesting... never noticed, but depending on which is doing the saving, there are two very similar looking but different save dialogs opened (see attached. Top is browser dialog, bottom is gedit dialog). ** Attachment added: "Save Dialogs: top browser, bottom Gedit" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1972034/+attachment/5595137/+files/Save%20Dialogs.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/1972034 Title: On browser download/save dialog, filename in name box is highlighted as if it is active, but typing doesn't edit name unless you click into the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1972034/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977655] Re: Nautilus Open Files and Save File... dialogs keep growing
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/1977655 Title: Nautilus Open Files and Save File... dialogs keep growing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1977655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977776] [NEW] Update gnome-shell to 42.2
Public bug reported: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.2/NEWS Test Case 1 - sudo apt install gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: GNOME GNOME Classic Ubuntu Ubuntu on Xorg Test Case 2 --- Because a GNOME Shell update years ago broke some GNOME Shell extensions, it's also requested that we do a basic test of all the extensions included in the Ubuntu repositories. https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from- universe-and-stop-auto-syncs/18437/9 Install all the extensions. Log out and then log back in. Use one of the Extensions apps to enable all the extensions. Verify that they can all be enabled without showing an error. What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-shell (Ubuntu) Importance: Low Status: Triaged ** Affects: gnome-shell (Ubuntu Jammy) Importance: Low Status: Triaged ** Tags: jammy upgrade-software-version ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => Triaged -- 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/196 Title: Update gnome-shell to 42.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/196/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923845] Re: Please compress packages with zstd by default
aptly is Fix Release in Kinetic in: aptly (1.4.0+ds1-7) unstable; urgency=medium * Team upload. * Add support for zstd compression (Closes: #1010465) ** Changed in: aptly (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1923845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977757] [NEW] tracker-extract: needs to rebuild shared objects with SHSTK support enabled
Public bug reported: When using a kernel compiled with enabled CET shadow stack on CPU supporting CET, we fail to load various shared libraries. We see the following journal messages: Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module '/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-jpeg.so': /usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-jpeg.so: rebuild shared object with SHSTK support enabled Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module '/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-pdf.so': /usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-pdf.so: rebuild shared object with SHSTK support enabled Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module '/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-tiff.so': /usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-tiff.so: rebuild shared object with SHSTK support enabled Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module '/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-xps.so': /usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-xps.so: rebuild shared object with SHSTK support enabled Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module '/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so': /usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so: rebuild shared object with SHSTK support enabled Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module '/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so': /usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so: rebuild shared object with SHSTK support enabled Jun 04 11:08:35 juro-ArcherCity tracker-extract[23678]: Could not load module '/usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so': /usr/lib/x86_64-linux-gnu/tracker-miners-3.0/extract-modules/libextract-gstreamer.so: rebuild shared object with SHSTK support enabled ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: tracker-extract 3.3.0-1 Uname: Linux 5.15.0-mvp3v8-5-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jun 6 08:31:15 2022 InstallationDate: Installed on 2022-06-03 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: tracker-miners UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1977757 Title: tracker-extract: needs to rebuild shared objects with SHSTK support enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1977757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1936302] Re: To support elanmoc driver
This bug was fixed in the package libfprint - 1:1.90.2+tod1-0ubuntu1~20.04.8 --- libfprint (1:1.90.2+tod1-0ubuntu1~20.04.8) focal; urgency=medium [ Marco Trevisan (Treviño) ] * debian/patches: Refresh * debian/patches: Cherry-pick upstream elanmoc driver support for Elan's Match on Chip devices (LP: #1936302). [ Andy Chi ] * d/p/elanmoc-Adjustments-to-protocol-change-passing-an-empty-u.patch: Cherry-pick upstream fixes for elanmoc driver (LP: #1936302) -- Marco Trevisan (Treviño) Fri, 20 May 2022 15:32:12 +0200 ** Changed in: libfprint (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1936302 Title: To support elanmoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1936302/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04
This bug was fixed in the package xdg-desktop-portal - 1.6.0-1ubuntu1 --- xdg-desktop-portal (1.6.0-1ubuntu1) focal; urgency=medium * Pass the current_filter from XDG Portal save dialogs through - d/patches/pass-current-filter-on-save.patch (lp: #1973564) -- Ted Gould Mon, 16 May 2022 10:58:47 -0500 ** Changed in: xdg-desktop-portal (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1973564 Title: File dialog doesn't return current filter in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04
This bug was fixed in the package xdg-desktop-portal-gtk - 1.6.0-1ubuntu1 --- xdg-desktop-portal-gtk (1.6.0-1ubuntu1) focal; urgency=medium * Return the current filter selected from file dialogs - d/patches/filechooser-current-filter.patch (lp: #1973564) -- Ted Gould Wed, 18 May 2022 15:30:59 +0200 ** Changed in: xdg-desktop-portal-gtk (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1973564 Title: File dialog doesn't return current filter in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1973564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1936302] Re: To support elanmoc driver
This bug was fixed in the package libfprint - 1:1.90.7+git20210222+tod1-0ubuntu4~21.10.4 --- libfprint (1:1.90.7+git20210222+tod1-0ubuntu4~21.10.4) impish; urgency=medium [ Marco Trevisan (Treviño) ] * debian/patches: Refresh * debian/patches: Cherry-pick upstream elanmoc driver support for Elan's Match on Chip devices (LP: #1936302). [ Andy Chi ] * d/p/elanmoc-Adjustments-to-protocol-change-passing-an-empty-u.patch: Cherry-pick upstream fixes for elanmoc driver (LP: #1936302) -- Marco Trevisan (Treviño) Mon, 23 May 2022 22:34:16 +0200 ** Changed in: libfprint (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1936302 Title: To support elanmoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1936302/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
I use `thread apply all bt full` to capture the gdb debug message and use `journalctl -b 0 /usr/bin/gnome-shell` to capture journal log. ** Attachment added: "gnome-shell-stack-trace-202206062108.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5595073/+files/gnome-shell-stack-trace-202206062108.tar.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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
So, attaching with gdb should happen when it's hanging, assuming that's the case I still don't see the result for `bt full` (or better `thread apply all bt full`), so that we can try to figure out where the process is hanging. As per the JS stack the one I see in logs is: 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: == Stack trace for context 0x5557c18144b0 == 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: #0 7fffd9616ef0 I resource:///org/gnome/shell/ui/workspace.js:820 (e45d6bfdbf0 @ 274) 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: #1 7fffd9616f80 I resource:///org/gnome/shell/ui/workspace.js:1409 (47907707d80 @ 264) 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: #2 7fffd9616ff0 I resource:///org/gnome/shell/ui/workspace.js:1274 (47907707830 @ 465) 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: #3 7fffd9617030 I resource:///org/gnome/shell/ui/workspace.js:1298 (479077079c0 @ 45) 六 06 16:11:11 ubuntu-XPS-13-9310 gnome-shell[1071]: #4 7fffd9617080 I self-hosted:1181 (3a3c201b0a10 @ 454) -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976554] Re: Screen auto rotates randomly after suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1976554 Title: Screen auto rotates randomly after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]
I report also this bug, which seams to be related to nvidia on Wayland. I made few test on my hybrid graphic laptop (Dell xps with GTX1050 Ti ): - Fresh Ubuntu install on Wayland (no nvidia driver): OK. - With Nvidia 510 driver, on-demand profile set, login Xorg: OK. - With Nvidia 510 driver, on-demand profile set, login with Wayland: FAILED. I got this error: Gdk-Message: 12:20:26.270: Error 71 (Protocol error) dispatching to Wayland display. I got similar result also with Nvidia profile set instead of on-demand. - With Nvidia 510 driver, INTEL profile set, login with Wayland: OK. With Flatpak app (NVIDIA/Wayland): - Install gnome-extensions with flatpak run org.gnome.Extensions: The app start BUT you I can’t access to the extensions settings. The sub-windows can’t open, I got this in logs when I press “setting” button of an listed extension: Sender gnome-shell, WL: error in client communication (pid 16887) Sender: gjs ,Error reading events from display: Protocol error Sender gnome-shell, Window manager warning: Ping serial 2322697 was reused for window W118, previous use was for window W111. -I also test another similar app on flatpak call com.mattjakeman.ExtensionManager: The app start but when trying to open extensions settings, the sub-windows does not open and I got this logs too: Sender: gjs, Error flushing display: Protocol error Sender gnome-shell, WL: error in client communication (pid 17125) -- 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/1965563 Title: gnome-extensions-app fails to start [Error reading events from display: Protocol error] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
Hi @3v1n0, [steps] 1. Install gnome-shell-dbgsym_42.1-0ubuntu0.1_amd64.ddeb, libglib2.0-dev-bin-dbgsym_2.72.1-1_amd64.ddeb, libmutter-test-10-dbgsym_42.1-0ubuntu1_amd64.ddeb, libglib2.0-0-dbgsym_2.72.1-1_amd64.ddeb, libglib2.0-tests-dbgsym_2.72.1-1_amd64.ddeb, mutter-10-tests-dbgsym_42.1-0ubuntu1_amd64.ddeb, libglib2.0-bin-dbgsym_2.72.1-1_amd64.ddeb, libmutter-10-0-dbgsym_42.1-0ubuntu1_amd64.ddeb and mutter-dbgsym_42.1-0ubuntu1_amd64.ddeb 2. Plug external monitor 3. Execute `sudo gdb -p $(pidof /usr/bin/gnome-shell) /usr/bin/gnome-shell` 4. Ctrl+C and `bt` 5. `call (void) gjs_dumpstack()` [journal log] 六 06 16:23:27 ubuntu-XPS-13-9310 gnome-shell[1071]: The offending callback was SourceFunc(). 六 06 16:23:27 ubuntu-XPS-13-9310 gnome-shell[1071]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter a ctor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked . ** Attachment added: "20220606-gnome-shell.log.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5595044/+files/20220606-gnome-shell.log.tar.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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977678] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1977678/+attachment/5595038/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1977678 Title: Crash on close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1977678/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977678] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1977678/+attachment/5595037/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1977678 Title: Crash on close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1977678/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1977678] Re: Crash on close
apport information ** Tags added: apport-collected jammy ** Description changed: ``` GNU Image Manipulation Program version 2.10.30 git-describe: GIMP_2_10_30 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 11.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-gcn/usr --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=2 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.2.0 (Ubuntu 11.2.0-16ubuntu1) # Libraries # using babl version 0.1.92 (compiled against version 0.1.88) using GEGL version 0.4.34 (compiled against version 0.4.34) using GLib version 2.72.1 (compiled against version 2.71.1) using GdkPixbuf version 2.42.8 (compiled against version 2.42.6) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.50.6 (compiled against version 1.50.3) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Speicherzugriffsfehler Stack trace: ``` # Stack traces obtained from PID 5848 - Thread 5848 # [New LWP 5849] [New LWP 5850] [New LWP 5851] [New LWP 5852] [New LWP 5853] [New LWP 5854] [New LWP 5855] [New LWP 5856] [New LWP 5857] [New LWP 5858] [New LWP 5859] [New LWP 5871] [New LWP 5872] [New LWP 5887] [New LWP 6094] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __GI___libc_read (nbytes=256, buf=0x7ffee02ebe90, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7fddcd062e80 (LWP 5848) "gimp-2.10" __GI___libc_read (nbytes=256, buf=0x7ffee02ebe90, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7fddcc65f640 (LWP 5849) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7fddcbe5e640 (LWP 5850) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7fddc365d640 (LWP 5851) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7fddcb65d640 (LWP 5852) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7fddcae5c640 (LWP 5853) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7fddca65b640 (LWP 5854) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7fddc9e5a640 (LWP 5855) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7fddc9659640 (LWP 5856) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 10 Thread 0x7fddc8e58640 (LWP 5857) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 11 Thread 0x7fddc3fff640 (LWP 5858) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7fddc2e5c640 (LWP 5859) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13 Thread 0x7fdd69ffb640 (LWP 5871) "gmain" 0x7fddcdd63d7f in __GI___poll (fds=0x56243753e0a0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 14 Thread 0x7fdd6a7fc640 (LWP 5872) "gdbus" 0x7fddcdd63d7f in __GI___poll (fds=0x56243755c030, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 15 Thread 0x7fdd26ff5640 (LWP 5887) "async" syscall () at
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Hi Jorge, do you have an external monitor connected via HDMI and an internal display (a laptop with hybrid graphics Intel + NVIDIA) too? I can't test this right now. My original bug report is a big messy. It is more like three separate issue into one. 1. Internal monitor doesn't wake up after sleep 2. External monitor doesn't get turned off during sleep 3. Poor performance. https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971149 All described issues aren't present in an Xorg session. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
