Unable to update, possibly A2DP issue?

Hi everyone,

I’ve been unable to update my OSMC (running on Pi3), ever since I installed retropi as a service. From reading around, I believe this is due to me installing bluetooth profiles? Can’t be sure however as my linux experience is rather limited. As requested, log is here:

https://paste.osmc.tv/yaguwocuqu

Any help resolving this issue is much appreciated, as I know i’m at least 6 months behind on updates and am missing some essential security patches.

Thanks and look forward to receiving any help!

Ian

After a bit more reading around (specifically here:

and

Udisks.service fails after latest update - #25 by dillthedog )

it would appear the error is caused due to using the Jessie staging repo? here’s my sources.list output:

osmc@osmc:/etc/apt$ cat sources.list

deb http://ftp.debian.org/debian jessie main contrib non-free

deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free

deb http://apt.osmc.tv jessie main

deb http://archive.raspberrypi.org/debian/ jessie main staging

deb-src http://archive.raspberrypi.org/debian/ jessie main staging

am I on the right track?

Well first I would try to remove this two lines and run update and dist-upgrade.

But you might have more issues than just that

Thank you fzinken, could you point me to a way to delete these sources? All my searches point to deleting media sources!

Well I wonder how you managed to get them in :slight_smile:

sudo nano /etc/apt/sources.list

A little knowledge is a very dangerous thing! :no_mouth:

Removed them, will try update again and report back, thanks for your help!

osmc@osmc:/etc/apt$ sudo apt-get update
Ign http://ftp.debian.org jessie InRelease
Hit http://security.debian.org jessie/updates InRelease                
Hit http://ftp.debian.org jessie-updates InRelease                     
Hit http://ftp.debian.org jessie Release.gpg   
Hit http://ftp.debian.org jessie Release                                
Hit http://apt.osmc.tv jessie InRelease                                 
Hit http://security.debian.org jessie/updates/main armhf Packages       
Hit http://security.debian.org jessie/updates/contrib armhf Packages
Hit http://security.debian.org jessie/updates/non-free armhf Packages                    
Get:1 http://ftp.debian.org jessie-updates/main armhf Packages/DiffIndex [9,376 B]       
Hit http://security.debian.org jessie/updates/contrib Translation-en                                
Hit http://ftp.debian.org jessie-updates/contrib armhf Packages     
Hit http://security.debian.org jessie/updates/main Translation-en                         
Get:2 http://ftp.debian.org jessie-updates/non-free armhf Packages/DiffIndex [736 B]      
Hit http://security.debian.org jessie/updates/non-free Translation-en                             
Hit http://ftp.debian.org jessie-updates/contrib Translation-en                           
Get:3 http://ftp.debian.org jessie-updates/main Translation-en/DiffIndex [3,688 B]
Get:4 http://ftp.debian.org jessie-updates/non-free Translation-en/DiffIndex [736 B]
Hit http://ftp.debian.org jessie/main armhf Packages                                 
Hit http://ftp.debian.org jessie/contrib armhf Packages                
Hit http://ftp.debian.org jessie/non-free armhf Packages
Hit http://ftp.debian.org jessie/contrib Translation-en              
Hit http://ftp.debian.org jessie/main Translation-en                      
Hit http://ftp.debian.org jessie/non-free Translation-en                                        
Get:5 http://apt.osmc.tv jessie/main armhf Packages/DiffIndex [2,023 B]                         
Ign http://apt.osmc.tv jessie/main Translation-en_GB                                  
Ign http://apt.osmc.tv jessie/main Translation-en
Fetched 16.6 kB in 8s (1,988 B/s)                                                                                                                                    
Reading package lists... Done
E: Sub-process /usr/bin/dpkg returned an error code (1)

error is still present. further help appreciated!

Looks strange, reasons can be many (even a SD Card failure).
First upload new set of logs grab-logs -A
Second try
sudo apt-get clean
sudo apt-get update

New logs:

after reboot
https://paste.osmc.tv/onagivaqij

after running
apt-get clean
apt-get update
apt-get dist-upgrade

https://paste.osmc.tv/mixalayoso

Did the “update” still gave an error?

yes still get the error.

looking through the logs and a few forum searches, issue could be related to

libasound2-data 1.0.28-1+rpi2

The following occurs in the logs

Unpacking rbp2-device-osmc (1.4.0) over (1.3.3) ...
dpkg: error processing archive /var/cache/apt/archives/rbp2-device-osmc_1.4.0_armhf.deb (--unpack):
 trying to overwrite '/usr/share/alsa/cards/JustBoomDigi.conf', which is also in package libasound2-data 1.0.28-1+rpi2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

and

Log started: 2017-06-20  13:07:38
Preparing to unpack .../rbp2-device-osmc_1.4.0_armhf.deb ...
Unpacking rbp2-device-osmc (1.4.0) over (1.3.3) ...
dpkg: error processing archive /var/cache/apt/archives/rbp2-device-osmc_1.4.0_armhf.deb (--unpack):
 trying to overwrite '/usr/share/alsa/cards/JustBoomDigi.conf', which is also in package libasound2-data 1.0.28-1+rpi2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/rbp2-device-osmc_1.4.0_armhf.deb
Log ended: 2017-06-20  13:07:40

Log started: 2017-06-22  16:20:08
Preparing to unpack .../rbp2-device-osmc_1.4.0_armhf.deb ...
Unpacking rbp2-device-osmc (1.4.0) over (1.3.3) ...
dpkg: error processing archive /var/cache/apt/archives/rbp2-device-osmc_1.4.0_armhf.deb (--unpack):
 trying to overwrite '/usr/share/alsa/cards/JustBoomDigi.conf', which is also in package libasound2-data 1.0.28-1+rpi2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/rbp2-device-osmc_1.4.0_armhf.deb
Log ended: 2017-06-22  16:20:16

according to this:

using apt-get remove libasound2-data 1.0.28-1+rpi2

will delete the conflicting package. should I also use --purge to remove the associated configs? or am i barking up the wrong tree?

No looks like a possible culprit. So go ahead with that

osmc@osmc:~$ sudo apt-get remove libasound2-data 1.0.28-1+rpi2
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package 1.0.28-1+rpi2
E: Couldn't find any package by regex '1.0.28-1+rpi2'
osmc@osmc:~$ sudo apt-get remove libasound2-data
Reading package lists... Done
Building dependency tree       
Reading state information... Done
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:

The following packages have unmet dependencies:
 libsdl1.2-dev : Depends: libsdl1.2debian (= 1.2.15-12rpi) but it is not going to be installed
                 Depends: libasound2-dev but it is not going to be installed
 libsdl2-dev : Depends: libsdl2-2.0-0 (= 2.0.5+4rpi) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Much thanks for your help fzinken. as you can see it appears to have not worked… I’ll try a sudo apt-get dist-upgrade again now and see what happens…

I think you first need to remove all the dependencies around libasound

are there any ways to resolve exactly which packages are dependant?

I’ve tried :

osmc@osmc:~$ sudo apt-get --purge autoremove libasound2
Reading package lists... Done
Building dependency tree       
Reading state information... Done
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:

The following packages have unmet dependencies:
 libsdl1.2-dev : Depends: libsdl1.2debian (= 1.2.15-12rpi) but it is not going to be installed
                 Depends: libasound2-dev but it is not going to be installed
 libsdl2-dev : Depends: libsdl2-2.0-0 (= 2.0.5+4rpi) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
osmc@osmc:~$ sudo apt-get remove libsdl1.2debian
Reading package lists... Done
Building dependency tree       
Reading state information... Done
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:

The following packages have unmet dependencies:
 libsdl1.2-dev : Depends: libsdl1.2debian (= 1.2.15-12rpi) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
osmc@osmc:~$ aptitude purge libsound2
-bash: aptitude: command not found
osmc@osmc:~$ sudo apt-get purge libasound2
Reading package lists... Done
Building dependency tree       
Reading state information... Done
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:

The following packages have unmet dependencies:
 libsdl1.2-dev : Depends: libsdl1.2debian (= 1.2.15-12rpi) but it is not going to be installed
                 Depends: libasound2-dev but it is not going to be installed
 libsdl2-dev : Depends: libsdl2-2.0-0 (= 2.0.5+4rpi) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
osmc@osmc:~$ 

but as you can see no dice!

Try apt-cache rdepends --installed libasound2
But what concerns me is this

ran apt-get -f install to fix the broken dependancies, then update and dist-upgrade, has gotten further into the install than usual… will report back!

  osmc@osmc:~$ apt-cache rdepends --installed libasound2
    libasound2
    Reverse Depends:
        liboss4-salsa-asound2
        liboss4-salsa-asound2
        liboss4-salsa-asound2
        liboss4-salsa-asound2
        liboss4-salsa-asound2
        liboss4-salsa-asound2
        liboss4-salsa-asound2
        liboss4-salsa-asound2
        liboss4-salsa-asound2
        liboss4-salsa-asound2
    osmc@osmc:~$ sudo apt-get remove liboss4-salsa-asound2
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    Package 'liboss4-salsa-asound2' is not installed, so not removed
    You might want to run 'apt-get -f install' to correct these:
    The following packages have unmet dependencies:
     rbp2-device-osmc : Depends: rbp2-mediacenter-osmc but it is not going to be installed
    E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
    osmc@osmc:~$ apt-get -f install
    E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
    E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
    osmc@osmc:~$ sudo apt-get -f install
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    Correcting dependencies... Done
    The following packages were automatically installed and are no longer required:
    osmc@osmc:~$ reboot
    Connection to 192.168.0.3 closed by remote host.
    Connection to 192.168.0.3 closed.

@fzinken, out of curiosity, why is this concerning?

Well it concerns me as you might have set a “hold” on a certain package.
But let’s see where you get with the new success

Sorry, hit my post limit yesterday, but, it appears to have worked :smile:

osmc@osmc:~$ grep Kodi .kodi/temp/kodi.log | head -3
14:04:38.238 T:1958514688  NOTICE: Starting Kodi (17.5). Platform: Linux ARM (Thumb) 32-bit
14:04:38.238 T:1958514688  NOTICE: Using Release Kodi x32 build (version for Raspberry Pi)
14:04:38.238 T:1958514688  NOTICE: Kodi compiled Oct 29 2017 by GCC 4.9.2 for Linux ARM (Thumb) 32-bit version 3.16.39 (200743)
osmc@osmc:~$ 

It has borked my retro pie installation however, so now to figure out how to get that running again.

@fzinken thank you for your help! very much appreciated, and now I have a little more knowledge, and so am both more and less dangerous. Schrodinger’s hacker if you will. :joy:

1 Like