Siduction Forum

@alexsid
Wenn apt -s remove libavcodec61 keine Probleme ausspuckt, so kannst du es problemlos entfernen. War bei mir problemlos und hat keine Anwendungen ins Nirwana befördert.

libavutil59 konnte ich problemlos installieren. Gibt es da eventuell noch Abhängigkeiten, die das bei dir verhindern?

If apt -s remove libavcodec61 doesn't throw any errors, then you can remove it without any issues. It worked fine for me and didn't break any applications.

I was able to install libavutil59 without any problems. Are there perhaps still some dependencies preventing you from doing so?

~$ apt policy  libavutil59
libavutil59:
  Installiert:           7:7.1.5-0+deb13u1
  Installationskandidat: 7:7.1.5-0+deb13u1
  Versionstabelle:
 *** 7:7.1.5-0+deb13u1 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        500 http://debian.superhosting.cz/debian sid/main amd64 Packages
        500 http://debian.dynamica.it/debian sid/main amd64 Packages
        500 http://ftp.debian.sk/debian sid/main amd64 Packages
        100 /var/lib/dpkg/status
Mit apt -s install libavutil59 einmal die Probleme aufspüren.

Gleiches sollte bei libswresample5 der Fall sein.

Try running apt -s install libavutil59 to troubleshoot the issues.
The same should apply to libswresample5.


~$ apt policy libswresample5
libswresample5:
  Installiert:           7:7.1.5-0+deb13u1
  Installationskandidat: 7:7.1.5-0+deb13u1
  Versionstabelle:
 *** 7:7.1.5-0+deb13u1 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        500 http://debian.superhosting.cz/debian sid/main amd64 Packages
        500 http://debian.dynamica.it/debian sid/main amd64 Packages
        500 http://ftp.debian.sk/debian sid/main amd64 Packages
        100 /var/lib/dpkg/status

policycoreutils-dbus Warten oder entfernen, falls du darauf verzichten willst oder kannst.
Wait, or remove it if you want to or are able to.


edlin

Quote from: Teriarch on 2026/07/19, 00:40:15@alexsid
> Is Python 3.14 transition finished or not?
As far as the python3 version 3.14.6-1 suite of Debian is concerned,
the answer is yes, all dust and done.
If you still have problems updating, you have packages installed still
depending on python3 version 3.13.x-y. First of all you should identify
them, so an output of
$ sudo apt-get install python3
might be helpful. If virtualbox is holding back the transit, you either
wait for an update of virtualbox or follow the instructions from above.
In any case: It's not python's fault, when developers react late (esp.
virtualbox Debian developers) when they are informed months before the transit
takes place (esp. when the corrections are so easy, they hardly pose a one week's
challenge to undergraduate students of computer science).
 

THANK YOU
I did

sudo apt-get install python3

and it automatically updated LibreOffice files.

I still have 4 packages on hold. They are as follows:

 libavcodec61  libavutil59  libswresample5  policycoreutils-dbus

What shall I do?

Well, I don't use Virtualbox (at least I don't know Iuse it :-) )

Quote from: hsp on 2026/07/16, 16:26:50

Code Select Expand

libavcodec61 ist obsolete, austauchen gegen libavcodec62....

Habe ich versucht.

Ausgangslage:

Aktualisiere nicht:
  libavcodec61  libavcodec61:i386  libavfilter10  libavformat61  libavutil59  libavutil59:i386  libpostproc58  libswresample5  libswresample5:i386  libswscale8  policycoreutils-dbus  r-bioc-biocgenerics

Versuch:

┌──(isegrimm ㉿ T-A-K-A-Y-A)-▷[~]
└─▷$ doas apt install -s libavcodec62

libavcodec62 ist schon die neueste Version (7:8.1.2-2+b1).
libavcodec62 wurde als manuell installiert festgelegt.
Zusammenfassung:                   
  Aktualisiere: 0, Installiere: 0, Entferne: 0, Aktualisiere nicht: 12

Offensichtlich hat libavcodec62 keine Ersetzung von libavcodec61 durchgeführt.

Sollte ich jetzt libavcodec61 jetzt purgen oder wie kriege ich das gelöst?

Ich hab das jetzt mal via --dry-run getestet:

┌──(isegrimm ㉿ T-A-K-A-Y-A)-▷[~]
└─▷$ doas apt remove --dry-run libavcodec61

Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
  libavutil59  libkpipewire5        libplacebo351     libpostproc58   libsphinxbase3t64  libswresample5  libvidstab1.1  libwinpr2-2t64  pocketsphinx-en-us
  libicu72     libkpipewiredmabuf5  libpocketsphinx3  librubberband2  libsvtav1enc2      libswscale8     libvpx11       libx265-215
Verwenden Sie »apt autoremove«, um sie zu entfernen.

ENTFERNE:
  freerdp2-x11  libavcodec61  libavfilter10  libavformat61  libfreerdp-client2-2t64  libfreerdp2-2t64  libkpipewirerecord5  qml-module-org-kde-pipewire

