I have always in my “Documents” a folder named “Writer’s Cafe Documents”. It’s empty. I have deleted it several times, but it reappears always.
I have never installed such application, as far as I can remember or know.
Does anybody know how to get rid of that folder forever?
I just checked my Documents folder and there is no such entry.
Is this “Writer’s Cafe” folder present for you after a new, standard installation?
On 07/06/2013 01:16 PM, wrbbt wrote:
>
> I have always in my “Documents” a folder named “Writer’s Cafe
> Documents”. It’s empty. I have deleted it several times, but it
> reappears always.
> I have never installed such application, as far as I can remember or
> know.
> Does anybody know how to get rid of that folder forever?
>
>
sounds like someone (maybe not you) installed a program called
Writer’s Cafe http://www.writerscafe.co.uk/ and apparently
either left it installed, or left some parts of it installed though
an incomplete uninstall (and what is left is trying to run and each
time it does i recreates that directory…
you might try this, in a user terminal
which writerscafe
rpm -qa | grep writercafe
cat /var/log/zypp/history | grep writercafe
and please copy/paste the in/output back to this thread using the
instructions here: http://goo.gl/i3wnr
No output whatsoever.
wrbbt:~> which writerscafe
which: no writerscafe in (/home/wrbbt/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games)
wrbbt:~> rpm -qa | grep writerscafe
wrbbt:~> cat /var/log/zypp/history | grep writerscafe
Anyway, I have found a *~/.Writer’s Cafe Documents
*this one was in ~ the one I referred in my first post was in ~/Documents and not hidden.
Appart from that, the one in ~/Documents was empty, and the one in ~ was not.
I have deleted both. Let’s see if this is enough.
Thanks.
On 2013-07-06 15:56, wrbbt wrote:
>
> No output whatsoever.
Try changing to “grep -i …”
Try also with “locate writecafe”, assuming locate is installed. If not,
you will have to try with ‘find’.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
After my last post I tried “locate Cafe” and had some output
wrbbt:~> locate Cafe
/home/wrbbt/.config/writerscafe2
I have deleted that folder too.
Let’s hope this is enough.
Thank you.
No way. The folder is always there. I don’t know who creates it every time the computer starts up.
It seems that there is no other file related to this
wrbbt:~> locate Cafe
/home/jds/Documents/Writer's Cafe Documents
Finally I decided to add a line in .bashrc
/bin/rm -r ~/Documents/Writer\'s\ Cafe\ Documents
Maybe it’s not a good solution, but I was already annoyed with that folder.
On 2013-07-12 10:46, wrbbt wrote:
>
> No way. The folder is always there. I don’t know who creates it every
> time the computer starts up.
There is a method with Apparmor to block certain files, If there is a
write attempt, the application that does it is denied access, and the
event is reported.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
That’s no solution at all. What else is the thing that’s doing this doing. Go through the autostart folders, check your ~/bin, check the services in Yast. Like said, something is causing this, and it might do other things. Also check running processes
Thank you, Knurpht. I have checked all those things and found nothing odd. Maybe my knowledge is not enough to detect the problem.
Anyway, I don’t think that folder (or the process that creates it) may cause any damage because this has been going on for quite a number of months and I have noticed nothing strange (apart from the folder itself). It’s only that I ended up getting annoyed with that folder that shows up everyday.
Of course, any other idea will be welcome.
locate is case-sensitive. So try this as well:
locate cafe
or
locate -i cafe
(’-i’ means “ignore case”)
Good idea!
I tried
locate -i cafe | grep -i writer
and found a couple of cookies. I removed them.
Don’t know if that will be enough.
Thanks
On 2013-07-12 17:16, wrbbt wrote:
>
> Knurpht;2571335 Wrote:
>> That’s no solution at all. What else is the thing that’s doing this
>> doing. Go through the autostart folders, check your ~/bin, check the
>> services in Yast. Like said, something is causing this, and it might do
>> other things. Also check running processes
>
> Thank you, Knurpht. I have checked all those things and found nothing
> odd. Maybe my knowledge is not enough to detect the problem.
> Anyway, I don’t think that folder (or the process that creates it) may
> cause any damage because this has been going on for quite a number of
> months and I have noticed nothing strange (apart from the folder
> itself).
What Knurpht says, I think, is that you don’t know what else that
process does.
> Of course, any other idea will be welcome.
Look at the AA idea I mentioned.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Thanks again.
I understood it. That’s why I said “I don’t think that folder (or the process that creates it) may cause any damage because this has been going on for quite a number of months and I have noticed nothing strange (apart from the folder itself).”
Anyway, I know you are right, because the cause of the creation of that folder remains unknown.
I know almost nothing about apparmor. I’ve gone through some documentation. If I got it right, to create a profile the first thing I should know is the application the profile is about. But that is exactly which I ignore. Can you help me in this?
On 2013-07-13 09:46, wrbbt wrote:
> I know almost nothing about apparmor. I’ve gone through some
> documentation. If I got it right, to create a profile the first thing I
> should know is the application the profile is about. But that is exactly
> which I ignore. Can you help me in this?
I was waiting to know if you wanted to try it before describing, it was
not my intention you find the trick reading the manual - I did not myself.
The trick, as described by Cristian Rodríguez in a 2009 post (a known
dev) is basically this:
auditctl -w /pathto/file -p awx
auditctl -e 1
Manual:
-p [r|w|x|a]
Describe the permission access type that a file
system watch will trigger on. r=read, w=write,
x=execute, a=attribute change. These permissions
are not the standard file permissions, but rather
the kind of syscall that would do this kind of
thing. The read & write syscalls are omitted from
this set since they would overwhelm the logs. But
rather for reads or writes, the open flags are
looked at to see what permission was requested.
-e [0..2]
Set enabled flag. When 0 is passed, this can be
used to temporarily disable auditing. When 1 is
passed as an argument, it will enable auditing.
To lock the audit configuration so that it can't
be changed, pass a 2 as the argument. Locking the
configuration is intended to be the last command
in audit.rules for anyone wishing this feature to
be active. Any attempt to change the configura-
tion in this mode will be audited and denied. The
configuration can only be changed by rebooting
the machine.
then you have to look at the logs to find out a permission denied.
However.
You have to run that before you log into your session. I suggest you
switch to a text console right after boot (or boot to level 3), log in
as root there, run those two commands, then switch back to graphical
mode (or init 5), and log in as your user there. See if the directory is
created (or not) and have a careful look at /var/log/messages or
/var/log/audit/audit.log.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Thanks. I’ll try and let you know.
Sorry for my ignorance, but if I try to run those comands in run level 3 or in a console the answer is command not found. I have tried to install it but I didn’t manage to know what package I have to install.
I have found it! I’ll try now what you said.
On 2013-07-13 16:56, wrbbt wrote:
> Sorry for my ignorance, but if I try to run those comands in run level
> 3 or in a console the answer is command not found. I have tried to
> install it but I didn’t manage to know what package I have to install.
It is “apparmor-utils” and probably some dependencies as well.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
In the last days, the folder didn’t appear any more. And also no messages in the logs you (Carlos) mentioned.
So, I suppose that deleting the cookies I referred to in post #12 is what made the trick. Could it be?