Summary: | Crash overwriting files | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | ultralux97 |
Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | BluishHumility, domhans, ervin, fanzhuyifan, GivenPurity, jay, kdelibs-bugs, konst, mail, matheust-_, max-huntermann, mike, nate, nuke7832, pollob666, qmm, rlaggren, sam, thibaud.laurent, whyhow+tech, zincles, zorinarch |
Priority: | VHI | Keywords: | drkonqi |
Version: | 5.110.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=476738 | ||
Latest Commit: | https://invent.kde.org/frameworks/kio/-/commit/48322f44323a1fc09305d66d9093fe6c3780709e | Version Fixed In: | 5.111 |
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
ultralux97
2023-09-12 13:03:55 UTC
*** Bug 474429 has been marked as a duplicate of this bug. *** *** Bug 474466 has been marked as a duplicate of this bug. *** *** Bug 474491 has been marked as a duplicate of this bug. *** *** Bug 474512 has been marked as a duplicate of this bug. *** *** Bug 474521 has been marked as a duplicate of this bug. *** Created attachment 161625 [details]
New crash information added by DrKonqi
dolphin (23.08.0) using Qt 5.15.10
Steps to reproduce:
1- Create two files, let's say "test1.txt" and "test2.txt".
2- Select "test1.txt", hit Ctrl+C and Ctrl+V.
3- Dolphin will ask what you want to call the new copy, type "test2.txt".
4- Dolphin will ask if you want to overwrite the file.
5- Overwrite it.
6- Dolphin crashes and no file operation is performed.
-- Backtrace (Reduced):
#6 QString::QString(QString const&) (other=<error reading variable: Cannot access memory at address 0x8>, this=0x7f2929f7a980, this=<optimized out>, other=<optimized out>) at /usr/include/qt/QtCore/qstring.h:1093
#7 KMountPoint::mountType() const (this=0x0) at /usr/src/debug/kio/kio-5.110.0/src/core/kmountpoint.cpp:411
#8 0x00007f2940f3c87d in isOnCifsMount (filePath=...) at /usr/include/qt/QtCore/qshareddata.h:161
#9 FileProtocol::copy(QUrl const&, QUrl const&, int, QFlags<KIO::JobFlag>) (this=0x7f29080012d0, srcUrl=..., destUrl=<optimized out>, _mode=420, _flags=...) at /usr/src/debug/kio/kio-5.110.0/src/ioslaves/file/file_unix.cpp:743
#10 0x00007f294aa2e8db in KIO::SlaveBase::dispatch(int, QByteArray const&) (this=0x7f29080012e0, command=<optimized out>, data=...) at /usr/src/debug/kio/kio-5.110.0/src/core/slavebase.cpp:1364
*** Bug 474536 has been marked as a duplicate of this bug. *** Created attachment 161627 [details]
New crash information added by DrKonqi
dolphin (23.08.1) using Qt 5.15.10
Dolphin crashes while trying to override any file.
for example:
create a file at ~/folder1/sth.txt;
create another at ~/folder2/sth.txt;
while I tries to copy the first file to overwrite the second file, while I click the "overwrite" button, the dolphin would immediately crash.
this problem seems to be happend on many other arch linux users. I also tried flatpak version of dolphin, and same bug happened.
-- Backtrace (Reduced):
#6 QString::QString(QString const&) (other=<error reading variable: Cannot access memory at address 0x8>, this=0x7fc869f7a980, this=<optimized out>, other=<optimized out>) at /usr/include/qt/QtCore/qstring.h:1093
#7 KMountPoint::mountType() const (this=0x0) at /usr/src/debug/kio/kio-5.110.0/src/core/kmountpoint.cpp:411
#8 0x00007fc87616987d in isOnCifsMount (filePath=...) at /usr/include/qt/QtCore/qshareddata.h:161
#9 FileProtocol::copy(QUrl const&, QUrl const&, int, QFlags<KIO::JobFlag>) (this=0x7fc82c0012d0, srcUrl=..., destUrl=<optimized out>, _mode=420, _flags=...) at /usr/src/debug/kio/kio-5.110.0/src/ioslaves/file/file_unix.cpp:743
#10 0x00007fc89c5998db in KIO::SlaveBase::dispatch(int, QByteArray const&) (this=0x7fc82c0012e0, command=<optimized out>, data=...) at /usr/src/debug/kio/kio-5.110.0/src/core/slavebase.cpp:1364
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1411 Created attachment 161630 [details]
New crash information added by DrKonqi
dolphin (23.08.1) using Qt 5.15.10
KDE Dolphin seems to crash whenever I try to cut / paste and replace (or copy / paste and replace) files across two different drives. This does not seem to happen on the same drive.
-- Backtrace (Reduced):
#6 QString::QString(QString const&) (other=<error reading variable: Cannot access memory at address 0x8>, this=0x7ff9fcad9980, this=<optimized out>, other=<optimized out>) at /usr/include/qt/QtCore/qstring.h:1093
#7 KMountPoint::mountType() const (this=0x0) at /usr/src/debug/kio/kio-5.110.0/src/core/kmountpoint.cpp:411
#8 0x00007ffa1d5d587d in isOnCifsMount (filePath=...) at /usr/include/qt/QtCore/qshareddata.h:161
#9 FileProtocol::copy(QUrl const&, QUrl const&, int, QFlags<KIO::JobFlag>) (this=0x7ff9d8000d70, srcUrl=..., destUrl=<optimized out>, _mode=420, _flags=...) at /usr/src/debug/kio/kio-5.110.0/src/ioslaves/file/file_unix.cpp:743
#10 0x00007ffa3d67e8db in KIO::SlaveBase::dispatch(int, QByteArray const&) (this=0x7ff9d8000d80, command=<optimized out>, data=...) at /usr/src/debug/kio/kio-5.110.0/src/core/slavebase.cpp:1364
something that might help: My system is on btrfs. The crash (not okular but kdevelop) crashes when copying a file to /tmp if I do mount -t tmpfs none /tmp the crash does not happen (KMountPoint::List::findByPath works) I have my system running off of a cryptsetup lvm. Running stat on / gives me 0:28 whereas mountinfo shows 0:26. guess that's the root cause of the issue.. (In reply to mike from comment #11) > something that might help: > > My system is on btrfs. The crash (not okular but kdevelop) crashes when > copying a file to /tmp > > if I do mount -t tmpfs none /tmp the crash does not happen > (KMountPoint::List::findByPath works) > > I have my system running off of a cryptsetup lvm. Running stat on / gives me > 0:28 whereas mountinfo shows 0:26. guess that's the root cause of the issue.. actually btrfs over lvm over cryptsetup. Guess in that case st_dev in stat does not match mountinfo, so the assumption that mountPtr->deviceId() == buff.st_dev matches at least once is in practice wrong (don't know if this is how it should work or a kernel bug, but the kernel used in my setup is currently 6.2) Git commit a6f7d3117f159f3e0a88ff08b5f69b9bc8612cf7 by Kevin Ottens, on behalf of Kevin Ottens. Committed on 15/09/2023 at 13:34. Pushed by ervin into branch 'master'. Don't crash if KMountPoint gives nothing back while checking for CIFS M +3 -0 src/kioworkers/file/file_unix.cpp https://invent.kde.org/frameworks/kio/-/commit/a6f7d3117f159f3e0a88ff08b5f69b9bc8612cf7 *** Bug 474555 has been marked as a duplicate of this bug. *** Created attachment 161647 [details]
New crash information added by DrKonqi
okular (23.08.0) using Qt 5.15.10
Crashes when saving editted file, or when using save as to overwrite existing file. Does not crash when using save as to new file.
-- Backtrace (Reduced):
#6 QString::QString(QString const&) (other=<error reading variable: Cannot access memory at address 0x8>, this=0x7f1627f7e980, this=<optimized out>, other=<optimized out>) at /usr/include/qt/QtCore/qstring.h:1093
#7 KMountPoint::mountType() const (this=0x0) at /usr/src/debug/kio/kio-5.110.0/src/core/kmountpoint.cpp:411
#8 0x00007f16900a587d in isOnCifsMount (filePath=...) at /usr/include/qt/QtCore/qshareddata.h:161
#9 FileProtocol::copy(QUrl const&, QUrl const&, int, QFlags<KIO::JobFlag>) (this=0x7f161c407f70, srcUrl=..., destUrl=<optimized out>, _mode=-1, _flags=...) at /usr/src/debug/kio/kio-5.110.0/src/ioslaves/file/file_unix.cpp:743
#10 0x00007f16c09b48db in KIO::SlaveBase::dispatch(int, QByteArray const&) (this=0x7f161c407f80, command=<optimized out>, data=...) at /usr/src/debug/kio/kio-5.110.0/src/core/slavebase.cpp:1364
Created attachment 161648 [details]
New crash information added by DrKonqi
okular (23.08.1) using Qt 5.15.10
crash on save, on save-as to existing file (overwrite). Does not crash on save-as to new file.
-- Backtrace (Reduced):
#6 QString::QString(QString const&) (other=<error reading variable: Cannot access memory at address 0x8>, this=0x7f8197f7e980, this=<optimized out>, other=<optimized out>) at /usr/include/qt/QtCore/qstring.h:1093
#7 KMountPoint::mountType() const (this=0x0) at /usr/src/debug/kio/kio-5.110.0/src/core/kmountpoint.cpp:411
#8 0x00007f81c821387d in isOnCifsMount (filePath=...) at /usr/include/qt/QtCore/qshareddata.h:161
#9 FileProtocol::copy(QUrl const&, QUrl const&, int, QFlags<KIO::JobFlag>) (this=0x7f8140317b20, srcUrl=..., destUrl=<optimized out>, _mode=-1, _flags=...) at /usr/src/debug/kio/kio-5.110.0/src/ioslaves/file/file_unix.cpp:743
#10 0x00007f81eab2b8db in KIO::SlaveBase::dispatch(int, QByteArray const&) (this=0x7f8140317b30, command=<optimized out>, data=...) at /usr/src/debug/kio/kio-5.110.0/src/core/slavebase.cpp:1364
Git commit 48322f44323a1fc09305d66d9093fe6c3780709e by Kevin Ottens, on behalf of Kevin Ottens. Committed on 15/09/2023 at 19:00. Pushed by ngraham into branch 'kf5'. Don't crash if KMountPoint gives nothing back while checking for CIFS M +3 -0 src/ioslaves/file/file_unix.cpp https://invent.kde.org/frameworks/kio/-/commit/48322f44323a1fc09305d66d9093fe6c3780709e Created attachment 161676 [details]
New crash information added by DrKonqi
dolphin (23.08.0) using Qt 5.15.10
I was trying to overwrite some files in a directory, and it crashed. I tried repeatedly, but everytime it crashed. I am running Fedora KDE Spin, My Fielsystem is BTRFS. I have also tried with Krusader, and the crash happened there also.
-- Backtrace (Reduced):
#4 0x00007ff26e2cf054 in KMountPoint::mountType() const () from /lib64/libKF5KIOCore.so.5
#5 0x00007ff244023136 in FileProtocol::copy(QUrl const&, QUrl const&, int, QFlags<KIO::JobFlag>) () from /usr/lib64/qt5/plugins/kf5/kio/kio_file.so
#6 0x00007ff26e27cfba in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5
#7 0x00007ff26e275a3d in KIO::SlaveBase::dispatchLoop() () from /lib64/libKF5KIOCore.so.5
#8 0x00007ff26e2f35e8 in KIO::WorkerThread::run() () from /lib64/libKF5KIOCore.so.5
*** Bug 474654 has been marked as a duplicate of this bug. *** (In reply to Albert Astals Cid from comment #19) > *** Bug 474654 has been marked as a duplicate of this bug. *** But I am running 23.08.1, long after this is "fixed". Still considered a duplicate? (In reply to GivenPurity from comment #20) > (In reply to Albert Astals Cid from comment #19) > > *** Bug 474654 has been marked as a duplicate of this bug. *** > > But I am running 23.08.1, long after this is "fixed". Still considered a > duplicate? This bug is not in kde gear but in kde frameworks. It was fixed in upstream development and will be release with kde frameworks 5.111 that has not been released yet. This bug hits everyone who has kio 5.110 and copies (or overwrites) a file on a btrfs using a kde application that uses kio to do that. This bug was introduced as a fix for the same operation but on cifs where a rename operation could fail. Essentially it was done by looking up the mountpoint for the destination file and if that is cifs/smb it would behave different. The issue with btrfs is that the way the lookup is done does not work with that filesystem (still doesn't, but for the use case all that is needed is to know if the file is on cifs. A method in kio could not handle that case and exactly that was causing the crash) *** Bug 474850 has been marked as a duplicate of this bug. *** *** Bug 474902 has been marked as a duplicate of this bug. *** *** Bug 476432 has been marked as a duplicate of this bug. *** For (k)ubuntu see https://bugs.launchpad.net/ubuntu/+source/kio/+bug/2039765 if this gets more attention maybe someone will backport this to 23.10 Same (exact) thing, opensuse 15.5 Why is this marked "Resolved Fixed" when it demonstrably is not? If there is a kludge to make it work, why is it not provided here? It hits me with ext4 file system. (In reply to rlaggren from comment #26) > Same (exact) thing, opensuse 15.5 > > Why is this marked "Resolved Fixed" when it demonstrably is not? If there is > a kludge to make it work, why is it not provided here? If you look carefully at the information fields at the top of the page, you can see that this is fixed in Frameworks version 5.111, with the commit fixing the issue being https://invent.kde.org/frameworks/kio/-/commit/48322f44323a1fc09305d66d9093fe6c3780709e. Please submit a new bug report if you are on a version newer than 5.111 and you still see this issue. If you are still on versions before 5.111, you would need to contact the maintainers of your distribution to have the fix backported, or to update to the latest version. Thx for you quick response. Done. That is, I found a later version of kio that was assembled to work with my distro release. I will try to find the right way to report this to the distro. On 1/31/24 10:04, bugzilla_noreply@kde.org wrote: ... > If you look carefully at the information fields at the top of the page, you can > see that this is fixed in Frameworks version 5.111, with the commit fixing the > issue being *** Bug 485191 has been marked as a duplicate of this bug. *** |