Docky.exe crashed with SIGABRT in g_type_name()

Bug #1436457 reported by vagner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
docky (Ubuntu)
New
Undecided
Unassigned

Bug Description

O aplicativo fechou inesperadamente

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: docky 2.2.0-2
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 25 04:09:07 2015
ExecutablePath: /usr/lib/docky/Docky.exe
InstallationDate: Installed on 2015-03-16 (9 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
InterpreterPath: /usr/bin/mono-sgen
PackageArchitecture: all
ProcCmdline: mono /usr/lib/docky/Docky.exe
Signal: 6
SourcePackage: docky
StacktraceTop:
 g_type_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: Docky.exe crashed with SIGABRT 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
vagner (vagnermassabane) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Steve Beattie (sbeattie) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
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.