Bug 292632

Summary: Crash after start session
Product: [Unmaintained] Network Management Reporter: Samir <sahincapiec>
Component: KDED ModuleAssignee: Lamarque V. Souza <lamarque>
Status: RESOLVED DUPLICATE    
Severity: crash CC: fermadrip, sahincapiec, unclemarcus91
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi
New crash information added by DrKonqi

Description Samir 2012-01-27 21:47:31 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 upgraded kde from 4.7.4 to 4.8
then i closed my session
then i rebooted the server x
then i start my session
then the crash window appears
- Custom settings of the application:
i updated kde from 4.7.4 to 4.8

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

Thread 3 (Thread 0xb3275b70 (LWP 9498)):
#0  0x00e46416 in __kernel_vsyscall ()
#1  0x00d5340e in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x03c4634b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x03c37896 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x03c37f9b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x03516cea in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0x03c5e5f4 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x024eda9c in ?? () from /usr/lib/nvidia-current/libGL.so.1
#8  0x00000000 in ?? ()

Thread 2 (Thread 0xb2a74b70 (LWP 9499)):
#0  0x00e3fd10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1  0x00ab17d5 in do_gettime (frac=0xb2a73f70, sec=0xb2a73f68) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x00b844b6 in QTimerInfoList::updateCurrentTime (this=0x8a9758c) at kernel/qeventdispatcher_unix.cpp:339
#4  0x00b8480a in QTimerInfoList::timerWait (this=0x8a9758c, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0x00b83053 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb2a7407c) at kernel/qeventdispatcher_glib.cpp:136
#6  0x00b830ed in timerSourcePrepare (source=0x8a97558, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0x03c3688c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0x03c37637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0x03c37c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0x00b83b37 in QEventDispatcherGlib::processEvents (this=0x89f2b50, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0x00b541dd in QEventLoop::processEvents (this=0xb2a74200, flags=...) at kernel/qeventloop.cpp:149
#12 0x00b54421 in QEventLoop::exec (this=0xb2a74200, flags=...) at kernel/qeventloop.cpp:201
#13 0x00a5790b in QThread::exec (this=0x8a8f988) at thread/qthread.cpp:498
#14 0x00b34e2d in QInotifyFileSystemWatcherEngine::run (this=0x8a8f988) at io/qfilesystemwatcher_inotify.cpp:248
#15 0x00a5a7b3 in QThreadPrivate::start (arg=0x8a8f988) at thread/qthread_unix.cpp:331
#16 0x024eda9c in ?? () from /usr/lib/nvidia-current/libGL.so.1
#17 0x00000000 in ?? ()

