contractor crashed with signal 5 in _start()

Bug #1001948 reported by Sergey "Shnatsel" Davidoff
412
This bug affects 77 people
Affects Status Importance Assigned to Milestone
Contractor
Fix Released
Critical
Akshay Shekher

Bug Description

I get these crashes from time to time even though I don't use Contractor. Often on startup.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: contractor 0.2-0~r12+pkg2~precise1 [origin: LP-PPA-elementary-os-daily]
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7+elementary2~precise1
Architecture: amd64
CrashCounter: 1
CrashDB: contractor
Date: Sun May 20 16:30:35 2012
ExecutablePath: /usr/bin/contractor
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120303)
ProcCmdline: /usr/bin/contractor
ProcEnviron:
 SHELL=/usr/bin/fish
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
Signal: 5
SourcePackage: contractor
StacktraceTop: _start ()
SuspiciousXErrors:

ThirdParty: True
Title: contractor crashed with signal 5 in _start()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Related branches

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :
Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

StacktraceTop:
 __lambda2_ () at /build/buildd/contractor-0.2/obj-x86_64-linux-gnu/src/contractor.c:4987
 ___lambda2__gbus_name_lost_callback (connection=<optimized out>, name=<optimized out>, self=<optimized out>) at /build/buildd/contractor-0.2/obj-x86_64-linux-gnu/src/contractor.c:4992
 ffi_call_unix64 () at ../src/x86/unix64.S:75
 ffi_call (cif=0x7ffffb5c8030, fn=0x4044f0 <___lambda2__gbus_name_lost_callback>, rvalue=<optimized out>, avalue=<optimized out>) at ../src/x86/ffi64.c:486
 g_cclosure_marshal_generic (closure=0x12b3f50, return_gvalue=0x0, n_param_values=2, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=0x4044f0) at /build/buildd/glib2.0-2.32.1/./gobject/gclosure.c:1454

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote : Stacktrace.txt
Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote : ThreadStacktrace.txt
description: updated
Changed in contractor:
importance: Undecided → Critical
milestone: none → luna-beta1
visibility: private → public
Changed in contractor:
status: New → Confirmed
Revision history for this message
Cassidy James Blaede (cassidyjames) wrote :

Still getting this, anyone working on it?

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

Not as far as I know.

Revision history for this message
Akshay Shekher (voldyman) wrote :

it can be easily fixed using the attached patch

Changed in contractor:
status: Confirmed → In Progress
assignee: nobody → Akshay Shekher (voldyman)
tags: removed: need-amd64-retrace
Cody Garver (codygarver)
Changed in contractor:
status: In Progress → Fix Committed
Revision history for this message
Jakob Eriksson (b-jakob-v) wrote :

So what happens with a bug after "Fix Commited"?

Revision history for this message
Tom Beckmann (tombeckmann) wrote :

Well, it's done and solved. Do you still experience this bug?

Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

Contractor is only available in form of daily builds at the moment, so "Fix committed" is equivalent to "Fix released" for now.

Changed in contractor:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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