(In reply to Jura from comment #0)
> If I click on workspace in overview(see screenshot) gnome-shell segfault.

This doesn't reproduce the crash here, so you'll have to provide a proper backtrace. If you have coredumpctl enabled, you can use that to retrieve the necessary information, otherwise you can follow https://wiki.gnome.org/Projects/GnomeShell/Debugging to gather the information yourself.

(Please make sure to install debug symbols for relevant components, that is at least mutter and gnome-shell)

Created attachment 359740 [details]
gdb.log

Created attachment 359741 [details]
another log

copied from terminal

any news?

Can you open gdb the same way as before, but also type

bt full

then attach the output as a file here? It seems you uploaded just the top most frame of the backtrace, meaning we can't see where the call came from, just the actual place it crashed.

Created attachment 359872 [details]
gdb log

Any news?

Not really.

We somehow end up calling st_theme_node_paint_borders() with a paint state that has no theme node set, but it's unclear how we end up there - we should catch that case[0] and make sure the paint state's node is updated.

[0] https://git.gnome.org//browse/gnome-shell/tree/src/st/st-theme-node-drawing.c#n2516


From inspecting the code, I only found one place that looks like it could trigger this, albeit under very suspicious circumstances (we should never dispose a theme node that is still used for painting) - does the following patch help?

diff --git a/src/st/st-theme-node.c b/src/st/st-theme-node.c
index 3739b93b4..746e8e51a 100644
--- a/src/st/st-theme-node.c
+++ b/src/st/st-theme-node.c
@@ -122,6 +122,7 @@ st_theme_node_dispose (GObject *gobject)
                                           on_custom_stylesheets_changed, node);
 
   st_theme_node_paint_state_free (&node->cached_state);
+  node->cached_textures = FALSE;
 
   g_clear_object (&node->theme);

I apply patch, but problem not disappear

Created attachment 360078 [details]
gdb.log

So the widget itself is already gibberish by frame 3:

+ Trace 237989

Note how the allocation is hosed.  Do you have any extensions enabled? I wonder if an extension is destroying the label from the "paint" signal or something like that.

I remove all extensions from ~/.local/share/gnome-shell/extensions and restart gnome-shell - problem not disapper

I disable all default extensions in gnome-tweak-tool - problem not disapper

I turn off switch for all extensions(see screenshot) - problem disapper.

If I turn on this switch and all extensions disabled problem reappears.

P.S. sorry for bad english

Created attachment 360080 [details]
gnome-tweak-tool switch

can you

1) start tweak tool
2) turn on the switch, but leave all extensions disabled
3) hit alt-f2
4) type lg <enter>
5) click the "Extensions" word in the upper right corner of the console that comes down
6) hit the print-screen key and wait until the screen flashes from a screenshot being taken
7) hit the escape key
8) upload the screenshot here (should be in ~/Pictures)

also, please confirm that after step 2 the problem still happens.

Created attachment 360082 [details]
first screen

Created attachment 360083 [details]
second screen

after step 2 problem still happens.

"Выключено" - translate as disabled
"Включено" - translate as enabled

in gnome-tweak-tool all extensions diabled, but in lg some extensions enabled

thanks, so one of the enabled ones is triggering the problem i guess.

For clarity, can you post the output of

$ gsettings get org.gnome.shell enabled-extensions

too?

$ gsettings get org.gnome.shell enabled-extensions

['sound-output-device-chooser@kgshank.net', 'EasyScreenCast@iacopodeenosee.gmail.com', 'SkypeNotification@chrisss404.gmail.com', 'transmission-daemon@patapon.info', 'auto-move-windows@gnome-shell-extensions.gcampax.github.com', 'launch-new-instance@gnome-shell-extensions.gcampax.github.com', 'native-window-placement@gnome-shell-extensions.gcampax.github.com', 'screenshot-window-sizer@gnome-shell-extensions.gcampax.github.com', 'user-theme@gnome-shell-extensions.gcampax.github.com', 'windowsNavigator@gnome-shell-extensions.gcampax.github.com', 'battery-power-statistics-shortcut@l300lvl.co.nr', 'ds4battery@slie.ru', 'extension-reloader@nls1729', 'gnome-shell-imgur@ttll.de', 'caffeine@patapon.info', 'nvidiatemp@baco', 'caffeine_patapon.info', 'ds4battery_slie.ru', 'nvidiatemp_baco', 'drive-menu_gnome-shell-extensions.gcampax.github.com', 'gnome-shell-screenshot_ttll.de', 'TopIcons@phocean.net', 'gnome-shell-screenshot@ttll.de', 'topIcons@adel.gadllah@gmail.com', 'topIcons_adel.gadllah_gmail.com']


it's strange most extensions removed

Are you using a custom theme?

Created attachment 360086 [details]
gnome-tweak-tool

No. And «users themes» extensions disabled in gnome-tweak-tool

(In reply to Jura from comment #22)
> And «users themes» extensions disabled in gnome-tweak-tool

Well, according to

(In reply to Jura from comment #18)
> "Включено" - translate as enabled

and

(In reply to Jura from comment #16)
> Created attachment 360082 [details]
> first screen

the extension is enabled.

Can you:

1. Turn off all extensions (one-by-one, not with the master switch)
2. Log out & log in again
3. Try to reproduce the issue
4. Enable the extensions one-by-one until you can reproduce the issue

Created attachment 360088 [details]
gnome-tweak-tool

All extensions disabled in gnome-tweak-tool ;)
But in lg some extensions is enabled.

Is there another way to disable extensions?

https://extensions.gnome.org/local/ - works

After enable "Native Window Placement" problem still happens

Created attachment 360091 [details] [review]
nativeWindowPlacement: Adjust to overview changes

title._spacing is no longer defined, so we end up with bogus positions
when window-captions-on-top is set to true. Adjust the positioning to
do without that for now, though the whole extension could use a rewrite
to not copy everything-and-the-kitching-sink, or be killed off as yet
another extension from the original random collection that turned out
too expensive to keep dragging along ...

Patch works. Thanks. Problem disapper.

Attachment 360091 [details] pushed as 530b165 - nativeWindowPlacement: Adjust to overview changes

*** Bug 788521 has been marked as a duplicate of this bug. ***