GNOME issueshttps://gitlab.gnome.org/groups/GNOME/-/issues2024-01-13T10:45:28Zhttps://gitlab.gnome.org/GNOME/mutter/-/issues/1700window jumps out of screen while resizing2024-01-13T10:45:28ZChristian Rauchrauch.christian@gmx.dewindow jumps out of screen while resizing<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Ubuntu 20.04, mutter 3.36.9, Wayland
### Bug summary
When t...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
Ubuntu 20.04, mutter 3.36.9, Wayland
### Bug summary
When trying to interactively resize a window while a new size is committed, the window will jump out of the screen.
### Steps to reproduce
1. download & build the [libdecor example](https://gitlab.gnome.org/christian-rauch/libdecoration/-/archive/7a7d771b2d9e22d8815acd18b327a265f3021508/libdecoration-7a7d771b2d9e22d8815acd18b327a265f3021508.tar.gz) (`meson build && ninja -C build`)
2. run `LIBDECOR_PLUGIN_DIR=build/src/plugins/cairo/ ./build/demo/libdecor-egl`, without interacting the window will switch periodically between two sizes
3. interactively resize the window by dragging on one of the edges and hold
### What happened
The window jumps away when a new size is committed.
### What did you expect to happen
The window should stay in place (x,y) and either keep the interactive size or the new size.
### Relevant logs, screenshots, screencasts etc.
![Bildschirmvideo_von_14.03.2021_21_31_32](/uploads/f7b63374aad4ac5e86b318f9975e800e/Bildschirmvideo_von_14.03.2021_21_31_32.webm)
This does not happen in either weston or egmde/Mir.
<!-- Do not remove the following line. -->GNOME 3.36https://gitlab.gnome.org/GNOME/mutter/-/issues/1690Gnome session crashes when using clipboard tool2021-05-09T15:36:55ZDaryl PIFFREGnome session crashes when using clipboard tool<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
* Fedora 32
* mutter 3.36.8
* Using wayland
### Bug summary...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
* Fedora 32
* mutter 3.36.8
* Using wayland
### Bug summary
If this is not the right place or if you need more information, tell me, I'm really out of my comfort zone writing this.
I've been using this tool : https://github.com/bugaevc/wl-clipboard and it worked fine for some time but now for some reason, using it completely crashes my session. I get this bug report : [crash.zip](/uploads/b7e642295e6730fc01ad3ad3877e8bbb/crash.zip)
I'm just a regular sysadmin and I don't know much about gnome or wayland aside from the basics so I posted the ticket to the tool's issues and they said that it was a problem for you rather than them.
### Steps to reproduce
Not sure how to make you reproduce it since it but it is now crashing every time for me.
But steps would be : download the tool (https://github.com/bugaevc/wl-clipboard), use it for a while and hope it starts crashing your session
### What happened
My gnome session crashed, I was brought back to login and was greeted with a bug report when my session opened.
### What did you expect to happen
I expected to be able to run the command wl-copy without crashing my session and having the information given to wl-copy copied to my clipboard.
### Relevant logs, screenshots, screencasts etc.
The crash report I posted should contain some information
<!-- Do not remove the following line. -->GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2997User Password is Visible on Logout2020-08-11T19:59:07ZMark WillUser Password is Visible on Logout<!--
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:
* Your OS an...<!--
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:
* Your OS and version
* Affected GNOME Shell version
* Does this issue appear in XOrg and/or Wayland
-->
- Noticed in GNOME 3.36 and it's also in 3.34.
- Tested with Pop!_OS, Ubuntu, Manjaro GNOME, and Fedora.
- Tested with 19.10 with 3.34 and 20.04 with 3.36.
- Tested on baremetal and VM.
### Bug summary
<!--
Provide a short summary of the bug you encountered.
-->
When I logout of my account, the password box from the login dialog shows again with the password still there. If when logging in, I decide to have the password visible, it is then visible for a brief moment when I logout. If the password is not visible, only the length is revealed.
### Steps to reproduce
1. Login using the GNOME UI (with password visible)
2. Logout
3. For a brief moment, the password value is visible.
### What happened
The password length or even the whole password are briefly visible.
### What did you expect to happen
The password value should be cleared on successful login.
### Relevant logs, screenshots, screencasts etc.
There is an attached video ![here](/uploads/93f1738b6611572b706278d608899b64/PopOSPassword.m4v).
### Original Discussion
This was discussed in the Pop!_OS community [https://chat.pop-os.org/community/pl/6n339z4g13rhxgie3q39m5e66c](https://chat.pop-os.org/community/pl/6n339z4g13rhxgie3q39m5e66c), with support from **im7ffy** and **technologyman101**.
<!-- Do not remove the following line. -->GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1033sound setting: a possible regression on profile_combo_box2020-06-18T00:50:37ZHui Wangsound setting: a possible regression on profile_combo_boxThere is no issue on gnome-control-center-3.28.2 (ubuntu 18.04)
There is issue on gnome-control-center-3.36.2 (ubuntu 20.04)
On the ubuntu 18.04, open the sound setting, there is profile combo box, users could select wanted profile and ...There is no issue on gnome-control-center-3.28.2 (ubuntu 18.04)
There is issue on gnome-control-center-3.36.2 (ubuntu 20.04)
On the ubuntu 18.04, open the sound setting, there is profile combo box, users could select wanted profile and then it will trigger the callback function profile_selection_changed()
While on ubuntu 20.04, open the sound setting, there is no profile combo box if there is only one profile, users couldn't select profile, so the callback function profile_changed_cb() shouldn't be triggered. But the reality is upon opening the sound-setting, the callback function is called, and whenever the input/output device changes, the callback function is called too. This behaviour is greatly different from gcc-3.28.2.
The callback function should be called only users actively select profile, the callback function will call gvc_mixer_control_change_profile_on_selected_device() in the libgvc, in this function it will set profile_swapping_device_id, then on each output/input device updates, it will call pa_context_set_default_sink/source, this will set configured_default_sink/source in the pulseaudio. The configured_default_sink/source only should be set when users select device from UI, but with gcc-3.36.2, even users don't select anything, the gcc will trigger profile_changed_cb(), then through libgvc and pulseaudio, the configured_default_sink/source is set or changed.
Since there is no profile selection combo box from UI if users have no other profile to select (only 1 profile in total) with gcc-3.36.2, why the callback function profile_changed_cb() is triggered? Could we do some change to let it behave the same as gcc-3.28.2: if users select the profile, the callback function will be called, otherwise it will not be called.
GNOME 3.36Robert AncellRobert Ancellhttps://gitlab.gnome.org/GNOME/gnome-software/-/issues/1008Age rating explanation includes an exhaustive list of attributes not present2020-11-18T07:36:53ZDylan McCallAge rating explanation includes an exhaustive list of attributes not presentIn an application's details panel, GNOME Software includes an age rating and an explanation of that age rating. For applications with negative OARS attributes, such as [Hedgewars from Flathub](https://www.flathub.org/apps/details/org.hed...In an application's details panel, GNOME Software includes an age rating and an explanation of that age rating. For applications with negative OARS attributes, such as [Hedgewars from Flathub](https://www.flathub.org/apps/details/org.hedgewars.Hedgewars) (with a "Teen" rating in my locale), the explanation is simple and straightforward:
> The application was rated this way because it features:
> - Uncontrolled chat functionality between users
However, for an application which has the "Early childhood" rating and no negative attributes, such as [GNOME Sudoku from Flathub](https://www.flathub.org/apps/details/org.gnome.Sudoku) (with an Early Childhood rating in my locale), the explanation is an exhaustive list of every OARS attribute under the sun which it (says it) does not have:
> The application was rated this way because it features:
> - No sexual violence
> - No references to alcohol
> - No references to illicit drugs
> - ...
I find this startling for a few reasons:
- The list is very long, but, unlike the list for Hedgewars, it does not feel like it is intended to be read. Instead, it could be summed up in a sentence: "The application was rated this way because it features no content which we consider objectionable."
- The list of negative attributes could be considered, itself, graphic detail :b There's nothing objectionable in how they are stated (in the right context), but looking at a friendly piece of software and quickly coming across a text box with phrases such as "dead human remains" beneath a button labelled "early childhood" does not inspire exploration.
- At least for ESRB ratings, E-rated software only lists the presence of negative descriptors on the box. For example: https://www.esrb.org/ratings/34067/Shovel+Knight/.
- In some ways, the full list of OARS attributes is an implementation detail. For instance, [D-Feet from Flathub](https://www.flathub.org/apps/details/org.gnome.dfeet) doesn't specify any OARS attributes, so GNOME Software draws from the complete set of possible attributes, including "No references to homosexuality". This is not a factor which should affect the content rating in many locales, and encourages people to file issues such as #993 because it is a concerning thing for GNOME Software to imply that it would.
My suggestion here is to handle the case of an application having no negative attributes differently. Instead of an exhaustive list of "no …", show a simple, non-frightening block of text which says the same thing. There's an argument to be made that the list of "no" attributes serves as documentation. That is, it reassures someone that the rating of some software is based on attributes they consider relevant. However, this list only appears in one case, even though the question of "what does this _not_ have" is just as relevant for something with stronger age restrictions. So perhaps it would make sense, in a separate task, to create a GNOME Help page about how these ratings are generated, or link to some relevant information on the web.GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-mines/-/issues/50Longer left-click adds a marker to a field2021-05-02T16:13:57ZAndre KlapperLonger left-click adds a marker to a fieldIn my understanding,
* a left click uncovers a field.
* a right click adds a marker to a field.
However, in 3.36 on Wayland (Fedora 32), left-clicking on a field and not immediately releasing the mouse also adds a marker.
This is unw...In my understanding,
* a left click uncovers a field.
* a right click adds a marker to a field.
However, in 3.36 on Wayland (Fedora 32), left-clicking on a field and not immediately releasing the mouse also adds a marker.
This is unwanted and disruptive.GNOME 3.36Robert RothRobert Roth2020-08-01https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/988Users configuration screen had no "unlock" or "add user" button if no users s...2020-05-05T11:43:59ZKrister SwensonUsers configuration screen had no "unlock" or "add user" button if no users show up.Detailed description of the issue. Put as much information as you can, potentially
with images showing the issue.
Steps to reproduce:
0. Have a system that displays no users in the GNOME settings users screen (see [this bug](https://bu...Detailed description of the issue. Put as much information as you can, potentially
with images showing the issue.
Steps to reproduce:
0. Have a system that displays no users in the GNOME settings users screen (see [this bug](https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876460) for an example).
1. Open GNOME Settings to the Users screen
2. See that there is no way to add a new user.
![users](/uploads/06fe33e966b70cc4324d1140e85edf85/users.png)GNOME 3.36Ondrej HolyOndrej Holyhttps://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/532Express Install for Fedora 31 Silverblue doesn't set password2020-06-15T09:03:25ZZlopezExpress Install for Fedora 31 Silverblue doesn't set passwordI tried to create a new VM with Fedora 31 Silverblue using express install and after installation I wasn't able to log in. Upon future investigation I found out that user in `/etc/shadow` has no password set.
gnome-boxes version: 3.36.3...I tried to create a new VM with Fedora 31 Silverblue using express install and after installation I wasn't able to log in. Upon future investigation I found out that user in `/etc/shadow` has no password set.
gnome-boxes version: 3.36.3-8c546823 - Flathub flatpakGNOME 3.36https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/583Today has wrong week2023-08-03T12:42:22ZStefan LindbladToday has wrong weekToday is Sunday (w.17) in Sweden, where weeks starts on Mondays. When pressing the today button I see the following week (w.18), and not the week where today is present (w.17).
Steps to reproduce:
1. Open GNOME Calendar on a Sunday, wi...Today is Sunday (w.17) in Sweden, where weeks starts on Mondays. When pressing the today button I see the following week (w.18), and not the week where today is present (w.17).
Steps to reproduce:
1. Open GNOME Calendar on a Sunday, with weeks starting on Mondays.GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/574Crash in gcal_event_is_multiday2023-02-11T05:04:12ZSéverin LemaignanCrash in gcal_event_is_multiday```
$ gnome-calendar --version
gnome-calendar: Version 3.36.0
```
## Steps to reproduce:
This crash seems to be dependent on the content of my calendar, but it is perfectly reproducible. Every time I navigate to a specific week, `gnome...```
$ gnome-calendar --version
gnome-calendar: Version 3.36.0
```
## Steps to reproduce:
This crash seems to be dependent on the content of my calendar, but it is perfectly reproducible. Every time I navigate to a specific week, `gnome-calendar` immediately crashes.
I can probably share the corresponding `.ical` if useful to reproduce.
## Backtrace
```
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f85f1d530f0 in g_type_check_instance_is_a (type_instance=type_instance@entry=0x55900e8a41e0, iface_type=<optimised out>) at ../../../gobject/gtype.c:4016
4016 ../../../gobject/gtype.c: No such file or directory.
[Current thread is 1 (Thread 0x7f85e800b200 (LWP 114391))]
(gdb) bt
#0 0x00007f85f1d530f0 in g_type_check_instance_is_a (type_instance=type_instance@entry=0x55900e8a41e0, iface_type=<optimised out>) at ../../../gobject/gtype.c:4016
#1 0x000055900c26bf0b in GCAL_IS_EVENT (ptr=0x55900e8a41e0) at ../src/core/gcal-event.h:47
#2 gcal_event_is_multiday (self=self@entry=0x55900e8a41e0) at ../src/core/gcal-event.c:1484
#3 0x000055900c2850cd in compare_events_by_length (event1=event1@entry=0x55900f86f0a0 [GcalEvent], event2=0x55900e8a41e0) at ../src/views/gcal-week-header.c:400
#4 0x00007f85f1c38f98 in g_list_insert_sorted_real
(list=0x55900ea41d00 = {...}, data=data@entry=0x55900f86f0a0, func=func@entry=0x55900c2850b0 <compare_events_by_length>, user_data=user_data@entry=0x0) at ../../../glib/glist.c:1109
#5 0x00007f85f1c39bdb in g_list_insert_sorted (list=<optimised out>, data=data@entry=0x55900f86f0a0, func=func@entry=0x55900c2850b0 <compare_events_by_length>)
at ../../../glib/glist.c:1166
#6 0x000055900c287c6d in add_event_to_weekday (weekday=-7, event=0x55900f86f0a0 [GcalEvent], self=0x55900ea741c0 [GcalWeekHeader]) at ../src/views/gcal-week-header.c:415
#7 add_event_to_grid (end=6, start=-7, event=0x55900f86f0a0 [GcalEvent], self=0x55900ea741c0 [GcalWeekHeader]) at ../src/views/gcal-week-header.c:794
#8 gcal_week_header_add_event (self=0x55900ea741c0 [GcalWeekHeader], event=0x55900f86f0a0 [GcalEvent]) at ../src/views/gcal-week-header.c:1797
#9 0x000055900c2889ee in update_unchanged_events (new_date=<optimised out>, self=0x55900ea741c0 [GcalWeekHeader]) at ../src/views/gcal-week-header.c:956
#10 gcal_week_header_set_date (self=0x55900ea741c0 [GcalWeekHeader], date=<optimised out>) at ../src/views/gcal-week-header.c:1928
#11 0x000055900c25fbdc in gcal_week_view_set_date (view=<optimised out>, date=0x55900daabd20) at ../src/views/gcal-week-header.h:33
#12 0x000055900c253ca8 in update_active_date (window=window@entry=0x55900f5e32a0 [GcalWindow], new_date=new_date@entry=0x55900daabd20) at ../src/gui/gcal-window.c:254
#13 0x000055900c254995 in on_window_next_date_activated_cb (action=<optimised out>, param=<optimised out>, user_data=<optimised out>) at ../src/gui/gcal-window.c:357
#17 0x00007f85f1d4b0d3 in <emit signal ??? on instance 0x55900e019d40 [GSimpleAction]> (instance=instance@entry=0x55900e019d40, signal_id=<optimised out>, detail=detail@entry=0)
at ../../../gobject/gsignal.c:3554
#14 0x00007f85f1d2b802 in g_closure_invoke (closure=0x55900e19afa0, return_value=0x0, n_param_values=2, param_values=0x7ffd8a77f210, invocation_hint=0x7ffd8a77f190)
at ../../../gobject/gclosure.c:810
#15 0x00007f85f1d3f814 in signal_emit_unlocked_R
(node=node@entry=0x7f85dc00a860, detail=detail@entry=0, instance=instance@entry=0x55900e019d40, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffd8a77f210) at ../../../gobject/gsignal.c:3742
#16 0x00007f85f1d4ab9e in g_signal_emit_valist (instance=<optimised out>, signal_id=<optimised out>, detail=<optimised out>, var_args=var_args@entry=0x7ffd8a77f3e0)
at ../../../gobject/gsignal.c:3498
#18 0x00007f85f1e62e25 in g_simple_action_activate (action=0x55900e019d40, parameter=0x0) at ../../../gio/gsimpleaction.c:225
#19 0x00007f85f2474932 in gtk_action_muxer_activate_action (action_group=0x55900f915b80, action_name=0x559010b76c70 "win.next-date", parameter=0x0) at ../../../../gtk/gtkactionmuxer.c:413
#20 0x00007f85f2474964 in gtk_action_muxer_activate_action (parameter=0x0, action_name=0x559010b76c70 "win.next-date", action_group=0x559010d20780) at ../../../../gtk/gtkactionmuxer.c:415
#21 gtk_action_muxer_activate_action (action_group=0x559010d20780, action_name=0x559010b76c70 "win.next-date", parameter=0x0) at ../../../../gtk/gtkactionmuxer.c:402
#22 0x00007f85f2474964 in gtk_action_muxer_activate_action (parameter=0x0, action_name=0x559010b76c70 "win.next-date", action_group=0x559010bc5740) at ../../../../gtk/gtkactionmuxer.c:415
#23 gtk_action_muxer_activate_action (action_group=0x559010bc5740, action_name=0x559010b76c70 "win.next-date", parameter=0x0) at ../../../../gtk/gtkactionmuxer.c:402
#24 0x00007f85f2474964 in gtk_action_muxer_activate_action (parameter=0x0, action_name=0x559010b76c70 "win.next-date", action_group=0x5590105f5480) at ../../../../gtk/gtkactionmuxer.c:415
#25 gtk_action_muxer_activate_action (action_group=0x5590105f5480, action_name=0x559010b76c70 "win.next-date", parameter=0x0) at ../../../../gtk/gtkactionmuxer.c:402
#26 0x00007f85f24a9227 in gtk_real_button_clicked (button=<optimised out>) at ../../../../gtk/gtkbutton.c:1975
#27 0x00007f85f1d2ba56 in _g_closure_invoke_va (closure=0x559010b21740, return_value=0x0, instance=0x55900e9e6340, args=0x7ffd8a77f7d0, n_params=0, param_types=0x0)
at ../../../gobject/gclosure.c:873
#28 0x00007f85f1d4ab28 in g_signal_emit_valist (instance=0x55900e9e6340, signal_id=<optimised out>, detail=0, var_args=var_args@entry=0x7ffd8a77f7d0) at ../../../gobject/gsignal.c:3407
#29 0x00007f85f1d4b0d3 in g_signal_emit (instance=<optimised out>, signal_id=<optimised out>, detail=<optimised out>) at ../../../gobject/gsignal.c:3554
#30 0x00007f85f24ab2ae in gtk_button_do_release (emit_clicked=<optimised out>, button=0x55900e9e6340 [GtkButton]) at ../../../../gtk/gtkbutton.c:1845
#31 gtk_button_do_release (button=0x55900e9e6340 [GtkButton], emit_clicked=<optimised out>) at ../../../../gtk/gtkbutton.c:1832
#32 0x00007f85f24ab318 in gtk_real_button_released (button=0x55900e9e6340 [GtkButton]) at ../../../../gtk/gtkbutton.c:1963
#36 0x00007f85f1d4b0d3 in <emit signal ??? on instance 0x55900e9e6340 [GtkButton]> (instance=instance@entry=0x55900e9e6340, signal_id=<optimised out>, detail=detail@entry=0)
at ../../../gobject/gsignal.c:3554
#33 0x00007f85f1d2b802 in g_closure_invoke (closure=0x55900d9b8670, return_value=0x0, n_param_values=1, param_values=0x7ffd8a77fae0, invocation_hint=0x7ffd8a77fa60)
at ../../../gobject/gclosure.c:810
#34 0x00007f85f1d3f962 in signal_emit_unlocked_R
(node=node@entry=0x55900d996d80, detail=detail@entry=0, instance=instance@entry=0x55900e9e6340, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffd8a77fae0) at ../../../gobject/gsignal.c:3672
#35 0x00007f85f1d4ab9e in g_signal_emit_valist (instance=<optimised out>, signal_id=<optimised out>, detail=<optimised out>, var_args=var_args@entry=0x7ffd8a77fc90)
at ../../../gobject/gsignal.c:3498
#37 0x00007f85f24a9754 in multipress_released_cb
(gesture=0x55900ea14260 [GtkGestureMultiPress], n_press=<optimised out>, x=<optimised out>, y=<optimised out>, widget=0x55900e9e6340 [GtkButton]) at ../../../../gtk/gtkbutton.c:666
#38 0x00007f85f275a661 in _gtk_marshal_VOID__INT_DOUBLE_DOUBLEv
(closure=<optimised out>, return_value=<optimised out>, instance=<optimised out>, args=<optimised out>, marshal_data=<optimised out>, n_params=<optimised out>, param_types=0x55900e8a8a30) at gtkmarshalers.c:4803
#39 0x00007f85f1d2ba56 in _g_closure_invoke_va (closure=0x55901107d180, return_value=0x0, instance=0x55900ea14260, args=0x7ffd8a77ffe0, n_params=3, param_types=0x55900e8a8a30) at ../../../gobject/gclosure.c:873
#40 0x00007f85f1d4ab28 in g_signal_emit_valist (instance=0x55900ea14260, signal_id=<optimised out>, detail=0, var_args=var_args@entry=0x7ffd8a77ffe0) at ../../../gobject/gsignal.c:3407
#41 0x00007f85f1d4b0d3 in g_signal_emit (instance=instance@entry=0x55900ea14260, signal_id=<optimised out>, detail=detail@entry=0) at ../../../gobject/gsignal.c:3554
#42 0x00007f85f2571f1c in gtk_gesture_multi_press_end (gesture=gesture@entry=0x55900ea14260 [GtkGestureMultiPress], sequence=sequence@entry=0x0) at ../../../../gtk/gtkgesturemultipress.c:287
#43 0x00007f85f1d2ec56 in g_cclosure_marshal_VOID__BOXEDv (closure=0x55900e8aaee0, return_value=<optimised out>, instance=<optimised out>, args=<optimised out>, marshal_data=<optimised out>, n_params=<optimised out>, param_types=0x55900e8aaf10) at ../../../gobject/gmarshal.c:1686
#44 0x00007f85f1d2ba56 in _g_closure_invoke_va (closure=0x55900e8aaee0, return_value=0x0, instance=0x55900ea14260, args=0x7ffd8a780390, n_params=1, param_types=0x55900e8aaf10) at ../../../gobject/gclosure.c:873
#45 0x00007f85f1d4ab28 in g_signal_emit_valist (instance=0x55900ea14260, signal_id=<optimised out>, detail=0, var_args=var_args@entry=0x7ffd8a780390) at ../../../gobject/gsignal.c:3407
#46 0x00007f85f1d4b0d3 in g_signal_emit (instance=instance@entry=0x55900ea14260, signal_id=<optimised out>, detail=detail@entry=0) at ../../../gobject/gsignal.c:3554
#47 0x00007f85f256ef62 in _gtk_gesture_set_recognized (sequence=0x0, recognized=0, gesture=0x55900ea14260 [GtkGestureMultiPress]) at ../../../../gtk/gtkgesture.c:346
#48 _gtk_gesture_check_recognized (gesture=gesture@entry=0x55900ea14260 [GtkGestureMultiPress], sequence=sequence@entry=0x0) at ../../../../gtk/gtkgesture.c:387
#49 0x00007f85f25705ab in gtk_gesture_handle_event (event=0x55900e39cb20, controller=0x55900ea14260 [GtkGestureMultiPress]) at ../../../../gtk/gtkgesture.c:815
#50 gtk_gesture_handle_event (controller=0x55900ea14260 [GtkGestureMultiPress], event=0x55900e39cb20) at ../../../../gtk/gtkgesture.c:713
#51 0x00007f85f2573596 in gtk_gesture_single_handle_event (controller=0x55900ea14260 [GtkGestureMultiPress], event=0x55900e39cb20) at ../../../../gtk/gtkgesturesingle.c:222
#52 0x00007f85f253abd0 in gtk_event_controller_handle_event (controller=0x55900ea14260 [GtkGestureMultiPress], event=event@entry=0x55900e39cb20) at ../../../../gtk/gtkeventcontroller.c:230
#53 0x00007f85f26fcced in _gtk_widget_run_controllers (widget=0x55900e9e6340 [GtkButton], event=0x55900e39cb20, phase=GTK_PHASE_BUBBLE) at ../../../../gtk/gtkwidget.c:7443
#54 0x00007f85f275416f in _gtk_marshal_BOOLEAN__BOXEDv (closure=0x55900d8231f0, return_value=0x7ffd8a780730, instance=<optimised out>, args=<optimised out>, marshal_data=<optimised out>, n_params=<optimised out>, param_types=0x55900d823220) at gtkmarshalers.c:129
#55 0x00007f85f1d2ba56 in _g_closure_invoke_va (closure=0x55900d8231f0, return_value=0x7ffd8a780730, instance=0x55900e9e6340, args=0x7ffd8a780800, n_params=1, param_types=0x55900d823220) at ../../../gobject/gclosure.c:873
#56 0x00007f85f1d49dd1 in g_signal_emit_valist (instance=0x55900e9e6340, signal_id=<optimised out>, detail=<optimised out>, var_args=var_args@entry=0x7ffd8a780800) at ../../../gobject/gsignal.c:3407
#57 0x00007f85f1d4b0d3 in g_signal_emit (instance=instance@entry=0x55900e9e6340, signal_id=<optimised out>, detail=detail@entry=0) at ../../../gobject/gsignal.c:3554
#58 0x00007f85f26fe7a3 in gtk_widget_event_internal (event=0x55900e39cb20, widget=0x55900e9e6340 [GtkButton]) at ../../../../gtk/gtkwidget.c:7808
#59 gtk_widget_event_internal (widget=0x55900e9e6340 [GtkButton], event=0x55900e39cb20) at ../../../../gtk/gtkwidget.c:7677
#60 0x00007f85f25b9fe8 in propagate_event_up (topmost=<optimised out>, event=<optimised out>, widget=0x55900e9e6340 [GtkButton]) at ../../../../gtk/gtkmain.c:2594
#61 propagate_event (widget=<optimised out>, event=0x55900e39cb20, captured=<optimised out>, topmost=0x0) at ../../../../gtk/gtkmain.c:2697
#62 0x00007f85f25bc29b in gtk_main_do_event (event=0x55900e39cb20) at ../../../../gtk/gtkmain.c:1917
#63 gtk_main_do_event (event=<optimised out>) at ../../../../gtk/gtkmain.c:1687
#64 0x00007f85f22a4f79 in _gdk_event_emit (event=event@entry=0x55900e39cb20) at ../../../../gdk/gdkevents.c:73
#65 0x00007f85f22d80f6 in gdk_event_source_dispatch (source=<optimised out>, callback=<optimised out>, user_data=<optimised out>) at ../../../../../gdk/x11/gdkeventsource.c:367
#66 0x00007f85f1c3dfbd in g_main_dispatch (context=0x55900d781bf0) at ../../../glib/gmain.c:3309
#67 g_main_context_dispatch (context=context@entry=0x55900d781bf0) at ../../../glib/gmain.c:3974
#68 0x00007f85f1c3e240 in g_main_context_iterate (context=context@entry=0x55900d781bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimised out>) at ../../../glib/gmain.c:4047
#69 0x00007f85f1c3e2e3 in g_main_context_iteration (context=context@entry=0x55900d781bf0, may_block=may_block@entry=1) at ../../../glib/gmain.c:4108
#70 0x00007f85f1e59f05 in g_application_run (application=0x55900d76d1e0 [GcalApplication], argc=<optimised out>, argv=<optimised out>) at ../../../gio/gapplication.c:2559
#71 0x000055900c2506d2 in main (argc=2, argv=0x7ffd8a780c78) at ../src/main.c:39
```GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/933Wired Connection dialog window: Rows of text collide and are not readable2020-09-04T06:28:24ZHussam Al-TayebWired Connection dialog window: Rows of text collide and are not readableFor some reason, the wired connection dialog window is too small and does not automatically expand to fit its contents. The wifi connection dialog on the other hand is large enough.
![Screenshot_from_2020-03-25_02-56-36](/uploads/14cff5e...For some reason, the wired connection dialog window is too small and does not automatically expand to fit its contents. The wifi connection dialog on the other hand is large enough.
![Screenshot_from_2020-03-25_02-56-36](/uploads/14cff5e3d2ca0510e8d765c1a7657738/Screenshot_from_2020-03-25_02-56-36.png)![Screenshot_from_2020-03-25_18-39-53](/uploads/0e226a80f3e7b97bd6880b551a1a9caa/Screenshot_from_2020-03-25_18-39-53.png).
Notice how the "last used" row is not given enough space to show.GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/553Show additional events button is broken2023-12-14T03:22:09ZMichael CatanzaroShow additional events button is brokenUsing gnome-calendar 3.34.2-1.fc31, I can't see the description for the event I'm about to join. See this screenshot:
![Screenshot_from_2020-03-19_10-26-34](/uploads/b765f7f5ce2bcd8385882315f3d2affd/Screenshot_from_2020-03-19_10-26-34.p...Using gnome-calendar 3.34.2-1.fc31, I can't see the description for the event I'm about to join. See this screenshot:
![Screenshot_from_2020-03-19_10-26-34](/uploads/b765f7f5ce2bcd8385882315f3d2affd/Screenshot_from_2020-03-19_10-26-34.png)
When I click the +3 button, an empty window appears. It should display the three extra events, but instead it displays nothing. I can't screenshot this window.GNOME 3.36Georges Basile Stavracas NetoGeorges Basile Stavracas Netohttps://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/142Wrong internet speed stat2020-11-09T18:19:00ZSourav GoswamiWrong internet speed statI was seeing stars in excitement when gnome-system-monitor showed 8 EiB DL/UL speed where my ISP provides 2 MiB/s max speed.
![Screenshot_from_2020-03-16_22-55-36](/uploads/59764a0645341b028b69a4ebf7ae362a/Screenshot_from_2020-03-16_22-...I was seeing stars in excitement when gnome-system-monitor showed 8 EiB DL/UL speed where my ISP provides 2 MiB/s max speed.
![Screenshot_from_2020-03-16_22-55-36](/uploads/59764a0645341b028b69a4ebf7ae362a/Screenshot_from_2020-03-16_22-55-36.png)
Version: 3.36.0 on Arch Linux x86_64GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/914Users - Take a Picture option is shown even when no camera is available2021-02-23T13:06:52ZDylan McCallUsers - Take a Picture option is shown even when no camera is availableIn the Users panel, there is a "Take a Picture" button for choosing a profile picture. However, this option is incorrectly visible and interactive on a system with no camera connected. When I click this button, I see the "Take a Photo" d...In the Users panel, there is a "Take a Picture" button for choosing a profile picture. However, this option is incorrectly visible and interactive on a system with no camera connected. When I click this button, I see the "Take a Photo" dialog, but with a big scary red icon in place of a preview.
Steps to reproduce:
1. On a system with no camera, open GNOME Settings.
2. Go the Users panel, and click a profile picture.
3. Note that the "Take a Picture" button is visible alongside "Select a File".
![Screenshot_from_2020-03-13_10-45-06](/uploads/4f19d0ef2742da999161ab4a27f3c5b9/Screenshot_from_2020-03-13_10-45-06.png)
![Screenshot_from_2020-03-13_10-45-17](/uploads/619d9466126cfa2b89bff356c62bc720/Screenshot_from_2020-03-13_10-45-17.png)GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/550One-day event displayed as extending for entire month2023-03-06T05:39:37ZMichael CatanzaroOne-day event displayed as extending for entire monthSee screenshot:
![Screenshot_from_2020-03-13_10-21-47](/uploads/6727b459cd73573d903e7ae21ad33929/Screenshot_from_2020-03-13_10-21-47.png)
Clearly something is wrong with this event:
![Screenshot_from_2020-03-13_10-22-50](/uploads/392f...See screenshot:
![Screenshot_from_2020-03-13_10-21-47](/uploads/6727b459cd73573d903e7ae21ad33929/Screenshot_from_2020-03-13_10-21-47.png)
Clearly something is wrong with this event:
![Screenshot_from_2020-03-13_10-22-50](/uploads/392fec134cda8b1428def348d529f998/Screenshot_from_2020-03-13_10-22-50.png)
So it is, correctly, defined as an all-day event on November 1. But for some reason, gnome-calendar 3.34.2 displays the event as beginning October 1 and ending November 1.GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/903The resolution list shows only current using resolution, if it is low resolut...2020-03-30T01:48:04ZJian-Hong PanThe resolution list shows only current using resolution, if it is low resolution like 720x576Settings->Devices->Display, tap on Resolution and it shows over 10 resolutions. Then choose low resolution like 720x576 and apply it. However, if we tap resolution again , it shows only one resolution - 720x576 , so user can't set it b...Settings->Devices->Display, tap on Resolution and it shows over 10 resolutions. Then choose low resolution like 720x576 and apply it. However, if we tap resolution again , it shows only one resolution - 720x576 , so user can't set it back or set to another resolution.
![Screenshot_from_2020-03-06_13-47-21](/uploads/5195e94beb0c321d462d0b5a3effb813/Screenshot_from_2020-03-06_13-47-21.png)GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2255Lock screen triggers g_error() when animations are disabled2020-03-06T14:33:12ZFlorian Müllnerfmuellner@gnome.orgLock screen triggers g_error() when animations are disabled<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
master
<!--
Provide at least the following information:
* Yo...<!--
Please read https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
first to ensure that you create a clear and specific issue.
-->
### Affected version
master
<!--
Provide at least the following information:
* Your OS and version
* Affected GNOME Shell version
* Does this issue appear in XOrg and/or Wayland
-->
### Bug summary
The lock screen crashes when animations are disabled.
### Steps to reproduce
1. Disable animations:
```sh
$ gsettings set org.gnome.desktop.interface enable-animations false
```
2. Lock the screen
3. Bring up the auth prompt (click, esc, ...)
### What happened
The shell aborts with
```
(gnome-shell:61155): Clutter-ERROR **: 19:01:10.075: ClutterBoxLayout child <unnamed>[<Gjs_ui_shellEntry_CapsLockWarning>:0x4fc1c80] natural height: 0.000000 < minimum 25.000000 for width 337.000000
== Stack trace for context 0x1bba4b0 ==
#0 1e4ff18 i resource:///org/gnome/shell/ui/unlockDialog.js:446 (29ce17946088 @ 1590)
```
<!--
What did GNOME Shell do that was unexpected?
-->
### Additional observations
Trying out the polkit dialog with animations disabled turns out to be fine, including toggling caps lock on/off.
Overriding `vfunc_get_preferred_height()` of `CapsLockWarning` shows it only requests sane values (nat > min > 0).
The following diff for some reason "fixes" the crash:
```diff
diff --git a/js/ui/shellEntry.js b/js/ui/shellEntry.js
index c1a1f1134..cf6953ce8 100644
--- a/js/ui/shellEntry.js
+++ b/js/ui/shellEntry.js
@@ -193,7 +193,6 @@ class CapsLockWarning extends St.Label {
this.natural_height_set = false;
let [, height] = this.get_preferred_height(-1);
- this.natural_height_set = true;
this.ease({
height: capsLockOn ? height : 0,
```
The above breaks some animations, so it's not an actual fix. This on the other hand might be, but I need to investigate some more:
```diff
diff --git a/js/ui/shellEntry.js b/js/ui/shellEntry.js
index c1a1f1134..38f5a836d 100644
--- a/js/ui/shellEntry.js
+++ b/js/ui/shellEntry.js
@@ -191,9 +191,10 @@ class CapsLockWarning extends St.Label {
this.remove_all_transitions();
+ const { naturalHeightSet } = this;
this.natural_height_set = false;
let [, height] = this.get_preferred_height(-1);
- this.natural_height_set = true;
+ this.natural_height_set = naturalHeightSet;
this.ease({
height: capsLockOn ? height : 0,
```
<!-- Do not remove the following line. -->GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-software/-/issues/9283.35.x crashing with `gs_review_histogram_set_ratings`2020-11-16T11:10:52ZAllan Day3.35.x crashing with `gs_review_histogram_set_ratings`I had this crash today testing Fedora 32. From the retrace reports it looks like it is new for 3.35.x/3.36:
https://retrace.fedoraproject.org/faf/reports/2829457/
I can't say exactly what I was doing at the time. @matthiasc seems to ha...I had this crash today testing Fedora 32. From the retrace reports it looks like it is new for 3.35.x/3.36:
https://retrace.fedoraproject.org/faf/reports/2829457/
I can't say exactly what I was doing at the time. @matthiasc seems to have had the same issue, when he clicked on an application tile in the developer tools section.GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2244Custom User Login Avatar not reflecting on the lock screen.2020-02-20T23:54:53ZClinton FrayCustom User Login Avatar not reflecting on the lock screen.Gnome 3.35.91
System: Wayland![5.after_gnome_logout](/uploads/1223bd3bc3c2e74f4f987552e3d2b5a2/5.after_gnome_logout.jpg)
### Bug summary
When updating the user profile to a custom avatar or image, the image does not show on the lock sc...Gnome 3.35.91
System: Wayland![5.after_gnome_logout](/uploads/1223bd3bc3c2e74f4f987552e3d2b5a2/5.after_gnome_logout.jpg)
### Bug summary
When updating the user profile to a custom avatar or image, the image does not show on the lock screen.
Changing the picture to one of the pictures in the predefined list, then it reflects when locking the screen.
When you change the profile picture to a custom avatar and you logout the session, then the user profile image appears. When you try and change the profile picture again it defaults to the last custom picture, until you logout of the current gnome session.
1. Go to settings change select users.
2. Change the user profile and select a customer file.
3. Lock the screen, if you had the standard picture than this will show and not the updated profile picture.
![1.lock_screen_before_change](/uploads/77f0d1f0c38dd164da3c07ddaeae6a0a/1.lock_screen_before_change.jpg)![2.before_the_profile_change](/uploads/7bd6da39a1f8c0a158990ca07a39c85c/2.before_the_profile_change.png)![3.profile_avatar_updated](/uploads/fc1af16d73500f1ad174ffe408a488f4/3.profile_avatar_updated.png)![4.lock_screen_after_profile_change](/uploads/45c669547cb7381c405e6a41ec3248ab/4.lock_screen_after_profile_change.jpg)
<!-- Do not remove the following line. -->GNOME 3.36https://gitlab.gnome.org/GNOME/mutter/-/issues/1058Cursor is invisible on Wayland2020-04-25T17:20:10ZDaniel SmithCursor is invisible on Wayland### Affected version
OS: Fedora 32.20200219.n.0 (Workstation Edition) (Silverblue)
Mutter: mutter-3.35.91-1.fc32.x86_64
Kernel: kernel-5.6.0-0.rc2.git0.1.fc32.x86_64
Mesa: mesa-libGL-20.0.0~rc3-1.fc32.x86_64
### Bug summary
When usi...### Affected version
OS: Fedora 32.20200219.n.0 (Workstation Edition) (Silverblue)
Mutter: mutter-3.35.91-1.fc32.x86_64
Kernel: kernel-5.6.0-0.rc2.git0.1.fc32.x86_64
Mesa: mesa-libGL-20.0.0~rc3-1.fc32.x86_64
### Bug summary
When using a hardware cursor, it is invisible. I can still interact with the desktop.
### Relevant logs, screenshots, screencasts etc.
These show up in the journal when moving the mouse.
```
Feb 20 14:05:31 isaplanet-local gnome-shell[1921]: set_crtc_cursor: assertion 'cursor_plane' failed
Feb 20 14:05:31 isaplanet-local gnome-shell[1921]: unset_crtc_cursor: assertion 'cursor_plane' failed
```
GPU driver. This happens with both amdgpu and radeon.
```
Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org (0x1002)
Device: AMD PITCAIRN (DRM 2.50.0, 5.6.0-0.rc2.git0.1.fc32.x86_64, LLVM 9.0.1) (0x6811)
Version: 20.0.0
Accelerated: yes
Video memory: 2048MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 4.5
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
<!-- Do not remove the following line. -->GNOME 3.36