[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051371 Title: Backspace in gnome-terminal often deletes cluster Status in bash package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: 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 [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 [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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2051371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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() Status in GTK+: New Bug description: 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: To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2051381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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() Status in GTK+: New Bug description: 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: To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2051381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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() Status in gnome-terminal package in Ubuntu: New Bug description: 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[16
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051371 Title: Backspace in gnome-terminal often deletes cluster Status in gnome-terminal package in Ubuntu: New Bug description: 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 [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 [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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2051371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051371 Title: Backspace in gnome-terminal often deletes cluster Status in gnome-terminal package in Ubuntu: New Bug description: If I have ខែ្ (U+1781 U+17c2 U+17d2) in the terminal and press backspace, the first backspace deletes U+17c2 U+17d2 s
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2051371 Title: Backspace in gnome-terminal often deletes cluster Status in gnome-terminal package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2051371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop
Packages, 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
Status in gnome-control-center package in Ubuntu:
Confirmed
Bug description:
As far as I remember, this problem was not present in the previous
versions of Ubuntu (Xorg):
After selecting "Switch input sources individually for each window" at
the "GNOME Settings" / "Keyboard / Input source switching" section,
the keyboard layout can be changed for each window using the keyboard
shortcut (Windows Key+Space), however when the selection is attempted
using the mouse, nothing is changed and the current layout stays as
is.
The problem is that I can use the keyboard shortcut on a local
machine; however, I have to use the mouse for a remote desktop, since
the key combination is captured by the local machine in this case.
Wayland seems to work OK in this respect.
Ref: https://askubuntu.com/questions/1436720/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Oct 22 19:02:15 2022
InstallationDate: Installed on 2019-03-08 (1324 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to jammy on 2022-04-29 (176 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993900/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gnome-terminal package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gnome-terminal package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gnome-terminal package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell 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] Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Status in gjs source package in Bionic: Confirmed Status in gnome-shell source package in Bionic: Confirmed Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 emula
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 Desktop Packages, which is subscribed to gnome-shell 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) Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806865] Re: Ghostscript removes links (regression from gs 9.18)
Yes, adding `-dPrinted=false` works. Thanks a lot! ** Changed in: ghostscript (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1806865 Title: Ghostscript removes links (regression from gs 9.18) Status in ghostscript package in Ubuntu: Invalid Bug description: I often reduce the size of pdf documents by running: gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS="/default" -dNOPAUSE -dQUIET -dBATCH -sOutputFile="foo.pdf" "Document.pdf" The latest ghostscript version 9.26 doesn't keep links in the pdf file and produces slightly larger pdf files compared to 9.18. The size doesn't matter so much, but it's really bad that the links get removed. The attached file GhostscriptBug.tar.bz2 contains four files: - Scribus document with a link (PDF annotation) - PDF file with a link, generated by Scribus - foo9.26.pdf is the file resulting from running the above command with ghostscript 9.26 (-> links removed) - foo9.18.pdf is the file resulting from running the above command with ghostscript 9.18 (-> links still there) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [05/Dec/2018:08:06:16 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [05/Dec/2018:08:06:16 +0100] Missing value on line 3543 of /var/cache/cups/job.cache. CurrentDesktop: Unity Date: Wed Dec 5 12:20:41 2018 InstallationDate: Installed on 2011-05-25 (2751 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) Lpstat: device for KyoceraTASKalfa356ci: socket://192.168.16.5:9100 device for PDF: cups-pdf:/ MachineType: Dell Inc. Precision Tower 3620 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KyoceraTASKalfa356ci.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KyoceraTASKalfa356ci.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=11d1e29d-6b9c-42d4-95ef-0c3bd947c636 ro quiet splash vt.handoff=7 SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0MWYPT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd12/11/2017:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1806865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806865] Re: Ghostscript removes links (regression from gs 9.18)
Same behaviour on bionic with 9.26 ** Tags added: bionic ghostscript -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1806865 Title: Ghostscript removes links (regression from gs 9.18) Status in ghostscript package in Ubuntu: New Bug description: I often reduce the size of pdf documents by running: gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS="/default" -dNOPAUSE -dQUIET -dBATCH -sOutputFile="foo.pdf" "Document.pdf" The latest ghostscript version 9.26 doesn't keep links in the pdf file and produces slightly larger pdf files compared to 9.18. The size doesn't matter so much, but it's really bad that the links get removed. The attached file GhostscriptBug.tar.bz2 contains four files: - Scribus document with a link (PDF annotation) - PDF file with a link, generated by Scribus - foo9.26.pdf is the file resulting from running the above command with ghostscript 9.26 (-> links removed) - foo9.18.pdf is the file resulting from running the above command with ghostscript 9.18 (-> links still there) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [05/Dec/2018:08:06:16 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [05/Dec/2018:08:06:16 +0100] Missing value on line 3543 of /var/cache/cups/job.cache. CurrentDesktop: Unity Date: Wed Dec 5 12:20:41 2018 InstallationDate: Installed on 2011-05-25 (2751 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) Lpstat: device for KyoceraTASKalfa356ci: socket://192.168.16.5:9100 device for PDF: cups-pdf:/ MachineType: Dell Inc. Precision Tower 3620 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KyoceraTASKalfa356ci.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KyoceraTASKalfa356ci.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=11d1e29d-6b9c-42d4-95ef-0c3bd947c636 ro quiet splash vt.handoff=7 SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0MWYPT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd12/11/2017:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1806865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806865] [NEW] Ghostscript removes links (regression from gs 9.18)
Public bug reported: I often reduce the size of pdf documents by running: gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS="/default" -dNOPAUSE -dQUIET -dBATCH -sOutputFile="foo.pdf" "Document.pdf" The latest ghostscript version 9.26 doesn't keep links in the pdf file and produces slightly larger pdf files compared to 9.18. The size doesn't matter so much, but it's really bad that the links get removed. The attached file GhostscriptBug.tar.bz2 contains four files: - Scribus document with a link (PDF annotation) - PDF file with a link, generated by Scribus - foo9.26.pdf is the file resulting from running the above command with ghostscript 9.26 (-> links removed) - foo9.18.pdf is the file resulting from running the above command with ghostscript 9.18 (-> links still there) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [05/Dec/2018:08:06:16 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [05/Dec/2018:08:06:16 +0100] Missing value on line 3543 of /var/cache/cups/job.cache. CurrentDesktop: Unity Date: Wed Dec 5 12:20:41 2018 InstallationDate: Installed on 2011-05-25 (2751 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) Lpstat: device for KyoceraTASKalfa356ci: socket://192.168.16.5:9100 device for PDF: cups-pdf:/ MachineType: Dell Inc. Precision Tower 3620 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KyoceraTASKalfa356ci.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KyoceraTASKalfa356ci.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=11d1e29d-6b9c-42d4-95ef-0c3bd947c636 ro quiet splash vt.handoff=7 SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0MWYPT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd12/11/2017:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. ** Affects: ghostscript (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ghostscript xenial ** Attachment added: "GhostscriptBug.tar.bz2" https://bugs.launchpad.net/bugs/1806865/+attachment/5219403/+files/GhostscriptBug.tar.bz2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1806865 Title: Ghostscript removes links (regression from gs 9.18) Status in ghostscript package in Ubuntu: New Bug description: I often reduce the size of pdf documents by running: gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS="/default" -dNOPAUSE -dQUIET -dBATCH -sOutputFile="foo.pdf" "Document.pdf" The latest ghostscript version 9.26 doesn't keep links in the pdf file and produces slightly larger pdf files compared to 9.18. The size doesn't matter so much, but it's really bad that the links get removed. The attached file GhostscriptBug.tar.bz2 contains four files: - Scribus document with a link (PDF annotation) - PDF file with a link, generated by Scribus - foo9.26.pdf is the file resulting from running the above command with ghostscript 9.26 (-> links removed) - foo9.18.pdf is the file resulting from running the above command with ghostscript 9.18 (-> links still there) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [05/Dec/2018:08:06:16 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [05/Dec/2018:08:06:16 +0100] Missing value on line 3543 of /var/cache/cups/job.cache. CurrentDesktop: Unity Date: Wed Dec 5 12:20:41 2018 InstallationDate: Installed on 2011-05-25 (2751 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) Lpstat: device for KyoceraTASKalfa356ci: socket://192.168.16.5:9100 device for PDF: cups-pdf:/ MachineType: Dell Inc. Precision Tower 3620 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KyoceraTASKalfa356ci.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KyoceraTASKalfa356ci.ppd: Pe
[Desktop-packages] [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 Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Invalid Status in gdm package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
