GNOME issueshttps://gitlab.gnome.org/groups/GNOME/-/issues2023-07-19T16:31:46Zhttps://gitlab.gnome.org/GNOME/evolution/-/issues/571IMAPx QResync: Folder doesn't show all messages actually in it2023-07-19T16:31:46ZBrian J. MurrellIMAPx QResync: Folder doesn't show all messages actually in itI have a folder on my evolution (version doesn't really matter since this has been going on for literally many years, but it is the most recent on Fedora 30) that never shows all of the messages that are actually in the folder.
Quite su...I have a folder on my evolution (version doesn't really matter since this has been going on for literally many years, but it is the most recent on Fedora 30) that never shows all of the messages that are actually in the folder.
Quite super annoyingly this is my _sent_ folder. I know there are more messages than evolution is showing me because if I start evolution on another Fedora 30 machine it shows me all of the messages in the folder and the folder reports that there are 114 messages in it.
On the broken evolution it only reports 83 messages.
I have tried to work this issue on IRC a number of times but it never goes anywhere near resolving the issue before the conversation just dies out.
Can we please get this resolved?https://gitlab.gnome.org/GNOME/libchamplain/-/issues/48devhelp is not showing the documentation2019-08-12T14:16:03ZLaurent Bigonvilledevhelp is not showing the documentationHello,
devhelp is not showing champlain documentation because the directory is called `champlain-0.12` and the devhelp file inside is called `champlain.devhelp2`Hello,
devhelp is not showing champlain documentation because the directory is called `champlain-0.12` and the devhelp file inside is called `champlain.devhelp2`https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/15183.33.90 Sound bar doesnt properly update2019-08-12T10:02:40ZBjörn Daase3.33.90 Sound bar doesnt properly updateWhen pressing the media control keys for increasing and decreasing the volume the volume changes absolutely correctly step by step. The echo sign also updates correctly. Only the sound bar does not updated correctly and only jumps betwee...When pressing the media control keys for increasing and decreasing the volume the volume changes absolutely correctly step by step. The echo sign also updates correctly. Only the sound bar does not updated correctly and only jumps between 0 and 100. See this video
![Screencast_from_12.08.2019_11_45_46](/uploads/bc48c02cf01072aa437ef05f8427e399/Screencast_from_12.08.2019_11_45_46.webm)
This problem did not exist in 3.33.4.https://gitlab.gnome.org/GNOME/mutter/-/issues/726gnome-shell 3.33.4 crashes when disconnecting a WD15 dock2019-10-04T12:36:12ZBjörn Daasegnome-shell 3.33.4 crashes when disconnecting a WD15 dockI have a Dell XPS 13 9370 which is connected to an external monitor via a Dell WD15 dock. I run Fedora Rawhide with gnome-shell 3.33.4. When I have a running gnome session and disconnect my dock, gnome-shell crashes and brings me back to...I have a Dell XPS 13 9370 which is connected to an external monitor via a Dell WD15 dock. I run Fedora Rawhide with gnome-shell 3.33.4. When I have a running gnome session and disconnect my dock, gnome-shell crashes and brings me back to gdm. This can be found in the journal right after the crash
```
Aug 08 18:50:59 xps-9370 audit[1773]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=1773 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=11 res=1
Aug 08 18:51:00 xps-9370 org.gnome.Shell.desktop[1773]: (EE) failed to read Wayland events: Broken pipe
Aug 08 18:51:01 xps-9370 org.gnome.Shell.desktop[3246]: glamor: No eglstream capable devices found
Aug 08 18:51:02 xps-9370 gnome-shell[3246]: g_dir_open_with_errno: assertion 'path != NULL' failed
Aug 08 18:51:02 xps-9370 gnome-shell[3246]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Aug 08 18:51:02 xps-9370 gnome-shell[3246]: g_dir_open_with_errno: assertion 'path != NULL' failed
Aug 08 18:51:02 xps-9370 gnome-shell[3246]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Aug 08 18:51:02 xps-9370 gnome-shell[3246]: Getting invalid resource scale property
```
This interestingly does not happen, when I have the monitor connected directly to my laptop. It happens only if I have the dock in between.
It also does only occur in Wayland sessions, not in an Xorg session.
The problem was also not there in 3.32.2.
Edit: If I reconnect the dock, the external monitor is not recognized any more (all other connected devices, e.g. drivers, speaker... are working). Restarting gnome-shell is not enough. I have to reboot completely.
https://gitlab.gnome.org/GNOME/epiphany/-/issues/879The Override Text Encoding dialog is confusing2022-07-08T12:31:35ZAdrien PlazasThe Override Text Encoding dialog is confusingThe current design of the Override Text Encoding dialog can be confusing:
- to see any of the possible actions, you first have to disable using the current encoding
- but that doesn't mean any other encoding will be used
- now you can ex...The current design of the Override Text Encoding dialog can be confusing:
- to see any of the possible actions, you first have to disable using the current encoding
- but that doesn't mean any other encoding will be used
- now you can expand the encodings list
- selecting an encoding will apply it immediatly
- then I'll have to close the page manually
It feels a bit weird to me, is there a good reason for that design?
I suggest:
- making the recommended encoding a prominent option and not a toggle
- making the encodings list available directly (avoiding a click to the users)
- have Cancel and Apply buttons
- selecting an encoding wouldn't do a thing, applying would (avoiding some confusion for the same amount of clicks)
The only downside of that design is that to test different encodings, you would have to open the dialog multiple times.
See https://source.puri.sm/Librem5/Apps_Issues/issues/91 for more on the confusion caused by the current design.https://gitlab.gnome.org/GNOME/gtk/-/issues/2092Windowlist Buttons with Adwaita on Xfce2019-08-12T08:43:00ZLioh MoellerWindowlist Buttons with Adwaita on XfceHi all,
I am using the Adwaita theme on Xfce 4.14 and would like to ask if it is possible to increase the spacing between the windowlist buttons a bit: ![xfce_4_windowlist_spacing](/uploads/ad4c6b42b666275f6d55696f8a1ee70f/xfce_4_window...Hi all,
I am using the Adwaita theme on Xfce 4.14 and would like to ask if it is possible to increase the spacing between the windowlist buttons a bit: ![xfce_4_windowlist_spacing](/uploads/ad4c6b42b666275f6d55696f8a1ee70f/xfce_4_windowlist_spacing.png)
Right now the windowlist buttons stick completely together and it would be great to have at lease 1px spacing between them.https://gitlab.gnome.org/GNOME/libchamplain/-/issues/47Please drop buildpath from champlain-enum-types.h2019-10-20T20:23:23ZLaurent BigonvillePlease drop buildpath from champlain-enum-types.hHello,
When building champlain, the resulting champlain-enum-types.h file contains reference to the build path, this might prevent to make champlain reproducible.
Could you please drop this?Hello,
When building champlain, the resulting champlain-enum-types.h file contains reference to the build path, this might prevent to make champlain reproducible.
Could you please drop this?https://gitlab.gnome.org/GNOME/retro-gtk/-/issues/26Document the pixbuf metadata2019-08-12T08:03:46ZAdrien PlazasDocument the pixbuf metadataSome metadata is stored in the GdkPixbuf generated by a RetroPixdata, but it's not documented so it's virtually undiscoverable.Some metadata is stored in the GdkPixbuf generated by a RetroPixdata, but it's not documented so it's virtually undiscoverable.https://gitlab.gnome.org/GNOME/mutter/-/issues/725Settings app crashes with Wayland, in cc_display_settings_rebuild_ui2019-08-13T15:09:06ZGhost UserSettings app crashes with Wayland, in cc_display_settings_rebuild_uiI am on a newly installed Fedora Workstation 30. My device (GPD Win 2) comes with a screen that has wrong default orientation, so my first course of action after installation was to rotate the screen in Settings. The app however crashes ...I am on a newly installed Fedora Workstation 30. My device (GPD Win 2) comes with a screen that has wrong default orientation, so my first course of action after installation was to rotate the screen in Settings. The app however crashes before I can get to the display settings, with this output:
```
[tear@localhost ~]$ gnome-control-center
(gnome-control-center:3236): display-cc-panel-WARNING **: 09:48:36.194: Monitor at eDP-1 has no modes?
**
display-cc-panel:ERROR:../panels/display/cc-display-settings.c:275:cc_display_settings_rebuild_ui: assertion failed: (modes)
Aborted (core dumped)
```
It appears that the display reports invalid EDID data:
```
[tear@localhost ~]$ edid-decode /sys/class/drm/card0-eDP-1/edid
Extracted contents:
header: 00 ff ff ff ff ff ff 00
serial number: 32 8d 37 39 5f 02 00 00 16 1c
version: 01 03
basic params: 80 0d 08 78 0a
chroma info: 0d c9 a0 57 47 98 27 12 48 4c
established: 00 00 00
standard: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1: ac 19 d0 78 20 00 18 50 32 14 84 00 a0 5a 00 00 00 1e
descriptor 2: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 3: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 4: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
extensions: 00
checksum: 29
EDID version: 1.3
Manufacturer: LTM Model 3937 Serial Number 607
Made in week 22 of 2018
Digital display
Maximum image size: 13 cm x 8 cm
Gamma: 2.20
RGB color display
First detailed timing is preferred timing
Display x,y Chromaticity:
Red: 0.6250, 0.3398
Green: 0.2802, 0.5947
Blue: 0.1552, 0.0703
White: 0.2832, 0.2978
Established timings supported:
Standard timings supported:
Detailed mode: Clock 65.720 MHz, 160 mm x 90 mm
720 770 790 840 hborder 0
1280 1288 1292 1304 vborder 0
+hsync +vsync
VertFreq: 59 Hz, HorFreq: 78238 Hz
Manufacturer-specified data, tag 0
Manufacturer-specified data, tag 0
Manufacturer-specified data, tag 0
Checksum: 0x29 (valid)
EDID block does NOT conform to EDID 1.3!
Missing name descriptor
Missing monitor ranges
```
The screen however works as expected on Windows 10 as well as Plasma on Xorg, and is able to be rotated in both cases. I think it is reasonable to expect GNOME/Wayland to handle the invalid data as gracefully as other environments.
System info:
Intel Core m3-7Y30
Intel HD Graphics 615
Built-in 720p display, portrait but mounted in landscape
Fedora Workstation 30, freshly installed and fully updated
Linux 5.2.6-200.fc30.x86_64
[backtrace](/uploads/141e2dff42192df22a6b354936c08a97/backtrace)https://gitlab.gnome.org/GNOME/mutter/-/issues/724Assertion failure when fullscreening Proton-based games2019-08-12T00:18:41ZGeorges Basile Stavracas NetoAssertion failure when fullscreening Proton-based gamesIt's 3am and I'm staying overnight in the airport. My brain is unable to sleep on public spaces so I open Steam and run "The Binding of Isaac".
It starts in window mode, so I press "f" to fullscreen it.
Session down.
In the system jou...It's 3am and I'm staying overnight in the airport. My brain is unable to sleep on public spaces so I open Steam and run "The Binding of Isaac".
It starts in window mode, so I press "f" to fullscreen it.
Session down.
In the system journal, I notice:
```
ago 12 02:11:40 feareniar-x1 org.gnome.Shell.desktop[19370]: **
ago 12 02:11:40 feareniar-x1 org.gnome.Shell.desktop[19370]: mutter:ERROR:../src/compositor/meta-window-actor.c:374:meta_window_actor_real_assign_surface_actor: assertion failed: (!priv->surface)
```
Perhaps `MetaXwayland` should do something else before calling `meta_window_actor_assign_surface_actor()`?https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/398file sharing GAVE GUEST READ WRITE ACCESS TO MY WHOLE HOME DIRECTORY instead ...2019-08-12T20:46:25ZGhost Userfile sharing GAVE GUEST READ WRITE ACCESS TO MY WHOLE HOME DIRECTORY instead of actually assigned share folderI've set my share folder to /home/boxshares and in most cases, the folder share works as meant. But it some situations, gnome-boxes will give the guest read-write access to all my directory - aka /home/myusername.
This seems to occur w...I've set my share folder to /home/boxshares and in most cases, the folder share works as meant. But it some situations, gnome-boxes will give the guest read-write access to all my directory - aka /home/myusername.
This seems to occur when a live snapshot of the guest has been taken while the folder share has been mounted. Upon restoring the guest, the guest folder is no longer mounted and in it's place is my home directory with full read and write access to everything.
How to reproduce (I'm only running Linux VM, I don't know if this is happening in other guest OSs):
1) setup a folder sharing
2) start vm
3) go to nautilus in guest, hit Other Locations in the sidebar and mount your folder share
4) close VM, either by hitting Ctrl+Alt,Alt-F4 or taking a snapshot and quitting
5) restore live snapshot and go back to nautilus, the guest should still be mounted but with your home directory instead.
I used the spice-webdavd plugin on a ubuntu 18.04 guest.
This is a very dangerous bug that will put the machine of anyone using a VM to run untrusted apps at risk. https://gitlab.gnome.org/GNOME/pango/-/issues/408Arabic text rendering broken in 1.442019-08-12T17:51:28ZGhost UserArabic text rendering broken in 1.44Arabic text rendering got broken in 1.44. Basicly, diacritics aren't correctly placed, and OpenType/FreeType features (that Mada font uses for example) aren't working.
`pango-view arabicText --font="Mada 42"`:
![Screenshot_٢٠١٩٠٨١٢_٠١٢٠...Arabic text rendering got broken in 1.44. Basicly, diacritics aren't correctly placed, and OpenType/FreeType features (that Mada font uses for example) aren't working.
`pango-view arabicText --font="Mada 42"`:
![Screenshot_٢٠١٩٠٨١٢_٠١٢٠٣٣](/uploads/524ef4292164a841986db116c5a42f7a/Screenshot_٢٠١٩٠٨١٢_٠١٢٠٣٣.png)
Expected (LO Writer 6.2.5.2):
![Screenshot_٢٠١٩٠٨١٢_٠١٢٤٥٦](/uploads/36fb75069db7ace6866cadb64e14a66c/Screenshot_٢٠١٩٠٨١٢_٠١٢٤٥٦.png)
Text:
```
هَذِهِ تَجْرِبَةٌ جَمِيلَةٌ جِدًّا جِدًّا!!
مَا لَكَ لا تُنَفِّذُ مَهَامَكَ يَا رَجُل؟!
```
Fonts tested: Mada: issues with diacritics and dots. Amiri: small bits with Shaddah and Tanwin. Cairo: issues with diacritics. Sakkal Majalla: issues with diacritics. (Other fonts affected but can't test everything)
OS: ArchLinux
Pango vesion: extra/pango 1:1.44.3-1
Cairo version: extra/cairo 1.17.2+17+g52a7c79fd-1https://gitlab.gnome.org/GNOME/gimp/-/issues/3792Issues opening JP2 file with corrupt ICC profile2019-09-01T10:52:21ZAaron BoxerIssues opening JP2 file with corrupt ICC profileThe file is relax.jp2: http://www.fnordware.com/j2k/jp2samples.html
The options are either keep the (corrupt) stored ICC profile, or apply a GIMP sRGB profile.
Could there be a third option to not apply an ICC profile at all ? Only vie...The file is relax.jp2: http://www.fnordware.com/j2k/jp2samples.html
The options are either keep the (corrupt) stored ICC profile, or apply a GIMP sRGB profile.
Could there be a third option to not apply an ICC profile at all ? Only viewers that are not ICC-aware
will display this image "correctly".https://gitlab.gnome.org/GNOME/gimp/-/issues/37912.10.12 JPEG 2000 Support2019-08-11T21:29:34ZAaron Boxer2.10.12 JPEG 2000 SupportI'm really happy with the improved j2k support in the latest version. Unfortunately, gimp fails to open many files in the [openjpeg test suite](https://github.com/uclouvain/openjpeg-data/tree/master/input/nonregression). So, apparently g...I'm really happy with the improved j2k support in the latest version. Unfortunately, gimp fails to open many files in the [openjpeg test suite](https://github.com/uclouvain/openjpeg-data/tree/master/input/nonregression). So, apparently gimp isn't using `openjpeg`. Are there plans to improve stability or switch to `openjpeg` ?https://gitlab.gnome.org/GNOME/epiphany/-/issues/878About version is wrong2019-09-03T16:12:56ZJan-Michael BrummerAbout version is wrongUsing a compiled master version of Epiphany shows:
**3.29.2**-1036-g462704e70Using a compiled master version of Epiphany shows:
**3.29.2**-1036-g462704e70https://gitlab.gnome.org/GNOME/mutter/-/issues/723Crash in MetaWaylandKeyboard send_keymap2020-07-12T02:08:05ZMichael CatanzaroCrash in MetaWaylandKeyboard send_keymapHere's another full-desktop crash:
```
#0 0x00007f6539924e75 in __GI_raise (sig=<optimized out>)
at ../sysdeps/unix/sysv/linux/raise.c:50
set =
{__val = {0, 94844108963616, 117, 8522508671030602496, 14072779857...Here's another full-desktop crash:
```
#0 0x00007f6539924e75 in __GI_raise (sig=<optimized out>)
at ../sysdeps/unix/sysv/linux/raise.c:50
set =
{__val = {0, 94844108963616, 117, 8522508671030602496, 140727798577280, 94844107947472, 94844105775152, 140072689635405, 2641133429, 8522508671030602496, 140727798577176, 140070896410976, 140727798575976, 140727798576176, 1722769849346318448, 0}}
pid = <optimized out>
tid = <optimized out>
#1 0x00007f6539924f00 in <signal handler called> () at /lib64/libc.so.6
#2 0x00007f6539a4a9f0 in __strcpy_avx2 ()
at ../sysdeps/x86_64/multiarch/strcpy-avx2.S:317
#3 0x00007f6539bb2518 in strcpy
(__src=<optimized out>, __dest=<optimized out>)
at /usr/include/bits/string_fortified.h:90
xkb_info = 0x56429d033940
error = 0x0
fd = 111
keymap_area = <optimized out>
#4 0x00007f6539bb2518 in send_keymap
(keyboard=keyboard@entry=0x56429d0338d0 [MetaWaylandKeyboard], resource=resource@entry=0x5642a0a30ad0) at ../src/wayland/meta-wayland-keyboard.c:161
xkb_info = 0x56429d033940
error = 0x0
fd = 111
keymap_area = <optimized out>
#5 0x00007f6539bb33f4 in meta_wayland_keyboard_create_new_resource (keyboard=0x56429d0338d0 [MetaWaylandKeyboard], client=0x56429d7d6240, seat_resource=<optimized out>, id=<optimized out>) at ../src/wayland/meta-wayland-keyboard.c:992
resource = 0x5642a0a30ad0
#6 0x00007f6538e54b28 in ffi_call_unix64 () at ../src/x86/unix64.S:76
#7 0x00007f6538e54339 in ffi_call (cif=cif@entry=0x7ffdbe71baf0, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x0, avalue=avalue@entry=0x7ffdbe71bbc0) at ../src/x86/ffi64.c:525
classes = {X86_64_INTEGERSI_CLASS, 32765, 954552416, 32613}
stack = <optimized out>
argp = 0x7ffdbe71b9c0 ""
arg_types = <optimized out>
gprcount = 3
ssecount = <optimized out>
ngpr = 1
nsse = 0
i = <optimized out>
avn = <optimized out>
ret_in_memory = <optimized out>
reg_args = <optimized out>
#8 0x00007f6536e8a1b7 in wl_closure_invoke (closure=closure@entry=0x56429ff42010, flags=flags@entry=2, target=<optimized out>, target@entry=0x5642a0760290, opcode=opcode@entry=1, data=<optimized out>, data@entry=0x56429d7d6240) at src/connection.c:1014
count = 1
cif = {abi = FFI_UNIX64, nargs = 3, arg_types = 0x7ffdbe71bb10, rtype = 0x7f6538e55180 <ffi_type_void>, bytes = 0, flags = 0}
ffi_types = {0x7f6538e55060 <ffi_type_pointer>, 0x7f6538e55060 <ffi_type_pointer>, 0x7f6538e550e0 <ffi_type_uint32>, 0x7f6538e55060 <ffi_type_pointer>, 0x7ffdbe71bbb8, 0x7f6536e8a875 <wl_os_recvmsg_cloexec+37>, 0x7ffdbe71bd60, 0x7ffdbe71bb90, 0x5642a06c2c00, 0x0, 0x0, 0x56429c3e0600, 0x0, 0x7f6536e88c41 <wl_connection_read+241>, 0x0, 0x5642a06c4c10, 0x0, 0x0, 0x7ffdbe71bbd0, 0x2, 0x7ffdbe71bbf0, 0x0}
ffi_args = {0x7ffdbe71bae0, 0x7ffdbe71bae8, 0x56429ff42028, 0x7646087b6bf72b00, 0x1d, 0x56429d7d6270, 0x56429ff42030, 0x7f6536e8aead <wl_map_reserve_new+109>, 0x56429d7d6240, 0x7f6536e8d2f8, 0x7ffdbe71bc70, 0x7f6536e89c0c <wl_connection_demarshal+492>, 0x56429ff420ec, 0x5642a06c2c00, 0x56429ff420e0, 0x56429ff42010, 0xcbe71be50, 0x7f6536e89f0f <wl_closure_lookup_objects+111>, 0x7f6538d90f78 <wl_seat_requests+24>, 0x7f6536e84d46 <log_closure+70>, 0x7f6538d90f78 <wl_seat_requests+24>, 0xffffffff}
implementation = <optimized out>
#9 0x00007f6536e86d32 in wl_client_connection_data (fd=<optimized out>, mask=<optimized out>, data=0x56429d7d6240) at src/wayland-server.c:429
client = 0x56429d7d6240
connection = 0x5642a06c2c00
resource = 0x5642a0760290
object = 0x5642a0760290
closure = 0x56429ff42010
message = 0x7f6538d90f78 <wl_seat_requests+24>
p = {15, 786433}
resource_flags = <optimized out>
opcode = 1
size = <optimized out>
since = <optimized out>
len = <optimized out>
#10 0x00007f6536e8836a in wl_event_loop_dispatch (loop=0x56429c3e0600, timeout=timeout@entry=0) at src/event-loop.c:641
ep = {{events = 1, data = {ptr = 0x5642a04a2eb0, fd = -1605751120, u32 = 2689216176, u64 = 94844157046448}}, {events = 0, data = {ptr = 0x7ffdbe71bd40, fd = -1099842240, u32 = 3195125056, u64 = 140727798578496}}, {events = 1, data = {ptr = 0xbe71bd9000000000, fd = 0, u32 = 0, u64 = 13722957965747552256}}, {events = 32765, data = {ptr = 0x50, fd = 80, u32 = 80, u64 = 80}}, {events = 0, data = {ptr = 0x9cf3ba0000000000, fd = 0, u32 = 0, u64 = 11309587598420213760}}, {events = 22082, data = {ptr = 0x7ffdbe71bdd0, fd = -1099842096, u32 = 3195125200, u64 = 140727798578640}}, {events = 2, data = {ptr = 0xbe71be4000000000, fd = 0, u32 = 0, u64 = 13722958721661796352}}, {events = 32765, data = {ptr = 0x7ffdbe78f0b0, fd = -1099370320, u32 = 3195596976, u64 = 140727799050416}}, {events = 1954047348, data = {ptr = 0x26be53f86168635f, fd = 1634231135, u32 = 1634231135, u64 = 2791761145267512159}}, {events = 2086, data = {ptr = 0x7ffdbe71be40, fd = -1099841984, u32 = 3195125312, u64 = 140727798578752}}, {events = 980255077, data = {ptr = 0x22ff00007f65, fd = 32613, u32 = 32613, u64 = 38478612037477}}, {events = 0, data = {ptr = 0x7646087b6bf72b00, fd = 1811360512, u32 = 1811360512, u64 = 8522508671030602496}}, {events = 1, data = {ptr = 0x9ef19f7000000000, fd = 0, u32 = 0, u64 = 11453110630765035520}}, {events = 22082, data = {ptr = 0x56429ef19f70, fd = -1628332176, u32 = 2666635120, u64 = 94844134465392}}, {events = 1811360512, data = {ptr = 0x7fffffff7646087b, fd = 1984301179, u32 = 1984301179, u64 = 9223372034544109691}}, {events = 0, data = {ptr = 0x56429ef19f70, fd = -1628332176, u32 = 2666635120, u64 = 94844134465392}}, {events = 2666636800, data = {ptr = 0x200005642, fd = 22082, u32 = 22082, u64 = 8589956674}}, {events = 0, data = {ptr = 0x7fffffff, fd = 2147483647, u32 = 2147483647, u64 = 2147483647}}, {events = 2621304368, data = {ptr = 0x6a7b6b9000005642, fd = 22082, u32 = 22082, u64 = 7672844656375256642}}, {events = 32612, data = {ptr = 0x7f6538848c51 <_dbus_transport_get_dispatch_status+385>, fd = 948210769, u32 = 948210769, u64 = 140072716635217}}, {events = 3195125376, data = {ptr = 0x6bf72b0000007ffd, fd = 32765, u32 = 32765, u64 = 7779734160305848317}}, {events = 1984301179, data = {ptr = 0x56429da40d40, fd = -1650193088, u32 = 2644774208, u64 = 94844112604480}}, {events = 2666636800, data = {ptr = 0x9ef19f7000005642, fd = 22082, u32 = 22082, u64 = 11453110630765057602}}, {events = 22082, data = {ptr = 0x7646087b6bf72b00, fd = 1811360512, u32 = 1811360512, u64 = 8522508671030602496}}, {events = 2666636800, data = {ptr = 0xbe71bf3800005642, fd = 22082, u32 = 22082, u64 = 13722959786813707842}}, {events = 32765, data = {ptr = 0x7ffdbe71bec0, fd = -1099841856, u32 = 3195125440, u64 = 140727798578880}}, {events = 2147483647, data = {ptr = 0x100000000, fd = 0, u32 = 0, u64 = 4294967296}}, {events = 0, data = {ptr = 0x7f65399f62c3 <__GI___clock_gettime+51>, fd = 966746819, u32 = 966746819, u64 = 140072735171267}}, {events = 2633218560, data = {ptr = 0x399d914c00005642, fd = 22082, u32 = 22082, u64 = 4151634187109029442}}, {events = 32613, data = {ptr = 0x56429d59f580, fd = -1655048832, u32 = 2639918464, u64 = 94844107748736}}, {events = 8, data = {ptr = 0xbe71bee000000000, fd = 0, u32 = 0, u64 = 13722959408856563712}}, {events = 32765, data = {ptr = 0x8, fd = 8, u32 = 8, u64 = 8}}}
source = <optimized out>
i = <optimized out>
count = <optimized out>
#11 0x00007f6539babf9b in wayland_event_source_dispatch (base=base@entry=0x56429d009c80, callback=<optimized out>, data=<optimized out>) at ../src/wayland/meta-wayland.c:91
source = 0x56429d009c80
loop = <optimized out>
#12 0x00007f653a6d8edd in g_main_dispatch (context=0x56429c3dee30) at ../glib/gmain.c:3189
dispatch = <optimized out>
prev_source = 0x0
was_in_call = <optimized out>
user_data = 0x0
callback = 0x0
cb_funcs = 0x0
cb_data = 0x0
need_destroy = <optimized out>
source = 0x56429d009c80
current = 0x56429c3fabc0
i = 0
__FUNCTION__ = "g_main_dispatch"
#13 0x00007f653a6d8edd in g_main_context_dispatch (context=context@entry=0x56429c3dee30) at ../glib/gmain.c:3854
#14 0x00007f653a6d9270 in g_main_context_iterate (context=0x56429c3dee30, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:3927
max_priority = 2147483647
timeout = 3
some_ready = 1
nfds = <optimized out>
allocated_nfds = <optimized out>
fds = 0x56429f43ab50
#15 0x00007f653a6d95a3 in g_main_loop_run (loop=0x56429cff6860) at ../glib/gmain.c:4123
__FUNCTION__ = "g_main_loop_run"
#16 0x00007f6539b66570 in meta_run () at ../src/core/main.c:683
#17 0x000056429afa7b94 in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:499
ctx = <optimized out>
error = 0x0
ecode = <optimized out>
```https://gitlab.gnome.org/GNOME/epiphany/-/issues/877Bookmark search is case sensitive?!2019-08-11T21:09:49ZClément CazaudBookmark search is case sensitive?!Say I have a single bookmark named *Gnome Epiphany*.
If I type `gnome` or `gnome epiphany` in header's search bar, I **do not** get the *Gnome Epiphany* item in the browser's search result box (aka predictions).
If I type `Gnome` in he...Say I have a single bookmark named *Gnome Epiphany*.
If I type `gnome` or `gnome epiphany` in header's search bar, I **do not** get the *Gnome Epiphany* item in the browser's search result box (aka predictions).
If I type `Gnome` in header's search bar, this time, I get the expected search result.
Note that it behaves the same way with bookmark tags.
Since most if not all users are not capitalizing their search keywords and since most bookmark names are capitalized by default during their addition, the bookmark search feature, as it is currently, is not functional or a pain to use.
Having adopted recently Epiphany, I kind of miss the bookmark folder structure other browsers offer. But I just started to convince myself that opening bookmarks via the browser or the gnome (super) search is more convenient, natural (even more with tags) and faster than scrolling the folder structure, opening them and finally find and click the bookmark in middle of many others...
Can we make the search *case insensitive* instead of *case sensitive* so that we get something functional?https://gitlab.gnome.org/GNOME/gimp/-/issues/3790Hyphenation should not apply to Chinese2019-09-10T11:36:31ZGhost UserHyphenation should not apply to ChineseGIMP version: 2.10.12
Operating System: Linux
Package: Arch
# Description of the bug
The text box adds unnecessary hyphenation to Chinese text, regardless of the language setting.
![image](/uploads/be9f56998ee9bec505f42134d0f87287/i...GIMP version: 2.10.12
Operating System: Linux
Package: Arch
# Description of the bug
The text box adds unnecessary hyphenation to Chinese text, regardless of the language setting.
![image](/uploads/be9f56998ee9bec505f42134d0f87287/image.png)
# Reproduction
Is the bug reproducible? Always
Reproduction steps:
1. Open text tool to add text
2. Input Chinese characters
3. Adjust the text box width to cause line wrapping
4. Hyphens appear.
…
Expected result: No hyphens.
Actual result: Hyphens appeared.
# Additional information
This bug didn't exist in 2.10.11 (tested on AppImage-git-2.10.11-20190425)
Perhaps provide an option to manually turn off the hyphenation?
The Chinese characters for you to test:
中文測試。分行時不應該加上連行號。https://gitlab.gnome.org/GNOME/gimp/-/issues/3788Gimp just crashes when adding a new layer or opening a file as layer2024-02-16T22:41:52ZGhost UserGimp just crashes when adding a new layer or opening a file as layerGIMP version: 2.10.12
Operating System: Linux Mint 19.2 XFCE
Package: Flatpak
# Description of the bug
Gimp just crashed, while I was using it.
# Reproduction
Is the bug reproducible?
Randomly, but it happened once.
# Additional ...GIMP version: 2.10.12
Operating System: Linux Mint 19.2 XFCE
Package: Flatpak
# Description of the bug
Gimp just crashed, while I was using it.
# Reproduction
Is the bug reproducible?
Randomly, but it happened once.
# Additional information
```
GNU Image Manipulation Program version 2.10.12
git-describe: GIMP_2_10_12
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-unknown-linux-gnu/8.3.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../configure --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/bin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --enable-deterministic-archives --enable-shared --build=x86_64-pc-linux-gnu --host=x86_64-unknown-linux-gnu lt_cv_sys_lib_dlsearch_path_spec=/usr/lib/x86_64-linux-gnu --target=x86_64-unknown-linux-gnu --disable-multilib --enable-multiarch --disable-bootstrap --with-build-sysroot=/cross-installation --enable-languages=c,c++,fortran --enable-default-pie --enable-default-ssp --without-isl --enable-linker-build-id host_configargs=lt_cv_sys_lib_dlsearch_path_spec=/usr/lib/x86_64-linux-gnu target_configargs=lt_cv_sys_lib_dlsearch_path_spec=/usr/lib/x86_64-linux-gnu
Thread model: posix
gcc version 8.3.0 (GCC)
using GEGL version 0.4.16 (compiled against version 0.4.16)
using GLib version 2.60.4 (compiled against version 2.60.2)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.1)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Aborted
Stack trace:
```
/app/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x3a6)[0x7f4bbdaae8a6]
gimp-2.10(+0xf2b3f)[0x55852143bb3f]
gimp-2.10(gimp_fatal_error+0x1d)[0x55852143bf7d]
gimp-2.10(+0xf36fc)[0x55852143c6fc]
/usr/lib/x86_64-linux-gnu/libpthread.so.0(+0x1306f)[0x7f4bbd4ef06f]
/usr/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10f)[0x7f4bbcd8c55f]
/usr/lib/x86_64-linux-gnu/libc.so.6(abort+0x126)[0x7f4bbcd76854]
/usr/lib/x86_64-linux-gnu/libc.so.6(+0x22728)[0x7f4bbcd76728]
/usr/lib/x86_64-linux-gnu/libc.so.6(__assert_fail+0x45)[0x7f4bbcd84a05]
/usr/lib/x86_64-linux-gnu/libX11.so.6(+0x488aa)[0x7f4bbcb068aa]
/usr/lib/x86_64-linux-gnu/libX11.so.6(+0x4894f)[0x7f4bbcb0694f]
/usr/lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x64)[0x7f4bbcb06c54]
/usr/lib/x86_64-linux-gnu/libX11.so.6(_XData32+0x87)[0x7f4bbcb09907]
/usr/lib/x86_64-linux-gnu/libX11.so.6(XChangeProperty+0xdb)[0x7f4bbcae307b]
/app/lib/libgdk-x11-2.0.so.0(gdk_window_set_icon_list+0x2b6)[0x7f4bbdb92976]
/app/lib/libgtk-x11-2.0.so.0(+0x26ff0b)[0x7f4bbde48f0b]
/app/lib/libgtk-x11-2.0.so.0(+0x274c0a)[0x7f4bbde4dc0a]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19c)[0x7f4bbd23177c]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x28a4b)[0x7f4bbd245a4b]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xddd)[0x7f4bbd24ebbd]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x92)[0x7f4bbd24f272]
/app/lib/libgtk-x11-2.0.so.0(gtk_widget_realize+0xcf)[0x7f4bbde4172f]
/app/lib/libgtk-x11-2.0.so.0(+0x272f9c)[0x7f4bbde4bf9c]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19c)[0x7f4bbd23177c]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x28a4b)[0x7f4bbd245a4b]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xddd)[0x7f4bbd24ebbd]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x92)[0x7f4bbd24f272]
/app/lib/libgtk-x11-2.0.so.0(gtk_widget_show+0x85)[0x7f4bbde40eb5]
gimp-2.10(layers_new_cmd_callback+0x11b)[0x5585214649db]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19c)[0x7f4bbd23177c]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x288a4)[0x7f4bbd2458a4]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xddd)[0x7f4bbd24ebbd]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x92)[0x7f4bbd24f272]
/app/lib/libgtk-x11-2.0.so.0(+0x85cf3)[0x7f4bbdc5ecf3]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19c)[0x7f4bbd23177c]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x28a4b)[0x7f4bbd245a4b]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0xddd)[0x7f4bbd24ebbd]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x92)[0x7f4bbd24f272]
/app/lib/libgtk-x11-2.0.so.0(gtk_widget_activate+0x81)[0x7f4bbde3a111]
/app/lib/libgtk-x11-2.0.so.0(gtk_menu_shell_activate_item+0x15c)[0x7f4bbdd32adc]
/app/lib/libgtk-x11-2.0.so.0(+0x159dad)[0x7f4bbdd32dad]
/app/lib/libgtk-x11-2.0.so.0(+0x1470ea)[0x7f4bbdd200ea]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x19c)[0x7f4bbd23177c]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x280fc)[0x7f4bbd2450fc]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x4aa)[0x7f4bbd24e28a]
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x92)[0x7f4bbd24f272]
/app/lib/libgtk-x11-2.0.so.0(+0x2623bb)[0x7f4bbde3b3bb]
/app/lib/libgtk-x11-2.0.so.0(gtk_propagate_event+0xab)[0x7f4bbdd1e28b]
/app/lib/libgtk-x11-2.0.so.0(gtk_main_do_event+0x2ea)[0x7f4bbdd1e67a]
/app/lib/libgdk-x11-2.0.so.0(+0x61aef)[0x7f4bbdb7daef]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2ad)[0x7f4bbd149ffd]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x53297)[0x7f4bbd14a297]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0xc1)[0x7f4bbd14a5c1]
gimp-2.10(app_run+0x34e)[0x55852143b34e]
gimp-2.10(main+0x3a5)[0x55852143abf5]
/usr/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf2)[0x7f4bbcd783e2]
gimp-2.10(_start+0x2d)[0x55852143ad7d]
```https://gitlab.gnome.org/GNOME/gtk/-/issues/2091FileChooser: Allow image preview pane2019-08-12T08:44:52ZGhost UserFileChooser: Allow image preview paneCurrently it is nearly impossible to differentiate the different between graphical files when trying to choose them, say to attach to an email, or attach to a chat. I think we should have an option to allow preview of image pane, much l...Currently it is nearly impossible to differentiate the different between graphical files when trying to choose them, say to attach to an email, or attach to a chat. I think we should have an option to allow preview of image pane, much like any other file chooser allows for you to have, except for gnome.
Please add this as a feature, even if it is a hidden feature that is required to have turned on via gnome tweak tool or dconf-editor.
Thank you.