Bug 305061 - Crash during configuring displays in systemsettings
Summary: Crash during configuring displays in systemsettings
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kamera (show other bugs)
Version: 1.0
Platform: Ubuntu Linux
: HI crash
Target Milestone: ---
Assignee: Marcus Meissner
URL:
Keywords:
: 318310 325652 329188 338201 359779 394328 398209 410790 411468 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-08-13 06:25 UTC by Oleg Atamanenko
Modified: 2022-10-25 05:01 UTC (History)
12 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (5.79 KB, text/plain)
2014-07-01 18:44 UTC, T2
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oleg Atamanenko 2012-08-13 06:25:14 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.9.00
Qt Version: 4.8.1
Operating System: Linux 3.2.0-29-generic-pae i686
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:

I tried to configure window behaviour. 

The systemsettings crashed.

Additional info: I have dual monitor setup with NVIDIA driver.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Sistemaj agordoj (systemsettings), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xaffcc740 (LWP 14459))]

Thread 3 (Thread 0xa9a25b40 (LWP 14499)):
#0  0xb76eb424 in __kernel_vsyscall ()
#1  0xb5c98380 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb2f8fa7b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb2f820ae in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb2f8256b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xab6861ba in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0xb2fa56b3 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb2476a11 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#8  0x5c8b0824 in ?? ()
#9  0xbab80424 in ?? ()
#10 0x65000000 in ?? ()
#11 0x001015ff in ?? ()
#12 0xd3890000 in ?? ()
#13 0xfff0013d in ?? ()
#14 0xc30173ff in ?? ()
#15 0x0f8122e8 in ?? ()
#16 0x9fc18100 in ?? ()
#17 0x8b001724 in ?? ()
#18 0xffff0889 in ?? ()
#19 0x29d231ff in ?? ()
#20 0x0d0365c2 in ?? ()
#21 0x00000000 in ?? ()

Thread 2 (Thread 0xa32ffb40 (LWP 14511)):
#0  0xb2d5cdcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1  0xb5f0c315 in do_gettime (frac=0xa32fef00, sec=0xa32feef8) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0xb5ff6226 in QTimerInfoList::updateCurrentTime (this=0xa2901a7c) at kernel/qeventdispatcher_unix.cpp:343
#4  0xb5ff657a in QTimerInfoList::timerWait (this=0xa2901a7c, tm=...) at kernel/qeventdispatcher_unix.cpp:450
#5  0xb5ff4e23 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xa32ff00c) at kernel/qeventdispatcher_glib.cpp:136
#6  0xb5ff4ebd in timerSourcePrepare (source=0xa2901a48, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0xb2f81872 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb2f81faf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb2f82201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb5ff58e7 in QEventDispatcherGlib::processEvents (this=0xa2900480, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#11 0xb5fc150d in QEventLoop::processEvents (this=0xa32ff190, flags=...) at kernel/qeventloop.cpp:149
#12 0xb5fc17a9 in QEventLoop::exec (this=0xa32ff190, flags=...) at kernel/qeventloop.cpp:204
#13 0xb5eaa94c in QThread::exec (this=0x9485498) at thread/qthread.cpp:501
#14 0xb5f9eb5d in QInotifyFileSystemWatcherEngine::run (this=0x9485498) at io/qfilesystemwatcher_inotify.cpp:248
#15 0xb5eadde0 in QThreadPrivate::start (arg=0x9485498) at thread/qthread_unix.cpp:298
#16 0xb2476a11 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#17 0x5c8b0824 in ?? ()
#18 0xbab80424 in ?? ()
#19 0x65000000 in ?? ()
#20 0x001015ff in ?? ()
#21 0xd3890000 in ?? ()
#22 0xfff0013d in ?? ()
#23 0xc30173ff in ?? ()
#24 0x0f8122e8 in ?? ()
#25 0x9fc18100 in ?? ()
#26 0x8b001724 in ?? ()
#27 0xffff0889 in ?? ()
#28 0x29d231ff in ?? ()
#29 0x0d0365c2 in ?? ()
#30 0x00000000 in ?? ()

