i am not on my laptop right now, but i am running ubuntu on a vm: and didn’t know how to run kde after installing from ubuntu software store, and apparently it require usb debugging on android, although i would prefer wireless debugging: i even struggled to install the teamviewer .deb file, but figured it out afterall and had to figure how to run teamviewer, then after launch, i had to activate remote desktop, i had to install this rdp thing, and yet couldn’t reach the teamviewer server. again, all this on the VM ( Vmware on windows 7)
i am used to windows gui, so i took alot of things for granted, and the smallest task requires me to look up a guide for it, but kinda worth it, since i can’t install win 11 since my laptop is too old and couldnt install win 10 since it required a different partition system, and after that it didn’t install, so i am familiarizing myself with linux on vm for now
OK, I just tried reinstalling KDE connect on my phone. I didn’t have to do anything with USB Debugging. There should just be KDE Connect in app menu after you install it, there you should be able to pair a new device. However I don’t know how well that may work under VM.
About the TeamViewer, I did use TeamViewer on Linux Mint without problems. Maybe again something to do with VM. RDP just seems to be Microsoft’s remote desktop protocol unrelated to TeamViewer.
But I never properly tried Ubuntu. I didn’t even manage to install it as the installer kept crashing :-/
The only unsuccessful part.
I was waiting for it to download but it wasn’t moving. So I hit “Cancel” in hope to retry the download. However it shown as installed even though it wasn’t. Trying to remove KDE connect resulted in following error:
Direct image link
I tried to find a way to delete cache or config for Ubuntu Software (snap-store), but I only managed to delete all icons from it by deleting ~/snap…
Installing via apt
As expected, the good old sudo apt install kdeconnect did its job perfectly. Direct image link
Pairing KDE connect
As expected, this did not work right away as by default the network adapter is attached to NAT in VirtualBox. As such I couldn’t see any devices in KDE connect.
The solution was to change it to Bridged Adapter and select the desired network card. This way it would directly communicate with outside world using my laptop’s network adapter.
The setting is located in: (Your VM) > Settings > Network
A new problem arose. Trying to pair my phone with VM instead sent pairing request to host as I have KDE Connect installed on it and both Host and Guest are using same IP address.
That problem solved itself after pairing my phone with host computer. KDE Connect dynamically assigns ports in range 1714-1764. I guess at first they were trying to both use the same port, thus host received the pairing request instead, but after pairing and connecting with host, guest had to use different port and now they were able to successfully connect.
Edit: Nope, they do get separate IPs. I don’t know why this occurred then.
So I was able to connect both my phone and laptop: Direct image link
TeamViewer
After downloading the TeamViewer .deb file I just double clicked it and then clicked on install in the installer window Direct image link
Then I just normally launched TeamViewer from app menu and requested connection from my phone.
Ubuntu just asked to select display and allow remote interaction Direct image link
And this is a screenshot from my phone: Direct image link
That’s not the purpose. I just wanted it to be clearly visible for people to tell my home instance without having to check my account. (This is my alt account.)
I had to do it this way due to stupid username decision. I didn’t yet know what Lemmy was, so I used the same username I used on SDF.org, which was yet another stupid decision: I just wanted to test it out without wasting my desired username, but a good user verified that account for me, thus I got stuck with the username.
What problem are you having?
i am not on my laptop right now, but i am running ubuntu on a vm: and didn’t know how to run kde after installing from ubuntu software store, and apparently it require usb debugging on android, although i would prefer wireless debugging: i even struggled to install the teamviewer .deb file, but figured it out afterall and had to figure how to run teamviewer, then after launch, i had to activate remote desktop, i had to install this rdp thing, and yet couldn’t reach the teamviewer server. again, all this on the VM ( Vmware on windows 7) i am used to windows gui, so i took alot of things for granted, and the smallest task requires me to look up a guide for it, but kinda worth it, since i can’t install win 11 since my laptop is too old and couldnt install win 10 since it required a different partition system, and after that it didn’t install, so i am familiarizing myself with linux on vm for now
OK, I just tried reinstalling KDE connect on my phone. I didn’t have to do anything with USB Debugging. There should just be KDE Connect in app menu after you install it, there you should be able to pair a new device. However I don’t know how well that may work under VM.
About the TeamViewer, I did use TeamViewer on Linux Mint without problems. Maybe again something to do with VM. RDP just seems to be Microsoft’s remote desktop protocol unrelated to TeamViewer.
But I never properly tried Ubuntu. I didn’t even manage to install it as the installer kept crashing :-/
i guess i ll have to dig in this further. i ll keep ur experience in mind.
Documenting results (mostly successful)
Trying to download KDE Connect in Ubuntu Software
The only unsuccessful part.
Direct image link
I was waiting for it to download but it wasn’t moving. So I hit “Cancel” in hope to retry the download. However it shown as installed even though it wasn’t. Trying to remove KDE connect resulted in following error:
I tried to find a way to delete cache or config for Ubuntu Software (
snap-store), but I only managed to delete all icons from it by deleting~/snap…Installing via apt
As expected, the good old
Direct image link
sudo apt install kdeconnectdid its job perfectly.Pairing KDE connect
As expected, this did not work right away as by default the network adapter is attached to NAT in VirtualBox. As such I couldn’t see any devices in KDE connect.
The solution was to change it to Bridged Adapter and select the desired network card. This way it would directly communicate with outside world using my laptop’s network adapter.
The setting is located in: (Your VM) > Settings > Network
A new problem arose. Trying to pair my phone with VM instead sent pairing request to host as I have KDE Connect installed on it
and both Host and Guest are using same IP address.That problem solved itself after pairing my phone with host computer.
KDE Connect dynamically assigns ports in range 1714-1764. I guess at first they were trying to both use the same port, thus host received the pairing request instead, but after pairing and connecting with host, guest had to use different port and now they were able to successfully connect.Edit: Nope, they do get separate IPs. I don’t know why this occurred then.
So I was able to connect both my phone and laptop:
Direct image link
TeamViewer
After downloading the TeamViewer .deb file I just double clicked it and then clicked on install in the installer window
Direct image link
Direct image link
Direct image link
Then I just normally launched TeamViewer from app menu and requested connection from my phone.
Ubuntu just asked to select display and allow remote interaction
And this is a screenshot from my phone:
man this is a dedicated effort! thank you so much.
I’ll try to download Ubuntu 23.04 ISO overnight and try it tomorrow on VirtualBox (7.0).
It does not require USB debugging or have anything to do with TeamViewer.
then one less step to figure out
Fwiw most/all of the plugins didnt work for me in Ubuntu until I switched from Wayland to X11
try flatpak version or appimage version, I’ve seen better results for apps on those formats in terms of ease of use
sure will
I like how you have mentioned your instance name in username to distinguish between your alt accounts
That’s not the purpose. I just wanted it to be clearly visible for people to tell my home instance without having to check my account. (This is my alt account.)
I had to do it this way due to stupid username decision. I didn’t yet know what Lemmy was, so I used the same username I used on SDF.org, which was yet another stupid decision: I just wanted to test it out without wasting my desired username, but a good user verified that account for me, thus I got stuck with the username.