[systemsettings] [Bug 304034] setting update time automatically and then hitting okay twice causes crash

thing1138 at mailingaddress.org thing1138 at mailingaddress.org
Mon Feb 18 18:14:03 GMT 2013


https://bugs.kde.org/show_bug.cgi?id=304034

--- Comment #2 from thing1138 at mailingaddress.org ---
Created attachment 77408
  --> https://bugs.kde.org/attachment.cgi?id=77408&action=edit
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

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list