Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #81458 > unrolled thread

Bug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version

Started byCarlos Suérez <bitseater@gmail.com>
First post2024-01-06 14:10 +0100
Last post2024-01-07 12:00 +0100
Articles 4 — 2 participants

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version Carlos Suérez <bitseater@gmail.com> - 2024-01-06 14:10 +0100
    Bug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version Salvatore Bonaccorso <carnil@debian.org> - 2024-01-06 15:50 +0100
      Bug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version Carlos Suérez <bitseater@gmail.com> - 2024-01-07 01:20 +0100
        Bug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version Carlos Suérez <bitseater@gmail.com> - 2024-01-07 12:00 +0100

#81458 — Bug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version

FromCarlos Suérez <bitseater@gmail.com>
Date2024-01-06 14:10 +0100
SubjectBug#1060150: linux-image-6.6.9-amd64: Unable to update to 6.6.9-1 version
Message-ID<HTeB4-1dDY-15@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Package: linux-image-6.6.9-amd64
Version: 6.6.9-1
Severity: important

Dear Maintainer,

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

* What led up to the situation? System update failure with manual 'apt
update' at terminal.
* What exactly did you do (or not do) that was effective (or
ineffective)? I have tried to install the package only
* What was the outcome of this action? I get the same error
* What outcome did you expect instead? Update done


-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.8-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE 
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-6.6.9-amd64 depends on:
ii initramfs-tools [linux-initramfs-tool] 0.142
ii kmod 31-1
ii linux-base 4.9

Versions of packages linux-image-6.6.9-amd64 recommends:
ii apparmor 3.0.12-1+b2
ii firmware-linux-free 20200122-3

Versions of packages linux-image-6.6.9-amd64 suggests:
pn debian-kernel-handbook <none>
ii grub-pc 2.12~rc1-12

pn linux-doc-6.6 <none>


*** Output when i try to update/install the linux-image package from 
6.6.8 to 6.6.9 ***

> /run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return 
> code 127
> dpkg: error al procesar el paquete linux-image-6.6.9-amd64 (--configure):
>  el subproceso instalado paquete linux-image-6.6.9-amd64 script 
> post-installatio
> n devolvió el código de salida de error 1
> Se encontraron errores al procesar:
>  linux-image-6.6.9-amd64
> E: Sub-process /usr/bin/dpkg returned an error code (1)/

Thanks for your attention and greetings.


Carlos Suárez (bitseater)

[toc] | [next] | [standalone]

#81467

FromSalvatore Bonaccorso <carnil@debian.org>
Date2024-01-06 15:50 +0100
Message-ID<HTg9P-1epS-1@gated-at.bofh.it>
In reply to#81458
Hi,

