From: Michael Sullivan <msulli1355@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] [Possibly OT] rile-roller having problems with deletions after upgrade to 3* series kernel
Date: Fri, 25 May 2012 23:49:28 -0500 [thread overview]
Message-ID: <4FC060D8.10303@gmail.com> (raw)
Each night (at midnight) I make backups of files that changed the
previous day, and on the first of the month I make full backups of
important directories (/home, /etc, etc etc). Each morning I do
maintenance on the partial backup from the day before. I've noticed
that since I upgraded to the 3* series kernel (at this moment it's
3.2.12) I've had problems with file-roller - I tell it to delete a
directory (something I consider nonessential like ~/.thumbnails) and I
says "Reading archive..." without actually deleting anything. I've
found that I can delete ten files at a time, which can be really
inconvenient when there are hundreds of nonessential files I need to
delete. I don't think it's tar - I can go into my terminal window and
delete all the files I want with tar and it works perfectly; it just
seems to be file-roller. Has anyone else experienced this?
reply other threads:[~2012-05-26 4:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FC060D8.10303@gmail.com \
--to=msulli1355@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox