Problem re-appeared with the latest update.
Thanks, we are aware of this issue. Can you please report the exact screen resolution you are running in using ‘tvservice -s’ and also paste your config.txt ? Thanks.
root@osmc:~# tvservice -s
state 0x12001a [HDMI CEA (4) RGB lim 16:9], 1280x720 @ 60.00Hz, progressive
config.txt
sdtv_mode=2
disable_overscan=1
hdmi_force_hotplug=1
hdmi_drive=2
hdmi_force_edid_audio=1
over_voltage=2
start_x=1
gpu_mem_512=256
sdtv_aspect=3
core_freq=500
hdmi_ignore_cec_init=1
over_voltage_sdram=0
initial_turbo=0
overscan_scale=1
hdmi_mode=4
dwc_otg.speed=1
force_turbo=0
sdram_freq=500
gpu_mem_256=128
hdmi_group=1
gpu_mem_1024=256
arm_freq=1000hmmm tried to get the new image and i am getting a read-only system error:
Cannot write to ‘armv7-splash-osmc_1.2.1_armhf.deb’ (Read-only file system)
wtf just happened?
both my root and osmc user says its a read-only file system. I cant make any folder or directory on the pi
Edit: well i did a reboot and the pi is on a crash loop before even getting into kodi.
Everything went to hell after the update 
should i just reinstall everything?
Edit2: Somehow checkdisk executed and fixed some stuff…no i can get back to kodi, but the welcome screen did not get fixed running
wget http://46.37.189.135/osmc/apt/pool/main/a/armv7-splash-osmc/armv7-splash-osmc_1.2.1_armhf.deb
sudo dpkg -i armv7-splash-osmc_1.2.1_armhf.deb
and god knows what else is broken by the update.
Here is my log files: http://paste.osmc.io/etibotozal
The update won’t have corrupted your file system or caused it to go read only - there will be an underlying hardware issue that is causing disk corruption, such as a marginal power supply or faulty SD card.
The reason why you would notice this during an upgrade is because a lot of critical files get overwritten during an upgrade, thus if any corruption of written files occurs it will cause you problems that will go unnoticed during normal operation.
If the partitions are read only you can try running fsck on them via SSH.
I’m not sure what you were hoping to achieve by reinstalling the splash package - as I said, we are aware of the issue with the splash image being corrupted (diagonal lines) on some screen resolutions in the current version of OSMC - we have not pushed out an update yet to fix this.
The hardware on this pi is all brand new. Hasnt even been 4 months since i got it. Power supply is efficient and the SD card was bought after reading tons of articles about its efficiency specifically for the pi. I’ve had a pi1 for years and only with osmc i’ve seen this read-only bug happening twice so far…and both times when the update was causing problems to some users.
Last time the splash img fixed the boot image problem, so i thought maybe getting the latest one would also fix it this time. 
Should i reformat the sd and put an earlier version of osmc or wait ?
Thanks
When I had the splash screen problem in May, it was solved by updating a splash package (see post #8).
It came back after 2015.07-1, and 2015.08-1 did not fix it.
I do not notice other issues besides the splash screen.
Stripes are back for me.
wget fix (post#8) gets a “not found” error
VERSION_ID=“2015.09-2”
resolution 1366x768
Are you sure you’re really in 1366x766 ? Please provide the output of:
tvservice -s
tvservice -m CEA
tvservice -m DMT
Also make sure you are fully up to date. There is a known problem with the splash screen at 720x576 (analog SD output) but it should be OK in 1366x766.
Here’s the output of those commands:
osmc@osmc:~$ tvservice -s
state 0x12000a [HDMI DMT (81) RGB full 16:9], 1366x768 @ 60.00Hz, progressive
osmc@osmc:~$ tvservice -m CEA
Group CEA has 15 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
mode 6: 720x480 @ 60Hz 4:3, clock:27MHz x2 interlaced
mode 7: 720x480 @ 60Hz 16:9, clock:27MHz x2 interlaced
(native) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive
mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced
mode 21: 720x576 @ 50Hz 4:3, clock:27MHz x2 interlaced
mode 22: 720x576 @ 50Hz 16:9, clock:27MHz x2 interlaced
mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive
osmc@osmc:~$ tvservice -m DMT
Group DMT has 6 modes:
mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive
mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive
mode 22: 1280x768 @ 60Hz 15:9, clock:68MHz progressive
(prefer) mode 81: 1366x768 @ 60Hz 16:9, clock:85MHz progressive
mode 85: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
And the version check:
osmc@osmc:~$ cat /proc/version
Linux version 4.2.1-1-osmc (root@vero) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP PREEMPT Wed Sep 23 17:57:49 UTC 2015
osmc@osmc:~$ cat /etc/os-release
PRETTY_NAME="Open Source Media Center"
NAME="OSMC"
VERSION="September 2015"
VERSION_ID="2015.09-2"
ID=osmc
ID_LIKE=debianstill same after december version