[Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "co

2020-04-17 Thread Fabio B
Ubuntu 19.10, mutter-3.34.3-1ubuntu1~19.10.1 and still crash sometimes
with IntelliJ

--
apr 17 16:40:45 delphy gnome-shell[2612]: **
apr 17 16:40:45 delphy gnome-shell[2612]: 
mutter:ERROR:../src/core/window.c:4851:set_workspace_state: 'workspace' should 
be NULL
apr 17 16:40:45 delphy gnome-shell[2612]: Bail out! 
mutter:ERROR:../src/core/window.c:4851:set_workspace_state: 'workspace' should 
be NULL
apr 17 16:40:45 delphy gnome-shell[2612]: GNOME Shell crashed with signal 6
apr 17 16:40:45 delphy gnome-shell[2612]: == Stack trace for context 
0x56084b40d3b0 ==
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 1.
apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME X11 Session 
(session: ubuntu).
apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME X11 Session (session: 
ubuntu).
apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME X11 Session.
apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME X11 Session.
apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME Shell on X11.
apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME Shell on X11.
apr 17 16:40:45 delphy systemd[2342]: Stopped GNOME Shell on X11.
apr 17 16:40:45 delphy systemd[2342]: Starting GNOME Shell on X11...

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1845281

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  meta_window_get_workspaces() [assertion failure "code should not be
  reached"]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "co

2020-02-25 Thread Fabio B
I recently reported the issue to jetbrains  
https://youtrack.jetbrains.com/issue/IDEA-233737
(with a screencast)

All packages: mutter, mutter-common, gir1.2-mutter-5 and libmutter-5-50
are at version 3.34.1+git20191107-1ubuntu1~19.10.1


journalctl log 
---
feb 25 12:20:29 delphy gnome-shell[9183]: **
feb 25 12:20:29 delphy gnome-shell[9183]: 
mutter:ERROR:../src/core/window.c:5513:meta_window_get_workspaces: code should 
not be reached
feb 25 12:20:29 delphy gnome-shell[9183]: Bail out! 
mutter:ERROR:../src/core/window.c:5513:meta_window_get_workspaces: code should 
not be reached
feb 25 12:20:29 delphy gnome-shell[9183]: == Stack trace for context 
0x55de5b4f1540 ==
feb 25 12:20:29 delphy gnome-shell[9183]: GNOME Shell crashed with signal 6
feb 25 12:20:29 delphy gnome-shell[9183]: == Stack trace for context 
0x55de5b4f1540 ==


Also attached the gdb.txt file produced with these instructions
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#Obtaining_a_stack_and_JS_trace_using_GDB_for_an_already_running_gnome-shell

Hope it helps


** Attachment added: "gdb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845281/+attachment/5330843/+files/gdb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1845281

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  meta_window_get_workspaces() [assertion failure "code should not be
  reached"]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1845281/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'

2016-10-25 Thread Fabio B
This bug affects me as well, anyway the "recent files" works inside
modal windows while opening/selecting files

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1633162

Title:
  Files application throws an error 'Oops! Something went wrong' when
  clicked on 'Recents'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1633162/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs