Bug 327809 - Fetch groups - unable to write group lists file
Summary: Fetch groups - unable to write group lists file
Status: RESOLVED WORKSFORME
Alias: None
Product: knode
Classification: Miscellaneous
Component: general (show other bugs)
Version: 4.11.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-19 12:32 UTC by Alan Prescott
Modified: 2013-12-28 00:43 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Prescott 2013-11-19 12:32:25 UTC
Every time I attempt to fetch a list of groups from usenet.plus.net:119 I get the error message
"Unable to write groups list file"

Reproducible: Always

Steps to Reproduce:
1. RMB on existing account and select Subscribe to newsgroups
2. Accept option to load the list of groups
3.
Actual Results:  
Error message "Unable to write groups list file"
Comment 1 Alan Prescott 2013-12-14 08:30:05 UTC
Running from CLI as `knode --nofork` produces:-
 
knode(3116) KNGroupListData::writeOut: unable to open "/home/alan/.kde4/share/apps/knode/nntp.1/groups"  reason 5 

"/home/alan/.kde4/share/apps/knode/nntp.1" is owned by user alan (me) and I have rwx access to it.

Just for the hell of it I've gone into /home/alan/.kde4/share/apps/knode/ and run
find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 640 {} \;
chown -R alan:Number9 *

and still get the same result from knode
Comment 2 Alan Prescott 2013-12-14 09:53:51 UTC
Ok - this appears to be something to do with my home folder being a CIFS mounted share.

I can create any file I want in the nntp.1 folder EXCEPT 'groups' (XXX, groupsX etc. all work Ok). If I log onto the CIFS server I can create the file but it doesn't show up on the client mount.  Why just the one file name I haven't worked out.
I've switched from cifs to nfs and now knode works Ok

I only used CIFS because nfs was causing a lot of spurious I/Os on the file server - something to do with encrypted fs I believe. When I have the opportunity to upgrade the server maybe that'll sort nfs out. Meanwhile I'll close this bug