VLC v 3.0.21 not starting

[Doug Clark]

I can run vlc 3.0.18 just fine, but I cannot run any version of VLC past 3.0.18

Some type of window flashes on the screen and then goes away.

I suspect that some new library, or change in a library, has happened since 3.0.18 but I cannot figure out what.

Anyone have any ideas?  Thanks in advance

[Dave Yeo]

The usual, check popuplog.os2 in the root of your boot volume, and download chkdll and use it to check for DLLs.
http://www.warpcave.com/betas/chkdll32-1.02-20210310.zip
Seems to me last time someone had a similar problem, it was libvpx, needed a legacy version IIRC.

[Doug Clark]

Thanks Dave,


popup log says


08-04-2024  16:33:18  SYS2070  PID 006c  TID 0001  Slot 00db
E:\PROGRAMS\VLC2\USR\LOCAL\BIN\VLC.EXE
A_MMS_PL->LIBCN0.2026
182
------------------------------------------------------------

08-04-2024  16:33:18  SYS2070  PID 006c  TID 0001  Slot 00db
E:\PROGRAMS\VLC2\USR\LOCAL\BIN\VLC.EXE
A_MMS_PL->LIBCN0.2026
182
------------------------------------------------------------

08-04-2024  16:33:19  SYS2070  PID 006e  TID 0001  Slot 00db
E:\PROGRAMS\VLC2\USR\LOCAL\BIN\VLC.EXE
A_MMS_PL->LIBCN0.2026
182
------------------------------------------------------------

08-04-2024  16:33:19  SYS2070  PID 006e  TID 0001  Slot 00db
E:\PROGRAMS\VLC2\USR\LOCAL\BIN\VLC.EXE
A_MMS_PL->LIBCN0.2026
182

==================================
and when I try to run YUM or AOS package manager I get the message
database disk image is malformed

so I can't check any libraries.

[Doug Clark]

Further info:

As for the YUM problem

I tried
yum clean all
yum clean metadata
yum clean dbcache
and
yum makecache

which returned
[Errno 2] No such file or directory: '/@unixroot/var/cache/yum/netlabs-rel/959a5
065a99df5b5b4d7e8672bbf1b90a4c9135f653d52968d19b4ae0dba9085-primary.sqlite.bz2'

[David Graser]

Hi Doug

What version of Arcaos are you using?

Are you installing over ver 3.0.18 or on a partition without  any VLC version?

[Doug Clark]

I am using AOS 5.1,

I have 3.0.18 installed in e:\programs\vlc3018
and 3.0.21 installed in e:\programs\vlc2

To start 3.0.18 I use the cmd file
set beginlibpath=e:\Programs\vlc3018\usr\local\lib;e:\usr\local\lib;e:\usr\lib;
vlc.exe

and to (not) start 3.0.21 the cmd file
set beginlibpath=e:\Programs\vlc2\usr\local\lib;e:\usr\local\lib;e:\usr\lib;
vlc.exe

I really don't need the e:\usr\local\lib;e:\usr\lib;
that is at the end of the BEINGLIBPATHs, but it is there to be redundant

[Dave Yeo]

Thanks Dave,


popup log says


08-04-2024  16:33:18  SYS2070  PID 006c  TID 0001  Slot 00db
E:\PROGRAMS\VLC2\USR\LOCAL\BIN\VLC.EXE
A_MMS_PL->LIBCN0.2026
182
------------------------------------------------------------

08-04-2024  16:33:18  SYS2070  PID 006c  TID 0001  Slot 00db
E:\PROGRAMS\VLC2\USR\LOCAL\BIN\VLC.EXE
A_MMS_PL->LIBCN0.2026
182
------------------------------------------------------------

08-04-2024  16:33:19  SYS2070  PID 006e  TID 0001  Slot 00db
E:\PROGRAMS\VLC2\USR\LOCAL\BIN\VLC.EXE
A_MMS_PL->LIBCN0.2026
182
------------------------------------------------------------

08-04-2024  16:33:19  SYS2070  PID 006e  TID 0001  Slot 00db
E:\PROGRAMS\VLC2\USR\LOCAL\BIN\VLC.EXE
A_MMS_PL->LIBCN0.2026
182

==================================
and when I try to run YUM or AOS package manager I get the message
database disk image is malformed

so I can't check any libraries.

OK, looks like you need a newer libc, or you have an old one on LIBPATH that is getting loaded.
Not sure what to do about malformed database, looks like you tried the obvious fixes.
You could do the nuclear option, that would mean reinstalling a bunch of RPM's.
Nuclear option. Go to @unixroot/usr/lib and run "unlock *.dll", move \usr, \var, and \etc out of the way, run ANPM, reboot when it asks you to. Install needed RPM's. Ask for advice if something like Python screws up. Create a backup.

[Andy Willis]

Weird, I too am getting the Error: database disk image is malformed

[Dave Yeo]

Weird, I too am getting the Error: database disk image is malformed

I just ran ANPM, downloaded a lot of data, and then gave me the same error. Luckily I have a backup.
I'd advise others not to run ANPM or YUM for now as it seems to be a problem upstream.