Thread 1 (Thread 0xb77ea710 (LWP 9487)):
[KCrash Handler]
#7  0x06c68194 in Knm::Setting::type (this=0x31000000) at ../../../libs/internals/setting.cpp:154
#8  0x06c65a12 in Knm::Connection::setting (this=0x89cda00, settingType=Knm::Setting::Wireless) at ../../../libs/internals/connection.cpp:356
#9  0x030d0f49 in WirelessSecurityAuthWidget::WirelessSecurityAuthWidget (this=0x89f7068, connection=0x89cda00, parent=0x0) at ../../../libs/ui/security/wirelesssecurityauth.cpp:57
#10 0x030ddd54 in ConnectionSecretsJob::doAskUser (this=0x8ab6d08) at ../../../libs/ui/connectionsecretsjob.cpp:115
#11 0x03083d72 in ConnectionSecretsJob::qt_metacall (this=0x8ab6d08, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x89a58c8) at moc_connectionsecretsjob.cpp:75
#12 0x00b5bb7d in metacall (argv=0x89a58c8, idx=26, cl=QMetaObject::InvokeMetaMethod, object=0x8ab6d08) at kernel/qmetaobject.cpp:237
#13 QMetaObject::metacall (object=0x8ab6d08, cl=QMetaObject::InvokeMetaMethod, idx=26, argv=0x89a58c8) at kernel/qmetaobject.cpp:232
#14 0x00b66685 in QMetaCallEvent::placeMetaCall (this=0x8a40628, object=0x8ab6d08) at kernel/qobject.cpp:535
#15 0x00b6db52 in QObject::event (this=0x8ab6d08, e=0x8a40628) at kernel/qobject.cpp:1217
#16 0x01150d84 in notify_helper (e=0x8a40628, receiver=0x8ab6d08, this=0x886da00) at kernel/qapplication.cpp:4486
#17 QApplicationPrivate::notify_helper (this=0x886da00, receiver=0x8ab6d08, e=0x8a40628) at kernel/qapplication.cpp:4458
#18 0x01156133 in QApplication::notify (this=0x8a40628, receiver=0x8ab6d08, e=0x8a40628) at kernel/qapplication.cpp:3886
#19 0x0079d011 in KApplication::notify (this=0xbf884130, receiver=0x8ab6d08, event=0x8a40628) at ../../kdeui/kernel/kapplication.cpp:311
#20 0x00b5519e in QCoreApplication::notifyInternal (this=0xbf884130, receiver=0x8ab6d08, event=0x8a40628) at kernel/qcoreapplication.cpp:787
#21 0x00b58f93 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#22 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x87b9ca8) at kernel/qcoreapplication.cpp:1428
#23 0x00b590ec in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1321
#24 0x00b836a4 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#25 postEventSourceDispatch (s=0x886fed0) at kernel/qeventdispatcher_glib.cpp:277
#26 0x03c3725f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#27 0x03c37990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#28 0x03c37c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#29 0x00b83ada in QEventDispatcherGlib::processEvents (this=0x87bb1e0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#30 0x01208e7a in QGuiEventDispatcherGlib::processEvents (this=0x87bb1e0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x00b541dd in QEventLoop::processEvents (this=0xbf884094, flags=...) at kernel/qeventloop.cpp:149
#32 0x00b54421 in QEventLoop::exec (this=0xbf884094, flags=...) at kernel/qeventloop.cpp:201
#33 0x00b5919d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#34 0x0114e924 in QApplication::exec () at kernel/qapplication.cpp:3760
#35 0x06726899 in kdemain (argc=1, argv=0x8847088) at ../../kded/kded.cpp:924
#36 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
#37 0x0804c909 in main (argc=) at ../../kinit/kinit.cpp:1861

Reported using DrKonqi
Comment 1 Lamarque V. Souza 2012-01-28 13:11:15 UTC
Can you still reproduce the problem? By the backtrace I do not see anything that could cause this crash. The only suspicious thing is the this pointer in "Knm::Setting::type (this=0x31000000)".
Comment 2 Christoph Feck 2012-01-29 14:35:49 UTC
*** Bug 292791 has been marked as a duplicate of this bug. ***
Comment 3 Samir 2012-01-30 01:26:21 UTC
Created attachment 68321 [details]
New crash information added by DrKonqi

