hangs when saving to encrypted hard drive

Bug #674350 reported by Mr. Morfoos
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qBittorrent
New
Undecided
Unassigned

Bug Description

I discovered this recently. When I set save location on encrypted partition or encrypted external USB drive, qbittorrent hangs and uses 100% CPU. I can't end qbittorrent process. I can't even kill it. It becomes zombie but, uses 100 % still.

Revision history for this message
Mr. Morfoos (am1) wrote :

Hmmm... interesting. Transmission does the same thing. This is probably a kernel bug in ubuntu.

Revision history for this message
Kern3l (kern3l) wrote :

I'm having the same problem. Thanks for tips on location - I didn't know that it hangs only on encrypted (I have whole /home enc.) ;]

Revision history for this message
Andriy Tsykholyas (andriy-tsykholyas) wrote :

I have the whole system (but /boot) encrypted and never seen this problem.

Revision history for this message
Timothée Manaud (timothee) wrote :

I have this issue too.
I only have an partition encrypted but not the whole system. Qbittorent seems to freeze when saving chunk of data. Then the PID is unkillable and end zombified, have to reboot the system (Ubuntu 10.10).
How can I help? Producing method? Log? Test?

Revision history for this message
Mr. Morfoos (am1) wrote :

The problem isn't caused by qbittorrent. The problem is caused by some strange interaction between ubuntu (customized) kernel and NVIDIA proprietary driver. At least that was in my case. When I used experimental (or standard 2D drivers) drivers for 3D acceleration, qbittorrent (and every other torrent client in ubuntu repositories) hanged and used 100% CPU power. I couldn't kill the process, or end it. I had to restart my computer.

So... let me explain it a little better:

The problem is probably caused by some below quality driver (or no driver at all for some hardware) on your system. In my case, it was GPU default drivers. When I installed proprietary NVIDIA driver, problem was gone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.