Hello!
I'm trying to get samba working and have added smb4k(browsing) app as with our other linux distros under a Windows 2003 Server domain. I have Toorox spec'd as a static IP with hostname and domain set in hosts smb.conf thru an editor, as I could not get the Network and Systems Settings GUI screens to enable. Related, we can see the Network Settings screen, but it is disabled/gray'd out and is missing the NIC card info and Domain Name System tab' Host name even though it's specified in smb.conf.

-ref active smb.conf Global section: (same as other linux box except they have winbind)
[global]
workgroup = i]Win03 domain name[/i
security = user
netbios name = toorox
hosts allow = 192.168.1. 127.
unix charset = ISO8859-1
; valid chars = [ ... ] # (errors if used)
keepalive = 30
os level = 2
kernel oplocks = no
domain master = no
socket options = SO_KEEPALIVE TCP_NODELAY IPTOS_LOWDELAY
username map = /etc/samba/smbusers
map to guest = Bad User
wins support = no
time server = yes
encrypt passwords = false
log level = 1
syslog = 0
restrict anonymous = no
preferred master = no
; max protocol = NT # (errors if used)
ldap ssl = No
server signing = Auto

Notes: We have no WINS, only have DNS. Yes, we have completely exited and restarted smb4k after changes to smb.conf

Please advise on disabled Network Settings screens within System Configuration GUI. i.e.: Is it broke? Also, what is the "valid chars" parameter for?

Thanks.
Al

Hello,

first click on Systemconfig -> Filesharing to start samba.
There you can manage your shares (add folders).
You can see your windows shares by starting dolphin (filemanager)
and then click on network -> Samba Shares.

Greetings

Does this answer any of my questions? -Doesn't appear to here.

To my knowledge, this function does not work correctly till now. Maybe with the release of KDE 4.4 and knetworkmanager?Execute:It's outdated and you can disable it.Remove the space

Joern

Okay, we do now also have Toorox_01.2010_32-Bit installed, however...

Attempting command yields CRASH!
i.e. Command: kdesu kcmshell4 kcm_knetworkconfmodule (ENTER)
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
KCrash: Application 'kcmshell4' crashing...
sock_file=/root/.kde4/socket-toorox/kdeinit4__0
Warning: connect() failed: : Connection refused
KCrash cannot reach kdeinit, launching directly.

warning: Can not parse XML syscalls information; XML support was disabled
at compile time.
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
QStringList Solid::Backends::Hal::HalManager:
:findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&)
error: "org.freedesktop.DBus.Error.AccessDenied"

Then, the "KDE Crash Handler" presents...
"We are sorry. KDE Control Module closed unexpectedly.
You cnan help us improve KDE by reporting theis error.
Note: It is safe to close this dialog if you do not want to report this bug.
Details:
Executable: kcmshell4 PID: 1382 Signal: 11 (Segmentation fault)"

Attempting to report the bug steails:
"Application: KDE Control Module (kcmshell4), signal: Segmentation fault
#0 0xffffe430 in __kernel_vsyscall ()
#1 0xb6f03d0b in waitpid () from /lib/libpthread.so.0
#2 0xb76a1f0b in ?? () from /usr/lib/libkdeui.so.5
#3 0x00000578 in ?? ()
#4 0x00000000 in ?? ()"

However, when trying to report the bug it also crashes. (Duh!) i.e.:
"warning: Can not parse XML syscalls information; XML support was disabled at compile time.
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
<unknown program name>(6440)/ ClientApp::doIt: Creating ClientApp
kioclient(6440): Session bus not found"

Can't even save this to file...
"QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.AccessDenied"

kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so" (repeated five times)

Also, trying to read instructions on how to report bugs, error...
"Could not start process Cannot talk to klauncher: Not connected to D-Bus server."


I think we need to set aside Toorox until perhaps yet another major release is provided... :(

Okay, we do now also have Toorox_01.2010_32-Bit installed, however...

Attempting command yields CRASH!
i.e. Command: kdesu kcmshell4 kcm_knetworkconfmodule (ENTER)
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
KCrash: Application 'kcmshell4' crashing...
sock_file=/root/.kde4/socket-toorox/kdeinit4__0
Warning: connect() failed: : Connection refused
KCrash cannot reach kdeinit, launching directly.

warning: Can not parse XML syscalls information; XML support was disabled
at compile time.
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
QStringList Solid::Backends::Hal::HalManager:
:findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&)
error: "org.freedesktop.DBus.Error.AccessDenied"

