Your message dated Sun, 3 May 2026 22:30:59 +0200
with message-id <[email protected]>
and subject line Re: Bug#1127368: kicad: KiCad changes files without reason or
authorization
has caused the Debian Bug report #1127368,
regarding kicad: KiCad changes files without reason or authorization
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1127368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127368
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kicad
Version: 9.0.6+dfsg-1
Severity: normal
KiCad changes files without reason or authorization.
Steps to reproduce:
* Open a KiCad file
* Double click on an element to see details
* Close the file
* --> KiCad asks if the changes should be saved, although nothing was
changed.
* --> User clicks "Discard" to prevent changing the file anyway.
* --> The file gets changed (new timestamp), although KiCad was told to
not
change it.
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: arm64 (aarch64)
Kernel: Linux 6.17.11+deb14-arm64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages kicad depends on:
ii libc6 2.42-5
ii libcairo2 1.18.4-3
ii libcurl4t64 8.17.0-3
ii libfontconfig1 2.17.1-3
ii libfreetype6 2.13.3+dfsg-1
ii libgcc-s1 15.2.0-11
ii libgit2-1.9 1.9.1+ds-1
ii libgl1 1.7.0-1+b2
ii libglew2.2 2.2.0-4+b2
ii libglib2.0-0t64 2.86.3-1
ii libglu1-mesa [libglu1] 9.0.2-1.1+b4
ii libgtk-3-0t64 3.24.51-4
ii libharfbuzz0b 12.3.1-1
ii libngspice0 45.2+ds-1
ii libnng1 1.11-1
ii libocct-data-exchange-7.8 7.8.1+dfsg1-7
ii libocct-foundation-7.8 7.8.1+dfsg1-7
ii libocct-modeling-algorithms-7.8 7.8.1+dfsg1-7
ii libocct-modeling-data-7.8 7.8.1+dfsg1-7
ii libocct-ocaf-7.8 7.8.1+dfsg1-7
ii libodbc2 2.3.14-1
ii libprotobuf32t64 3.21.12-14+b1
ii libpython3.13 3.13.11-1+b1
ii libsecret-1-0 0.21.7-2
ii libstdc++6 15.2.0-11
ii libwxbase3.2-1t64 3.2.8+dfsg-2
ii libwxgtk-gl3.2-1t64 3.2.8+dfsg-2
ii libwxgtk3.2-1t64 3.2.8+dfsg-2
ii libzstd1 1.5.7+dfsg-2
ii python3 3.13.9-3
ii python3-wxgtk4.0 4.2.4+dfsg-1
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
Versions of packages kicad recommends:
ii kicad-demos 9.0.6+dfsg-1
ii kicad-libraries 9.0.6+dfsg-1
ii xsltproc 1.1.43-0.3
Versions of packages kicad suggests:
pn extra-xdg-menus
<none>
pn kicad-doc-ca | kicad-doc-de | kicad-doc-en | kicad-doc-es | kicad-d
<none>
oc-fr | kicad-doc-id | kicad-doc-it | kicad-doc-ja | kicad-doc-pl |
kicad-doc-ru | kicad-doc-zh
pn kicad-packages3d
<none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Matthias,
I'll close the report now as no feedback was ever given.
Am 15.03.26 um 10:21 schrieb Carsten Schoenert:
Hello Matthias,
Am 07.02.26 um 14:28 schrieb Matthias Brennwald:
KiCad changes files without reason or authorization.
Steps to reproduce:
* Open a KiCad file
* Double click on an element to see details
* Close the file
* --> KiCad asks if the changes should be saved, although nothing was
changed.
* --> User clicks "Discard" to prevent changing the file anyway.
* --> The file gets changed (new timestamp), although KiCad was told to not
change it.
Has the content of the file changed? I guess no.
If not than the behavior isn't issue and a normal thing that is happen
due how filesystems do work.
An example.
Given we create a new file 'testfile.txt' and we look at the low level
file properties which are created by the tool stat.
$ echo -e "Current time: $(date '+%F %H:%M:%S.%N')\n" && echo "test data" >
testfile.txt && LANG= stat testfile.txt
Current time: 2026-03-15 10:04:20.999735307 <--- The output of the date call.
File: testfile.txt <--- The output of the stat command.
Size: 10 Blocks: 8 IO Block: 4096 regular file
Device: 259,3 Inode: 1713991 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 1000/ carsten) Gid: ( 1000/ carsten)
Access: 2026-03-15 10:04:20.997852751 +0200
Modify: 2026-03-15 10:04:20.997852751 +0200
Change: 2026-03-15 10:04:20.997852751 +0200
Birth: 2026-03-15 10:04:20.997852751 +0200
You can see the file is created with four dedicated values about
different times. As the file was just created all the parameters have
the same timestamp!
Now do just using the cat command, means we will read the file.
$ echo -e "Current time: $(date '+%F %H:%M:%S.%N')\n" && cat testfile.txt &&
LANG= stat testfile.txt
Current time: 2026-03-15 10:04:49.073065930
test data
File: testfile.txt
Size: 10 Blocks: 8 IO Block: 4096 regular file
Device: 259,3 Inode: 1713991 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 1000/ carsten) Gid: ( 1000/ carsten)
Access: 2026-03-15 10:04:49.071198334 +0200 <-----
Modify: 2026-03-15 10:04:20.997852751 +0200
Change: 2026-03-15 10:04:20.997852751 +0200
Birth: 2026-03-15 10:04:20.997852751 +0200
The timestamp has only changed for the Access entry as it was a read
only access.
Now open the file in a editor, change nothing but save the file while
closing.
$ echo -e "Current time: $(date '+%F %H:%M:%S.%N')\n" && LANG= stat testfile.txt
Current time: 2026-03-15 10:07:46.117659114
File: testfile.txt
Size: 10 Blocks: 8 IO Block: 4096 regular file
Device: 259,3 Inode: 1713991 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 1000/ carsten) Gid: ( 1000/ carsten)
Access: 2026-03-15 10:05:07.320072273 +0200 <-----
Modify: 2026-03-15 10:05:05.683993944 +0200 <-----
Change: 2026-03-15 10:05:05.687994136 +0200 <-----
Birth: 2026-03-15 10:04:20.997852751 +0200
Now it is visible that the timestamp for the Access, Modify and Change
has been changed. But the content is still the same.
If you still think the behavior is a bug you will need to address this
issue upstream, Debian is not doing any special things, we do just
package the upstream data with just some minor modifications about the
apptsream data and the string of the Release version.
Further information can be found also here.
https://linuxconfig.org/check-file-access-and-modification-time-in-linux
--
Mit freundlichen Grüßen
Carsten Schönert
--- End Message ---
