#172 closed defect (fixed)
Difficult to fix a journal filled by downloading
| Reported by: | lod | Owned by: | tomeu |
|---|---|---|---|
| Priority: | Urgent | Milestone: | |
| Component: | journal | Version: | 0.82.x |
| Severity: | Critical | Keywords: | |
| Cc: | bernie | Distribution/OS: | Unspecified |
| Bug Status: | New |
Description
I'm downloading a sizeable file and ran out of journal space.
I got an error message which states that the journal is full and offering to show the journal (there's no other option).
When the journal comes up I have about a second to take some kind of action before the error message reappears and takes over the screen.
I was downloading a file off a local http server using the browse activity.
Workaround: Press the show journal button and while the screen is redrawing start tapping on the stop download button. There's not enough time to right click and delete a file.
I am using build 767 on an XO.
Change History (8)
comment:1 Changed 15 years ago by gregdek
- Bug Status set to New
- Distribution/OS set to Unspecified
- Milestone set to 0.84
- Priority changed from normal to High
- Severity set to Major
comment:2 follow-up: ↓ 3 Changed 15 years ago by tomeu
Yes, the strategies for checking if we are running tight of space doesn't work well with a single download filling everything.
Perhaps the best we can do for now is to tell Browse to interrupt a download before things get too bad?
comment:3 in reply to: ↑ 2 Changed 15 years ago by tomeu
comment:4 Changed 15 years ago by erikos
- Milestone changed from 0.84 to 0.86
comment:5 Changed 13 years ago by bernie
- Cc bernie added
- Priority changed from High to Urgent
- Severity changed from Major to Critical
This bug is very common in the field. It should be made top-priority.
comment:6 Changed 13 years ago by RafaelOrtiz
Still happening (also in dextrose). In general is difficult to recover a full journal.
comment:7 Changed 10 years ago by godiard
- Resolution set to fixed
- Status changed from new to closed
Now browse stop downloading a file if available space is lower than 50MB.
Seems to me like this is an important bug -- has anyone seen this? A perfect example of a corner case that no one finds until too late. :)