Bug 304034 - setting update time automatically and then hitting okay twice causes crash
Summary: setting update time automatically and then hitting okay twice causes crash
Status: RESOLVED DUPLICATE of bug 242648
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-25 04:19 UTC by illumilore
Modified: 2013-05-26 22:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (9.76 KB, text/plain)
2013-02-18 18:14 UTC, thing1138
Details
New crash information added by DrKonqi (4.95 KB, text/plain)
2013-05-26 22:57 UTC, ali.sherif10
Details

Note You need to log in before you can comment on or make changes to this bug.
Description illumilore 2012-07-25 04:19:51 UTC
Application: kcmshell4 ()
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.1
Operating System: Linux 3.5.0-030500rc6-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed: when setting the update time to automatic in adjust date and time window, and then hitting okay twice right after that, a crash occurs.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Control Module (kcmshell4), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f78639ee780 (LWP 4696))]

Thread 3 (Thread 0x7f7846e01700 (LWP 4697)):
#0  0x00007f78632dd0bd in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f784c3874bc in ?? () from /usr/lib/nvidia-current/libGL.so.1
#2  0x00007f784b5beb27 in ?? () from /usr/lib/nvidia-current/tls/libnvidia-tls.so.302.17
#3  0x00007f785deb28cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f785de77ba4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f785de77fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f785de7849a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007f78470ea406 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#8  0x00007f785de999e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007f784c3884d4 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#10 0x00007f785eb96e9a in start_thread (arg=0x7f7846e01700) at pthread_create.c:308
#11 0x00007f78632ea4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f7845528700 (LWP 4698)):
#0  0x00007f78632deb03 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f785de78036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f785de78164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f7861ed0426 in QEventDispatcherGlib::processEvents (this=0x7f78340008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f7861e9fc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f7861e9fed7 in QEventLoop::exec (this=0x7f7845527d10, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f7861d9efa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f7861e7f9ff in QInotifyFileSystemWatcherEngine::run (this=0x1b19710) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f7861da1fcb in QThreadPrivate::start (arg=0x1b19710) at thread/qthread_unix.cpp:298
#9  0x00007f784c3884d4 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#10 0x00007f785eb96e9a in start_thread (arg=0x7f7845528700) at pthread_create.c:308
#11 0x00007f78632ea4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f78639ee780 (LWP 4696)):
[KCrash Handler]
#6  0x000000000206dd70 in ?? ()
#7  0x00007f7861eb6bf2 in QObject::connect (sender=0x1b08300, signal=<optimized out>, receiver=0x1eca750, method=0x7f78523da3f1 "load()", type=Qt::AutoConnection) at kernel/qobject.cpp:2588
#8  0x00007f7861ebe95a in QSingleShotTimer::QSingleShotTimer (this=0x1b08300, msec=5000, receiver=0x1eca750, member=0x7f78523da3f0 "1load()") at kernel/qtimer.cpp:300
#9  0x00007f7861ebeb0e in QTimer::singleShot (msec=5000, receiver=0x1eca750, member=0x7f78523da3f0 "1load()") at kernel/qtimer.cpp:363
#10 0x00007f78523d8840 in KclockModule::save (this=0x1eca750) at ../../../kcontrol/dateandtime/main.cpp:109
#11 0x00007f7862fd8997 in KCModuleProxy::save (this=<optimized out>) at ../../kutils/kcmoduleproxy.cpp:279
#12 0x00007f7862fd5890 in KCMultiDialogPrivate::apply (this=<optimized out>) at ../../kutils/kcmultidialog.cpp:300
#13 0x00007f7862fd59f7 in KCMultiDialog::slotOkClicked (this=0x1c9a1b0) at ../../kutils/kcmultidialog.cpp:334
#14 0x00007f7861eb5281 in QMetaObject::activate (sender=0x1c847d0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff7ecee160) at kernel/qobject.cpp:3547
#15 0x00007f7862c5288f in KPushButton::authorized (this=<optimized out>, _t1=0x1f892b0) at ./kpushbutton.moc:143
#16 0x00007f7861eb5281 in QMetaObject::activate (sender=0x1c847d0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff7ecee2b0) at kernel/qobject.cpp:3547
#17 0x00007f78618b3c72 in QAbstractButton::clicked (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:220
#18 0x00007f78615f1a4e in QAbstractButtonPrivate::emitClicked (this=<optimized out>) at widgets/qabstractbutton.cpp:548
#19 0x00007f78615f2d8b in QAbstractButtonPrivate::click (this=0x1caefe0) at widgets/qabstractbutton.cpp:541
#20 0x00007f78615f2ffc in QAbstractButton::mouseReleaseEvent (this=0x1c847d0, e=0x7fff7eceeb80) at widgets/qabstractbutton.cpp:1123
#21 0x00007f7861274144 in QWidget::event (this=0x1c847d0, event=0x7fff7eceeb80) at kernel/qwidget.cpp:8362
#22 0x00007f7861223894 in notify_helper (e=0x7fff7eceeb80, receiver=0x1c847d0, this=0x1a85530) at kernel/qapplication.cpp:4559
#23 QApplicationPrivate::notify_helper (this=0x1a85530, receiver=0x1c847d0, e=0x7fff7eceeb80) at kernel/qapplication.cpp:4531
#24 0x00007f78612290bf in QApplication::notify (this=<optimized out>, receiver=0x1c847d0, e=0x7fff7eceeb80) at kernel/qapplication.cpp:4102
#25 0x00007f7862b849e6 in KApplication::notify (this=0x7fff7ecef8a0, receiver=0x1c847d0, event=0x7fff7eceeb80) at ../../kdeui/kernel/kapplication.cpp:311
#26 0x00007f7861ea0e9c in QCoreApplication::notifyInternal (this=0x7fff7ecef8a0, receiver=0x1c847d0, event=0x7fff7eceeb80) at kernel/qcoreapplication.cpp:876
#27 0x00007f7861224862 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#28 QApplicationPrivate::sendMouseEvent (receiver=0x1c847d0, event=0x7fff7eceeb80, alienWidget=0x1c847d0, nativeWidget=0x1c9a1b0, buttonDown=0x1c847d0, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3170
#29 0x00007f78612a3bf5 in QETWidget::translateMouseEvent (this=0x1c9a1b0, event=<optimized out>) at kernel/qapplication_x11.cpp:4617
#30 0x00007f78612a2bae in QApplication::x11ProcessEvent (this=0x7fff7ecef8a0, event=0x7fff7ecef450) at kernel/qapplication_x11.cpp:3732
#31 0x00007f78612cc0d2 in x11EventSourceDispatch (s=0x1a8a400, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#32 0x00007f785de77d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x00007f785de780a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x00007f785de78164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x00007f7861ed03bf in QEventDispatcherGlib::processEvents (this=0x1a62770, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#36 0x00007f78612cbd5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#37 0x00007f7861e9fc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#38 0x00007f7861e9fed7 in QEventLoop::exec (this=0x7fff7ecef7f0, flags=...) at kernel/qeventloop.cpp:204
#39 0x00007f78616f3936 in QDialog::exec (this=0x1c9a1b0) at dialogs/qdialog.cpp:554
#40 0x00007f78635ddd2c in kdemain (_argc=<optimized out>, _argv=<optimized out>) at ../../kcmshell/main.cpp:292
#41 0x00007f786321976d in __libc_start_main (main=0x400640 <main(int, char**)>, argc=2, ubp_av=0x7fff7ecf00b8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff7ecf00a8) at libc-start.c:226
#42 0x0000000000400671 in _start ()

