Great thanks! I’ll watch the video and see if it clarifies things.

Ahh thanks!

Wtf is ApplicationDebuggable anti-feature?

I have a Surface 7 Pro running KDE Neon. I don’t have a pen, but touch screen works perfectly (you might need to manually install an on-screen keyboard beforehand, as usually Linux doesn’t preinstall one by default), and I’d assume pen would too. Webcams are going to be an issue. You can find all information and support tables/matrix on the linux-surface website.

https://github.com/linux-surface/linux-surface/wiki/Supported-Devices-and-Features#feature-matrix

Here’s a long explanation on the work being done to make the cameras work (hint -they don’t, for our SP7 for now): https://github.com/linux-surface/linux-surface/wiki/Camera-Support

I actually clicked on the replace partition option on the installer, instead of a full disk wipe. The profile did look brand new once I managed to login in safe mode, but I didn’t stay too long to check, as I just concluded hell, if it only boots in safe mode I might as well continue troubleshooting on the original install.

Anyway…After going back to the original image (as I had it backed up anyway), I paid a bit more attention at that weird popup on safe mode as I logged in, mentioning it failed to launch startlxde. So I ran

sudo dpkg --reconfigure sddm

And on the menu, for some reason sddm wasn’t the first choice. After choosing it again, this time it went straight to the boot screen. Some other day I’ll check again whichever random login menu is installed, and remove it, as it clearly causes issues.

I actually clicked on the replace partition option on the installer, instead of a full disk wipe. The profile did look brand new once I managed to login in safe mode, but I didn’t stay too long to check, as I just concluded hell, if it only boots in safe mode I might as well continue troubleshooting on the original install.

Anyway…After going back to the original image (as I had it backed up anyway), I paid a bit more attention at that weird popup on safe mode as I logged in, mentioning it failed to launch startlxde. So I ran

sudo dpkg --reconfigure sddm

And on the menu, for some reason sddm wasn’t the first choice. After choosing it again, this time it went straight to the boot screen. Some other day I’ll check again whichever random login menu is installed, and remove it, as it clearly causes issues.

Just an update. Today I made a rescuezilla full backup of the whole drive, and then wiped and installed KDE Neon brand new from Dec 1st release from their page. Guess what…that one ALSO fails to boot.

Just an update. Today I made a rescuezilla full backup of the whole drive, and then wiped and installed KDE Neon brand new from Dec 1st release from their page. Guess what…that one ALSO fails to boot.

Yeah…It looks to me like it just says it went alright, right until I hit the poweroff button, because it’s actually completely crashed.

Just an update. Today I made a rescuezilla full backup of the whole drive, and then wiped and installed KDE Neon brand new from Dec 1st release from their page. Guess what…that one ALSO fails to boot.

About that - I´d like to run a backup that takes all apps and their configuration files (more than my own docs and files, which I already have properly backed in Seafile). What would you recommend just for the apps, their configs (and maybe the repos) etc?

Dec 03 16:27:12 SurfaceNeon wpa_supplicant[1436]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=HK

Dec 03 16:27:12 SurfaceNeon NetworkManager[1428]: <info>  [1733214432.6906] manager: startup complete

Dec 03 16:27:12 SurfaceNeon systemd[1]: Finished NetworkManager-wait-online.service - Network Manager Wait Online.

Dec 03 16:27:12 SurfaceNeon systemd[1]: Reached target network-online.target - Network is Online.

Dec 03 16:27:12 SurfaceNeon systemd[1]: Started update-notifier-download.timer - Download data for packages that failed at 
package install time.

Dec 03 16:27:12 SurfaceNeon systemd[1]: Started update-notifier-motd.timer - Check to see whether there is a new version of Ubuntu available.

Dec 03 16:27:12 SurfaceNeon systemd[1]: Reached target timers.target - Timer Units.

Dec 03 16:27:12 SurfaceNeon systemd[1]: Started cups-browsed.service - Make remote CUPS printers available locally.

Dec 03 16:27:12 SurfaceNeon systemd[1]: Started deluged.service - Deluge Bittorrent Client Daemon.

Dec 03 16:27:12 SurfaceNeon systemd[1]: Reached target multi-user.target - Multi-User System.

Dec 03 16:27:12 SurfaceNeon systemd[1]: Reached target graphical.target - Graphical Interface.

Dec 03 16:27:12 SurfaceNeon systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP...

Dec 03 16:27:12 SurfaceNeon systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.

Dec 03 16:27:12 SurfaceNeon systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.

Dec 03 16:27:12 SurfaceNeon systemd[1]: Startup finished in 4.484s (firmware) + 6.837s (loader) + 3.208s (kernel) + 11.614s (userspace) = 26.145s.

Dec 03 16:27:12 SurfaceNeon systemd[1]: dmesg.service: Deactivated successfully.

Dec 03 16:27:14 SurfaceNeon ModemManager[1454]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin

Dec 03 16:27:20 SurfaceNeon systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

Dec 03 16:27:20 SurfaceNeon systemd-logind[1351]: Power key pressed short.

Dec 03 16:27:20 SurfaceNeon systemd-logind[1351]: Powering off...

Dec 03 16:27:20 SurfaceNeon systemd-logind[1351]: System is powering down.

deleted by creator

Thanks. I pulled the journalctl. This is…A bit extensive. EDIT: Well seems I only can see the KDE logo and a frozen gear, but according to systemctl the system is up and running, and the network connected? After 7 seconds frozen I give up once more and hold power button, since this is the only thing it seems to react to, and yet, even this gets logged onto journalctl.

I mean…I run the software discover update almost daily, whenever the icon pops in the tray…I don’t remember seeing anything scary on the update list, but I might have missed it.

Yeah…but usually the the sticker ones with a slide have a space where the cover slides to, and all that space will be over the screen. Unless you want to permanently cover the punch-hole camera.

Except these days the camera is a hole in the screen in a mobile phone, so you’d be effectively blocking part of the screen too.

So…both cloudflare tunnels and tailscale funnels would require to have the service exposed to have a link with a tailscale-running server, right? As in, every single of my services/containers running via funnel would need their own tailscale install. If it’s a web service I can publish it via the nginx proxy-tailscale one, but if it’s just a service with no defined URL, just the port, I need a tailscale funnel in every single container of these, right? Or am I getting this wrong?

Thanks!

Our only hope of anyone doing anything would be in the EU now.

Define “open”…Where? In the router? I’m…having the issue where my router I’m trying to set is behind CGNAT, and effectively locks me out of opening anything in it. I’m going through this Tailscale process in the hopes of being able to open specific apps and ports in my CGNAT-ed server.

Question…I started working on this. How would you go about opening an SSH or RDP port (on some random port such as 12345) on a local machine, in a way that I can reach it via the tailscale IP?