Прикупил тут клаву mx5000 logitech она намного удобнее обычной. Идет с адаптером bluetooth она 2007 года.
на винде работает на 11 – со всеми функциями.
на ubuntu – не хочет
сделал по описанию, но оно к старой версии , не 23.04
(на новой Ubuntu c 2016 года есть подключение по удаленке, Microsoft RDP -новый вариант – а программ полно, даже на телефоне Андроид, и на айфоне. если серверов 10 штук – тут есть на страничках, как настроить. Скриптом простым, не через графические настройки, при входе – используя старую версию графического экрана. Так же, как и на FreeBSD сервере, там даже сложнее. dconf-editor – подсказка, если скрипт от 2016 версии а в 2023 году не заработал – Xorg а не Xwayland. и видеоплату надо хорошую, Radeon RX580 – 8 gb у меня, они поработали в майнинге и будет сейчас перезапуск. самые новые типа 3080 не надо, а 3060 можно, если больше нравится нвидия. )
как отключить пароль от keyring ubuntu 23.04 23.11
|
1 |
не вiрус но безопасность снижается - а по другому не работает |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 |
Пытаюсь подключиться с Windows 11 к 22.04.1-Ubuntu desktop в настройках settings -> Sharing - > Remote Desktop (включено Remote Desktop и Remote Control), Также включен аутологон Setting - Users - Autologon - enable. И это работает, но до ПЕРЕЗАГРУЗКИ. После при попытке зайти по RDP ошибка: [Window Title] Подключение к удаленному рабочему столу [Content] Произошла внутренняя ошибка. [Expanded Information] Код ошибки: 0x4 Расширенный код ошибки: 0x0 Только когда я перехожу к настройкам общего доступа на моем Ubuntu, я могу снова подключиться. (и ввожу пароль руками, который он запрашивает в этом меню - все начмнает работать) Кто-нибудь знает, почему это так? I am trying to setup remote desktop sharing for a Ubuntu 22.04 desktop system with the intended purpose of running this system headless without a screen connected. I am able to successfully VNC to the 22.04 system from Remmina on a different PC using the username and password generated by the Remote Desktop Sharing application, however each time I reboot the 22.04 system this password changes and I need to connect a screen to find out what the password is. How do I stop this from happening? I need VNC access to the 22.04 system with a password that does not ever change. Thanks. Well - I can tell you how to fix this one particular way (its the only way I know how) but it will open up another can of worms for you. The issue is that in Ubuntu 22.04, all the username and passwords for your system are, by default, encrypted with your username's password. That is being stored in what is called the keyring. What is happening is that the VNC server is being loaded without the keyring being unlocked and therefore can't access the stored VNC password (as its encrypted) so it auto generates a new one each time you boot up. So, if you auto boot up with your user login, during the auto boot up, Ubuntu 22.04 doesn't automatically unlock the keyring. So to fix this, go to Utilities, Password and Keys, right click on Default Keyring, select change password. It will ask for your username password. Enter that. Then for the new password, do not enter one. Leave it blank. It will warn you that all passwords stored on your keyring will become and remain unencrypted. If you can wear that risk, accept that. Then go back to remote desktop, ensure the password you want is set, and each time you reboot, that password will then remain the same. Hope that all makes sense :) то есть - открыть в утилитах ключи и пароли, вернуться там нажав стрелочку - в основную программу, а там - выбрать в левом меню список сохраненных паролейдля удаленного доступа - и - по правой кнопке мыши - поменять пароль. Завести один раз старый - его устанавливали обычно - как пароль пользователя, а потом поменять - на пустой. прогрмма предупредит, что не будет зашифровано, а по другому - не заработает. //После перезагрузки - будет сохраняться установленый пароль дальше - первый раз после перезагрузки - опять надо зайти в настройки - и включить и выключить удаленный доступ и сохранить пароль - в том числе и на vnc после открывания этого окна настроек - доступ появляется.. как запустить сразу - ищем решение. (рестарт службы подключившись через шелл..) получилось - после второй перезагрузки и захода еще раз в настройки, пароль на кольцо ключей не спрашивала система. Пароль на rdp (windows remote desktop protokol теперь и на ubuntu) сохранен и после перезагрузки подключился. конечно, автологин включен в etc xdg то ли в gdm3 AutoAdminLogon |
|
1 2 3 |
NVIDIA H100 GPUs are now available, for as low as $2.24/hour. взято с DigitalOcean View details -> [New] Speed up your apps & websites with Premium General Purpose Droplets -> Join the many businesses saving up to 50% or more with DigitalOcean -> Blog Docs Get Support Contact Sales Tutorials Questions Learning Paths For Businesses Product Docs Social Impact CONTENTS Prerequisites Step 1 — Installing a Desktop Environment on Ubuntu Step 2 — Installing xrdp on Ubuntu Step 3 — Configuring xrdp and Updating Your Firewall Step 4 — Testing the RDP Connection Conclusion // Tutorial // How To Enable Remote Desktop Protocol Using xrdp on Ubuntu 22.04 Published on September 20, 2022 Networking Ubuntu Best Curved Monitors Default avatar By Raghav Aggarwal How To Enable Remote Desktop Protocol Using xrdp on Ubuntu 22.04 The author selected the COVID-19 Relief Fund to receive a donation as part of the Write for DOnations program. Introduction Remote Desktop Protocol (RDP) is a network protocol developed by Microsoft that allows users to remotely access and interact with the graphical user interface of a remote Windows server. RDP works on the client-server model, where an RDP client is installed on a local machine, and an RDP server is installed on the remote server. RDP is widely used for Windows remote connections, but you can also access and interact with the graphical user interface of a remote Linux server by using a tool like xrdp, an open-source implementation of the RDP server. In this tutorial, you will install and configure an RDP server using xrdp on a Ubuntu 22.04 server and access it using an RDP client from your local machine. You will understand how to establish access to a remote Linux server by configuring and using an RDP connection. Deploy your frontend applications from GitHub using DigitalOcean App Platform. Let DigitalOcean focus on scaling your app. Prerequisites To complete this tutorial, you will need: One Ubuntu 22.04 server with a non-root user with sudo privileges, a firewall, and at least 1GB of RAM, which you can set up by following the Ubuntu 22.04 initial server setup guide. A local computer with an RDP client installed. A list of available RDP clients for different operating systems is provided below: On Windows, you can use the default Remote Desktop Connection application. On macOS, you can use the Microsoft Remote Desktop application. On Linux, you can use FreeRDP, or Remmina. Step 1 — Installing a Desktop Environment on Ubuntu In this step, you will install and configure a desktop environment on your Ubuntu server. By default, an Ubuntu server comes with a terminal environment only. A desktop environment will need to be installed to access a user interface. From the available options for Ubuntu, you will install the Xfce desktop environment. Xfce offers a lightweight, user-friendly desktop environment for Linux-based systems. To begin, connect to your server using SSH and update the list of available packages using the following command: sudo apt update Next, install the xfce and xfce-goodies packages on your server: sudo apt install xfce4 xfce4-goodies -y You will be prompted to choose a display manager, which is a program that manages graphical login mechanisms and user sessions. You can select any option from the list of available display managers, but this tutorial will use gdm3. After installing the desktop environment, you will now install xrdp on your server. Step 2 — Installing xrdp on Ubuntu xrdp is an open-source implementation of the RDP server that allows RDP connections for Linux-based servers. In this step, you will install the xrdp on your Ubuntu server. To install xrdp, run the following command in the terminal: sudo apt install xrdp -y After installing xrdp, verify the status of xrdp using systemctl: sudo systemctl status xrdp This command will show the status as active (running): Output ● xrdp.service - xrdp daemon Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor preset: enabled) Active: **active (running)** since Sun 2022-08-07 13:00:44 UTC; 26s ago Docs: man:xrdp(8) man:xrdp.ini(5) Main PID: 17904 (xrdp) Tasks: 1 (limit: 1131) Memory: 1016.0K CGroup: /system.slice/xrdp.service └─17904 /usr/sbin/xrdp If the status of xrdp is not running, you may have to start the service manually with this command: sudo systemctl start xrdp After executing the above command, verify the status again to ensure xrdp is in a running state. You have now installed xrdp on your server. Next, you will review the xrdp configuration to accept connections from remote clients. Step 3 — Configuring xrdp and Updating Your Firewall In this step, you will review the default configuration of xrdp, which is stored under /etc/xrdp/xrdp.ini, and add a configuration for an RDP connection. You will also update the firewall settings. xrdp.ini is the default configuration file to set up RDP connections to the xrdp server. The configuration file can be modified and customized to meet the RDP connection requirements. Open the file in nano text editor or any editor of your choice: sudo nano /etc/xrdp/xrdp.ini The configuration file contains different sections: Globals defines some global configuration settings for xrdp. Logging defines logging subsystem parameters for logs. Channels defines multiple channel parameters that RDP supports. Session types defines multiple supported session types by xrdp. Every session type configuration is defined as a separate section under its session type name enclosed in square brackets, such as [Xorg] and [XVnc]. There is no [Sessions types] heading in the file; instead, it is written as a comment. In the configuration file, navigate to the Session types section. You will find multiple supported session types and their parameters listed: Output ... ; ; Session types ; ; Some session types such as Xorg, X11rdp, and Xvnc start a display server. ; Startup command-line parameters for the display server are configured ; in sesman.ini. See and configure also sesman.ini. [Xorg] name=Xorg lib=libxup.so username=ask password=ask ip=127.0.0.1 port=-1 code=20 [Xvnc] name=Xvnc lib=libvnc.so username=ask password=ask ip=127.0.0.1 port=-1 #xserverbpp=24 #delay_ms=2000 [vnc-any] ... [neutrinordp-any] ... ... By default, the username and password parameters are set to ask, which means the user will be prompted to enter their username and password to connect over RDP. Parameters, such as name, username, and password, can be modified if necessary. For the initial RDP connection to the server, the default configuration will suffice. Save and close the file when finished. Now move to your user’s home directory if you are not there already: cd ~ Next, you will create a .xsession file under /home/sammy and add the xfce4-session as the session manager to use upon login: echo "xfce4-session" | tee .xsession tee writes the echoed string "xfce4-session" to the file .xsession. The above configuration ensures that xfce4-session is used as a session manager upon graphical login request. As a result of installingxfce as your desktop environment, xfce4-session serves as its session manager. If you don’t include this information in the .xsession file, no session manager is chosen, and the RDP session will fail to connect to the graphical display. Restart the xrdp server: sudo systemctl restart xrdp Next, you will configure your firewall to allow remote connections from your public IP on port 3389. An RDP connection serves on TCP/IP port 3389. To access the remote server over RDP, you must allow port 3389 in your firewall. First, find the public IP for your local machine: curl ifconfig.me On Windows, use the Windows Command Prompt to run this command. curl places a request on ifconfig.me that returns your public IP as an output: Output ... your_local_ip Next, allow access to the RDP port 3389 on your remote server, replacing your_local_ip with the output of the last command: sudo ufw allow from your_local_ip/32 to any port 3389 Verify the status of your UFW firewall: sudo ufw status The output should look like the following: Output Status: Active To Action From -- ------ ---- OpenSSH ALLOW Anywhere 3389 ALLOW your_local_ip OpenSSH (v6) ALLOW Anywhere (v6) ... You have now enabled port 3389 to accept connections from your public IP. Next, you will test your local machine’s RDP connection to your remote server. Step 4 — Testing the RDP Connection In this step, you will test the RDP connection from your local machine. The sections below include actions for testing the connection on Windows, macOS, and Linux machines. Testing the RDP Connection on Windows To test the connection using the Remote Desktop Connection client on Windows, first launch the Remote Desktop Connection app. Enter your remote server’s public IP and username into the fillable text boxes for Computer and User name. You may need to press the down arrow for Show Options to input the username: Screencapture of the Remote Desktop Connection Client initial logon page Press the Connect button. If you receive an alert that the Remote Desktop can't connect to the remote computer, check that you have turned on the Remote Desktop option in your system settings. Press Yes if you receive the identity verification popup: Screencapture of the Identity Verification popup Then, enter your remote server’s username (sammy) and the password you created for user sammy during the initial server setup. Press Ok. Screencapture display the xrdp login screen Once you have logged in, you should be able to access your Ubuntu Desktop environment: Screenapture of the remote Ubuntu Desktop Using RDP, you successfully connected to your remote Ubuntu server from your local machine. You can close it with the exit button when you have finished using your graphical desktop. Testing the RDP Connection on macOS To test the connection using the Remote Desktop Connection client on macOS, first launch the Microsoft Remote Desktop Connection app. Press Add PC, then enter your remote server’s public IP in the fillable box: Screencapture showing the "Add PC" setup page with an empty box for the remote server's IP address You can Add a user account when setting up the connection: Screencapture showing the "Add a username account" option If you do not add a user during setup, you will be prompted for your user login credentials: Screencapture showing the "Enter your user account" prompt Press Yes to bypass the identity verification popup: Screencapture showing the identity verification prompt Once you have logged in, you can access your Ubuntu remote desktop. You can close it with the exit button when you have finished using your graphical desktop. Testing the RDP Connection on Linux You will need an RDP client to test the RDP connection on a local Linux machine. First, install the remmina RDP client for Ubuntu: sudo apt install remmina Select y if prompted to complete the installation. This command will install Remmina, an open-source remote desktop client on your Ubuntu system using apt. For other Linux distributions, you can review the Remmina documentation for installation. Once installed, launch the remmina application on your local Linux machine and enter your remote server’s public IP in the fillable box. Press Enter on your keyboard to connect to your remote desktop. Screenapture showing the Remmina client with a blurred IP address entered in the RDP box Then, enter your remote server’s username (for this tutorial, the username is sammy) and the password you created for the user during the initial server setup. Press Ok. Screencapture showing the xrdp Login Screen with selected for session type, filled in the username box, and a redacted password in the password box You may need to enter your user’s password again to unlock the remote desktop. Once you have logged in, you should be able to access your Ubuntu Desktop environment. Using RDP, you successfully connected to your remote Ubuntu server from your local machine. You can close it with the exit button when you have finished using your graphical desktop. Once you have ensured the remote connection works, you can use this sequence whenever you need to use the graphical interface for your remote Linux server. Conclusion In this article, you configured xrdp to connect to a graphical desktop for your remote Ubuntu server over an RDP connection from a local machine. Now, you can try configuring a VNC connection for your Linux server with How to Install and Configure VNC on Ubuntu 20.04. VNC is another option for remote connection to a Linux desktop. Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases. Learn more about us About the authors Default avatar Raghav Aggarwal author Default avatar Caitlin Postal editor Technical Editor Still looking for an answer? Ask a question Search for more help Was this helpful? 6 Comments This textbox defaults to using Markdown to format your answer. You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link! Sign In or Sign Up to Comment 870e7d300f0a446f9def949a0f5ef7 • April 27, 2023 Hi, thanks for this excellent work. is there a way to always send output to remote/client screen? (sometimes sub-windows open on server screen, instead of desired remote screen steps to repeat - VS-code runs on servers I open vscode on remote/client screen, it opens properly on remote screen then using vs-code I open directory, the directory selector screen open on server. a05fa21fb5af41ca81d95b1b9820c2 • April 18, 2023 It’s extremely irresponsible to add -y to apt without giving the user the opportunity to realise what’s happening, and then let them inspect the output first. You, the author, cannot predict the output of every Ubuntu-based system out there, no matter how experienced you are. Case in point, the above commands cause xorg to be uninstalled on Linux Mint 19.1 setups. Pierre Henri Fricot • March 22, 2023 If you have the autologin activated you will have to disable it for the XRDP to work. Otherwise you will have issue with snap. SleepingLapisSnorkler • March 10, 2023 Managed to connect from Windows 10 to Ubuntu 22.04 by this step. But there pair of steps that should be done additionally: a) sudo adduser xrdp ssl-cert b) echo "sudo -u ${USER} xfce4-session" | tee .xsession Pavel A. f173ec4b64fd45659e0af6fbcf1a16 • January 29, 2023 Hi, Thanks for the subject training materials. I have followed the steps, but still, after connecting from my machine, which is Windows 10, to my remote Ubuntu machine, there is only a black screen. Please let me know if you have any suggestions on how to troubleshoot this issue . Thanks, tijmenschoemaker • November 4, 2022 This default doesn’t seem to work for me out of the box. Using a default Ubuntu 22.04 installation. Is that because of the shell that is being used by default? Creative Commons This work is licensed under a Creative Commons Attribution-NonCommercial- ShareAlike 4.0 International License. Try DigitalOcean for free Click below to sign up and get $200 of credit to try our products over 60 days! Sign up Popular Topics Ubuntu Linux Basics JavaScript Python MySQL Docker Kubernetes All tutorials Talk to an expert card icon Get our biweekly newsletter Sign up for Infrastructure as a Newsletter. Sign up card icon Hollie's Hub for Good Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help. Learn more card icon Become a contributor You get paid; we donate to tech nonprofits. Learn more Featured on Community Kubernetes Course Learn Python 3 Machine Learning in Python Getting started with Go Intro to Kubernetes DigitalOcean Products Cloudways Virtual Machines Managed Databases Managed Kubernetes Block Storage Object Storage Marketplace VPC Load Balancers Welcome to the developer cloud DigitalOcean makes it simple to launch in the cloud and scale up as you grow – whether you’re running one virtual machine or ten thousand. Learn more -> DigitalOcean Cloud Control Panel Get started for free Sign up and get $200 in credit for your first 60 days with DigitalOcean. Get started This promotional offer applies to new accounts only. Company About Leadership Blog Careers Customers Partners Referral Program Affiliate Program Press Legal Privacy Policy Security Investor Relations DO Impact Nonprofits Products Products Overview Droplets Kubernetes Paperspace App Platform Functions Cloudways Managed Databases Spaces Marketplace Load Balancers Block Storage Tools & Integrations API Pricing Documentation Release Notes Uptime Community Tutorials Q&A CSS-Tricks Write for DOnations Currents Research Hatch Startup Program deploy by DigitalOcean Shop Swag Research Program Open Source Code of Conduct Newsletter Signup Meetups Solutions Website Hosting VPS Hosting Web & Mobile Apps Game Development Streaming VPN SaaS Platforms Cloud Hosting for Blockchain Startup Resources Contact Support Sales Report Abuse System Status Share your ideas © 2024 DigitalOcean, LLC.Sitemap. Cookie_preferences This site uses cookies and related technologies, as described in our privacy policy, for purposes that may include site operation, analytics, enhanced user experience, or advertising. You may choose to consent to our use of these technologies, or manage your own preferences. |
Code:
hcitool dev
and I get an output like this;
Code:
hci0 00:07:61:40:CC:77
now what you can do is this, I found that the automatic startup wont connect unless you manually connect at least once. So to do this put the keyboard and mouse in discoverable mode (little red buttons on the bottom of the keyboard and mouse)
in terminal enter this;
sudo nano /etc/default/bluetooth
hcitool scan
(нажав кнопочки на устройстве – мыш или клава – connect и на BT адаптере тоже)
mac address выведет – у клавы или мыши, связь должна работать.
sudo mcedit /etc/defaults/bluetooth
my settings, that got my mx5000 to work;
Code:
——
HIDD_ENABLED=1
HIDD_OPTIONS=”-i hci0 –connect 00:07:61:32:70:6F –connect 00:07:61:33:CF:33 –master –server
—–
however these HIDD_OPTIONS have worked, according to others in the bug report;
—————
my logitech MX5000 works, after repluging in the reciver, just fine though, would that be the only solution to my problem?
хрен там
Заходи в настройки убунту После перезагрузки.
в настройках – устройства bluetooth
нажимаем красные кнопочки опять – соединение
устройство находится – подключаем . Проверка – определяется правильно – клава или мышь
Работает. Устройство балованое, любит поспать, а потом выдает очередью по несколько символов.
2023 2024 январь – версия 23.04 ssd 1 tb no name Shenzhen made , Xeon 32 core 3200 ? 2 nm 19 watt? Russia Chinese Made ? Motherboard x99 X-22 Rus all above 39 USA Dollars?, 4000 Russian Rouble. Ubuntu Linux 23/04 / Mining Rig/ Game Station. .. intel original 9 стоит 700 долл. или 69300р. тут я перепродаю один сервер на Аху..илион денег / не знаю чего распродажа – война может будет . не торговая. Насколько я разбираюсь, технология 2 или 3 нанометра уже не только тайваньская, но и в России и в Китайском районе, скорее всего Shenzhen. Технопарк это.. У нас возможно Микрон московский – Зеленоград, а то и Фрязино, где 315 транзистор сделали. Это .. гражданские.. производства, для мирного применения, а есть еще и Рязань и Воронеж с Брянском. Иностранцы вообще не понимают, как это в России 10 тысяч заводов, а их не меньше пятой части в Москве и рядом! И почти все остались, ну парочку успели снести.. ( в общем то – это он и есть, чуть уменьшеный в тысячу раз, и теперь состоит из 20 атомов кремния, а может и 15. Первый транзистор такого типа, который сейчас во всех чипах, и компьютерных процессорах тоже, сделан в Подмосковье, СССР 1967 год. )
несколько настроек в убунту . Раз даже 1с бухгалтерия на убунту стала работать – переустанавливаем линукс. Сносим глючную винду. (кто сказал – запускать на виртуалке из windows ..)
Related Images:
Pages: 1 2