kded4 ($Id$) on KDE Platform 4.8.00 (4.8.0 using Qt 4.7.4

- What I was doing when the application crashed:
i started up my computer
then i started my session
then when kde's load complete the crash window appears
- Custom settings of the application:
i updated kde from 4.7.4 to 4.8

-- Backtrace (Reduced):
#7  0x033c2a08 in Knm::Connection::setting (this=0x963e000, settingType=Knm::Setting::Wireless) at ../../../libs/internals/connection.cpp:355
#8  0x03715f49 in WirelessSecurityAuthWidget::WirelessSecurityAuthWidget (this=0x967a660, connection=0x963e000, parent=0x0) at ../../../libs/ui/security/wirelesssecurityauth.cpp:57
#9  0x03722d54 in ConnectionSecretsJob::doAskUser (this=0x93c1fe0) at ../../../libs/ui/connectionsecretsjob.cpp:115
#10 0x036c8d72 in ConnectionSecretsJob::qt_metacall (this=0x93c1fe0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x9614c70) at moc_connectionsecretsjob.cpp:75
#11 0x005dbb7d in metacall (argv=0x9614c70, idx=26, cl=QMetaObject::InvokeMetaMethod, object=0x93c1fe0) at kernel/qmetaobject.cpp:237
Comment 4 Samir 2012-01-30 20:15:12 UTC
Created attachment 68348 [details]
New crash information added by DrKonqi

kded4 ($Id$) on KDE Platform 4.8.00 (4.8.0 using Qt 4.7.4

- What I was doing when the application crashed:
i started up my computer
i started my session
then when kde's load completed the crash windows 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 (Reduced):
#7  0x03d2ca08 in Knm::Connection::setting (this=0xa1a81a0, settingType=Knm::Setting::Wireless) at ../../../libs/internals/connection.cpp:355
#8  0x03ed4f49 in WirelessSecurityAuthWidget::WirelessSecurityAuthWidget (this=0xa205708, connection=0xa1a81a0, parent=0x0) at ../../../libs/ui/security/wirelesssecurityauth.cpp:57
#9  0x03ee1d54 in ConnectionSecretsJob::doAskUser (this=0x9fbfa48) at ../../../libs/ui/connectionsecretsjob.cpp:115
#10 0x03e87d72 in ConnectionSecretsJob::qt_metacall (this=0x9fbfa48, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xa25d880) at moc_connectionsecretsjob.cpp:75
#11 0x00c71b7d in metacall (argv=0xa25d880, idx=26, cl=QMetaObject::InvokeMetaMethod, object=0x9fbfa48) at kernel/qmetaobject.cpp:237
Comment 5 Lamarque V. Souza 2012-01-30 20:30:23 UTC
I use KDE SC 4.8.0 with Qt 4.7.4 and I cannot reproduce this problem. (K)Ubuntu 11.10 ships with a very old Plasma NM version from more than five months ago. Can you upgrade to a newer Plasma NM and see if that solves the problem?
Comment 6 Samir 2012-01-30 21:16:27 UTC
hi,

i have installed network-manager (0.9.1.90-0ubuntu5.1) oneiric-proposed

2012/1/30 Lamarque V. Souza <lamarque@kde.org>

> https://bugs.kde.org/show_bug.cgi?id=292632
>
>
>
>
>
> --- Comment #5 from Lamarque V. Souza <lamarque kde org>  2012-01-30
> 20:30:23 ---
> I use KDE SC 4.8.0 with Qt 4.7.4 and I cannot reproduce this problem.
> (K)Ubuntu
> 11.10 ships with a very old Plasma NM version from more than five months
> ago.
> Can you upgrade to a newer Plasma NM and see if that solves the problem?
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You reported the bug.
>
Comment 7 Lamarque V. Souza 2012-01-30 21:26:59 UTC
I was talking about Plasma NetworkManagement (Plasma NM), not NetworkManager. I think (K)Ubuntu uses plasma-widget-networkmanagement as the package name for Plasma NM. That is the package you must upgrade to at least version 0.8.99 (again that is the Plasma NM version, not NetworkManager's).
Comment 8 Samir 2012-01-30 22:14:56 UTC
Hi,

I have installed plasma-widget-networkmanagement Network Management widget
for KDE Plasma workspaces version 0.9.0~rc4-0ubuntu1~oneiric1~ppa1

2012/1/30 Lamarque V. Souza <lamarque@kde.org>

> https://bugs.kde.org/show_bug.cgi?id=292632
>
>
>
>
>
> --- Comment #7 from Lamarque V. Souza <lamarque kde org>  2012-01-30
> 21:26:59 ---
> I was talking about Plasma NetworkManagement (Plasma NM), not
> NetworkManager. I
> think (K)Ubuntu uses plasma-widget-networkmanagement as the package name
> for
> Plasma NM. That is the package you must upgrade to at least version 0.8.99
> (again that is the Plasma NM version, not NetworkManager's).
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You reported the bug.
>
Comment 9 Lamarque V. Souza 2012-01-30 22:24:03 UTC
Ok, that is that latest Plasma NM I have released. Which security type your wifi connection use (WEP, WPA, WPA2)?
Comment 10 Samir 2012-01-30 22:28:11 UTC
my wifi connection use WEP

2012/1/30 Lamarque V. Souza <lamarque@kde.org>

> https://bugs.kde.org/show_bug.cgi?id=292632
>
>
>
>
>
> --- Comment #9 from Lamarque V. Souza <lamarque kde org>  2012-01-30
> 22:24:03 ---
> Ok, that is that latest Plasma NM I have released. Which security type your
> wifi connection use (WEP, WPA, WPA2)?
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You reported the bug.
>
Comment 11 Lamarque V. Souza 2012-02-03 11:28:30 UTC
*** Bug 293107 has been marked as a duplicate of this bug. ***
Comment 12 Lamarque V. Souza 2012-02-05 22:50:45 UTC
Please enable debugging using kdebugdialog, reproduce the crash and send me the file ~/.xsession-errors (compress it if it is too big). After launching kdebugdialog search for the string "network" and mark all checkboxes that appear.
Comment 13 Lamarque V. Souza 2012-02-09 13:46:52 UTC
*** Bug 293684 has been marked as a duplicate of this bug. ***
Comment 14 Lamarque V. Souza 2012-02-09 13:47:08 UTC
*** Bug 293685 has been marked as a duplicate of this bug. ***
Comment 15 Lamarque V. Souza 2012-02-12 01:16:32 UTC
Can you configure NetworkManager to use keyfile plugin instead of ifnet,
ifcfg-rh or other plugin and test if the problem still happens? You can do that
by editing the file /etc/NetworkManager/NetworkManager.conf or
/etc/NetworkManager/nm-system-settings.conf. Just change the line with
"plugins=" looks like this:

[main]
plugins=keyfile

and restart NetworkManager.

I was talking with a friend about a bug he had where Plasma NM did not detect
the correct WEP key type. Today we have figured out that it happens because
NetworkManager was using ifcfg-rh, using keyfile Plasma NM works correctly. I
think the same problem that caused my friend's problem can also cause this
crash, so please test NetworkManager with keyfile plugin and report if that
solves the problem or not.
Comment 16 Samir 2012-02-12 11:56:51 UTC
i'm using Unity

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

> https://bugs.kde.org/show_bug.cgi?id=292632
>
>
>
>
>
> --- Comment #15 from Lamarque V. Souza <lamarque kde org>  2012-02-12
> 01:16:32 ---
> Can you configure NetworkManager to use keyfile plugin instead of ifnet,
> ifcfg-rh or other plugin and test if the problem still happens? You can do
> that
> by editing the file /etc/NetworkManager/NetworkManager.conf or
> /etc/NetworkManager/nm-system-settings.conf. Just change the line with
> "plugins=" looks like this:
>
> [main]
> plugins=keyfile
>
> and restart NetworkManager.
>
> I was talking with a friend about a bug he had where Plasma NM did not
> detect
> the correct WEP key type. Today we have figured out that it happens because
> NetworkManager was using ifcfg-rh, using keyfile Plasma NM works
> correctly. I
> think the same problem that caused my friend's problem can also cause this
> crash, so please test NetworkManager with keyfile plugin and report if that
> solves the problem or not.
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You reported the bug.
>
Comment 17 Lamarque V. Souza 2012-02-12 13:07:36 UTC
(In reply to comment #16)
> i'm using Unity

Are you using Unity now or were you using Unity when you reported the this bug? Unity is not KDE software, can I close this bug?
Comment 18 Lamarque V. Souza 2012-02-12 13:37:35 UTC

*** This bug has been marked as a duplicate of bug 291874 ***
Comment 19 Samir 2012-02-12 14:02:25 UTC
when i used kubuntu (kde 4.8) i reported the this bug, now i use ubuntu
(unity).
i think is better fix this bug than close it

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

> https://bugs.kde.org/show_bug.cgi?id=292632
>
>
> Lamarque V. Souza <lamarque@kde.org> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |RESOLVED
>         Resolution|                            |DUPLICATE
>
>
>
>
> --- Comment #18 from Lamarque V. Souza <lamarque kde org>  2012-02-12
> 13:37:35 ---
>
>
> *** This bug has been marked as a duplicate of bug 291874 ***
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You reported the bug.
>
Comment 20 Lamarque V. Souza 2012-02-17 13:05:07 UTC
*** Bug 294303 has been marked as a duplicate of this bug. ***
Comment 21 Samir 2012-03-19 23:11:46 UTC
Hi,

I think I found the reason for the crash window don't appears.
I used two cards similar network, two network cards encore enuwi-g2, and
when i started the session the crash window appeared.
Now I have connected only one network card in the pc and when I start the
session does not show crash window .

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

> https://bugs.kde.org/show_bug.cgi?id=292632
>
>
> Lamarque V. Souza <lamarque@kde.org> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                 CC|                            |unclemarcus91@hotmail.com
>
>
>
>
> --- Comment #20 from Lamarque V. Souza <lamarque kde org>  2012-02-17
> 13:05:07 ---
> *** Bug 294303 has been marked as a duplicate of this bug. ***
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You reported the bug.
>
Comment 22 Lamarque V. Souza 2012-08-09 13:05:37 UTC
*** Bug 304850 has been marked as a duplicate of this bug. ***