Ubuntu
kile package

kile crashed with SIGSEGV in QStackedWidget::currentWidget()

Bug #427538 reported by tijnema on 2009-09-10

56

This bug affects 8 people

Affects		Status	Importance	Assigned to	Milestone
	kile	Fix Released	High	kde-bugs #220343
	kile (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

Binary package hint: kile

just running kile, idle, nothing special

Description: Ubuntu karmic (development branch)
Release: 9.10

kile:
  Installed: 1:2.1.0~svn1014763beta2-1ubuntu1
  Candidate: 1:2.1.0~svn1014763beta2-1ubuntu1
  Version table:
*** 1:2.1.0~svn1014763beta2-1ubuntu1 0

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 10 22:36:32 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kile
NonfreeKernelModules: nvidia
Package: kile 1:2.1.0~svn1014763beta2-1ubuntu1
ProcCmdline: /usr/bin/kile
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.30-generic
SegvAnalysis:
Segfault happened at: 0x7f6475cf0904 <_ZNK14QStackedWidget13currentWidgetEv+4>: mov 0x200(%rax),%rdi
PC (0x7f6475cf0904) ok
source "0x200(%rax)" (0x00000410) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kile
Stacktrace:
#0 0x00007f6475cf0904 in QStackedWidget::currentWidget (this=0x2b494c0)
at widgets/qstackedwidget.cpp:229
No locals.
#1 0x00000000006cf2fd in _start ()
No symbol table info available.
StacktraceTop:
QStackedWidget::currentWidget (this=0x2b494c0)
_start ()
Title: kile crashed with SIGSEGV in QStackedWidget::currentWidget()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

tijnema (tijnema) wrote on 2009-09-10:

#1

Dependencies.txt Edit (6.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (47.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (771 bytes, text/plain; charset="utf-8")
Registers.txt Edit (980 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.5 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-10: Stacktrace.txt (retraced)

#2

Stacktrace.txt (retraced) Edit (12.1 KiB, text/plain)

StacktraceTop:QStackedWidget::currentWidget ()
KileView::Manager::currentTextView (
KileInfo::activeTextDocument (
KileDocument::Manager::getInfo (this=0x22b4cf0)
KileView::Manager::updateStructure (this=0x22e3b70,

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-10: ThreadStacktrace.txt (retraced)

#3

ThreadStacktrace.txt (retraced) Edit (12.7 KiB, text/plain)

Changed in kile (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Jonathan Thomas (echidnaman) wrote on 2009-09-10:

#4

Upstream bug: https://bugs.kde.org/show_bug.cgi?id=202885
Hopefully this'll be enough info for the developers. Thanks for the report.

Changed in kile (Ubuntu):
status:	New → Triaged

Revision history for this message

John B. (jbuncher) wrote on 2009-09-25:

#5

Encountered this on an i386 install of Karmic Alpha 6.

Revision history for this message

Bart (bart-lamiroy-gmail) wrote on 2009-11-03:

#6

Just upgraded to Karmic (public release).

Revision history for this message

Bart (bart-lamiroy-gmail) wrote on 2009-11-03:

#7

Just upgraded to Karmic (public release) same problem apparently.

Revision history for this message

gloonie (gloonie) wrote on 2009-12-02:

#8

I confirm I get this on i386 architecture. I close kile down properly, and several minutes later I get the crash message. Should I report this as a separate bug, since it's not on amd64 architecture? Looks like the same problem, though.

Revision history for this message

Andreas Wenning (andreas-wenning) wrote on 2009-12-02:

#9

A new beta 3 of kile has just been released. I've made a test build of it in my PPA for kile: https://launchpad.net/~andreas-wenning/+archive/ppa/
Does the crash still happen with that version?

@gloonie: There should be no need to report a new bug; as long as the stack-traces look similar.

Revision history for this message

gloonie (gloonie) wrote on 2009-12-02:

#10

I just tried the beta 3 from Andreas' ppa, and so far so good. I have opened and closed kile many times in different ways and it has not crashed. Will report any future bad behavior, but currently it's looking good. Thanks, Andreas

Revision history for this message

Andreas Wenning (andreas-wenning) wrote on 2009-12-02:

#11

Fixed in upstream svn according to the kile-devel mail list.

Changed in kile (Ubuntu):
status:	Triaged → Fix Committed

Revision history for this message

Andreas Wenning (andreas-wenning) wrote on 2010-01-27:

#12

kile (1:2.1.0~svn1079982-0ubuntu1) lucid; urgency=low

  * New upstream svn snapshot including beta3.
    (LP: #409581, #432931, #429336, #267113, 476860, 427538)
  * debian/control: Recommend firefox instead of iceweasel to have it look like
    (konqueror | firefox); on default Ubuntu kile will then no longer install
    konqueror. (LP: #452079)
  * debian/rules: Use override_dh_compress to not compress index.docbook.

Changed in kile (Ubuntu):
status:	Fix Committed → Fix Released

Bug Watch Updater (bug-watch-updater) on 2010-02-17

Changed in kile:
status:	Unknown → Invalid

Jonathan Thomas (echidnaman) on 2010-02-17

Changed in kile:
status:	Invalid → Unknown

Bug Watch Updater (bug-watch-updater) on 2010-02-17

Changed in kile:
status:	Unknown → Fix Released

Bug Watch Updater (bug-watch-updater) on 2011-02-27

Changed in kile:
importance:	Unknown → High

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

kde-bugs #202885
[RESOLVED DUPLICATE] Edit
kde-bugs #220343
[RESOLVED FIXED] Edit

Bug watches keep track of this bug in other bug trackers.