On Sat, Jan 06, 2024 at 02:00:58PM +0100, Carlos Suérez wrote:
> Package: linux-image-6.6.9-amd64
> Version: 6.6.9-1
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate
> ***
> 
> * What led up to the situation? System update failure with manual 'apt
> update' at terminal.
> * What exactly did you do (or not do) that was effective (or
> ineffective)? I have tried to install the package only
> * What was the outcome of this action? I get the same error
> * What outcome did you expect instead? Update done
> 
> 
> -- System Information:
> Debian Release: trixie/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.6.8-amd64 (SMP w/12 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_USER
> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages linux-image-6.6.9-amd64 depends on:
> ii initramfs-tools [linux-initramfs-tool] 0.142
> ii kmod 31-1
> ii linux-base 4.9
> 
> Versions of packages linux-image-6.6.9-amd64 recommends:
> ii apparmor 3.0.12-1+b2
> ii firmware-linux-free 20200122-3
> 
> Versions of packages linux-image-6.6.9-amd64 suggests:
> pn debian-kernel-handbook <none>
> ii grub-pc 2.12~rc1-12
> 
> pn linux-doc-6.6 <none>
> 
> 
> *** Output when i try to update/install the linux-image package from 6.6.8
> to 6.6.9 ***
> 
> > /run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return
> > code 127
> > dpkg: error al procesar el paquete linux-image-6.6.9-amd64 (--configure):
> >  el subproceso instalado paquete linux-image-6.6.9-amd64 script
> > post-installatio
> > n devolvió el código de salida de error 1
> > Se encontraron errores al procesar:
> >  linux-image-6.6.9-amd64
> > E: Sub-process /usr/bin/dpkg returned an error code (1)/

Can you please provide the full log of the update, which other
packages are involved? Do you have any dkms modules packages
installed?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#81473

FromCarlos Suérez <bitseater@gmail.com>
Date2024-01-07 01:20 +0100
Message-ID<HTp3r-1k5G-1@gated-at.bofh.it>
In reply to#81467

[Multipart message — attachments visible in raw view] — view raw

Hi ,

The full log for that upgrade was:

> Start-Date: 2024-01-02 20:30:06
> Commandline: apt upgrade
> Requested-By: bitseater (1000)
> Install: linux-image-6.6.9-amd64:amd64 (6.6.9-1, automatic)
> Upgrade: qemu-system-x86:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
> udev:amd64 (255.2-2, 255.2-3), libexttextcat-2.0-0:amd64 (3.4.6-1, 
> 3.4.7-1), libmm-glib0:amd64 (1.22.0-1, 1.22.0-2), 
> systemd-container:amd64 (255.2-2, 255.2-3), libnss-myhostname:amd64 
> (255.2-2, 255.2-3), modemmanager:amd64 (1.22.0-1, 1.22.0-2), 
> qemu-system-modules-opengl:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
> libpam-systemd:amd64 (255.2-2, 255.2-3), sed:amd64 (4.9-1, 4.9-2), 
> xxd:amd64 (2:9.0.2116-1, 2:9.0.2189-1), python3-httpx:amd64 (0.23.3-1, 
> 0.26.0-1), libnorm1:amd64 (1.5.9+dfsg-2, 1.5.9+dfsg-3), 
> vim-common:amd64 (2:9.0.2116-1, 2:9.0.2189-1), 
> qemu-system-modules-spice:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
> libsystemd0:amd64 (255.2-2, 255.2-3), libudev-dev:amd64 (255.2-2, 
> 255.2-3), systemd:amd64 (255.2-2, 255.2-3), libudev1:amd64 (255.2-2, 
> 255.2-3), qemu-utils:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
> systemd-dev:amd64 (255.2-2, 255.2-3), libnss-mymachines:amd64 
> (255.2-2, 255.2-3), linux-image-amd64:amd64 (6.6.8-1, 6.6.9-1), 
> vim-tiny:amd64 (2:9.0.2116-1, 2:9.0.2189-1), qemu-system-misc:amd64 
> (1:8.2.0+ds-1, 1:8.2.0+ds-2), libcrypt-dev:amd64 (1:4.4.36-2, 
> 1:4.4.36-4), multipath-tools:amd64 (0.9.4-7, 0.9.4-10), 
> libcrypt1:amd64 (1:4.4.36-2, 1:4.4.36-4), qemu-system-common:amd64 
> (1:8.2.0+ds-1, 1:8.2.0+ds-2), python3-httpcore:amd64 (0.17.3-1, 
> 1.0.2-1), qemu-block-extra:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
> libopenmpi3:amd64 (4.1.6-4, 4.1.6-5), libsystemd-shared:amd64 
> (255.2-2, 255.2-3), systemd-sysv:amd64 (255.2-2, 255.2-3), 
> libexttextcat-data:amd64 (3.4.6-1, 3.4.7-1), libxml-parser-perl:amd64 
> (2.46-4, 2.47-1), qemu-system-data:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
> kpartx:amd64 (0.9.4-7, 0.9.4-10), valgrind:amd64 (1:3.20.0-2, 
> 1:3.20.0-2.1), qemu-system-gui:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
> libsystemd-dev:amd64 (255.2-2, 255.2-3), linux-libc-dev:amd64 
> (6.6.8-1, 6.6.9-1)
> Error: Sub-process /usr/bin/dpkg returned an error code (1)
> End-Date: 2024-01-02  20:31:08
/
/

I don't have any dkms module packages installed.


Regards


El 6/1/24 a las 15:40, Salvatore Bonaccorso escribió:
> Hi,
>
> On Sat, Jan 06, 2024 at 02:00:58PM +0100, Carlos Suérez wrote:
>> Package: linux-image-6.6.9-amd64
>> Version: 6.6.9-1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> *** Reporter, please consider answering these questions, where appropriate
>> ***
>>
>> * What led up to the situation? System update failure with manual 'apt
>> update' at terminal.
>> * What exactly did you do (or not do) that was effective (or
>> ineffective)? I have tried to install the package only
>> * What was the outcome of this action? I get the same error
>> * What outcome did you expect instead? Update done
>>
>>
>> -- System Information:
>> Debian Release: trixie/sid
>> APT prefers unstable
>> APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 6.6.8-amd64 (SMP w/12 CPU threads; PREEMPT)
>> Kernel taint flags: TAINT_USER
>> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not
>> set
>> Shell: /bin/sh linked to /usr/bin/dash
>> Init: systemd (via /run/systemd/system)
>> LSM: AppArmor: enabled
>>
>> Versions of packages linux-image-6.6.9-amd64 depends on:
>> ii initramfs-tools [linux-initramfs-tool] 0.142
>> ii kmod 31-1
>> ii linux-base 4.9
>>
>> Versions of packages linux-image-6.6.9-amd64 recommends:
>> ii apparmor 3.0.12-1+b2
>> ii firmware-linux-free 20200122-3
>>
>> Versions of packages linux-image-6.6.9-amd64 suggests:
>> pn debian-kernel-handbook <none>
>> ii grub-pc 2.12~rc1-12
>>
>> pn linux-doc-6.6 <none>
>>
>>
>> *** Output when i try to update/install the linux-image package from 6.6.8
>> to 6.6.9 ***
>>
>>> /run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return
>>> code 127
>>> dpkg: error al procesar el paquete linux-image-6.6.9-amd64 (--configure):
>>>   el subproceso instalado paquete linux-image-6.6.9-amd64 script
>>> post-installatio
>>> n devolvió el código de salida de error 1
>>> Se encontraron errores al procesar:
>>>   linux-image-6.6.9-amd64
>>> E: Sub-process /usr/bin/dpkg returned an error code (1)/
> Can you please provide the full log of the update, which other
> packages are involved? Do you have any dkms modules packages
> installed?
>
> Regards,
> Salvatore

[toc] | [prev] | [next] | [standalone]

#81476

FromCarlos Suérez <bitseater@gmail.com>
Date2024-01-07 12:00 +0100
Message-ID<HTz2O-1qx8-17@gated-at.bofh.it>
In reply to#81473

[Multipart message — attachments visible in raw view] — view raw

Hi Salvatore,

I have found an error in '/etc/grub.d//proxifiedScripts/linux' caused by 
grub-customizer. I have to uninstall grub-customizer, delete and purge 
all content about it. Then i can install linux-image-6.6.9-amd64. I'm 
sorry for the inconvenience.

Can you close this issue? Thanks.

Regards. Carlos Suárez

El 7/1/24 a las 1:15, Carlos Suárez escribió:
>
> Hi ,
>
> The full log for that upgrade was:
>
>> Start-Date: 2024-01-02  20:30:06
>> Commandline: apt upgrade
>> Requested-By: bitseater (1000)
>> Install: linux-image-6.6.9-amd64:amd64 (6.6.9-1, automatic)
>> Upgrade: qemu-system-x86:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
>> udev:amd64 (255.2-2, 255.2-3), libexttextcat-2.0-0:amd64 (3.4.6-1, 
>> 3.4.7-1), libmm-glib0:amd64 (1.22.0-1, 1.22.0-2), 
>> systemd-container:amd64 (255.2-2, 255.2-3), libnss-myhostname:amd64 
>> (255.2-2, 255.2-3), modemmanager:amd64 (1.22.0-1, 1.22.0-2), 
>> qemu-system-modules-opengl:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
>> libpam-systemd:amd64 (255.2-2, 255.2-3), sed:amd64 (4.9-1, 4.9-2), 
>> xxd:amd64 (2:9.0.2116-1, 2:9.0.2189-1), python3-httpx:amd64 
>> (0.23.3-1, 0.26.0-1), libnorm1:amd64 (1.5.9+dfsg-2, 1.5.9+dfsg-3), 
>> vim-common:amd64 (2:9.0.2116-1, 2:9.0.2189-1), 
>> qemu-system-modules-spice:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
>> libsystemd0:amd64 (255.2-2, 255.2-3), libudev-dev:amd64 (255.2-2, 
>> 255.2-3), systemd:amd64 (255.2-2, 255.2-3), libudev1:amd64 (255.2-2, 
>> 255.2-3), qemu-utils:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
>> systemd-dev:amd64 (255.2-2, 255.2-3), libnss-mymachines:amd64 
>> (255.2-2, 255.2-3), linux-image-amd64:amd64 (6.6.8-1, 6.6.9-1), 
>> vim-tiny:amd64 (2:9.0.2116-1, 2:9.0.2189-1), qemu-system-misc:amd64 
>> (1:8.2.0+ds-1, 1:8.2.0+ds-2), libcrypt-dev:amd64 (1:4.4.36-2, 
>> 1:4.4.36-4), multipath-tools:amd64 (0.9.4-7, 0.9.4-10), 
>> libcrypt1:amd64 (1:4.4.36-2, 1:4.4.36-4), qemu-system-common:amd64 
>> (1:8.2.0+ds-1, 1:8.2.0+ds-2), python3-httpcore:amd64 (0.17.3-1, 
>> 1.0.2-1), qemu-block-extra:amd64 (1:8.2.0+ds-1, 1:8.2.0+ds-2), 
>> libopenmpi3:amd64 (4.1.6-4, 4.1.6-5), libsystemd-shared:amd64 
>> (255.2-2, 255.2-3), systemd-sysv:amd64 (255.2-2, 255.2-3), 
>> libexttextcat-data:amd64 (3.4.6-1, 3.4.7-1), libxml-parser-perl:amd64 
>> (2.46-4, 2.47-1), qemu-system-data:amd64 (1:8.2.0+ds-1, 
>> 1:8.2.0+ds-2), kpartx:amd64 (0.9.4-7, 0.9.4-10), valgrind:amd64 
>> (1:3.20.0-2, 1:3.20.0-2.1), qemu-system-gui:amd64 (1:8.2.0+ds-1, 
>> 1:8.2.0+ds-2), libsystemd-dev:amd64 (255.2-2, 255.2-3), 
>> linux-libc-dev:amd64 (6.6.8-1, 6.6.9-1)
>> Error: Sub-process /usr/bin/dpkg returned an error code (1)
>> End-Date: 2024-01-02  20:31:08
> /
> /
>
> I don't have any dkms module packages installed.
>
>
> Regards
>
>
> El 6/1/24 a las 15:40, Salvatore Bonaccorso escribió:
>> Hi,
>>
>> On Sat, Jan 06, 2024 at 02:00:58PM +0100, Carlos Suérez wrote:
>>> Package: linux-image-6.6.9-amd64
>>> Version: 6.6.9-1
>>> Severity: important
>>>
>>> Dear Maintainer,
>>>
>>> *** Reporter, please consider answering these questions, where appropriate
>>> ***
>>>
>>> * What led up to the situation? System update failure with manual 'apt
>>> update' at terminal.
>>> * What exactly did you do (or not do) that was effective (or
>>> ineffective)? I have tried to install the package only
>>> * What was the outcome of this action? I get the same error
>>> * What outcome did you expect instead? Update done
>>>
>>>
>>> -- System Information:
>>> Debian Release: trixie/sid
>>> APT prefers unstable
>>> APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
>>> Architecture: amd64 (x86_64)
>>>
>>> Kernel: Linux 6.6.8-amd64 (SMP w/12 CPU threads; PREEMPT)
>>> Kernel taint flags: TAINT_USER
>>> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not
>>> set
>>> Shell: /bin/sh linked to /usr/bin/dash
>>> Init: systemd (via /run/systemd/system)
>>> LSM: AppArmor: enabled
>>>
>>> Versions of packages linux-image-6.6.9-amd64 depends on:
>>> ii initramfs-tools [linux-initramfs-tool] 0.142
>>> ii kmod 31-1
>>> ii linux-base 4.9
>>>
>>> Versions of packages linux-image-6.6.9-amd64 recommends:
>>> ii apparmor 3.0.12-1+b2
>>> ii firmware-linux-free 20200122-3
>>>
>>> Versions of packages linux-image-6.6.9-amd64 suggests:
>>> pn debian-kernel-handbook <none>
>>> ii grub-pc 2.12~rc1-12
>>>
>>> pn linux-doc-6.6 <none>
>>>
>>>
>>> *** Output when i try to update/install the linux-image package from 6.6.8
>>> to 6.6.9 ***
>>>
>>>> /run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return
>>>> code 127
>>>> dpkg: error al procesar el paquete linux-image-6.6.9-amd64 (--configure):
>>>>   el subproceso instalado paquete linux-image-6.6.9-amd64 script
>>>> post-installatio
>>>> n devolvió el código de salida de error 1
>>>> Se encontraron errores al procesar:
>>>>   linux-image-6.6.9-amd64
>>>> E: Sub-process /usr/bin/dpkg returned an error code (1)/
>> Can you please provide the full log of the update, which other
>> packages are involved? Do you have any dkms modules packages
>> installed?
>>
>> Regards,
>> Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web