Bug 28956 - k3b loses files when more than 199 files are in a directory.
Summary: k3b loses files when more than 199 files are in a directory.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-22 01:01 CEST by Ken Arromdee
Modified: 2024-08-22 23:01 CEST (History)
4 users (show)

See Also:
Source RPM: k3b-20.12.0-1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Ken Arromdee 2021-05-22 01:01:31 CEST
Description of problem: 
k3b loses files when more than 199 files are in a directory.

Version-Release number of selected component (if applicable):
20.12.0

How reproducible:
Always

Steps to Reproduce:
1.Create a data project in k3b
2."Add to Project" a folder containing 217 files
3. Observe that 18 files are added
4. Repeat with direcotres containing other numbers of files greater than 199.

I reported this bug for k3b at https://bugs.kde.org/show_bug.cgi?id=437451 but it was closed as fixed in a newer version.  I think this should be part of a Mageia update because it can cause data loss.
Comment 1 Aurelien Oudelet 2021-05-23 20:13:32 CEST
Closed upstream as Resolved Fixed according to:
> Albert Astals Cid 2021-05-21 20:27:26 UTC
>
> Update to 21.04.0

A candidate to upgrade KDE/Plasma stack.

Status: NEW => UPSTREAM
CC: (none) => ouaurelien

Comment 2 Morgan Leijström 2021-05-23 23:58:57 CEST
Thank you for reporting.
I see a commit pointed out in upstream link.
Assigning to KDE team.

CC: (none) => fri
Assignee: bugsquad => kde

Comment 3 Tóthpál István 2023-02-02 14:58:30 CET
Hi,

I see there will be an update,
I just would like to link my report about the similar problem:
https://forums.mageia.org/en/viewtopic.php?f=7&t=14848

CC: (none) => tistis73

Comment 4 David GEIGER 2023-02-04 09:08:19 CET
Should be fixed in upcoming k3b-20.12.0-1.1.mga8 in Core/Updates_testing repo!

Please test it.

CC: (none) => geiger.david68210

Comment 5 Tóthpál István 2023-02-04 11:53:49 CET
Hi, 

I've mad a fast test only about this error.
I have removed old rpms:
febr 04 11:12:01 localhost [RPM][56393]: Transaction ID 63de2f71 started
febr 04 11:12:04 localhost [RPM][56393]: erase k3b-4:20.12.0-1.mga8.x86_64: success
febr 04 11:12:04 localhost [RPM][56393]: erase lib64k3blib7-4:20.12.0-1.mga8.x86_64: success
febr 04 11:12:04 localhost [RPM][56393]: erase lib64k3bdevice7-4:20.12.0-1.mga8.x86_64: success
febr 04 11:12:30 localhost [RPM][56393]: Transaction ID 63de2f71 finished: 0


(as I haven't installed the version I've compiled it cannot reached e.g. the rc files, but looked it is also workable, maybe have to install...)

I have installed new ones from GUI package manager, after I've added Test repo:
febr 04 11:38:18 localhost [RPM][167627]: Transaction ID 63de359a started
febr 04 11:38:21 localhost [RPM][167627]: install lib64k3bdevice7-4:20.12.0-1.1.mga8.x86_64: success
febr 04 11:38:21 localhost [RPM][167627]: install lib64k3blib7-4:20.12.0-1.1.mga8.x86_64: success
febr 04 11:38:22 localhost [RPM][167627]: install transcode-1.1.7-29.2.mga8.tainted.x86_64: success
febr 04 11:38:23 localhost [RPM][167627]: install k3b-4:20.12.0-1.1.mga8.x86_64: success
success
febr 04 11:38:54 localhost [RPM][167627]: Transaction ID 63de359a finished: 0

I can run this version, and if I add folders to project as previously, it looks it done well. I've tried to add same photo folders and drupal too, no files were skipped...

So I haven't written anything yet, just focused on the error I have realized, and looks that is repaired in this version...
Ty
Comment 6 David GEIGER 2023-02-05 06:00:18 CET
Updated packages in core/updates_testing:
========================
libk3blib7-20.12.0-1.1.mga8
lib64k3blib7-20.12.0-1.1.mga8
libk3bdevice7-20.12.0-1.1.mga8
lib64k3bdevice7-20.12.0-1.1.mga8
k3b-devel-20.12.0-1.1.mga8
k3b-20.12.0-1.1.mga8

from SRPMS:
k3b-20.12.0-1.1.mga8.src.rpm

Assignee: kde => qa-bugs

Comment 7 Marja Van Waes 2024-08-22 23:01:35 CEST
We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

Status: UPSTREAM => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.