> 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
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
> 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.
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
** 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
** 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
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,
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
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,
** 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
** 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.
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
-
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
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/)
--
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
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
** 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
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
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
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.
--
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
21 matches
Mail list logo
