[Bug 1947187] Re: [amdgpu] Graphics corruption during modal dialog dimming on Xorg
No the gsettings did not help, also not after a reboot. -- 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/1947187 Title: [amdgpu] Graphics corruption during modal dialog dimming on Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947187/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
I just found that this problem is not present in Debian testing, even if they have the same version of both mutter and ibus. Something seems to make Xwayland start at login, and hence ibus-x11 is also running. That speaks against using im-config to work around it, since im-config is used by both Debian and Ubuntu. I think we need to ask the Ubuntu desktop folks for advice. -- 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/1946969 Title: ibus-x11 does not start automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1947187] Re: Running in xorg unreadable firefox password request
Does this work around the problem? gsettings set org.gnome.mutter attach-modal-dialogs false ** Tags added: amdgpu ** Summary changed: - Running in xorg unreadable firefox password request + [amdgpu] Graphics corruption during modal dialog dimming ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Summary changed: - [amdgpu] Graphics corruption during modal dialog dimming + [amdgpu] Graphics corruption during modal dialog dimming on Xorg -- 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/1947187 Title: [amdgpu] Graphics corruption during modal dialog dimming on Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947187/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1947185] Re: Wayland does not initially display conky output
This is almost certainly a bug in conky, since countless other apps support Wayland sessions just fine. Reassigning. ** Package changed: wayland (Ubuntu) => mutter (Ubuntu) ** Summary changed: - Wayland does not initially display conky output + GNOME on Wayland does not initially display conky output ** Package changed: mutter (Ubuntu) => conky (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/1947185 Title: GNOME on Wayland does not initially display conky output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1947185/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1947187] [NEW] [amdgpu] Graphics corruption during modal dialog dimming
You have been subscribed to a public bug: If I use xorg and Firefox asks for the master password that small window is unreadable and distorted. See the screenshot. If I type in the password blindly everything is working again. The problem does not exist with Wayland, but that one has another issue :( ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 13:14:41 2021 DistUpgraded: 2021-10-14 11:46:37,562 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2021-10-09 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_57vi20@/vmlinuz-5.13.0-19-generic root=ZFS=rpool/ROOT/ubuntu_57vi20 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago) dmi.bios.date: 03/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.50 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.50:bd03/12/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 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: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug impish ubuntu -- [amdgpu] Graphics corruption during modal dialog dimming https://bugs.launchpad.net/bugs/1947187 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 1947185] [NEW] Wayland does not initially display conky output
You have been subscribed to a public bug: Starting Ubuntu with wayland does not initially display the .conkyrc file. Only after a change in that file, conky restarts the display and .conkyrc is displayed. Conky has been started according to the system monitor. I doubled the time before starting conky, but that did not help. If I change the display to xorg, .conkyrc displays directly as expected. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libwayland-bin (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 12:58:20 2021 DistUpgraded: 2021-10-14 11:46:37,562 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2021-10-09 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_57vi20@/vmlinuz-5.13.0-19-generic root=ZFS=rpool/ROOT/ubuntu_57vi20 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago) dmi.bios.date: 03/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.50 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.50:bd03/12/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 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: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu wayland-session -- Wayland does not initially display conky output https://bugs.launchpad.net/bugs/1947185 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 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]
Thanks! That one was waiting for sponsorship almost nine months. -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915910] Re: evince does not print
Thanks Karsten, it works! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]
$ dput gnome-shell-extension-desktop-icons_20.04.0-3\~ubuntu20.04.4_source.changes Trying to upload package to ubuntu Checking signature on .changes gpg: /tmp/pkgs/focal/gnome-shell-extension-desktop-icons_20.04.0-3~ubuntu20.04.4_source.changes: Valid signature from 1E918B66765B3E31 Checking signature on .dsc gpg: /tmp/pkgs/focal/gnome-shell-extension-desktop-icons_20.04.0-3~ubuntu20.04.4.dsc: Valid signature from 1E918B66765B3E31 Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading gnome-shell-extension-desktop-icons_20.04.0-3~ubuntu20.04.4.dsc: done. Uploading gnome-shell-extension-desktop-icons_20.04.0-3~ubuntu20.04.4.debian.tar.xz: done. Uploading gnome-shell-extension-desktop-icons_20.04.0-3~ubuntu20.04.4_source.buildinfo: done. Uploading gnome-shell-extension-desktop-icons_20.04.0-3~ubuntu20.04.4_source.changes: done. Successfully uploaded packages. -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234]
I sponsored the patch in comment #28 after updating the changelog as some new versions of that package came out. -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798166] Re: “Mouse battery low” notification can't be disabled
This has been fixed on the GNOME side. Can we have this backported? I'm willing to do the backport, if it will get merged. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1943488] Re: when typeing too fast in the search line searching stops to work
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/1943488 Title: when typeing too fast in the search line searching stops to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1943488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1943488] Re: when typeing too fast in the search line searching stops to work
I am facing the exact same error in the exact same configuration $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ~perebal-sze, thank you for sharing about cutting and pasting the search text in step 4. I hadn't know it before. It works for me as well. -- 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/1943488 Title: when typeing too fast in the search line searching stops to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1943488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
> When that reaches Debian, there is a risk that Ubuntu's desktop team won't accept to keep mozc in main (and on the ISO). I think so too. Unfortunately the Qt renderer and Gtk renderer seem to be exclusive at the moment. We still need Gtk renderer. > > However ibus-x11 process is doubled, it is ok? > Yeah, I saw that and assumed that it won't hurt... Is that duplication avoided with your idea with xrefresh (a command whose existence I wasn't aware of)? If it is, maybe that's a better approach. Thanks confirm. I agree to adopt im-config approach. Please SRU it. -- 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/1946969 Title: ibus-x11 does not start automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
On 2021-10-14 15:43, Ikuya Awashiro wrote: >> It would be good if any of you could submit an upstream GNOME issue. > I think it is not mutter or gnome-shell issue but ibus-mozc issue. > ibus-mozc should work under wayland session. > Latest Mozc renderer was completely re-written. > https://github.com/google/mozc/commit/3b3068e924e17f8820a35899f105f2ef838d0535 > I will try it later. Hmm.. My thoughts in response to that: * The commit message says: "Initial implementation of Qt-based renderer". When that reaches Debian, there is a risk that Ubuntu's desktop team won't accept to keep mozc in main (and on the ISO). Please remember that mozc-utils-gui is already not in main due to the qt dependencies. * I assumed that the issue may be present also for other IBus IMs, which is why I proposed a general workaround in im-config. But if it's a pure mozc thing, it may be better to let the ibus-mozc package install a separate autostart file in line with what you and Mitsuya discuss above. On 2021-10-14 15:46, Mitsuya Shibata wrote: > However ibus-x11 process is doubled, it is ok? Yeah, I saw that and assumed that it won't hurt... Is that duplication avoided with your idea with xrefresh (a command whose existence I wasn't aware of)? If it is, maybe that's a better approach. Anyway, thanks both for confirming that the proposal in the PPA works. But I'm not sure ATM that doing it in im-config is right. -- 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/1946969 Title: ibus-x11 does not start automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945061] Re: gdm3 crashed with SIGSEGV in ensure_display_for_seat()
Upstream proposed a fix in https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/160 and describe the crash as being an issue when neither wayland nor xorg is working. Could someone describe in which kind of setup they encounter the error? -- 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/1945061 Title: gdm3 crashed with SIGSEGV in ensure_display_for_seat() To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1945061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945061] Re: gdm3 crashed with SIGSEGV in ensure_display_for_seat()
** Changed in: gdm3 (Ubuntu) Milestone: ubuntu-21.10 => impish-updates -- 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/1945061 Title: gdm3 crashed with SIGSEGV in ensure_display_for_seat() To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1945061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
Hi Gunnar, > In the meantime im-config is the natural package for a workaround. This PPA: It works for me. Thank you for your quick response! However ibus-x11 process is doubled, it is ok? PIDPGID SID TTY STAT TIME COMMAND 140014001400 ?Ssl0:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu (snip) 143814381438 ?Ssl0:12 /usr/bin/gnome-shell 172414381438 ?Sl 0:00 /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.EDN3A1 -listen 4 -listen 5 -displayfd 6 -initfd 7 177117711438 ?Sl 0:01 ibus-daemon --panel disable -r --xim 179217711438 ?Sl 0:00 /usr/libexec/ibus-dconf 179417711438 ?Sl 0:01 /usr/libexec/ibus-extension-gtk3 184417711438 ?Sl 0:00 /usr/lib/ibus-mozc/ibus-engine-mozc --ibus 184717711438 ?SLl0:00 /usr/lib/mozc/mozc_server (snip) 170416961400 ?Sl 0:00 /usr/libexec/ibus-x11 --kill-daemon 177617761776 ?Ssl0:00 /usr/libexec/gsd-xsettings 180317711438 ?Sl 0:00 /usr/libexec/ibus-x11 --kill-daemon 180713021302 ?Sl 0:00 /usr/libexec/ibus-portal -- 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/1946969 Title: ibus-x11 does not start automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946969] Re: ibus-x11 does not start automatically
Thank you for your comments! > However to reproduce this behaviour, you need to reboot on twice, isn't it? Yes. You are right. Always right. > It would be good if any of you could submit an upstream GNOME issue. I think it is not mutter or gnome-shell issue but ibus-mozc issue. ibus-mozc should work under wayland session. Latest Mozc renderer was completely re-written. https://github.com/google/mozc/commit/3b3068e924e17f8820a35899f105f2ef838d0535 I will try it later. > Please let me know if you consider the im-config change to be sufficient, and > also if you see any adverse side effects. This change works great for me. Thank you for your work. -- 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/1946969 Title: ibus-x11 does not start automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1947149] Re: dock auto-hide off but hidden on login
** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu) -- 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/1947149 Title: dock auto-hide off but hidden on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1947149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1947149] [NEW] dock auto-hide off but hidden on login
You have been subscribed to a public bug: When the dock is set to "Auto-hide the Dock" = Off, the dock will un- hide when logging on. Both on boot and after locking the user. This causes any open full-screen windows to move and resize as needed. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 21.10 Release:21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell-extension-ubuntu-dock: Installed: 70~ubuntu3 Candidate: 70~ubuntu3 Version table: *** 70~ubuntu3 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish/main i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen The dock to start displayed (un-hidden) as per the settings. And not move. 4) What happened instead The dock appears from the left, as if hidden. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- dock auto-hide off but hidden on login https://bugs.launchpad.net/bugs/1947149 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1941983] Re: gnome-shell crashes on display hotplug
*** This bug is a duplicate of bug 1871262 *** https://bugs.launchpad.net/bugs/1871262 Your system log ends with: [ 327.514699] ozmodiar gnome-shell[3502]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed So yes I think bug 1871262 is appropriate even if the steps are different. It gives the dozen or so affected people a central location to discuss their findings. Also the rarity of the crash provides no evidence that the original cause was ever fixed. And indeed the issue is still open upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/930 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #930 https://gitlab.gnome.org/GNOME/mutter/-/issues/930 -- 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/1941983 Title: gnome-shell crashes on display hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1941983/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1947132] Re: gnome-shell crashed with SIGSEGV in XRRGetCrtcInfo() from update_outputs() from _cogl_xlib_renderer_connect() from _cogl_winsys_renderer_connect() from connect_custom_winsys()
** Summary changed: - /usr/bin/gnome-shell:11:XRRGetCrtcInfo:update_outputs:_cogl_xlib_renderer_connect:_cogl_winsys_renderer_connect:connect_custom_winsys + gnome-shell crashed with SIGSEGV in XRRGetCrtcInfo() from update_outputs() from _cogl_xlib_renderer_connect() from _cogl_winsys_renderer_connect() from connect_custom_winsys() ** Tags added: nvidia ** Summary changed: - gnome-shell crashed with SIGSEGV in XRRGetCrtcInfo() from update_outputs() from _cogl_xlib_renderer_connect() from _cogl_winsys_renderer_connect() from connect_custom_winsys() + [nvidia] gnome-shell crashed with SIGSEGV in XRRGetCrtcInfo() from update_outputs() from _cogl_xlib_renderer_connect() from _cogl_winsys_renderer_connect() from connect_custom_winsys() -- 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/1947132 Title: [nvidia] gnome-shell crashed with SIGSEGV in XRRGetCrtcInfo() from update_outputs() from _cogl_xlib_renderer_connect() from _cogl_winsys_renderer_connect() from connect_custom_winsys() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947132/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1947132] [NEW] [nvidia] gnome-shell crashed with SIGSEGV in XRRGetCrtcInfo() from update_outputs() from _cogl_xlib_renderer_connect() from _cogl_winsys_renderer_connect() from connect_custom_wins
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/2acefc8fc5476d2f02ae266fe5892dd8bffc1fed contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic hirsute impish nvidia -- 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/1947132 Title: [nvidia] gnome-shell crashed with SIGSEGV in XRRGetCrtcInfo() from update_outputs() from _cogl_xlib_renderer_connect() from _cogl_winsys_renderer_connect() from connect_custom_winsys() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947132/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1936826] Re: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199]
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1936826 Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1936826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1947130] Re: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer:JSObject::writeBarrierPost from js::InternalBarrierMethods from js::InternalBarrierMethods from js::BarrierMethods
** Summary changed: - /usr/bin/gnome-shell:11:js::gc::Cell::storeBuffer:JSObject::writeBarrierPost:js::InternalBarrierMethods:js::InternalBarrierMethods:js::BarrierMethods + gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer:JSObject::writeBarrierPost from js::InternalBarrierMethods from js::InternalBarrierMethods from js::BarrierMethods -- 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/1947130 Title: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer:JSObject::writeBarrierPost from js::InternalBarrierMethods from js::InternalBarrierMethods from js::BarrierMethods To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1947130] [NEW] gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer:JSObject::writeBarrierPost from js::InternalBarrierMethods from js::InternalBarrierMethods from js::BarrierMethods
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/22d9d466c0128fadf2a5a14e35cac37531875d1e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: impish -- 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/1947130 Title: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer:JSObject::writeBarrierPost from js::InternalBarrierMethods from js::InternalBarrierMethods from js::BarrierMethods To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947130/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1941983] Re: gnome-shell crashes on display hotplug
*** This bug is a duplicate of bug 1871262 *** https://bugs.launchpad.net/bugs/1871262 Are you sure about duplicate status? This is a new issue I'm experiencing with 21.10, and the reproduction steps are different (I see nothing in the other bug about display hotplug). -- 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/1941983 Title: gnome-shell crashes on display hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1941983/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946970] Re: Memory leak in gnome-shell after lock and unlock the screen
Memory in gnome-shell does not get freed quickly because of JavaScript garbage collection. Memory usage will tend to grow slowly and plateau. Significant drops are rare, but I would not consider it a leak unless you see growth continuing above 500MB. Starting at 200MB is normal. If you are still concerned about the memory use then please also check to see if you get the same behaviour with no extensions at all. -- 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/1946970 Title: Memory leak in gnome-shell after lock and unlock the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946970] Re: Memory leak in gnome-shell after lock and unlock the screen
I switch off all the extensions except for Ubuntu ones. Every lock/unlock action raises the memory usage by ~10MB until it reaches ~280MB. Super-A (app overview) raised further the usage. After a while something happend (Not lock/unlock or Super-A) and now the memory usage of gnome-shell is 302MB and is not changing. What is the normal memory usage of gnome-shell? Is it normal (what I have described) or it should stay at the beginning level? -- 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/1946970 Title: Memory leak in gnome-shell after lock and unlock the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 781931] Re: New windows are moved to front but don't take focus
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: compiz (Ubuntu Precise) Status: Confirmed => Won't Fix -- 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/781931 Title: New windows are moved to front but don't take focus To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/781931/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 840942] Re: set_size_request is ignored [update-manager details is one line]
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: gtk+3.0 (Ubuntu Precise) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/840942 Title: set_size_request is ignored [update-manager details is one line] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/840942/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 842768] Re: Cups notifies "printer ' xxx ' may be not connected " although printer is OK and printing is OK too
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: gnome-settings-daemon (Ubuntu Precise) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/842768 Title: Cups notifies "printer ' xxx ' may be not connected " although printer is OK and printing is OK too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/842768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 871083] Re: gzip -9n sometimes generates a different output file on different architectures
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: libtasn1-3 (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/871083 Title: gzip -9n sometimes generates a different output file on different architectures To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/871083/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 874660] Re: Two finger scrolling works poorly - utouch to blame
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: evince (Ubuntu Precise) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/874660 Title: Two finger scrolling works poorly - utouch to blame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/874660/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 879528] Re: Display utility doesn't offer to use nvidia-settings with proprietary drivers installed?
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: gnome-control-center (Ubuntu Precise) Status: Triaged => Won't Fix -- 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/879528 Title: Display utility doesn't offer to use nvidia-settings with proprietary drivers installed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/879528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 959838] Re: [regression] gnome-dvb-control crashes on startup with TypeError in __create_toolbar(): __init__() got an unexpected keyword argument 'icon_widget'
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: pygobject (Ubuntu Precise) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/959838 Title: [regression] gnome-dvb-control crashes on startup with TypeError in __create_toolbar(): __init__() got an unexpected keyword argument 'icon_widget' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/959838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 960967] Re: eog crashed with SIGSEGV in do_rot_270()
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: libjpeg-turbo (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/960967 Title: eog crashed with SIGSEGV in do_rot_270() To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/960967/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 971353] Re: power : gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: gnome-settings-daemon (Ubuntu Precise) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/971353 Title: power : gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/971353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 987220] Re: [Dell Inspiron 1720] System does not power off reliably when "Shut Down" chosen from GUI
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Precise) Status: Incomplete => Won't Fix -- 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/987220 Title: [Dell Inspiron 1720] System does not power off reliably when "Shut Down" chosen from GUI To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/987220/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1028518] Re: Fn keys such as brightness and volume stopped working after update
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: gnome-settings-daemon (Ubuntu Precise) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1028518 Title: Fn keys such as brightness and volume stopped working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1028518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1039292] Re: Yelp 3.4 doesn't correctly handle conditional platform processing
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: yelp (Ubuntu Precise) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1039292 Title: Yelp 3.4 doesn't correctly handle conditional platform processing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1039292/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