Possible duplicates by query: bug 303978, bug 302428, bug 301875, bug 301806, bug 301731.

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-07-25 05:39:34 UTC

*** This bug has been marked as a duplicate of bug 242648 ***
Comment 2 thing1138 2013-02-18 18:14:03 UTC
Created attachment 77408 [details]
New crash information added by DrKonqi

systemsettings (1.0) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1

- What I was doing when the application crashed:
Steps to repeat error:
1.) Open [System Settings] from the "kickoff application launcher".
2.) In the 5th section down tittled "System Administration" Open [Date & Time]
3.) Just below the "Date and Time" tab is a check box titled "Set date and time automatically", make sure this box has a check mark in it. If this box already has a checkmark then click on it twice to remove and reapply the check mark so the "apply" button in the lower right hand side of the window is enabled.
4.) Click the "Apply" button in the lower right hand side of the window.

Results from Step 4: All items in the window become greyed out for a moment and unclickable, then all items return to there normal color and are now enabled or clickable again.

5.) From here there are two options one that leads to a crash and one that does not.

option-01_(non-crash).1) Click on "Overview" in the upper left hand corner.
option-01_(non-crash).2) An "Apply Settings - System Settings" dialog appears with the button options of "Apply" "Discard" and "Cancel". Click on "Apply".  The system is updated as it should and everything seems fine.

