search for: kodis

On Fri, 2 Nov 2018 08:33:56 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, > > I think he also forgot to mention this part of kodi and smbclient. > > ( the default of kodi its smbclient ) > .smb/smb.conf > [global] > lock directory = /home/username/.kodi/.smb/ > name resolve order = bcast host >

On 11/1/18 11:22 AM, Rowland Penny via samba wrote: > It is for a standalone server without guest access, it also will not > allow network browsing because of the default 'server max protocol = > SMB3' > > I think you need to understand that network browsing is going away, you > need SMB1 for this. > > Anyway, it shouldn't crash, so can you get a level 10 from

Hai, smbclient -L $(hostname -s) on CLI, wworks witout problem on ubuntu 18.04, with the newly builded samba 4.9.1 package from repo and the kodi 18 Beta4. I also noticed that kodi 18 has some setting now in /home/kodi/.kodi/userdata/guisettings.xml <setting id="smb.legacysecurity" default="true">false</setting> <setting

On 11/3/18 11:10 AM, Rowland Penny via samba wrote: > I think it may be because Debian uses libgnutls28-dev, whilst Fedora > uses trousers It seems to be a Kodi CMake issue, but I would argue Samba or trousers need to change the name of "read_data" to something more unique if it is going to be an exported shared symbol. Kodi requires libmicrohttpd. The libmicrohttpd library

I have samba joined to domain an all ad users can access shares from windows clients . I created ad user for kodi and have Domain;username:password and shares are not accessible to kodi. What I am missing. check_ntlm_password: Checking password for unmapped user [WORKGROUP]\[firetv]@[LOCALHOST] with the new password interface [2016/10/12 06:55:40.254367, 3]

Hai, I think he also forgot to mention this part of kodi and smbclient. ( the default of kodi its smbclient ) .smb/smb.conf [global] lock directory = /home/username/.kodi/.smb/ name resolve order = bcast host include = /home/username/.kodi/.smb/user.conf I suggest, he needs to add the needed smbclient -mSMB1 into the user.conf of kodi. At least he should try it

On Sat, 3 Nov 2018 09:30:08 -0500 Michael Cronenworth via samba <samba at lists.samba.org> wrote: > On 11/2/18 4:29 PM, Michael Cronenworth via samba wrote: > > > > A compiler bug is also possible. When I have time I'll try to > > rebuild Samba with -O0 to make sure it isn't an optimization issue. > > When I built with -O0 the backtrace changed. >

On 11/2/18 5:43 AM, L.P.H. van Belle via samba wrote: > Its a headless server so in this case im unable to test from within kodi, atm. > But Michael count try to to adjust the maxprotocol from within kodi and see if that helps. Kodi is a GUI app. There is no "shell" or "exit to shell" feature. It calls library functions and does not call the "smbclient"

https://bugs.freedesktop.org/show_bug.cgi?id=98657 Bug ID: 98657 Summary: Reproducible freeze when changing volume amplification in kodi Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

On Fri, 2 Nov 2018 11:43:11 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, > > > smbclient -L $(hostname -s) on CLI, wworks witout problem on ubuntu > 18.04, with the newly builded samba 4.9.1 package from repo and the > kodi 18 Beta4. > > I also noticed that kodi 18 has some setting now > in

Hai Rowland,     Good catch.. ;-) (the ntlm settings)   But first this must be correct. [HEBE]\[firetv]@[LOCALHOST]                   ^^^^^^^^ The user that connect is called firetv? Not kodi?   And what i forgot also, kodi uses NMBD a lot, and Samba AD does not use MBD. So if you need to "Browse the netwerk" setup zeroconf/Avahi also or drop samba AD and use old style

Hai, Can you check the following, a few things that where bit buggy lately. Disable nmbd ( systemctl stop nmbd ) And Try again. And what is in /etc/nsswitch.conf And is SeLinux or Apparmor installed/enabled? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland Penny via samba > Verzonden: vrijdag 2

On 11/2/18 4:28 PM, Jeremy Allison wrote: > if you're getting the abort(), then urand_fd == -1. > If urand_fd != -1 and you're hitting the abort then > you have a compiler bug. A compiler bug is also possible. When I have time I'll try to rebuild Samba with -O0 to make sure it isn't an optimization issue.

Hi, I maintain Kodi[1] in RPMFusion[2] and the latest version of Kodi, 18.0, is crashing when trying to browse the SMB network. The previous version, 17.x, worked fine. The backtrace shows that Samba was not able to open /dev/urandom, which can't be true and must be masking another issue. The issue occurs on any Fedora 28 or 29 system (multiple user reports[3]). SELinux is disabled and

Hai, Ok, we have 2 last things to try. Change in : /etc/nsswitch.conf Only this line. hosts:      files dns myhostname mdns4_minimal [NOTFOUND=return] There are know problems with the search orders. A guess, but worth a try. Last, what if you run kodi as root? I did run it as a normal user. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces

On Sat, 3 Nov 2018 15:12:37 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Sat, 3 Nov 2018 09:30:08 -0500 > Michael Cronenworth via samba <samba at lists.samba.org> wrote: > > > On 11/2/18 4:29 PM, Michael Cronenworth via samba wrote: > > > > > > A compiler bug is also possible. When I have time I'll try to > > >

...;'m not sure how to go about this, or even what tools are most appropriate. Is this something that the Rails framework provides, or is it a job for Rake? for Rubygems? for Tar2rubyscript or Rubyscript2exe? A pointer to a "Distributing your Rails Application" would be ideal. -- John Kodis.

I am running one version before 4.4.5 on arch Linux it is join to my domain controller and it not functioning as dc. Do I need to configure host name for kodi ? I will setup setup zeroconf/Avahi

On Thu, Nov 01, 2018 at 09:40:32AM -0500, Michael Cronenworth via samba wrote: > Hi, > > I maintain Kodi[1] in RPMFusion[2] and the latest version of Kodi, 18.0, is > crashing when trying to browse the SMB network. The previous version, 17.x, > worked fine. > > The backtrace shows that Samba was not able to open /dev/urandom, which > can't be true and must be masking

On 11/2/18 4:29 PM, Michael Cronenworth via samba wrote: > > A compiler bug is also possible. When I have time I'll try to rebuild Samba with > -O0 to make sure it isn't an optimization issue. When I built with -O0 the backtrace changed. #0  0x00007ff699ec153f in raise () from /lib64/libc.so.6 #1  0x00007ff699eab895 in abort () from /lib64/libc.so.6 #2  0x00007ff696b19925 in