https://bugs.kde.org/show_bug.cgi?id=402017
kingfa...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kingfa...@gmail.com
--- Comment #62 from kingfa...@gmail.com ---
(In reply to Karl from comment #59)
> This bug is a pain..
>
> I found a way to recover using PV .. a work-around
>
> 1) find the process+fd by looking directly in /proc:
>
> ls -al /proc/*/fd/* 2>/dev/null | grep {filename}
>
> 2) Then with pv thrown in:
>
> tail -c +0 -f /proc/{procnum}/fd/{fdnum} | pv -s {expectedsize} >
> {recovery_filename}
>
> You may need to Ctrl-C when done (ls /proc/{procnum}/fd/{fdnum} will tell
> you that the file no longer exists)), but if you know the exact size in
> bytes, you can use pv -S to make it exit when the count is reached.
This bug has caused me a lot of troubles, lost nerves and data, incredibly
frustrating that this is ongoing for 3 years. I'm happy you were able to find a
workaround. Can you maybe give a further explanation? Are you supposed to close
Okular throughout? I tried copying into another directory using
{recovery_filename}, but the progress chart does not move. I'm not able to
create files inside that folder either. It keeps being stuck at 0Bytes and does
not change.
--
You are receiving this mail because:
You are watching all bug changes.
