Bug 184011

Summary: kompare crashes when comparing two directories
Product: [Applications] kompare Reporter: somshekar <som_kadam>
Component: generalAssignee: Kompare developers <kompare-devel>
Status: RESOLVED WORKSFORME    
Severity: crash CC: andresbajotierra, bruggie, som_kadam
Priority: NOR Keywords: investigated, triaged
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description somshekar 2009-02-11 11:06:24 UTC
Version:           3.5.2 (using KDE 4.2.0)
Compiler:          gcc 4.3.2 redhat 4.3.27 
OS:                Linux
Installed from:    Fedora RPMs

run kompare for diff of two directory on start crashes giving the follwoing 


Application: Kompare (kompare), signal SIGSEGV
[Current thread is 1 (Thread 0xb7f8b9a0 (LWP 9237))]

Thread 1 (Thread 0xb7f8b9a0 (LWP 9237)):
[KCrash Handler]
#6  0x084b4817 in KServiceType::serviceOffersOffset() const () from /usr/lib/libkdecore.so.5
#7  0x08052273 in _start ()
Comment 1 somshekar 2009-02-11 11:08:03 UTC
Please help to fix this on Fedora 11, or if any patch available let us know

Thanks In Advance
Neelu
Comment 2 Otto Bruggeman 2009-02-11 11:15:13 UTC
Is Fedora 11 usng Qt4.5? If so this is a duplicate of an already reported bug and this will closed.
If not please get us a useful backtrace because what you wrote in the first comment is useless to find out what the problem is.
Comment 3 Kevin Kofler 2009-02-11 11:29:01 UTC
> Is Fedora 11 usng Qt4.5

No, not yet. Latest in dist-f11 (i.e. Rawhide - Fedora 11 is not released yet) is qt-4.4.3-16.fc11.
Comment 4 Dario Andres 2009-09-28 02:04:59 UTC
- Is this still happening with an updated KDE version ? Thanks
Comment 5 Kevin Kofler 2009-09-28 02:11:08 UTC
Is this the same user error as in bug 124121? Kompare doesn't take directories, only files.
Comment 6 Andrew Crouthamel 2018-09-20 03:06:26 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-10-21 05:09:58 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!