GNOME issueshttps://gitlab.gnome.org/groups/GNOME/-/issues2023-05-20T18:57:26Zhttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2579Long startup time of GNOME Shell Wayland session2023-05-20T18:57:26ZPaul MenzelLong startup time of GNOME Shell Wayland sessionOn a AMD Ryzen 3 2200G with SSD and Debian Sid/unstable with GNOME Shell 3.34.4, logging into a GNOME Shell Wayland session from GDM it takes around three seconds until the Shell is visible and ready to go. According to `systemd-analyze ...On a AMD Ryzen 3 2200G with SSD and Debian Sid/unstable with GNOME Shell 3.34.4, logging into a GNOME Shell Wayland session from GDM it takes around three seconds until the Shell is visible and ready to go. According to `systemd-analyze --user blame`, the user service `gnome-shell-wayland.service` takes over 1.2 seconds to start.
```
● gnome-shell-wayland.service - GNOME Shell on Wayland
Loaded: loaded (/usr/lib/systemd/user/gnome-shell-wayland.service; static; vendor preset: enabled)
Active: active (running) since Sat 2020-04-04 09:33:35 CEST; 6s ago
Main PID: 992 (gnome-shell)
CGroup: /user.slice/user-1002.slice/user@1002.service/gnome-shell-wayland.service
├─ 992 /usr/bin/gnome-shell
├─1028 /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1002/.mutter-Xwaylandauth.3TWCI0 -listen 4 -listen 5 -displayfd 6
├─1134 ibus-daemon --panel disable -r --xim
├─1145 /usr/libexec/ibus-memconf
├─1146 /usr/libexec/ibus-extension-gtk3
├─1150 /usr/libexec/ibus-x11 --kill-daemon
└─1318 /usr/libexec/ibus-engine-simple
Apr 04 09:33:35 tokeiihto gnome-shell[992]: Error while sending AddMatch() message: Verbindung ist geschlossen
Apr 04 09:33:35 tokeiihto gnome-shell[992]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed
Apr 04 09:33:35 tokeiihto gnome-shell[992]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed
Apr 04 09:33:36 tokeiihto gnome-shell[1322]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Apr 04 09:33:36 tokeiihto gnome-shell[1322]: > Warning: Unsupported maximum keycode 569, clipping.
Apr 04 09:33:36 tokeiihto gnome-shell[1322]: > X11 cannot support keycodes above 255.
Apr 04 09:33:36 tokeiihto gnome-shell[1322]: > Internal error: Could not resolve keysym Invalid
Apr 04 09:33:36 tokeiihto gnome-shell[1322]: Errors from xkbcomp are not fatal to the X server
Apr 04 09:33:36 tokeiihto gnome-shell[992]: GNOME Shell started at Sat Apr 04 2020 09:33:35 GMT+0200 (CEST)
Apr 04 09:33:36 tokeiihto gnome-shell[992]: Registering session with GDM
$ journalctl --user | grep -i -e gnome-shell -e "GNOME Shell"
Apr 04 09:33:34.489016 tokeiihto systemd[873]: Starting GNOME Shell on Wayland...
Apr 04 09:33:34.766420 tokeiihto gnome-shell[992]: can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
Apr 04 09:33:34.857635 tokeiihto gnome-shell[1050]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Apr 04 09:33:34.857635 tokeiihto gnome-shell[1050]: > Internal error: Could not resolve keysym XF86FullScreen
Apr 04 09:33:34.860726 tokeiihto gnome-shell[1050]: Errors from xkbcomp are not fatal to the X server
Apr 04 09:33:35.225550 tokeiihto gnome-shell[992]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
Apr 04 09:33:35.226507 tokeiihto gnome-shell[992]: Will monitor session 2
Apr 04 09:33:35.410196 tokeiihto dbus-daemon[900]: [session uid=1002 pid=900] Activating service name='org.gnome.Shell.CalendarServer' requested by ':1.21' (uid=1002 pid=992 comm="/usr/bin/gnome-shell ")
Apr 04 09:33:35.440480 tokeiihto dbus-daemon[900]: [session uid=1002 pid=900] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.35' (uid=1002 pid=1123 comm="/usr/lib/gnome-shell/gnome-shell-calendar-server ")
Apr 04 09:33:35.572657 tokeiihto gnome-shell[992]: Telepathy is not available, chat integration will be disabled.
Apr 04 09:33:35.685576 tokeiihto at-spi-dbus-bus.desktop[999]: dbus-daemon[999]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1002 pid=992 comm="/usr/bin/gnome-shell ")
Apr 04 09:33:35.695548 tokeiihto dbus-daemon[900]: [session uid=1002 pid=900] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.35' (uid=1002 pid=1123 comm="/usr/lib/gnome-shell/gnome-shell-calendar-server ")
Apr 04 09:33:35.921648 tokeiihto gnome-shell[992]: ibus_bus_hello: assertion 'ibus_bus_is_connected (bus)' failed
Apr 04 09:33:35.921706 tokeiihto gnome-shell[992]: Error while sending AddMatch() message: Verbindung ist geschlossen
Apr 04 09:33:35.921912 tokeiihto gnome-shell[992]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed
Apr 04 09:33:35.921994 tokeiihto gnome-shell[992]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed
Apr 04 09:33:36.093902 tokeiihto gnome-shell[1322]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Apr 04 09:33:36.093902 tokeiihto gnome-shell[1322]: > Warning: Unsupported maximum keycode 569, clipping.
Apr 04 09:33:36.093902 tokeiihto gnome-shell[1322]: > X11 cannot support keycodes above 255.
Apr 04 09:33:36.102659 tokeiihto gnome-shell[1322]: > Internal error: Could not resolve keysym Invalid
Apr 04 09:33:36.103036 tokeiihto gnome-shell[1322]: Errors from xkbcomp are not fatal to the X server
Apr 04 09:33:36.776310 tokeiihto gnome-shell[992]: GNOME Shell started at Sat Apr 04 2020 09:33:35 GMT+0200 (CEST)
Apr 04 09:33:36.776627 tokeiihto gnome-shell[992]: Registering session with GDM
[…]
```
How can the login time be decreased to nearly instantanious?https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/341Animate moving windows between monitors2023-05-20T18:56:20ZSergey BugaevAnimate moving windows between monitorsGNOME Shell has a "move to another monitor" action for windows (available as Super-Left/Right shortcut and "Move to Monitor Right/Left" window menu item). Unlike other window size/position transitions that are animated, this one happens ...GNOME Shell has a "move to another monitor" action for windows (available as Super-Left/Right shortcut and "Move to Monitor Right/Left" window menu item). Unlike other window size/position transitions that are animated, this one happens without animation.https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/184Gnome Maps doesn't start with "GLXBadContext" error2023-05-20T18:17:38ZGhost UserGnome Maps doesn't start with "GLXBadContext" errorHere's the output when I try to run the program. It's worked before, and I'm not sure what's changed. I'm using Manjaro Gnome with a GTX 1080 GPU.
If there's more info that would be helpful I'm happy to provide it.
```
$ flatpak run or...Here's the output when I try to run the program. It's worked before, and I'm not sure what's changed. I'm using Manjaro Gnome with a GTX 1080 GPU.
If there's more info that would be helpful I'm happy to provide it.
```
$ flatpak run org.gnome.Maps
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
(org.gnome.Maps:3): Gdk-ERROR **: 09:24:46.334: The program 'org.gnome.Maps' received an X Window System error.
This probably reflects a bug in the program.
The error was 'GLXBadContext'.
(Details: serial 201 error_code 158 request_code 151 (GLX) minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
```https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/385GeoJSON edition2023-05-20T18:01:56ZjlemondeGeoJSON editionDear all!
It would be cool if it were possible to create geoJSON layers (not only open them), add arbitrary points and shapes to it, set labels and search among them.
I can't find a piece of software that does that, and such a feature ...Dear all!
It would be cool if it were possible to create geoJSON layers (not only open them), add arbitrary points and shapes to it, set labels and search among them.
I can't find a piece of software that does that, and such a feature would fit nicely in gnome-maps!
Is there hope such a feature would be implemented anytime soon? That's basic requirement for a maps app according to me, for now I have no other choice than use _Google Maps_, which offers similar features...https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/185Add altitude track visualizer2023-05-20T17:56:22ZGhost UserAdd altitude track visualizerCan such panel be added as a bottom collapsible one when a track or gpx route is selected?
![Elevation-Information-1000x274](/uploads/ac836ffc8b3a6fafdd27e18fd6a924ad/Elevation-Information-1000x274.jpg)
This distribution is typical, gr...Can such panel be added as a bottom collapsible one when a track or gpx route is selected?
![Elevation-Information-1000x274](/uploads/ac836ffc8b3a6fafdd27e18fd6a924ad/Elevation-Information-1000x274.jpg)
This distribution is typical, green for down, blue for plain and red for climbing parts. It can add waypoints (and distance) and kilometer on hover for mouse (or time recorded).
The best existing example I can think of (to be reworked) is the gnome-power-statistics, but needs to be ported to javascript:
![power_statistics_laptop_battery_history](/uploads/b4e674592f0159d2a69256bc3b1b93e9/power_statistics_laptop_battery_history.jpg)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/393Keep overview open when clicking the middle mouse button on dash icons2023-05-20T17:53:56ZDanManKeep overview open when clicking the middle mouse button on dash icons…so you only need one hand to start multiple programs/instances from the overview. ~~Middle mouse click currently does nothing there, so why not.~~ Gives lazy people like me another option to arrange programs on the overview/workspaces.
...…so you only need one hand to start multiple programs/instances from the overview. ~~Middle mouse click currently does nothing there, so why not.~~ Gives lazy people like me another option to arrange programs on the overview/workspaces.
I've actually already built me an extension that does that, but it's a bit glitchy. From what I can tell it only affects `AppDisplay.AppIcon.activate()`.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6503Gnome Shell + Wayland + Telegram + Screen Locking = CRASH2023-05-20T17:36:22ZМарк КоренбергGnome Shell + Wayland + Telegram + Screen Locking = CRASHSee https://github.com/telegramdesktop/tdesktop/issues/25892
In short, Gnome-Shell segfaults every time I lock the screen if Telegram is running. Before, TG was crashing every time. After investigation they fix something in locking. And...See https://github.com/telegramdesktop/tdesktop/issues/25892
In short, Gnome-Shell segfaults every time I lock the screen if Telegram is running. Before, TG was crashing every time. After investigation they fix something in locking. And now GnomeShell\Wayland crashes, so I basically can not debug Telegram.
I have unusual configuration of displays (the embedded screen of my laptop is high-res and switched off. main disaply is external one (HDMI)). Crash does not happen if I lock the screen with unplugged external monitor of my laptop.
Please tell me how to debug.
```
gnome-shell[660893]: segfault at 0 ip 00007fd2eda73709 sp 00007fff0f6cc3f0 error 4 in libwayland-server.so.0.21.0[7fd2eda71000+8000] likely on CPU 0 (core 0, socket 0)
```https://gitlab.gnome.org/GNOME/calls/-/issues/436Changing account options regularly crashes app, can't register with TLS on Vo...2023-05-20T17:32:21ZJohn SmithChanging account options regularly crashes app, can't register with TLS on VoIP.msHere's a list of things that don't seem to work :
Changing account settings regularly crashes the application. When the application resumes, the previous account settings are missing altogether. If I can add an account with a differen...Here's a list of things that don't seem to work :
Changing account settings regularly crashes the application. When the application resumes, the previous account settings are missing altogether. If I can add an account with a different name without having it crash, the original account shows back up again.
TLS registration doesn't work with VoIP.ms. When I'm on the Accounts page, the slider won't lock to online.
UDP registration will work with VoIP.ms (I can see the softphone registration on their website) ~~but I don't get any audio. The call goes through because it records a blank voicemail, but I don't hear the announcement and it doesn't record my voice. I tried this in a Parallels Desktop VM on a Mac and audio works elsewhere in the VM (tested in the GNOME Settings-Sound in the VM).~~. Incoming calls won't ring in GNOME Calls, but will ring on other softphones. Might be a firewall issue - investigating.
FYI: I have tried enabling and disabling their option for "Encrypted SIP Traffic" and it doesn't seem to make a difference for either protocol, nor does it affect registration (I can see registration only for UDP, as described above, and it shows not encrypted, even when encrypted SIP traffic option is enabled).
Trying this on Fedora Workstation 35 with GNOME Calls from Flathub (installed new same day as this post).https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/255gnome-shell implicit -`--wayland` and default `--mode`2023-05-20T17:12:35ZДилян Палаузовgit-dpa@aegee.orggnome-shell implicit -`--wayland` and default `--mode`gnome-shell-3.28.1 --list-modes prints `user` and `gdm`. How can one determine which mode is the default?
Typing `gnome-shell` prints `Window manager warning: unsupported session type`, while `gnome-shell --wayland` works. To be preci...gnome-shell-3.28.1 --list-modes prints `user` and `gdm`. How can one determine which mode is the default?
Typing `gnome-shell` prints `Window manager warning: unsupported session type`, while `gnome-shell --wayland` works. To be precise, just typing `gnome-shell` does nothing, and typing a second time `gnome-shell` emits the above warning.
Why doesn't `gnome-shell` under this circumstances imply `--wayland` and how to change the default, so that is implies `--wayland`?https://gitlab.gnome.org/GNOME/mutter/-/issues/2823gnome-shell crash if close ffplay on mode fullscreen2023-05-20T16:58:21ZMuhammad Akbar Yanuar Mantarignome-shell crash if close ffplay on mode fullscreen<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Provide at least the following information:
* openSUSE Tumbl...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Provide at least the following information:
* openSUSE Tumbleweed
* Affected GNOME Shell version [44.1+40~git.c57f4a1c](https://build.opensuse.org/package/show/home:mantarimay:GNOME:wayland/gnome-shell)
* This issue appear in Wayland
<!--* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
### Bug summary
gnome-shell crash if close ffplay on mode fullscreen
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
1. open video with ffplay
2. double click/press 'f' to make ffplay fullscreen
3. quit with press 'q'
4. crash
<!-- -->
### What happened
<!--
What did GNOME Shell do that was unexpected?
-->
closing ffplay without crash
### What did you expect to happen
<!--
What did you expect GNOME Shell to do?
-->
crash if close ffplay on mode fullscreen
### Relevant logs, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
<details><summary>coredumpctl gdb -r gnome-shell</summary>
```
may@mantari:~> coredumpctl gdb -r gnome-shell
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
PID: 17541 (gnome-shell)
UID: 1000 (may)
GID: 1000 (may)
Signal: 11 (SEGV)
Timestamp: Wed 2023-05-10 14:44:13 WIB (1min 11s ago)
Command Line: /usr/bin/gnome-shell
Executable: /usr/bin/gnome-shell
Control Group: /user.slice/user-1000.slice/session-3.scope
Unit: session-3.scope
Slice: user-1000.slice
Session: 3
Owner UID: 1000 (may)
Boot ID: 11e1a9b7a8ee44c3ab30e3c305c1a104
Machine ID: 0cdc0d70ada040dc8e2165d66c0a4b4b
Hostname: mantari
Storage: /var/lib/systemd/coredump/core.gnome-shell.1000.11e1a9b7a8ee44c3ab30e3c305c1a104.17541.1683704653000000.zst (present)
Size on Disk: 15.4M
Message: Process 17541 (gnome-shell) of user 1000 dumped core.
Stack trace of thread 17541:
#0 0x00007f51c6936892 should_constraint_be_enabled (libmutter-12.so.0 + 0x136892)
#1 0x00007f51c6937154 meta_wayland_pointer_constraint_maybe_remove_for_seat (libmutter-12.so.0 + 0x137154)
#2 0x00007f51c7398448 g_closure_invoke (libgobject-2.0.so.0 + 0x17448)
#3 0x00007f51c73ab4fe n/a (libgobject-2.0.so.0 + 0x2a4fe)
#4 0x00007f51c73b282e g_signal_emit_valist (libgobject-2.0.so.0 + 0x3182e)
#5 0x00007f51c73b29df g_signal_emit (libgobject-2.0.so.0 + 0x319df)
#6 0x00007f51c739c6c4 n/a (libgobject-2.0.so.0 + 0x1b6c4)
#7 0x00007f51c739f6ec g_object_notify_by_pspec (libgobject-2.0.so.0 + 0x1e6ec)
#8 0x00007f51c68b0478 meta_window_set_focused_internal (libmutter-12.so.0 + 0xb0478)
#9 0x00007f51c68b0584 meta_display_set_input_focus (libmutter-12.so.0 + 0xb0584)
#10 0x00007f51c68d6241 meta_window_focus (libmutter-12.so.0 + 0xd6241)
#11 0x00007f51c68d778c meta_workspace_focus_default_window (libmutter-12.so.0 + 0xd778c)
#12 0x00007f51c68d0809 meta_window_unmanage (libmutter-12.so.0 + 0xd0809)
#13 0x00007f51c6937893 meta_wayland_shell_surface_destroy_window (libmutter-12.so.0 + 0x137893)
#14 0x00007f51c693df2e meta_wayland_xdg_toplevel_reset (libmutter-12.so.0 + 0x13df2e)
#15 0x00007f51c6941a34 meta_wayland_xdg_surface_reset (libmutter-12.so.0 + 0x141a34)
#16 0x00007f51c693ed8b meta_wayland_surface_role_apply_state (libmutter-12.so.0 + 0x13ed8b)
#17 0x00007f51c693f920 meta_wayland_transaction_commit (libmutter-12.so.0 + 0x13f920)
#18 0x00007f51c6937ff6 meta_wayland_surface_commit (libmutter-12.so.0 + 0x137ff6)
#19 0x00007f51c6a188d2 n/a (libffi.so.8 + 0x78d2)
#20 0x00007f51c6a1524f n/a (libffi.so.8 + 0x424f)
#21 0x00007f51c6a17e96 ffi_call (libffi.so.8 + 0x6e96)
#22 0x00007f51c4cf80a8 wl_closure_invoke.constprop.0 (libwayland-server.so.0 + 0x90a8)
#23 0x00007f51c4cfc408 wl_client_connection_data (libwayland-server.so.0 + 0xd408)
#24 0x00007f51c4cfae62 wl_event_loop_dispatch (libwayland-server.so.0 + 0xbe62)
#25 0x00007f51c69265e7 wayland_event_source_dispatch (libmutter-12.so.0 + 0x1265e7)
#26 0x00007f51c6d2b8d8 g_main_context_dispatch (libglib-2.0.so.0 + 0x5d8d8)
#27 0x00007f51c6d2bce8 n/a (libglib-2.0.so.0 + 0x5dce8)
#28 0x00007f51c6d2bf9f g_main_loop_run (libglib-2.0.so.0 + 0x5df9f)
#29 0x00007f51c68bf975 meta_context_run_main_loop (libmutter-12.so.0 + 0xbf975)
#30 0x0000559b94a6e98f main (gnome-shell + 0x398f)
#31 0x00007f51c662cbb0 __libc_start_call_main (libc.so.6 + 0x27bb0)
#32 0x00007f51c662cc79 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x27c79)
#33 0x0000559b94a6ec65 _start (gnome-shell + 0x3c65)
Stack trace of thread 17544:
#0 0x00007f51c670bcef __poll (libc.so.6 + 0x106cef)
#1 0x00007f51c6d2bc5e n/a (libglib-2.0.so.0 + 0x5dc5e)
#2 0x00007f51c6d2bd7c g_main_context_iteration (libglib-2.0.so.0 + 0x5dd7c)
#3 0x00007f51c6d2bdc1 n/a (libglib-2.0.so.0 + 0x5ddc1)
#4 0x00007f51c6d57f0e n/a (libglib-2.0.so.0 + 0x89f0e)
#5 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#6 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17549:
#0 0x00007f51c670bcef __poll (libc.so.6 + 0x106cef)
#1 0x00007f51c6d2bc5e n/a (libglib-2.0.so.0 + 0x5dc5e)
#2 0x00007f51c6d2bd7c g_main_context_iteration (libglib-2.0.so.0 + 0x5dd7c)
#3 0x00007f51c01d383d n/a (libdconfsettings.so + 0x683d)
#4 0x00007f51c6d57f0e n/a (libglib-2.0.so.0 + 0x89f0e)
#5 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#6 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17553:
#0 0x00007f51c668f05e __futex_abstimed_wait_common (libc.so.6 + 0x8a05e)
#1 0x00007f51c6691da0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8cda0)
#2 0x00007f51b8cc7bfb n/a (crocus_dri.so + 0xc7bfb)
#3 0x00007f51b8d0eb37 n/a (crocus_dri.so + 0x10eb37)
#4 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#5 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17574:
#0 0x00007f51c668f05e __futex_abstimed_wait_common (libc.so.6 + 0x8a05e)
#1 0x00007f51c6691da0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8cda0)
#2 0x00007f51c5836727 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-102.so.0 + 0xa36727)
#3 0x00007f51c58368b5 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so.0 + 0xa368b5)
#4 0x00007f51c504c445 n/a (libmozjs-102.so.0 + 0x24c445)
#5 0x00007f51c504c4f1 n/a (libmozjs-102.so.0 + 0x24c4f1)
#6 0x00007f51c504b807 n/a (libmozjs-102.so.0 + 0x24b807)
#7 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#8 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17554:
#0 0x00007f51c670bcef __poll (libc.so.6 + 0x106cef)
#1 0x00007f51c6d2bc5e n/a (libglib-2.0.so.0 + 0x5dc5e)
#2 0x00007f51c6d2bf9f g_main_loop_run (libglib-2.0.so.0 + 0x5df9f)
#3 0x00007f51c6965b07 input_thread (libmutter-12.so.0 + 0x165b07)
#4 0x00007f51c6d57f0e n/a (libglib-2.0.so.0 + 0x89f0e)
#5 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#6 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17543:
#0 0x00007f51c6711bbd syscall (libc.so.6 + 0x10cbbd)
#1 0x00007f51c6d8535f g_cond_wait (libglib-2.0.so.0 + 0xb735f)
#2 0x00007f51c6cf5f4b n/a (libglib-2.0.so.0 + 0x27f4b)
#3 0x00007f51c6d58552 n/a (libglib-2.0.so.0 + 0x8a552)
#4 0x00007f51c6d57f0e n/a (libglib-2.0.so.0 + 0x89f0e)
#5 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#6 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17546:
#0 0x00007f51c670bcef __poll (libc.so.6 + 0x106cef)
#1 0x00007f51c6d2bc5e n/a (libglib-2.0.so.0 + 0x5dc5e)
#2 0x00007f51c6d2bf9f g_main_loop_run (libglib-2.0.so.0 + 0x5df9f)
#3 0x00007f51c6f37896 n/a (libgio-2.0.so.0 + 0x122896)
#4 0x00007f51c6d57f0e n/a (libglib-2.0.so.0 + 0x89f0e)
#5 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#6 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17547:
#0 0x00007f51c668f05e __futex_abstimed_wait_common (libc.so.6 + 0x8a05e)
#1 0x00007f51c6691da0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8cda0)
#2 0x00007f51b8cc7bfb n/a (crocus_dri.so + 0xc7bfb)
#3 0x00007f51b8d0eb37 n/a (crocus_dri.so + 0x10eb37)
#4 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#5 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17575:
#0 0x00007f51c668f05e __futex_abstimed_wait_common (libc.so.6 + 0x8a05e)
#1 0x00007f51c6691da0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8cda0)
#2 0x00007f51c5836727 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-102.so.0 + 0xa36727)
#3 0x00007f51c58368b5 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so.0 + 0xa368b5)
#4 0x00007f51c504c445 n/a (libmozjs-102.so.0 + 0x24c445)
#5 0x00007f51c504c4f1 n/a (libmozjs-102.so.0 + 0x24c4f1)
#6 0x00007f51c504b807 n/a (libmozjs-102.so.0 + 0x24b807)
#7 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#8 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17551:
#0 0x00007f51c668f05e __futex_abstimed_wait_common (libc.so.6 + 0x8a05e)
#1 0x00007f51c6691da0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8cda0)
#2 0x00007f51b8cc7bfb n/a (crocus_dri.so + 0xc7bfb)
#3 0x00007f51b8d0eb37 n/a (crocus_dri.so + 0x10eb37)
#4 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#5 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
ELF object binary architecture: AMD x86-64
GNU gdb (GDB; openSUSE Tumbleweed) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/gnome-shell...
Reading symbols from /usr/lib/debug/usr/bin/gnome-shell.debug...
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f51c6936892 in should_constraint_be_enabled (constraint=constraint@entry=0x559b96994670) at ../src/wayland/meta-wayland-pointer-constraints.c:483
483 ../src/wayland/meta-wayland-pointer-constraints.c: No such file or directory.
[Current thread is 1 (Thread 0x7f51c36bb600 (LWP 17541))]
```
</details>
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6679gnome-shell crash if close ffplay on mode fullscreen2023-05-20T16:58:08ZMuhammad Akbar Yanuar Mantarignome-shell crash if close ffplay on mode fullscreen<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Provide at least the following information:
* openSUSE Tumbl...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Provide at least the following information:
* openSUSE Tumbleweed
* Affected GNOME Shell version [44.1+40~git.c57f4a1c](https://build.opensuse.org/package/show/home:mantarimay:GNOME:wayland/gnome-shell)
* This issue appear in Wayland
<!--* Does this issue happen without extensions (please follow instructions below)
To properly disable extensions you can use gnome-extensions-app and then restart
your session. Disabling extensions without a restart is not sufficient to rule
out extensions as cause of a bug. If an issue can only be reproduced with a
certain extension, please file a bug report against that extension first.
-->
### Bug summary
gnome-shell crash if close ffplay on mode fullscreen
<!--
Provide a short summary of the bug you encountered.
-->
### Steps to reproduce
1. open video with ffplay
2. double click/press 'f' to make ffplay fullscreen
3. quit with press 'q'
4. crash
<!-- -->
### What happened
<!--
What did GNOME Shell do that was unexpected?
-->
closing ffplay without crash
### What did you expect to happen
<!--
What did you expect GNOME Shell to do?
-->
crash if close ffplay on mode fullscreen
### Relevant logs, screenshots, screencasts etc.
<!--
If you have further information, such as technical documentation, logs,
screenshots or screencasts related, please provide them here.
If the bug is a crash, please obtain a stack trace with installed debug
symbols (at least for GNOME Shell and Mutter) and attach it to
this issue following the instructions on
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces.
-->
<details><summary>coredumpctl gdb -r gnome-shell</summary>
```
may@mantari:~> coredumpctl gdb -r gnome-shell
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
PID: 17541 (gnome-shell)
UID: 1000 (may)
GID: 1000 (may)
Signal: 11 (SEGV)
Timestamp: Wed 2023-05-10 14:44:13 WIB (1min 11s ago)
Command Line: /usr/bin/gnome-shell
Executable: /usr/bin/gnome-shell
Control Group: /user.slice/user-1000.slice/session-3.scope
Unit: session-3.scope
Slice: user-1000.slice
Session: 3
Owner UID: 1000 (may)
Boot ID: 11e1a9b7a8ee44c3ab30e3c305c1a104
Machine ID: 0cdc0d70ada040dc8e2165d66c0a4b4b
Hostname: mantari
Storage: /var/lib/systemd/coredump/core.gnome-shell.1000.11e1a9b7a8ee44c3ab30e3c305c1a104.17541.1683704653000000.zst (present)
Size on Disk: 15.4M
Message: Process 17541 (gnome-shell) of user 1000 dumped core.
Stack trace of thread 17541:
#0 0x00007f51c6936892 should_constraint_be_enabled (libmutter-12.so.0 + 0x136892)
#1 0x00007f51c6937154 meta_wayland_pointer_constraint_maybe_remove_for_seat (libmutter-12.so.0 + 0x137154)
#2 0x00007f51c7398448 g_closure_invoke (libgobject-2.0.so.0 + 0x17448)
#3 0x00007f51c73ab4fe n/a (libgobject-2.0.so.0 + 0x2a4fe)
#4 0x00007f51c73b282e g_signal_emit_valist (libgobject-2.0.so.0 + 0x3182e)
#5 0x00007f51c73b29df g_signal_emit (libgobject-2.0.so.0 + 0x319df)
#6 0x00007f51c739c6c4 n/a (libgobject-2.0.so.0 + 0x1b6c4)
#7 0x00007f51c739f6ec g_object_notify_by_pspec (libgobject-2.0.so.0 + 0x1e6ec)
#8 0x00007f51c68b0478 meta_window_set_focused_internal (libmutter-12.so.0 + 0xb0478)
#9 0x00007f51c68b0584 meta_display_set_input_focus (libmutter-12.so.0 + 0xb0584)
#10 0x00007f51c68d6241 meta_window_focus (libmutter-12.so.0 + 0xd6241)
#11 0x00007f51c68d778c meta_workspace_focus_default_window (libmutter-12.so.0 + 0xd778c)
#12 0x00007f51c68d0809 meta_window_unmanage (libmutter-12.so.0 + 0xd0809)
#13 0x00007f51c6937893 meta_wayland_shell_surface_destroy_window (libmutter-12.so.0 + 0x137893)
#14 0x00007f51c693df2e meta_wayland_xdg_toplevel_reset (libmutter-12.so.0 + 0x13df2e)
#15 0x00007f51c6941a34 meta_wayland_xdg_surface_reset (libmutter-12.so.0 + 0x141a34)
#16 0x00007f51c693ed8b meta_wayland_surface_role_apply_state (libmutter-12.so.0 + 0x13ed8b)
#17 0x00007f51c693f920 meta_wayland_transaction_commit (libmutter-12.so.0 + 0x13f920)
#18 0x00007f51c6937ff6 meta_wayland_surface_commit (libmutter-12.so.0 + 0x137ff6)
#19 0x00007f51c6a188d2 n/a (libffi.so.8 + 0x78d2)
#20 0x00007f51c6a1524f n/a (libffi.so.8 + 0x424f)
#21 0x00007f51c6a17e96 ffi_call (libffi.so.8 + 0x6e96)
#22 0x00007f51c4cf80a8 wl_closure_invoke.constprop.0 (libwayland-server.so.0 + 0x90a8)
#23 0x00007f51c4cfc408 wl_client_connection_data (libwayland-server.so.0 + 0xd408)
#24 0x00007f51c4cfae62 wl_event_loop_dispatch (libwayland-server.so.0 + 0xbe62)
#25 0x00007f51c69265e7 wayland_event_source_dispatch (libmutter-12.so.0 + 0x1265e7)
#26 0x00007f51c6d2b8d8 g_main_context_dispatch (libglib-2.0.so.0 + 0x5d8d8)
#27 0x00007f51c6d2bce8 n/a (libglib-2.0.so.0 + 0x5dce8)
#28 0x00007f51c6d2bf9f g_main_loop_run (libglib-2.0.so.0 + 0x5df9f)
#29 0x00007f51c68bf975 meta_context_run_main_loop (libmutter-12.so.0 + 0xbf975)
#30 0x0000559b94a6e98f main (gnome-shell + 0x398f)
#31 0x00007f51c662cbb0 __libc_start_call_main (libc.so.6 + 0x27bb0)
#32 0x00007f51c662cc79 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x27c79)
#33 0x0000559b94a6ec65 _start (gnome-shell + 0x3c65)
Stack trace of thread 17544:
#0 0x00007f51c670bcef __poll (libc.so.6 + 0x106cef)
#1 0x00007f51c6d2bc5e n/a (libglib-2.0.so.0 + 0x5dc5e)
#2 0x00007f51c6d2bd7c g_main_context_iteration (libglib-2.0.so.0 + 0x5dd7c)
#3 0x00007f51c6d2bdc1 n/a (libglib-2.0.so.0 + 0x5ddc1)
#4 0x00007f51c6d57f0e n/a (libglib-2.0.so.0 + 0x89f0e)
#5 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#6 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17549:
#0 0x00007f51c670bcef __poll (libc.so.6 + 0x106cef)
#1 0x00007f51c6d2bc5e n/a (libglib-2.0.so.0 + 0x5dc5e)
#2 0x00007f51c6d2bd7c g_main_context_iteration (libglib-2.0.so.0 + 0x5dd7c)
#3 0x00007f51c01d383d n/a (libdconfsettings.so + 0x683d)
#4 0x00007f51c6d57f0e n/a (libglib-2.0.so.0 + 0x89f0e)
#5 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#6 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17553:
#0 0x00007f51c668f05e __futex_abstimed_wait_common (libc.so.6 + 0x8a05e)
#1 0x00007f51c6691da0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8cda0)
#2 0x00007f51b8cc7bfb n/a (crocus_dri.so + 0xc7bfb)
#3 0x00007f51b8d0eb37 n/a (crocus_dri.so + 0x10eb37)
#4 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#5 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17574:
#0 0x00007f51c668f05e __futex_abstimed_wait_common (libc.so.6 + 0x8a05e)
#1 0x00007f51c6691da0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8cda0)
#2 0x00007f51c5836727 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-102.so.0 + 0xa36727)
#3 0x00007f51c58368b5 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so.0 + 0xa368b5)
#4 0x00007f51c504c445 n/a (libmozjs-102.so.0 + 0x24c445)
#5 0x00007f51c504c4f1 n/a (libmozjs-102.so.0 + 0x24c4f1)
#6 0x00007f51c504b807 n/a (libmozjs-102.so.0 + 0x24b807)
#7 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#8 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17554:
#0 0x00007f51c670bcef __poll (libc.so.6 + 0x106cef)
#1 0x00007f51c6d2bc5e n/a (libglib-2.0.so.0 + 0x5dc5e)
#2 0x00007f51c6d2bf9f g_main_loop_run (libglib-2.0.so.0 + 0x5df9f)
#3 0x00007f51c6965b07 input_thread (libmutter-12.so.0 + 0x165b07)
#4 0x00007f51c6d57f0e n/a (libglib-2.0.so.0 + 0x89f0e)
#5 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#6 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17543:
#0 0x00007f51c6711bbd syscall (libc.so.6 + 0x10cbbd)
#1 0x00007f51c6d8535f g_cond_wait (libglib-2.0.so.0 + 0xb735f)
#2 0x00007f51c6cf5f4b n/a (libglib-2.0.so.0 + 0x27f4b)
#3 0x00007f51c6d58552 n/a (libglib-2.0.so.0 + 0x8a552)
#4 0x00007f51c6d57f0e n/a (libglib-2.0.so.0 + 0x89f0e)
#5 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#6 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17546:
#0 0x00007f51c670bcef __poll (libc.so.6 + 0x106cef)
#1 0x00007f51c6d2bc5e n/a (libglib-2.0.so.0 + 0x5dc5e)
#2 0x00007f51c6d2bf9f g_main_loop_run (libglib-2.0.so.0 + 0x5df9f)
#3 0x00007f51c6f37896 n/a (libgio-2.0.so.0 + 0x122896)
#4 0x00007f51c6d57f0e n/a (libglib-2.0.so.0 + 0x89f0e)
#5 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#6 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17547:
#0 0x00007f51c668f05e __futex_abstimed_wait_common (libc.so.6 + 0x8a05e)
#1 0x00007f51c6691da0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8cda0)
#2 0x00007f51b8cc7bfb n/a (crocus_dri.so + 0xc7bfb)
#3 0x00007f51b8d0eb37 n/a (crocus_dri.so + 0x10eb37)
#4 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#5 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17575:
#0 0x00007f51c668f05e __futex_abstimed_wait_common (libc.so.6 + 0x8a05e)
#1 0x00007f51c6691da0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8cda0)
#2 0x00007f51c5836727 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-102.so.0 + 0xa36727)
#3 0x00007f51c58368b5 _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS_27TimeDurationValueCalculatorEEE (libmozjs-102.so.0 + 0xa368b5)
#4 0x00007f51c504c445 n/a (libmozjs-102.so.0 + 0x24c445)
#5 0x00007f51c504c4f1 n/a (libmozjs-102.so.0 + 0x24c4f1)
#6 0x00007f51c504b807 n/a (libmozjs-102.so.0 + 0x24b807)
#7 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#8 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
Stack trace of thread 17551:
#0 0x00007f51c668f05e __futex_abstimed_wait_common (libc.so.6 + 0x8a05e)
#1 0x00007f51c6691da0 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8cda0)
#2 0x00007f51b8cc7bfb n/a (crocus_dri.so + 0xc7bfb)
#3 0x00007f51b8d0eb37 n/a (crocus_dri.so + 0x10eb37)
#4 0x00007f51c6692ab4 start_thread (libc.so.6 + 0x8dab4)
#5 0x00007f51c6719b60 __clone3 (libc.so.6 + 0x114b60)
ELF object binary architecture: AMD x86-64
GNU gdb (GDB; openSUSE Tumbleweed) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/gnome-shell...
Reading symbols from /usr/lib/debug/usr/bin/gnome-shell.debug...
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f51c6936892 in should_constraint_be_enabled (constraint=constraint@entry=0x559b96994670) at ../src/wayland/meta-wayland-pointer-constraints.c:483
483 ../src/wayland/meta-wayland-pointer-constraints.c: No such file or directory.
[Current thread is 1 (Thread 0x7f51c36bb600 (LWP 17541))]
```
</details>
<!-- Do not remove the following line. -->https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/234Gnome Scroll Bug2023-05-20T16:30:12ZNaufan Rusyda FaikarGnome Scroll BugThis bug can be generated when we use software such as Atom Text Editor. When we alt + tab to another software likes Mozilla Firefox and do scrolling mouse. Then we go back to Atom and we will be thrown into an improper line when we try ...This bug can be generated when we use software such as Atom Text Editor. When we alt + tab to another software likes Mozilla Firefox and do scrolling mouse. Then we go back to Atom and we will be thrown into an improper line when we try to scrolling.
NB: I've no issue when using another shell.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/243application update causes dash icons to disappear as they would when closed2023-05-20T16:29:30ZThomas Pointhuberapplication update causes dash icons to disappear as they would when closedOriginal Bugreport: https://github.com/micheleg/dash-to-dock/issues/715
When someone for example on Arch Linux updates firefox while the application is running. Gnome no longer shows the application as open in the dash, and a click on t...Original Bugreport: https://github.com/micheleg/dash-to-dock/issues/715
When someone for example on Arch Linux updates firefox while the application is running. Gnome no longer shows the application as open in the dash, and a click on the application icon creates a new window instead of opening the already open one.
Doing a shell reload fixes this issue.
Probably related: on my system, wireshark-gtk does not even show an icon in the dash unless I reload the shell.https://gitlab.gnome.org/GNOME/gtk/-/issues/5836critical from gridview2023-05-20T16:28:27ZMatthias Clasencritical from gridviewOpen the file browser demo in gtk4-demo, change to a different folder, observe:
(gtk4-demo:1525505): Gtk-CRITICAL **: 09:21:46.324: gtk_grid_view_get_unknown_row_size: assertion 'heights->len > 0' failedOpen the file browser demo in gtk4-demo, change to a different folder, observe:
(gtk4-demo:1525505): Gtk-CRITICAL **: 09:21:46.324: gtk_grid_view_get_unknown_row_size: assertion 'heights->len > 0' failedhttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1456App icons does not show in application grid2023-05-20T16:24:50ZTheAifam5App icons does not show in application gridHey!
While searching for an application which is installed on the system, the icons does not show up in any case but after pressing "ENTER" shows an animation with an Firefox icon and the application starts up.
![CROPPPED](/uploads/d7d...Hey!
While searching for an application which is installed on the system, the icons does not show up in any case but after pressing "ENTER" shows an animation with an Firefox icon and the application starts up.
![CROPPPED](/uploads/d7dfa1285726455f0b2c307759aabd2d/CROPPPED.png)
I'm using ArchLinux with an custom AUR package from here:
- https://aur.archlinux.org/packages/gnome-shell-performance/
The reason of using that package is, that on NVIDIA GPU's the gnome shell is unusable and while streaming freezes the system completely.
Gnome-Shell: ae05679498ff78b88ede8f15bd646716366b2ff8
Regards,
TheAifam5https://gitlab.gnome.org/GNOME/gimp/-/issues/5740gimp-2.10.22/app/gui/splash.c:178:8: style:inconclusive: Found duplicate bran...2023-05-20T16:22:28Zdcb314gimp-2.10.22/app/gui/splash.c:178:8: style:inconclusive: Found duplicate branches for 'if' and 'else'Source code is
```
else if (splash->width > 2 * ink.width)
gimp_pango_layout_set_scale (splash->upper, PANGO_SCALE_MEDIUM);
else
gimp_pango_layout_set_scale (splash->upper, PANGO_SCALE_MEDIUM);
```
Might be a possible cut'n'p...Source code is
```
else if (splash->width > 2 * ink.width)
gimp_pango_layout_set_scale (splash->upper, PANGO_SCALE_MEDIUM);
else
gimp_pango_layout_set_scale (splash->upper, PANGO_SCALE_MEDIUM);
```
Might be a possible cut'n'paste error ?2.99.16https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/185Gnome-shell too prone to be killed on out-of-memory2023-05-20T15:55:29ZGunter KönigsmannGnome-shell too prone to be killed on out-of-memoryI hope gnome-shell is the right application to report this for:
When using wayland if my system runs out-of-memory it is quite likely that not the application (maxima/firefox/gcl/gcc) that uses up all the memory gets killed. Instead a p...I hope gnome-shell is the right application to report this for:
When using wayland if my system runs out-of-memory it is quite likely that not the application (maxima/firefox/gcl/gcc) that uses up all the memory gets killed. Instead a process gets killed that causes the display not to change any more (no reaction on mouse movement, keypress, alt+shift+Fn in order to switch to another virtual console or output of the application that continues running.
I assume something triggers the kernel's heuristics for "unimportant processes that can be killed on out-of-memory".
I'm using gnome-shell 3.28.0 and the original bug report reads: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759760https://gitlab.gnome.org/GNOME/gnome-text-editor/-/issues/573gnome-text-editor | Korean | ibus-hangul, F9 popup position is abnormal.2023-05-20T15:38:03Zjimin honggnome-text-editor | Korean | ibus-hangul, F9 popup position is abnormal.Hello, I started to use Arch Linux + GNOME.
I installed ibus, ibus-hangul (Korean IME), gnome-text-editor, google chrome(AUR).
In google-chrome(AUR), when I entered korean character "ㅁ"+F9, special input popup appears normal.
But...Hello, I started to use Arch Linux + GNOME.
I installed ibus, ibus-hangul (Korean IME), gnome-text-editor, google chrome(AUR).
In google-chrome(AUR), when I entered korean character "ㅁ"+F9, special input popup appears normal.
But in **<u>gnome-text-editor</u>**, when I entered korean character "ㅁ"+F9, special input popup appears abnormal.
Please check a screenshot.
Sorry for my poor english.
![스크린샷_2023-05-21_09-14-22](/uploads/3bafc321229496dabda149635f184bc8/스크린샷_2023-05-21_09-14-22.png)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/419Export information about flatpak app windows2023-05-20T15:00:04ZMatthias ClasenExport information about flatpak app windowsSome portals want to allow access only for apps which are active. To do that, we need a way for the portal to find out
a) does a given flatpak app (identified by its app-id) have a window ?
b) is the window active ?
A small dbus interfac...Some portals want to allow access only for apps which are active. To do that, we need a way for the portal to find out
a) does a given flatpak app (identified by its app-id) have a window ?
b) is the window active ?
A small dbus interface for this would be idealhttps://gitlab.gnome.org/GNOME/gimp/-/issues/9469Bunch of errors when trying to do a curve bend2023-05-20T14:58:54ZBitte SonerBunch of errors when trying to do a curve bend### Environment/Versions
- GIMP version: 2.99.14
- Package: <!--[flatpak? Installer from gimp.org? If another installer, tell us where from] (write it after the > symbol)--> From gimp.org
- Operating System: <!--[Windows? macOS? Linux? ...### Environment/Versions
- GIMP version: 2.99.14
- Package: <!--[flatpak? Installer from gimp.org? If another installer, tell us where from] (write it after the > symbol)--> From gimp.org
- Operating System: <!--[Windows? macOS? Linux? All?] (write it after the > symbol) --> Windows 11 22H2
<!--Note: bug reporters are expected to have verified the bug still exists
either in the last stable version of GIMP or on updated development code
(master branch).-->
### Description of the bug
<!--Please describe your issue with details.
Add screenshot or other files if needed.(write it after the > symbol)--> When trying to do a curve bend (see attachment for how I did the curve bend) ![image_2023-05-20_172250874](/uploads/8fcd8f9a3ed90f062e74972c5c8b71e6/image_2023-05-20_172250874.png)
I got a bunch of errors ![image_2023-05-20_172408926](/uploads/c9495b23b3bdbd741f97f88090b6d613/image_2023-05-20_172408926.png),
how do I fix this?
### Reproduction
Is the bug reproducible? <!--[Always / Randomly / Happened only once ] (write it after the > symbol)--> Always
Reproduction steps:
1. Write a text to curve bend it.
2. Make the curve bend looks like this (gray line is the upper curve for border while the black line is the lower curve for border) ![image](/uploads/78b27b6adfce2ab4ec641ac7419f4a13/image.png)
3. Click OK and it should have an error.
…
Expected result: The text middle being streched
Actual result: Erorrs
### Additional information
If you have a backtrace for a crash or a warning, paste it here.
<!-- Copy-paste this whole debug data to report to developers -->
```
GNU Image Manipulation Program version 2.99.14
git-describe: GIMP_2_99_14
Build: org.gimp.GIMP_official rev 0 for windows
# C compiler #
Using built-in specs.
COLLECT_GCC=C:/msys64/mingw64/bin/cc.exe
COLLECT_LTO_WRAPPER=C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: ../gcc-12.2.0/configure --prefix=/mingw64 --with-local-prefix=/mingw64/local --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --with-native-system-header-dir=/mingw64/include --libexecdir=/mingw64/lib --enable-bootstrap --enable-checking=release --with-arch=x86-64 --with-tune=generic --enable-languages=c,lto,c++,fortran,ada,objc,obj-c++,jit --enable-shared --enable-static --enable-libatomic --enable-threads=posix --enable-graphite --enable-fully-dynamic-string --enable-libstdcxx-filesystem-ts --enable-libstdcxx-time --disable-libstdcxx-pch --enable-lto --enable-libgomp --disable-multilib --disable-rpath --disable-win32-registry --disable-nls --disable-werror --disable-symvers --with-libiconv --with-system-zlib --with-gmp=/mingw64 --with-mpfr=/mingw64 --with-mpc=/mingw64 --with-isl=/mingw64 --with-pkgversion='Rev6, Built by MSYS2 project' --with-bugurl=https://github.com/msys2/MINGW-packages/issues --with-gnu-as --with-gnu-ld --disable-libstdcxx-debug --with-boot-ldflags=-static-libstdc++ --with-stage1-ldflags=-static-libstdc++
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (Rev6, Built by MSYS2 project)
# Libraries #
using babl version 0.1.99 (compiled against version 0.1.99)
using GEGL version 0.4.41 (compiled against version 0.4.41)
using GLib version 2.74.1 (compiled against version 2.74.1)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 3.24.34 (compiled against version 3.24.34)
using Pango version 1.50.11 (compiled against version 1.50.11)
using Fontconfig version 2.14.0 (compiled against version 2.14.0)
using Cairo version 1.17.6 (compiled against version 1.17.6)
```
> GIMP-WARNING: gimp-2.99.exe: gimp_wire_read(): error