Docky.exe crashed with SIGSEGV in g_type_name()

Bug #984714 reported by Carsten Lange
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
docky (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Ubuntu Precise 12.04
Docky 2.1.4-1

Crash after calling Update Manager Notification out of Docky.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: docky 2.1.4-1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Wed Apr 18 11:24:52 2012
ExecutablePath: /usr/lib/docky/Docky.exe
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
InterpreterPath: /usr/bin/mono
PackageArchitecture: all
ProcCmdline: mono /usr/lib/docky/Docky.exe
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc42449871b <vfprintf+155>: callq 0x7fc4244e3790 <strchrnul>
 PC (0x7fc42449871b) ok
 source "0x7fc4244e3790" (0x7fc4244e3790) ok
 destination "(%rsp)" (0x7fc425337f60) in non-writable VMA region: 0x7fc425334000-0x7fc425338000 r--p /usr/lib/mono/gac/notify-sharp/0.4.0.0__2df29c54e245917a/notify-sharp.dll
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA /usr/lib/mono/gac/notify-sharp/0.4.0.0__2df29c54e245917a/notify-sharp.dll
Signal: 11
SourcePackage: docky
StacktraceTop:
 g_type_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: Docky.exe crashed with SIGSEGV in g_type_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Carsten Lange (milkthemilk) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_name (type=<optimized out>) at /build/buildd/glib2.0-2.32.1/./gobject/gtype.c:3301
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in docky (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

fontconfig version 2.8.0-3ubuntu8 required, but 2.8.0-3ubuntu9 is available
python version 2.7.3-0ubuntu1 required, but 2.7.3-0ubuntu2 is available
libfontconfig1 version 2.8.0-3ubuntu8 required, but 2.8.0-3ubuntu9 is available
python-minimal version 2.7.3-0ubuntu1 required, but 2.7.3-0ubuntu2 is available
fontconfig-config version 2.8.0-3ubuntu8 required, but 2.8.0-3ubuntu9 is available
outdated debug symbol package for libgconf2-4: package version 3.2.5-0ubuntu2 dbgsym version 3.2.3-0ubuntu0.1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.