gnome-shell issueshttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues2019-07-16T01:01:23Zhttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1062Crash for certain entries in org.gnome.clocks world-clocks2019-07-16T01:01:23ZMichael LassCrash for certain entries in org.gnome.clocks world-clocksAfter updating to gnome-shell 3.32.0 on Arch Linux, gnome-shell crashed directly on login for me with the following messages in the journal:
```
Mär 16 00:02:38 bevan-thinkpad gnome-shell[9571]: g_callable_info_get_n_args: assertion 'in...After updating to gnome-shell 3.32.0 on Arch Linux, gnome-shell crashed directly on login for me with the following messages in the journal:
```
Mär 16 00:02:38 bevan-thinkpad gnome-shell[9571]: g_callable_info_get_n_args: assertion 'info != NULL' failed
Mär 16 00:02:38 bevan-thinkpad gnome-shell[9571]: Failed to launch ibus-daemon: Kindprozess »ibus-daemon« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden)
Mär 16 00:02:38 bevan-thinkpad gnome-shell[9571]: JS ERROR: TypeError: b.location.get_timezone(...) is null
_clocksChanged/<@resource:///org/gnome/shell/ui/dateMenu.js:127:20
_clocksChanged@resource:///org/gnome/shell/ui/dateMenu.js:125:9
_connectHandler@resource:///org/gnome/shell/misc/util.js:472:9
watchSetting@resource:///org/gnome/shell/misc/util.js:463:9
WorldClocksSection@resource:///org/gnome/shell/ui/dateMenu.js:102:9
_init@resource:///org/gnome/shell/ui/dateMenu.js:530:28
_ensureIndicator@resource:///org/gnome/shell/ui/panel.js:1115:25
_updateBox@resource:///org/gnome/shell/ui/panel.js:1126:29
_updatePanel@resource:///org/gnome/shell/ui/panel.js:1071:9
_init@resource:///org/gnome/shell/ui/panel.js:872:9
_initializeUI@resource:///org/gnome/shell/ui/main.js:175:13
start@resource:///org/gnome/shell/ui/main.js:124:5
@<main>:1:31
Mär 16 00:02:38 bevan-thinkpad gnome-shell[9571]: Execution of main.js threw exception: Script <main> threw an exception
Mär 16 00:02:38 bevan-thinkpad gnome-shell[9571]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Mär 16 00:02:38 bevan-thinkpad gnome-shell[9571]: The offending signal was destroy on Gjs_DateMenuButton 0x5583714a58e0.
Mär 16 00:02:38 bevan-thinkpad org.gnome.Shell.desktop[9571]: == Stack trace for context 0x55836fffc290 ==
Mär 16 00:02:38 bevan-thinkpad gnome-session[9530]: gnome-session-binary[9530]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Mär 16 00:02:38 bevan-thinkpad gnome-session-binary[9530]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
```
I could work around this issue by wiping "org.gnome.clocks" in gsettings:
```
gsettings list-recursively org.gnome.clocks > world-clocks.bak
gsettings reset-recursively org.gnome.clocks
```
Here is the old content which caused the crash:
```
org.gnome.clocks timer uint32 1800
org.gnome.clocks geolocation true
org.gnome.clocks world-clocks [{'location': <(uint32 2, <('Anywhere on Earth (AoE)', '@AoE', false, @a(dd) [], @a(dd) [])>)>}, {'location': <(uint32 2, <('San Francisco', 'KSFO', true, [(0.65658801258494626, -2.1356672871875406)], [(0.659296885757089, -2.1366218601153339)])>)>}, {'location': <(uint32 2, <('New York City, Central Park', 'KNYC', false, [(0.71180344078725644, -1.2909618758762367)], [(0.71059804659265924, -1.2916478949920254)])>)>}, {'location': <(uint32 2, <('Panamá', 'MPHO', true, [(0.15562519745392522, -1.3892820845874863)], [(0.15649786207992239, -1.3881185259350592)])>)>}, {'location': <(uint32 2, <('Santiago', 'SCEL', true, [(-0.58264907613967609, -1.2354022163855554)], [(-0.58381263479210321, -1.2333660105604238)])>)>}, {'location': <(uint32 2, <('Coordinated Universal Time (UTC)', '@UTC', false, @a(dd) [], @a(dd) [])>)>}, {'location': <(uint32 2, <('Moscow', 'UUWW', true, [(0.97127572873484425, 0.65042604039431762)], [(0.97305983920281813, 0.65651530216830811)])>)>}, {'location': <(uint32 2, <('Shanghai', 'ZSSS', true, [(0.54396095602266359, 2.1194114825206833)], [(0.54493057368860898, 2.1198429802716539)])>)>}, {'location': <(uint32 2, <('Tokyo', 'RJTI', true, [(0.62191898430954862, 2.4408429589140699)], [(0.62282074357417661, 2.4391218722853854)])>)>}, {'location': <(uint32 2, <('Sydney', 'YSSY', true, [(-0.59253928105207498, 2.6386469349889961)], [(-0.59137572239964786, 2.6392287230418559)])>)>}]
org.gnome.clocks alarms @aa{sv} []
```https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1064alt+esc doesn't work anymore in 3.32: TypeError: this._switcherList is null2019-03-18T09:54:07ZAhmed Khaledalt+esc doesn't work anymore in 3.32: TypeError: this._switcherList is nullPressing *Alt+Esc* doesn't do anything after upgrading to Gnome 3.32 and it prints this error message in the systemd journal when I press it:
```
JS ERROR: TypeError: this._switcherList is null
vfunc_allocate@resource:///org/gnome/shell/...Pressing *Alt+Esc* doesn't do anything after upgrading to Gnome 3.32 and it prints this error message in the systemd journal when I press it:
```
JS ERROR: TypeError: this._switcherList is null
vfunc_allocate@resource:///org/gnome/shell/ui/switcherPopup.js:81:13
```GNOME 3.32https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1065"JS ERROR: TypeError: this._workspacesViews[i] is undefined" when opening the...2021-08-26T19:30:57ZLéo"JS ERROR: TypeError: this._workspacesViews[i] is undefined" when opening the activities overviewFrom time to time, I can see this error in system logs when opening the activities overview:
```
mars 16 14:40:35 gnome-shell[1749]: JS ERROR: TypeError: this._workspacesViews[i] is undefined
_updateWo...From time to time, I can see this error in system logs when opening the activities overview:
```
mars 16 14:40:35 gnome-shell[1749]: JS ERROR: TypeError: this._workspacesViews[i] is undefined
_updateWorkspacesFullGeometry@resource:///org/gnome/shell/ui/workspacesView.js:639:13
setWorkspacesFullGeometry@resource:///org/gnome/shell/ui/workspacesView.js:629:9
setWorkspacesFullGeometry@resource:///org/gnome/shell/ui/viewSelector.js:293:9
_updateWorkspacesGeometry@resource:///org/gnome/shell/ui/overviewControls.js:458:9
vfunc_allocate@resource:///org/gnome/shell/ui/overviewControls.js:391:9
_updateWorkspacesViews@resource:///org/gnome/shell/ui/workspacesView.js:562:13
show@resource:///org/gnome/shell/ui/workspacesView.js:482:9
show@resource:///org/gnome/shell/ui/viewSelector.js:268:9
_animateVisible@resource:///org/gnome/shell/ui/overview.js:527:9
show@resource:///org/gnome/shell/ui/overview.js:513:9
toggle@resource:///org/gnome/shell/ui/overview.js:636:13
_toggleOverview@resource:///org/gnome/shell/ui/layout.js:1234:13
_emit@resource:///org/gnome/gjs/modules/signals.js:142:27
_trigger@resource:///org/gnome/shell/ui/layout.js:1365:9
_onBarrierHit@resource:///org/gnome/shell/ui/layout.js:1407:13
```
Arch Linux
GNOME Shell 3.32.0
gjs 1.56.0https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1066Crash when resuming from sleep2019-03-18T18:27:07ZTim SummererCrash when resuming from sleepI just updated my Arch Linux install on my ThinkPad T450 to gnome-shell build `1:3.32.0+15+gb7d79a5f0-1` from the Arch repositories.
When I close the lid of my laptop the computer goes to sleep normally. However, when I open the lid I s...I just updated my Arch Linux install on my ThinkPad T450 to gnome-shell build `1:3.32.0+15+gb7d79a5f0-1` from the Arch repositories.
When I close the lid of my laptop the computer goes to sleep normally. However, when I open the lid I see a black screen for roughly 10-15 seconds until I am greeted by GDM where I have to login to a new session.
The old session is completely lost.
Of course, I disabled all extensions and the issue still persists. I attached the stacktrace from journalctl if it helps.
Maybe it's an issue with `libglib-2`, just recently there was [this](https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/432) issue with gnome-control-center and glib2. But I could be totally wrong.
Any help would be greatly appreciated.[stacktrace.txt](/uploads/0dbda357349eeef8df9d3f14d30be03f/stacktrace.txt)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1067Running app indicators are hard to see on certain wallpapers2022-11-16T13:32:52ZAlice MikhaylenkoRunning app indicators are hard to see on certain wallpapersSuch as the default 3.32 one in the day:
![Screenshot_from_2019-03-16_12-01-45](/uploads/cdc441453fba6bcad44a35d1b3958390/Screenshot_from_2019-03-16_12-01-45.png)
Calculator is actually running hereSuch as the default 3.32 one in the day:
![Screenshot_from_2019-03-16_12-01-45](/uploads/cdc441453fba6bcad44a35d1b3958390/Screenshot_from_2019-03-16_12-01-45.png)
Calculator is actually running herehttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1069GNOME Shell v.32 breaks extensions API with legacy GJS Lang module2019-03-21T17:28:53ZkonkorGNOME Shell v.32 breaks extensions API with legacy GJS Lang module# System information #
Ubuntu 19.04, Arch Linux GNOME Shell 3.32
# Bug information #
## Steps to reproduce ##
- Install some extension which using inheriting of "pure" JS GNOME Shell classes like popupMenu.PopupBaseMenuItem to an exampl...# System information #
Ubuntu 19.04, Arch Linux GNOME Shell 3.32
# Bug information #
## Steps to reproduce ##
- Install some extension which using inheriting of "pure" JS GNOME Shell classes like popupMenu.PopupBaseMenuItem to an example.
- You will get an JS exception.
## Current behaviour ##
Messages in the system journal (`sudo journalctl`):
```sh
mars 16 09:24:02 user gnome-shell[7372]: Extension "uuid@extension" had error: TypeError: this._construct is not a function
```
## Possible solution ##
I have noticed that inheriting from GNOME Shell classes based on St.Widgets which are based on GObject don't break extension's API and work well. [See panelMenu.`ButtonBox` etc](https://gitlab.gnome.org/GNOME/gnome-shell/blob/master/js/ui/panelMenu.js#L10)
So you should inherit all GNOME Shell classes from GObject or GObject based classes and will work fine. For an example for the popupMenu.PopupBaseMenuItem class it should be something like this:
```js
var PopupBaseMenuItem = GObject.registerClass({
Signals: {
'activate': {},
'sensitive-changed': {},
'active-changed': {param_types: [GObject.TYPE_BOOLEAN]}
},
}, class PopupBaseMenuItem extends GObject {
_init(params) {
super._init({});
params = Params.parse (params, { reactive: true,
activate: true,
hover: true,
style_class: null,
can_focus: true
});
this.actor = new St.BoxLayout({ style_class: 'popup-menu-item',
reactive: params.reactive,
track_hover: params.reactive,
can_focus: params.can_focus,
accessible_role: Atk.Role.MENU_ITEM });
this.actor._delegate = this;
...
}
...
}
```
Or even inherit it from already GObject `St.BoxLayout` class
It would be really helpful to support extensions for different Shell versions.
Thanks!https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1070gnome-shell crashed with SIGABRT2019-03-17T00:19:43ZEl Jinete Sin Cabezagnome-shell crashed with SIGABRTOpen bug in launchpad.net https://bugs.launchpad.net/bugs/1820331
Package: gnome-shell 3.32.0-1ubuntu1
"In the last few weeks, gnome-shell has been crashing almost every time I open my laptop to wake it from suspend. The rapid pace of ...Open bug in launchpad.net https://bugs.launchpad.net/bugs/1820331
Package: gnome-shell 3.32.0-1ubuntu1
"In the last few weeks, gnome-shell has been crashing almost every time I open my laptop to wake it from suspend. The rapid pace of package updates has stopped Apport from letting me report it until now, but the problem persists."
BackTrace:
```
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 93891631369213, 93891633677856, 140120981703840, 93891631369356, 2064, 129, 140120981703744, 18446744073709551536, 0, 2048, 140120980338365, 551368720384, 140120981703840, 127, 343597383837}}
pid = <optimized out>
tid = <optimized out>
ret = <optimized out>
#1 0x00007f70753b1535 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x7f707615181b, sa_sigaction = 0x7f707615181b}, sa_mask = {__val = {11626575254519809, 0, 153, 93891595584784, 13633401375222288896, 75, 140120994158619, 140120994180365, 140121982631936, 93891595584784, 0, 0, 13633401375222288896, 140120982913880, 93891595584784, 154}}, sa_flags = 1981595136, sa_restorer = 0x7ffc6c54b570}
sigs = {__val = {32, 0 <repeats 15 times>}}
#2 0x00007f70760c7dc3 in g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7f7075698490 <__FUNCTION__.106414> "meta_gpu_kms_flip_crtc", message=<optimized out>) at ../../../glib/gtestutils.c:2878
lstr = "276\000\374\177\000\000\000RrbQ\222\063\275P\316!`p\177\000\000\240\203iup\177\000"
s = 0x5564d733c510 ""
#3 0x00007f7076122bfa in g_assertion_message_expr (domain=domain@entry=0x7f707568285f "mutter", file=file@entry=0x7f7075698358 "../src/backends/native/meta-gpu-kms.c", line=line@entry=276, func=func@entry=0x7f7075698490 <__FUNCTION__.106414> "meta_gpu_kms_flip_crtc", expr=expr@entry=0x7f70756983a0 "monitor_manager->power_save_mode == META_POWER_SAVE_ON") at ../../../glib/gtestutils.c:2904
s = 0x5564d9456320 "assertion failed: (monitor_manager->power_save_mode == META_POWER_SAVE_ON)"
#4 0x00007f707566da16 in meta_gpu_kms_flip_crtc (gpu_kms=gpu_kms@entry=0x5564d6c7ade0, crtc=crtc@entry=0x5564d6edceb0, fb_id=117, flip_closure=0x5564d7ecfa40, error=error@entry=0x7ffc6c54b680) at ../src/backends/native/meta-gpu-kms.c:276
gpu = 0x5564d6c7ade0
monitor_manager = <optimized out>
closure_container = <optimized out>
kms_fd = 11
connectors = 0x5564d70112d0
n_connectors = 3174273617
ret = -1
__FUNCTION__ = "meta_gpu_kms_flip_crtc"
#5 0x00007f70756727e7 in retry_page_flips (user_data=0x5564d9e25db0) at ../src/backends/native/meta-renderer-native.c:1576
crtc = 0x5564d6edceb0
l_next = 0x0
retry_page_flip_data = 0x5564d8b26fb0
gpu_kms = 0x5564d6c7ade0
error = 0x0
did_flip = <optimized out>
onscreen_native = <optimized out>
now_us = 11852199802
l = 0x5564d754eb80
#6 0x00007f70760fa958 in g_main_dispatch (context=0x5564d6c69e80) at ../../../glib/gmain.c:3189
dispatch = 0x7f7075671e90 <retry_page_flips_source_dispatch>
prev_source = 0x0
was_in_call = 0
user_data = 0x5564d9e25db0
callback = 0x7f7075672690 <retry_page_flips>
cb_funcs = <optimized out>
cb_data = 0x5564d91e63f0
need_destroy = <optimized out>
source = 0x5564d8f9e1a0
current = 0x5564d6c83a70
i = 0
current = <optimized out>
i = <optimized out>
__FUNCTION__ = "g_main_dispatch"
source = <optimized out>
_g_boolean_var_ = <optimized out>
was_in_call = <optimized out>
user_data = <optimized out>
callback = <optimized out>
cb_funcs = <optimized out>
cb_data = <optimized out>
need_destroy = <optimized out>
dispatch = <optimized out>
prev_source = <optimized out>
_g_boolean_var_ = <optimized out>
#7 g_main_context_dispatch (context=context@entry=0x5564d6c69e80) at ../../../glib/gmain.c:3854
No locals.
#8 0x00007f70760fad48 in g_main_context_iterate (context=0x5564d6c69e80, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:3927
max_priority = 0
timeout = 0
some_ready = 1
nfds = <optimized out>
allocated_nfds = 17
fds = 0x5564d7e36480
#9 0x00007f70760fb042 in g_main_loop_run (loop=0x5564d6f93a70) at ../../../glib/gmain.c:4123
self = <optimized out>
__FUNCTION__ = "g_main_loop_run"
#10 0x00007f707560d50c in meta_run () at ../src/core/main.c:683
No locals.
#11 0x00005564d50c8847 in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:583
ctx = <optimized out>
error = 0x0
shell_debug = <optimized out>
debug_flags_string = 0x5564d6f7aa60 "/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-gif.so"
ecode = <optimized out>
```https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1071gnome-shell dumps core and takes down entire GNOME Wayland session when tryin...2019-03-17T02:29:47ZMateus Rodrigues Costamateusrodcosta@gmail.comgnome-shell dumps core and takes down entire GNOME Wayland session when trying to unlockHi, so today I had this issue where I locked my computer, went away for a while and, when I got back and tried to unlock, my session got basically taken down. According to the journal logs it was due to gnome-shell dumping core.
After c...Hi, so today I had this issue where I locked my computer, went away for a while and, when I got back and tried to unlock, my session got basically taken down. According to the journal logs it was due to gnome-shell dumping core.
After compiling glib2 and gnome-shell with debug symbols I got the following backtrace:
```
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007f0faf9c9d7f in raise () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7f0fa7022100 (LWP 8582))]
(gdb) bt
#0 0x00007f0faf9c9d7f in raise () at /usr/lib/libc.so.6
#1 0x000055b7406fc912 in dump_gjs_stack_on_signal_handler (signo=6) at ../gnome-shell/src/main.c:343
#2 0x00007f0faf9c9e00 in <signal handler called> () at /usr/lib/libc.so.6
#3 0x00007f0faf9c9d7f in raise () at /usr/lib/libc.so.6
#4 0x00007f0faf9b4672 in abort () at /usr/lib/libc.so.6
#5 0x00007f0faf427042 in g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7f0fae989fd0 "meta_gpu_kms_flip_crtc", message=<optimized out>)
at ../glib/glib/gtestutils.c:2878
#6 0x00007f0faf454b9c in g_assertion_message_expr
(domain=0x7f0fae99b8d2 "mutter", file=0x7f0fae987d40 "../mutter/src/backends/native/meta-gpu-kms.c", line=276, func=0x7f0fae989fd0 "meta_gpu_kms_flip_crtc", expr=<optimized out>)
at ../glib/glib/gtestutils.c:2904
#7 0x00007f0fae8caf97 in () at /usr/lib/libmutter-4.so.0
#8 0x00007f0fae8bdb0a in () at /usr/lib/libmutter-4.so.0
#9 0x00007f0faf477661 in g_main_dispatch (context=0x55b740b01ca0) at ../glib/glib/gmain.c:3189
#10 0x00007f0faf477661 in g_main_context_dispatch (context=context@entry=0x55b740b01ca0) at ../glib/glib/gmain.c:3854
#11 0x00007f0faf479739 in g_main_context_iterate (context=0x55b740b01ca0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:3927
#12 0x00007f0faf47a6d2 in g_main_loop_run (loop=0x55b740e4cc20) at ../glib/glib/gmain.c:4123
#13 0x00007f0fae931b8c in meta_run () at /usr/lib/libmutter-4.so.0
#14 0x000055b7406fc3ab in main (argc=<optimized out>, argv=<optimized out>) at ../gnome-shell/src/main.c:499
(gdb) quit
```
OS: Arch Linux 64-bits
gnome-shell `1:3.32.0+15+gb7d79a5f0-1`
glib2 `2.60.0-1`
mutter `3.32.0+15+gc96cf0608-1`
I tried to compile mutter with debug symbols but was unable to, so only gnome-shell and glib2 have them.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1072Application menu is shown regardless of setting in Gnome Tweaks2019-06-14T11:08:48ZMaxXorApplication menu is shown regardless of setting in Gnome Tweakshttps://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1073Activities broken2019-03-18T15:02:18ZF BActivities brokenWhen entering the activities overview the application that had been focused before overlaps the other applications.
There is also no grid that the applications are positioned at like in 3.30, which means they are stacked on top of anothe...When entering the activities overview the application that had been focused before overlaps the other applications.
There is also no grid that the applications are positioned at like in 3.30, which means they are stacked on top of another.
The scaling is not working for some applications, which means that they fill way too much space.
As a result I cannot switch to an application that is in the background and sometimes I cannot switch to another desktop because there is an application on top blocking the desktop chooser on the right side.
I'm running gnome-shell 3.32.0 (arch linux package version 3.32.0-1).
It happens in wayland and X11.
Extensions:
* Drop down terminal
* Kstatusnotifieritem/appindicator support
* Windownavigator
![Screenshot_from_2019-03-17_23-11-55](/uploads/9e1d5977a39830b94803014df30c3612/Screenshot_from_2019-03-17_23-11-55.png)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1074Gnome-shell crashes (dumps core) on startup2019-03-22T09:53:54ZGhost UserGnome-shell crashes (dumps core) on startup[journalctl-xe.out](/uploads/a13615fc23312a0a175b120c6b7ab948/journalctl-xe.out)
This is in issue on my machine with all the 3.32 builds I tried. I'm not sure what the SHA of the first one is, but the latest two are b7d79a5f0 and 1341d...[journalctl-xe.out](/uploads/a13615fc23312a0a175b120c6b7ab948/journalctl-xe.out)
This is in issue on my machine with all the 3.32 builds I tried. I'm not sure what the SHA of the first one is, but the latest two are b7d79a5f0 and 1341d5557).
My system is arch linux. I start X and my gnome-session from the console with startx.
I set `export GDK_BACKEND=x11` in my `.xinitrx` before trying to start gnome.
[xinitrc.txt](/uploads/952a3e13090a2a616681ec471b823a6d/xinitrc.txt)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/10753.32.0: Busy spinner cursor stays forever.2019-03-18T17:40:31ZDaniel van Vugtdaniel.van.vugt@canonical.com3.32.0: Busy spinner cursor stays forever.Busy spinner cursor stays forever. Verified in gnome-shell 3.32.0-1ubuntu1 and mutter 3.32.0-1.
1. Log into a Wayland session.
2. Double-click a text file to open it in gedit.
3. Move the cursor out of the gedit window.
Downstream bug:...Busy spinner cursor stays forever. Verified in gnome-shell 3.32.0-1ubuntu1 and mutter 3.32.0-1.
1. Log into a Wayland session.
2. Double-click a text file to open it in gedit.
3. Move the cursor out of the gedit window.
Downstream bug: https://bugs.launchpad.net/bugs/1820542https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1076Official extension API?2019-03-18T17:29:22ZKhảiOfficial extension API?Consider that extensions break with 2 recent update (3.28 → 3.30 and 3.30 → 3.32), I think an official extension API is necessary.
It would also allow extensions to support multiple distribution since no two distributions share the same...Consider that extensions break with 2 recent update (3.28 → 3.30 and 3.30 → 3.32), I think an official extension API is necessary.
It would also allow extensions to support multiple distribution since no two distributions share the same gnome version.
Related:
* https://gitlab.gnome.org/GNOME/gnome-shell-extensions/issues/142
* https://gitlab.gnome.org/GNOME/gnome-shell/issues/1069https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1077Notification dot suddenly envelop symbol2019-03-21T10:11:01ZFlatronEZNotification dot suddenly envelop symbolAfter switching to KDE and back to Gnome on Ubuntu 18.04 LTS the notification dot suddenly turned into an envelop symbol:
![gnomeshell_notification_dot](/uploads/9c8cfb35ad8aca1598f407bd858c413a/gnomeshell_notification_dot.png)
```
GNO...After switching to KDE and back to Gnome on Ubuntu 18.04 LTS the notification dot suddenly turned into an envelop symbol:
![gnomeshell_notification_dot](/uploads/9c8cfb35ad8aca1598f407bd858c413a/gnomeshell_notification_dot.png)
```
GNOME Shell 3.28.3
Linux XXXXXXXXX 4.19.0-041900-generic #201810221809 SMP Mon Oct 22 22:11:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
```
What is the reason for this / how can this be fixed (I want the old notification dot back)?https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1078Strange clip behavior for the Panel2020-10-17T10:00:39ZPapyElGringoStrange clip behavior for the PanelHello there is something I can't figured out alone.
Can someone explain me why:
`Main.panel.set_clip(0,0,48,48)`
Does clip the panel visually and also the mouse interactions. (Expected behavior) but
`Main.panel._leftBox.set_clip(0,0,...Hello there is something I can't figured out alone.
Can someone explain me why:
`Main.panel.set_clip(0,0,48,48)`
Does clip the panel visually and also the mouse interactions. (Expected behavior) but
`Main.panel._leftBox.set_clip(0,0,48,48)`
Only clip the mouse interactions but not the visual.
It's happen for every child of the panel and I can't understand why.
Im working on adding ripple effect on clickable elements and it's mandatory for me to create a clippable container in the panel.
Thanks for the support !!https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1079OSK Enter, space and backspace keys don't work when typing in Greek in Ubuntu...2023-10-11T02:49:21ZEfthimios ChaskarisOSK Enter, space and backspace keys don't work when typing in Greek in Ubuntu 19.04The enter, space and backspace keys on the Ubuntu On-screen keyboard don't work when typing in Greek. Applies for Ubuntu 19.04 and 18.10.The enter, space and backspace keys on the Ubuntu On-screen keyboard don't work when typing in Greek. Applies for Ubuntu 19.04 and 18.10.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1081No cursor upscale on 1.25 display of one-sized cursor theme2019-03-18T17:57:43ZettavoltNo cursor upscale on 1.25 display of one-sized cursor themeI'm using cursor theme that has only 32px frames. Cursor is OK when over XWayland window but is very small otherwise.
With default theme (Adwaita) I get more or less equally sized cursor because, I think, this theme provides frames up to...I'm using cursor theme that has only 32px frames. Cursor is OK when over XWayland window but is very small otherwise.
With default theme (Adwaita) I get more or less equally sized cursor because, I think, this theme provides frames up to 96px.
![small-cursor](/uploads/6fd964983ea3dc3dd38a51fff14b5cd1/small-cursor.webm)
Screencast shows how the visual size changes when cursor is moved from XWayland (Chromium) to Wayland (Gnome Disks). It's choppy because it had to encode 2400x2430 (FullHD top display * 1.25 + FullHD bottom (the one with HiDPI configured). Real perceivable movement is smooth. There are four ghosts from #1030 too. ☺
Similar problem is observed when moving from regular display to HiDPI if a Wayland surface spans both (any window or the shell itself).
Versions (Arch Linux):
gnome-shell 3.32.0+16+g1341d5557
mutter 3.32.0+15+gc96cf0608
gtk 3.24.7
Meanwhile, what frames should I add to my 32px-only theme to get a properly sized cursor?
(32px on 1.25 display = 40px real)https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1082Show tray apps in overview.2019-12-09T16:57:37ZripefigShow tray apps in overview.Gnome's removal of the "legacy" system tray doesn't solve the problem of daemon-like applications. There is an inherent need for such applications and this means there is a need for something like the system tray. Android has one, window...Gnome's removal of the "legacy" system tray doesn't solve the problem of daemon-like applications. There is an inherent need for such applications and this means there is a need for something like the system tray. Android has one, windows has one, OSX has one. These daemon-like apps are different from normal ones: they don't need to have a window open and they cannot in principle be associated with any workspace. At the same time, these apps are no background services, which run without any user interaction whatsoever.
The user needs some way to tell that these "Special" apps are running. I don't want to dig through the system manager to see that Skype is open (or "offline"), or that that a downloader is hogging bandwidth. But I also don't want them open and cluttering up the overview and dock. That's what a system tray was for.
Gnome axed the system tray a year ago and not a single app - to my knowledge - has found an alternative way of telling the user that it's running without a window, never mind communicating state and providing the options that are traditionally exposed via right-click on the system tray. People have taken to writing extensions just to reproduce the functionality of particular tray icons, which is absolutely ridiculous. Meanwhile, users are installing the appindicator extension to restore the missing functionality and Ubuntu is shipping it by default. Appindicator is just like a normal tray only worse: it lacks the ability to hide icons.
Something is clearly not working.
TL;DR. I understand not wanting tray icons to pollute the panel. This means their function has to be transferred to some other place. Currently, the "solution" is to just to break Gnome's design 100% and install appindindicator, which irrevocably pollutes the panel.
There is plenty of room in the overview. Why not just put the tray icons on the bottom in the overview? Isn't the function of the overview to show running GUI applications? If so, it must show these daemon-like applications, otherwise it's not doing its job. It's not like there is no space for them there.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1083Icon overlay option for overview.2021-02-06T13:50:01ZripefigIcon overlay option for overview.When you have more than five windows open in a single workspace, they all begin to look the same in the overview, at least to me. It particularly bad on small screens, though on large screens you have more area you need to visually scan ...When you have more than five windows open in a single workspace, they all begin to look the same in the overview, at least to me. It particularly bad on small screens, though on large screens you have more area you need to visually scan so it bad there too. I have good eyesight, to be clear.
I sometimes intentionally change the theme of individual apps just so I can more readily see them in the overview.
One could create tons of workspaces and/or close every unnecessary window but that's really more effort than it's worth, especially cause too many work-spaces just displaces the problem of finding windows.
The only way I've found to make the overview usable for me is to install the icons overlay extension. https://extensions.gnome.org/extension/60/overlay-icons/
(Note that you can change the style to a different one - the one pictured here is bad. What I found works best is to just have a very faint but large icon overlayed on window thumbnail, without any grey padding like in this screenshot. It looks very nice and doesn't obscure the window content.)
With this extension, I am able to find the windows I am looking for much faster. I hated the overview before I installed this. I suspect this is a reason why many people never get used to the overview is because they have trouble finding windows due to a lack of icons. So they just install a dock extension and give up on the default switcher. The dock also offers fixed order for pinned apps, which makes stuff memorable, so to get all the benefits of a dock, you'd ideally have to extend the concept of pinned apps to the overview, essentially making it a full-screen dock. But the icon overlay alone may be enough for most people to make the transition from docks to the overlays.
This extension is very useful and very obscure (and it might be broken with the latest release). I think many users will benefit if were shipped with gnome, or at least formally supported by Gnome.https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1084Backgrounds selected from "Pictures" become completely black after sleep (Nvi...2021-12-09T21:39:31ZAlexandr OleynikovBackgrounds selected from "Pictures" become completely black after sleep (Nvidia)**System Info:**
* Distribution: Arch Linux
* Kernel: Linux 4.19.29-1-lts (installed from linux-lts package)
* Gnome version: 3.32
* Graphics: Nvidia GTX 1070
* Driver version: Proprietary 418.43 (installed through nvidia-dkms package)
...**System Info:**
* Distribution: Arch Linux
* Kernel: Linux 4.19.29-1-lts (installed from linux-lts package)
* Gnome version: 3.32
* Graphics: Nvidia GTX 1070
* Driver version: Proprietary 418.43 (installed through nvidia-dkms package)
How to reproduce:
1. Select a background from "Pictures" tab and set it as main background (in my case, I used this png image: https://yadi.sk/i/rrcsStEXdzQEpw)
2. Press sleep button on your device or enter sleep through Gnome's menu.
3. Wake the computer up
As a result, the background becomes completely black and remains that way until I log out or reboot (even if I change to a different picture and change it back in the settings).
This did not occur in Gnome 3.30.