https://bugs.kde.org/show_bug.cgi?id=272740
--- Comment #6 from Stefan Endrullis ---
Yeah, let's close this issue. The progress of copy processes is visible again.
The issue is anyway very, very old (2011).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #14 from Stefan Endrullis ---
That's it! You fixed the crash! Thank you very much!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #12 from Stefan Endrullis ---
And thanks for your effort!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #11 from Stefan Endrullis ---
OK, waiting for more patches to test...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #9 from Stefan Endrullis ---
OK, I checked out the new git master version, applied the patch, compiled and
started the project. Unfortunately, krusader crashed in the buggy directory
again:
#0 0x55711074 in memset (__len
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #7 from Stefan Endrullis ---
$ readlink -v core
readlink: core: Protocol error
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #5 from Stefan Endrullis ---
OK, here is the backtrace with line numbers:
#0 0x55710ab5 in memset (__len=2957657807, __ch=0,
__dest=0x7fff4fb58670) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:71
#1 FileSystem
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #3 from Stefan Endrullis ---
@Nikita
That's a good question. Unfortunately, I don't have an answer to it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389413
--- Comment #1 from Stefan Endrullis ---
I completely forgot to mention the behavior of krusader.
So, krusader works fine as long as I do not enter directories with read errors,
but once I do it immediately crashes with an segmentation fault.
--
You
https://bugs.kde.org/show_bug.cgi?id=389413
Bug ID: 389413
Summary: Krusader crashes when entering directories with read
errors
Product: krusader
Version: Git
Platform: Ubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=389363
Stefan Endrullis changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=389363
--- Comment #5 from Stefan Endrullis ---
Ah, I forgot to clear the cache. You're right. With ".." it works.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389363
--- Comment #4 from Stefan Endrullis ---
$ cd krusader/krusader-build
$ cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local/
CMake Error: The source "/home/stefan/software/krusader/CMakeLists.txt" does
not match the source "/home/stefan/so
https://bugs.kde.org/show_bug.cgi?id=389363
--- Comment #2 from Stefan Endrullis ---
libkf5i18n-dev is already installed in version 5.38.0-0ubuntu1.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389363
Stefan Endrullis changed:
What|Removed |Added
CC||ste...@endrullis.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=389363
Bug ID: 389363
Summary: build fails with 'Unknown CMake command
"ki18n_wrap_ui"'
Product: krusader
Version: Git
Platform: Ubuntu Packages
OS: Linux
Sta
16 matches
Mail list logo
