[Bug 2051371] Re: Backspace in gnome-terminal often deletes cluster
> It's never the terminal emulator (whether GNOME Terminal or any other terminal app) that decides what to print on a backspace keypress. The only thing it does is that it tells over the tty line that the backspace key has been pressed. Makes sense. However, the user thinks of gnome-terminal because that's what he runs... > If your input method cannot generate the symbols you need, and you need to press backspace as a workaround to get that, moreover, you need to rely on one particular behavior of backspace, then I'd argue that it's all the fault of your input method, it should be able to produce straight away whatever you wish to end up with. Unfortunately that's not always possible. Please take a look at the wiki page under [1]. With complex writing systems there's more than one way to write a word which look 'correct' on the screen, but the order of the code points is different [2]. Not very good if you search for that word. Therefore Keyman allows to define keyboards that can auto-correct words so that you end up with the same order of the code points regardless which way you type [3]. And that requires to replace some codepoints typed previously. > Maybe the bug you _really_ wanted to report is that gnome-terminal doesn't use the "surrounding text" feature of input methods? That would be nice to have but until then it would be good to have backspace working properly. But as you wrote in an earlier comment that has nothing to do with gnome-terminal... [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion [2] https://www.sil.org/resources/archives/91817 [3] https://help.keyman.com/keyboard/khmer_angkor/1.0.7/KAK_Documentation_EN.pdf ** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051371 Title: Backspace in gnome-terminal often deletes cluster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2051371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051381] Re: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset()
Here's the link to the failing code (mainly for me so that I can find it again...): https://gitlab.gnome.org/GNOME/gtk/-/blame/a487deb1898ff1453168594f797d38c2b38187ac/modules/input/imwayland.c#L253 ** Package changed: gnome-terminal (Ubuntu) => gtk -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051381 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2051381/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051381] Re: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset()
> So I'm wondering, shouldn't you have filed this bug against that component, rather than gnome-terminal? I guess you're right. Sorry. I'll try or re-assign. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051381 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2051381/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051381] [NEW] gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset()
Public bug reported: When I'm using ibus-keyman with the IPA (SIL) keyboard in gnome-terminal and type n> (or just backspace after the n), gnome-terminal crashes. The reason is that in text_input_delete_surrounding_text() (modules/input/imwayland.c:253) before_length doesn't get checked. If we don't have surrounding text (as in this case) cursor_pointer is NULL and thus (cursor_pointer - before_length) results in an invalid pointer. The other question is why we don't have surrounding text, but that's a different problem. In any case we shouldn't crash in text_input_delete_surrounding_text(). I believe this is a different bug from #2036647 because of the different callstack and that we shouldn't call g_utf8_pointer_to_offset with invalid pointers. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-terminal 3.49.92-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 17:43:54 2024 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2024-01-23 (3 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) JournalErrors: Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed Jan 26 17:43:53 hostname gnome-terminal-[4907]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed Jan 26 17:44:00 hostname systemd[1623]: gnome-terminal-server.service: Main process exited, code=dumped, status=11/SEGV Jan 26 17:44:00 hostname systemd[1623]: gnome-terminal-server.service: Failed with result 'core-dump'. ProcCmdline: /usr/libexec/gnome-terminal-server ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f884099c180 :movzbl (%rsi),%ecx PC (0x7f884099c180) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_utf8_pointer_to_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users vboxsf modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2024-01-26T17:42:28.299334 separator: ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash mantic need-amd64-retrace wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051381 Title: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2051381/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051371] Re: Backspace in gnome-terminal often deletes cluster
** Description changed: If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left with ខ (U+1781). Instead it should only delete the last codepoint, U+17d2. If I have ខែ (U+1781 U+17c2) a backspace deletes only U+17c2, similarly if I have ខ្ (U+1781 U+17d2) where the backspace deletes U+17d2. Further investigations show that backspace often deletes the entire cluster, i.e. diacritic(s) plus the base character, for example with x̣́ (U+0078 U+0301 U+0323) where a backspace deletes all three codepoints. gnome-terminal should only delete the last codepoint [1]. A real live example where this behavior is problematic is when using - ibus-keyman with the Khmer Angkor keyboard. When typing xEjmr the + ibus-keyman with the Khmer Angkor keyboard [2]. When typing xEjmr the expected output is ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman does some reordering while typing to put the codepoints in a standardized order. Because gnome-terminal lacks support for surrounding text, the codepoints have to be deleted by emitting several backspace keypresses. Because of the deletion of the cluster the result in gnome- terminal is ្មែរ (U+17d2 U+1798 U+17c2 U+179a). - [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster- - deletion + [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster-deletion + [2] https://github.com/keymanapp/keyman/issues/10481 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 [modified: usr/libexec/gnome-terminal-server] ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 12:21:42 2024 InstallationDate: Installed on 2022-04-12 (653 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051371 Title: Backspace in gnome-terminal often deletes cluster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2051371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051371] Re: Backspace in gnome-terminal often deletes cluster
** Description changed: If I have `ខែ្` (U+1781 U+17c2 U+17d2) in the terminal and press backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left with `ខ` (U+1781). Instead it should only delete the last codepoint, U+17d2. If I have `ខែ` (U+1781 U+17c2) a backspace deletes only U+17c2, similarly if I have `ខ្` (U+1781 U+17d2) where the backspace deletes U+17d2. Further investigations show that backspace often deletes the entire cluster, i.e. diacritic(s) plus the base character, for example with `x̣́` (U+0078 U+0301 U+0323) where a backspace deletes all three codepoints. gnome-terminal should only delete the last codepoint [1]. A real live example where this behavior is problematic is when using ibus-keyman with the Khmer Angkor keyboard. When typing xEjmr the expected output is `ខ្មែរ` (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman does some reordering while typing to put the codepoints in a standardized order. Because gnome-terminal lacks support for surrounding text, the codepoints have to be deleted by emitting several backspace keypresses. Because of the deletion of the cluster the result in gnome- - terminal is `មែរ` (U+1798 U+17c2 U+179a). + terminal is ` ្មែរ` (U+17d2 U+1798 U+17c2 U+179a). [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster- deletion ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 [modified: usr/libexec/gnome-terminal-server] ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 12:21:42 2024 InstallationDate: Installed on 2022-04-12 (653 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - If I have `ខែ្` (U+1781 U+17c2 U+17d2) in the terminal and press + If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left - with `ខ` (U+1781). Instead it should only delete the last codepoint, + with ខ (U+1781). Instead it should only delete the last codepoint, U+17d2. - If I have `ខែ` (U+1781 U+17c2) a backspace deletes only U+17c2, - similarly if I have `ខ្` (U+1781 U+17d2) where the backspace deletes - U+17d2. + If I have ខែ (U+1781 U+17c2) a backspace deletes only U+17c2, similarly + if I have ខ្ (U+1781 U+17d2) where the backspace deletes U+17d2. Further investigations show that backspace often deletes the entire - cluster, i.e. diacritic(s) plus the base character, for example with - `x̣́` (U+0078 U+0301 U+0323) where a backspace deletes all three - codepoints. + cluster, i.e. diacritic(s) plus the base character, for example with x̣́ + (U+0078 U+0301 U+0323) where a backspace deletes all three codepoints. gnome-terminal should only delete the last codepoint [1]. A real live example where this behavior is problematic is when using - ibus-keyman with the Khmer Angkor keyboard. When typing - xEjmr the - expected output is `ខ្មែរ` (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman + ibus-keyman with the Khmer Angkor keyboard. When typing xEjmr the + expected output is ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman does some reordering while typing to put the codepoints in a standardized order. Because gnome-terminal lacks support for surrounding text, the codepoints have to be deleted by emitting several backspace keypresses. Because of the deletion of the cluster the result in gnome- - terminal is ` ្មែរ` (U+17d2 U+1798 U+17c2 U+179a). + terminal is ្មែរ (U+17d2 U+1798 U+17c2 U+179a). [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster- deletion ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 [modified: usr/libexec/gnome-terminal-server] ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 12:21:42 2024 InstallationDate: Installed on 2022-04-12 (653 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051371 Title: Backspace in gnome-terminal often deletes cluster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2051371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubun
[Bug 2051371] [NEW] Backspace in gnome-terminal often deletes cluster
Public bug reported: If I have `ខែ្` (U+1781 U+17c2 U+17d2) in the terminal and press backspace, the first backspace deletes U+17c2 U+17d2 so that I'm left with `ខ` (U+1781). Instead it should only delete the last codepoint, U+17d2. If I have `ខែ` (U+1781 U+17c2) a backspace deletes only U+17c2, similarly if I have `ខ្` (U+1781 U+17d2) where the backspace deletes U+17d2. Further investigations show that backspace often deletes the entire cluster, i.e. diacritic(s) plus the base character, for example with `x̣́` (U+0078 U+0301 U+0323) where a backspace deletes all three codepoints. gnome-terminal should only delete the last codepoint [1]. A real live example where this behavior is problematic is when using ibus-keyman with the Khmer Angkor keyboard. When typing xEjmr the expected output is `ខ្មែរ` (U+1781 U+17d2 U+1798 U+17c2 U+179a). Keyman does some reordering while typing to put the codepoints in a standardized order. Because gnome-terminal lacks support for surrounding text, the codepoints have to be deleted by emitting several backspace keypresses. Because of the deletion of the cluster the result in gnome- terminal is `មែរ` (U+1798 U+17c2 U+179a). [1] https://github.com/keymanapp/keyman/wiki/Backspace-and-cluster- deletion ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 [modified: usr/libexec/gnome-terminal-server] ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 26 12:21:42 2024 InstallationDate: Installed on 2022-04-12 (653 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (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 gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051371 Title: Backspace in gnome-terminal often deletes cluster To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2051371/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993900] Re: "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse
I see the same behavior in Ubuntu 22.10 when running X11 ("Ubuntu on
Xorg"). I don't see this bug with Wayland.
--
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/1993900
Title:
"Switch input sources individually for each window" does not work when
a keyboard layout is selected using the mouse
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993900/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916493] [NEW] Rendering problems with Khmer text containing U+17D2 and U+17C2
Public bug reported: gnome-terminal has some problems displaying Khmer text: The Khmer Sign Coeng (U+17D2) functions to indicate that the following Khmer letter is to be rendered subscripted. The Khmer Vowel Sign Ae (U+17C2) needs to be rendered in front of the preceding character. However, that doesn't work in gnome-terminal. See attached screenshots how things are supposed to look like (as rendered in gedit) and how they look in gnome-terminal: ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a) word fragments: ខ្ម (U+1781 U+17d2 U+1798) ខែ (U+1781 U+17c2) System information: $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.28.2-1ubuntu1~18.04.1 Candidate: 3.28.2-1ubuntu1~18.04.1 Version table: *** 3.28.2-1ubuntu1~18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Expected rendering (gedit)" https://bugs.launchpad.net/bugs/1916493/+attachment/5465939/+files/Khmer-expected.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1916493 Title: Rendering problems with Khmer text containing U+17D2 and U+17C2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916493] Re: Rendering problems with Khmer text containing U+17D2 and U+17C2
** Attachment added: "Actual rendering in gnome-terminal" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+attachment/5465940/+files/Khmer-actual.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1916493 Title: Rendering problems with Khmer text containing U+17D2 and U+17C2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916493] Re: Rendering problems with Khmer text containing U+17D2 and U+17C2
** Attachment added: "Khmer text sample" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+attachment/5465941/+files/Khmer.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1916493 Title: Rendering problems with Khmer text containing U+17D2 and U+17C2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
I have a Dell Precision 3510 with Radeon HD 8830M/R7 M465X and Intel HD Graphics 530 (radeon and i915 drivers) running Ubuntu 18.04.2. Installed and active gnome extensions: - Auto Move Windows - Google Earth Wallpaper - Hide veth interface - NoAnnoyance - Shortcuts - Suspend Button - system-monitor -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812527] Re: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] when running Android emulator (QEMU)
Crashing here as well, and I don't have the Android emulator running. It's happening seemingly randomly when switching between workspaces. I tried to follow the steps from #2, but steps 1 and 2 didn't work, and I'm not clear what workaround from bug 994921 is meant exactly. syslog also shows a crash in libmutter-2.so.0.0.0. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1812527 Title: gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] when running Android emulator (QEMU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
I could work around this problem by uninstalling dbus-user-session (and its dependendants xdg-desktop-portal and xdg-desktop-portal-gtk). Those packages came in through flatpak. Thanks to Olaf who brought me on the right track (https://forum.ubuntuusers.de/topic/gnome-keyring-daemon-doppelt/) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505789] Re: gnome-screensaver-command -p triggers keyboard event
Thanks for the quick fix! -- gnome-screensaver-command -p triggers keyboard event https://bugs.launchpad.net/bugs/505789 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505789] Re: gnome-screensaver-command -p triggers keyboard event
With the new package (2.28.0-0ubuntu3.3) I don't get this bug anymore. -- gnome-screensaver-command -p triggers keyboard event https://bugs.launchpad.net/bugs/505789 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505789] Re: gnome-screensaver-command -p triggers keyboard event
** Changed in: gnome-screensaver (Ubuntu) Status: New => Confirmed -- gnome-screensaver-command -p triggers keyboard event https://bugs.launchpad.net/bugs/505789 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505789] Re: gnome-screensaver-command -p triggers keyboard event
As a workaround I use the following proximity command in blueproximity: "xdotool key Scroll_Lock && xdotool key Scroll_Lock". Hopefully gnome-screensaver-command -p isn't issued by other apps I'm running. -- gnome-screensaver-command -p triggers keyboard event https://bugs.launchpad.net/bugs/505789 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505789] Re: gnome-screensaver-command -p triggers keyboard event
I can confirm this behavior with blueproximity, OO and gnome- screensaver. Running the following batch script in a terminal window, then giving focus to OO Writer clearly shows that the problem is gnome-screensaver- command, not blueproximity: #!/bin/bash for (( ; ; )) do gnome-screensaver-command -p sleep 5 done To me it looks like gnome-screensaver-command --poke just sends the Alt key on its own. In OO (as well as any Windows app) this opens the first menu item (or closes the menu if it happens to be open). This behavior is really annoying since it basically makes OO unuseable when running blueproximity. See also discussion at bottom of bug #216939. -- gnome-screensaver-command -p triggers keyboard event https://bugs.launchpad.net/bugs/505789 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 113067] Re: gdm hangs before login
Reinstalling the packages (dpkg --purge and then install again) as suggested in previous comments helped! -- gdm hangs before login https://bugs.launchpad.net/bugs/113067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 113067] Re: gdm hangs before login
I have the same problem on Hardy Heron Beta after updating the packages on 4/3/08. -- gdm hangs before login https://bugs.launchpad.net/bugs/113067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
