Bug 215537 - Just clic on modify default value on shares tab.
Summary: Just clic on modify default value on shares tab.
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_samba (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: triaged
: 206082 237820 245861 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-11-21 11:48 UTC by Sandra H. Bruel
Modified: 2018-10-27 03:47 UTC (History)
5 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 Sandra H. Bruel 2009-11-21 11:48:18 UTC
Application that crashed: kcmshell4
Version of the application: 
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
As said in the title a simple clic on "Modify default value" on the share tab cause Samba crash.


 -- Backtrace:
Application: Module de Configuration de KDE (kcmshell4), signal: Segmentation fault
[KCrash Handler]
#6  Q3GDict::hashKeyString (this=0x0, key=...) at tools/q3gdict.cpp:103
#7  0x01ae9276 in Q3GDict::look_string (this=0x0, key=..., d=0x0, op=0) at tools/q3gdict.cpp:337
#8  0x06e040e7 in Q3Dict<SambaShare>::find (this=0x9ca98c8, share=...) at /usr/include/qt4/Qt3Support/q3dict.h:79
#9  SambaFile::getShare (this=0x9ca98c8, share=...) at ../../../../filesharing/advanced/kcm_sambaconf/sambafile.cpp:299
#10 0x06dbaa82 in KcmSambaConf::editShareDefaults (this=0x9bd3230) at ../../../../filesharing/advanced/kcm_sambaconf/kcmsambaconf.cpp:500
#11 0x06dcabdb in KcmSambaConf::qt_metacall (this=0x9bd3230, _c=QMetaObject::InvokeMetaMethod, _id=38, _a=0xbfd60eb8) at ./kcmsambaconf.moc:93
#12 0x00cff263 in QMetaObject::activate (sender=0x9a45cb8, from_signal_index=29, to_signal_index=30, argv=0xbfd60eb8) at kernel/qobject.cpp:3113
#13 0x00cff6d8 in QMetaObject::activate (sender=0x9a45cb8, m=0x19480a4, from_local_signal_index=2, to_local_signal_index=3, argv=0xbfd60eb8) at kernel/qobject.cpp:3207
#14 0x01761cc1 in QAbstractButton::clicked (this=0x9a45cb8, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200
#15 0x0148a549 in QAbstractButtonPrivate::emitClicked (this=0x9a45cd0) at widgets/qabstractbutton.cpp:543
#16 0x0148c1a4 in QAbstractButtonPrivate::click (this=0x9a45cd0) at widgets/qabstractbutton.cpp:536
#17 0x0148c431 in QAbstractButton::mouseReleaseEvent (this=0x9a45cb8, e=0xbfd614b0) at widgets/qabstractbutton.cpp:1115
#18 0x0112a012 in QWidget::event (this=0x9a45cb8, event=0xbfd614b0) at kernel/qwidget.cpp:7549
#19 0x0148a3ee in QAbstractButton::event (this=0x9a45cb8, e=0xbfd60d2c) at widgets/qabstractbutton.cpp:1077
#20 0x0153466d in QPushButton::event (this=0x9a45cb8, e=0xbfd614b0) at widgets/qpushbutton.cpp:662
#21 0x010d4f54 in QApplicationPrivate::notify_helper (this=0x99601b0, receiver=0x9a45cb8, e=0xbfd614b0) at kernel/qapplication.cpp:4056
#22 0x010dd033 in QApplication::notify (this=0xbfd62eb4, receiver=0x9a45cb8, e=0xbfd614b0) at kernel/qapplication.cpp:3758
#23 0x009eabfa in KApplication::notify (this=0xbfd62eb4, receiver=0x9a45cb8, event=0xbfd614b0) at ../../kdeui/kernel/kapplication.cpp:302
#24 0x00ce96cb in QCoreApplication::notifyInternal (this=0xbfd62eb4, receiver=0x9a45cb8, event=0xbfd614b0) at kernel/qcoreapplication.cpp:610
#25 0x010dbf6e in QCoreApplication::sendSpontaneousEvent (receiver=0x9a45cb8, event=0xbfd614b0, alienWidget=0x9a45cb8, nativeWidget=0x9a6d780, buttonDown=0x194faa0, lastMouseReceiver=...)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#26 QApplicationPrivate::sendMouseEvent (receiver=0x9a45cb8, event=0xbfd614b0, alienWidget=0x9a45cb8, nativeWidget=0x9a6d780, buttonDown=0x194faa0, lastMouseReceiver=...)
    at kernel/qapplication.cpp:2924
#27 0x0114a7c0 in QETWidget::translateMouseEvent (this=0x9a6d780, event=0xbfd62afc) at kernel/qapplication_x11.cpp:4409
#28 0x01149c4b in QApplication::x11ProcessEvent (this=0xbfd62eb4, event=0xbfd62afc) at kernel/qapplication_x11.cpp:3428
#29 0x01176502 in x11EventSourceDispatch (s=0x9963400, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#30 0x01f88e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#31 0x01f8c720 in ?? () from /lib/libglib-2.0.so.0
#32 0x01f8c853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#33 0x00d1402c in QEventDispatcherGlib::processEvents (this=0x994aa30, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#34 0x01175be5 in QGuiEventDispatcherGlib::processEvents (this=0x994aa30, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#35 0x00ce7c79 in QEventLoop::processEvents (this=0xbfd62df0, flags=) at kernel/qeventloop.cpp:149
#36 0x00ce80ca in QEventLoop::exec (this=0xbfd62df0, flags=...) at kernel/qeventloop.cpp:201
#37 0x015c1d53 in QDialog::exec (this=0x9a6d780) at dialogs/qdialog.cpp:498
#38 0x00358f8e in kdemain (_argc=4, _argv=0xbfd63124) at ../../kcmshell/main.cpp:267
#39 0x0804865b in main (argc=4, argv=0xbfd63124) at kcmshell4_dummy.cpp:3

Reported using DrKonqi
Comment 1 Dario Andres 2009-11-21 14:32:49 UTC
This could be related to bug 206082. @Christoph: did your patches "fixed" this ?
Regards
Comment 2 Christoph Feck 2010-05-19 01:12:08 UTC
*** Bug 206082 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2010-05-19 01:12:19 UTC
*** Bug 237820 has been marked as a duplicate of this bug. ***
Comment 4 Nicolas L. 2010-08-14 16:05:45 UTC
*** Bug 245861 has been marked as a duplicate of this bug. ***
Comment 5 Christoph Feck 2013-09-12 21:42:54 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Comment 6 Andrew Crouthamel 2018-09-24 02:01:00 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-10-27 03:47:03 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!