Summary: | Connection editor crashed when trying to edit WPA-PSK secured WiFi network | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Christopher Griffiths <kde> |
Component: | kcm_networkmanagement | Assignee: | Lukáš Tinkl <lukas> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bugs.kde.org, jgrulich |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Christopher Griffiths
2015-04-13 17:32:27 UTC
Created attachment 92015 [details]
New crash information added by DrKonqi
kde-nm-connection-editor (0.9.3.4) on KDE Platform 4.14.3 using Qt 4.8.6
- What I was doing when the application crashed:
Trying to open the configuration window of a connection; any connection crashed.
- Custom settings of the application:
I installed a second Wifi adapter and used it instead of my other adapter to connect to the same network; this created an entry with the same name as the one used with the other adapter. I was planning on modifying the names to disambiguate them and then encountered this crash.
-- Backtrace (Reduced):
#5 0x00007faff1c893bd in ConnectionDetailEditor::gotSecrets(QString const&, bool, QMap<QString, QMap<QString, QVariant> > const&, QString const&) () from /usr/lib64/libplasmanetworkmanagement-editor.so
[...]
#7 0x00007faff19126dd in NetworkManager::Connection::gotSecrets(QString const&, bool, QMap<QString, QMap<QString, QVariant> > const&, QString const&) () from /usr/lib64/libNetworkManagerQt.so.1
#8 0x00007faff1914a13 in NetworkManager::Connection::onSecretsArrived(QDBusPendingCallWatcher*) () from /usr/lib64/libNetworkManagerQt.so.1
[...]
#10 0x00007fafeee3a24f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /usr/lib64/qt4/libQtDBus.so.4
#11 0x00007faff15668a6 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
*** This bug has been marked as a duplicate of bug 340084 *** |