-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reports missing desktop sessions when using desktopmultiplex #6445
Comments
Update: Just noticed, It's logging Files and Terminal Sessions but not Desktop Sessions |
strange one, you have |
I'll try that now and let you know. |
Changed the config.json to: Still no change in the reports |
@WingedSpur did you try connecting to a machine for like a min or 2 then disconnect and run the report? |
Let me give that a try. One moment... |
no worries! glad its fixed for the moment, but indeed you have found a bug so thank you! |
I am so glad for your help on this. I'm sure your guys will figure it where the bug is hiding in no time. But for now I'm VERY happy. I have a question about another portion (not really a bug). How do I get it to keep more than 1024mb of Session Recordings? |
in your sessionrecording section in config.json you have set so you are mixing and matching these options, |
I'll underscore those right away. Have a wonderful weekend |
Signed-off-by: si458 <simonsmith5521@gmail.com>
all fixed for you! 🥳 |
You Sir are brilliant. All my missing Desktop Sessions are being reported correctly with this patch. |
@WingedSpur glad it's fixed/sorted! |
Describe the bug
Remote Sessions work normally (Even have Session Recording working), You can see them logged under the My Events tab but when you generate a report nothing comes up.
Server Software (please complete the following information):
Client Device (please complete the following information):
Remote Device (please complete the following information):
Additional context
Problem occured shortly after enabling Session Recording
Your config.json file
The text was updated successfully, but these errors were encountered: