Bug 99376 - Control Center -> Internet & Network -> Samba -> Crash
Summary: Control Center -> Internet & Network -> Samba -> Crash
Status: RESOLVED FIXED
Alias: None
Product: kcontrol
Classification: Miscellaneous
Component: kcmsamba (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Jan Schaefer
URL:
Keywords:
: 105202 129905 132324 132867 180392 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-02-14 16:53 UTC by Kim-Einar Larsen
Modified: 2009-04-14 23:04 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kim-Einar Larsen 2005-02-14 16:53:28 UTC
Version:            (using KDE KDE 3.3.1)
Installed from:    RedHat RPMs
Compiler:          2.6.10-1.760_FC3 
OS:                Linux

Hi! I've installed FC3 with only KDE(not gnome), and running kernel 2.6.10-1.760_FC3.
And have resently tryed to get Samba to work, I've changed some settings and now I can't configure Samba from the Control Center. What I really did want to do is it get my linux to be able to access some files on a windows network(large network, about 200 pc's).
When I'm starting Control Center and clicks other items in the list they work as they should, but when I click on "Samba Configuration" the Control Center crashes...

The Samba daemon, still works (I think), It loads & Unload normally when it should.

There was no problem yesterday with "Samba Configuration", before I started to edit some files. (smb.conf and some others)

And lastly I really want to know how a normal Samba configuration to access a standard windows network(winXP) should be, and does it exist any program that helps me to do that?

Thanks!  


Here is the backtraces:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208080704 (LWP 5928)]
[KCrash handler]
#4  0x028112af in QGDict::hashKeyString ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#5  0x02812645 in QGDict::look_string ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#6  0x00664635 in SambaShare::getValue ()
   from /usr/lib/kde3/libkcm_kcmsambaconf.so
#7  0x00664560 in SambaShare::getGlobalValue ()
   from /usr/lib/kde3/libkcm_kcmsambaconf.so
#8  0x00665271 in SambaShare::setValue ()
   from /usr/lib/kde3/libkcm_kcmsambaconf.so
#9  0x0065e119 in SambaFile::openFile ()
   from /usr/lib/kde3/libkcm_kcmsambaconf.so
#10 0x0065e401 in SambaFile::load () from /usr/lib/kde3/libkcm_kcmsambaconf.so
#11 0x00608321 in KcmSambaConf::load ()
   from /usr/lib/kde3/libkcm_kcmsambaconf.so
#12 0x006083e4 in KcmSambaConf::slotSpecifySmbConf ()
   from /usr/lib/kde3/libkcm_kcmsambaconf.so
#13 0x0060e481 in KcmSambaConf::KcmSambaConf ()
   from /usr/lib/kde3/libkcm_kcmsambaconf.so
#14 0x0060e527 in create_KcmSambaConf ()
   from /usr/lib/kde3/libkcm_kcmsambaconf.so
#15 0x002c7221 in KCModuleLoader::load () from /usr/lib/libkutils.so.1
#16 0x002c75bb in KCModuleLoader::loadModule () from /usr/lib/libkutils.so.1
#17 0x0018401e in ConfigModule::module () from /usr/lib/libkdeinit_kcontrol.so
#18 0x00178006 in ModuleWidget::load () from /usr/lib/libkdeinit_kcontrol.so
#19 0x001786b2 in DockContainer::loadModule ()
   from /usr/lib/libkdeinit_kcontrol.so
#20 0x00178bb9 in DockContainer::dockModule ()
   from /usr/lib/libkdeinit_kcontrol.so
#21 0x092d8220 in ?? ()
#22 0x00000034 in ?? ()
#23 0x092fae60 in ?? ()
#24 0x00000001 in ?? ()
#25 0x0018b400 in ?? () from /usr/lib/libkdeinit_kcontrol.so
#26 0x0000002e in ?? ()
#27 0x0938c198 in ?? ()
#28 0x09361ed8 in ?? ()
#29 0x09367b68 in ?? ()
#30 0x092d8220 in ?? ()
#31 0x0018bc74 in ?? () from /usr/lib/libkdeinit_kcontrol.so
#32 0x029b1fd0 in vtable for QGArray () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#33 0x00000000 in ?? ()
Comment 1 Jan Schaefer 2005-11-11 22:43:19 UTC
Could you post the contents of your smb.conf file?
Comment 2 Tommi Tervo 2006-06-27 18:37:00 UTC
*** Bug 129905 has been marked as a duplicate of this bug. ***
Comment 3 Tommi Tervo 2006-06-27 18:37:18 UTC
*** Bug 105202 has been marked as a duplicate of this bug. ***
Comment 4 Tommi Tervo 2006-08-23 15:03:48 UTC
*** Bug 132867 has been marked as a duplicate of this bug. ***
Comment 5 Tommi Tervo 2007-01-31 15:42:33 UTC
*** Bug 132867 has been marked as a duplicate of this bug. ***
Comment 6 Tommi Tervo 2007-02-02 10:23:29 UTC
*** Bug 132324 has been marked as a duplicate of this bug. ***
Comment 7 Jan Schaefer 2008-05-10 16:37:22 UTC
Without a sample smb.conf file to reproduce this bug, I cannot confirm whether this bug is still valid or not. I close it now. If it should reappear in KDE 4.1 or later, please reopen it and give the corresponding smb.conf file, which causes the crash.
Comment 8 Vladimir Ionescu 2008-11-10 21:19:10 UTC
I can confirm this bug in Gentoo with Konqueror 3.5.9. Furthermore, the bug seems to occur when smb.conf misses the global section. For example with smb.conf like this the bug occurs:

[Media]
comment = Media
path = /home/vlad/media
browseable = yes
read only = yes
guest ok = yes

Adding a global section causes the problem to go away:

[global]

workgroup = HOME
server string = Samba Server %v
log file = /var/log/samba/log.%m
max log size = 50

[Media]
comment = Media
path = /home/vlad/media
browseable = yes
read only = yes
guest ok = yes
Comment 9 Jan Schaefer 2008-11-10 22:26:15 UTC
Ok. Thank you for this hint with the missing global section. I then reopen the bug.
Comment 10 Jan Schaefer 2009-04-04 15:43:45 UTC
SVN commit 949087 by schafer:

Fixed bug that causes a crash if the GLOBAL section is missing in the smb.conf file
BUG: 99376


 M  +6 -2      sambashare.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=949087
Comment 11 Jan Schaefer 2009-04-04 15:45:05 UTC
SVN commit 949088 by schafer:

Fixed bug that causes a crash if the GLOBAL section is missing in the smb.conf file
BUG: 99376


 M  +6 -2      sambashare.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=949088
Comment 12 Jan Schaefer 2009-04-14 23:04:53 UTC
*** Bug 180392 has been marked as a duplicate of this bug. ***