Use regular expressions in kompare causes "could not parse diff output"

[wsfulton]

Binary package hint: kompare

Add in a regular expression, eg Settings, configure Kompare, Diff, Options tab and click 'Ignore regexp'. I used ^Version as the regular expression. Close kompare and execute the following

william@caracal:/tmp$ mkdir dir1 dir2
william@caracal:/tmp$ touch dir1/abc.txt dir2/abc.txt
william@caracal:/tmp$
william@caracal:/tmp$ kompare dir1 dir2 &

A dialog stating "could not parse output" appear making the program unusable. This is a regression from Ubuntu 8.04.

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$

[Bruce Edge (bruce-edge)]

I can confirm this.
I can't get any regexp to work, even simple string, with and without quotes. I even RTFM'd but the FM gives no info on the regexp syntax.

ii kompare 4:4.3.95-0ubuntu1~karmic1~ppa1 file difference viewer for KDE 4

[Bruce Edge (bruce-edge)]

...here's the stdout after a failed diff because there's a non-null ignore regexp:

kompare(26884)/kompare (libs) KomparePart::cleanUpTemporaryFiles: Cleaning temporary files.
kompare(26884)/kompare (nav view) KompareNavTreePart::slotModelsChanged: Models ( 0x0 ) have changed... scanning the models...
kompare(26884)/kompare (libs) KompareProcess::writeCommandLine: Using the first diff in the path...
kompare(26884)/kompare (libs) KompareProcess::slotFinished: Exited with exit code : 2
kompare(26884)/kompare (libs) Diff2::KompareModelList::parseDiffOutput: KompareModelList::parseDiffOutput
kompare(26884)/kompare (libs) Diff2::Parser::determineGenerator: We'll assume it is a diff Diff
kompare(26884)/kompare (libs) Diff2::Parser::parse: Cleaned up 0 line(s) of crap from the diff...
kompare(26884)/kompare (libs) Diff2::Parser::parse: It is a diff generated diff...
kompare(26884)/kompare (libs) Diff2::DiffParser::determineFormat: Determining the format of the diff Diff
kompare(26884)/kompare (libs) Diff2::DiffParser::determineFormat: Difflines are from an unknown diff...
kompare(26884)/kompare (libs) Diff2::DiffParser::determineFormat: Determining the format of the diff Diff
kompare(26884)/kompare (libs) Diff2::DiffParser::determineFormat: Difflines are from an unknown diff...
kompare(26884)/kompare (libs) Diff2::KompareModelList::parseDiffOutput: Now i'll be damned, there should be models here !!!

[Alessandro Ghersi (alessandro-ghersi)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at: https://bugs.kde.org/show_bug.cgi?id=253188
Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.

Thanks!

[Alessandro Ghersi (alessandro-ghersi)]

Version: unspecified (using KDE 1.2)
OS: Linux

Bug reported here:
https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/303502

Add in a regular expression, eg Settings, configure Kompare, Diff, Options tab and click 'Ignore regexp'. I used ^Version as the regular expression. Close kompare and execute the following

william@caracal:/tmp$ mkdir dir1 dir2
william@caracal:/tmp$ touch dir1/abc.txt dir2/abc.txt
william@caracal:/tmp$
william@caracal:/tmp$ kompare dir1 dir2 &

A dialog stating "could not parse output" appear making the program unusable. This is a regression from Ubuntu 8.04.

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$

Reproducible: Didn't try

[matt (matthiasgies)]

Still present in oneiric...

[Harald Sitter (apachelogger)]

Because it is not fixed upstream.

[hamish (hamish-b)]

Hi,

I can reproduce this on debian/stable (squeeze).

kompare .deb package version 4:4.4.5-1.
help -> about says kompare 4.0.0, kde 4.4.5.

using the same regex pattern on the command line for 'diff -I' works ok.

thanks,
Hamish

[Andrew-crouthamel (andrew-crouthamel)]

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

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

[Andrew-crouthamel (andrew-crouthamel)]

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

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

[Justin Zobel (justin-zobel)]

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

[Bug-janitor (bug-janitor)]

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
mark the bug 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!

[Bug-janitor (bug-janitor)]

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!