Bug 346897

Summary: Connection Editor crashes when editing openvpn
Product: [Applications] systemsettings Reporter: Joe <deathraccooni2p>
Component: kcm_networkmanagementAssignee: Lukáš Tinkl <lukas>
Status: RESOLVED DUPLICATE    
Severity: crash CC: frycarson, 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 Joe 2015-04-29 12:21:57 UTC 
Application: kde-nm-connection-editor (0.9.3.4)
KDE Platform Version: 4.14.3 (Compiled from sources)
Qt Version: 4.8.5
Operating System: Linux 4.0.0-ck x86_64
Distribution: "Gentoo Base System release 2.2"

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

I had already imported a vpn config. When I attepted to edit that connection, the application crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Connection editor (kde-nm-connection-editor), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x00007fb7236b23bd in ConnectionDetailEditor::gotSecrets(QString const&, bool, QMap<QString, QMap<QString, QVariant> > const&, QString const&) () from /usr/lib64/libplasmanetworkmanagement-editor.so
#6  0x00007fb722f8c73a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#7  0x00007fb72333b6dd in NetworkManager::Connection::gotSecrets(QString const&, bool, QMap<QString, QMap<QString, QVariant> > const&, QString const&) () from /usr/lib64/libNetworkManagerQt.so.1
#8  0x00007fb72333da13 in NetworkManager::Connection::onSecretsArrived(QDBusPendingCallWatcher*) () from /usr/lib64/libNetworkManagerQt.so.1
#9  0x00007fb722f8c73a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#10 0x00007fb720874eaf in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /usr/lib64/qt4/libQtDBus.so.4
#11 0x00007fb722f90bc6 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#12 0x00007fb7212f962c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#13 0x00007fb7212ffda8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#14 0x00007fb7229bfd6a in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#15 0x00007fb722f7826c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#16 0x00007fb722f7b3a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4
#17 0x00007fb722fa675e in ?? () from /usr/lib64/qt4/libQtCore.so.4
#18 0x00007fb71fa994ab in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#19 0x00007fb71fa996c8 in ?? () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fb71fa9978c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fb722fa5ebc in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#22 0x00007fb72139a806 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#23 0x00007fb722f76dcf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#24 0x00007fb722f7710d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#25 0x00007fb722f7c409 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#26 0x0000000000409e62 in ?? ()
#27 0x00007fb720ab6aa5 in __libc_start_main () from /lib64/libc.so.6
#28 0x0000000000409f69 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 340084.

Possible duplicates by query: bug 346735, bug 346145, bug 346057, bug 345417, bug 342074.

Reported using DrKonqi
Comment 1 Jan Grulich 2015-04-29 12:38:06 UTC 

*** This bug has been marked as a duplicate of bug 340084 ***
Comment 2 frycarson 2015-05-04 04:38:10 UTC 
Created attachment 92405 [details]
New crash information added by DrKonqi

kde-nm-connection-editor (0.9.3.4) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed:
Attempting to edit existing VPN Connection
Able to edit Wired Connection without issue

-- Backtrace (Reduced):
#6  0x00007fcbb6951166 in ConnectionDetailEditor::gotSecrets(QString const&, bool, QMap<QString, QMap<QString, QVariant> > const&, QString const&) () from /usr/lib/libplasmanetworkmanagement-editor.so
[...]
#8  0x00007fcbb65c6b4d in NetworkManager::Connection::gotSecrets(QString const&, bool, QMap<QString, QMap<QString, QVariant> > const&, QString const&) () from /usr/lib/x86_64-linux-gnu/libNetworkManagerQt.so.1
#9  0x00007fcbb65c74d0 in NetworkManager::Connection::onSecretsArrived(QDBusPendingCallWatcher*) () from /usr/lib/x86_64-linux-gnu/libNetworkManagerQt.so.1
[...]
#11 0x00007fcbb6349e1f in QDBusPendingCallWatcher::finished (this=<optimized out>, _t1=0x220e4c0) at .moc/release-shared/moc_qdbuspendingcall.cpp:105
#12 0x00007fcbb5d56e11 in QObject::event (this=0x220e4c0, e=<optimized out>) at kernel/qobject.cpp:1222