← Back to team overview

budgie-remix-bug-busters team mailing list archive

[Bug 1899083] Re: budgie-panel crashed with SIGSEGV in g_type_check_instance_cast()


Going to close this - this area has been extensively rewritten.  If you
can reproduce under 22.04 then do please advise.

** Changed in: budgie-desktop (Ubuntu)
       Status: New => Invalid

You received this bug notification because you are a member of ubuntu
budgie bug busters, which is subscribed to budgie-desktop in Ubuntu.

  budgie-panel crashed with SIGSEGV in g_type_check_instance_cast()

Status in budgie-desktop package in Ubuntu:

Bug description:
  dont know

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: budgie-core 10.5.1+git20200824-2
  ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13
  Uname: Linux 5.8.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Thu Oct  8 23:10:31 2020
  ExecutablePath: /usr/bin/budgie-panel
  InstallationDate: Installed on 2020-10-08 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201006)
  ProcCmdline: budgie-panel --replace &
   Segfault happened at: 0x7fac6d152cd0 <g_type_check_instance_cast+64>:	movzbl 0x16(%rdi),%eax
   PC (0x7fac6d152cd0) ok
   source "0x16(%rdi)" (0x3948c031fa1e1006) not located in a known VMA region (needed readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: budgie-desktop
   g_type_check_instance_cast () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libwnck-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: budgie-panel crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to: