Bug 293107

Summary: when kde's load was completed, the crash window appears
Product: [Unmaintained] Network Management Reporter: Samir <sahincapiec>
Component: KDED ModuleAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: lamarque
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Samir 2012-02-02 00:39:42 UTC
Application: kded4 ($Id$)
KDE Platform Version: 4.8.00 (4.8.0
Qt Version: 4.7.4
Operating System: Linux 3.0.0-15-generic i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:
i started up my computer
i started my session
then when kde's load was completed, the crash window appears

- Custom settings of the application:
i updated from kde 4.7.4 to 4.8
when I was using kde 4.7.4 I did not have this problem but now since I updated kde to 4.8 whenever I turn on my computer this error occurs

-- Backtrace:
Application: Servicio de KDE (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb77db710 (LWP 1535))]

Thread 3 (Thread 0xb325db70 (LWP 1615)):
#0  0x00bea416 in __kernel_vsyscall ()
#1  0x00a8b40e in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x078da34b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x078cb896 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x078cbf9b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x0401fcea in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0x078f25f4 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x027a9a9c in ?? () from /usr/lib/nvidia-current/libGL.so.1
#8  0x00000000 in ?? ()

Thread 2 (Thread 0xb2a5cb70 (LWP 1616)):
#0  0x0661ed44 in __pthread_mutex_unlock_usercnt () from /lib/i386-linux-gnu/libpthread.so.0
#1  0x00aa7f54 in pthread_mutex_unlock () from /lib/i386-linux-gnu/libc.so.6
#2  0x078ca7e1 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x078cb637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x078cbc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x0101eb37 in QEventDispatcherGlib::processEvents (this=0x8dd8c40, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x00fef1dd in QEventLoop::processEvents (this=0xb2a5c200, flags=...) at kernel/qeventloop.cpp:149
#7  0x00fef421 in QEventLoop::exec (this=0xb2a5c200, flags=...) at kernel/qeventloop.cpp:201
#8  0x00ef290b in QThread::exec (this=0x8dcdfd8) at thread/qthread.cpp:498
#9  0x00fcfe2d in QInotifyFileSystemWatcherEngine::run (this=0x8dcdfd8) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00ef57b3 in QThreadPrivate::start (arg=0x8dcdfd8) at thread/qthread_unix.cpp:331
#11 0x027a9a9c in ?? () from /usr/lib/nvidia-current/libGL.so.1
#12 0x00000000 in ?? ()

