Apply in Preferences dialog in Kompare crash

Bug #303505 reported by wsfulton
26
Affects Status Importance Assigned to Milestone
KDE Software Development Kit
Fix Released
High
kdesdk (Ubuntu)
Fix Released
Medium
Unassigned
Intrepid
Fix Released
Medium
Jonathan Thomas

Bug Description

*Below added by Jonathan Thomas*
  Stable Release Update (SRU) infos:
  -Impact: Anybody who tries to change Kompare's settings will encounter this bug
  -Addressed by: This bug has been addressed by adding an upstream patch committed for KDE 4.2.1 that fixes the infinite recursion that causes this bug.
  -Testcase: Install kompare. Start kompare. Go to Settings -> Configure Kompare. Change any setting and hit apply
  -Patch/regression potential: Small. The changes aren't invasive and it can hardly get worse than it already is.
#######################################################################

Run:
kompare dir1 dir2

Open the preferences dialog... Settings, Configure Kompare. Then press the Apply button. The program just hangs and after a while seg faults. It seems to be stuck in a loop, here is the gdb stack trace:

(gdb) where
#0 0xb733d989 in QByteArrayMatcher::QByteArrayMatcher () from /usr/lib/libQtCore.so.4
#1 0xb733bea3 in QByteArray::replace () from /usr/lib/libQtCore.so.4
#2 0xb733c409 in QByteArray::replace () from /usr/lib/libQtCore.so.4
#3 0xb7583dd3 in ?? () from /usr/lib/libkdecore.so.5
#4 0xb7587311 in KConfigGroup::writeEntry () from /usr/lib/libkdecore.so.5
#5 0xb7dfbe9b in ?? () from /usr/lib/libkdeui.so.5
#6 0xb7587512 in KConfigGroup::writeEntry () from /usr/lib/libkdecore.so.5
#7 0xb8087f20 in ViewSettings::saveSettings () from /usr/lib/libkomparedialogpages.so.4
#8 0xb808dfdd in ViewPage::apply () from /usr/lib/libkomparedialogpages.so.4
#9 0xb47fe1e5 in ?? () from /usr/lib/kde4/libkomparepart.so
#10 0xb47fdf5b in ?? () from /usr/lib/kde4/libkomparepart.so
#11 0xb743ba60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb743c7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb7e13287 in KDialog::applyClicked () from /usr/lib/libkdeui.so.5
#14 0xb47fe201 in ?? () from /usr/lib/kde4/libkomparepart.so
#15 0xb47fdf5b in ?? () from /usr/lib/kde4/libkomparepart.so
#16 0xb743ba60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb743c7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb7e13287 in KDialog::applyClicked () from /usr/lib/libkdeui.so.5
#19 0xb47fe201 in ?? () from /usr/lib/kde4/libkomparepart.so
#20 0xb47fdf5b in ?? () from /usr/lib/kde4/libkomparepart.so
#21 0xb743ba60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#22 0xb743c7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb7e13287 in KDialog::applyClicked () from /usr/lib/libkdeui.so.5

... over and over again ...

This used to work in Ubuntu 8.04. Details:

william@caracal:/tmp$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
william@caracal:/tmp$ apt-cache policy kompare
kompare:
  Installed: 4:4.1.2-0ubuntu1.1
  Candidate: 4:4.1.2-0ubuntu1.1
  Version table:
 *** 4:4.1.2-0ubuntu1.1 0
        500 http://gb.archive.ubuntu.com intrepid-updates/main Packages
        100 /var/lib/dpkg/status
     4:4.1.2-0ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
william@caracal:/tmp$

Changed in kdesdk:
importance: Undecided → Medium
status: New → Triaged
Changed in kdesdk:
status: Unknown → New
Changed in kdesdk:
status: New → Confirmed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

A fix has been committed upstream in trunk. I'm guessing it'll be backported to the 4.2 series to be released with KDE 4.2.1. (If not it will be quite easy to do)

Since this is such an easy-to-trigger bug a SRU should probably be prepared for Intrepid's KDE 4.1 packages. I'll look into this once KDE 4.1.4 is pushed in to intrepid-updates.

Changed in kdesdk:
status: Triaged → Fix Committed
Changed in kdesdk:
status: Confirmed → Fix Released
Changed in kdesdk:
milestone: none → jaunty-alpha-5
Changed in kdesdk:
assignee: nobody → echidnaman
importance: Undecided → Medium
milestone: none → intrepid-updates
status: New → In Progress
Revision history for this message
Jonathan Thomas (echidnaman) wrote :
Revision history for this message
Jonathan Thomas (echidnaman) wrote :
description: updated
Revision history for this message
Martin Pitt (pitti) wrote :

Is there a patch or pointer to websvn or similar?

Revision history for this message
Jonathan Thomas (echidnaman) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Thanks, approved. Please get it uploaded.

Revision history for this message
Jonathan Riddell (jr) wrote :

Uploaded and accepted into intrepid-proposed, please test.

Revision history for this message
wsfulton (wsf) wrote :

intrepid-proposed fixes the bug for me. Thanks :)

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kdesdk - 4:4.1.4-0ubuntu1~intrepid1.1

---------------
kdesdk (4:4.1.4-0ubuntu1~intrepid1.1) intrepid-proposed; urgency=low

  * Add kubuntu_02_fix_kompare_settings_crash.diff to fix KDE bug 176797
    (LP: #303505)

 -- Jonathan Thomas <email address hidden> Thu, 19 Feb 2009 09:24:24 -0500

Changed in kdesdk:
status: In Progress → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This bug was fixed in the package kdesdk - 4:4.2.1-0ubuntu1

---------------
kdesdk (4:4.2.1-0ubuntu1) jaunty; urgency=low

  * New upstream release
  * Update install files (replace 4.2.0 w/ 4.2.*)
  * Update build-deps (kdelibs5-dev, kdepimlibs5-dev, libplasma-dev,
    libphonon-dev)
  * Update kapptemplate deps (kdelibs5-dev)
  * Update lokalize deps (libkrosspython0)

 -- <email address hidden> (Roderick B. Greening) Fri, 27 Feb 2009 13:24:00 -0330

Changed in kdesdk:
status: Fix Committed → Fix Released
Changed in kdesdk:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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