Kompare crashes on startup in Jaunty

Bug #344846 reported by John McCabe-Dansted
6
Affects Status Importance Assigned to Milestone
kdesdk (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: kdesdk

Kompare always crashes on startup in Jaunty i386 no matter what. The KDE backtrace is as follows:

Application: Kompare (kompare), signal SIGSEGV

Thread 1 (Thread 0xb5b1b700 (LWP 5533)):
[KCrash Handler]
#5 0xb6915a77 in KServiceType::serviceOffersOffset () from /usr/lib/libkdecore.so.5
#6 0x08054133 in _start ()

(yes, its really short).

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: kompare 4:4.2.1-0ubuntu1
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_AU.UTF-8
SourcePackage: kdesdk
Uname: Linux 2.6.28-8-generic i686

Revision history for this message
John McCabe-Dansted (gmatht) wrote :
Revision history for this message
Harald Sitter (apachelogger) wrote :

Hello John,

Unfortunately I am not able to reproduce this behaviour. Please install the package kdesdk-dbg and obtain a new backtrace of this crash, I suspect the one you posted initially is so short because some debugging related files are missing (I might be wrong though :)).
If kdesdk-dbg doesn't help to get a longer backtrace, an strace might be of use. Please run
strace kompare > ~/kompare.strace 2&>1
this will create a file called kompare.strace in your home directory, please attach this file to this bug report.
Thank you very much in advance and have a nice day.

Changed in kdesdk (Ubuntu):
status: New → Incomplete
Revision history for this message
Ben Heley (oxygen84) wrote :

I'm getting the same thing on 8.10, I've screwed around with my software sources though, so my system may be inconsistent somewhere.

Application: Kompare (kompare), signal SIGSEGV

Thread 1 (Thread 0xb5ba46c0 (LWP 9261)):
[KCrash Handler]
#5 0xb6940797 in KServiceType::serviceOffersOffset () from /usr/lib/libkdecore.so.5
#6 0x08054133 in KompareShell (this=0x815e858) at /build/buildd/kdesdk-4.2.2/kompare/kompare_shell.cpp:68
#7 0x0805060e in main (argc=1, argv=0xbfa820a4) at /build/buildd/kdesdk-4.2.2/kompare/main.cpp:95

Revision history for this message
sreque (seanthenewt) wrote :

I see this exact bug in Intrepid 9.04. It happens every time on startup.

Application: Kompare (kompare), signal SIGSEGV
0x00007f0d27d358f5 in waitpid () from /lib/libc.so.6

Thread 1 (Thread 0x7f0d2c66b750 (LWP 30196)):
[KCrash Handler]
#4 0x00007f0d28fa4c20 in KServiceType::serviceOffersOffset () from /usr/lib/libkdecore.so.5
#5 0x00007f0d28f8e6fe in KMimeTypeTrader::query () from /usr/lib/libkdecore.so.5
#6 0x000000000040de8a in KompareShell (this=0x1b8dd60) at /build/buildd/kdesdk-4.2.2/kompare/kompare_shell.cpp:68
#7 0x000000000040a66e in main (argc=1, argv=0x7fff3469fbc8) at /build/buildd/kdesdk-4.2.2/kompare/main.cpp:95

Revision history for this message
sreque (seanthenewt) wrote :

Oops, I Meant Jaunty 9.04!

Revision history for this message
sreque (seanthenewt) wrote :

Another interesting thing to note. I just tried running kompare inside of the kde desktop instead of gnome, and it didn't crash.

Revision history for this message
Bruce MacDonald (b-macdonald-auckland) wrote :

Kompare crashed in Ubuntu 8.10 complaining about files not existing in .kde, but only if I gave it arguments (if no arguments, it runs and functions fine except for the window taking the whole screen). After running konqueror this problem goes away, even after a reboot kompare is fine. I can't reproduce it. I don't use konqueror much so maybe there was some legacy set up in .kde, that kompare does not fix.

Revision history for this message
Srinidhi (srinidhimmeera) wrote :

Hello,

I am using Linux Mint 7 on a AMD64 machine. I am facing the same problem and i have the trace also. Can i post it here?

Revision history for this message
fsando (fsando) wrote :

I'm seeing the same on Ubuntu 8.10

Revision history for this message
John McCabe-Dansted (gmatht) wrote :

I cannot reproduce on 10.04 LTS

Changed in kdesdk (Ubuntu):
status: Incomplete → Fix Released
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.