Posts by kurai

Yes - the problem seems to be that at boot time the ExecStart=/usr/lib/samba/samba-config initiated from samba-config.service failes to create (or create in time ??) the /run/samba/smbpasswd that smbd is looking for during startsmbfilepwent_internal , so smbd recreates an empty smbpasswd file.

Executing /usr/lib/samba/samba-config later in an SSH session *does* create a proper /run/samba/smbpasswd

So, my question is ... how do I ensure that a populated smbpasswd file is created and|or created in time for smbd to find ?

I'm using LibreELEC-Generic.x86_64-12.0-nightly-20230522-794a8ad, and it's still an issue.

Seems entries in /run/samba/smbpasswd are not persisting after reboot.

I'm getting somewhat lost with the auto-assembly of the final samba config in /run/samba from various other files scattered around the install.

Between /storage/.config/samba.conf , /storage/.kodi/.smb/smb.conf , /storage/.cache/services/samba.conf (and any I've missed) where/what should I be doing so that the smbpasswd username/password entered via LibreELEC-Settings->Services is populated after next boot ?

Cheers,

--

kurai

It's back now - thank you Mysterious Masked Janitor for whatever it was you did.

This *does* normally work, but the server isn't offering up a download list at the moment.

It occasionally fills up it's diskspace and needs someone to check what it's done and tidy up, as and when they have time.

Never mind - booted from a some linux live OS USB stick and did it from console there.

Told you I was too tired - once I accepted that I had spent *waaaay* too long trying to futz around doing it with only LibreElec/Kodi things and dug out the bag of random USB stuff it took 2 minutes

Aaargh - after doing some work getting some new skin code to work on the LE Nightly, I used the restore function of the Backup plugin to quickly wipe/reset my changes.

Turns out the plugin doesn't (or can't ?) honour the permissions settings of /storage/.cache/ssh/

Now I can't get back into console as the SSHD bails after complaining the permissions are too open.

It's late, and my brain isn't working properly any more - is there *any* way or workaround to change the permissions via the UI/file-manager or local keyboard access ?

Or otherwise get a local console going, since there's a keyboard and mouse connected to the machine.

I'm on the Generic Nightly, & CTRL+ALT+F3 doesn't work, neither does the web-console from systemtools addon.

Any advice welcome as I'm clearly too tired to be thinking coherently

I have an N6005 device - pretty much the same thing but clocked a little higher and it works fine on Generic LE11 Kodi 20 (Nexus) - even HDR.

There were a lot of updates to the kernel for Jasper Lake series iGPU happening during the Kodi 19 (Matrix) development cycle.

Try the Generic-legacy version if you want to stay with LE10/Kodi19 (that worked fine from the start, only without HDR functionality)

Have you also added the mapping of the Harmony Clear button-send to the Kodi Delete function in .Kodi\userdata\keymaps\keymap.xml ?

In the Harmony software I have the Clear button set to send the Clear keypress and change it's function, once received, in the keymap instead.

e.g. snippets from my keymap.xml

...
  <MyFiles>
    <remote>
      <clear>Delete</clear>
      <zero>Highlight</zero>
      <star>Move</star>
      <hash>Rename</hash>
      <menu>ContextMenu</menu>
    </remote>
  </MyFiles>
...
  <MyMusicPlaylist>
    <remote>
      <clear>Delete</clear>
    </remote>
  </MyMusicPlaylist>
...
  <MyVideoLibrary>
    <remote>
      <zero>Queue</zero>
      <clear>Delete</clear>
      <menu>ContextMenu</menu>
     </remote>
  </MyVideoLibrary>
...
  <MyVideoPlaylist>
    <remote>
      <clear>Delete</clear>
      <zero>Delete</zero>
    </remote>
  </MyVideoPlaylist>
...
etc.

I'm using the Harmony Hub + RF remote + IR blaster to USB MCE receiver but the principle should be the same with Harmony 665 + Flirc IR receiver.

RSS 2.0 feed confirmed as working for me on Nightlies & Nexus 11 Beta 1 builds with the (now ancient) Kodi RSS ticker.

Nice one

Great news CvH

