[RESOLVED]vlc updates today

[GuiGuy]

Code: Select all

sudo apt full-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libaribb24-0 libbasicusageenvironment1 libdvbpsi10 libebml4v5 libgroupsock8 liblivemedia57
  libmatroska6v5 libmicrodns0 libopenmpt-modplug1 libplacebo4 libprotobuf-lite10
  libresid-builder0c2a libsdl-image1.2 libsidplay2 libspatialaudio0 libupnp6 libusageenvironment3
  libva-wayland2 libvlc-bin libvlc5 libvlccore9 libxcb-xv0 vlc-l10n vlc-plugin-base vlc-plugin-qt
  vlc-plugin-video-output
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  vlc vlc-bin
The following packages have been kept back:
  vlc-data vlc-plugin-qt
The following packages will be upgraded:
  libvlc-bin libvlc5 libvlccore9 vlc-l10n
4 upgraded, 0 newly installed, 2 to remove and 2 not upgraded.
Need to get 6,673 kB of archives.
After this operation, 603 kB disk space will be freed.
Do you want to continue? [Y/n] [code/]

[m_pav]

Re previous post.. lots of signature issues there..

Only for Virtualbox though, won't affect security updates

[asqwerth]

I'm confused.

You said you did not accept the vlc updates in the first post.

If that is the case, how come the command

sudo apt full-upgrade

does not surface them again as outstanding updates?

[m_pav]

Follow my earlier suggestion before you do anything else

[m_pav]

For further assistance, you could post your most recent log files from /var/log/ so we can examine them.
/var/log/dpkg.log
/var/log/dkpg.log.1

[GuiGuy]

It looks like the MX version of VLC is installed, but something is broken with it, potentially a supporting library or an incomplete upgrade. Synaptic should throw up a notification when you start it about having held broken packages. To get a better look, in Synaptic on the lower left column there are 6 clickable buttons, click the Status button and the list in the panel above will show 6 entries. If there are any broken packages in your system, you'll see 7 entries, one will have the word broken. Click on broken to see what package has been affected.

To attempt to fix broken packages, close Synaptic and try running the following from a terminal.

Code: Select all

sudo dkpg -f install 

This type of issue is mostly caused by using later version unstable or external sources for upgraded apps which work for the intended purpose, but can potentially cause library mismatches in the dpkg database, leading to failed updates for our standard apps.

VlC starts without error and synaptic shows no broken passages.

[GuiGuy]

For further assistance, you could post your most recent log files from /var/log/ so we can examine them.
/var/log/dpkg.log
/var/log/dkpg.log.1

Here are the last few entries:-

2019-08-21 08:50:58 status half-configured opencpn-plugin-celestial-dbgsym:amd64 2.3.0-0~1mx17+2
2019-08-21 08:50:58 status installed opencpn-plugin-celestial-dbgsym:amd64 2.3.0-0~1mx17+2
2019-08-21 08:50:58 configure opencpn-plugin-projections-dbgsym:amd64 0.1.0-0mx17+2 <none>
2019-08-21 08:50:58 status unpacked opencpn-plugin-projections-dbgsym:amd64 0.1.0-0mx17+2
2019-08-21 08:50:58 status half-configured opencpn-plugin-projections-dbgsym:amd64 0.1.0-0mx17+2
2019-08-21 08:50:58 status installed opencpn-plugin-projections-dbgsym:amd64 0.1.0-0mx17+2
2019-08-21 08:50:58 configure opencpn-plugin-pypilot-dbgsym:amd64 0.5.0-0mx17+2 <none>
2019-08-21 08:50:58 status unpacked opencpn-plugin-pypilot-dbgsym:amd64 0.5.0-0mx17+2
2019-08-21 08:50:59 status half-configured opencpn-plugin-pypilot-dbgsym:amd64 0.5.0-0mx17+2
2019-08-21 08:50:59 status installed opencpn-plugin-pypilot-dbgsym:amd64 0.5.0-0mx17+2
2019-08-21 08:50:59 configure opencpn-plugin-squiddio-dbgsym:amd64 0.7.1-0mx17+2 <none>
2019-08-21 08:50:59 status unpacked opencpn-plugin-squiddio-dbgsym:amd64 0.7.1-0mx17+2
2019-08-21 08:50:59 status half-configured opencpn-plugin-squiddio-dbgsym:amd64 0.7.1-0mx17+2
2019-08-21 08:50:59 status installed opencpn-plugin-squiddio-dbgsym:amd64 0.7.1-0mx17+2
2019-08-21 08:51:00 configure opencpn-plugin-dr-dbgsym:amd64 0.1.0-0mx17+2 <none>
2019-08-21 08:51:00 status unpacked opencpn-plugin-dr-dbgsym:amd64 0.1.0-0mx17+2
2019-08-21 08:51:00 status half-configured opencpn-plugin-dr-dbgsym:amd64 0.1.0-0mx17+2
2019-08-21 08:51:00 status installed opencpn-plugin-dr-dbgsym:amd64

[quote/]

[m_pav]

Page 2, response # 20, have you done it yet?

[m_pav]

It's after midnight and I have a big day tomorrow, so sorry to abandon you right now, I'm off to bed.

[Stevo]

Either the VLC 3.0.8 we have in the test repo or the Debian 3.0.8, which came a little later, do upgrade fine over the MX version 3.0.7 we have in our main repo. Make sure you have a good repo--the one in NZ and Australia might be a bit flaky.

Quite often, these issues are a result of a package that the user installed from deb-multimedia. This command will show any packages that have the string "dmo". Libdvdcss2 could be installed from our codec installer and is known not to interfere, as are dtx texture packages. Ignore the packages that have the "dmo" in the package name like "libvidmode".

Code: Select all

dpkg-query -W | grep 'dmo'

If nothing shows up here, we'll have to fix your system from the command line with aptitude.
First, try

Code: Select all

aptitude why-not vlc

and see if it can show the culprit, because you do have one somewhere.