Just updating OSMC now - no keyboard and smb.conf message

[fatboyslim]

Is this a time I need to buy some generic USB keyboard?

On a plus side I did backup just before.

[ MacGyver tools available now: usb mouse, putty connecting to RPi ]

PS I have nothing to hit Enter - to confirm choice

[ActionA]

Updating Vero needs input I cannot give

This is a problem that was not caused by us, but by the Debian Samba package maintainers who out of the blue added a “high priority” question in their package configuration causing this prompt. We are just as annoyed about this as you I can assure you and I’ve spent a couple of hours tonight (before we had even seen any reports on the forum - I saw the problem occur on my own system first) working out a long term solution for this which has just been pushed out as an update. To work around it…

Click the above link for the workaround solution to this issue… Sorry for the inconvenience.

[fatboyslim]

Well no worries. More importantly thanks for showing me direction @ActionA

I’ll update when its ready.

[kriticar]

I have solved it by commenting include line in smb.conf file.

[DBMandrake]

Once you have updated you can restore that line as we have included a fix in the latest update that will prevent it happening again. Thanks for highlighting another possible workaround.

[kriticar]

That was exactly what I have done, but I forgot to write it in my previous post.

[fatboyslim]

update from command line stopped at 28%

commenting the line in smb.conf worked

thanks

sudo nano /etc/samba/smb.conf

[DBMandrake]

@fatboyslim

update from command line stopped at 28%

If you were updating from the command line via SSH you should have seen the same blue message which you would have been able to use cursor keys and Enter to answer to proceed.

[fatboyslim]

@DBMandrake

would have been able to use cursor keys and Enter to answer to proceed.

I did. It stopped like a minute later.

[ashtonaut]

Updating from 2015.12-1 to 2015.12-3 and I got the Samba message as well. Used the SSH and command line upgrade to workaround with no issues.

My concern is that I support several others running OSMC (with the Samba server installed) who won’t have the skills or knowledge to do any kind of SSH workaround and don’t have USB keyboards.

If one has installed the Samba server package, is some form of workaround going to be mandatory when upgrading? I realise that the latest update will prevent the problem in the future, my concern is preventing (if possible) it happening now, for this specific Samba case.

[DBMandrake]

If Samba is already installed there is no “easy” (non ssh) way to prevent it happening other than uninstalling Samba before upgrading then reinstalling it.

Unfortunate, but our hands really are tied due to the way debconf and apt work. We can’t update the updating script until after the message would have already appeared as debconf runs first before any packages are installed.

[ashtonaut]

OK, thanks for confirming. At least I am forewarned… It will probably be easiest to find and plug in a USB keyboard when they get this message, assuming that this will work.