Thread 1 (Thread 0xaffcc740 (LWP 14459)):
[KCrash Handler]
#7  0xb6c04c66 in data (this=0x4) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
#8  qGetPtrHelper<QScopedPointer<QObjectData> > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2430
#9  d_func (this=0x0) at itemviews/qstandarditemmodel.h:425
#10 QStandardItemModel::clear (this=0x0) at itemviews/qstandarditemmodel.cpp:2088
#11 0xab783e24 in KKameraConfig::populateDeviceListView (this=0x8dce318) at ../../kcontrol/kamera.cpp:178
#12 0xab78585f in KKameraConfig::load (this=0x8dce318) at ../../kcontrol/kamera.cpp:264
#13 0xb71e03a3 in qt_static_metacall (_a=0x9283b00, _id=3, _o=0x8dce318, _c=<optimized out>) at ./kcmodule.moc:66
#14 KCModule::qt_static_metacall (_o=0x8dce318, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x9283b00) at ./kcmodule.moc:57
#15 0xb5fd4c01 in QMetaCallEvent::placeMetaCall (this=0x9442398, object=0x8dce318) at kernel/qobject.cpp:525
#16 0xb5fddc7b in QObject::event (this=0x8dce318, e=0x9442398) at kernel/qobject.cpp:1195
#17 0xb6609e62 in QWidget::event (this=0x8dce318, event=0x9442398) at kernel/qwidget.cpp:8821
#18 0xb65afed4 in notify_helper (e=0x9442398, receiver=0x8dce318, this=0x8853be8) at kernel/qapplication.cpp:4559
#19 QApplicationPrivate::notify_helper (this=0x8853be8, receiver=0x8dce318, e=0x9442398) at kernel/qapplication.cpp:4531
#20 0xb65b53a2 in QApplication::notify (this=0x8853be8, receiver=0x8dce318, e=0x9442398) at kernel/qapplication.cpp:4524
#21 0xb7134e41 in KApplication::notify (this=0xbfe1441c, receiver=0x8dce318, event=0x9442398) at ../../kdeui/kernel/kapplication.cpp:311
#22 0xb5fc297e in QCoreApplication::notifyInternal (this=0xbfe1441c, receiver=0x8dce318, event=0x9442398) at kernel/qcoreapplication.cpp:876
#23 0xb5fc6ad8 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x87c3130) at kernel/qcoreapplication.cpp:1500
#25 0xb5fc6e0c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1393
#26 0xb5ff5494 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#27 postEventSourceDispatch (s=0x87c4628) at kernel/qeventdispatcher_glib.cpp:279
#28 0xb2f81d86 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#29 0xb2f82125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#30 0xb2f82201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#31 0xb5ff5887 in QEventDispatcherGlib::processEvents (this=0x8853648, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#32 0xb6668aaa in QGuiEventDispatcherGlib::processEvents (this=0x8853648, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0xb5fc150d in QEventLoop::processEvents (this=0xbfe14374, flags=...) at kernel/qeventloop.cpp:149
#34 0xb5fc17a9 in QEventLoop::exec (this=0xbfe14374, flags=...) at kernel/qeventloop.cpp:204
#35 0xb5fc6eba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#36 0xb65ada74 in QApplication::exec () at kernel/qapplication.cpp:3820
#37 0x08050438 in main (argc=<error reading variable: Cannot access memory at address 0x220c6800>, argv=<error reading variable: Cannot access memory at address 0x220c6804>) at ../../../systemsettings/app/main.cpp:49

Reported using DrKonqi
Comment 1 Christoph Feck 2013-04-13 22:07:57 UTC
*** Bug 318310 has been marked as a duplicate of this bug. ***
Comment 2 Jekyll Wu 2013-10-05 09:31:12 UTC
*** Bug 325652 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2013-12-26 15:12:41 UTC
*** Bug 329188 has been marked as a duplicate of this bug. ***
Comment 4 T2 2014-07-01 18:44:07 UTC
Created attachment 87504 [details]
New crash information added by DrKonqi

systemsettings (4.11.9) on KDE Platform 4.13.1 using Qt 4.8.6

- What I was doing when the application crashed:

clicked into camera (it loaded...add device panel i think), at some point i selected the setting i wanted to check next. i 'might' have hit the quit button when it seg'ed...

-- Backtrace (Reduced):
#6  data (this=0x2f007300700078) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
[...]
#9  QStandardItemModel::clear (this=0x2f007300700070) at itemviews/qstandarditemmodel.cpp:2088
#10 0x00007f4254270a04 in KKameraConfig::populateDeviceListView (this=this@entry=0x61bffe0) at ../../kcontrol/kamera.cpp:173
#11 0x00007f4254272579 in KKameraConfig::load (this=0x61bffe0) at ../../kcontrol/kamera.cpp:259
#12 0x00007f427cbe2dc9 in KCModule::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at ./kcmodule.moc:65
Comment 5 Christoph Feck 2014-08-11 21:51:14 UTC
*** Bug 338201 has been marked as a duplicate of this bug. ***
Comment 6 Christoph Feck 2016-02-25 03:12:11 UTC
*** Bug 359779 has been marked as a duplicate of this bug. ***
Comment 7 Christoph Feck 2017-11-23 23:08:54 UTC
*** Bug 386533 has been marked as a duplicate of this bug. ***
Comment 8 David Edmundson 2018-03-22 00:50:09 UTC
Still relevant in 5, see final linked report
Comment 9 Christoph Feck 2018-09-26 00:08:23 UTC
*** Bug 394328 has been marked as a duplicate of this bug. ***
Comment 10 Christoph Feck 2018-10-01 14:44:56 UTC
*** Bug 398209 has been marked as a duplicate of this bug. ***
Comment 11 Christoph Feck 2019-09-17 02:29:57 UTC
*** Bug 411468 has been marked as a duplicate of this bug. ***
Comment 12 David Edmundson 2019-09-19 23:59:44 UTC
*** Bug 410790 has been marked as a duplicate of this bug. ***
Comment 13 Justin Zobel 2022-09-25 22:38:29 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 14 Bug Janitor Service 2022-10-10 04:51:59 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
mark the bug 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 15 Bug Janitor Service 2022-10-25 05:01:15 UTC
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!