Bug 571837

Summary:	Many kde processes start with ~/Documents as initial current working directory
Product:	[Fedora] Fedora	Reporter:	Lawrence Lowe <lowe255-lnx>
Component:	kdelibs	Assignee:	Than Ngo <than>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	chepioq, fedora, jreznik, kevin, ltinkl, rdieter, rnovacek, ry, smparrish, than, thomasj
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-04 13:11:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lawrence Lowe 2010-03-09 17:03:39 UTC

Description of problem:

Many kde processes start with ~/Documents as current working directory. This includes kde basic processes unrelated to documents, started at logon time, but also to terminals and file-managers, and probably most other applications, when started from Kickoff.

Version-Release number of selected component (if applicable):

4.4.0-5 and 4.3.4-1

How reproducible:

Always

Steps to Reproduce:
1. Do adduser for a fresh account and KDE login to that account
2. /usr/sbin/lsof | grep /Documents
3.

Actual results:

a list of 17 or more kde-related processes: klauncher kded4 gam_server kglobalaccel knotify4 krunner abrt-applet kmix klipper etc.

Expected results:

Null. Most KDE processes are unrelated to a directory intended for documents and should have $HOME and not ~/Documents as the initial current working directory.

Additional info:

This is a change of behaviour since KDE 3 and is confusing to users. It affects the initial working directory of logon-started processes and also kickoff-started applications like Terminal, lxterminal, gnome-terminal, Thunar File Manager, xarchiver, and many more.

Circumventable by changing the Documents Path to $HOME in KDE System-Settings, About Me, Paths: this has an immediate effect on newly started applications. But this should not be necessary, and defeats the object of having a Documents Path, which ought to lead to a directory which only contains Documents.

It's interesting to note that konsole and Dolphin have now been individually fixed in this respect: clearly KDE folk think that starting up in Documents was incorrect, but they didn't fix the general issue.

This report is related to historic bugs 466266 and 568731 but I think demonstrates the broader issue which still exists.

Comment 1 Steven M. Parrish 2010-03-13 02:27:41 UTC

Thank you for taking the time to report this issue to us.  This is an issue which is best addressed by the upstream developers.

Please file a report at bugs.kde.org , and when done add the upstream report info to this report.

We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.

Thank you for the bug report.

Steven M. Parrish
KDE & Packagekit Triager 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Bug Zapper 2010-11-03 20:19:00 UTC

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Rex Dieter 2010-11-04 13:08:59 UTC

confirmed still valid for f14/kde-4.5.x

I'm pretty sure there's an upstream bug tracking this already, need to find it.

There's some relalated though (including those already mentioned).

Comment 4 Rex Dieter 2010-11-04 13:11:26 UTC

From reading those 2 referenced upstream bugs, seems this is "by design", we'll have to take it up with them.

Comment 5 Kevin Kofler 2012-07-19 22:26:06 UTC

*** Bug 841471 has been marked as a duplicate of this bug. ***