GNOME issueshttps://gitlab.gnome.org/groups/GNOME/-/issues2023-10-11T02:49:19Zhttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/164osk: Can't input tons of 'e's2023-10-11T02:49:19ZAdrien Plazasosk: Can't input tons of 'e'sWhen holding down a key on the OSK, either this key is inputed many times or a popover with more keys appear. The behavior is inconsistent:
- If I want to check whether a key hides more keys and it doesn't, I end up with tons of times th...When holding down a key on the OSK, either this key is inputed many times or a popover with more keys appear. The behavior is inconsistent:
- If I want to check whether a key hides more keys and it doesn't, I end up with tons of times the same character, which is not good.
- If I want to press many times a key hiding more keys (like 'e'), I can't just hold as it will just make the popover appear, and I have to press it many times.
A way to solve that is by always having a popover appearing when holding a key, this popover would have the secondary keys but also the main one, and by having only keys from a popover to be holdable. This way I know what holding a key will do, I can still input characters many times if needed and I can do it for all character.
If I want to maintain a key pressed, I can afford the extra time of first holding a primary key and then a secondary one for consistency and predictability even if the secondary one is exactly the same as the primary one.GNOME 3.28https://gitlab.gnome.org/GNOME/nautilus/-/issues/338Hide starred entry on sidebar if there are no starred items2019-04-19T13:05:37ZRafael WHide starred entry on sidebar if there are no starred items### Desired behavior
What do you think about hiding the starred items entry in the sidebar if there are no starred items. If the user star a item the entry pop up in the sidebar.
### Benefits of the solution
- remove entry for users don...### Desired behavior
What do you think about hiding the starred items entry in the sidebar if there are no starred items. If the user star a item the entry pop up in the sidebar.
### Benefits of the solution
- remove entry for users don't use starred items feature
- if there are no starred items the entry is empty
### Possible drawbacks
- maybe users could forgot this useful feature
<!-- Ignore the text under this line. -->GNOME 3.28https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/257Wrong dates in all day event setting2018-05-01T07:44:45ZTom BarboříkWrong dates in all day event settingWhen I set event date in range for more than 1 day, for example February 23 to February 24 and set the event as All day, tooltip for this event shows instead of "02/23/2018 - 02/24/2018" "02/23/2018 - 02/25/2018".
I added screenshot so y...When I set event date in range for more than 1 day, for example February 23 to February 24 and set the event as All day, tooltip for this event shows instead of "02/23/2018 - 02/24/2018" "02/23/2018 - 02/25/2018".
I added screenshot so you can see.![Screenshot_from_2018-02-22_17-06-56](/uploads/4c01910c405c6c409d045deb4e0541cf/Screenshot_from_2018-02-22_17-06-56.png)GNOME 3.28https://gitlab.gnome.org/GNOME/gnome-software/-/issues/303Category pages UX review2018-02-22T15:05:22ZAllan DayCategory pages UX reviewAt some point during the 3.27.x cycle, the category page redesign landed. I only just learned of this, so have only just been able to do a quick UX review. Issues that I've observed:
## General issues
The views feel a bit ambiguous in ...At some point during the 3.27.x cycle, the category page redesign landed. I only just learned of this, so have only just been able to do a quick UX review. Issues that I've observed:
## General issues
The views feel a bit ambiguous in general. Reasons for this:
* The two sections of tiles aren't framed - it's not entirely clear what the three larger tiles at the top are for, or what their relationship is with the smaller tiles below.
* The role of the filter drop down isn't clear - it just says "All". All what?
* The placement of the filter and sort options on either side confuses the fact that they perform a similar function.
My suggestion here would be to:
- [x] Add a "Featured <category name> heading at the top
- [x] Move the filter and sort drop downs, so they are next to each other
- [x] Give the filter drop down a "Show" label
A bit like this:
![category-pages](/uploads/f3a2741aa37ea09e1de15cdd1905d83c/category-pages.png)
## Add-ons category
This category behaves oddly. The first time I tried it, the notebook widget didn't span the entire width of the window (it was constrained to the same width as the tiles below). Trying it subsequently, opening the category results in the window width expanding so that it shoots off the right side of the screen:
![Screenshot_from_2018-02-16_11-03-18](/uploads/b40395857d6e77b1a439c49165b0069b/Screenshot_from_2018-02-16_11-03-18.png)
The sort drop down doesn't work in the shell extensions section - they are always sorted by name.GNOME 3.28https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/45Use Cantarell Light prominently2023-12-12T14:08:43ZJakub SteinerUse Cantarell Light prominentlyOne of the great new hotness from Cantarell is new weights, particularly the thin weight useful for large titles. It would be desirable to use it for:
- time for the lock screen
- time and notification popover datesOne of the great new hotness from Cantarell is new weights, particularly the thin weight useful for large titles. It would be desirable to use it for:
- time for the lock screen
- time and notification popover datesGNOME 3.28Jakub SteinerJakub Steinerhttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues/401Todo plugin not updating entries from Python files2022-10-06T20:49:11ZChristian HergertTodo plugin not updating entries from Python fileshttps://bugzilla.gnome.org/show_bug.cgi?id=793325
Some quick testing shows that it's working fine in C, but when I test with a Python/GNOME template, it is not responding to changes.https://bugzilla.gnome.org/show_bug.cgi?id=793325
Some quick testing shows that it's working fine in C, but when I test with a Python/GNOME template, it is not responding to changes.GNOME 3.28https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/400Can't build flatpaks on Atomic Workstation2018-02-15T23:58:26ZAndreas NilssonCan't build flatpaks on Atomic Workstation(Might be an issue somewhere else, but not sure where else to file)
I tried to build GNOME Maps on my Fedora Atomic Workstation 27 machine today.
It fails with:
```
Starting build of org.gnome.Maps
(flatpak-builder:201): flatpak-builde...(Might be an issue somewhere else, but not sure where else to file)
I tried to build GNOME Maps on my Fedora Atomic Workstation 27 machine today.
It fails with:
```
Starting build of org.gnome.Maps
(flatpak-builder:201): flatpak-builder-WARNING **: 16:04:20.136: rofiles-fuse not available, doing without
========================================================================
Building module libical in /home/andreasn/.var/app/org.gnome.Builder/cache/gnome-builder/flatpak-builder/build/libical-1
========================================================================
bwrap: Can't mkdir parents for /home/andreasn/.var/app/org.gnome.Builder/cache/gnome-builder/flatpak-builder/build/libical-1: No such file or directory
Error: module libical: Child process exited with code 1
```
This is using Builder 3.27.90 flatpak-nightly
It works fine on my other laptop, also running the same version of Builder, but it's a regular Fedora Workstation system.
Would be thankful if others could test it on their systems running OSTree.GNOME 3.28https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/391Builder should detect new flatpak manifest files2018-03-26T22:21:02ZChristian HergertBuilder should detect new flatpak manifest filesIt would be nice to fix things so that if someone copies a JSON manifest into the file tree, we pick that up and load it.
We need to be slightly careful since those can reference external files (to ensure we reload when depenent files a...It would be nice to fix things so that if someone copies a JSON manifest into the file tree, we pick that up and load it.
We need to be slightly careful since those can reference external files (to ensure we reload when depenent files are updated that would cause a load to finally succeed).GNOME 3.28https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/371Fix flatpak configuration monitoring to update active config2018-01-31T10:30:32ZChristian HergertFix flatpak configuration monitoring to update active configThis was a regression in the refactoring of configuration providers to be thread-safe.
The code could, in general, benefit from a large cleanup in how it reads/writes configs. We might even need to switch to a json parser that allows fo...This was a regression in the refactoring of configuration providers to be thread-safe.
The code could, in general, benefit from a large cleanup in how it reads/writes configs. We might even need to switch to a json parser that allows for non-destructive editing.GNOME 3.28https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/366Code-index get_changes_async() should prefilter list to files that are supported2018-01-27T09:24:32ZChristian HergertCode-index get_changes_async() should prefilter list to files that are supportedCurrently the files check to see if a code index is out of date looks to be always getting the incorrect value of changed. We probably need to filter our list of files to things that have build flags or are known supported (js, etc).
Th...Currently the files check to see if a code index is out of date looks to be always getting the incorrect value of changed. We probably need to filter our list of files to things that have build flags or are known supported (js, etc).
Then our n_files comparison should be more accurate.GNOME 3.28https://gitlab.gnome.org/GNOME/gjs/-/issues/38Clicking on the lock screen crashes gnome shell2019-12-04T12:41:08ZGhost UserClicking on the lock screen crashes gnome shellDescription:
gjs 1:1.50.3-1 is causing serious issues with GNOME's lock screen.
Clicking the lock screen background/wallpaper (before it slides up) with the mouse causes gnome-shell to crash. Additionally, this can be considered a secur...Description:
gjs 1:1.50.3-1 is causing serious issues with GNOME's lock screen.
Clicking the lock screen background/wallpaper (before it slides up) with the mouse causes gnome-shell to crash. Additionally, this can be considered a security concern as it briefly exposes the users desktop and running applications. Downgrading to gjs 1:1.50.2-1 resolves the issue.
Additional info:
* package version: gjs 1:1.50.3-1
Steps to reproduce:
1. Lock screen (Super+L)
2. Use the mouse to click the lock screen background/wallpaper
3. Watch it crashGNOME 3.26 bugfixeshttps://gitlab.gnome.org/GNOME/gnome-contacts/-/issues/88Update the AppData screenshot2022-08-12T19:10:40ZNiels De Graefnielsdegraef@gmail.comUpdate the AppData screenshotOur AppData file should get a new screenshot before releasing 3.28, instead of the current one from so many years ago.Our AppData file should get a new screenshot before releasing 3.28, instead of the current one from so many years ago.GNOME 3.28https://gitlab.gnome.org/GNOME/gnome-themes-extra/-/issues/6Optimize PNGs with zopflipng2018-01-28T10:59:31ZBugzillaOptimize PNGs with zopflipng## Submitted by Ville Skyttä
**[Link to original bug (#768307)](https://bugzilla.gnome.org/show_bug.cgi?id=768307)**
## Description
Created attachment 330765
Optimize PNGs with zopflipng
zopflipng produces smaller PNGs than optipng...## Submitted by Ville Skyttä
**[Link to original bug (#768307)](https://bugzilla.gnome.org/show_bug.cgi?id=768307)**
## Description
Created attachment 330765
Optimize PNGs with zopflipng
zopflipng produces smaller PNGs than optipng. Ok if I push this + run all existing *.png (not included in the patch) through zopflipng -m?
**Patch 330765**, "Optimize PNGs with zopflipng":
[0001-Use-zopflipng-to-optimize-PNGs.patch](/uploads/3fd4188263d6901adee1594d6b959fb6/0001-Use-zopflipng-to-optimize-PNGs.patch)
### Depends on
* [Bug 768212](https://bugzilla.gnome.org/show_bug.cgi?id=768212)GNOME 3.28Juraj Fialajurf@riseup.netJuraj Fialajurf@riseup.nethttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues/358PTY occasionally gets write errors with parallel make2018-01-30T05:18:02ZChristian HergertPTY occasionally gets write errors with parallel makeSometimes, when using the new PTY interceptor, I see an error from make (only during parallel builds) where there is a write error to stdout.
After some instrumentation on ptyintercept.c, it doesn't appear we're closing any FDs. I also ...Sometimes, when using the new PTY interceptor, I see an error from make (only during parallel builds) where there is a write error to stdout.
After some instrumentation on ptyintercept.c, it doesn't appear we're closing any FDs. I also increased our buffer sizes, but that had little-or-no effect.
The VTE test program I made doesn't seem to exhibit the behavior. I'm not sure if we're just very timing sensitive or what.GNOME 3.28Christian HergertChristian Hergerthttps://gitlab.gnome.org/GNOME/gjs/-/issues/33Gnome Shell crash with places-status extension when you plug an USB device2019-12-04T12:41:08ZRaphaël Hertzoghertzog@debian.orgGnome Shell crash with places-status extension when you plug an USB deviceThis issue has been first reported to Kali here: https://bugs.kali.org/view.php?id=4488
With gnome 3.26 as in Debian testing/unstable, if you have the places-status extension enabled and if you plug an USB device, the entire session cra...This issue has been first reported to Kali here: https://bugs.kali.org/view.php?id=4488
With gnome 3.26 as in Debian testing/unstable, if you have the places-status extension enabled and if you plug an USB device, the entire session crashes. It does not happen every time, but on my test VM it happens half of the time (50% of my tests show a session crash).
We tracked this down to a regression in gjs. This problem started with the 1.50.2-3 version in Debian which cherry-picked a few commits from 1.50.3. The version 1.50.2-2 of Debian was fine. Then new version 1.50.3-1 currently in Debian unstable is also affected.
Here are the patches which were cherry-picked in that earlier version:
https://salsa.debian.org/gnome-team/gjs/tree/debian/1.50.2-3/debian/patches
I tried to run gnome-shell under gdb but I don't get a backtrace... the process seems to "exit(1)". I will happily test any patch or provide further information on request.
Unfortunately the systemd log doesn't seem to show anything useful. I still paste it here for you to double check (messages between the kernel detecting the new device and the confirmation that the GNOME Shell is gone):
```
Jan 23 18:08:43 kali-rolling gnome-shell[3431]: GNOME Shell started at Tue Jan 23 2018 18:08:41 GMT+0100 (CET)
Jan 23 18:08:47 kali-rolling kernel: usb 2-3: new high-speed USB device number 9 using ehci-pci
Jan 23 18:08:48 kali-rolling kernel: usb 2-3: New USB device found, idVendor=090c, idProduct=1000
Jan 23 18:08:48 kali-rolling kernel: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 23 18:08:48 kali-rolling kernel: usb 2-3: Product: USB DISK
Jan 23 18:08:48 kali-rolling kernel: usb 2-3: Manufacturer: SMI Corporation
Jan 23 18:08:48 kali-rolling kernel: usb-storage 2-3:1.0: USB Mass Storage device detected
Jan 23 18:08:48 kali-rolling kernel: scsi host2: usb-storage 2-3:1.0
Jan 23 18:08:48 kali-rolling mtp-probe[3472]: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:06.7/usb2/2-3"
Jan 23 18:08:48 kali-rolling mtp-probe[3472]: bus: 2, device: 9 was not an MTP device
Jan 23 18:08:48 kali-rolling upowerd[612]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:06.7/usb2/2-3/2-3:1.0
Jan 23 18:08:48 kali-rolling upowerd[612]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:06.7/usb2/2-3
Jan 23 18:08:48 kali-rolling dbus-daemon[343]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.328' (uid=127 pid=3473 comm="/usr/lib/colord/colord-sane ")
Jan 23 18:08:48 kali-rolling dbus-daemon[343]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Jan 23 18:08:49 kali-rolling kernel: scsi 2:0:0:0: Direct-Access MIMOBOT 1100 PQ: 0 ANSI: 4
Jan 23 18:08:49 kali-rolling kernel: sd 2:0:0:0: Attached scsi generic sg1 type 0
Jan 23 18:08:49 kali-rolling kernel: sd 2:0:0:0: [sda] 15360000 512-byte logical blocks: (7.86 GB/7.32 GiB)
Jan 23 18:08:49 kali-rolling kernel: sd 2:0:0:0: [sda] Write Protect is off
Jan 23 18:08:49 kali-rolling kernel: sd 2:0:0:0: [sda] Mode Sense: 43 00 00 00
Jan 23 18:08:49 kali-rolling kernel: sd 2:0:0:0: [sda] No Caching mode page found
Jan 23 18:08:49 kali-rolling kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Jan 23 18:08:49 kali-rolling kernel: sda: sda1 sda2
Jan 23 18:08:49 kali-rolling kernel: sd 2:0:0:0: [sda] Attached SCSI removable disk
Jan 23 18:08:50 kali-rolling dbus-daemon[343]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' requested by ':1.329' (uid=127 pid=3473 comm="/usr/lib/colord/colord-sane ")
Jan 23 18:08:50 kali-rolling dbus-daemon[343]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Jan 23 18:08:50 kali-rolling kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jan 23 18:08:50 kali-rolling udisksd[934]: Failed to setup systemd-based mount point cleanup: Process reported exit code 5: Failed to start clean-mount-point@media-root-P1-FAT32.service: Unit media-root-P1-FAT32.mount not found.
Jan 23 18:08:50 kali-rolling udisksd[934]: Mounted /dev/sda1 at /media/root/P1-FAT32 on behalf of uid 0
Jan 23 18:08:50 kali-rolling kernel: EXT4-fs (sda2): recovery complete
Jan 23 18:08:50 kali-rolling kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Jan 23 18:08:50 kali-rolling udisksd[934]: Failed to setup systemd-based mount point cleanup: Process reported exit code 5: Failed to start clean-mount-point@media-root-P2-EXT4.service: Unit media-root-P2-EXT4.mount not found.
Jan 23 18:08:50 kali-rolling udisksd[934]: Mounted /dev/sda2 at /media/root/P2-EXT4 on behalf of uid 0
Jan 23 18:08:50 kali-rolling polkitd(authority=local)[403]: Unregistered Authentication Agent for unix-session:11 (system bus name :1.323, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jan 23 18:08:50 kali-rolling gnome-session[3000]: gnome-session-binary[3000]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 23 18:08:50 kali-rolling gnome-session-binary[3000]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Jan 23 18:08:50 kali-rolling gnome-session[3000]: gnome-session-binary[3000]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Jan 23 18:08:50 kali-rolling gnome-session-binary[3000]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
```GNOME 3.26 bugfixesPhilip ChimentoPhilip Chimentohttps://gitlab.gnome.org/GNOME/gnome-music/-/issues/135"assertion 'iter_is_valid (iter, list_store)' failed" error messages in playl...2018-01-23T00:40:11ZJean Felder"assertion 'iter_is_valid (iter, list_store)' failed" error messages in playlistviewSometimes, the following messages appears from playlistview. It seems related to self._iter_to_clean:
```
(gnome-music:21108): Gtk-CRITICAL **: 10:23:33.068: gtk_list_store_set_value: assertion 'iter_is_valid (iter, list_store)' failed...Sometimes, the following messages appears from playlistview. It seems related to self._iter_to_clean:
```
(gnome-music:21108): Gtk-CRITICAL **: 10:23:33.068: gtk_list_store_set_value: assertion 'iter_is_valid (iter, list_store)' failed
```
Steps to reproduce:
1. Go to playlist view
2. Select a playlist and start a song
3. Select an other playlist
4. launch a new songGNOME 3.28https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/338Builder configuration selection not re-applied on subsequent project loads2018-01-31T11:37:36ZBugzillaBuilder configuration selection not re-applied on subsequent project loads## Submitted by Jan-Michael Brummer `@jbrummer`
**[Link to original bug (#791905)](https://bugzilla.gnome.org/show_bug.cgi?id=791905)**
## Description
Currently builder switches build system to flatpak once a flatpak json file is de...## Submitted by Jan-Michael Brummer `@jbrummer`
**[Link to original bug (#791905)](https://bugzilla.gnome.org/show_bug.cgi?id=791905)**
## Description
Currently builder switches build system to flatpak once a flatpak json file is detected. Even after switching to "Default" host operating compilation this setting is not persisted. Restarting builder again switches to flatpak.GNOME 3.28https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/336Create a new file, save as freeze2018-01-27T07:19:37ZBugzillaCreate a new file, save as freeze## Submitted by Daniel Espinosa Ortiz `@esodan`
**[Link to original bug (#791829)](https://bugzilla.gnome.org/show_bug.cgi?id=791829)**
## Description
Using Ctrl+N to create a new file, then save as and type a name freeze the GtkFil...## Submitted by Daniel Espinosa Ortiz `@esodan`
**[Link to original bug (#791829)](https://bugzilla.gnome.org/show_bug.cgi?id=791829)**
## Description
Using Ctrl+N to create a new file, then save as and type a name freeze the GtkFileChooser dialog but Builder is responsive.
The problem seems to be related to autocompletion, as I have lot of files with same prefix, after writing first letter tries dialog just freeze and I need to close Builder using window's close button, as Builder is responsive.GNOME 3.28https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/263New project flatpak JSON contains invalid JSON after changing Configure Options2018-01-31T06:45:16ZBugzillaNew project flatpak JSON contains invalid JSON after changing Configure Options## Submitted by Link Dupont `@subpop`
**[Link to original bug (#785831)](https://bugzilla.gnome.org/show_bug.cgi?id=785831)**
## Description
STEPS TO REPRODUCE
1. Create new GNOME project
2. Select 'Build Preferences' (Alt-,)
3. Ad...## Submitted by Link Dupont `@subpop`
**[Link to original bug (#785831)](https://bugzilla.gnome.org/show_bug.cgi?id=785831)**
## Description
STEPS TO REPRODUCE
1. Create new GNOME project
2. Select 'Build Preferences' (Alt-,)
3. Add --enable-debug to 'Configure Options'
EXPECTED RESULTS
The '--enable-debug' option to be added to the flatpak JSON file.
ACTUAL RESULTS
The JSON file ends up with some invalid unicode characters. This diff:
diff --git a/org.gnome.TestJson.json b/org.gnome.TestJson.json
index c38fd29..641ef30 100644
--- a/org.gnome.TestJson.json
+++ b/org.gnome.TestJson.json
@@ -46,7 +46,8 @@
"type": "git",
"url": "file:///home/link/Projects/test-json"
}
- ]
- }
+`<C0>``<94>`,
+ "config-opts": ["--enable-debug"],
]
+ }
}
NOTES
Typing into the Configure Options text field is also extremely laggy. It feels as if some heavy validation is being run on each character entry into the field.
gnome-builder-3.24.2-2.fc26.x86_64GNOME 3.28https://gitlab.gnome.org/GNOME/gnome-music/-/issues/4artist search returns all songs2018-02-04T23:58:50ZMarinus Schraalmschraal@gnome.orgartist search returns all songsSearching for artist returns all songs on a hit, instead of songs specific to that artist. Works correctly for albums/artists.Searching for artist returns all songs on a hit, instead of songs specific to that artist. Works correctly for albums/artists.GNOME 3.28