this is fixed in tbird 3 ... temp files are now read-only.
** Changed in: thunderbird (Ubuntu)
Status: New => Fix Released
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because you are a member of Ubunt
No more fixes for Firefox 2.
** Changed in: firefox (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: firefox (Ubuntu)
Assignee: Alexander Sack (asac) => (unassigned)
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received th
** Also affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Also affects: thunderbird (Baltix)
Importance: Undecided
Status: New
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification
adding firefox-3.0 task as fix released to document that this is fixed
in ffox 3.
** Also affects: firefox-3.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: firefox-3.0 (Ubuntu)
Status: New => Fix Released
--
Users should be discouraged from editing temporary files
we have a patch for this in thunderbird. we should try to get this
applied upstream.
** Changed in: firefox (Ubuntu)
Status: In Progress => Triaged
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because
Yes it is fixed in firefox 3. I was very pleased to see that.
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
My mistake. Source package for firefox-2 is firefox. Reopening the task.
Sorry.
** Changed in: firefox (Ubuntu)
Status: Fix Released => In Progress
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because
This is fixed in Firefox 3, but is still present in Firefox 2. Opening
task for firefox-2 package.
** Changed in: firefox (Ubuntu)
Status: Triaged => Fix Released
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notifi
Seems to be fixed.
By the look of it, firefox now marks things in /tmp read only.
Thank goodness for that.
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because you are a member of Ubuntu
Bugs, which is a dire
** Tags removed: likely-dup
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Okay, somebody put a bounty on this. How much is it going to cost me?
Endless frustration isn't a cost I'm going to accept.
So what'll it be? $50? $100? What do I have to pay to not have edited
documents getting wiped out with no warning?
Let's see.. assuming that 7 hours of work have been los
This is an old issue.. but I have some new information
The problem is also present in IE.. BUT with a work around.
HKCR\Excel.Sheet.5\BrowserFlags
HKCR\Excel.Sheet.8\BrowserFlags
HKCR\Word.Document.6\BrowserFlags
HKCR\Word.Document.8\BrowserFlags
HKCR\MSProject.Project.8\BrowserFlags
HKCR\Pow
Sounds good to me :)
Could you do the read only thing with an extension?
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs ma
Firefox should have in its preferences a checkbox to "make files opened from
the web read-only" and that box should be ticked by default.
There should also be a way to set the directory where it downloads stuff opened
(as oposed to saved) and the default should be /tmp
You can't save a read-only
Checkout my comment above, the provided suggestion fixes the deletion part of
the problem for all programs saving downloaded stuff in /tmp:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/15179/comments/11
However it is a bit controversial so you are at your own, it works for
me though.
My dad spent four hours yesterday working on an extremely important
document firefox ->open with ->open office, being very sure to hit
'save' very often, as this was a _VITAL_ document. Turns out, it got
put in /tmp and wiped. His confidence in both Ubuntu and OpenOffice is
completely gone, and h
** Changed in: firefox (Ubuntu)
Assignee: Mozilla Bugs => Alexander Sack
Status: Confirmed => Triaged
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Sat, Sep 01, 2007 at 01:29:57PM -, Jeroen van Splunder wrote:
> Please do NOT save all files which firefox downloads when you choose
> 'open' outside of /tmp. The reason you can choose behind 'open' and
> 'save to disk' is obvious: you don't want to keep stuff you 'open'. If a
> file is open
Please do NOT save all files which firefox downloads when you choose
'open' outside of /tmp. The reason you can choose behind 'open' and
'save to disk' is obvious: you don't want to keep stuff you 'open'. If a
file is opened by a user and he changes his mind (and edits anyway),
however, he should b
True enough ... maybe the options should change. Instead of "Open with ..."
and "Save to Disk", there should be: "Open with ...", "Save, and open with
...", and "Save".
Interestingly, I recently found out my mom didn't want to pick "Save to
Disk" because she associated "disk" with needing a flopp
On Mon, May 28, 2007 at 12:08:35AM -, Sean Kennedy wrote:
> Perhaps adding something to the download dialog (where you pick to open it
> with an application or save to disk) saying that unless the file is saved to
> another location, that it will be deleted when the computer is shut down
> woul
Perhaps adding something to the download dialog (where you pick to open it
with an application or save to disk) saying that unless the file is saved to
another location, that it will be deleted when the computer is shut down
would be sufficient.
That, at least, would warn the user, if they read the
Because sometimes they download something, and expect to be able to find it
later ...
I think this is how a desktop background got disappeared in one case.
On 15/05/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
> On Tue, May 15, 2007 at 04:15:50PM -, Sean Kennedy wrote:
> > Yes, I think the
On Tue, May 15, 2007 at 04:15:50PM -, Sean Kennedy wrote:
> Yes, I think the general Downloads dir would get too crowded.
> What about a personal downloads directory (like was originally proposed),
> say ~/.webfiles or ~/.firefox/webfiles? Things downloaded to this directory
> should be saved
Yes, I think the general Downloads dir would get too crowded.
What about a personal downloads directory (like was originally proposed),
say ~/.webfiles or ~/.firefox/webfiles? Things downloaded to this directory
should be saved read-only so the user will be prompted to save the file
somewhere else
we could download to default Downloads dir ... this of course might
produce garbage if you just want to look at read-only docs like pdf.
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because you are a member of
On Mon, May 14, 2007 at 03:05:48PM -, Phil Bull wrote:
> Mozilla upstream didn't reject the bug, the bug was rejected in the
> Firefox product on Launchpad, which is technically upstream of the
> Ubuntu/Firefox product. It's a particularly confusing feature of
> Launchpad's.
>
> I don't even t
Mozilla upstream didn't reject the bug, the bug was rejected in the
Firefox product on Launchpad, which is technically upstream of the
Ubuntu/Firefox product. It's a particularly confusing feature of
Launchpad's.
I don't even think that a bug has been filed for this in the Mozilla bug
tracker. Wou
I can't find the Moziall bug either ...
We need to know why they have rejected the bug, but if they aren't going to
fix it, Ubuntu should. Losing a file destroys the user's confidence in the
system.
On 14/05/07, seanh <[EMAIL PROTECTED]> wrote:
>
> Agreed, I don't really see the justification fo
Agreed, I don't really see the justification for this begin "medium".
People lose essays etc., it is a usability issue leading to data loss.
Is there any way to to get a link to the upstream bug report at firefox
bugzilla through launchpad? I'd be interested to see why they rejected
it. (I searche
** Changed in: firefox (upstream)
Status: Unconfirmed => Rejected
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mai
I've just had a user lose data due to this issue. As this is a data-loss
bug, I would recommend increasing the severity of it.
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because you are a member of Ubuntu
Bu
anyone has bugzilla.mozilla.org bug id for this?
Thanks,
- Alexander
** Tags added: mt-upstream
** Tags added: likely-dup
--
Users should be discouraged from editing temporary files
https://bugs.launchpad.net/bugs/15179
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: firefox (Ubuntu)
Assignee: Mozilla Team => Mozilla Bugs
--
Users should be discouraged from editing temporary files
https://launchpad.net/bugs/15179
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
OK thanks, I think this report contains enough information to go
upstream. For now I add an empty remote bug reference to indicate this.
Next submission round, this will go up.
** Also affects: firefox (upstream)
Importance: Undecided
Status: Unconfirmed
--
Users should be discouraged
How about storing them in
${FIREFOX_DOWNLOAD_DIR}/${USERNAME}AutomaticDownloads by default? (e.g:
/home/sean/Downloads/seanAutomaticDownloads)
Also, let the user specify where the AutoDownloads directory should go ...
maybe some people want to set it as /tmp. (e.g.
/tmp/seanAutomaticDownloads)
"
So where is the best place to store these files to? $HOME, $DESKTOP? or
even some temp/ folder somewhere in the users profile dir?
--
Users should be discouraged from editing temporary files
https://launchpad.net/bugs/15179
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Mozilla Bugs
--
Users should be discouraged from editing temporary files
https://launchpad.net/bugs/15179
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
No problem, don't forget to open bug reports for all other affected GUI
apps also then. If MOTU decides to fix this I'd prefer the read-only
permission solution on files saved by GUI apps using helper apps. I
guess it could work in most cases by just changing the 'umask' in the
right place when st
Changing package back to firefox based on comments by me, Snark, Murray
Cumming, jhasse, Eric Feliksik and seanh.
** Changed in: sysvinit (Ubuntu)
Sourcepackagename: sysvinit => firefox
--
Users should be discouraged from editing temporary files
https://launchpad.net/bugs/15179
--
ubuntu-bugs
I think this is a Firefox bug. Firefox should discourage storing user
files to /tmp directory, just like other programs do.
I am against the hackish fix by making temporary files non-temporary by
some arbitrary permission criteria. Even though I think it's a nice
temporary hack, it's probably not
Removing files in the _temporary_ directory isn't "behind users' back",
so it's better : you claim something, you stick to it.
Why not make applications save those files readonly? That way the user
will not write to them.
--
Users should be discouraged from editing temporary files
https://launch
Murray:
I agree that some people may consider the aproach a bit harsh but compared to
fixing lots of userspace application that is used as helperapps for archivers,
browsers and such I think it is worth some consideration.
Fixing this is in a lot of applications will introduce more bugs and we
Moving files behind the user's back is a very bad practice.
Doing so looking at their permissions is fragile.
My two eurocents.
--
Users should be discouraged from editing temporary files
https://launchpad.net/bugs/15179
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
I don't think it's a good idea to pretend that this really fixes the
issue, so I'd prefer us not to pretend that it does.
Maybe it's a suitable temporary fix. Someone more expert than me should
judge whether the pros outweight the cons. I'd imagine that some people
might see this as breaking the t
Well, it is simple change to 'allow' people to do this without loosing
their work and the discouragement lies in the extra effort to pick the
file up from the personal garbage bin rather than from /tmp. A
preference could control this behaviour of sysvinit to be turned on or
off.
I guess your poin
How would the change in sysvinit discourage people from editing
temporary files?
--
Users should be discouraged from editing temporary files
https://launchpad.net/bugs/15179
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Changed to sysvinit since the root cause is not application (ie Firefox)
specific
** Changed in: firefox (Ubuntu)
Sourcepackagename: firefox => sysvinit
--
Users should be discouraged from editing temporary files
https://launchpad.net/bugs/15179
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
OK, this works for me: I just changed the /etc/init.d/bootclean
[EMAIL PROTECTED]:/etc/init.d$ diff bootclean.sh bootclean.sh~
63c63
< ! -perm 644 ! -type d -print0 | xargs -0r rm -f
---
> ! -type d -print0 | xargs -0r rm -f
to not remov
For some reason the documents saved from the web in Firefox for instance
are saved with a 600 permission while when saved from Open Office they
get 644 permission. Personally, that just lost half a day of work, I
will install a filter copying all files in /tmp with my user and 644
permission to $HO
I commented the following to the blog post :
<>
--
Users should be discouraged from editing temporary files
https://launchpad.net/bugs/15179
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have come across this issue also, I've seen people lose essays on
Ubuntu this way and have to start them again. In fact, this is a very
serious usability issue because:
1. It can result in data loss, including complete loss of important
data, such as an entire essay.
2. Most users will fall int
P.S. I don't know how to do this, but I think this bug report should be
linked to GtkFileChooser as well as or instead of Firefox, as I think
the file chooser is where the correct fix resides.
--
Users should be discouraged from editing temporary files
https://launchpad.net/bugs/15179
--
ubuntu
I think Tero Karvinen's solution of patching gtkFileChooser is
excellent:
[quote]
When the "File: Save as" dialog is shown:
1) Check if "Save in folder" is /tmp/ or /var/tmp/
2) If yes, change the "Save in folder" to $HOME
In Evince pdf document viewer, it is already solved like this.
In the high
** Changed in: firefox (Ubuntu)
Assignee: Ian Jackson => (unassigned)
--
Users should be discouraged from editing temporary files
https://launchpad.net/bugs/15179
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
55 matches
Mail list logo
