Bug 123368

Summary:	Get an error dialog when I change the permissions on a file
Product:	[Applications] kdevelop	Reporter:	mgolden
Component:	general	Assignee:	kdevelop-bugs-null
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description mgolden 2006-03-10 09:09:25 UTC

Version:           3.3.1 (on KDE 3.5.1) (using KDE KDE 3.5.1)
Installed from:    Fedora RPMs
OS:                Linux

This is the same problem as bug 114731 in Konqueror:

 http://bugs.kde.org/show_bug.cgi?id=114731

Presumably this problem is caused by some library that underlies the Permissions dialog in both applications.

Here, again, is the description

Open a project in KDevelop:C/C++. (Again, I'm using Fedora Core 4, updated)
Open the File Selector.
Right click on some file or other.
Choose Properties.
Go to Permissions tab.
Change a permission.
Click OK.
Listen to glass breaking.

Comment 1 Jens Dagerbo 2006-03-10 17:26:00 UTC

I'm not sure I understand. If this is "same problem as bug 114731 in Konqueror", why report it again? As you said, this is taken care of by an underlying KDE library. It's not implemented in KDevelop.

If I understand Bug #114731 correctly, this was fixed in kio in the KDE-3.5 branch after the 3.5.1 release. This means it should be in KDE-3.5.2

Is there any reason I don't see to report this against KDevelop?

Comment 2 mgolden 2006-03-10 19:36:13 UTC

When I posted it here, the conversation in the bug 114731 indicated that this was was supposed to be already fixed, in 3.5.1 or earlier.  The comment to which I was replying said that it was possibly a Fedora issue.  Since I am unfamiliar with the code, I don't know if it's definitely an underlying library or not, or which development team is responsible for it, I thought it would be helpful to report it to the development teams whose applications were affected.

A comment posted after mine indicated that it was going to be fixed in 3.5.2, but wasn't in 3.5.1.  If that's the case, then it might make sense to close the bug here and make sure it's in the right place.   If Konqueror is that place, then we're all set.

Comment 3 Jens Dagerbo 2006-03-10 23:01:34 UTC

Technically KIO would have been the place, but in either case, it seems it should be fixed in 3.5.2.

*** This bug has been marked as a duplicate of 114731 ***