conky crashed with SIGSEGV in strndup()

Bug #983102 reported by Redsandro
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
conky-all (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This bug was reported before, but the apport-bot preaches about "outdated packages". Because I *just* updated everything, I will submit this bug once again just for shits and giggles.

Possible duplicates:
#944629
#946149
#968833

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: conky-all 1.8.1-6
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
Date: Mon Apr 16 16:04:00 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/conky
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: conky -d
SegvAnalysis:
 Segfault happened at: 0x7f61f132ccb1: pcmpeqb (%rdi),%xmm2
 PC (0x7f61f132ccb1) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm2" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: conky-all
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 strndup () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Title: conky crashed with SIGSEGV in strndup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Redsandro (redsandro) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI___strndup (s=0x0, n=<optimized out>) at strndup.c:45
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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 conky-all (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:

libgcc1 version 1:4.6.3-1ubuntu4 required, but 1:4.6.3-1ubuntu5 is available
outdated debug symbol package for conky-all: package version 1.8.1-6 dbgsym version 1.8.1-2
libglib2.0-0 version 2.32.0-1ubuntu3 required, but 2.32.1-0ubuntu1 is available
libc-bin version 2.15-0ubuntu7 required, but 2.15-0ubuntu9 is available
outdated debug symbol package for libc-bin: package version 2.15-0ubuntu9 dbgsym version 2.15-0ubuntu7
gcc-4.6-base version 4.6.3-1ubuntu4 required, but 4.6.3-1ubuntu5 is available
libstdc++6 version 4.6.3-1ubuntu4 required, but 4.6.3-1ubuntu5 is available
outdated debug symbol package for libstdc++6: package version 4.6.3-1ubuntu5 dbgsym version 4.6.3-1ubuntu4
multiarch-support version 2.15-0ubuntu7 required, but 2.15-0ubuntu9 is available
libc6 version 2.15-0ubuntu7 required, but 2.15-0ubuntu9 is available

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
Revision history for this message
Redsandro (redsandro) wrote :

That is funny mr apport-bot, it's not easy to update all those:

$ sudo apt-get update && sudo apt-get upgrade
(...)
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

visibility: private → 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.