kppp crashed with SIGSEGV in QString::replace()

Bug #368528 reported by Sergiu Bivol
6
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kdenetwork

kppp crashed while connecting.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/kppp
NonfreeKernelModules: hsfengine
Package: kppp 4:4.2.2-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/kppp
ProcEnviron:
 LANGUAGE=ro_RO:ro:en_GB:en
 PATH=(custom, no user)
 LANG=ro_RO.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdenetwork
Stacktrace:
 #0 0x00007f297303ddd1 in QString::replace () from /usr/lib/libQtCore.so.4
 #1 0x0000000000434e52 in _start ()
StacktraceTop:
 QString::replace () from /usr/lib/libQtCore.so.4
 _start ()
ThreadStacktrace:
 .
 Thread 1 (process 5843):
 #0 0x00007f297303ddd1 in QString::replace () from /usr/lib/libQtCore.so.4
 #1 0x0000000000434e52 in _start ()
Title: kppp crashed with SIGSEGV in QString::replace()
Uname: Linux 2.6.30-020630rc3-generic x86_64
UserGroups:

Revision history for this message
Sergiu Bivol (sergiu-bivol) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:QString::replace (this=0x7fff7dbbadc0, rx=@0x7fff7dbbada0,
ConnectWidget::setExpect (this=0x2082290,
ConnectWidget::timerEvent (this=0x2082290)
ConnectWidget::checkBuffers (this=0x2082290)
ConnectWidget::setExpect (this=0x2082290,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdenetwork (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this crash still reproducible with KDE 4.3? (http://www.kubuntu.org/news/kde-4.3.1)

Changed in kdenetwork (Ubuntu):
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 kdenetwork (Ubuntu):
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.