Fedora with ScreenConnect
-
@bnrstnr said in Fedora with ScreenConnect:
My screen is only blank on Fedora 28 Cinnamon until I actually login. It's not an issue for me because I'm the only user of this machine, so I connect, type my password, and then it works.
So maybe there's some kind of process that doesn't start until login? If so, maybe it could be set to run always?
That is an issue that I have never troubleshot. It has always been like that.
-
I have the same problem. I installed Fedora 28 with cinnamon on an older Thinkpad a couple weeks ago. I also found the article on the SC site. I even posted in the comments.
Also, I had to edit some sort of config to disable the sleep when lid is closed function, but that didn't last past a reboot
-
There is also this link - https://docs.connectwise.com/ConnectWise_Control_Documentation/Get_started/Knowledge_base/Connect_to_a_headless_Linux_machine#I_have_installed_an_access_agent_on_my_headless_Linux_machine.2C_but_I_see_a_black_screen_when_I_connect_to_it.
Edit: You have to scroll down to the bottom to find the potentially relevant info regarding frame buffer adjustments.
-
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller I told you to use rpm.
rpm -U screenconnect.rpm
Yeah... and that's what does this.
-
@bnrstnr said in Fedora with ScreenConnect:
My screen is only blank on Fedora 28 Cinnamon until I actually login. It's not an issue for me because I'm the only user of this machine, so I connect, type my password, and then it works.
So maybe there's some kind of process that doesn't start until login? If so, maybe it could be set to run always?
But it's logged in. So that can't be it in this case.
-
@wrx7m said in Fedora with ScreenConnect:
There is also this link - https://docs.connectwise.com/ConnectWise_Control_Documentation/Get_started/Knowledge_base/Connect_to_a_headless_Linux_machine#I_have_installed_an_access_agent_on_my_headless_Linux_machine.2C_but_I_see_a_black_screen_when_I_connect_to_it.
Edit: You have to scroll down to the bottom to find the potentially relevant info regarding frame buffer adjustments.
So you need the headless adjustments even for headed systems?
-
@wrx7m said in Fedora with ScreenConnect:
There is also this link - https://docs.connectwise.com/ConnectWise_Control_Documentation/Get_started/Knowledge_base/Connect_to_a_headless_Linux_machine#I_have_installed_an_access_agent_on_my_headless_Linux_machine.2C_but_I_see_a_black_screen_when_I_connect_to_it.
Edit: You have to scroll down to the bottom to find the potentially relevant info regarding frame buffer adjustments.
Not the issue, comes back sane. My system is not headless, so should not be needed as it has to be good output for the desktop to work.
-
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller I told you to use rpm.
rpm -U screenconnect.rpm
Yeah... and that's what does this.
Did you install java?
dnf install java
-
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller I told you to use rpm.
rpm -U screenconnect.rpm
Yeah... and that's what does this.
Did you install java?
dnf install java
Yes. And it installs for you if you miss it, but I made sure to do it manually first on every machine tested.
-
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller I told you to use rpm.
rpm -U screenconnect.rpm
Yeah... and that's what does this.
Did you install java?
dnf install java
The system runs, so the RPM definitely worked, Java definitely worked, it makes the connection, it collects data, it just shows a blank screen no matter what.
-
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller I told you to use rpm.
rpm -U screenconnect.rpm
Yeah... and that's what does this.
Did you install java?
dnf install java
The system runs, so the RPM definitely worked, Java definitely worked, it makes the connection, it collects data, it just shows a blank screen no matter what.
Ah, so you are farther than before. I misread that.
When I connect to my desktop at home I see the blank screen.
I blindly type my password and hit enter.
Assuming I typed it right, it logs me in and I see my desktop.When I connect to my bookstack server I see a blank screen. I hit enter and see this.
-
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller I told you to use rpm.
rpm -U screenconnect.rpm
Yeah... and that's what does this.
Did you install java?
dnf install java
The system runs, so the RPM definitely worked, Java definitely worked, it makes the connection, it collects data, it just shows a blank screen no matter what.
Ah, so you are farther than before. I misread that.
When I connect to my desktop at home I see the blank screen.
I blindly type my password and hit enter.
Assuming I typed it right, it logs me in and I see my desktop.When I connect to my bookstack server I see a blank screen. I hit enter and see this.
I will have to try that on my Thinkpad later on. I also have to fix that lid closing sleep issue.
-
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller I told you to use rpm.
rpm -U screenconnect.rpm
Yeah... and that's what does this.
Did you install java?
dnf install java
The system runs, so the RPM definitely worked, Java definitely worked, it makes the connection, it collects data, it just shows a blank screen no matter what.
Ah, so you are farther than before. I misread that.
When I connect to my desktop at home I see the blank screen.
I blindly type my password and hit enter.
Assuming I typed it right, it logs me in and I see my desktop.Interesting, okay. What happens if you don't know what user it is attempting to log in? Or, what happens if the remote user is already logged in?
-
If someone is logged in and using the machine and you want to support them, how does this work?
-
@wrx7m said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller I told you to use rpm.
rpm -U screenconnect.rpm
Yeah... and that's what does this.
Did you install java?
dnf install java
The system runs, so the RPM definitely worked, Java definitely worked, it makes the connection, it collects data, it just shows a blank screen no matter what.
Ah, so you are farther than before. I misread that.
When I connect to my desktop at home I see the blank screen.
I blindly type my password and hit enter.
Assuming I typed it right, it logs me in and I see my desktop.When I connect to my bookstack server I see a blank screen. I hit enter and see this.
I will have to try that on my Thinkpad later on. I also have to fix that lid closing sleep issue.
Tried the password thing, it didn't change anything.
At some point, though, instead of a blank screen it started always showing this...
-
Here is an example of the console output while SC shows a blank screen..
-
@scottalanmiller said in Fedora with ScreenConnect:
If someone is logged in and using the machine and you want to support them, how does this work?
For a desktop machine with a GUI? Yeah that would suck.
For a console machine I never have a problem.
-
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
If someone is logged in and using the machine and you want to support them, how does this work?
For a desktop machine with a GUI? Yeah that would suck.
For a console machine I never have a problem.
We use Ubuntu machines like this for shared training and support stations. So having multiple people able to see the same screen is most of the point. And as they are multiple users, we'd never be sure who it was trying to log in.
So we are okay, we just use Xubuntu for this today. But Fedora with XFCE runs performance circles around Xubuntu and looks nicer. I'd much rather be using that, especially as our desktops are Fedora. Having ubuntu machines for jump stations is unnecessarily awkward, but not a big deal.
-
But ScreenConnect has some glitches with Ubuntu that causes other issues. Like it can't display certain GUI elements. I'll make a different post about that later.
-
@wrx7m said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller said in Fedora with ScreenConnect:
@jaredbusch said in Fedora with ScreenConnect:
@scottalanmiller I told you to use rpm.
rpm -U screenconnect.rpm
Yeah... and that's what does this.
Did you install java?
dnf install java
The system runs, so the RPM definitely worked, Java definitely worked, it makes the connection, it collects data, it just shows a blank screen no matter what.
Ah, so you are farther than before. I misread that.
When I connect to my desktop at home I see the blank screen.
I blindly type my password and hit enter.
Assuming I typed it right, it logs me in and I see my desktop.When I connect to my bookstack server I see a blank screen. I hit enter and see this.
I will have to try that on my Thinkpad later on. I also have to fix that lid closing sleep issue.
On my Fedora Gnome computer, I make the following changes:
sudo vi /etc/systemd/logind.conf
And I either uncomment
HandleLidSwitch=suspend
and change suspend to ignore. Or add
HandleLidSwitch=ignore