GNOME issueshttps://gitlab.gnome.org/groups/GNOME/-/issues2024-01-10T18:23:39Zhttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1598Enabling high contrast breaks icons2024-01-10T18:23:39ZJakub SteinerEnabling high contrast breaks iconsWe'll likely find the problem elsewhere in the stack, but Settings completely breaks witching to high contrast accessibility settings.
![Screenshot_from_2022-01-26_10-23-51](/uploads/2d3e31be5ea3c3c3abe44c134ebb9a25/Screenshot_from_2022...We'll likely find the problem elsewhere in the stack, but Settings completely breaks witching to high contrast accessibility settings.
![Screenshot_from_2022-01-26_10-23-51](/uploads/2d3e31be5ea3c3c3abe44c134ebb9a25/Screenshot_from_2022-01-26_10-23-51.png)
![Screenshot_from_2022-01-26_10-23-56](/uploads/dab6e702a60f93fb08efe5c6017f210f/Screenshot_from_2022-01-26_10-23-56.png)Jakub SteinerJakub Steinerhttps://gitlab.gnome.org/GNOME/libshumate/-/issues/30Missing signal map position changed2022-04-02T21:24:30ZZwarfMissing signal map position changedI try to use the map such that a user inputs a location, by navigating to it, which they would like to receive information about. Therefore I need to know when a user moves the map and when the movement of the map stopped. However, there...I try to use the map such that a user inputs a location, by navigating to it, which they would like to receive information about. Therefore I need to know when a user moves the map and when the movement of the map stopped. However, there is no signal which provides this information. I tried to use the gesture "drag-end" but due to the kinetic behavior, the point in time where this signal is emitted does not correspond to the time where the map stops its movement.
Maybe it would be useful to emit a signal as soon as the kinetic-scrolling reaches velocity=0?
Or is there another solution for this which I am missing?https://gitlab.gnome.org/GNOME/console/-/issues/115"Command completed" notification frequently persists across shut-down2023-08-05T00:13:49ZIvan Molodetskikhyalterz@gmail.com"Command completed" notification frequently persists across shut-downIf I update flatpaks or rpm-ostree right before turning the PC off for the night, next morning I frequently see this:
![image](/uploads/09bff35079e0961b2532418af34cab81/image.png)
Not sure if it's kgx side or gnome-shell side. I'm on k...If I update flatpaks or rpm-ostree right before turning the PC off for the night, next morning I frequently see this:
![image](/uploads/09bff35079e0961b2532418af34cab81/image.png)
Not sure if it's kgx side or gnome-shell side. I'm on kgx c327aa35 on F35 Silverblue.GNOME 45https://gitlab.gnome.org/GNOME/nautilus/-/issues/2123Please Remove Small Triangles in GTK4 Port of Files2022-01-26T13:35:38ZBrucePlease Remove Small Triangles in GTK4 Port of FilesI am using Files GTK4 port(form Gnome Nightly flatpak latest)
Please remove these small triangles(in context menu) in GTK4 port of Files:-
![GTK4-issue](/uploads/1534c6f279a209c9c076ff80092cdffa/GTK4-issue.png)I am using Files GTK4 port(form Gnome Nightly flatpak latest)
Please remove these small triangles(in context menu) in GTK4 port of Files:-
![GTK4-issue](/uploads/1534c6f279a209c9c076ff80092cdffa/GTK4-issue.png)https://gitlab.gnome.org/GNOME/pango/-/issues/662Chinese characters are only properly monospaced when font size is a multiple ...2022-01-27T16:51:21ZDavid YangChinese characters are only properly monospaced when font size is a multiple of 3Issue initially found in Geany, reported upstream to [scintilla](https://sourceforge.net/p/scintilla/bugs/2310/), further moved up to here.
Using various Chinese monospaced fonts, Chinese characters are only correctly monospaced alongsi...Issue initially found in Geany, reported upstream to [scintilla](https://sourceforge.net/p/scintilla/bugs/2310/), further moved up to here.
Using various Chinese monospaced fonts, Chinese characters are only correctly monospaced alongside other characters like letters of the alphabet and typical programming punctuation `{}()[]` when the font size is a multiple of 3. A font where this occurs is attached. The maintainer at scintilla noted font widths provided by pango at font sizes 9, 10, 11 and 12:
```
MeasureWidths [6] '字母' 12 24
MeasureWidths [4] 'abcd' 6 12 18 24
MeasureWidths [6] '字母' 13 26
MeasureWidths [4] 'abcd' 7 14 21 28
MeasureWidths [6] '字母' 15 30
MeasureWidths [4] 'abcd' 7 14 21 28
MeasureWidths [6] '字母' 16 32
MeasureWidths [4] 'abcd' 8 16 24 32
```
Could either be solved by allowing non-integer dimensions, or by snapping the widths of double width monospaced characters to double the width of the single width characters.
[sarasa-mono-slab-sc-light.ttf](/uploads/a24e285c0987782869026f6914dbc67a/sarasa-mono-slab-sc-light.ttf)
gtk4-4.4.1-1.fc35.x86_64
Also installed, gtk3-3.24.31-2.fc35.x86_64
Fedora 35https://gitlab.gnome.org/GNOME/gtk/-/issues/4662Disable gtk-primary-button-warps-slider by default2022-01-26T00:17:51ZMahdi321Disable gtk-primary-button-warps-slider by defaultgtk-primary-button-warps-slider is annoying and flee noobs from Linux. MS Windows scroll bar behavior is fast enough and perfect (page down per click). Please disable gtk-primary-button-warps-slider by default to avoid noobs hating Linuxgtk-primary-button-warps-slider is annoying and flee noobs from Linux. MS Windows scroll bar behavior is fast enough and perfect (page down per click). Please disable gtk-primary-button-warps-slider by default to avoid noobs hating Linuxhttps://gitlab.gnome.org/GNOME/librsvg/-/issues/842Error reading SVG with large embedded image.2022-05-27T16:51:31Zreese murdockError reading SVG with large embedded image.I get an error when converting a SVG, with a large embedded image, to PDF using rsv-convert.exe V2.52.2 on windows.
![large_image_4607.svg](/uploads/b6355e66173d71820db15f8c1896ce2e/large_image_4607.svg)
> Error reading SVG large_ima...I get an error when converting a SVG, with a large embedded image, to PDF using rsv-convert.exe V2.52.2 on windows.
![large_image_4607.svg](/uploads/b6355e66173d71820db15f8c1896ce2e/large_image_4607.svg)
> Error reading SVG large_image_4607.svg: XML parse error: Error domain 1 code 77 on line 128254 column 76 of data: Premature end of data in tag g line 7
This conversion works correctly if the image is an external file. It also works if reduce the amount of data, but not the number of pixels, e.g. if I reduce the color depth of the image from 24bit to 8bit.
![large_image_4607_8bit.svg](/uploads/64ef634f30b6ab6a750a25ef794c47d4/large_image_4607_8bit.svg)https://gitlab.gnome.org/GNOME/gimp/-/issues/7778Gimp won't launch on Catalina2022-01-26T20:36:44Zdavidhi420Gimp won't launch on Catalina```
GNU Image Manipulation Program version 2.10.10
git-describe: GIMP_2_10_8-775-g596f855749
C compiler:
Configured with: --prefix=/Applications/Xcode-10.app/Contents/Developer/usr --with-gxx-include-dir=/Library/Developer/CommandLineTo...```
GNU Image Manipulation Program version 2.10.10
git-describe: GIMP_2_10_8-775-g596f855749
C compiler:
Configured with: --prefix=/Applications/Xcode-10.app/Contents/Developer/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.9.sdk/usr/include/c++/4.2.1
Apple LLVM version 10.0.0 (clang-1000.11.45.2)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: /Applications/Xcode-10.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
using GEGL version 0.4.14 (compiled against version 0.4.14)
using GLib version 2.58.1 (compiled against version 2.58.1)
using GdkPixbuf version 2.36.12 (compiled against version 2.36.12)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.4 (compiled against version 1.42.4)
using Fontconfig version 2.13.0 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Segmentation fault: 11
Stack trace:
```
0 libgimpbase-2.0.0.dylib 0x000000010ab87bb5 gimp_stack_trace_print + 1509
1 gimp-bin 0x0000000109c412e6 gimp_eek + 374
2 gimp-bin 0x0000000109c4116b gimp_fatal_error + 27
3 gimp-bin 0x0000000109c41e2d gimp_sigfatal_handler + 45
4 libsystem_platform.dylib 0x00007fff6e3ce5fd _sigtramp + 29
5 ??? 0x0000000000000003 0x0 + 3
6 libpangocairo-1.0.0.dylib 0x000000010abe421f pango_core_text_fontset_new + 191
7 libpangocairo-1.0.0.dylib 0x000000010abe3d4f pango_core_text_font_map_load_fontset + 127
8 libpangocairo-1.0.0.dylib 0x000000010abe3bdd pango_core_text_font_map_load_font + 61
9 libpangocairo-1.0.0.dylib 0x000000010abdeae9 _pango_cairo_font_private_get_hex_box_info + 921
10 libpangocairo-1.0.0.dylib 0x000000010abdf4cf _pango_cairo_font_private_get_glyph_extents + 591
11 libpangocairo-1.0.0.dylib 0x000000010abe620d _pango_core_text_shape + 1853
12 libpangocairo-1.0.0.dylib 0x000000010abe3198 _pango_core_text_shape_engine_shape + 40
13 libpango-1.0.0.dylib 0x000000010ac32d36 _pango_engine_shape_shape + 38
14 libpango-1.0.0.dylib 0x000000010ac4b318 pango_shape_full + 184
15 libpango-1.0.0.dylib 0x000000010ac40f24 shape_run + 1236
16 libpango-1.0.0.dylib 0x000000010ac40209 process_item + 313
17 libpango-1.0.0.dylib 0x000000010ac37d81 pango_layout_check_lines + 2561
18 libpango-1.0.0.dylib 0x000000010ac3b138 pango_layout_get_unknown_glyphs_count + 104
19 libgtk-quartz-2.0.0.dylib 0x000000010a627772 find_invisible_char + 210
20 libgtk-quartz-2.0.0.dylib 0x000000010a62e0e6 gtk_entry_init + 102
21 libgobject-2.0.0.dylib 0x000000010b424049 g_type_create_instance + 889
22 libgobject-2.0.0.dylib 0x000000010b4111c7 g_object_new_internal + 55
23 libgobject-2.0.0.dylib 0x000000010b4109bc g_object_new + 252
24 libgtk-quartz-2.0.0.dylib 0x000000010a6163da gtk_combo_box_constructor + 42
25 libgobject-2.0.0.dylib 0x000000010b41151a g_object_new_internal + 906
26 libgobject-2.0.0.dylib 0x000000010b410f14 g_object_new_valist + 772
27 libgobject-2.0.0.dylib 0x000000010b41095a g_object_new + 154
28 gimp-bin 0x0000000109d5041b gimp_statusbar_init + 635
29 libgobject-2.0.0.dylib 0x000000010b424049 g_type_create_instance + 889
30 libgobject-2.0.0.dylib 0x000000010b4111c7 g_object_new_internal + 55
31 libgobject-2.0.0.dylib 0x000000010b4109bc g_object_new + 252
32 gimp-bin 0x0000000109d2d31e gimp_display_shell_constructed + 2926
33 libgobject-2.0.0.dylib 0x000000010b4111ec g_object_new_internal + 92
34 libgobject-2.0.0.dylib 0x000000010b410f14 g_object_new_valist + 772
35 libgobject-2.0.0.dylib 0x000000010b41095a g_object_new + 154
36 gimp-bin 0x0000000109d2a1ce gimp_display_shell_new + 286
37 gimp-bin 0x0000000109d27a3c gimp_display_new + 460
38 gimp-bin 0x0000000109c471ac gui_display_create + 332
39 gimp-bin 0x0000000109c452b8 gui_restore_after_callback + 1112
40 libgobject-2.0.0.dylib 0x000000010b40aadc g_closure_invoke + 204
41 libgobject-2.0.0.dylib 0x000000010b420dd5 signal_emit_unlocked_R + 2901
42 libgobject-2.0.0.dylib 0x000000010b4218d0 g_signal_emit_valist + 2240
43 libgobject-2.0.0.dylib 0x000000010b4220c2 g_signal_emit + 130
44 gimp-bin 0x0000000109f11ae9 gimp_restore + 297
45 gimp-bin 0x0000000109c406f5 app_run + 517
46 gimp-bin 0x0000000109c4351d main + 989
47 libdyld.dylib 0x00007fff6e1d5cc9 start + 1
48 ??? 0x0000000000000001 0x0 + 1
```https://gitlab.gnome.org/GNOME/file-roller/-/issues/148Archive Manager / File Roller unable to open 7z archives after switch from p7...2022-02-12T12:53:53ZCommonOddityArchive Manager / File Roller unable to open 7z archives after switch from p7zip to 7zipThe issue: Archive Manager attempts to open 7z archives however it does not show file contents nor does it ask for a password for encrypted files. The window for file roller/archive manager is simply empty.
Reproducible: 100% of the tim...The issue: Archive Manager attempts to open 7z archives however it does not show file contents nor does it ask for a password for encrypted files. The window for file roller/archive manager is simply empty.
Reproducible: 100% of the time
Distro: OpenSuSE Tumbleweed (latest updates as of Jan 24th)
DE: Cinnamon
Version of archive manager: 3.40.0
Information for package file-roller:
------------------------------------
Repository : Main Repository (OSS)
Name : file-roller
Version : 3.40.0+51-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 830.2 KiB
Installed : Yes
Status : up-to-date
Source package : file-roller-3.40.0+51-1.1.src
Summary : An Archive Manager for GNOME
Description :
File Roller is an archive manager for GNOME. With it, you can create
and modify archives, view the contents of an archive, view a file
contained in the archive, and extract files from the archive.
Steps to reproduce:
1) zypper dup (distro upgrade) to an iteration that forces the swap from p7zip to 7zip
2) Attempt to open .7z archive
Caveats:
1) 7zip is installed correctly, all binaries are in place
2) It should be noted that this happened after my distro's (OpenSuSE Tumbleweed) update forced the switch from p7zip to the 7zip package
Please let me know if any additional information or output is required.https://gitlab.gnome.org/GNOME/mutter/-/issues/2117Clicks on burger menu entries by openQA test framework sometimes lost with mu...2023-10-04T23:36:57ZAdam WilliamsonClicks on burger menu entries by openQA test framework sometimes lost with mutter 42~alphaSince the Fedora-Rawhide-20220117.n.1 compose, we've noticed that two tests run by [Fedora openQA](https://openqa.fedoraproject.org) are often failing in a specific manner.
The tests are functionality tests of eog and evince. Both tests...Since the Fedora-Rawhide-20220117.n.1 compose, we've noticed that two tests run by [Fedora openQA](https://openqa.fedoraproject.org) are often failing in a specific manner.
The tests are functionality tests of eog and evince. Both tests perform several actions by opening the app's "burger menu" and clicking an entry in it. Somehow, sometimes, this isn't working properly. When the test opens the menu and clicks on an entry, the menu closes, but the action the menu entry should have triggered does not happen.
We cannot reproduce this behaviour with manual testing in local VMs. My colleague also ran test in openQA's "development mode", which can be set to pause the test on failure and leave the VNC connection that openQA's test runner usually uses to control input in the VM open for manual connection. He then accessed this VNC connection manually and found he was able to use the menus normally, i.e. he could not trigger the bug that way either.
However, it does seem to be a bug that's recurring frequently and that does not happen with mutter before 42~alpha. As it happens, there's a handy confirmation of this - due to another bug, ostree generation is currently broken in Rawhide, so the Fedora Silverblue images that are built each day contain an old ostree with an earlier version of mutter. The bug is not happening when the same two tests are run on an install of the Silverblue image from each day's Rawhide. The bug only happens when the tests are run on an install of the Workstation live image, or an upgrade of an existing Workstation install. This seems to confirm that it's a change in the installed system that triggers the bug, not something that's changed about openQA.
Here's [the report of packages that changed in that compose](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/NB62ABZPLB64H6IYRMFSL5B2U5QWP3JE/). It's a pretty long list, but mutter seems the most likely suspect. @carlosg did suggest that [this recent merge](https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1915) could have been the trigger.
So far, we're thinking the bug may happen only in openQA runs because of the details of exactly how openQA's test runner (os-autoinst) does input. So I've tried to pin that down in as much detail as I can. Here's a log extract of the relevant os-autoinst actions from a failure case, with timestamps:
[2022-01-25T11:49:10.704240Z] [debug] tests/applications/eog/pic_to_wallpaper.pm:13 called testapi::assert_and_click
[2022-01-25T11:49:10.704500Z] [debug] <<< testapi::assert_screen(mustmatch="gnome_burger_menu", timeout=30)
[2022-01-25T11:49:10.896127Z] [debug] >>> testapi::_handle_found_needle: found gnome_burger_menu_dark-20220124, similarity 1.00 @ 941/44
[2022-01-25T11:49:10.896305Z] [debug] tests/applications/eog/pic_to_wallpaper.pm:13 called testapi::assert_and_click
[2022-01-25T11:49:10.896417Z] [debug] <<< testapi::assert_and_click(mustmatch="gnome_burger_menu", timeout=30)
[2022-01-25T11:49:10.897803Z] [debug] clicking at 954/54
[2022-01-25T11:49:10.898031Z] [debug] tests/applications/eog/pic_to_wallpaper.pm:13 called testapi::assert_and_click
[2022-01-25T11:49:10.898217Z] [debug] <<< testapi::mouse_set(x=954, y=54)
[2022-01-25T11:49:10.898983Z] [debug] mouse_move 954, 54
[2022-01-25T11:49:10.899170Z] [debug] send_pointer_event 0, 954, 54, 1
[2022-01-25T11:49:10.899622Z] [debug] tests/applications/eog/pic_to_wallpaper.pm:13 called testapi::assert_and_click
[2022-01-25T11:49:10.899764Z] [debug] <<< testapi::mouse_click(button="left", cursor_down="0.15")
[2022-01-25T11:49:10.900356Z] [debug] pointer_event 1 954, 54
[2022-01-25T11:49:10.900476Z] [debug] send_pointer_event 1, 954, 54, 1
[2022-01-25T11:49:11.051831Z] [debug] pointer_event 0 954, 54
[2022-01-25T11:49:11.051993Z] [debug] send_pointer_event 0, 954, 54, 1
[2022-01-25T11:49:12.052772Z] [debug] tests/applications/eog/pic_to_wallpaper.pm:13 called testapi::assert_and_click
[2022-01-25T11:49:12.053054Z] [debug] <<< testapi::mouse_hide(border_offset=0)
[2022-01-25T11:49:12.054131Z] [debug] mouse_move 1023, 767
[2022-01-25T11:49:12.054286Z] [debug] send_pointer_event 0, 1023, 767, 1
[2022-01-25T11:49:12.054840Z] [debug] tests/applications/eog/pic_to_wallpaper.pm:15 called testapi::assert_and_click
[2022-01-25T11:49:12.055031Z] [debug] <<< testapi::assert_screen(mustmatch="eog_set_wallpaper", timeout=30)
[2022-01-25T11:49:12.282970Z] [debug] >>> testapi::_handle_found_needle: found eog_set_wallpaper, similarity 1.00 @ 862/253
[2022-01-25T11:49:12.283159Z] [debug] tests/applications/eog/pic_to_wallpaper.pm:15 called testapi::assert_and_click
[2022-01-25T11:49:12.283309Z] [debug] <<< testapi::assert_and_click(mustmatch="eog_set_wallpaper", timeout=30)
[2022-01-25T11:49:12.284306Z] [debug] clicking at 919/261
[2022-01-25T11:49:12.284418Z] [debug] tests/applications/eog/pic_to_wallpaper.pm:15 called testapi::assert_and_click
[2022-01-25T11:49:12.284502Z] [debug] <<< testapi::mouse_set(x=919, y=261)
[2022-01-25T11:49:12.285039Z] [debug] mouse_move 919, 261
[2022-01-25T11:49:12.285211Z] [debug] send_pointer_event 0, 919, 261, 1
[2022-01-25T11:49:12.285583Z] [debug] tests/applications/eog/pic_to_wallpaper.pm:15 called testapi::assert_and_click
[2022-01-25T11:49:12.285674Z] [debug] <<< testapi::mouse_click(button="left", cursor_down="0.15")
[2022-01-25T11:49:12.286189Z] [debug] pointer_event 1 919, 261
[2022-01-25T11:49:12.286306Z] [debug] send_pointer_event 1, 919, 261, 1
[2022-01-25T11:49:12.437326Z] [debug] pointer_event 0 919, 261
[2022-01-25T11:49:12.437457Z] [debug] send_pointer_event 0, 919, 261, 1
[2022-01-25T11:49:13.438157Z] [debug] tests/applications/eog/pic_to_wallpaper.pm:15 called testapi::assert_and_click
[2022-01-25T11:49:13.438433Z] [debug] <<< testapi::mouse_set(x=1023, y=767)
[2022-01-25T11:49:13.439627Z] [debug] mouse_move 1023, 767
[2022-01-25T11:49:13.439785Z] [debug] send_pointer_event 0, 1023, 767, 1
Hopefully that's kind of understandable. In that extract there are two 'identify a thing and click on it' events. The first one is for "gnome_burger_menu", which is identifying the burger menu icon itself and then clicking on it. The second is for "eog_set_wallpaper", which is identifying the "Set as Wallpaper" entry in the burger menu and clicking on it. In each case, what os-autoinst actually does in detail is:
* Match the relevant area and determine its centre point (954/54 for the burger menu, 919/261 for the "Set as Wallpaper" entry)
* Set the cursor to that precise position; it does not "move" the cursor the way a human would, it just zaps it there with a [single VNC event](https://github.com/os-autoinst/os-autoinst/blob/master/consoles/VNC.pm#L745-L760)
* Send a 'mouse button down' event
* Wait 0.15 seconds
* Send a 'mouse button up' event
* Wait 1 second
* Set the cursor to 1023,767: this is called a "mouse hide" event, the purpose is to position the cursor somewhere we hope it won't happen to interfere with a subsequent match attempt (i.e. the bottom right corner of the screen)
Possibly also relevant: os-autoinst by default runs qemu with an emulated tablet for input, not an emulated mouse (as virt-manager also does, these days). I believe this is supposed to make input smoother or more efficient somehow, I forget the details. There is a way you can configure it not to do this, I'm currently testing with that set to see if it makes any difference.
I'm also going to test if disabling the 'mouse hide' behaviour avoids the bug. I'll report back on those tests when they're done. @carlosg also suggested that output from running with `GDK_DEBUG=events` or `WAYLAND_DEBUG=1` would be useful, I'll try and get that too - not clear if they need to be set for just the app or if they need to be set for GNOME itself somehow.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/761Running VM without titlebar2022-01-26T11:19:41ZArtur O.Running VM without titlebarRight know the titlebar is quite big to fit all the options, it would be awesome if it was possible to toggle the tittle bar to just run the VM without any added vertical space.
Something like borderless fullscreen game's do nowdays.Right know the titlebar is quite big to fit all the options, it would be awesome if it was possible to toggle the tittle bar to just run the VM without any added vertical space.
Something like borderless fullscreen game's do nowdays.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4974Session crashes when extensions are enabled (mozjs-91 / latest main)2022-02-20T06:35:41ZRobert Maderrobert.mader@posteo.deSession crashes when extensions are enabled (mozjs-91 / latest main)With latest main, whenever I log in with the Appindicator extension (version 41, which is also latest git tip) enabled, the session crashes with the following trace. Enabling extensions manually a bit later works fine.
```
(gdb) bt full
...With latest main, whenever I log in with the Appindicator extension (version 41, which is also latest git tip) enabled, the session crashes with the following trace. Enabling extensions manually a bit later works fine.
```
(gdb) bt full
#0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
tid = <optimized out>
ret = 0
pd = <optimized out>
old_mask =
{__val = {558, 137239168, 39, 140319856184749, 0, 140319856299618, 32, 23873408, 140319846594448, 137239168, 140319846577536, 140319798128522, 140319824590304, 0, 22874112, 23873408}}
ret = <optimized out>
#1 0x00007f9ec24088f3 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
#2 0x00007f9ec23bb6a6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
ret = <optimized out>
#3 0x0000000000403006 in dump_gjs_stack_on_signal_handler (signo=6) at ../src/main.c:353
sa =
{__sigaction_handler = {sa_handler = 0x403020 <dump_gjs_stack_alarm_sigaction>, sa_sigaction = 0x403020 <dump_gjs_stack_alarm_sigaction>}, sa_mask = {__val = {0 <repeats 16 times>}}, sa_flags = 0, sa_restorer = 0x0}
i = 65
#4 0x00007f9ec23bb750 in <signal handler called> () at /lib64/libc.so.6
#5 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
tid = <optimized out>
ret = 0
pd = <optimized out>
old_mask =
{__val = {0, 140319857114512, 140725440198816, 140319846577536, 140319846577536, 140319840627717, 140319846577536, 140319840624249, 0, 127, 0, 140319856184749, 2048, 140319856218307, 140316581560400, 652482592497312512}}
ret = <optimized out>
#6 0x00007f9ec24088f3 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78
#7 0x00007f9ec23bb6a6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
ret = <optimized out>
#8 0x00007f9ec23a57d3 in __GI_abort () at abort.c:79
save_stage = 1
act =
{__sigaction_handler = {sa_handler = 0x82e4150, sa_sigaction = 0x82e4150}, sa_mask = {__val = {140319856184749, 257, 140319856339207, 137151040, 140725440198720, 32, 652482592497312512, 0, 18446744073709551488, 0, 234, 140725440198816, 140319846577536, 140319846577536, 140319840627717, 140319846575302}}, sa_flags = -1019567378, sa_restorer = 0x21d3b50}
sigs =
{__val = {32, 137239168, 137239168, 652482592497312512, 39, 18446744073709551488, 0, 140725440198712, 257, 1, 35470160, 140319840627717, 257, 1, 35470160, 137249104}}
#9 0x00007f9ec32b4d4c in g_assertion_message
(domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=<optimized out>, message=<optimized out>) at ../glib/gtestutils.c:3223
lstr = "1088\000\031\000\000\000\243\355\373u\025\016\t\v", '\000' <repeats 13 times>, "\376\377"
s = <optimized out>
#10 0x00007f9ec331545f in g_assertion_message_expr (domain=0x7f9ec29b60cb "Gjs", file=0x7f9ec29c2cc6 "../gjs/context.cpp", line=1088, func=0x7f9ec29c3580 "void GjsContextPrivate::unregister_unhandled_promise_rejection(uint64_t)", expr=<optimized out>) at ../glib/gtestutils.c:3249
s = 0x82cc240 "assertion failed: (((void)\"Handler attached to rejected promise that wasn't \" \"previously marked as unhandled\", erased == 1))"
#11 0x00007f9ec29754e6 in GjsContextPrivate::unregister_unhandled_promise_rejection(unsigned long) (this=0x15d0690, id=<optimized out>) at ../gjs/context.cpp:1088
erased = <optimized out>
__PRETTY_FUNCTION__ = "void GjsContextPrivate::unregister_unhandled_promise_rejection(uint64_t)"
#12 0x00007f9ebfb0fb2c in PerformPromiseThenWithReaction(JSContext*, JS::Handle<js::PromiseObject*>, JS::Handle<PromiseReactionRecord*>) [clone .lto_priv.0] () at /lib64/libmozjs-91.so.0
#13 0x00007f9ebfb07f26 in PromiseResolveBuiltinThenableJob(JSContext*, unsigned int, JS::Value*) () at /lib64/libmozjs-91.so.0
#14 0x00007f9ebfa12703 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) () at /lib64/libmozjs-91.so.0
#15 0x00007f9ebfa12ca2 in js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>, js::CallReason) () at /lib64/libmozjs-91.so.0
#16 0x00007f9ebfa780ee in JS::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::HandleValueArray const&, JS::MutableHandle<JS::Value>) () at /lib64/libmozjs-91.so.0
#17 0x00007f9ec297653e in JS::Call (rval=..., args=..., funObj=..., thisv=..., cx=<optimized out>) at /usr/include/mozjs-91/js/RootingAPI.h:1193
fun = {<js::RootedBase<JS::Value, JS::Rooted<JS::Value> >> = {<js::MutableWrappedPtrOperations<JS::Value, JS::Rooted<JS::Value> >> = {<js::WrappedPtrOperations<JS::Value, JS::Rooted<JS::Value> >> = {<No data fields>}, <No data fields>}, <No data fields>}, stack = 0x16c47e8, prev = 0x7ffd31dfbd80, ptr = {asBits_ = 18446203685612074544}}
ar = {cx_ = 0x16c4780, oldRealm_ = 0x0}
ok = <optimized out>
ix = 6
retval = true
job = {<js::RootedBase<JSObject*, JS::Rooted<JSObject*> >> = {<js::MutableWrappedPtrOperations<JSObject*, JS::Rooted<JSObject*> >> = {<js::WrappedPtrOperations<JSObject*, JS::Rooted<JSObject*> >> = {<No data fields>}, <No data fields>}, <No data fields>}, stack = 0x16c4798, prev = 0x0, ptr = 0x14851768b630}
args = {length_ = 0, elements_ = 0x0}
rval = {<js::RootedBase<JS::Value, JS::Rooted<JS::Value> >> = {<js::MutableWrappedPtrOperations<JS::Value, JS::Rooted<JS::Value> >> = {<js::WrappedPtrOperations<JS::Value, JS::Rooted<JS::Value> >> = {<No data fields>}, <No data fields>}, <No data fields>}, stack = 0x16c47e8, prev = 0x0, ptr = {asBits_ = 18446203685612071440}}
#18 GjsContextPrivate::run_jobs_fallible(_GCancellable*) (this=0x15d0690, cancellable=0x16ae250) at ../gjs/context.cpp:1015
ar = {cx_ = 0x16c4780, oldRealm_ = 0x0}
ok = <optimized out>
ix = 6
retval = true
job = {<js::RootedBase<JSObject*, JS::Rooted<JSObject*> >> = {<js::MutableWrappedPtrOperations<JSObject*, JS::Rooted<JSObject*> >> = {<js::WrappedPtrOperations<JSObject*, JS::Rooted<JSObject*> >> = {<No data fields>}, <No data fields>}, <No data fields>}, stack = 0x16c4798, prev = 0x0, ptr = 0x14851768b630}
args = {length_ = 0, elements_ = 0x0}
rval = {<js::RootedBase<JS::Value, JS::Rooted<JS::Value> >> = {<js::MutableWrappedPtrOperations<JS::Value, JS::Rooted<JS::Value> >> = {<js::WrappedPtrOperations<JS::Value, JS::Rooted<JS::Value> >> = {<No data fields>}, <No data fields>}, <No data fields>}, stack = 0x16c47e8, prev = 0x0, ptr = {asBits_ = 18446203685612071440}}
#19 0x00007f9ec2976b43 in GjsContextPrivate::runJobs(JSContext*, _GCancellable*) (this=0x15d0690, cx=0x16c4780, cancellable=cancellable@entry=0x16ae250) at ../gjs/context.cpp:964
__PRETTY_FUNCTION__ = "void GjsContextPrivate::runJobs(JSContext*, GCancellable*)"
#20 0x00007f9ec298d373 in Gjs::PromiseJobDispatcher::Source::dispatch() (this=0x16ae1a0) at ../gjs/context-private.h:178
#21 operator() (source=0x16ae1a0, __closure=0x0) at ../gjs/promise.cpp:154
#22 _FUN(GSource*, GSourceFunc, void*) () at ../gjs/promise.cpp:155
#23 0x00007f9ec32eb130 in g_main_dispatch (context=0x1319aa0) at ../glib/gmain.c:3381
dispatch = 0x7f9ec298d320 <_FUN(GSource*, GSourceFunc, void*)>
prev_source = 0x0
begin_time_nsec = 3971221060062
was_in_call = <optimized out>
user_data = 0x0
callback = 0x0
cb_funcs = 0x0
cb_data = 0x0
need_destroy = <optimized out>
source = 0x16ae1a0
current = 0x138d800
i = 0
#24 g_main_context_dispatch (context=0x1319aa0) at ../glib/gmain.c:4099
#25 0x00007f9ec3340208 in g_main_context_iterate.constprop.0 (context=0x1319aa0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4175
max_priority = -1000
timeout = 0
some_ready = 1
nfds = 0
allocated_nfds = 15
fds = <optimized out>
begin_time_nsec = 3971221055859
#26 0x00007f9ec32ea853 in g_main_loop_run (loop=0x38569e0) at ../glib/gmain.c:4373
__func__ = "g_main_loop_run"
#27 0x00007f9ec2665776 in meta_context_run_main_loop (context=context@entry=0x1316e00, error=error@entry=0x7ffd31dfbfd8) at ../src/core/meta-context.c:433
priv = 0x1316da0
__func__ = "meta_context_run_main_loop"
#28 0x0000000000402898 in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:563
context = 0x1316e00
error = 0x0
ecode = 0
```https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/50keysym simulation gets affected by capslock2022-09-17T13:52:22ZSamuel Thibaultkeysym simulation gets affected by capslockHello,
As reported on
https://brltty.app/pipermail/brltty/2022-January/019137.html
when at-spi2-core simulates a keysym with `spi_dec_synth_keysym`, the keysym translation gets affected by the state of capslock
(yes the report is ab...Hello,
As reported on
https://brltty.app/pipermail/brltty/2022-January/019137.html
when at-spi2-core simulates a keysym with `spi_dec_synth_keysym`, the keysym translation gets affected by the state of capslock
(yes the report is about brltty paste, but in the precise way he is doing it, that's using `synth_keysym` behind, if he was using control-V the normal paste would happen without any issue, but the problem still holds for other kinds of keysym simulation).
I would tend to be submitting this (untested for now) patch:
[patch](/uploads/8fe46c1f56f0860a4ede4e632a62460f/patch)
which just disables the capslock modifier while synthesizing the keysym, to make sure that it doesn't get affected by capslock.
What do you think about doing that? If doing this is fine, I'll test and submit the patch properly.
Samuelhttps://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1597Pull non-generic Settings icons from Adwaita set to the panels themselves.2022-12-14T15:51:18ZSam Hewittsnwh@gnome.orgPull non-generic Settings icons from Adwaita set to the panels themselves.Adwaita icon theme is carrying along several icons that are specific to the Settings panels which [we'd like to deprecate from the set](https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues/163) and move over to the panels themselve...Adwaita icon theme is carrying along several icons that are specific to the Settings panels which [we'd like to deprecate from the set](https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues/163) and move over to the panels themselves--given the Multitasking panel is already one that is shipping its icon along with the panel it's probably a good idea that the others follow suit.
To note this only means the icons that represent the panels themselves--that show in the sidebar for instance--and not things that are status icons.https://gitlab.gnome.org/GNOME/epiphany/-/issues/1688Favicons don't appear for some sites2022-07-14T21:27:54ZCleo Menezes Jr.Favicons don't appear for some sites![Captura_de_tela_de_2022-01-25_10-48-10](/uploads/589888aef290a05f5b635f0de7a8071d/Captura_de_tela_de_2022-01-25_10-48-10.png)
- Epiphany 41.3 Flatpak
- Fedora 35 Workstation![Captura_de_tela_de_2022-01-25_10-48-10](/uploads/589888aef290a05f5b635f0de7a8071d/Captura_de_tela_de_2022-01-25_10-48-10.png)
- Epiphany 41.3 Flatpak
- Fedora 35 Workstationhttps://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues/163Symbolic: Deprecate the app symbolic icons2022-02-14T07:55:47ZSam Hewittsnwh@gnome.orgSymbolic: Deprecate the app symbolic iconsIt's probably time to move all the "generic" app symbolic icons to their respective applications and drop them from a-i-t, or at a minimum move all Settings related icons to Settings.
Apps:
- [x] accessories-calculator-symbolic.svg
- [x...It's probably time to move all the "generic" app symbolic icons to their respective applications and drop them from a-i-t, or at a minimum move all Settings related icons to Settings.
Apps:
- [x] accessories-calculator-symbolic.svg
- [x] accessories-character-map-symbolic.svg
- [x] accessories-dictionary-symbolic.svg
- [x] accessories-text-editor-symbolic.svg
- [x] applets-screenshooter-symbolic.svg
- [x] help-browser-symbolic.svg
- [x] help-contents-symbolic.svg
- [x] help-faq-symbolic.svg
- [x] system-file-manager-symbolic.svg
- [x] system-software-install-symbolic.svg
- [x] text-editor-symbolic.svg
- [x] user-info-symbolic.svg
- [x] utilities-terminal-symbolic.svg
- [x] web-browser-symbolic.svg
Settings Panels:
- [x] gnome-power-manager-symbolic.svg
- [x] goa-panel-symbolic.svg
- [x] multimedia-volume-control-symbolic.svg
- [x] preferences-color-symbolic.svg
- [x] preferences-desktop-accessibility-symbolic.svg
- [x] preferences-desktop-appearance-symbolic.svg
- [x] preferences-desktop-apps-symbolic.svg
- [x] preferences-desktop-display-symbolic.svg
- [x] preferences-desktop-font-symbolic.svg
- [x] preferences-desktop-keyboard-shortcuts-symbolic.svg
- [x] preferences-desktop-keyboard-symbolic.svg
- [x] preferences-desktop-locale-symbolic.svg
- [x] preferences-desktop-multitasking-symbolic.svg
- already in Settings
- [x] preferences-desktop-remote-desktop-symbolic.svg
- [x] preferences-desktop-screensaver-symbolic.svg
- [x] preferences-desktop-wallpaper-symbolic.svg
- [x] preferences-system-details-symbolic.svg
- [x] preferences-system-devices-symbolic.svg
- [x] preferences-system-network-proxy-symbolic.svg
- [x] preferences-system-network-symbolic.svg
- [x] preferences-system-notifications-symbolic.svg
- [x] preferences-system-parental-controls-symbolic.svg
- [x] preferences-system-privacy-symbolic.svg
- [x] preferences-system-search-symbolic.svg
- [x] preferences-system-sharing-symbolic.svg
- [x] preferences-system-time-symbolic.svg
- [x] system-users-symbolic.svghttps://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/303gnome-text-editor: symbol lookup error: /lib64/libgtk-4.so.1: undefined symbo...2022-01-25T23:03:18Zamethylghostlinggnome-text-editor: symbol lookup error: /lib64/libgtk-4.so.1: undefined symbol: wl_proxy_marshal_flagsUnable to open due to this error error. Using geckolinux rolling pantheon native package
Libgtk-4-1 Version: 4.6.0-2.2
I dont wish to install flatpak version even if it solves the problem.
Thanks in advanceUnable to open due to this error error. Using geckolinux rolling pantheon native package
Libgtk-4-1 Version: 4.6.0-2.2
I dont wish to install flatpak version even if it solves the problem.
Thanks in advancehttps://gitlab.gnome.org/GNOME/gimp/-/issues/7777Export Image as JPEG: Conflicting mnemonics2024-02-12T17:49:31ZKevin Connor ArpeExport Image as JPEG: Conflicting mnemonicsI use Debian bleeding edge. My GIMP version is 2.10.30
Today, I was exported an image as JPEG. I noticed there is a conflicting keyboard shortcut.
From Debian/KDE, Alt+E maps to both: "Save _E_xif data" and "_E_xport". Honestly, I a...I use Debian bleeding edge. My GIMP version is 2.10.30
Today, I was exported an image as JPEG. I noticed there is a conflicting keyboard shortcut.
From Debian/KDE, Alt+E maps to both: "Save _E_xif data" and "_E_xport". Honestly, I am not a GIMP developer. It is possible that Debian/KDE is doing so remapping. Does this conflict exist in standard settings for GNOME and KDE? If yes, can we improve the situation?
Also, I noticed that when "Comment" box has focus, it is impossible to escape with keyboard-only shortcuts. I always needed to use a mouse. :( This might be hard for disabled users who do not have full control of a mouse.https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1609rust analyzer doesn't work with host projects2022-09-27T05:05:32ZAndrés Parrarust analyzer doesn't work with host projectsWhen running a host project with meson or cargo, rust analyzer doesn't provide any code completion suggestions even though builder recognizes rust analyzer.
somewhat relevant logs from a cargo project:
``` 11:13:32.4283 ...When running a host project with meson or cargo, rust analyzer doesn't provide any code completion suggestions even though builder recognizes rust analyzer.
somewhat relevant logs from a cargo project:
``` 11:13:32.4283 ide-pipeline[ 2]: DEBUG: IdeNotificationAddin loaded in 0.000008 seconds
11:13:32.4288 ide-pipeline[ 2]: DEBUG: GbpGitPipelineAddin loaded in 0.000412 seconds
11:13:32.4315 ide-pipeline[ 2]: DEBUG: RustAnalyzerPipelineAddin loaded in 0.002316 seconds
11:13:32.4316 ide-pipeline[ 2]: DEBUG: IdeAutotoolsPipelineAddin loaded in 0.000012 seconds
```
``` 11:13:32.4664 ide-pipeline[ 2]: DEBUG: waf_plugin+WafPipelineAddin loaded in 0.000048 seconds
11:13:32.4665 rust-analyzer-pipeline-addin[ 2]: DEBUG: Using rust-analyzer from home directory
11:13:32.4686 ide-subproces-supervisor[ 2]: DEBUG: Setting subprocess to 6167
11:13:32.8733 gbp-code-index-service[ 2]: WARNING: Code indexing failed: No files were provided
11:13:38.2714 gbp-editor-workspace-addin[ 2]: DEBUG: Loading editor page for "src/main.rs"
11:13:38.3110 dzl-widget-action-group[ 2]: DEBUG: Action redo disabled
11:13:38.3111 dzl-widget-action-group[ 2]: DEBUG: Action undo disabled
11:13:38.3958 ide-workspace[ 2]: DEBUG: Adding IdeEditorPage to page MRU
11:13:38.4330 gb-beautifier-helper[ 2]: DEBUG: Beautifier plugin: Can't find a GtkSourceLanguage for the buffer
11:13:38.4985 gbp-symbol-frame-addin[ 2]: DEBUG: Failed to get symbol tree: {'code': <int64 -32603>, 'message': <'file not found: /home/aparra/Projects/vulkan-performance-tests/src/main.rs'>}
11:13:38.9925 gbp-symbol-frame-addin[ 2]: DEBUG: Failed to find nearest scope: Finding nearest scope is not supported for this language
```https://gitlab.gnome.org/GNOME/nautilus/-/issues/2122Path bar active state papercuts2022-03-27T11:44:10ZTobias BernardPath bar active state papercutsThe hover/active state on path bar items currently looks a bit unpolished:
![image](/uploads/a9db37b603e7659d5801f0d2dfce76e9/image.png)
The main issues to my eyes here are:
- The bounding box of the items touching the dividers. I'd tr...The hover/active state on path bar items currently looks a bit unpolished:
![image](/uploads/a9db37b603e7659d5801f0d2dfce76e9/image.png)
The main issues to my eyes here are:
- The bounding box of the items touching the dividers. I'd try about 3px margins around them.
- The rounded edges touching the edge of the container, which isn't something we do anywhere. We could either keep the size but stop rounding the edges, or maybe make the items less tall so we can have a few pixels of padding around the box.Utkarsh GandhiUtkarsh Gandhi