The bug hasn't seen any activity in years and there has been no recent
similar reports, the code also changed quite a lot since and it's likely
the issue doesn't exist anymore. Closing, feel free to open a new report
if you still get problems in recent Ubuntu versions

** Changed in: gnome-control-center (Ubuntu)
       Status: Confirmed => Invalid

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.

  [sound]: gnome-control-center crashed with SIGSEGV in _int_malloc()

Status in gnome-control-center package in Ubuntu:

Bug description:
  Crashed while I was changing the systems sounds (bark, drop, etc.).
  Froze before crashing.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Sep 17 20:32:02 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
  ProcCmdline: gnome-control-center sound
   PATH=(custom, no user)
   Segfault happened at: 0x7fc33d314c5f:        mov    0x10(%r14),%r8
   PC (0x7fc33d314c5f) ok
   source "0x10(%r14)" (0x53555f6e75) not located in a known VMA region (needed 
readable region)!
   destination "%r8" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
   ?? () from /lib/x86_64-linux-gnu/
   malloc () from /lib/x86_64-linux-gnu/
   g_malloc () from /lib/x86_64-linux-gnu/
   g_strdup () from /lib/x86_64-linux-gnu/
   g_strdupv () from /lib/x86_64-linux-gnu/
  Title: [sound]: gnome-control-center crashed with SIGSEGV in malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
   deja-dup                    23.90-0ubuntu1
   gnome-control-center-signon 0.0.15-0ubuntu2
   indicator-datetime          12.10.0-0ubuntu2

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to