Bug#899004: gnome-shell: crash on attempt to lock

2018-06-01 Thread Josep M. Perez

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



Bug#899004: gnome-shell: crash on attempt to lock

2018-05-22 Thread Simon McVittie
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



Bug#899004: gnome-shell: crash on attempt to lock

2018-05-22 Thread Josep M. Perez

Hi,

Sorry for the late response.

On 18/05/18 20:15, Simon McVittie wrote:

Control: tags -1 + moreinfo

On Fri, 18 May 2018 at 15:21:57 +0200, Josep M. Perez wrote:

gnome-shell crashes when I press meta+L to lock the session. After the third
failed attempt, it crashes and also suspends the computer.

How reproducible is this? If you reboot your computer and try repeatedly
locking your screen, does the same thing happen again?
Yes, it happens even if I reboot. This started happening when I went 
from 2.26 to 2.28. Since the crash is related to JS, I started to 
disable extensions. 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.


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. 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.


Since activating and deactivating extensions makes the problem go away, 
I will keep you posted about whether this is finally stable.



Is there anything that looks relevant in the systemd journal or syslog
at around the time of the crash?

Not really. It only happens when I attempt to lock the screen.

Did you previously run a version of gnome-shell that did not have this bug?
If you did, what packages did you upgrade around the time it started
happening? (/var/log/apt/history.log* might be useful)

Do you have any GNOME Shell extensions enabled?

I notice that the backtrace you provided involves libnm, the NetworkManager
client library. Is there anything unusual about your networking that might
explain why you see this crash when other people don't?
I have an ethernet connection, a wifi connection and an OpenVPN bridge 
using the tap interface.

I uploaded new versions of gnome-shell, mutter and gjs earlier today
(gnome-shell 3.28.2, mutter 3.28.2 and gjs 1.52.3-2). Please could you
try with those when they become available, and report back with whether
this bug is still visible in those versions?

Yes. The list of versions are:

ii  chrome-gnome-shell 10-1    
all  GNOME Shell extensions integration for web browsers
ii  gnome-shell 3.28.2-1    amd64    
graphical shell for the GNOME desktop
ii  gnome-shell-common 3.28.2-1    
all  common files for the GNOME graphical shell
ii  gnome-shell-dbgsym 3.28.2-1    
amd64    debug symbols for gnome-shell
ii  gnome-shell-extension-appindicator 
22-1    all 
AppIndicator/KStatusNotifierItem support for GNOME Shell
ii  gnome-shell-extension-autohidetopbar 
20171126-2  all  GNOME shell 
automatic topbar hider
ii  gnome-shell-extension-dash-to-panel 
13-1    all  combines the dash 
and the GNOME main panel into a single panel
ii  gnome-shell-extension-dashtodock 
63-1    all  dash-to-dock 
extension for GNOME shell
ii  gnome-shell-extension-disconnect-wifi 
17-2    all  disconnect wifi 
extension for GNOME shell
ii  gnome-shell-extension-hide-activities 
0.00~git20131024.1.6574986-1    all  GNOME shell 
extension that hides the activities button
ii  gnome-shell-extension-impatience 
0.4.5-3 all  speed up the 
gnome-shell animation speed
ii  gnome-shell-extension-move-clock 
1.01-1  all  move clock 
extension for GNOME shell
ii  gnome-shell-extension-multi-monitors 
0.00~git20171014.1.df5d6e4-1    all  Better support for 
additional monitors in GNOME shell
ii  gnome-shell-extension-pixelsaver 
1.10+git20161217-49f47bf-1  all  pixel saver 
extension for GNOME shell
ii  gnome-shell-extension-redshift 
3.20.1-2    all  redshift extension 
for GNOME Shell
ii  gnome-shell-extension-remove-dropdown-arrows 
9-1 all  removes drop down 
arrows from panel on GNOME shell
ii  gnome-shell-extension-shortcuts 
1.1.1-1 all  Creates a shortcuts 
help pop-up in GNOME Shell
ii  gnome-shell-extension-show-ip 
8-3 all  Shows the current 
private or public IP address
ii  gnome-shell-extension-suspend-button 
0~git20171025-2 all  Gnome-shell 
extension to modify the suspend/shutdown buttons
ii  gnome-shell-extension-system-monitor 
35-1    all  

Processed: Re: Bug#899004: gnome-shell: crash on attempt to lock

2018-05-18 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo
Bug #899004 [gnome-shell] gnome-shell: crash on attempt to lock
Added tag(s) moreinfo.

-- 
899004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#899004: gnome-shell: crash on attempt to lock

2018-05-18 Thread Simon McVittie
Control: tags -1 + moreinfo

On Fri, 18 May 2018 at 15:21:57 +0200, Josep M. Perez wrote:
> gnome-shell crashes when I press meta+L to lock the session. After the third
> failed attempt, it crashes and also suspends the computer.

How reproducible is this? If you reboot your computer and try repeatedly
locking your screen, does the same thing happen again?

Is there anything that looks relevant in the systemd journal or syslog
at around the time of the crash?

Did you previously run a version of gnome-shell that did not have this bug?
If you did, what packages did you upgrade around the time it started
happening? (/var/log/apt/history.log* might be useful)

Do you have any GNOME Shell extensions enabled?

I notice that the backtrace you provided involves libnm, the NetworkManager
client library. Is there anything unusual about your networking that might
explain why you see this crash when other people don't?

I uploaded new versions of gnome-shell, mutter and gjs earlier today
(gnome-shell 3.28.2, mutter 3.28.2 and gjs 1.52.3-2). Please could you
try with those when they become available, and report back with whether
this bug is still visible in those versions?

Thanks,
smcv



Bug#899004: gnome-shell: crash on attempt to lock

2018-05-18 Thread Josep M. Perez
Package: gnome-shell
Version: 3.28.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

gnome-shell crashes when I press meta+L to lock the session. After the third
failed attempt, it crashes and also suspends the computer.

A backtrace follows:

#0  0x770c14f4 in g_hash_table_iter_init
(iter=iter@entry=0x7ffef010, hash_table=0x10004) at
../../../../glib/ghash.c:769
#1  0x72909042 in nm_ip_address_dup (address=) at libnm-
core/nm-setting-ip-config.c:388
#2  0x773aaecb in g_boxed_copy (boxed_type=93825030200288,
src_boxed=src_boxed@entry=0x563791e0) at ../../../../gobject/gboxed.c:343
#3  0x7609f540 in gjs_boxed_from_c_struct(JSContext*, GIStructInfo*,
void*, GjsBoxedCreationFlags) (context=context@entry=0x55dd7a00,
info=info@entry=0x57aec540, gboxed=0x563791e0, flags=)
at gi/boxed.cpp:1235
#4  0x7609b194 in gjs_value_from_g_argument(JSContext*,
JS::MutableHandleValue, GITypeInfo*, GArgument*, bool)
(context=context@entry=0x55dd7a00, value_p=...,
type_info=type_info@entry=0x58331ca0, arg=arg@entry=0x7ffef4b8,
copy_structs=copy_structs@entry=true) at gi/arg.cpp:2909
#5  0x7609bf33 in gjs_array_from_carray_internal(JSContext*,
JS::MutableHandleValue, GITypeInfo*, guint, gpointer)
(context=context@entry=0x55dd7a00, value_p=..., value_p@entry=...,
param_info=param_info@entry=0x58331ca0, length=1, array=) at
gi/arg.cpp:2346
#6  0x7609a446 in gjs_array_from_boxed_array (arg=0x7ffef998,
param_info=0x58331ca0, array_type=, value_p=...,
context=0x55dd7a00) at gi/arg.cpp:2462
#7  0x7609a446 in gjs_value_from_g_argument(JSContext*,
JS::MutableHandleValue, GITypeInfo*, GArgument*, bool)
(context=context@entry=0x55dd7a00, value_p=...,
type_info=type_info@entry=0x7ffef9c0, arg=arg@entry=0x7ffef998,
copy_structs=copy_structs@entry=true) at gi/arg.cpp:3012
#8  0x760a677e in gjs_invoke_c_function(JSContext*, Function*,
JS::HandleObject, JS::HandleValueArray const&,
mozilla::Maybe, GIArgument*)
(context=context@entry=0x55dd7a00, function=function@entry=0x576f0b00,
obj=...,
obj@entry=..., args=..., js_rval=..., r_value=r_value@entry=0x0) at
gi/function.cpp:1147
#9  0x760a6a24 in function_call(JSContext*, unsigned int, JS::Value*)
(context=context@entry=0x55dd7a00, js_argc=0, vp=0x55f14d50)
at gi/function.cpp:1406
#10 0x7fffed039fdc in js::CallJSNative(JSContext*, bool (*)(JSContext*,
unsigned int, JS::Value*), JS::CallArgs const&) (args=...,
native=0x760a68c0 ,
cx=0x55dd7a00) at ./js/src/jscntxtinlines.h:239
#11 0x7fffed039fdc in js::InternalCallOrConstruct(JSContext*, JS::CallArgs
const&, js::MaybeConstruct) (cx=0x55dd7a00, args=...,
construct=js::NO_CONSTRUCT) at ./js/src/vm/Interpreter.cpp:447
#12 0x7fffed02d087 in js::CallFromStack(JSContext*, JS::CallArgs const&)
(args=..., cx=) at ./js/src/vm/Interpreter.cpp:510
#13 0x7fffed02d087 in Interpret(JSContext*, js::RunState&)
(cx=0x55dd7a00, state=...) at ./js/src/vm/Interpreter.cpp:2922
#14 0x7fffed039846 in js::RunScript(JSContext*, js::RunState&)
(cx=cx@entry=0x55dd7a00, state=...) at ./js/src/vm/Interpreter.cpp:405
#15 0x7fffed039e1f in js::InternalCallOrConstruct(JSContext*, JS::CallArgs
const&, js::MaybeConstruct) (cx=cx@entry=0x55dd7a00, args=...,
construct=construct@entry=js::NO_CONSTRUCT) at ./js/src/vm/Interpreter.cpp:477
#16 0x7fffed03a099 in InternalCall(JSContext*, js::AnyInvokeArgs const&)
(cx=cx@entry=0x55dd7a00, args=...) at ./js/src/vm/Interpreter.cpp:504
#17 0x7fffed03a0f9 in js::Call(JSContext*, JS::Handle,
JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle)
(cx=cx@entry=0x55dd7a00, fval=..., fval@entry=..., thisv=...,
thisv@entry=..., args=..., rval=rval@entry=...) at
./js/src/vm/Interpreter.cpp:523
#18 0x7fffece2c079 in js::jit::InvokeFunction(JSContext*,
JS::Handle, bool, unsigned int, JS::Value*,
JS::MutableHandle) (cx=0x55dd7a00, obj=...,
constructing=, argc=, argv=0x7fff06c0,
rval=...) at ./js/src/jit/VMFunctions.cpp:114
#19 0x35b97b5083c6 in  ()
#20 0x7fff0780 in  ()
#21 0x7fff0670 in  ()
#22 0xfff9 in  ()
#23 0x7fffee1dc040 in js::jit::InvokeFunctionInfo () at
/usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#24 0x7fffc05739a0 in  ()
#25 0x35b97b59f89b in  ()
#26 0x7820 in  ()
#27 0x7fffa999c700 in  ()
---Type  to continue, or q  to quit---
#28 0x in  ()

(gdb) info sharedlibrary
>FromTo  Syms Read   Shared Object Library
0x779a8c40  0x779c22de  Yes /usr/lib/gnome-
shell/libgnome-shell.so
0x776290a0  0x7770b162  Yes /usr/lib/x86_64-linux-
gnu/libgio-2.0.so.0
0x773a7f10  0x773d9b3e  Yes /usr/lib/x86_64-linux-