Then, the "KDE Crash Handler" presents...
"We are sorry. KDE Control Module closed unexpectedly.
You cnan help us improve KDE by reporting theis error.
Note: It is safe to close this dialog if you do not want to report this bug.
Details:
Executable: kcmshell4 PID: 1382 Signal: 11 (Segmentation fault)"

Attempting to report the bug steails:
"Application: KDE Control Module (kcmshell4), signal: Segmentation fault
#0 0xffffe430 in __kernel_vsyscall ()
#1 0xb6f03d0b in waitpid () from /lib/libpthread.so.0
#2 0xb76a1f0b in ?? () from /usr/lib/libkdeui.so.5
#3 0x00000578 in ?? ()
#4 0x00000000 in ?? ()"

However, when trying to report the bug it also crashes. (Duh!) i.e.:
"warning: Can not parse XML syscalls information; XML support was disabled at compile time.
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
<unknown program name>(6440)/ ClientApp::doIt: Creating ClientApp
kioclient(6440): Session bus not found"

Can't even save this to file...
"QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.AccessDenied"

kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so" (repeated five times)

Also, trying to read instructions on how to report bugs, error...
"Could not start process Cannot talk to klauncher: Not connected to D-Bus server."


I think we need to set aside Toorox until perhaps yet another major release is provided... :(

When you start it as user:without any problem?
And what about:

kcmshell4 kcm_knetworkconfmodule
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!

sudo kcmshell4 kcm_knetworkconfmodule
No protocol specified
Kcmshell4: cannot connect to X server :0.0

That's all.
Al

That's strange ...

Please insert and boot the live DVD and execute the same commands from a terminal of KDE.
Same result?

kcmshell4 kcm_knetworkconfmodule
This opened the “Network Settings – KDE Control Module” window, however there is no network interface listed and everything was gray’d out/disabled. i.e.: No apparent way to create a network interface record… Also, all tabs are disabled…

sudo kcmshell4 kcm_knetworkconfmodule
I received a lot of errors like,
“Error: “/var/tmp/kdecache-user” is owned by uid 1000 instead of uid 0”
(More than a dozen of these type errors.)
Then the “Network Settings – KDE Control Module” window, however, although the 2nd-4th tabs were enabled (usable), the 1st tab “Network Interfaces” was still blank and gray’d out/disabled (unusable) with no NIC listed.

Afterward, I then altered smb.conf (as initially posted above) to 'force' it onto my W2003 domain, as the network and Samba screens were not usable.
Then I ran "kcmshell4 kcm_knetworkconfmodule" again to find it crashes with error text:
"kdeinit4: preparing to launch /UNIONFS/usr/lib/libkdeinit4_klauncher.so
kdeinit4: Communication error with launcher. Exiting!
KCrash: Application 'kcmshell4' crashing...
sock_file=/root/.kde4/socket-Toorox/kdeinit4__0
Warning: connect() failed: : Communication refused
KCrash cannot reach kdeinit, launching directly."

RE: This IS the DVD running -not the hard drive.
So, it appears as this (DVD) may be having a permissions problem... (?) and maybe among other issues.

Is this the only one, which doesn't work correctly in your Toorox installation?
If yes, then don't worry about it - you can configure your NICs via LAN+WLAN
or execute:

Yes, well I tried /etc/init.d/NetworkManager start -w/ a capital "M", then kdesu nm-applet...
Error message presented: "** (nm-applet:12168): WARNING **: <WARN> request_name(): Could not acquire the NetworkManagerUserSettings service as it is already taken. Return: 3"
RE: The Network and Samba screens are core screens, and are only the ones we've reported -when will these disabled screens be fixed?
We can't be doing this anymore. At this point, I believe we need to wait for another major release of Toorox -after you have thoroughly tested it...
Thanks.
Bye.
Al