I am working up to upgrading my desktop machine's Debian 9 installation to Debian 10 (an upgrade, not a clean install). For previous upgrades, the release notes warned not to run the apt upgrade commands from a terminal within the desktop GUI, which might become unstable during the upgrade. Rather, the instructions said to use a virtual console running the screen program.

I don't see any of this in the release notes for Debian 10 (unless you are running the upgrade from a remote machine). Did I just miss something, or is it now OK to run the apt upgrade commands from a terminal in the desktop GUI?

I did some searches but didn't find anything on this question.

Thanks.

https://www.cyberciti.biz/faq/update...10-buster/amp/

May help?

1 members found this post helpful.

The instructions in your link seem entirely consistent with the release notes. I guess I'll press on with the upgrade without the VCs and screen. Thanks. I'll mark this "solved".

I use kubuntu, a Debian derivative, and I have never had an issue with doing an upgrade from a GUI terminal (konsole.)

1 members found this post helpful.

Although you marked this as solved, I thought I might chime in that I found no issue running the upgrade from the terminal using apt from 9 to 10.

I hadn't seen the link presented here before doing it, but simply did it in the old 3 pass method, updating after setting the sources list, then using upgrade / reboot / full-upgrade. I haven't had any issues in the many months since.

1 members found this post helpful.

jamison20000e, josephj, bogs: I do appreciate very much your helpful replies. Virtual consoles and the screen program are a significant impediment if, like me, your experience with them is minimal.

1 members found this post helpful.

I often do it with a GUI but it won't hurt without, could run into issues either way?

Normally I use a quick work around and throw a hashtag in front of "/usr/bin/sddm" sddm in my case at /etc/X11/default-display-monitor then for the GUI just "startx" or "startx /usr/bin/kde4" again KDE in my case.

Have fun!

1 members found this post helpful.

This worked: http://ask.xmodulo.com/boot-into-com...tu-debian.html
seems my old workaround won't anymore...

1 members found this post helpful.

I have to admit I have been wondering about this. Now I am wondering if this is different from booting into recovery mode from the Grub menu, which also gives a text-only window.

I had to go doodle with the Grub recovery mode login. After login as root, all the disks in fstab were mounted, but I didn't have internet access. I ran 'NetworkManager up', which appeared to start networking but did not give internet access -- until I added the 'up' option. At least 'up' enabled pings.