Bug 180086

Summary:	kppp crashes on config setup
Product:	[Unmaintained] kppp	Reporter:	donald rick <geek0101>
Component:	general	Assignee:	Harri Porten <porten>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description donald rick 2009-01-09 02:06:40 UTC

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

On trying to setup Kppp for Sierra 860 wireless aircard, can't get past phone # on configure without it crashing.  I've had this feature on earlier versions of kde.  I'm using Kubuntu 8.10 intrepid.

Here is the detail:


This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5d18920 (LWP 14255)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb80b2430 in __kernel_vsyscall ()
[Current thread is 0 (process 14255)]

Thread 1 (Thread 0xb5d18920 (LWP 14255)):
#0  0xb80b2430 in __kernel_vsyscall ()
#1  0xb65535e3 in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2  0xb78dafcf in ?? () from /usr/lib/libkdeui.so.5
#3  0xb78dbf63 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#4  <signal handler called>
#5  0xb70e6a49 in ?? () from /usr/lib/libQtGui.so.4
#6  0xb70e7ae5 in QLineEdit::text () from /usr/lib/libQtGui.so.4
#7  0x0807e7cc in _start ()
#0  0xb80b2430 in __kernel_vsyscall ()

Comment 1 Dario Andres 2009-01-09 03:45:42 UTC

This may be related/duplicate of bug 176645
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)

Comment 2 Dario Andres 2009-01-09 12:10:47 UTC

Donald sent my the backtrace and the steps to reproduce the bug.
Marking as duplicate of bug 176645
@Donald: thanks for the info

*** This bug has been marked as a duplicate of bug 176645 ***