*** This bug is a duplicate of bug 1947130 ***
    https://bugs.launchpad.net/bugs/1947130

Success! Forced the kernel to create regular core files and then added
debug symbols in the live session:

Core was generated by `gnome-shell --sm-disable --mode=ubiquity'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f2ace7dda6c in js::gc::Cell::storeBuffer (this=<optimized out>, 
this=<optimized out>) at .././js/src/gc/Cell.h:363
[Current thread is 1 (Thread 0x7f2ac912f5c0 (LWP 1795))]
(gdb) bt
#0  0x00007f2ace7dda6c in js::gc::Cell::storeBuffer (this=<optimized out>, 
this=<optimized out>) at .././js/src/gc/Cell.h:363
#1  JSObject::writeBarrierPost (next=<optimized out>, prev=<optimized out>, 
cellp=<optimized out>) at .././js/src/vm/JSObject.h:758
#2  js::InternalBarrierMethods<JSObject*>::postBarrier (next=<optimized out>, 
prev=<optimized out>, vp=0x7f2ab4029cf0) at .././js/src/gc/Barrier.h:332
#3  js::InternalBarrierMethods<JSObject*>::postBarrier (vp=0x7f2ab4029cf0, 
prev=<optimized out>, next=<optimized out>) at .././js/src/gc/Barrier.h:331
#4  0x00007f2ad064a792 in js::BarrierMethods<JSObject*>::postWriteBarrier 
(next=<optimized out>, prev=<optimized out>, vp=<optimized out>, vp=<optimized 
out>, prev=<optimized out>, next=<optimized out>) at 
/usr/include/mozjs-78/js/RootingAPI.h:772
#5  JS::Heap<JSObject*>::postWriteBarrier (next=<optimized out>, 
prev=<optimized out>, this=<optimized out>, this=<optimized out>, 
prev=<optimized out>, next=<optimized out>) at 
/usr/include/mozjs-78/js/RootingAPI.h:366
#6  JS::Heap<JSObject*>::~Heap (this=<optimized out>, this=<optimized out>) at 
/usr/include/mozjs-78/js/RootingAPI.h:328
#7  mozilla::detail::VectorImpl<JS::Heap<JSObject*>, 0ul, 
js::SystemAllocPolicy, false>::destroy (aEnd=0x7f2ab4029d00, aBegin=<optimized 
out>) at /usr/include/mozjs-78/mozilla/Vector.h:65
#8  mozilla::Vector<JS::Heap<JSObject*>, 0ul, js::SystemAllocPolicy>::~Vector 
(this=<optimized out>, this=<optimized out>) at 
/usr/include/mozjs-78/mozilla/Vector.h:889
#9  JS::GCVector<JS::Heap<JSObject*>, 0ul, js::SystemAllocPolicy>::~GCVector 
(this=<optimized out>, this=<optimized out>) at 
/usr/include/mozjs-78/js/GCVector.h:35
#10 GjsContextPrivate::~GjsContextPrivate (this=<optimized out>, 
this=<optimized out>) at ../gjs/context.cpp:467
#11 0x00007f2ad064b748 in gjs_context_finalize (object=0x55e730b0d220) at 
../gjs/context.cpp:480
#12 0x00007f2ad10d7e5d in g_object_unref () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x00007f2ad132277d in _shell_global_destroy_gjs_context (self=<optimized 
out>) at ../src/shell-global.c:703
#14 0x000055e72f365ece in main (argc=<optimized out>, argv=<optimized out>) at 
../src/main.c:659

Looks like bug 1947130.

** This bug has been marked a duplicate of bug 1947130
   gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer from 
JSObject::writeBarrierPost from js::InternalBarrierMethods from 
js::InternalBarrierMethods from js::BarrierMethods

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1962513

Title:
  gnome-shell crashed with SIGSEGV in jammy live session (gnome-shell
  --sm-disable --mode=ubiquity)

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  I was installing Jammy Jellyfish and an error popped up, It brought me to 
this so heres the info
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:      22.04
  gnome-shell:
    Installed: 41.3-1ubuntu1
    Candidate: 41.3-1ubuntu1
    Version table:
   *** 41.3-1ubuntu1 500
          500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
          100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 16 18:10:33 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C.UTF-8
   XDG_RUNTIME_DIR=<set>
  RelatedPackageVersions: mutter-common 41.3-3ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fe597633a6c:        mov    0xffff0(%rsi),%rax
   PC (0x7fe597633a6c) ok
   source "0xffff0(%rsi)" (0x14ac711ffff0) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x00007fe597633a6c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffdb417b9d0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962513/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to