konqueror crashed with SIGSEGV

Bug #151864 reported by pol
54
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: konqueror

sometimes konqueror crashes with 'segmentation fault' - kubuntu gutsy 10.7

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Oct 10 16:04:34 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/konqueror
Package: konqueror 4:3.5.7-1ubuntu28
PackageArchitecture: i386
ProcCmdline: konqueror
ProcCwd: /home/pol
ProcEnviron:
 LANGUAGE=en_US
 PATH=/home/pol/uxs:/home/pol/bin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/local/uxs
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
Signal: 11
SourcePackage: kdebase
Stacktrace: #0 0xb5b981cc in ?? () from /usr/lib/libpcre.so.3
StacktraceTop: ?? () from /usr/lib/libpcre.so.3
ThreadStacktrace:
 .
 Thread 1 (process 15135):
 #0 0xb5b981cc in ?? () from /usr/lib/libpcre.so.3
Title: konqueror crashed with SIGSEGV
Uname: Linux ambhi 2.6.22-14-generic #1 SMP Tue Oct 9 09:51:52 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom crontab dialout dictd dip dirmngr dovecot fax floppy games lp lpadmin mail news plugdev powerdev proxy scanner staff video

Tags: apport-crash
Revision history for this message
pol (xtekhne) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:match (
match (

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in kdebase:
importance: Undecided → Medium
Revision history for this message
Harald Sitter (apachelogger) wrote :

Hm, not even retracing worked. :(

Does this still occur in 8.04 or even 8.10?

Changed in kdebase:
status: New → Incomplete
Revision history for this message
Harald Sitter (apachelogger) 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 kdebase:
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.