openmediavault 0.4.19

Hi any change list of 0.4.13 ?

The following update is not working for me. I have 64bit version of .4 with all the latest updates.
I set the Session timeout to 0 yet it keeps timing out.

•Setting session timeout to 0 in the ‘System | General Settings | Web Administration’ page sets the session timeout to unlimited.

I am using Internet Explorer 10 on Windows 8. I will try a different browser.
Would the log for authentication be helpful?

Do I understand this feature correctly?

If I login I should stay logged indefinitely without having to re-login if I set session timeout to zero

Newer versions of IE have given me many problems with sites over the years. I'd recommend Google Chrome.

Same result with Chrome. Hum....

Specifically I am timing out from the General settings page. So far for all my tests I have just left the browser on this page.
Times out at 30 minutes.

Are you using a Desktop or Laptop when you set it. Did you try using 0 from the 10 key or the alternate setup for numbers on a laptop. It may be keymap issue. I just tested on mine and it works.

I am using a desktop. I am not sure which 0 I used. I just tried leaving the browser on the Mail Notification page and it didn't timeout.
Which zero did you use?

I used the 0 from my Galaxy Tab so it will not be the same. Make sure numbers lock is on and use the 0 on the 10 key and see if that works.

That seems to have worked even for IE.

To me that's still a bug but at least we have pinpointed the problem.

Glad it's fixed. The bug may lie in driver for your keyboard. Who knows but as long as you got a fix is all that matters....

Yes, It's good to have a work-around.
I have a very standard Microsoft keyboard. So, I don't imagine that I will be the only one with this problem.

PS: I use a number (not Zero) in my login password from the regular number keys and it works fine.

Did my usual; check on Update Manager and ticked for install for all the items (4 SAMBA and 1 for OMV itself), it gets the OMV aupdate but I'm getting the following errors for the others...

Reading package lists...
Building dependency tree...
Reading state information...
Suggested packages:
  openbsd-inetd inet-superserver smbldap-tools ldb-tools ctdb
The following packages will be upgraded:
  libwbclient0 samba samba-common samba-common-bin
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.2 MB of archives.
After this operation, 111 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  libwbclient0 samba samba-common samba-common-bin
Authentication warning overridden.
Err http://security.debian.org/ squeeze/updates/main libwbclient0 amd64 2:3.5.6~dfsg-3squeeze9
  404  Not Found [IP: 128.101.240.212 80]
Err http://security.debian.org/ squeeze/updates/main samba amd64 2:3.5.6~dfsg-3squeeze9
  404  Not Found [IP: 128.101.240.212 80]
Err http://security.debian.org/ squeeze/updates/main samba-common all 2:3.5.6~dfsg-3squeeze9
  404  Not Found [IP: 128.101.240.212 80]
Err http://security.debian.org/ squeeze/updates/main samba-common-bin amd64 2:3.5.6~dfsg-3squeeze9
  404  Not Found [IP: 128.101.240.212 80]
Failed to fetch http://security.debian.org/pool/updates/main/s/samba/libwbclient0_3.5.6~dfsg-3squeeze9_amd64.deb  404  Not Found [IP: 128.101.240.212 80]
Failed to fetch http://security.debian.org/pool/updates/main/s/samba/samba_3.5.6~dfsg-3squeeze9_amd64.deb  404  Not Found [IP: 128.101.240.212 80]
Failed to fetch http://security.debian.org/pool/updates/main/s/samba/samba-common_3.5.6~dfsg-3squeeze9_all.deb  404  Not Found [IP: 128.101.240.212 80]
Failed to fetch http://security.debian.org/pool/updates/main/s/samba/samba-common-bin_3.5.6~dfsg-3squeeze9_amd64.deb  404  Not Found [IP: 128.101.240.212 80]
Done ...

Do I wait and check tomorrow or is it something more?

Drama over, obviously something wrong with one of the mirrors, just gone through now

Love, Mr Impatient xxx

False positive, IE just timed out again.

Hap, your prob is not big deal. For some reason, maybe maintenance, your omv cannot reach a repo.
Do an:
apt-get update

tell me how many failed to fetch errors, just 1 it looks like, you see at end of this command running.