The VideoLAN Forums

Have configured VLC for manual updates only and wonder if this is the reason the program won't let me go online with the update function "Help, Check for Updates ...". I get the msg: "An error occurred while checking .. ". This happens with or w/o the firewall in place.

Here is what the VLC debug log has to say:

[00000522] logger interface: VLC media player - version 0.9.8a Grishenko - (c) 1
996-2008 the VideoLAN team
[00000522] logger interface:
Warning: if you can't access the GUI anymore, open a command-line window, go to
the directory where you installed VLC and run "vlc -I qt"

[00000522] logger interface: using logger...
[00000522] logger interface warning: no log filename provided, using `vlc-log.tx
t'
[00000522] logger interface debug: opening logfile `vlc-log.txt'
[00000522] main interface debug: using interface module "logger"
[00000522] main interface debug: thread 5932 (interface) created at priority 0 (
interface/interface.c:168)
[00000522] main interface debug: thread started

[00000524] main update check debug: thread 5948 (check for update) created at pr
iority 0 (misc/update.c:1391)
[00000524] main update check debug: thread started
[00000001] main libvlc debug: creating access 'http' path='update.videolan.org/v
lc/status-win-x86'
[00000525] main access debug: looking for access module: 2 candidates
[00000525] access_http access debug: http: server='update.videolan.org' port=80
file='/vlc/status-win-x86
[00000525] main access debug: net: connecting to update.videolan.org port 80
[00000525] main access debug: connection: Resource temporarily unavailable
[00000525] main access debug: connection succeeded (socket = 6000)
[00000525] access_http access debug: protocol 'HTTP' answer code 206
[00000525] access_http access debug: Content-Type: text/plain
[00000525] access_http access debug: stream size=148,pos=0,remaining=148
[00000525] access_http access debug: this frame size=148
[00000525] access_http access debug: Server: lighttpd/1.4.13
[00000525] main access debug: using access module "access_http"
[00000526] main stream debug: Using AStream*Stream
[00000526] main stream debug: pre-buffering...
[00000526] main stream debug: received first data for our buffer
[00000525] main access debug: removing module "access_http"
[00000525] main access debug: waitpipe: object killed
[00000001] main libvlc debug: creating access 'http' path='update.videolan.org/v
lc/status-win-x86.asc'
[00000527] main access debug: looking for access module: 2 candidates
[00000527] access_http access debug: http: server='update.videolan.org' port=80
file='/vlc/status-win-x86.asc
[00000527] main access debug: net: connecting to update.videolan.org port 80
[00000527] main access debug: connection: Resource temporarily unavailable
[00000527] main access debug: connection succeeded (socket = 5992)
[00000527] access_http access debug: protocol 'HTTP' answer code 206
[00000527] access_http access debug: Content-Type: text/plain
[00000527] access_http access debug: stream size=189,pos=0,remaining=189
[00000527] access_http access debug: this frame size=189
[00000527] access_http access debug: Server: lighttpd/1.4.13
[00000527] main access debug: using access module "access_http"
[00000528] main stream debug: Using AStream*Stream
[00000528] main stream debug: pre-buffering...
[00000528] main stream debug: received first data for our buffer
[00000001] main libvlc debug: Downloading signature (189 bytes)
[00000527] main access debug: removing module "access_http"
[00000527] main access debug: waitpipe: object killed
[00000001] main libvlc debug: Unarmoring signature
[00000001] main libvlc warning: Bad SHA1 hash for status file
[00000001] main libvlc warning: update check 524 destroyed while thread alive (V
LC might crash)

Thx for your input
MH

Known issue.

Will there be a fix? I am asking this because that problem is not specific to 0.9.8b. It also occurred in previous versions.

0.9.6 didn't have this issue, IIRC.

That may be. I started encountering this problem starting with 0.9.7 as far as I can remember.

There isn't official 0.9.7 release.

As I wrote, I can't tell for sure. But it is definitely a problem in 0.9.8a (which is, according to the download page, the latest official version).