Summary: | Dolphin crashes when moving directories | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | cordawyn |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | adawit, david.a.ordenes.d |
Priority: | NOR | ||
Version: | 2.1 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
cordawyn
2013-01-20 09:28:59 UTC
Thanks for the bug report. Looks like a problem with the smb kioslave that has been reported already. *** This bug has been marked as a duplicate of bug 291060 *** Created attachment 76678 [details]
New crash information added by DrKonqi
dolphin (2.1) on KDE Platform 4.9.4 using Qt 4.8.3
Kubuntu 12.10, KDE 4.9.4:
I was moving files from one folder in and ext4 partition to another of the same format.
Only a few folders get to be created on destination and the process crashed.
Error shown: dialog with "The process for the file protocol died unexpectedly."
This has happened through the day (no reboot in between), especially when dealing with more than a few tens of files and folders.
Possibly related since this appeared seemingly jointly: when I search files by content from Dolphin specifying "everything", I get the same error as when I tried to move the folders, and nothing is located: "The process for the file protocol died unexpectedly."
Also, search by rating and document type appear permanently greyed out since I started having problems.
-- Backtrace (Reduced):
#6 0x00007f8c039bd425 in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x00007f8c039c0b8b in __GI_abort () at abort.c:91
[...]
#9 0x00007f8c03a9182c in __GI___fortify_fail (msg=<optimized out>) at fortify_fail.c:38
#10 0x00007f8c03a90700 in __GI___chk_fail () at chk_fail.c:29
#11 0x00007f8c03a917be in __fdelt_chk (d=<optimized out>) at fdelt_chk.c:26
*** This bug has been marked as a duplicate of bug 303225 *** |