Don’t set up console-common, it will cause problems. Also don’t run apt-get upgrade in the future.
I suspect you will need to reinstall.
Also don’t use aptitude unless you really know how to administer a Debian system. You have effectively introduced some packages which will delineate you from OSMC’s upgrade path. We can’t provide support for this.
Actually, it probably does. The use of apt-get upgrade has not been recommended by Debian since the turn of the decade.
OSMC needs to maintain compatibility and an update system for many systems and users. We cannot guarantee updates will work if modifications are made, although such changes are usually harmless. Installing aptitude is unfortunately not supported.
We don’t have the resources to verify every permutation of system modification. However we can, and do support users upgrading via the official upgrade path.
We maintain an update path for a lot of users. If you are comfortable enough to install things like ‘console-common’ which has been remarked as a ‘black box’ by Debian developers and is scheduled for deprecation in Stretch+1, you should probably know what you are doing and be prepared to investigate and work this out. I recommended this in the past, but it was assuming that you would be willing to investigate issues around it. There’s a reason this isn’t in standard OSMC yet.
Nope, but you’ll get an older version of Node that may not be appropriate for your use case. You can use the official Node repos for a more up to date version.
Neither do your logs. There is more than meets the eye here. Your posts suggest that OSMC is incorrectly handling USB and Bluetooth keyboards, but this is not the case for a large number of users. Your issue lies in your changes to the OSMC system. If you make modifications without telling us that you made them; explaining why you made them or in detail what you did, there’s not much we can do to help. I want to support as much customisation as possible, but some things are currently not possible. I’d be more interested in improving things incrementally.
There is substantial evidence you have not managed your system properly. Your current comments are not particularly constructive. When you can administer one system properly, as recommended by Debian, I will happily listen to your suggestions on how to administer hundreds of thousands of devices.
No. And you cannot run this on Debian or Ubuntu either, because it upgrades packages without capturing new dependencies. The proper command is dist-upgrade. apt-get dist-upgrade is fine; aptitude dist-upgrade is fine.
This isn’t your fault, but many tutorials and examples follow 2009 era instructions when apt-get did not track dependencies as well as it does today. But it is your fault for not reading the Wiki which explains this under the Updating OSMC article.
The issue is has come up before and in the next release of OSMC, we will feature a warning when apt-get is invoked with upgrade. It leads to problems.
Nor will you need it. The upgrade is set to run in non-interactive mode to ensure that people aren’t left requiring to input when they may not be able to do so (no keyboard attached). My suggestion is that if you want upgrades to work reliably, you do so via My OSMC. You won’t have a problem with this upgrade method, and it’s supported.
I do not think you have read the Wiki article on troubleshooting.
I think I used the letters ‘F’ and ‘U’ across those sentences, yes.
Now that your reading has improved, check out Wiki - OSMC.
Your problem is rooted in knowing enough to cause invasive system changes, but not really understanding what these changes do, and not reading resources provided to you on how to properly manage your system.
Time that could have been spent improving the OSMC experience for everyone. I’m not normally harsh on newcomers, as there’s always a learning curve. However, when people denounce OSMC as unstable; stubbornly refuse to read resources provided to them and then take personal offense when told to do so, I’ll remind them that time can be better spent.