Bug 187973 - KOffice does not work with Windows roaming profiles (or maybe spaces in the profile path or something?)
Summary: KOffice does not work with Windows roaming profiles (or maybe spaces in the p...
Status: RESOLVED WORKSFORME
Alias: None
Product: kde-windows
Classification: Miscellaneous
Component: network and files (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: KDE-Windows
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2009-03-24 08:17 UTC by alister.hood
Modified: 2018-10-27 02:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alister.hood 2009-03-24 08:17:21 UTC
Version:            (using KDE 4.2.1)
OS:                MS Windows
Installed from:    MS Windows

Background: we use Windows roaming profiles, so my profile is on the server, although I thought ?? it is copied between the server and C: drive, so KDE should actually access it in C:
Or maybe it should refer to it as H: drive like everything else?

1. When I open a KOffice application (I didn't try them all, but I tried at least Kplato, Kword and Krita), an error message says "The file or folder /AKLSERVER02/Users/alister.hood/My Documents does not exist."

2. If I use file-open in a Koffice application either a) I get the same error message, the program freezes, and my computer makes loud noises like hard drives used to make when they were reading things, or b) the same as a but without the error message.
Comment 1 Christian Ehrlicher 2009-03-24 17:32:11 UTC
Looks like a poblem accessing with windows shared folders... I'll take a look into it.
Can you please tell me what's the content of environment variable USERPROFILE? We're using WinAPI to get the user paths (at least when kdelibs functionality is used...) so I wonder why this function should return a windows share.
Comment 2 alister.hood 2009-03-24 20:51:34 UTC
It is C:\Documents and Settings\alister.hood
Comment 3 Christoph Feck 2013-09-12 21:42:52 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 4 Andrew Crouthamel 2018-09-24 02:04:28 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 5 Andrew Crouthamel 2018-10-27 02:06:13 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!