← Back to team overview

budgie-remix-bug-busters team mailing list archive

[Bug 1719911] Re: budgie-panel crashed with SIGABRT in g_assertion_message()


[Expired for budgie-desktop (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: budgie-desktop (Ubuntu)
       Status: Incomplete => Expired

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 SIGABRT in g_assertion_message()

Status in budgie-desktop package in Ubuntu:

Bug description:
  Using budgie's regulation tools and making a lot of mistakes, i try to
  adjust icons position on the top taskbar on budgie panel. It's a work
  that i can do by myself, i hope so, but i am not sure. I am learning
  and i like this. If you can & want help me, you're welcome. Thanks
  friends, the best for you

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: budgie-core 10.4-1ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 27 16:56:02 2017
  ExecutablePath: /usr/bin/budgie-panel
  InstallationDate: Installed on 2017-05-27 (123 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  ProcCmdline: budgie-panel
   PATH=(custom, user)
  Signal: 6
  SourcePackage: budgie-desktop
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_weak_ref_set () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_weak_ref_clear () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: budgie-panel crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to: