Bug 316222

Summary: session manager not UNC compatible
Product: [Applications] konqueror Reporter: Matthew Millar <mattmill30>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: 4.8.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Session manager UNC error

Description Matthew Millar 2013-03-06 12:32:01 UTC
The session manager is unable to load sessions on a UNC path; producing an error that the file or folder cannot be found on /server/share$/Application Data/.kde/share/apps/konqueror/sessions.

The session menu lists the saved sessions correctly, and previous sessions can be loaded correctly

Reproducible: Always

Steps to Reproduce:
1. Configure user's home directory on Windows Domain to \\fs-server\user$
2. Logon to client as user
3. Open Konqueror; File > Sessions > Manage...
Actual Results:  
Produces an error that the file or folder cannot be found on /fs-server/user$/Application Data/.kde/share/apps/konqueror/sessions.

Expected Results:  
I expect the sessions on the UNC to be accessed and listed in the session manager in same way that they are accessed and listed in the session menu.

As this is running on Windows using the official KDE on Windows system, I would expect when the server, share or directory is inaccessible that the address would appear as a MS Networking UNC (\\server\share$\directory\subdirectory).
Comment 1 Matthew Millar 2013-03-06 12:46:22 UTC
Created attachment 77798 [details]
Session manager UNC error
Comment 2 Andrew Crouthamel 2018-11-10 03:16:19 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-20 04:11:06 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2023-01-02 02:04:22 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-01-17 05:15: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
mark the bug 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 6 Bug Janitor Service 2023-02-01 05:04:54 UTC
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!