host: Windows 10
remote: archlinux
In Windows:
$ wfreerdp.exe /v:... /u:... /p:... /size:1920x1080 /floatbar /f
(This is FreeRDP version 2.0.0-dev5 (00eabb2))
Remote session opens with (i think) size 1366x768. Scaled to 1920x1080 (my notebook native resolution), and is very blury.
If I open that session with Microsoft Remote Desktop then screen resolution will be 1920x1080.
I expect that session will be with 1920x1080 screen resolution.
Related
Something is preventing Opencv (4.5.1 last commit) to open camera device if there is no UX session active, for example, if the process is running as a system service on Ubuntu.
I am trying to run my program as a service on Ubuntu 20.04. When the process try to open the camera:
cv::VideoCapture camera;
camera.open(0);
fails with message:
/opencv/modules/videoio/src/cap_v4l.cpp (890) open VIDEOIO(V4L2:/dev/video0): can't open camera by index
The program open the camera without errors if I perform a loggin in the UX. However, the program cannot open the device if I am logged only by ssh (and I'm not logged in the UX). On ssh I can see the device there:
d$ ls -ls /dev/video0
0 crw-rw----+ 1 root video 81, 0 fev 24 14:16 /dev/video0
So, how to make opencv open the device if the program is running as a service?
EDIT:
As a workaround, I managed to open the camera running the service with sudo. It is not a great solution because means that I need to run the program with admin rights. Anyway, It suggests that the problem is caused by some permission issue.
Here's what happens:
Using a Macbook Pro, I use the Microsoft Remote Desktop Connection application to connect to my work computer, which is a Windows 10 machine
If I try to launch Spyder on my work computer, I get this error:
Load Library Error
However:
If I am at my work computer (i.e. physically at work instead of logging in remotely), I can launch Spyder successfully
If I leave Spyder open on my work computer, then go home and do a remote log-in to my work computer, I can use Spyder without issue. The problem/error described above arises only if I try to open Spyder through the remote connection.
This error only seems to affect Spyder and I can use all other programs without issue through a remote connection. As a workaround I've been using other IDEs and successfully running scripts, but I strongly prefer Spyder.
What I have tried so far (without success):
The 4 troubleshooting steps posted by Fazil M. to this Microsoft thread
Uninstalling/reinstalling Spyder using Conda
Restarting my work computer
System Information:
Work Computer OS: Windows 10, 64-bit
OS of computer through which I'm logging in to work computer: Mac OS X El Capitan 10.11.6
Spyder version: 4.1.1
Any thoughts as to what could be going on?
Update--More information and trials:
I checked out Issue #3736 on Spyder's GitHub. It says to download and add a file called opengl32sw.dll to the folder ~\Lib\site-packages\PyQt5\Qt\bin. But when I go to the PyQt5 folder, I do not see a subfolder for Qt. I tried placing it into the PyQt5 main folder, but that did not fix the problem.
I've heard this can be a graphics card issue too. On my machine I have two graphics cards: AMD RadeonT R5 430 and Intel(R) HD Graphics 630.
Darren's answer did not work for me. What did work was to:
First option: go into the device manager and disable the Intel HD Graphics card under "display adapters."
Second option:
run "Gpedit.msc"
navigate to Computer Configuration->Administrative
Templates->Windows Components->Remote Desktop Services->Remote
Desktop Session Host->Remote Session Environment
Disable "use WDDM graphics display driver for remote desktop
connections"
Restart the computer
See https://answers.microsoft.com/en-us/windows/forum/all/windows-10-1903-may-update-black-screen-with/23c8a740-0c79-4042-851e-9d98d0efb539
It took help from my organization's IT contractor, but I fixed the issue by doing the following:
Run a file called "gpedit.msc", which will open up a window for Local Group Policy Editor
In the tree menu on the left, navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment, and open the Remote Session Environment folder (not the subfolder within it)
Make sure the following are set to "Enabled":
"Use hardware graphics adapters for all Remote Desktop Services"
"Prioritize H.265/AVC444 graphics mode for Remote Desktop Connections"
"Configure H.264/AVC hardware encoding for Remote Desktop Connections"
Then restart the computer.
Since I was unable to get pass LoadLibrary 126 error using the solutions provided online and on here, I stepped back and realized the obvious workaround. The errors occurs when you open the program while you're using a remote session, right? The obvious solution is to launch the program while a remote session is not in progress. To do this while you're remoting, you should create a batch script to launch the program but make sure to include to a time delay before that (I used 'timeout 10 /nobreak' to do so). Run the batch script and, before your program launchs, disconnect from RDP. After enough time passes for the program to launch, you can reconnect to RDP and your program will be up and ready
I want to show some kind of loading screen on LCD display while beagleBone is booting linux.
Is it possible?
thanx
Plymouth is how Fedora and Ubuntu splash screens work.
According to Arch Linux, Plymouth requires Kernel Mode Setting or an applicable buffer, so assuming that you have the DRM modesetting capabilities (see Plymouth link below) you could evaluate cross-compiling from source.
https://www.freedesktop.org/wiki/Software/Plymouth/
For some unknown reasons, my NVIDIA driver does not work after installing caffe (I might do "yum update" during caffe installation).
So I re-installed NVIDIA driver, it works properly. But Centos 7 does not show login screen after reboot. The X sever is running, the default is graphical.target.
I also tried to "startx" or "sudo startx", and both shows "xauth: file /home/user/.serverauth.xxxx does not exist"
Is there any suggestion for this problem? Thanks.
I have a laptop (Asus N55SF) with NVIDIA GT555M GPU, with Elementary OS installed (based on Ubuntu).
I have Bumblebee installed, with NVIDIA drivers, which works. (optirun glxspheres has higher fps than just glxspheres)
When I connect a display to the VGA adapter, everything works fine. However, when I try to connect a HDMI device, nothing happens. The HDMI port works on Windows 7 and 8, so hardware failure can't be it.
The weird thing is, when I run xrandr, I get the following output:
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
1920x1080 60.0*+ 59.9
1680x1050 60.0 59.9
1600x1024 60.2
1400x1050 60.0
1280x1024 60.0
1440x900 59.9
1280x960 60.0
1360x768 59.8 60.0
1152x864 60.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
There is no HDMI device listed using xrandr! I searched the web, tried some other drivers, but I really have no clue what to do next.
Someone who might know what the problem is here?
Although this is an old question, the answer will help probably more people. That xrandr does not list your device often signifies a problem with the driver.
Use the hardware lister to check your hardware;
sudo lshw -C video
You will find that if there is something wrong with the driver that there is a display, but that it is unclaimed:
*-display UNCLAIMED
The reason why your driver isn't working can be manifold. In my case I used a new (apparently yet unsupported) 4.1.0 kernel and the nvidia-346 driver was silently failing in the Ubuntu GUI. Reinstalling it on the command-line with apt-get showed that the compilation failed to insert the module in the kernel. Rolling back to 3.19.0 solved the problem.
PS: In your case you should've used optirun xrandr. HDMI will not be available if the NVIDIA graphical card is not in use.
Same was happening with me. I tried to update and downgrade nvidia drivers but couldn't solve the issue. The reason might be here that your nvidia driver cannot work properly because secure boot might be enabled in the bios settings.
I also checked the gpu properties by sudo lshw -C video
and it showed *-display UNCLAIMED for my nvidia gpu.
Then I tried this and it worked for me-
Switch to nvidia gpu.
Power off the system and enter the bios settings. Find and disable 'secure boot' which I found in security settings in bios.
Reboot to linux.
Switch to nvidia gpu again just in case.
Now xrandr should show all the display output ports.
My gpu - GTX 1650. nvidia-driver version - 460
My laptop - Asus rog strix g(g351gt)
Recently I had run into the same problem when I upgraded my windows 10 to 11(running a dual boot with Kubuntu 20.04). That had changed the secure boot settings. I had to disable that and re-install the Nvidia drivers to get it working again.
Kubuntu 20.04 running on Acer Nitro 5.