Bug 497102 - Error when opening on the first time
Summary: Error when opening on the first time
Status: RESOLVED DUPLICATE of bug 486782
Alias: None
Product: kdiff3
Classification: Applications
Component: application (show other bugs)
Version: 1.11.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: michael
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-05 20:58 UTC by Marcelo Jimenez
Modified: 2024-12-06 22:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 1.12
Sentry Crash Report:


Attachments
Modal window with the error (8.82 KB, image/png)
2024-12-05 20:58 UTC, Marcelo Jimenez
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcelo Jimenez 2024-12-05 20:58:49 UTC
Created attachment 176380 [details]
Modal window with the error

SUMMARY
When opening a simple diff of two files, kdiff3 gives an error opening the second file.

STEPS TO REPRODUCE
1. cd /tmp
2. echo "asdf" > file1.txt
3. echo "qwer" > file2.txt
4. kdiff3 file1.txt file2.txt

OBSERVED RESULT
A modal window appears with the following message: 
File open error - KDiff3
Opening of these files failed:
- /tmp/file2.txt

EXPECTED RESULT
No error.

SOFTWARE/OS VERSIONS
$ kinfo
Operating System: openSUSE Tumbleweed 20241121
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: X11
Processors: 24 × 12th Gen Intel® Core™ i9-12900K
Memory: 62.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3050/PCIe/SSE2

ADDITIONAL INFORMATION
If you click ok, the `file open...` dialog appears with the correct file names and paths, and the diff is successfully opened.

But, this additional step creates problems when diffing from version control software, e.g.,  mercurial or git On mercurial, it is still possible to see the diff if there is more than one file changed, but in git it is not possible to see anything. Even in mercurial, if the diff consists of only one file, it is also not possible to see any diff.
Comment 1 Marcelo Jimenez 2024-12-05 22:29:23 UTC
Some more info.

- I just built from the git repo, version 1.11.70 and master does not contain the bug.
- I did a bisect and the commit that fixes the problem is 7c598f336ec36ee6534098491b11db563ea6e2b3
- The commit title is "Fix starting with command line parameters"
- It is an incredibly simple three-liner by C. Balles, so please, do consider applying it.
Comment 2 michael 2024-12-06 22:33:43 UTC
1.12.0 will have the fix just tagged the release. Will be uploaded in 24 to 48 hrs,

*** This bug has been marked as a duplicate of bug 486782 ***