Closing due to age.
If a similar problem appears in 13.04 please open a new bug report.
** Changed in: file-roller (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad
Hello DeMus, you might want to send this upstream to bugzilla.gnome.org
since you're getting the issue there, I've tested file-roller with a few
big files and i don't see any issue here. For instructions on how to
forward the report upstream please have a look to
https://wiki.ubuntu.com/Bugs/Upstre
Hi Pedro,
The answer to your question is yes and no. I don't see any changes in
Karmic with respect to Jaunty, the speed is (about) the same. What I did
notice is this:
It is not the processor which determines the speed with which
File-roller operates, it is the harddisk. The data throughput of
is this still an issue on karmic?
** Changed in: file-roller (Ubuntu)
Status: New => Incomplete
--
File-roller makes computer unresponsive
https://bugs.launchpad.net/bugs/420904
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
** Changed in: file-roller (Ubuntu)
Status: Incomplete => New
--
File-roller makes computer unresponsive
https://bugs.launchpad.net/bugs/420904
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
deskto
Hi,
Thanks for answering upon my bug report.
I'll try to answer the questions as well as possible.
Yes, it is reproducible. It happens every time when I want to unrar a
row of joined rar files (xxx1.rar, xxx2.rar, , xxxn.rar, but also
with xxx.rar, xxx.r01, xxx.r02, ... , xxx.r0n).
The cpu
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: file-roller (Ubu
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
https://wiki.ubuntu.com/Bug
