Bug 18570

Summary: Ktorrent warns on permissions but works (upgraded from mga5)
Product: Mageia Reporter: Morgan Leijström <fri>
Component: RPM PackagesAssignee: KDE maintainers <kde>
Status: RESOLVED OLD QA Contact:
Severity: minor    
Priority: Normal CC: mageia, marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: ktorrent-5.0.1-1.mga6.src.rpm CVE:
Status comment:

Description Morgan Leijström 2016-05-28 15:46:53 CEST 
System is 64 bit, was upgraded online from mga5 to cauldron a couple weeks ago.
It was seeding a few mageia isos and continue doing that again now :)

Starting ktorrent it pops up an error message it could not create
/home/myuser/.local/share/ktorrent/tor5/torrent:  Permission denied

klicking OK there it pops up a new message with increased number: 
/home/myuser/.local/share/ktorrent/tor6/torrent:  Permission denied

But then it works OK.

In /home/myuser/.local/share/ktorrent i see seven tor* folders tor0 .. tor6
tor5 and tor6 have date 2016-05-17, while the OK folders updates to current time.
However the times of three files in also the tor5 and tor6 update to current time and everything seem to work.

The permissions all look the same, same owner (me) and rights, except for the files "torrent"n the problematic folders have rights set to -r-------- whereas in the OK folders they are set -rw-r--r--  weird.

Local fix: 
§ chmod 644 torrent
in the problematic folders.

This issue seems weird, and it may be special and transient.
I suggest not spend time on it until someone else report they see similar problem
Morgan Leijström 2016-05-28 16:23:47 CEST

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Marja Van Waes 2016-05-29 17:20:25 CEST

Assignee: bugsquad => mageia
CC: (none) => marja11

Samuel Verschelde 2016-08-25 16:24:30 CEST

Assignee: mageia => kde

Comment 1 Nicolas Lécureuil 2017-03-18 01:43:04 CET 
is it still valid with current cauldron ?

CC: (none) => mageia

Comment 2 Morgan Leijström 2017-04-02 15:07:00 CEST 
Dont know how to test reliably... 
as noone else seem to have seen it, let it be unconfirmed or close as old...
Comment 3 Aurelien Oudelet 2021-05-17 01:15:38 CEST 
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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