Ubuntu
strongswan package

charon crashed with SIGABRT in start_thread()

Bug #745958 reported by Derek
62
This bug affects 7 people
Affects Status Importance Assigned to Milestone
strongswan (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: strongswan

Natty crashes are pretty common, usually on signing in.
Applets (like show desktop) crash, or things like this. I'm not too sure, frankly, what causes it. The laptop is pretty much a clean new natty install, and this sort of thing happens on a clean boot, with or without a network connection.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: strongswan-ikev2 4.5.0-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 30 14:08:32 2011
ExecutablePath: /usr/lib/ipsec/charon
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/ipsec/charon --use-syslog
ProcCwd: /
ProcEnviron: PATH=(custom, no user)
Signal: 6
SourcePackage: strongswan
StacktraceTop:
 ?? () from /usr/lib/ipsec/plugins/libstrongswan-dhcp.so
 ?? () from /usr/lib/libstrongswan.so.0
 ?? () from /usr/lib/libstrongswan.so.0
 ?? () from /usr/lib/libstrongswan.so.0
 start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
Title: charon crashed with SIGABRT in start_thread()
UpgradeStatus: Upgraded to natty on 2011-03-24 (5 days ago)
UserGroups:

Revision history for this message
Derek (bugs-m8y) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 handle_offer (this=0x7f155a8880c0) at dhcp_socket.c:523
 receive_dhcp (this=0x7f155a8880c0) at dhcp_socket.c:595
 execute (this=0x7f155a888580) at processing/jobs/callback_job.c:203
 process_jobs (this=0x7f155a862540) at processing/processor.c:135
 thread_main (this=0x7f155a88a220) at threading/thread.c:287

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 strongswan (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Daniel Hahler (blueyed)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in strongswan (Ubuntu):
status: New → Confirmed
Daniel Hahler (blueyed)
Changed in strongswan (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Simon Déziel (sdeziel) wrote :

Natty has long been out of support. Derek, are you still seeing this crash?

Changed in strongswan (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Derek (bugs-m8y) wrote :

Corporate config changed years ago. I'll see if I can find a network to try it on - wouldn't surprise me if it has been fixed in the interim though. Feel free to close it if you like... I can always file a new one and reference this one.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for strongswan (Ubuntu) because there has been no activity for 60 days.]

Changed in strongswan (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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