[konversation] [Bug 461051] New: log file name prefix not updated when network renamed

[argonel]

https://bugs.kde.org/show_bug.cgi?id=461051

            Bug ID: 461051
           Summary: log file name prefix not updated when network renamed
    Classification: Applications
           Product: konversation
           Version: Git
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: konversation-devel at kde.org
          Reporter: argonel at gmail.com
  Target Milestone: ---

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.