Bug 461051 - log file name prefix not updated when network renamed
Summary: log file name prefix not updated when network renamed
Status: CONFIRMED
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: Git
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-27 05:56 UTC by argonel
Modified: 2022-10-27 05:56 UTC (History)
0 users

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 argonel 2022-10-27 05:56:05 UTC
SUMMARY
If one changes the network name without first closing the tab for the server, the logging will continue in the old network name.


STEPS TO REPRODUCE
1. Create a network with the name "A" and add a server to it
2. Connect to said network so as to create the logs
3. Open the logging dir in Dolphin
4. See that the files are prefixed with "A"
5. Disconnect from the network but do not close the tab
6. Rename the network in the server list box
7. Reconnect to the network
8. See that no files with the new name are created
9. Repeat steps above but close the tab in step 6 and see that the new name is used


OBSERVED RESULT
When the network is disconnected but not closed, renaming the network doesn't switch to logging under the new name.

EXPECTED RESULT
Technically the logging could immediately begin in the new logs given the way the files are used, but this would be somewhat jarring when reading the logs later. Konversation could offer to rename the existing logs if the network is connected. When the network is disconnected however, it should behave the same as if the network is closed.