The ticker was usually the way I heard about significant updates/developments first, since I would often miss inbuilt updater notifications and I am otherwise not checking the site/forums all that often ... unless I encounter an issue or just randomly remember to check in, once in a while.

I am very much of the "if it Just Works[tm]" ... leave it alone until it doesn't ... mindset

There are downsides to this - I recently made a query in the Bug Report section about something and it turned out the root cause was me leaving in an old advancedsettings.xml entry that hasn't been relevant/useful for *at least* 3 hardware platform updates that I've gone through

Well ... that was quick, once I had my wrong-headed assumption challenged and re-calibrated my brain.

This was the culprit, in advancedsettings.xml

<gui>
   <algorithmdirtyregions>2</algorithmdirtyregions>
</gui>

That was a bit of left-over lint from at least 2 hardware upgrades back.

Thank you.

Aaaaah - looks like I had a brain-lock. I was making the assumption the windowing init was happening at a point before any addons were loaded, so they wouldn't be relevant at that stage of startup.

Turns out that's completely wrong as the clean/vanilla instance chewitt suggests does indeed work properly.

Looks like it's time for me to go on a cruft-hunt to find out what part of the years worth of accumulated tinkering has misbehaved

Hardware: Odroid H3+ (Intel N6005 Pentium Silver, 11th gen UHD iGPU - Jasper Lake)

Debug logs from non-working GBM LibreELEC-Generic.x86_64-11.0-nightly-20230117-5f4b4a4 :-

http://ix.io/4ltz

Debug logs from working X11 LibreELEC-Generic-legacy.x86_64-11.0-nightly-20230117-5f4b4a4 for comparison, if it helps:-

http://ix.io/4ltA

I've been using using nightlies since I got this new hardware in October as, at the time, the kernel in the mainline releases didn't support Intel Jasper Lake fully.

I've been updating the nightly version to latest every week or two since then - never been able to get the GBM versions to init.

As someone else has confirmed it *should* work, I'll go ahead and collect debug logs etc when I get home.

Hi all.

Before I waste everyone's time asking you to comb through debug logfiles & shell outputs, am I correct in thinking that the title hardware *should* work just fine with the standard Generic GBM nightly build ?

For some reason it always stops at the "critical <general>: CApplication::CreateGUI - unable to init windowing system" entry and I have to use the Generic-Legacy nightly builds with X11 instead, which is a pain since I want to try out HDR.

I've trawled through a great many of the existing posts and nearly all the potential pitfalls & issues have either already been fixed/integrated into later Nightly builds or don't apply to my specific hardware.

Am I just being dim, and not finding something already known and/or obvious that prevents GBM working with my shiny new Odroid H3+ ?

Resurrecting this old thread because I noticed it's still an issue while I was testing a Nightly build install.

To be clear - it's not an issue with the build itself - it's a problem with this website and how it has implemented it's RSS feed and/or a quirk of the way the Kodi RSSReader deals with it.

For whatever reason the inbuilt Kodi RSSReader ticker cannot parse this particular feed, even though it checks out fine on the W3C validator.

Feed Validator Results: https://libreelec.tv/feed.xml

I copied the XML to my local webserver and chopped out all the article entries, in case it was a parsing issue with one post, but even with just the barebones XML feed structure it still failed to parse it.

Feed display appears to be b0rked again.

It fetches and seems to look properly formatted in a web browser, but won't display in LE/Kodi RSS ticker.

(For both https://libreelec.tv/feed and https://libreelec.tv/feed.xml)

Other feeds work, and I've changed nothing related on my end, so it looks to be a libreelec.tv issue

DEBUG <general>: Thread RSSReader start, auto delete: false
DEBUG <general>: CurlFile::Open(0x7efdeb34e900) https://libreelec.tv/feed.xml
DEBUG <general>: easy_acquire - Created session to https://libreelec.tv
DEBUG <general>: Got rss feed: https://libreelec.tv/feed.xml
DEBUG <general>: RSS feed encoding: UTF-8
DEBUG <general>: Thread RSSReader 139629037942336 terminating

A successful feed has the following DEBUG entry after the encoding line:-

DEBUG <general>: Parsed rss feed: https://kodi.tv/rss.xml