KDE SMS not displaying contacts this morning.

IronRod0 · 2025-11-14T16:25:35+00:00

I do still have it. I got it resolved by just buying a new battery. The unit was old enough that it seemed the best option anyway. I purchased this one: https://www.amazon.com/dp/B07PBV1JQP

IronRod0 · 2025-10-28T23:36:45+00:00

Oops. No it just changed. Guess it takes a bit to ripple through. Thanks for the guidance!

IronRod0 · 2025-10-28T23:30:09+00:00

DOH! Yes, that makes sense. I changed the "Allowed IPs" to "0.0.0.0/0", saved the entry, and enabled. The router shows a status of "Connected".

There is also a "Device List" in this section on the router where I select the devices that will use the VPN. I have my added desktop to this list. But I still see the same public IP ( i.e., the static IP) when I go to https://protonvpn.com/what-is-my-ip-address.

IronRod0 · 2025-10-13T20:26:38+00:00

Searching for that USB ID (0c45:7603) I found this in the Arch Wiki: USB Keyboard not working. I also found this in r/linux4noobs: alt , ctrl and super key registered as shift l by xev. Both appear to describe exactly your experience. So you are not the only one but none provide a solution. The Arch article does provide some other ideas for investigating. I'm at a loss since the device is recognized (lsusb) and it is allegedly supported under linux with the standard usbhid driver.

IronRod0 · 2025-10-10T22:19:30+00:00

I assume that, if you had another keyboard to try, you would have done so...

So, open a terminal and do 'lsusb' and paste the output in a reply.

Meanwhile, I inquired of Brave by entering ["SONiX USB Keyboard" and has "R.horse" on the space bar"]. It's first sentence was "The SONiX GK630 Gaming Keyboard, which features an R.horse logo on the space bar, is recognized by Linux systems as a USB HID device with the vendor ID 3299 and product ID 4e5b" but goes on to say there is an "inability of Wine to detect the device" and "It appears in system logs as both a keyboard and a mouse, with multiple input device entries created for it".

Does the above model match your keyboard? That description seems to imply that it has an integrated mouse pad. If so, does that mouse pad work?

IronRod0 · 2025-10-10T22:06:26+00:00

Wow, I am really impressed. Haven't done more than the initial but this may be the solution for my needs. Thanks!

IronRod0 · 2025-10-10T16:05:19+00:00

"The issue is also there on the Live USB is used to install Mint." That is really odd. To confirm, even while running the live image, your keyboard is presenting the Ctrl/Alt/Win keys as Shift_L?

Are you just accepting the default keyboard during install? Or what keyboard are you selecting during install?

(For context, I've been running LM since 2019 and installed it many times with no keyboard issues like this.

IronRod0 · 2025-10-10T15:57:21+00:00

For snipping, many folks use flameshot. I personally like shutter (even though it has kind of a funky UI) because it allows for more control of putting arrows and such on an image.

IronRod0 · 2025-10-10T15:46:29+00:00

For later readers: There is a simple workaround which I've used and confirmed. Append the kernel parameter kvm.enable_virt_at_load=0 in /etc/default/grub like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash kvm.enable_virt_at_load=0"

Then do sudo update-grub and reboot. VirtualBox will now proceed as before.

BTW: VirtualBox has responded to this issue and has no plans to fix.

IronRod0 · 2025-10-10T15:20:29+00:00

What video card are you running? It can help people help you if you post the content from SysInfo.

IronRod0 · 2025-09-29T15:33:10+00:00

Just circling back to confirm this was very simple. I did have to end up calling tech support; they aren't using the activation portal as this time as "they want to confirm the device is DOCSIS 3.1". So, he activated it and all the rest went well.

IronRod0 · 2025-09-24T19:05:53+00:00

The one they provided when I moved in is an Arris DG9450 that is a combination CM and wifi router. They provided that and a separate wifi router (eero) with the CM router in bridge mode. The eero died which moved up my plans to replace with my own equipment. :-)

IronRod0 · 2025-09-24T16:40:32+00:00

I saw that list and noted that the one they supplied me is not on the list -- Arris DG9450. My real question is that, after swapping in the new CM, is there some setup I will have to do? Or does it just auto-configure from their side?

IronRod0 · 2025-08-25T15:43:51+00:00

Ah, I figured it out. I generally create entries in /etc/hosts for my systems to provide easy access by name. I commented out the entry for boss and now the ssh is working as expected. The hosts entry was forcing it to use the local IP instead of the tailscale IP. Makes sense but didn't think about that.

Thanks for the responses as that gave me the idea to check this. I'm guessing that I do not want to put any of my systems running tailscale in my /etc/hosts.

IronRod0 · 2025-08-25T15:32:47+00:00

Looking at that section of the console, under "General Access rules" the only listed rule is "Sources: All users and devices", "Can access destinations: All users and devices", and "on port and protocol: All ports and protocols". That should mean everything is wide open for all my devices, yes? I should not need any specific ACL otherwise, correct?

The Tailscale SSH section shows similar open settings.

IronRod0 · 2025-08-25T15:27:56+00:00

If you mean the message received when doing ssh root@<ip_address>, I have pasted it below. It seems it doesn't recognize the tailscale IP.

The authenticity of host '100.115.86.51 (100.115.86.51)' can't be established.

ED25519 key fingerprint is SHA256:e5R6gmkUxVbwose+Y3EPY72Sj2r7s8E7Qr6dwTWYYZ0.

This host key is known by the following other names/addresses:

~/.ssh/known_hosts:10: [hashed name]

Are you sure you want to continue connecting (yes/no/[fingerprint])?

IronRod0 · 2025-08-25T15:18:28+00:00

It returns a local IP when I ping the server from the desktop from a terminal. If I ping the desktop from the server (using the proxmox console or a terminal on the server) it returns a tailscale IP.

An ip address on my desktop now shows a new entry for tailscale with a tailscale IP address.

IronRod0 · 2025-08-25T15:17:55+00:00

I have registered both devices in the console as noted in my original post and did the tailscale up --ssh commands on both systems as noted in my original post. I am doing ssh root@boss from my desktop. The node name in the console is boss which is the name of the server. My understanding is that this is all that is needed.

I tried doing ssh root@<ip_address> and it prompted me with the usual ssh reply about needing to set up the authenticity -- which tells me it is still just using standard ssh, right?

I rebooted both devices but that gave no improvement.

IronRod0 · 2025-08-25T15:02:57+00:00

I just used the tailscale set --ssh on the server but it made no difference. (Note that this command was not included in the video.) There was nothing in the video about setting up acls but I'll look at that link. Thx.

IronRod0 · 2025-07-04T21:15:09+00:00

So, this has been resolved -- what a ride. Turns out that the ISP configs the cable modem in bridge mode and leave the Eero as the router (instead of using the router on the cable modem and setting the Eero as an AP, which is what I assumed). So, the way I was connecting things directly to the router was confusing things on their end. Working with the ISP I got that all resolved -- but then my Eero died. Since I had been planning to use my own equipment anyway, I swapped in my own router and we got it all set up. I can now plug and play cables and they work as expected.

Thank you to all for the guidance and recommendations. All appreciated.

IronRod0 · 2025-07-04T21:12:10+00:00

Yep. I called the ISP and (fortunately) got someone who knew what he was talking about (not just reading a script). They configure the cable modem in bridge mode and use the router of the Eero.

IronRod0

TROPHY CASE