Groups | Search | Server Info | Login | Register
Groups > comp.os.linux.misc > #37645
| From | TJ <TJ@noneofyour.business> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: Release upgrade problems |
| Date | 2023-03-25 18:57 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <tvnu7v$2cdlc$1@dont-email.me> (permalink) |
| References | (1 earlier) <tvfhb8$nr7m$5@dont-email.me> <tvn0su$27bkh$2@dont-email.me> <tvn6op$2853g$3@dont-email.me> <87tty8d49s.fsf@usenet.ankman.de> <tvnng6$2aprn$5@dont-email.me> |
On 2023-03-25 17:01, The Natural Philosopher wrote: > On 25/03/2023 19:23, Andreas Kohlbach wrote: >> On Sat, 25 Mar 2023 17:16:25 +0100, Marco Moock wrote: >>> >>> Am 25.03.2023 um 15:36:14 Uhr schrieb db: >>> >>>> This seems like a dangerous thing to do. Is it safe? I do see >>>> a lot of instances of "bionic" in etc/apt/sources.list >>> >>> That is a normal way to do it - the default for Debian. >>> I did it many times - without any problems. >> >> I ran into problems twice. After the upgrade it hung in the display >> manager login screen without being able to choose to log in. Only the >> mouse pointer was moving. IIRC it also wouldn't let me login from a TTY. >> >> Anyway, I still see this as an option. Because otherwise you have an >> outdated installation (accumulating bugs over time). If lucky, the >> upgrade works. If not, install something fresh. > Sometimes it works and sometimes it doesn't > > I tried to incrementally upgrade from Mint17 to Mint 20 in 'easy stages' > but halfway along something broke, and I ended up with a clean install > and spending the time recreating the environment instead > Upgrade problems are more likely if you use the Plasma DE, IMO. The Friendly Folks at KDE have a habit of re-arranging where settings are found and changing defaults to what *they* think you *ought* to want, instead of letting you keep your own decisions. TJ
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar
Release upgrade problems db <dieterhansbritz@gmail.com> - 2023-03-22 15:15 +0100
Re: Release upgrade problems The Natural Philosopher <tnp@invalid.invalid> - 2023-03-22 15:07 +0000
Re: Release upgrade problems Pancho <Pancho.Jones@proton.me> - 2023-03-22 15:34 +0000
Re: Release upgrade problems Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-03-22 17:51 +0000
Re: Release upgrade problems Marco Moock <mo01@posteo.de> - 2023-03-22 19:27 +0100
Re: Release upgrade problems Pancho <Pancho.Jones@proton.me> - 2023-03-23 08:28 +0000
Re: Release upgrade problems Joerg Lorenz <hugybear@gmx.ch> - 2023-03-22 19:15 +0100
Re: Release upgrade problems Joerg Lorenz <hugybear@gmx.ch> - 2023-03-25 18:28 +0100
Re: Release upgrade problems Marco Moock <mo01@posteo.de> - 2023-03-22 19:27 +0100
Re: Release upgrade problems db <dieterhansbritz@gmail.com> - 2023-03-25 15:36 +0100
Re: Release upgrade problems Marco Moock <mo01@posteo.de> - 2023-03-25 17:16 +0100
Re: Release upgrade problems Andreas Kohlbach <ank@spamfence.net> - 2023-03-25 15:23 -0400
Re: Release upgrade problems The Natural Philosopher <tnp@invalid.invalid> - 2023-03-25 21:01 +0000
Re: Release upgrade problems TJ <TJ@noneofyour.business> - 2023-03-25 18:57 -0400
Re: Release upgrade problems Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2023-03-23 15:20 +0200
Re: Release upgrade problems Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2023-03-26 20:07 +0300
csiph-web