(Here is the journalctl.txt file.)
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714989/+attachment/4985109/+files/journalctl.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I’m encountering a similar crash, this time in
"g_type_check_instance_is_fundamentally_a", and not
"g_type_check_instance_cast". Attached are the gdb.txt and
journalctl.txt files generated following the procedure given above.
This time it seems that it is coming from another extension, Pomodoro,
Here's the gdb.txt
** Attachment added: "gdb.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714989/+attachment/4984504/+files/gdb.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
And here's my journalctl
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714989/+attachment/4984515/+files/journalctl.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Using pgrep here is actually safer:
sudo gdb -p $(pgrep -U $USER -x gnome-shell) -batch \
-ex "set logging on" -ex continue \
-ex "bt full" -ex "call gjs_dumpstack()" \
-ex quit
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Ok, actually that's not needed...
Just use this:
sudo gdb -p $(pidof gnome-shell) -batch \
-ex "set logging on" -ex continue \
-ex "bt full" -ex "call gjs_dumpstack()" \
-ex quit
This could be run from your session too and should not freeze anything.
When you get a crash, just attach
Paul, you need to do that from another system via SSH or from tty3 (or any free
one), although you still might not be able to go back to the tty when frozen...
So having another system around (using byobu too) would help.
--
You received this bug notification because you are a member of Ubuntu
I attempted to run
$ sudo gdb -p 4798
twice last night and both times it just caused my system to freeze.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714989
Title:
I use dash to panel.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714989
Title:
gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
st_label_set_text()
** Changed in: gnome-shell
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714989
Title:
gnome-shell crashed with SIGSEGV in
I use dash to dock rather than dash-to-panel but am now running the
command and will try and get an output for you.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714989
Title:
So this is mostly triggered by extensions (and considering how things are done,
we can't prevent them).
Or some wrong JS code which we didn't identified yet.
Crash for users using dash-to-panel is fixed (I've proposed the fix
upstream https://github.com/jderose9/dash-to-panel/pull/263), for the
Juerg, also, if you have a core file handy (or a full /var/crash/
*.crash file), that would be helpful.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714989
Title:
Indeed these bugs might be triggered by one extension, more than vanilla
experience, but they still underline issues in the code, so it's still a
bug we've to fix.
As I said, if you happen to catch this wile running gnome-shell in gdb,
please run `call gjs_dumpstack()` from the gdb shell in order
The dash to panel extension is not present on my system (Ubuntu GNOME),
so the bug is surely not specific to that, as seen in the linked GNOME
Bugzilla report.
Here are lines from my syslog from various crashes (not adding any extra
debug information, which has been provided in previous
** Summary changed:
- gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
st_label_set_text()
+ gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
st_label_set_text() (dash-to-panel specific?)
--
You received this bug notification because you are a member
16 matches
Mail list logo
