[DE] Fehler bei Software-Installation

[hasan]

In Verbindung mit folgendem Thread, wo u.a. durch Treiberinstallation mein Sound-Problem gelöst wurde

https://forum.siduction.org/index.php?topic=9380.0

bekomme ich Fehlermeldung beim Installationsversuch z.B. von Chrome oder testweise auch von Opera (möglicherweise von ähnlicher Softwareinstallation überhaupt)

Fehler: >>libasound2<< kann nicht installiert werden

Im erwähnten Thread war sonst meine Frage im Begriff unterzugehen. Außerdem dachte ich, für dieses Thema ein extra Thread besser wäre für ähnliche Fälle.

[dibl]

Code: [Select]

$ sudo apt -s install libasound2

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 libasound2t64 : Breaks: libasound2 (< 1.2.11-1)
Error: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Code: [Select]

$ sudo apt policy libasound2t64

libasound2t64:
  Installed: 1.2.11-1+b1
  Candidate: 1.2.11-1+b1
  Version table:
 *** 1.2.11-1+b1 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
See:  https://forum.siduction.org/index.php?topic=9297.0

[hasan]

Sind diese Abhängigkeiten gut lösbar? Ich fühle mich nicht fähig genug, mich da ran zu machen,
obwohl ich nicht völlig unerfahren bin und auf dem Desktop-PC siduction-farewell-cinnamon-iso aus 2021 ohne Probleme als mein Haupt-OS ausschließlich verwendet habe.

Kann dieses Problem hier eventuell mit der iso zu tun haben, die ich hier (auf dem neuen Laptop) installiert habe
 siduction-Masters_of_War-cinnamon-amd64-latest.iso (22-1 aus 2022/12)
die scheint als eine letzte cinnamon-iso etwas zusammengeschustert zu sein, wo drin Einiges von KDE zu sehen ist (wie KDE-Connect-Einstellungen und KDE-Systemeinstellungen), was mich auch gewundert hatte.

Falls die Probleme an dieser nicht mehr ganz aktuellen cinnamon-iso liegt, also mein Wunsch nach cinnamon nicht mehr sinnvoll ist, bin ich bereit eine aktuelle iso mit Xfce auszuprobieren.

----------------------------------------------
EN:
Are these dependencies easy to resolve? I don't feel capable enough to tackle this,
although I'm not completely inexperienced and have used siduction-farewell-cinnamon-iso from 2021 as my main OS on the desktop PC without any problems.

Could this problem possibly have something to do with the iso that I installed here (on the new laptop)
siduction-Masters_of_War-cinnamon-amd64-latest.iso (22-1 from 2022/12)
it seems to be a bit cobbled together as a last cinnamon iso, where you can see some of KDE (like KDE Connect settings and KDE system settings), which also surprised me.

If the problems are due to this cinnamon iso that is no longer up to date, i.e. my desire for cinnamon no longer makes sense, I'm willing to try a current iso with Xfce.

[dibl]

Could this problem possibly have something to do with the iso that I installed here (on the new laptop)
siduction-Masters_of_War-cinnamon-amd64-latest.iso (22-1 from 2022/12)

No. If your installation is fully updated (i.e. you have run "apt update && apt full-upgrade" regularly), then it doesn't matter which ISO you originally used to install the system. You should have the same libasound2t64 package as I do.

Try

Code: [Select]

apt rdepends libasound2 to learn which package on your system has libasound2 as a dependency. That package is your problem. And I expect it is not a package from Debian sid, but instead is something you downloaded from elsewhere.

OR, if you are only seeing this error when you try to install a downloaded package, then you need to find the correct package in the Debian sid (unstable) repo, and use that one. ".deb" packages from other sources may have been compiled with a libasound2 dependency, and that won't be compatible with your system because, as you read in the link I gave before, Debian has replaced libasound2 with libasound2t64.

[hasan]

apt rdepends libasound2

