GNOME issueshttps://gitlab.gnome.org/groups/GNOME/-/issues2023-10-08T01:00:40Zhttps://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/1Gnome keyring not unlocked using fingerprint authentication for user log-in2023-10-08T01:00:40ZGhost UserGnome keyring not unlocked using fingerprint authentication for user log-inGnome keyring is not being unlocked automatically after login, if the user logs into a session using fingerprint authentication. The user is prompted to unlock the keyring, first time an application requires a password stored in the keyr...Gnome keyring is not being unlocked automatically after login, if the user logs into a session using fingerprint authentication. The user is prompted to unlock the keyring, first time an application requires a password stored in the keyring.
Fedora 28. Gnome Version 3.28.2. Gnome Keyring Version 3.28.2.https://gitlab.gnome.org/GNOME/gtk/-/issues/1119Open dialog doesn't allow Ctrl+V to insert path to file directly in some cases2021-12-30T12:03:25ZNazar MokrynskyiOpen dialog doesn't allow Ctrl+V to insert path to file directly in some casesInitially reported in Geany, but appears to be upstream issue: https://github.com/geany/geany/issues/1865
Steps to reproduce:
* copy full path to file into clipboard, for instance, `/home/nazar-pc/.gitconfig` in my case
* open Gedit, Ge...Initially reported in Geany, but appears to be upstream issue: https://github.com/geany/geany/issues/1865
Steps to reproduce:
* copy full path to file into clipboard, for instance, `/home/nazar-pc/.gitconfig` in my case
* open Gedit, Geany or any other app that is configured to accept non-local files
* Ctrl+O to open "Open file" dialog
* Ctrl+V to insert file path
Expected result:
Dialog window switches to corresponding directory with file from clipboard selected or something very similar.
Actual behavior:
```
The folder contents could not be displayed
Operation not supported
```
Workaround:
Type `/` first, then Ctrl+V and Enter.https://gitlab.gnome.org/GNOME/nautilus/-/issues/461No existing way of managing extensions2020-06-13T15:47:46ZMaoschanzNo existing way of managing extensions### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
There is no existing way of enabling/disabling nautilus' extensions.
Example 1: i installed KDE Connect and the "MConnect...### Use cases
<!-- Describe what problem(s) the user is experiencing and that this request
is trying to solve. -->
There is no existing way of enabling/disabling nautilus' extensions.
Example 1: i installed KDE Connect and the "MConnect" GS extension, which comes with a nautilus extension (via the python binding). Later i uninstalled KDE Connect, disabled the GNOME Shell extension, but the nautilus extension still exists and try to establish dbus connections. I have to search for it in ~/.local/share and delete the script if i don't want polluted logs
Example 2: i don't care about the "sent to" extension, and i would have to delete files in /usr/share, or to remove packages (breaking dependencies) if i want to get rid of it.
Example 3: i have Tilix, and the extension "open in Tilix", so i don't care about "open in a terminal", but can't remove it.
### Desired behavior
<!-- Describe the desired functionality. -->
The user should be able to disable/enable extensions instead of deleting them. This could be integrated in the Preferences window, or at least just in a gsettings key.
### Benefits of the solution
<!-- List the possible benefits of the solution and how it fits in the project. -->
Giving to the user a better control over what additional actions are polluting his contextual menus, without requiring the removal of obscure packages or the deletion of files the user shouldn't even know about.
### Possible drawbacks
<!--
Describe possible drawbacks of the feature and list how it could affect
the project i.e. UI discoverability, complexity, impact in more or less
number of users, etc.
-->
A gsettings key for activated extensions, **if not exposed in the Preferences window**, implies that the user have to dig in the dconf editor in order to use what he installed, or that all concerned packages have to be updated.
**If exposed in the Preferences window**, it means more preferences, and i know you don't like that.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/mutter/-/issues/173Stutter on video playback with Chrome2023-07-21T04:36:36ZPavilufStutter on video playback with ChromeHello,
Some time ago, Chrome / Chromium implemented _NET_WM_BYPASS_COMPOSITOR and use it with value 2 (https://bugs.chromium.org/p/chromium/issues/detail?id=344141) to avoid tearing with Mutter since Mutter unredirect fullscreen windows...Hello,
Some time ago, Chrome / Chromium implemented _NET_WM_BYPASS_COMPOSITOR and use it with value 2 (https://bugs.chromium.org/p/chromium/issues/detail?id=344141) to avoid tearing with Mutter since Mutter unredirect fullscreen windows by default
https://gitlab.gnome.org/GNOME/mutter/issues/24 ... Now there is stutter on video playback with Chrome... Of course it need to be confirmed but it seems that Mutter can't handle smooth video playback without unredirecting fullscreen windows...
Fedora 28 / Ubuntu 18.04
Intel iGPU
Thanks.https://gitlab.gnome.org/GNOME/glib/-/issues/1392Many unit tests fails on macOS2023-04-20T14:33:43ZXavier Claessensxclaesse@gmail.comMany unit tests fails on macOSI installed a macosx CI in !19 and logs of failing tests can be seen here:
https://xclaesse.pages.gitlab.gnome.org/-/glib/-/jobs/37050/artifacts/_build/meson-logs/testlog.txt
Tests which need fixing:
* [ ] `gio/appmonitor`
* [ ] `gio...I installed a macosx CI in !19 and logs of failing tests can be seen here:
https://xclaesse.pages.gitlab.gnome.org/-/glib/-/jobs/37050/artifacts/_build/meson-logs/testlog.txt
Tests which need fixing:
* [ ] `gio/appmonitor`
* [ ] `gio/contenttype` (tracked separately as #1251)
* [x] `gio/giomodule`: !2950
* [x] `gio/gsubprocess`: !2785
* [x] `gio/g-file-info`: !2990 / !3004
* [x] `gio/network-address`: !2520 / !2538
* [ ] `gio/socket`
* [ ] `gio/gdbus-address-get-session` !3032
* [ ] `gio/gdbus-peer` (partly fixed by !3032)
* [x] `gio/resources`: !2950
* [ ] `glib/date`
* [ ] `glib/environment`https://gitlab.gnome.org/GNOME/shotwell/-/issues/3Feature request: skip or disable previewing of connected camera2023-12-22T21:12:54ZjimisFeature request: skip or disable previewing of connected cameraUsing shotwell-0.28.3-1.fc27.x86_64
Problem: I connect my phone in MTP mode and Shotwell immediately starts previewing the photos. It takes around 30 min for previewing to be over, in order for me to be able to hit the "import all" butt...Using shotwell-0.28.3-1.fc27.x86_64
Problem: I connect my phone in MTP mode and Shotwell immediately starts previewing the photos. It takes around 30 min for previewing to be over, in order for me to be able to hit the "import all" button.
Feature request: To stop or disable previewing but still be able to do "import all" afterwards.
Thanks in advance!https://gitlab.gnome.org/GNOME/gexiv2/-/issues/29critical errors while previewing from MTP phone2019-10-12T01:17:21Zjimiscritical errors while previewing from MTP phoneUsing shotwell-0.28.3-1.fc27.x86_64
After I connect the phone, previewing starts automatically. In the console I get plenty of critical errors, that are mostly of 2 kinds:
```
L 9070 2018-05-26 03:01:18 [CRT] Upper boundary of data for...Using shotwell-0.28.3-1.fc27.x86_64
After I connect the phone, previewing starts automatically. In the console I get plenty of critical errors, that are mostly of 2 kinds:
```
L 9070 2018-05-26 03:01:18 [CRT] Upper boundary of data for directory Photo, entry 0xa420 is out of bounds: Offset = 0x0000028e, size = 25, exceeds buffer size by 1 Bytes; truncating the entry
```
and
```
L 9070 2018-05-26 03:01:39 [CRT] Upper boundary of data for directory GPSInfo, entry 0x0004 is out of bounds: Offset = 0x00000302, size = 24, exceeds buffer size by 2 Bytes; truncating the entry
```
I can't see anything going wrong though. What do these errors mean and why are they critical?
Thank you in advance!
EDIT: Same issue with the following message printed by shotwell, moved from issue shotwell#2:
```
L 9070 2018-05-26 03:04:02 [WRN] Directory Thumbnail, entry 0x0201: Data area exceeds data buffer, ignoring it.
```
https://gitlab.gnome.org/GNOME/libmanette/-/issues/8Use CI to detect changes in upstream mapping DBs2020-03-21T09:09:31ZAdrien PlazasUse CI to detect changes in upstream mapping DBsThis would help keeping our downstream mappings database up to date.This would help keeping our downstream mappings database up to date.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/305No notifications dot next to date/time2024-02-04T04:31:09ZBrian ZwahrNo notifications dot next to date/timeI just clicked on my time/date/notification thing to check the song playing in Spotify (because it's listed there). While there, I saw a notification from Deja Dup that backup finished, two manual notifications I made with notify-send to...I just clicked on my time/date/notification thing to check the song playing in Spotify (because it's listed there). While there, I saw a notification from Deja Dup that backup finished, two manual notifications I made with notify-send to test something, and a notification from Peek about a GIF I made. All these notifications, and there was no dot next to the date/time to let me know. Is that normal? Do I misunderstand how the dot is supposed to work?
I'm not exactly sure why I'm not seeing a dot. I know I have seen a dot before, but couldn't tell you the circumstances in which I saw it. I read somewhere that the dot only shows up if a notification wasn't able to be displayed (ie. multiple notifications come it at once). That seems far less useful than it could be. For example, if I get up and get some water, then come back to my desk, I'll have no idea a notification came through while I was away. Unless I make a habit of manually checking by clicking on the date/time every time I come back to my computer, which is a bit of a pain.
Perhaps a dot can be shown until a notification is acted on (the notifying app is visited) or "seen". What I mean by "seen" is this: Let's say I get up to get water and come back. I see a dot. I click the date/time (is there a better name for that?) and see, for instance, a Mattermost notification. For whatever reason, I decide not to clear it out (so I can see it or reference it later, whatever reason, doesn't matter). There's no reason to continuing showing a dot for that notification. If you keep showing a dot, then I get another glass of water and come back, I won't know if the dot means "new notifications" or if it means "you still have that Mattermost notification in there that you've already seen".https://gitlab.gnome.org/GNOME/gimp/-/issues/1503Add support for ".hgt.zip" files.2018-10-12T13:02:39ZTobiasAdd support for ".hgt.zip" files.The NASA provides his HGT files always as ".hgt.zip" It would be nice to be able to open them directly.The NASA provides his HGT files always as ".hgt.zip" It would be nice to be able to open them directly.2.10https://gitlab.gnome.org/GNOME/dia/-/issues/2No Ctrl + A, Ctrl + Arrow or selection support during text edition2019-09-25T16:55:01ZGhost UserNo Ctrl + A, Ctrl + Arrow or selection support during text editionWhile editing a text field on the main panel, the common shortcut Ctrl+A doesn't act as commonly expected. Ctrl + A should select all the text in the field.
edit by @neduard (moved issue text from #3 and #4 as they are basically the sam...While editing a text field on the main panel, the common shortcut Ctrl+A doesn't act as commonly expected. Ctrl + A should select all the text in the field.
edit by @neduard (moved issue text from #3 and #4 as they are basically the same from a development standpoint):
While editing a text field on the main panel, it is not possible to select text by highlighting it.
When an object is selected and you click on the text-editing tool, the UI changes and makes the user think he can type, but nothing happens. You need to click again on the already selected object to actually have the keyboard focused on it.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/304gnome-shell memory leak with nvidia GPU memory2024-01-29T22:12:31ZMatthias Bodenbindergnome-shell memory leak with nvidia GPU memoryHi,
I know that gnome-shell has a memory leak but I do not know if the existing reports also cover the memory leak on the graphics card. That is the issue here: GPU memory leak.
I am checking the GPU memory consumption of my GTX 1050 T...Hi,
I know that gnome-shell has a memory leak but I do not know if the existing reports also cover the memory leak on the graphics card. That is the issue here: GPU memory leak.
I am checking the GPU memory consumption of my GTX 1050 Ti with nvidia-smi. When I first login to gnome the used memory is around 100 MiB. When I just start and exit darktable repeatedly for a while, the memory consumtion is persitently going up by ca. 30 MiB per darktable start/exit. The result is that at some point darktable has not enough "headroom" anymore to use opencl which has a significant performance impact to darktable. I have checked the same scenario with plasma5 and it is not showing the same memory increase.
I am using Manjaro Testing, kernel 4.16.11 with gnome-shell 3.28 and nvidia 1:396.24-4https://gitlab.gnome.org/GNOME/mutter/-/issues/172Mouse cursor jitter on one display2023-10-10T02:38:06ZJeff WaughMouse cursor jitter on one displayI have a new Radeon 5450 with two displays attached (DP and DVI). The cursor is jittery / skipping on the DP display, but seems fine on the DVI display. Settings says the DP display is primary, while the DVI display is numbered 1.
Danie...I have a new Radeon 5450 with two displays attached (DP and DVI). The cursor is jittery / skipping on the DP display, but seems fine on the DVI display. Settings says the DP display is primary, while the DVI display is numbered 1.
Daniel Stone [suggested](https://twitter.com/jdub/status/999631851936301056) it might be a mutter issue, and thought a video might help illustrate the problem. I took a [slow motion video](https://twitter.com/jdub/status/999662153308127232) with my phone. Sorry about the Twitter compression, let me know if you need a higher quality version.https://gitlab.gnome.org/GNOME/glib/-/issues/1391Disallow pushing directly to git2022-07-04T11:03:20ZPhilip WithnallDisallow pushing directly to gitCurrently, we need to allow developers access to push directly to git so that the Damned Lies translation workflow continues to work. Once https://gitlab.gnome.org/GNOME/damned-lies/issues/78 is fixed, we can turn that off, and prevent a...Currently, we need to allow developers access to push directly to git so that the Damned Lies translation workflow continues to work. Once https://gitlab.gnome.org/GNOME/damned-lies/issues/78 is fixed, we can turn that off, and prevent anyone from pushing to the `master` or `glib-*` branches. We can continue to allow people to push to `*` branches so that they don’t need to fork the repository.https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/53intel_backlight not included in available kernal interfaces list in gsd-backl...2018-08-31T19:21:59ZGhost Userintel_backlight not included in available kernal interfaces list in gsd-backlight-helper.cRecently installed Fedora on my laptop and was unable to change the screen backlight through the system menu slider. After searching for a while, a workaround found was to install xbacklight and change the backlight through the terminal....Recently installed Fedora on my laptop and was unable to change the screen backlight through the system menu slider. After searching for a while, a workaround found was to install xbacklight and change the backlight through the terminal. xbacklight works now but the slider still doesn't.
Searched further and found this bug report : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651741 ,which says adding intel_backlight to `backlight_interfaces[]` (https://gitlab.gnome.org/GNOME/gnome-settings-daemon/blob/64f2267ae0752a71db8af1010cc1a989f6fa36f0/plugins/power/gsd-backlight-helper.c) might solve the problem.https://gitlab.gnome.org/GNOME/evolution/-/issues/2Use gnome-shell-calendar-server for Reminders in GNOME2023-11-13T15:33:59ZMilan CrhaUse gnome-shell-calendar-server for Reminders in GNOMEOnce GNOME/gnome-shell#155 is finished, the evolution-alarm-notify should not be started in GNOME by evolution. This bug is for it and it depends on changes from GNOME/evolution-data-server#1.
In the change, evolution reads org.gnome.Ev...Once GNOME/gnome-shell#155 is finished, the evolution-alarm-notify should not be started in GNOME by evolution. This bug is for it and it depends on changes from GNOME/evolution-data-server#1.
In the change, evolution reads org.gnome.Evolution-alarm-notify.desktop file and in it the NotShowIn key and compares it with the XDG_CURRENT_DESKTOP environment. When the environment variable value matches one of the values in the .desktop file the evolution-alarm-notify start is ignored.
[evo.patch](/uploads/cc38aab41a774a2b44ddb61a5897ba36/evo.patch)https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/1Use gnome-shell-calendar-server for Reminders in GNOME2023-11-13T15:33:59ZMilan CrhaUse gnome-shell-calendar-server for Reminders in GNOMEOnce GNOME/gnome-shell#155 is finished the evolution-alarm-notify should not be auto-started in GNOME. This change is for it.
I did two things:
a) in the .desktop file I changed OnlyShowIn into NotShowIn entry, because I do not know the...Once GNOME/gnome-shell#155 is finished the evolution-alarm-notify should not be auto-started in GNOME. This change is for it.
I did two things:
a) in the .desktop file I changed OnlyShowIn into NotShowIn entry, because I do not know the reason why it should be hidden everywhere but 5 desktop environments
b) I enabled the status icon of evolution-alarm-notify for GNOME
Users can still run the alarm notify on their own, this is only for the auto-start of it after login.[eds.patch](/uploads/7a3b72ceecd05590b6d61ee80ff142a4/eds.patch)https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/515Code folding2023-09-16T00:56:52ZGhost UserCode foldingAdd a code folding implementation based on different strategies (indentation, AST)
![code folding](https://ui.netbeans.org/docs/ui/code_folding/cf_1.gif)
Define shortcutsAdd a code folding implementation based on different strategies (indentation, AST)
![code folding](https://ui.netbeans.org/docs/ui/code_folding/cf_1.gif)
Define shortcutshttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/302Full text of truncated messages cannot be shown2024-03-12T00:08:35ZRüdiger KupperFull text of truncated messages cannot be shownWhen gnome shell shows messages on screen or in the message tray, and the message is too long, it is truncated with "...".
The user expects that pointing the mouse to the shortened message, clicking on it, etc., should reveal the full te...When gnome shell shows messages on screen or in the message tray, and the message is too long, it is truncated with "...".
The user expects that pointing the mouse to the shortened message, clicking on it, etc., should reveal the full text. But this does not happen, the full text is never shown. Clicking the message makes it instantly disappear.
I often have to guess what the messages tries to tell me. This should not happen.
Here's a screenshot of a full screen message, but the same thing happens in the message tray, and also in the application overview (when application descriptions are too long).
![Bildschirmfoto_von_2018-05-24_11-02-52](/uploads/c1ae54d0a1229f6ad6d27f238910563d/Bildschirmfoto_von_2018-05-24_11-02-52.png)https://gitlab.gnome.org/GNOME/gimp/-/issues/1498Nearest color selection (from color reduction) is fatal2020-06-20T21:23:23ZBugzillaNearest color selection (from color reduction) is fatal## Submitted by piotrunio-2004@wp.pl
**[Link to original bug (#796377)](https://bugzilla.gnome.org/show_bug.cgi?id=796377)**
## Description
Created attachment 372376
A huge color sample, containing all hues, lighter, darker and less...## Submitted by piotrunio-2004@wp.pl
**[Link to original bug (#796377)](https://bugzilla.gnome.org/show_bug.cgi?id=796377)**
## Description
Created attachment 372376
A huge color sample, containing all hues, lighter, darker and less saturated, as well as grayscale.
It pathetically chooses the nearest color. The nearest color pick is very crazy and irregular.
Attachment picture reduced to the 8 classic colors (no dithering) looks like THIS:
![jJlT7Vi](/uploads/dd83552e776f6b5b4250490caa4d7e5e/jJlT7Vi.png)
What the heck is that black and white doing between cyan and blue?! And why does it form strange patterns between the colors? That is not right.
Compare that to the Posterize...d version, which looks perfect:
![tgeR8kl](/uploads/50f624dd37276c20f5854592c30cb930/tgeR8kl.png)
All colors are mapped to the real closest color in that version.
God, the color difference should be calculated with this formula: rederror+2×greenerror+blueerror. Where Xerror is the difference in the X channel. Then pick the color with the lowest difference from the original, and if some colors tie the lowest difference, pick whichever color comes first in the palette; for example, a palette with cyan and yellow will pick cyan for white, but a palette with yellow and cyan will pick yellow for white.
The Custom Palette Editor could also be reworked. Each new palette added is evaporated each time GIMP is closed. Drag–and–dropping colors in the CPE duplicates them with Untitled name, instead of moving them as expected. Also, there should be an option to create a new palette from image, which will generate a palette containing all unique colors from the image in the order of their first appearance in the image.
**Attachment 372376**, "A huge color sample, containing all hues, lighter, darker and less saturated, as well as grayscale.":
![colorsamplehuge](/uploads/60780a6481eec209fe12e617fca08c97/colorsamplehuge.PNG)
Version: 2.8.18