Public bug reported:
This issue when upgrading to 26.04 beta, I had the bad idea to look at a Config
file (or differences file ?) when asked, then I could not exit the text editor,
then did a CTRL+C (perhaps the right command should have been ':q'), this broke
the upgrade :(
I was stuck on Ubuntu failing to load for several days, until I have the idea
the select the previous Kernel version at boot. Still have no idea how I will
fix the issue, I hope system updates will do it.
Perhaps my report will help next users: Canonical please tell newbies
how to exit this text editor before to open it :)
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: ubuntu-release-upgrader-core 1:26.04.13
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Uname: Linux 7.0.0-7-generic x86_64
ApportVersion: 2.33.1-0ubuntu7
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CrashReports: 644:0:109:0:2026-04-13 06:35:01.687470123 +0200:2026-04-07
23:43:51.792999919 +0200:/var/crash/kdump_lock
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 13 06:36:47 2026
InstallationDate: Installed on 2025-07-18 (269 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
Log time: 2026-04-13 06:34:00.015250
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
Entering ResolveByKeep
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug dist-upgrade resolute wayland-session
** Description changed:
- This issue when upgrading to 26.04, I had the bad idea to look at a Config
file when asked, then I could not exit the text editor, then did a CTRL+C
(perhaps the right commande should have be ':q', this broke the upgrade :(
+ This issue when upgrading to 26.04, I had the bad idea to look at a Config
file when asked, then I could not exit the text editor, then did a CTRL+C
(perhaps the right command should have been ':q'), this broke the upgrade :(
I was stuck on Ubuntu failing to load for several days, until I have the idea
the select the previous Kernel version at boot. Still have no idea how I will
fix the issue, I hope system updates will do it.
Perhaps my report will help next users: Canonical please write how to
exit this text editor :)
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: ubuntu-release-upgrader-core 1:26.04.13
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Uname: Linux 7.0.0-7-generic x86_64
ApportVersion: 2.33.1-0ubuntu7
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CrashReports: 644:0:109:0:2026-04-13 06:35:01.687470123 +0200:2026-04-07
23:43:51.792999919 +0200:/var/crash/kdump_lock
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 13 06:36:47 2026
InstallationDate: Installed on 2025-07-18 (269 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64
(20250215)
PackageArchitecture: all
ProcEnviron:
- LANG=fr_FR.UTF-8
- PATH=(custom, no user)
- SHELL=/bin/bash
- TERM=xterm-256color
- XDG_RUNTIME_DIR=<set>
+ LANG=fr_FR.UTF-8
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ TERM=xterm-256color
+ XDG_RUNTIME_DIR=<set>
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
- Log time: 2026-04-13 06:34:00.015250
- Starting pkgProblemResolver with broken count: 0
- Starting 2 pkgProblemResolver with broken count: 0
- Done
- Entering ResolveByKeep
+ Log time: 2026-04-13 06:34:00.015250
+ Starting pkgProblemResolver with broken count: 0
+ Starting 2 pkgProblemResolver with broken count: 0
+ Done
+ Entering ResolveByKeep
** Description changed:
- This issue when upgrading to 26.04, I had the bad idea to look at a Config
file when asked, then I could not exit the text editor, then did a CTRL+C
(perhaps the right command should have been ':q'), this broke the upgrade :(
+ This issue when upgrading from 25.10 to 26.04 beta, I had the bad idea to
look at a Config file when asked, then I could not exit the text editor, then
did a CTRL+C (perhaps the right command should have been ':q'), this broke the
upgrade :(
I was stuck on Ubuntu failing to load for several days, until I have the idea
the select the previous Kernel version at boot. Still have no idea how I will
fix the issue, I hope system updates will do it.
Perhaps my report will help next users: Canonical please write how to
exit this text editor :)
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: ubuntu-release-upgrader-core 1:26.04.13
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Uname: Linux 7.0.0-7-generic x86_64
ApportVersion: 2.33.1-0ubuntu7
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CrashReports: 644:0:109:0:2026-04-13 06:35:01.687470123 +0200:2026-04-07
23:43:51.792999919 +0200:/var/crash/kdump_lock
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 13 06:36:47 2026
InstallationDate: Installed on 2025-07-18 (269 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64
(20250215)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
Log time: 2026-04-13 06:34:00.015250
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
Entering ResolveByKeep
** Description changed:
- This issue when upgrading from 25.10 to 26.04 beta, I had the bad idea to
look at a Config file when asked, then I could not exit the text editor, then
did a CTRL+C (perhaps the right command should have been ':q'), this broke the
upgrade :(
+ This issue when upgrading from 25.10 to 26.04 beta, I had the bad idea to
look at a Config file (or differences file ?) when asked, then I could not exit
the text editor, then did a CTRL+C (perhaps the right command should have been
':q'), this broke the upgrade :(
I was stuck on Ubuntu failing to load for several days, until I have the idea
the select the previous Kernel version at boot. Still have no idea how I will
fix the issue, I hope system updates will do it.
- Perhaps my report will help next users: Canonical please write how to
- exit this text editor :)
+ Perhaps my report will help next users: Canonical please tell newbies
+ how to exit this text editor before to open it :)
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: ubuntu-release-upgrader-core 1:26.04.13
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Uname: Linux 7.0.0-7-generic x86_64
ApportVersion: 2.33.1-0ubuntu7
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CrashReports: 644:0:109:0:2026-04-13 06:35:01.687470123 +0200:2026-04-07
23:43:51.792999919 +0200:/var/crash/kdump_lock
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 13 06:36:47 2026
InstallationDate: Installed on 2025-07-18 (269 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64
(20250215)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
Log time: 2026-04-13 06:34:00.015250
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
Entering ResolveByKeep
** Summary changed:
- Problem when upgrading to 26.04 beta
+ Problem when upgrading to 26.04 beta after exiting a text viewer
** Description changed:
- This issue when upgrading from 25.10 to 26.04 beta, I had the bad idea to
look at a Config file (or differences file ?) when asked, then I could not exit
the text editor, then did a CTRL+C (perhaps the right command should have been
':q'), this broke the upgrade :(
+ This issue when upgrading to 26.04 beta, I had the bad idea to look at a
Config file (or differences file ?) when asked, then I could not exit the text
editor, then did a CTRL+C (perhaps the right command should have been ':q'),
this broke the upgrade :(
I was stuck on Ubuntu failing to load for several days, until I have the idea
the select the previous Kernel version at boot. Still have no idea how I will
fix the issue, I hope system updates will do it.
Perhaps my report will help next users: Canonical please tell newbies
how to exit this text editor before to open it :)
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: ubuntu-release-upgrader-core 1:26.04.13
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Uname: Linux 7.0.0-7-generic x86_64
ApportVersion: 2.33.1-0ubuntu7
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CrashReports: 644:0:109:0:2026-04-13 06:35:01.687470123 +0200:2026-04-07
23:43:51.792999919 +0200:/var/crash/kdump_lock
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 13 06:36:47 2026
InstallationDate: Installed on 2025-07-18 (269 days ago)
InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64
(20250215)
PackageArchitecture: all
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
Log time: 2026-04-13 06:34:00.015250
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
Entering ResolveByKeep
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2148151
Title:
Problem when upgrading to 26.04 beta after exiting a text viewer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2148151/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
