Problems with videos/youtube [Solved]

[Eadwine Rose]

Who says you HAVE to upgrade?

If it ain't broken...


Making a snapshot or something similar will help, of course :)

[keos]

I mean I should apply in the terminal:

Code: Select all

sudo aptitude update and upgrade

-- this copy I just reinstalled of MX23 is I think a month old.

EDIT:

Talking about the subject and it appears to me ... (sorry, spanish)

Code: Select all

actualización completa
  Leyendo lista de paquetes...
  Creando árbol de dependencias...
  Leyendo la información de estado...
  Calculando la actualización...
  Se instalarán los siguientes paquetes NUEVOS:
     linux-headers-6.8.12-1-liquorix-amd64 (6.8-18~mx23ahs)
     linux-image-6.8.12-1-liquorix-amd64 (6.8-18~mx23ahs)
  Los siguientes paquetes se han retenido:
     mx-docs (20240410 => 20240411)
  Se actualizarán los siguientes paquetes:
     gir1.2-gst-plugins-base-1.0 (1.22.0-3+deb12u1 => 1.22.0-3+deb12u2)
     gstreamer1.0-alsa (1.22.0-3+deb12u1 => 1.22.0-3+deb12u2)
     gstreamer1.0-plugins-base (1.22.0-3+deb12u1 => 1.22.0-3+deb12u2)
     libgstreamer-gl1.0-0 (1.22.0-3+deb12u1 => 1.22.0-3+deb12u2)
     libgstreamer-plugins-base1.0-0 (1.22.0-3+deb12u1 => 1.22.0-3+deb12u2)
     libgstreamer-plugins-base1.0-0:i386 (1.22.0-3+deb12u1 => 1.22.0-3+deb12u2)
     linux-headers-liquorix-amd64 (6.8-14~mx23ahs => 6.8-18~mx23ahs)
     linux-image-liquorix-amd64 (6.8-14~mx23ahs => 6.8-18~mx23ahs)
     localize-repo-mx (24.03.01 => 24.05.01)
     mx-packageinstaller-pkglist (24.05.06mx23 => 24.06.02mx23)
     mx-repo-list (24.5.01 => 24.5.02)
     mx-snapshot (24.4.02 => 24.5)
  12 actualizados, 2 nuevos se instalarán, 0 para eliminar y 1 no actualizados.
  Se necesita descargar 132 MB de archivos.
  Se utilizarán 228 MB de espacio de disco adicional después de esta operación.
  

[j2mcgreg]

I got tired of the whole thing and reinstalled the system, it seemed to me that it was the fastest thing to do with ...

Now everything is perfectly fine, just like before, but... I have to upgrade! -- is there anything that I should take into account, before to update to avoid the same thing happening again?

Code: Select all

ken@ken:~
$ uname -a
Linux ken 6.8.9-5-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 6.8-14~mx23ahs (2024-05-17) x86_64 GNU/Linux
ken@ken:~
$ 

Actually, I think that you should downgrade a bit. The Liquorix 6.8.9 series has proven to be problematic for some folks. I think that the 6.6.12-1 would be a better fit. If you go this route, remember to use Boot Options in MX Tools to make it the new default.

[keos]

After update/upgrade it is workin fine, i will take note of your advice.

but in case ... what do you means by:

If you go this route, remember to use Boot Options in MX Tools to make it the new default.

Thanks.


EDIT:

After reboot-shutdown-power-on, the system change the kernel to:

Code: Select all

ken@ken:~
$ uname -r
6.8.12-1-liquorix-amd64
ken@ken:~
$ 

but it still working fine; very weird the whole thing.

[siamhie]

After reboot-shutdown-power-on, the system change the kernel to:

Code: Select all

ken@ken:~
$ uname -r
6.8.12-1-liquorix-amd64
ken@ken:~
$ 

but it still working fine; very weird the whole thing.

Nothing weird. You updated the kernel in post #22.

Code: Select all

linux-headers-liquorix-amd64 (6.8-14~mx23ahs => 6.8-18~mx23ahs)
linux-image-liquorix-amd64 (6.8-14~mx23ahs => 6.8-18~mx23ahs)

[keos]

I did not explain myself well, I meant that it is strange that after the change of kernel for the current one, it still works correctly

-- I do not understand what happened, I reinstall the system and everything was solved, but what happened ...?

[Eadwine Rose]

My guess is that you stuffed something up between that last copy you made the install from and now.

[keos]

Nothing. I don't install new things anymore, I don't make new configurations with the browsers, I now just do the updates that come with the system (?)

[j2mcgreg]

Nothing. I don't install new things anymore, I don't make new configurations with the browsers, I now just do the updates that come with the system (?)

In that case, you my have gotten a poorly transmitted or somehow corrupted update that messed up your system. Since you reside in the USA, as a precaution against this happening in future, you might use Repo Manager in MX Tools to switch your main repository to the one in Salt Lake City which is owned and operated by the MX team.

[CharlesV]

There is also the shear fact that not everything can always be saved perfectly. There are times when bits can get messed up because of cache, saving at the wrong time, and then 'just didnt save correctly'.

Any of these can cause big issues if they are in a config or a data file that is relied upon for your system to run properly.

This IS one of the best reasons I know of to have a method to recover your system. A good backup strategy will recover from most anything that causes a problems.