| Summary: | Dolphin crash because Home/.config/katerc NOT writeable | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Harrison <sainokawara.sisyphus> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | gnu4ever, kushaldeveloper, mcfletch |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 15.12.3 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Harrison
2016-05-04 15:56:00 UTC
Should Home/.config/katerc User/Group Ownership really be "root"? Not knowing any better, I changed the Permissions for Ownership User to my User Id and the problem has not reoccurred. But, beware of suggestions by ignorant users! ===== Also, do I need to do anything special for the other bug I reported? I could provide additional information but it would really be helpful if someone could reproduce the problem under Windows Hyper-V in a different environment. Thank you, Created attachment 99701 [details]
New crash information added by DrKonqi
dolphin (15.12.3) using Qt 5.5.1
- What I was doing when the application crashed:
I have a local Samba shared folder on my Kubuntu 16.04 machine ('rwx' privileges set to everyone). A relative of mine stored a file there from his Win8.1 machine, resulting in a file belonging to 'nobody'/'nogroup' and the sole Read privilege granted to everyone on my machine.
What I did with Dolphin:
- Opened the properties of my Samba shared folder.
- Checked that the 'rwx' privilege was indeed granted to everyone (this was the case), then ticked option "Apply to all subfolders and their contents" (sorry, approximative English translation) and clicked OK.
- Dolphin raised an "Access refused" error message for the file coming from Win8.1.
- Acknowledging the error message led to Dolphin's crash.
-- Backtrace (Reduced):
#8 0x00007f127ae6eb99 in KDialogJobUiDelegate::Private::next() () from /usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#9 0x00007f127764bea1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f127811f05c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f1278124516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f127761c62b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
Created attachment 100519 [details]
New crash information added by DrKonqi
dolphin (15.12.3) using Qt 5.5.1
- What I was doing when the application crashed:
Just saw this happen when browsing to a (remote, slow) smb server. Clicked the address bar, typed in the *wrong-cased* next segment of the URL I wanted to visit. When replicating there was a dialog displayed saying that the wrong-cased version of the path didn't exist before Dolphin crashed. That is, it may not just be permissions causing the issue, it may be simply "missing" directories.
-- Backtrace (Reduced):
#8 0x00007f3200968b99 in KDialogJobUiDelegate::Private::next() () from /usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#9 0x00007f31fd145ea1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f31fdc1905c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f31fdc1e516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f31fd11662b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
Created attachment 101780 [details]
New crash information added by DrKonqi
dolphin (15.12.3) using Qt 5.5.1
- What I was doing when the application crashed:
copying a file from mtp to local storage
I think the crash happened when the usb connection got physically disconnected while moving the file. I understand that this would cause the transfer to fail but it shouldn't crash dolphin I think.
I am trying it again now and it hasn't crashed so far. I might not be able to reproduce this.
-- Backtrace (Reduced):
#8 0x00007f16bd189b99 in KDialogJobUiDelegate::Private::next() () from /usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#9 0x00007f16b9966ea1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f16ba43a05c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f16ba43f516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f16b993762b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
*** This bug has been marked as a duplicate of bug 353462 *** |