[apport] osplugin crashed with SIGSEGV in strlen()

Bug #116101 reported by Tsvi Mostovicz
6
Affects Status Importance Assigned to Milestone
opensync (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

While testing opensync according to the following guide: http://www.opensync.org/wiki/SetupGuide and going through the kde-pim plugin part for some reason it called up kontact which was closed up till then and crashed the sync.

ProblemType: Crash
Architecture: amd64
Date: Tue May 22 04:03:06 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/opensync/osplugin
Package: libopensync0 0.19-1.2ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/lib/opensync/osplugin /home/tsvi/.opensync/group1 1
ProcCwd: /home/tsvi/sync1
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: opensync
StacktraceTop:
 strlen () from /lib/libc.so.6
 KCrash::startDrKonqi ()
 KCrash::defaultCrashHandler ()

 KCal::Calendar::addIncidence ()
Uname: Linux tsvi-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Tsvi Mostovicz (tsvi) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:strlen () from /lib/libc.so.6
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in opensync:
importance: Undecided → Medium
Revision history for this message
Javier Jardón (jjardon) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in opensync:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in opensync:
status: Incomplete → Invalid
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.