[Bug 1968390] Re: JS ERROR: TypeError: this.window_container is null
In progress: https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/2738 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => 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/1968390 Title: JS ERROR: TypeError: this.window_container is null To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968390/+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
In progress: https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/2738 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6065 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6065 ** Changed in: gnome-shell Status: New => Unknown ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6448 => gitlab.gnome.org/GNOME/gnome-shell/-/issues #6065 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => 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/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/gnome-shell/+bug/1968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998267] Re: glib not aware of snap confinement
I've looked at the autopkgtests and the failures don't seem to be related to this change. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998267] Re: glib not aware of snap confinement
Tested glib2.0 2.72.4-0ubuntu2 in a jammy VM and working. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998267 Title: glib not aware of snap confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016743] Re: Unable to switch windows while drag-and-drop
** Package changed: 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/2016743 Title: Unable to switch windows while drag-and-drop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2016743/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016743] [NEW] Unable to switch windows while drag-and-drop
You have been subscribed to a public bug: Unable to switch windows while drag-and-drop. Atl-tab, super-tab, etc. are not working while trying to drag anything from one window to other. System configuration: Ubuntu 23.04, GNOME version 44.0 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 02:58:01 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-07 (10 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- Unable to switch windows while drag-and-drop https://bugs.launchpad.net/bugs/2016743 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 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
** Changed in: gdm Status: Unknown => Fix Released -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
Upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/808 ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #808 https://gitlab.gnome.org/GNOME/gdm/-/issues/808 ** Also affects: gdm via https://gitlab.gnome.org/GNOME/gdm/-/issues/808 Importance: Unknown Status: Unknown -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
I could not reproduce with kinetic (see my steps in bug 2016193). I went back to a clean jammy install, reproduced, then upgraded just the gdm3 packages to kinetic's versions, and the problem went away, so it seems gdm3 in isolation is the relevant difference. I took a look at the differences between the jammy and kinetic gdm3 source, and there really isn't that much different. One piece that stood out is the following, which appears to be a typo: diff -urpN gdm3-42.0/daemon/gdm-local-display-factory.c gdm3-43.0/daemon/gdm-local-display-factory.c --- gdm3-42.0/daemon/gdm-local-display-factory.c2023-04-17 15:07:42.0 -0600 +++ gdm3-43.0/daemon/gdm-local-display-factory.c2022-09-20 09:22:21.0 -0600 @@ -402,7 +402,7 @@ gdm_local_display_factory_create_transie display = gdm_local_display_new (); g_object_set (G_OBJECT (display), "session-type", session_types[0], - "supported-session-tyes", session_types, + "supported-session-types", session_types, NULL); is_initial = TRUE; } On a lark, I rebuilt the jammy version of gdm3 to use "supported- session-types" here, and that seems to have fixed the problem for me. I can reliable downgrade to the jammy version of gdm3 and reproduce, and reliably *not* reproduce the bug after installing my patched version. -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
** Attachment added: "xprop" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+attachment/5664802/+files/google-chat.xprop -- 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/2007652 Title: [snap] PWA don't launch as applications, just another chromium window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
I can verify that in Bionic (with the deb) the application shows in Gnome's task bar as a separate application, not grouped under Chromium, and that in Lunar (with the snap) it shows in Gnome's task bar grouped under the Chromium button. However, 1. Wmctrl shows that the window classes and names are consistent, --> Lunar <-- 0x01c3 0 chromium.Chromium 0x01c00011 0 crx_mdpkiolbdkhdjpekf.Chromium --> Bionic <-- 0x01c3 0 chromium-browser.Chromium-browser 0x01c00019 0 crx_mdpkiolbdkhdjpekf.Chromium-browserChat 2. The bug is absent from both Unity and Icewm (see attachments). So I think this is a regression in Gnome Shell from Ubuntu 20.04 vs Ubuntu 18.04. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ice.png" https://bugs.launchpad.net/bugs/2007652/+attachment/5664797/+files/ice.png ** Attachment added: "unity.png" https://bugs.launchpad.net/bugs/2007652/+attachment/5664798/+files/unity.png -- 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/2007652 Title: [snap] PWA don't launch as applications, just another chromium window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016708] [NEW] Characthers search through GNOME Shell is broken
Public bug reported: [ Impact ] Searching for characters in gnome shell does not bring any result [ Test Case ] - Having gnome-characters installed - Open the overview (hit super), search for "pizza" - The "pizza slice" character should show in the search results: [ Regression potential ] The shell search provider is never stopped once done. ** Affects: gnome-characters (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/2016708 Title: Characthers search through GNOME Shell is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/2016708/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965323] Re: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL
** Changed in: gnome-shell Status: Unknown => 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/1965323 Title: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_
Still crashing in accountsservice 22.08.8-1ubuntu7: https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 ** Changed in: accountsservice (Ubuntu) Status: Fix Released => Confirmed ** Changed in: accountsservice (Ubuntu) Assignee: Sebastien Bacher (seb128) => (unassigned) ** Changed in: indicator-messages (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
This is now the #1 crash in jammy. ** Tags added: jammy ** Tags removed: artful eoan groovy -- 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/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016013] Re: New windows don't get centered if Desktop Icons NG is loaded
This also explains why gnome-initial-setup is not centered on some screens. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Triaged ** Changed in: mutter (Ubuntu) Status: New => Triaged -- 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/2016013 Title: New windows don't get centered if Desktop Icons NG is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016013/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
I think we might have multiple different bugs here. The log in comment #80 sounds like this kernel bug which might occur on HDMI connections that are not 16:9 aspect: https://gitlab.freedesktop.org/drm/intel/-/issues/6153 But not everyone here seems to have an unusual aspect ratio, or even HDMI. So everyone else please follow the steps in comment #75. ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #6153 https://gitlab.freedesktop.org/drm/intel/-/issues/6153 -- 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: [i915] 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/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Next please: * More people follow the steps in comment #75. * Some people try newer kernel versions to see if/where the problem was fixed: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D -- 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: [i915] 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/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
This is looking like a kernel bug (comment #81) and increasingly unlike mutter has done anything wrong. Sounds like it is specifically about i915 HDMI handling. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Summary changed: - Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] + [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] ** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Confirmed ** Tags added: i915 -- 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: [i915] 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/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016308] Re: gnome-shell crashed with signal 6: libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
** Changed in: mutter Status: Unknown => Fix Released -- 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/2016308 Title: gnome-shell crashed with signal 6: libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage: assertion failed: (window->display->focus_window != window) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016308/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Thanks! It looks like most of the errors are in fact caused by previous errors: i915 :00:02.0: [drm:drm_atomic_crtc_check [drm]] [CRTC:45:pipe A] requesting event but off i915 :00:02.0: [drm:drm_atomic_check_only [drm]] [CRTC:45:pipe A] atomic core check failed ... KMS: [atomic] KMS update failed: drmModeAtomicCommit: Invalid argument So those could be improved, but they're not the root cause. The root cause seems to be a failure of the first frame (modeset) when waking from sleep: i915 :00:02.0: [drm:intel_hdmi_compute_clock [i915]] picking 12 bpc for HDMI output (pipe bpp: 36) i915 :00:02.0: [drm:intel_hdmi_compute_config [i915]] bad AVI infoframe i915 :00:02.0: [drm:intel_modeset_pipe_config [i915]] Encoder config failure: -22 That "-22" is the first "Invalid argument". -- 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/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016408] Re: Running all KDE apps on Wayland - apps bad working
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- 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/2016408 Title: Running all KDE apps on Wayland - apps bad working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2016408/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016387] Re: After updating to 23.04, none of the integrated shell extensions work
Thanks for the bug report. We will focus on supported extensions only here. Unsupported extensions will need to be ported to gnome-shell 44 by their respective authors... Please try deleting unsupported extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then reinstall the supported extension: sudo apt install --reinstall gnome-shell-extension-ubuntu-dock ** Package changed: gnome-shell-extension-ubuntu-dock (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-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2016387 Title: After updating to 23.04, none of the integrated shell extensions work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2016387/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016408] [NEW] Running all KDE apps on Wayland - apps bad working
You have been subscribed to a public bug: Hi, on Ubuntu 23.04 all KDE apps work not properly. When I run KDE apps (like clementine, kaffeine, smplayer), the cursor on HDPi monitor (scale 200%) is so huge than in Gnome apps. KDE apps discrespect windows decorations (like max, min, close buttons - I have them on the left site, but kde apps have it on right site). When I start smplayer, it crashes because can't play video over mplayer/mpv player...blank window and crashes. Same problems here: https://www.reddit.com/r/kde/comments/xev3jq/is_there_a_way_to_make_smplayermpv_work_under/ Solution for me is run KDE apps like: QT_QPA_PLATFORM=xcb smplayer If i try tu run application like that, everything is working properly. Can you pleas repair it on Ubuntu 23.04 for wayland? ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 16 11:16:28 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed v4l2loopback/0.12.7, 6.2.0-20-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694] InstallationDate: Installed on 2023-04-14 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230414) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=d6cce96a-9549-40b0-8d45-aeb37eabc158 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1805 dmi.board.asset.tag: Default string dmi.board.name: Z170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1805:bd05/13/2016:br5.11:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar performance ubuntu wayland-session -- Running all KDE apps on Wayland - apps bad working https://bugs.launchpad.net/bugs/2016408 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2001594] Re: Mutter crashes on xdg_activation.activate request
*** This bug is a duplicate of bug 1988256 *** https://bugs.launchpad.net/bugs/1988256 ** This bug has been marked a duplicate of bug 1988256 gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland_seat_get_grab_info() from token_can_activate() -- 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/2001594 Title: Mutter crashes on xdg_activation.activate request To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2001594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016331] Re: On Ubuntu 20.4, the PC shuts down when the screen is locked. This happens despite automatic suspend being off.
Thanks for the bug report. Next time the problem happens, after restarting, please run: journalctl -b-1 > prevboot.txt gsettings list-recursively org.gnome.settings-daemon.plugins.power > settings.txt and attach the resulting text files here. ** Tags added: focal ** Changed in: gnome-power-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/2016331 Title: On Ubuntu 20.4, the PC shuts down when the screen is locked. This happens despite automatic suspend being off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/2016331/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016364] Re: The GDM3 login welcome message is not showing after editing "/etc/gdm3/greeter.dconf-defaults" and setting the option banner-message-enable to true.
** Tags added: 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/2016364 Title: The GDM3 login welcome message is not showing after editing "/etc/gdm3/greeter.dconf-defaults" and setting the option banner- message-enable to true. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2016364/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs