Bug 189248 - Crash when exiting with unsaved changes
Summary: Crash when exiting with unsaved changes
Status: RESOLVED DUPLICATE of bug 178885
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-10 00:35 UTC by Vitor M. Pereira
Modified: 2009-04-10 03:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vitor M. Pereira 2009-04-10 00:35:17 UTC
Version:           4.2.1 (using KDE 4.2.1)
OS:                Linux
Installed from:    Fedora RPMs

When leaving systemsettings without saving the changes the application crashes with SIGSEGV. This seems to occur only for some modules, but when it occurs it is reproducible. For example:

1. In systemsettings go to Appearance -> Style
2. Change something without applying the changes
3. Close systemsettings using the window close button
4. Discard the changes in the next dialog.
5. Application crashes on exit

The same happens for "icons", "splashscreen", etc. (but not for "colors", for example).

Below is the backtrace for the steps provided above.

------------------------------------------------------------------------

Application: System Settings (systemsettings), signal SIGSEGV
[Current thread is 1 (Thread 0xb7f75770 (LWP 10489))]

Thread 1 (Thread 0xb7f75770 (LWP 10489)):
[KCrash Handler]
#6  0x058aad3a in QProgressBar::minimum () from /usr/lib/libQtGui.so.4
#7  0x04fc88cf in QObject::event () from /usr/lib/libQtCore.so.4
#8  0x054c768c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#9  0x054cf4ce in QApplication::notify () from /usr/lib/libQtGui.so.4
#10 0x046900fd in KApplication::notify () from /usr/lib/libkdeui.so.5
#11 0x04fb91c1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#12 0x04fe7081 in ?? () from /usr/lib/libQtCore.so.4
#13 0x04fe38a0 in ?? () from /usr/lib/libQtCore.so.4
#14 0x009f5238 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#15 0x009f88e3 in ?? () from /lib/libglib-2.0.so.0
#16 0x009f8aa1 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#17 0x04fe37f8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#18 0x05560515 in ?? () from /usr/lib/libQtGui.so.4
#19 0x04fb788a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#20 0x04fb7a4a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#21 0x04fba105 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#22 0x054c7507 in QApplication::exec () from /usr/lib/libQtGui.so.4
#23 0x08055f1b in _start ()
Comment 1 Dario Andres 2009-04-10 03:17:45 UTC
This is a Qt bug fixed on 4.5.0 final. Thanks for reporting

*** This bug has been marked as a duplicate of bug 178885 ***