option-02_(crash).1) If you are not currently at step 5, then repeat steps 1 through 5 and instead of doing option-02_(crash).2), now do this: Click "Apply" in the lower right hand corner.

Results from option-02_(crash).2: Everything except the "Apply" button is greyed out for a moment then comes back as normal. 

option-02_(crash).3) Notice that if you click the "Apply" button the "Apply" buttin itself is not greyed out and the user can still click on it while everything else is still updating. This is the step where reproducing the bug becomes possible. To reproduce the bug at this step simply click the "Apply" button, and while everything else is still greyed out click the "Apply" button again, then follow the rest of the steps in quick succession which is what I think other people have been doing.

Results from option-02_(crash).3: An error message appears tittled "Error - System Settings" with the message "Unable to authenticate/execute the action: 6," with an "OK" button. Quickly select the "OK" button then either try to reapply the "Apply" button in the lower right hand corner, or go back to the overview page by quickly selecting "Overview" in the upper left hand corner followed by "Apply" in the window that appears and the Settings Manager will crash.

In other words, users are impatient and if something is available to click on the user interprets this as a notice that what they did didn't work, so they click on it again. To avoid this, I suggest not only greying out the "Apply" and "Overview" buttons, but also display a short message saying something like "please be patient, the settings are being updated" in order to avoid future bug report floods.

-- Backtrace (Reduced):
#7  0x00007f808fa2ebf2 in QObject::connect (sender=0x16d9770, signal=<optimized out>, receiver=0x1140180, method=0x7f807afe53f1 "load()", type=Qt::AutoConnection) at kernel/qobject.cpp:2588
#8  0x00007f808fa3695a in QSingleShotTimer::QSingleShotTimer (this=0x16d9770, msec=5000, receiver=0x1140180, member=0x7f807afe53f0 "1load()") at kernel/qtimer.cpp:300
#9  0x00007f808fa36b0e in QTimer::singleShot (msec=5000, receiver=0x1140180, member=0x7f807afe53f0 "1load()") at kernel/qtimer.cpp:363
#10 0x00007f807afe3840 in KclockModule::save (this=0x1140180) at ../../../kcontrol/dateandtime/main.cpp:109
#11 0x00007f8091a33997 in KCModuleProxy::save (this=<optimized out>) at ../../kutils/kcmoduleproxy.cpp:279
Comment 3 ali.sherif10 2013-05-26 22:57:14 UTC
Created attachment 80098 [details]
New crash information added by DrKonqi

systemsettings (1.0) on KDE Platform 4.10.2 "release 1" using Qt 4.8.4

- What I was doing when the application crashed:

I clicked on the Set date and time automatically checkbox then I clicked Apply. After I had entered root password, I clicked on the Overview button then I was asked to enter root password again. After I had entered it, I saw this message: "Unable to authenticate/excute the action: 6,". After I had clicked OK, the application crashed.

-- Backtrace (Reduced):
#5  0x00007fcb24f3a231 in QObject::connect (sender=0x1698490, signal=0x7fcb24ffc644 "timeout()", receiver=0xef82a0, method=0x7fcb0df46744 "load()", type=Qt::AutoConnection) at kernel/qobject.cpp:2596
#6  0x00007fcb24f3df6a in QSingleShotTimer::QSingleShotTimer (this=0x1698490, msec=5000, receiver=0xef82a0, member=0x7fcb0df46743 "1load()") at kernel/qtimer.cpp:300
#7  0x00007fcb24f3e116 in QTimer::singleShot (msec=5000, receiver=0xef82a0, member=0x7fcb0df46743 "1load()") at kernel/qtimer.cpp:363
[...]
#9  0x00007fcb26f13b27 in KCModuleProxy::save() () from /usr/lib64/libkcmutils.so.4
#10 0x00007fcb26cea133 in ModuleView::moduleSave(KCModuleProxy*) () from /usr/lib64/libsystemsettingsview.so.2