Hi,

Since the last update I have locked and unlocked my session several times, and rebooted three times and I haven't had any more problems. The current set of enabled-extensions is: ['ubuntu-appindicat...@ubuntu.com', 'gpa...@gnome-shell-extensions.gnome.org', 'drive-m...@gnome-shell-extensions.gcampax.github.com'].

So, from my side this bug can be closed. Thanks for your help!

Cheers,

Josep M. Perez



On 22/05/18 12:04, Simon McVittie wrote:
On Tue, 22 May 2018 at 11:18:04 +0200, Josep M. Perez wrote:
So, I opened dconf-editor and saw that for some reason
/org/gnome/shell/disable-extension-version-validation was active, and that
was the default value.
That is correct. By default extensions don't need to declare compatibility
with specific GNOME Shell versions since 3.21.92 (in earlier versions, the
Shell interfaces that extensions use changed more frequently).

If that option had any effect, it would be to disable some of your
extensions. Extensions that say they are compatible with Shell 3.28 should
never be affected by it. gpaste and "removable drive menu" seem to both
be from packages that are updated in sync with the rest of GNOME 3.28,
so I would expect that they declare compatibility with Shell 3.28 and are
unaffected by extension version validation.

Last week, it seemed that disabling the "gpaste" extension solved it. However,
today I updated, rebooted, and it seems that now that it still happens until I
disable the "removable drive menu" extension.
...
I have set it to false, emptied the contents of
/org/gnome/shell/enabled-extensions, and enabled only gpaste and "removable
drive menu" through the "tweaks" application. After this, I can lock the
screen with no trouble.
That sounds like it might be an intermittent bug that doesn't necessarily
depend on the enabled state of those extensions, unfortunately.

ii  gnome-shell-extensions 3.28.1-1
all          Extensions to extend functionality of GNOME Shell
FYI, this is the package containing the "removable drive menu" extension.

     smcv


http://bsc.es/disclaimer

Reply via email to