Zusammenfassung:
  Aktualisiere: 0, Installiere: 0, Entferne: 8, Aktualisiere nicht: 9
Remv freerdp2-x11 [2.11.7+dfsg1-6]
Remv qml-module-org-kde-pipewire [5.27.11-1+b1]
Remv libkpipewirerecord5 [5.27.11-1+b1]
Remv libfreerdp-client2-2t64 [2.11.7+dfsg1-6]
Remv libfreerdp2-2t64 [2.11.7+dfsg1-6]
Remv libavcodec61 [7:7.1.3-1] [libavfilter10:amd64 libavformat61:amd64 ]
Remv libavfilter10 [7:7.1.3-1] [libavformat61:amd64 ]
Remv libavformat61 [7:7.1.3-1]

... und dann mit der *:i386-Version:

┌──(isegrimm ㉿ T-A-K-A-Y-A)-▷[~]
└─▷$ doas apt remove --dry-run libavcodec61:i386

Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
  libcairo-gobject2:i386    libgsm1:i386     libmp3lame0:i386     librav1e0.8:i386      libshine3:i386      libtheoradec2:i386  libvorbisenc2:i386  libx264-165:i386
  libcodec2-1.2:i386        libhwy1t64:i386  libmpg123-0t64:i386  librsvg2-2:i386       libsnappy1v5:i386   libtheoraenc2:i386  libvpx11:i386       libx265-215:i386
  libgdk-pixbuf-2.0-0:i386  libjxl0.11:i386  libogg0:i386         librsvg2-common:i386  libspeex1:i386      libtwolame0:i386    libwebp7:i386       libxvidcore4:i386
  libglycin-2-0:i386        liblcms2-2:i386  libopenjp2-7:i386    libseccomp2:i386      libsvtav1enc2:i386  libvorbis0a:i386    libwebpmux3:i386    libzvbi0t64:i386
Verwenden Sie »apt autoremove«, um sie zu entfernen.

ENTFERNE:
  libavcodec61:i386

Zusammenfassung:
  Aktualisiere: 0, Installiere: 0, Entferne: 1, Aktualisiere nicht: 11
Remv libavcodec61:i386 [7:7.1.3-1]

Sollte ich das so umsetzen?

Quote from: alexsid on 2026/07/18, 22:33:21Hi all!
Is Python 3.14 transition finished or not?
sudo apt full-upgrade
still holds 41 files from upgrade including libreoffice files.
How long shall we wait?

It was similar for me.

I then ran
apt install libreoffice and everything went smoothly.

-------------

Das war bei mir ähnlich.

Ich habe dann ein
apt install libreoffice durchgeführt und alles lief gut durch.

@alexsid
> Is Python 3.14 transition finished or not?
As far as the python3 version 3.14.6-1 suite of Debian is concerned,
the answer is yes, all dust and done.
If you still have problems updating, you have packages installed still
depending on python3 version 3.13.x-y. First of all you should identify
them, so an output of
$ sudo apt-get install python3
might be helpful. If virtualbox is holding back the transit, you either
wait for an update of virtualbox or follow the instructions from above.
In any case: It's not python's fault, when developers react late (esp.
virtualbox Debian developers) when they are informed months before the transit
takes place (esp. when the corrections are so easy, they hardly pose a one week's
challenge to undergraduate students of computer science).
 

Hi all!
Is Python 3.14 transition finished or not? 
sudo apt full-upgrade
still holds 41 files from upgrade including libreoffice files.
How long shall we wait?

I have since learnt, that after using kde for some time, the shutdown or hibernate from vty3 does not work any more. It also will hang when trying to shut the system off.

debian13-stable, TileOS-niri-Version(es gibt noch sway, miracle, qtile und river)
https://tile-os.com/
https://downloads.tile-os.com/stable/

   

I think I figured it out, but need more tests.  I think the problem was the changes I made when the virtual consoles stopped working.  towo had a post to fix it, but then an official fix came and I never reverted those commands that towo suggested. . I did it today and I think that the problem is fixed .

EDIT: No, it did not work. 🙁  It seems that there is some randomness, as the computer did turn off once (after logging in KDE and shutting down from there), but not at the end of the day.

My thinkpad T61 type 6463A13 is also affected by this. I ran a little test series:

When booting into init 3 (attach 3 at last position of linux boot line)
the following work impeccably:
systemctl suspend, shutdown, hibernate.

When booting into sddm, but not starting kde,
pressing the suspend, shutdown, hibernate icons on sddm screen,
they will all hang, producing heat and running the fan.
They then need a power off reset to come out of it.

The same behaviour happens when issuing the systemctl commands
from within konsole in kde.

When booting into sddm, then opening vty3 (ctrl-alt-F3)
the commands systemctl suspend, shutdown, hibernate will all work,
and the system will properly reduce energy consumption / shut off.
It can then be activated properly again.

What is the cause of this annoying behaviour?
thx, gnasch