hud-service crashed with signal 5 in g_type_create_instance()

Bug #1218313 reported by Daniel Winzen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hud (Ubuntu)
New
Undecided
Unassigned

Bug Description

After I closed CompizConfig settings manager, this crash came up.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: hud 13.10.1+13.10.20130822.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Thu Aug 29 13:11:44 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service
InstallationDate: Installed on 2013-02-27 (183 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130226)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service
Signal: 5
SourcePackage: hud
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.2
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: hud-service crashed with signal 5 in g_type_create_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
modified.conffile..etc.apport.crashdb.conf.d.hud.crashdb.conf: [deleted]
upstart.hud.log: ** (process:11226): ERROR **: Unable to get org.ayatana.bamf matcher: Fehler beim Aufruf von StartServiceByName für org.ayatana.bamf: Zeitüberschreitung wurde erreicht

Revision history for this message
Daniel Winzen (q-d-deactivatedaccount) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1216323, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

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.