Thread 1 (Thread 0xb77db710 (LWP 1535)):
[KCrash Handler]
#7  ref (this=0x6f0074) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#8  QList (l=..., this=0xbfb44a80) at /usr/include/qt4/QtCore/qlist.h:118
#9  QForeachContainer (t=..., this=0xbfb44a80) at /usr/include/qt4/QtCore/qglobal.h:2253
#10 Knm::Connection::setting (this=0x8e019a0, settingType=Knm::Setting::Wireless) at ../../../libs/internals/connection.cpp:355
#11 0x03642f49 in WirelessSecurityAuthWidget::WirelessSecurityAuthWidget (this=0x8e33c18, connection=0x8e019a0, parent=0x0) at ../../../libs/ui/security/wirelesssecurityauth.cpp:57
#12 0x0364fd54 in ConnectionSecretsJob::doAskUser (this=0x8e60980) at ../../../libs/ui/connectionsecretsjob.cpp:115
#13 0x035f5d72 in ConnectionSecretsJob::qt_metacall (this=0x8e60980, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x8e4a998) at moc_connectionsecretsjob.cpp:75
#14 0x00ff6b7d in metacall (argv=0x8e4a998, idx=26, cl=QMetaObject::InvokeMetaMethod, object=0x8e60980) at kernel/qmetaobject.cpp:237
#15 QMetaObject::metacall (object=0x8e60980, cl=QMetaObject::InvokeMetaMethod, idx=26, argv=0x8e4a998) at kernel/qmetaobject.cpp:232
#16 0x01001685 in QMetaCallEvent::placeMetaCall (this=0x8de4068, object=0x8e60980) at kernel/qobject.cpp:535
#17 0x01008b52 in QObject::event (this=0x8e60980, e=0x8de4068) at kernel/qobject.cpp:1217
#18 0x01282d84 in notify_helper (e=0x8de4068, receiver=0x8e60980, this=0x8ba6a68) at kernel/qapplication.cpp:4486
#19 QApplicationPrivate::notify_helper (this=0x8ba6a68, receiver=0x8e60980, e=0x8de4068) at kernel/qapplication.cpp:4458
#20 0x01288133 in QApplication::notify (this=0x8de4068, receiver=0x8e60980, e=0x8de4068) at kernel/qapplication.cpp:3886
#21 0x002fe011 in KApplication::notify (this=0xbfb45390, receiver=0x8e60980, event=0x8de4068) at ../../kdeui/kernel/kapplication.cpp:311
#22 0x00ff019e in QCoreApplication::notifyInternal (this=0xbfb45390, receiver=0x8e60980, event=0x8de4068) at kernel/qcoreapplication.cpp:787
#23 0x00ff3f93 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8af2ca8) at kernel/qcoreapplication.cpp:1428
#25 0x00ff40ec in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1321
#26 0x0101e6a4 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#27 postEventSourceDispatch (s=0x8ba8ed0) at kernel/qeventdispatcher_glib.cpp:277
#28 0x078cb25f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#29 0x078cb990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#30 0x078cbc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#31 0x0101eada in QEventDispatcherGlib::processEvents (this=0x8af41e0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#32 0x0133ae7a in QGuiEventDispatcherGlib::processEvents (this=0x8af41e0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x00fef1dd in QEventLoop::processEvents (this=0xbfb452f4, flags=...) at kernel/qeventloop.cpp:149
#34 0x00fef421 in QEventLoop::exec (this=0xbfb452f4, flags=...) at kernel/qeventloop.cpp:201
#35 0x00ff419d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#36 0x01280924 in QApplication::exec () at kernel/qapplication.cpp:3760
#37 0x0695c899 in kdemain (argc=1, argv=0x8b80070) at ../../kded/kded.cpp:924
#38 0x0804f762 in launch (argc=<optimized out>, _name=0x8052465 "kded4", args=<optimized out>, cwd=0x0, envc=0, envs=<optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x805234c "0") at ../../kinit/kinit.cpp:746
#39 0x0804c909 in main (argc=) at ../../kinit/kinit.cpp:1861

Reported using DrKonqi
Comment 1 Lamarque V. Souza 2012-02-03 11:28:30 UTC
Why did you create a duplicate of a bug that you already reported? Do not do that. Creating multiple bug entries is not going to make me fix them quickly, on the contrary, it makes me lose time to close them.

*** This bug has been marked as a duplicate of bug 292632 ***
Comment 2 Samir 2012-02-03 16:39:10 UTC
i don't create a duplicate because the duplicate's list was empty.

2012/2/3 Lamarque V. Souza <lamarque@kde.org>

> https://bugs.kde.org/show_bug.cgi?id=293107
>
>
> Lamarque V. Souza <lamarque@kde.org> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |RESOLVED
>                 CC|                            |lamarque@kde.org
>          Component|kded                        |KDED Module
>         Resolution|                            |DUPLICATE
>            Product|kdelibs                     |Network Management
>
>
>
>
> --- Comment #1 from Lamarque V. Souza <lamarque kde org>  2012-02-03
> 11:28:30 ---
> Why did you create a duplicate of a bug that you already reported? Do not
> do
> that. Creating multiple bug entries is not going to make me fix them
> quickly,
> on the contrary, it makes me lose time to close them.
>
> *** This bug has been marked as a duplicate of bug 292632 ***
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>