Bug 188671

Summary:	process for the trash protocol died unexpectedly when deleting files with ACLs applied
Product:	[Unmaintained] kio	Reporter:	plottygat
Component:	trash	Assignee:	David Faure <faure>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	cfeck
Priority:	NOR	Keywords:	triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description plottygat 2009-04-02 17:11:44 UTC

Version:           sconosciuto (using 3.5.9, compiled sources)
Compiler:          Target: i586-manbo-linux-gnu
OS:                Linux (i686) release 2.6.24.7-desktop-2mnb

I've got an ext3 file system mounted with ACLs enabled.
I applied the following ACL to all files and directories in this file system:

setfacl -m g:users:rwx 

so, files permissions are like this:

-rw-rw-r--+ 1 moro moro  9 2009-04-02 16:39 foo.txt

and this is the output of getfacl:

# file: foo.txt
# owner: moro
# group: moro
user::rw-
group::rwx                      #effective:rw-
group:users:rwx                 #effective:rw-
mask::rw-
other::r--

If I try to move such a file (even if I'm the owner) to the trashcan, in KDE, I get the following message:
"The process for the trash protocol died unexpectedly"

Then I can find the file in the trashcan, but it is not removed from the original directory.
The problem occurs in many KDE applications (Konqueror, Digikam, Amarok etc..), and only with files: empty directories with the same ACLs applied are deleted correctly.
Other actions as move or copy work fine.
If no ACL is applied all work perfectly.

I found these messages in my .xsession-errors:

...
QWidget: Cannot create a QWidget when no GUI is being used
kioslave: ####### CRASH ###### protocol = trash pid = 30981 signal = 11
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
...

Let me know if you need other information

Thanks

Moreno

Comment 1 Christoph Feck 2013-09-12 21:39:14 UTC

This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)

Comment 2 Andrew Crouthamel 2018-09-24 02:08:24 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-10-27 04:11:58 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!