libasound2
Reverse Depends:
  Hängt ab von: libatopology2 (>= 1.2.7.1)
    libasound2t64
  Hängt ab von: lxqt-panel (>= 1.0.16)
    libasound2t64
  Hängt ab von: vokoscreen (>= 1.0.16)
    libasound2t64
  Hängt ab von: qpwgraph (>= 1.0.16)
    libasound2t64
  Hängt ab von: google-android-extras-google-auto-installer (>= 1.0.16)
    libasound2t64
  Hängt ab von: torbrowser-launcher
    libasound2t64
    liboss4-salsa-asound2
  Hängt ab von: libwine-development (>= 1.0.16)
    libasound2t64
  Kollidiert mit: liboss4-salsa-asound2
    libasound2t64
  Hängt ab von: openjdk-19-jre-headless (>= 1.0.16)
    libasound2t64
  Empfiehlt: libopenal1 (>= 1.0.16)
    libasound2t64
  Schlägt vor: libmono-system4.0-cil (>> 1.0.18)
    libasound2t64
  Hängt ab von: lives (>= 1.0.16)
    libasound2t64
  Schlägt vor: libao4
    libasound2t64
    liboss4-salsa-asound2
  Schlägt vor: gimp
    libasound2t64
    liboss4-salsa-asound2
  Hängt ab von: libecereaudio0 (>= 1.0.16)
    libasound2t64
  Hängt ab von: dolphin-emu (>= 1.0.16)
    libasound2t64
  Ersetzt: libatopology2 (<< 1.2.1.1)
  Beschädigt: libatopology2 (<< 1.2.1.1)
  Beschädigt: libasound2t64 (<< 1.2.11-1)
  Ersetzt: libasound2t64
    libasound2t64
    liboss4-salsa-asound2
  Beschädigt: libasound2-data (<< 1.2.10-3)
  Ersetzt: libasound2-data (<< 1.2.10-3)

Yes, I'm trying to install google-chrome-stable_current_amd64.deb because Trust Crypto Wallet as a browser extension absolutely requires chrome. I also have that on the desktop as a second browser. I normally use Firefox.

[hasan]

I ran "apt update && apt full-upgrade". All packages are up to date.

No. If your installation is fully updated (i.e. you have run "apt update && apt full-upgrade" regularly), then it doesn't matter which ISO you originally used to install the system. You should have the same libasound2t64 package as I do.

Thanks, that means a lot to me

[dibl]

Yes, I'm trying to install google-chrome-stable_current_amd64.deb because Trust Crypto Wallet as a browser extension absolutely requires chrome. ...

Unfortunately, by replacing libasound2 with libasound2t64, Debian (unstable) has left your google-chrome-stable_xxxx package behind, for now. This is the risk you have when you use Debian unstable/sid for your operating system. Eventually, libasound2t64 will become the stable package, and your chrome version will be recompiled to be compatible. But for now, it is not compatible with your siduction system.   :'(

[towo]

Code: [Select]

~
towo:Defiant> dpkg -l | grep -iE "google-chrome|libasound"
ii  google-chrome-stable                                     126.0.6478.126-1                         amd64        The web browser from Google
ii  libasound2-data                                          1.2.11-1                                 all          Configuration files and profiles for ALSA drivers
ii  libasound2-dev:amd64                                     1.2.11-1+b1                              amd64        shared library for ALSA applications -- development files
ii  libasound2-plugin-equal:amd64                            0.6-8+b2                                 amd64        equalizer plugin for ALSA
ii  libasound2-plugins:amd64                                 1:1.2.12-dmo1                            amd64        ALSA library additional plugins
ii  libasound2-plugins:i386                                  1:1.2.12-dmo1                            i386         ALSA library additional plugins
ii  libasound2t64:amd64                                      1.2.11-1+b1                              amd64        shared library for ALSA applications
ii  libasound2t64:i386                                       1.2.11-1+b1                              i386         shared library for ALSA applications

[hasan]

All right, then I'll wait and see. Now that I understand the situation, it's not difficult for me.

Thank you very much for everything!

Not necessarily that important, but for me, from a technical point of view, the point remains to understand how I was able to install Chrome on the desktop PC using Siduction

@towo, is what you're showing a possible workaround to get to Chrome? If so, how do you handle it?

[towo]

@towo, is what you're showing a possible workaround to get to Chrome? If so, how do you handle it?

I do not have applied any workaround, chrome is installed since ages and as log, you do not show us, the output of

Code: [Select]

apt full-upgrade
no one can say anything. It's your system and only you see, what's on your screen.

[hendrikL]

I have just (Mi 26. Jun 07:30:25 CEST 2024) installed chrome stable!

Code: [Select]

dpkg -l | grep -iE "google-chrome|libasound"

ii  google-chrome-stable                                     126.0.6478.126-1                         amd64        The web browser from Google
ii  libasound2-data                                          1.2.11-1                                 all          Configuration files and profiles for ALSA drivers
ii  libasound2-plugins:amd64                                 1.2.7.1-1+b2                             amd64        ALSA library additional plugins
ii  libasound2t64:amd64                                      1.2.11-1+b2                              amd64        shared library for ALSA applications


Code: [Select]

sudo apt install --solver 3.0 ./google-chrome-stable_current_amd64.deb
Hinweis: »google-chrome-stable« wird an Stelle von »./google-chrome-stable_current_amd64.deb« gewählt.
Installing:                 
  google-chrome-stable

Installing dependencies:
  libu2f-udev

Summary:
  Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 22
  Download size: 4.712 B / 109 MB
  Space needed: 348 MB / 85,9 GB available

Continue? [J/n]
Holen:1 https://deb.debian.org/debian unstable/main amd64 libu2f-udev all 1.1.10-3.2 [4.712 B]
Holen:2 /home/hhl/Downloads/google-chrome-stable_current_amd64.deb google-chrome-stable amd64 126.0.6478.126-1 [109 MB]
Es wurden 4.712 B in 2 s geholt (2.502 B/s).
Laden der Fehlerberichte … Erledigt
»Found/Fixed«-Informationen werden ausgewertet … Erledigt
Vormals nicht ausgewähltes Paket libu2f-udev wird gewählt.
(Lese Datenbank ... 342746 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libu2f-udev_1.1.10-3.2_all.deb ...
Entpacken von libu2f-udev (1.1.10-3.2) ...
Vormals nicht ausgewähltes Paket google-chrome-stable wird gewählt.
Vorbereitung zum Entpacken von .../google-chrome-stable_current_amd64.deb ...
Entpacken von google-chrome-stable (126.0.6478.126-1) ...
libu2f-udev (1.1.10-3.2) wird eingerichtet ...
google-chrome-stable (126.0.6478.126-1) wird eingerichtet ...
update-alternatives: /usr/bin/google-chrome-stable wird verwendet, um /usr/bin/x-www-browser (x-www-browser) im automatischen Modus bereitzustellen
update-alternatives: /usr/bin/google-chrome-stable wird verwendet, um /usr/bin/gnome-www-browser (gnome-www-browser) im automatischen Modus bereitzustellen
update-alternatives: /usr/bin/google-chrome-stable wird verwendet, um /usr/bin/google-chrome (google-chrome) im automatischen Modus bereitzustellen
Trigger für man-db (2.12.1-2) werden verarbeitet ...
Trigger für menu (2.1.50) werden verarbeitet ...
Trigger für mailcap (3.72) werden verarbeitet ...
Trigger für desktop-file-utils (0.27-2) werden verarbeitet ...

If the apt option --solver 3.0 is needed?
I am not sure, I used it for no reason, maybe because I wanted to be on the save side.

[hasan]

It worked, just like it did for you, thank you very much hendrikL

Code: [Select]

dpkg -l | grep -iE "google-chrome|libasound"
ii  google-chrome-stable                                 126.0.6478.114-1              amd64        The web browser from Google
ii  libasound2-data                                          1.2.11-1                             all                Configuration files and profiles for ALSA drivers
ii  libasound2-plugins:amd64                          1.2.7.1-1+b2                      amd64        ALSA library additional plugins
ii  libasound2t64:amd64                                  1.2.11-1+b1                       amd64        shared library for ALSA applications

At the end there was the note

Code: [Select]

Notice: Der Download wird als root und nicht Sandbox-geschützt durchgeführt, da auf die Datei »/home/haso/ev/allg/Linux/chrome/google-chrome-stable_current_amd64.deb« durch den Benutzer »_apt« nicht zugegriffen werden kann. - pkgAcquire::Run (13: Keine Berechtigung)
In any case, chrome could now be started without a password, unlike chrome on my desktop, which was annoying there. Could this possibly have something to do with your --solver 3.0? Many thanks again

[hendrikL]

In this case, I don't think that the solver option was needed.

https://linuxnews.de/apt-2-9-3-fuehrt-neuen-solver-ein/


The note at the end only informs you, that you doesn't worked in a chroot environnement or similar, not sandboxed.

[hasan]

All right, thanks hendrik