Console issueshttps://gitlab.gnome.org/GNOME/console/-/issues2023-08-05T00:13:44Zhttps://gitlab.gnome.org/GNOME/console/-/issues/304pointer over links is hand even tho clicking does nothing2023-08-05T00:13:44Ztwopointer over links is hand even tho clicking does nothinghovering over a link or any text that may be an email or http link makes the mouse pointer into a hand like on links in browsers. but they aren't actually clickable if you're not holding ctrl. imo it should turn into a pointing hand only...hovering over a link or any text that may be an email or http link makes the mouse pointer into a hand like on links in browsers. but they aren't actually clickable if you're not holding ctrl. imo it should turn into a pointing hand only when ctrl is heldGNOME 45https://gitlab.gnome.org/GNOME/console/-/issues/303Feature request: support coloured and styled underlines2023-09-23T09:04:05ZKeir LawsonFeature request: support coloured and styled underlinesThis is a feature from Kitty that is now compatible with a few other terminal emulators: https://sw.kovidgoyal.net/kitty/underlines/
Its specifically used by the likes of helix editor: https://github.com/helix-editor/helix/wiki/Terminal...This is a feature from Kitty that is now compatible with a few other terminal emulators: https://sw.kovidgoyal.net/kitty/underlines/
Its specifically used by the likes of helix editor: https://github.com/helix-editor/helix/wiki/Terminal-Support#extended-underlineshttps://gitlab.gnome.org/GNOME/console/-/issues/302Output lines overlap each other instead of appearing below each other2023-07-03T02:34:10ZAutomeris naranjaOutput lines overlap each other instead of appearing below each other## Affected version
gnome-console-44.0-1.fc38.x86_64
vte291-gtk4-0.72.2-1.fc38.x86_64
## Steps to reproduce
Run `pkcon install <package>`
## Seen behavior
When pkcon progress generates new lines of output, these lines will start overl...## Affected version
gnome-console-44.0-1.fc38.x86_64
vte291-gtk4-0.72.2-1.fc38.x86_64
## Steps to reproduce
Run `pkcon install <package>`
## Seen behavior
When pkcon progress generates new lines of output, these lines will start overlapping old ones instead of appearing below them:
![Screencast_from_2023-07-01_23-58-33-1](/uploads/49ed014aca636c7d8f363222fdb28e8b/Screencast_from_2023-07-01_23-58-33-1.webm)https://gitlab.gnome.org/GNOME/console/-/issues/301GNOME Console crashes when a tab is dragged in then dragged out to the desktop.2023-11-25T14:13:37ZJamie ChamberlainGNOME Console crashes when a tab is dragged in then dragged out to the desktop.![Screencast_from_2023-06-30_18-16-49](/uploads/8c24f294079bcc02ad5b84f01831271b/Screencast_from_2023-06-30_18-16-49.webm) [message.txt](/uploads/a04f199601718f5f64aebc7b9ddfeca0/message.txt)![Screencast_from_2023-06-30_18-16-49](/uploads/8c24f294079bcc02ad5b84f01831271b/Screencast_from_2023-06-30_18-16-49.webm) [message.txt](/uploads/a04f199601718f5f64aebc7b9ddfeca0/message.txt)https://gitlab.gnome.org/GNOME/console/-/issues/300Dim text only works in dark mode2023-12-19T16:50:34ZnleanbaDim text only works in dark modeWhen in light mode, the difference between normal text and “dim” text (achieved with ANSI escape `\e[2m`) is nonexistent.
Expected behavior: dimmed text shows up gray in light mode too
![Screenshot Dark Mode](/uploads/e1d426c8e20880f07...When in light mode, the difference between normal text and “dim” text (achieved with ANSI escape `\e[2m`) is nonexistent.
Expected behavior: dimmed text shows up gray in light mode too
![Screenshot Dark Mode](/uploads/e1d426c8e20880f07132f3ed136ce11d/Screenshot_from_2023-06-20_17-27-03.png)
![Screenshot Light Mode](/uploads/eb8da10585f8e8e3e26ce5545fa6dbd2/Screenshot_from_2023-06-20_17-27-13.png)
I am using Console 44.0https://gitlab.gnome.org/GNOME/console/-/issues/299adw_tab_view_get_n_pages: assertion2023-10-21T15:52:14Ztekstryderadw_tab_view_get_n_pages: assertion### Affected version
* Arch Linux kernel 6.1.33
* X11 / nVidia
* gnome/mutter 44.2
* kgx 44.0
### Bug summary
Seeing these errors occur, seemingly once for each instance of kgx
### Relevant logs, screenshots, screencasts etc.
```
Jun...### Affected version
* Arch Linux kernel 6.1.33
* X11 / nVidia
* gnome/mutter 44.2
* kgx 44.0
### Bug summary
Seeing these errors occur, seemingly once for each instance of kgx
### Relevant logs, screenshots, screencasts etc.
```
Jun 06 07:45:08 kgx[19549]: adw_tab_view_get_n_pages: assertion 'ADW_IS_TAB_VIEW (self)' failed
Jun 06 10:24:26 kgx[19549]: adw_tab_view_get_n_pages: assertion 'ADW_IS_TAB_VIEW (self)' failed
Jun 07 08:16:04 kgx[1886]: adw_tab_view_get_n_pages: assertion 'ADW_IS_TAB_VIEW (self)' failed
Jun 08 12:27:43 kgx[8850]: adw_tab_view_get_n_pages: assertion 'ADW_IS_TAB_VIEW (self)' failed
Jun 09 13:03:41 kgx[49432]: adw_tab_view_get_n_pages: assertion 'ADW_IS_TAB_VIEW (self)' failed
Jun 09 17:13:43 kgx[1826]: adw_tab_view_get_n_pages: assertion 'ADW_IS_TAB_VIEW (self)' failed
Jun 10 07:13:02 kgx[15918]: adw_tab_view_get_n_pages: assertion 'ADW_IS_TAB_VIEW (self)' failed
Jun 10 07:22:08 kgx[29814]: adw_tab_view_get_n_pages: assertion 'ADW_IS_TAB_VIEW (self)' failed
```GNOME 45https://gitlab.gnome.org/GNOME/console/-/issues/298Options hamburger menu create "assertion failed" warnings2023-08-05T13:58:55ZtekstryderOptions hamburger menu create "assertion failed" warnings### Affected version
* Arch Linux kernel 6.1.33
* X11 / nVidia
* gnome/mutter 44.2
* kgx 44.0
* No extensions enabled
### Bug summary
Clicking the 'hamburger' options menu in console spews a ton of errors into the system journal
### ...### Affected version
* Arch Linux kernel 6.1.33
* X11 / nVidia
* gnome/mutter 44.2
* kgx 44.0
* No extensions enabled
### Bug summary
Clicking the 'hamburger' options menu in console spews a ton of errors into the system journal
### Steps to reproduce
1. Click options
2. Observe errors
### Relevant logs, screenshots, screencasts etc.
```Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:36 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_x: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
Jun 09 20:42:37 kgx[15918]: _gtk_css_corner_value_get_y: assertion 'corner->class == >K_CSS_VALUE_CORNER' failed
```https://gitlab.gnome.org/GNOME/console/-/issues/297if sudo is within a script, does not turn red2023-05-28T17:49:41ZSteven Jay Cohenif sudo is within a script, does not turn red1. Put a **SUDO** command into a shell script.
2. Run shell script.
3. See [sudo] echoed back as it requests password.
4. Script runs but does **NOT** turn the terminal **RED**.
SUGGESTED FIX: Use the fact that [sudo] is echoed back to ...1. Put a **SUDO** command into a shell script.
2. Run shell script.
3. See [sudo] echoed back as it requests password.
4. Script runs but does **NOT** turn the terminal **RED**.
SUGGESTED FIX: Use the fact that [sudo] is echoed back to trigger turning the terminal RED.https://gitlab.gnome.org/GNOME/console/-/issues/296get focus2023-05-28T11:58:23ZRJGhugoget focusWhen open a new Console window the focus stays on the last used application.When open a new Console window the focus stays on the last used application.https://gitlab.gnome.org/GNOME/console/-/issues/295Feature Request: Tab behavior2023-06-01T14:29:05ZgargulliaFeature Request: Tab behaviorAdd the ability to open new terminals in a new window OR in a new tab.
In this way, the terminal will always run alone (many windows will not be created).
This functionality is available in TilixAdd the ability to open new terminals in a new window OR in a new tab.
In this way, the terminal will always run alone (many windows will not be created).
This functionality is available in Tilixhttps://gitlab.gnome.org/GNOME/console/-/issues/294Window title is blank in Zsh2023-05-23T06:22:53ZJovial Joe JayarsonWindow title is blank in ZshWindow title is visible and it sticks when `bash` is executed.
![Screencast_from_2023-05-23_11-13-43](/uploads/a98b6fa816baabfd21383e2780c6b4c5/Screencast_from_2023-05-23_11-13-43.webm)Window title is visible and it sticks when `bash` is executed.
![Screencast_from_2023-05-23_11-13-43](/uploads/a98b6fa816baabfd21383e2780c6b4c5/Screencast_from_2023-05-23_11-13-43.webm)https://gitlab.gnome.org/GNOME/console/-/issues/293Feature Request: Rename tabs2023-10-25T00:52:04ZDouglasFeature Request: Rename tabsgnome-terminal lets you double-click a tab and quickly assign it a new display name, making it easier to distinguish between multiple tabs. I often keep at least 3 tabs open all the time, one for docker logs (renamed as "logs"), other fo...gnome-terminal lets you double-click a tab and quickly assign it a new display name, making it easier to distinguish between multiple tabs. I often keep at least 3 tabs open all the time, one for docker logs (renamed as "logs"), other for git (renamed as "git") and another for database access (renamed as "db").
Here's the current situation: :disappointed:
![image](/uploads/19a011fbdbdda53f10a2730c6be14734/image.png)https://gitlab.gnome.org/GNOME/console/-/issues/292shift key can be ignored on non-latin layouts2023-10-08T12:04:22Ztwoshift key can be ignored on non-latin layouts**Reproducing**: switch to ukrainian keyboard layout, press Ctrl+Shift+C
**Expected**: text is copied
**Actual**: Ctrl+C is sent, running program is killed.
```
$ kgx --version
# KGX 43.0 з використанням VTE 0.70.3 +BIDI +GNUTLS +ICU ...**Reproducing**: switch to ukrainian keyboard layout, press Ctrl+Shift+C
**Expected**: text is copied
**Actual**: Ctrl+C is sent, running program is killed.
```
$ kgx --version
# KGX 43.0 з використанням VTE 0.70.3 +BIDI +GNUTLS +ICU +SYSTEMD
```https://gitlab.gnome.org/GNOME/console/-/issues/291"New Tab" should open a new tab with in same cwd (current working directory)2024-02-12T14:29:18ZEvan Greenup"New Tab" should open a new tab with in same cwd (current working directory)In `gnome-terminal`, when click "[+]" button in the window bar, it will add a new tab with same current working directory. However, for `gnome-console` (`kgx`), it open with the default current working directory (user's \$HOME). It is in...In `gnome-terminal`, when click "[+]" button in the window bar, it will add a new tab with same current working directory. However, for `gnome-console` (`kgx`), it open with the default current working directory (user's \$HOME). It is inconvenient. Because for the most case, when user want to click "[+]" button, it means user want to a terminal with same current working directory.
It would make the behavior from `gnome-terminal` to `gnome-console` again.https://gitlab.gnome.org/GNOME/console/-/issues/290Console isn't available in Flathub2023-05-16T08:31:14ZAutomeris naranjaConsole isn't available in FlathubNot sure if this is out of scope, but installing Console in Fedora Silverblue requires modifying the base system. It would be nice to install Console as a flatpak, like Black Box.Not sure if this is out of scope, but installing Console in Fedora Silverblue requires modifying the base system. It would be nice to install Console as a flatpak, like Black Box.https://gitlab.gnome.org/GNOME/console/-/issues/289make red highlighting for sudo only affect the one tab2023-05-16T10:13:58ZZbigniew Jędrzejewski-Szmekmake red highlighting for sudo only affect the one tabWhen I run a superuser command, Console makes the tab reddish, which is nice. But it's just the one tab that is executing the command, so only that one tab should have the highlight, not the full window. (Also, when I switch to another t...When I run a superuser command, Console makes the tab reddish, which is nice. But it's just the one tab that is executing the command, so only that one tab should have the highlight, not the full window. (Also, when I switch to another tab, the highlight is completely removed, even though the superuser program is still running in the other tab.)https://gitlab.gnome.org/GNOME/console/-/issues/288Launching Console from the GNOME Shell dash using a mouse click does not capt...2023-05-12T01:47:58ZBritt Yazelbwyazel@gnome.orgLaunching Console from the GNOME Shell dash using a mouse click does not capture keyboard focusThis is hopefully a very small bug report / usability request, but when launching Console from the GNOME Shell dash via a mouse click, Console does not start capturing the keyboard input straight away. Instead you have to click a second ...This is hopefully a very small bug report / usability request, but when launching Console from the GNOME Shell dash via a mouse click, Console does not start capturing the keyboard input straight away. Instead you have to click a second time within the app itself for it to begin capturing keyboard input. This is in stark contrast to launching Console from GNOME Shell using the keyboard (i.e. searching for Console and pressing enter), or strangely, if you use the mouse click to launch console from anywhere 'other' than the dash, in which case Console begins capturing keyboard input straight away.
Likewise, another weird quirk is that the first time you pin Console to the dash, launching it from the dash with a mouse click will continue capturing keyboard inputs straight away for the remainder of that session. But if you log out or reboot the session, launching Console from the dash with a mouse click will go back to not capturing the keyboard input.
So there seems to be some weird interaction with Console being pinned to the dash and the state in which it launches.
Other apps, such as GNOME Text Editor will capture keyboard input straight away, regardless of which way they are launched. I can't get this behavior to appear in any other GNOME apps that I have tried that have some sort of primary keyboard entry element. Even apps like GNOME Software will capture keyboard entry straight away and use it to populate the search box.
Here is a recording where I demonstrate the above issue on a session that already has Console pinned to the dash.
![Screencast_from_2023-05-11_17-43-58](/uploads/1c149569efd8a6cd9706438d43861293/Screencast_from_2023-05-11_17-43-58.webm)
My system is running Arch Linux with GNOME 44.1 on a Wayland session. That said, I experienced this same issue for the whole time I was on GNOME 43 as well.https://gitlab.gnome.org/GNOME/console/-/issues/287space in path2023-08-04T23:00:18ZRJGhugospace in path- os: 6.3.1-arch1-1
- nautilus: 44.1-2
- gnome-console: 44.0-1
1. mkdir -p /tmp/'Test 1'
1. Type "cd " and drag & drop '/tmp/Test 1' from Nautilus to Konsole
1. cd /tmp/Test 1 bash: cd: Zu viele Argumente. (too many arguments)- os: 6.3.1-arch1-1
- nautilus: 44.1-2
- gnome-console: 44.0-1
1. mkdir -p /tmp/'Test 1'
1. Type "cd " and drag & drop '/tmp/Test 1' from Nautilus to Konsole
1. cd /tmp/Test 1 bash: cd: Zu viele Argumente. (too many arguments)GNOME 45Zander Brownzbrown@gnome.orgZander Brownzbrown@gnome.orghttps://gitlab.gnome.org/GNOME/console/-/issues/286Incorrect key press order when typing keys with QMK home row modifiers2023-05-01T13:24:58ZdagIncorrect key press order when typing keys with QMK home row modifiersTyping any 2 key combination where exactly one of the keys is a home row modifier (key acting as a modifier when held, but as normal key when pressed normally) by rolling the keys (still holding the first key when pressing the second) al...Typing any 2 key combination where exactly one of the keys is a home row modifier (key acting as a modifier when held, but as normal key when pressed normally) by rolling the keys (still holding the first key when pressing the second) always results the normal key getting output first. regardless of the order of the key presses. For example, `fg` becomes `gf` on a qwerty layout if `f` is a home row modifier. I think it has to do with the fact that the keyboard will immediately output both keys when the modifier key is released (since it at that point knows that the key was not used as a modifier, a home row modifier is usually configured so that it needs to be held for a minimum amount of time in order to register as a modifier to allow for rolling the keys when typing) and Console for some reason gets the order wrong when it receives two key codes very close to each other.
I am only seeing this issue in Console, no other terminal emulators or other applications. I'm using Console 44.0.https://gitlab.gnome.org/GNOME/console/-/issues/285Previous output of a command appears again after clearing the terminal with C...2023-04-28T20:04:45ZAutomeris naranjaPrevious output of a command appears again after clearing the terminal with CTRL+L## Affected version
gnome-console-44.0-1.fc38.x86_64
## Steps to reproduce
1. Run `sudo /usr/libexec/fwupd/fwupd --verbose`
2. Press CTRL+C to cancel
3. Press CTRL+L to clear the terminal output
4. Run `sudo /usr/libexec/fwupd/fwupd --v...## Affected version
gnome-console-44.0-1.fc38.x86_64
## Steps to reproduce
1. Run `sudo /usr/libexec/fwupd/fwupd --verbose`
2. Press CTRL+C to cancel
3. Press CTRL+L to clear the terminal output
4. Run `sudo /usr/libexec/fwupd/fwupd --verbose` again
## Seen behavior
The previous output of `sudo /usr/libexec/fwupd/fwupd --verbose` will appear and the cancel action will be visible as `^C` despite the terminal being cleared with CTRL+L.
![Screenshot_from_2023-04-25_14-47-42](/uploads/157be31708b80eedc0df0cbad06720c7/Screenshot_from_2023-04-25_14-47-42.png)