Logout lightdm session does not close session - centos

I have lightdm running on RHEL7.9. But when I try to logout user from vnc session. It doesn't close the vnc session instead it stays with blank screen and the process is not getting exited.
I have also tried "exit_on_failure=true" under Seats configuration. But it will close all the vnc sessions
Any suggestions?
TIA

Related

Can you always have a vscode-server running?

I'm trying to use remote ssh and liveshare so I can have liveshare constantly running on a server, meaning anyone can collaborate at anytime. However, whenever I close the window I started the server on, the liveshare disconnects. Is there a way to have it running 24/7 on my server?
EDIT: I'm using Remote Development

Powershell chat server working in background

It is possible for poshchat server to work in the background?
When I close the PowerShell console, I see the service running in task manager but I can't have the client connect to this server anymore.

WWW::Mechanize::Firefox troubleshooting

I have MozRepl installed in my browser and set to start on startup and accept outside connections.
So my questions are as follows
1) will simply running the code my $mech = WWW::Mechanize::Firefox->new(); launch the firefox browser?
2) I have set MozRepl to accept outside connections however, while firefox is not launched, when my script reaches the code in 1), it tells me unable to connect, problem connecting to localhost, on port 4242. I tried to debug by doing telnet localhost 4242 with firefox browser not launched. It also gives me this error Could not open connection to the host, on port 4242: Connect failed.
Should i be expecting this result?
3) Given the difficulties I'm experiencing above, I decided to use system() to launch the browser before creating mechanize::firefox instance. The browser is able to start, however it never reaches the code where mechanize::firefox instance is to be created.
#where i manually fire up firefox.
system('"C:\Program Files\Mozilla Firefox\firefox.exe"');
my $mech = WWW::Mechanize::Firefox->new(ssl_opts => { verify_hostname => 0});
$mech->get( 'https://192.168.1.23' );
What can i do to make sure firefox browser can be launched yet it will not affect the sequence of the code, such that mechanize::firefox instance can be created to manipulate the browser?
You have to start your browser before your test, it is not started automaticaly.
I takes time to start firefox, but system returns instantly after firefox started. I takes some seconds to initialize all of its plugins, etc.
The easiest thing is to wait 30 sec via sleep, or you start a while loop to wait until it is responding.
It is possible that a firewall rule prevent you access mozrepl. The default port is 4242.
check the port via telnet:
telnet 192.168.1.23 4242
telnet 127.0.0.1 4242

TortoiseHg web server says it's stopped even though it's still running

When I right click on my Hg folder and choose TortoiseHg > Web Server, I can start the web server on port 7999 without a problem. I then shut that dialog box. If I go and run netstat -a -o from a command prompt, I can see that an instance of thgw.exe is running and listening on port 7999 (even after closing the dialog box). It's ironic that in Task Manager the thgw.exe process is called "TortoiseHg GUI tools for Mercurial SCM" even though there's no GUI running.
Problem
If I open that dialog box again via TortoiseHg > WebServer, it reports that the status is "stopped", and the Start button is enabled. This is incorrect because the port is still listening. If I click the start button I get this message in the log as I'd expected:
abort: cannot start server at ':7999': Only one usage of each socket address (protocol/network address/port) is normally permitted
Questions
So why does TortoiseHg not realize that an existing thgw.exe is running on the port?
Is there a better way besides netstat and task manager to check if TortoiseHg is listening on a web port? And also learn which port is representing which folder?
I can't stop the web server so how are you supposed to gracefully shutdown a TortoiseHg web server without killing it from Task Manager? That seems like a scary thing to do to my production source control system!
When the Close button of the Serve window is clicked, the window does not actually close, but minimize itself into the notification area. See the globe icon in the screenshot below:
If you click the icon, the original Serve window appears, where the Start button is actually disabled, and Stop enabled. You can stop the server from there.
This behavior was tested on TortoiseHg 2.4, Windows 7.
The only problem I see here is that the original window is not opened when you choose the appropriate menu item.
See also issue 1845 on the TortoiseHg bug tracker.

Fiddler 2 won't launch

I try to start fiddler 2 and I get this message box:
Fiddler 2 startup aborted
Fiddler appears to be running in this users account
Maybe in a terminals services session
I loaded fiddler onto another machine on our wireless network and it displays the same message. How do I fix this so I can run fiddler normally?
Do you see the problem with the latest version? https://www.fiddler2.com/dl/fiddler2alphasetup.exe