20/06/2016 about 15:00
here are your how to help questions and my answers:
During (June) update I got a message: </b>
An error occurred while updating the following package
armv7-eventlirc-osmc
<please report this to the OSMC forum.>
restarting in 30sec
But the Vero2 had hung. It didn't respond to its remote control.
It did not respond to an ssh login via putty (timeout)
I have not enabled debug logging at this point: nevertheless the 10th
instance of lirc in the logs may be useful.
http://paste.osmc.io/ipabehixel
debug log when I tried to update again, http://paste.osmc.io/axuqetikag
(dependency problems)
What you were doing when this issue occurred
I responded yes to an invitation to perform an update on vero2, then
switched the TV to display HDMI 1 (a sony pvr) to watch recorded motor sport.
the PVR shut down cleanly, but unexpectedly after a couple of minutes. On request,
It powered up fine and continued. After a few minutes watching,
I switched to HDMI2 (= vero2 connection)
The error message above was waiting for me.
Whether you can replicate this issue on demand. If you can, then please
provide some steps on how an OSMC developer can reproduce the same
issue.
I have not tried yet.
p.s. retrying the update with debugging on gives similar error messages in the log, but
did not prompt me onscreen to report. see below. 20/06/2016 from 17:00
The message implied I should report this issue at once.
While researching how to report I discover that I may have to turn logging on and
reproduce the fault. That will be in a later post.
The device you are currently running
OSMC on Vero 2 about 1 month since purchase.
What peripherals are attached to the device?
HP 16Gb USB stick
Vero remote, with dongle on the side.
I read the dongle should be at the back, so I tried repositioning
it there, but it would not respond. I reverted to usb at the side.
It works, but sometimes need debouncing.
Has this issue been introduced by a new version of OSMC?
yes
When did the issue first appear
about 15:00 20/06/2015
and can you recall a time when it was not present?
Yes, Earlier
Vero2 with OSMC was restarted by re-plugging. While power off I moved
the remote control dongle to the rear port & unplugged the USB stick.
restart. Remote control working in rear port
copy logs to SDcard (none visible with card in PC)
upload logs seems to have worked.
restart, enabled debug logging.
requested settings backup (presumably to usb stick)
request restart
Message:
a stop job is running on HPstick (time1, time2)
about 10 mins later,
“target shutdown reached.”
~17:30 no restart
18:09 power cycled
backed up settings
my Osmc / updates/ manual /backup settings
- my Osmc / updates/ manual / update now
no onscreen error messages
18:31 try logs to SD card again
18:32 logs uploaded http://paste.osmc.io/axuqetikag
new log shows similar error to before:
…
Preparing to unpack …/armv7-eventlircd-osmc_1.2.0_armhf.deb …
Unpacking armv7-eventlircd-osmc (1.2.0) over (1.1.9) …
Setting up armv7-eventlircd-osmc (1.2.0) …
dpkg: error processing package armv7-eventlircd-osmc (–configure):
armv7-remote-osmc depends on armv7-eventlircd-osmc; however:
Package armv7-eventlircd-osmc is not configured yet.
armv7-eventlircd-osmc
Upgrade: vero2-kernel-osmc:armhf (2.6.8, 2.8.0), …,
armv7-eventlircd-osmc:armhf (1.1.9, …
jay