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)".

*** Bug 292791 has been marked as a duplicate of this bug. ***

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

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

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?

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.
>

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).

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.
>

Ok, that is that latest Plasma NM I have released. Which security type your wifi connection use (WEP, WPA, WPA2)?

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.
>

*** Bug 293107 has been marked as a duplicate of this bug. ***

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.

*** Bug 293684 has been marked as a duplicate of this bug. ***

*** Bug 293685 has been marked as a duplicate of this bug. ***

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.

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.
>

(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?

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

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.
>

*** Bug 294303 has been marked as a duplicate of this bug. ***

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.
>

*** Bug 304850 has been marked as a duplicate of this bug. ***