[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1016874: marked as done (bugs.debian.org: PC unable to boot after package update)

Your message dated Thu, 20 Feb 2025 14:59:51 +0100 (CET)
with message-id <20250220135951.61896BE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1016874,
regarding bugs.debian.org: PC unable to boot after package update
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1016874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016874
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: bugs.debian.org
Severity: normal
X-Debbugs-Cc: shatin85@mail.ru

Dear Maintainer,

Last package update put my pc into boot-loop. This was solved by selecting boot
option manually (pc has dual boot). Also I suspect the BIOS settings were
affected.

video: https://youtu.be/Ax5ENzazpL0

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Update through Synaptic package manager of the following packages:
aspnetcore-runtime-6.0 (6.0.6-1) to 6.0.7-1
aspnetcore-targeting-pack-6.0 (6.0.6-1) to 6.0.7-1
code (1.69.0-1657183742) to 1.70.0-1659589288
curl (7.74.0-1.3+deb11u1) to 7.74.0-1.3+deb11u2
dotnet-apphost-pack-6.0 (6.0.6-1) to 6.0.7-1
dotnet-host (6.0.6-1) to 6.0.7-1
dotnet-hostfxr-6.0 (6.0.6-1) to 6.0.7-1
dotnet-runtime-6.0 (6.0.6-1) to 6.0.7-1
dotnet-runtime-deps-6.0 (6.0.6-1) to 6.0.7-1
dotnet-sdk-6.0 (6.0.301-1) to 6.0.302-1
dotnet-targeting-pack-6.0 (6.0.6-1) to 6.0.7-1
firefox-esr (91.11.0esr-1~deb11u1) to 91.12.0esr-1~deb11u1
gir1.2-javascriptcoregtk-4.0 (2.36.3-1~deb11u1) to 2.36.4-1~deb11u1
gir1.2-webkit2-4.0 (2.36.3-1~deb11u1) to 2.36.4-1~deb11u1
libcurl3-gnutls (7.74.0-1.3+deb11u1) to 7.74.0-1.3+deb11u2
libcurl4 (7.74.0-1.3+deb11u1) to 7.74.0-1.3+deb11u2
libjavascriptcoregtk-4.0-18 (2.36.3-1~deb11u1) to 2.36.4-1~deb11u1
libtirpc-common (1.3.1-1) to 1.3.1-1+deb11u1
libtirpc3 (1.3.1-1) to 1.3.1-1+deb11u1
libwebkit2gtk-4.0-37 (2.36.3-1~deb11u1) to 2.36.4-1~deb11u1
linux-image-5.10.0-16-amd64 (5.10.127-1) to 5.10.127-2
linux-image-amd64 (5.10.127-1) to 5.10.127-2
xserver-common (2:1.20.11-1+deb11u1) to 2:1.20.11-1+deb11u2
xserver-xephyr (2:1.20.11-1+deb11u1) to 2:1.20.11-1+deb11u2
xserver-xorg-core (2:1.20.11-1+deb11u1) to 2:1.20.11-1+deb11u2
xserver-xorg-legacy (2:1.20.11-1+deb11u1) to 2:1.20.11-1+deb11u2
xwayland (2:1.20.11-1+deb11u1) to 2:1.20.11-1+deb11u2


   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Entered boot menu by pressing hardware key, choose boot option manually.

   * What was the outcome of this action?

After manual selection of the boot option, pc can boot. If booted into windows,
successive boots are ok, until booting debian.

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: