Bug 377586 - Plasma crash after opening network manager twice?
Summary: Plasma crash after opening network manager twice?
Status: RESOLVED DUPLICATE of bug 358321
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: master
Platform: Other Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-13 22:13 UTC by Paul
Modified: 2017-03-17 15:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
crashlog (26.23 KB, text/plain)
2017-03-13 22:13 UTC, Paul
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul 2017-03-13 22:13:00 UTC
Created attachment 104547 [details]
crashlog

While looking at adding a recently added virtual network adapter to the actual network manager, I ended up opening said manager twice via the taskbar icon, the existing window was minimised and it appears that it remained open when plasma restarted.
Comment 1 Marco Martin 2017-03-17 15:35:28 UTC
backtraces must be pasted inline

Thread 1 (Thread 0x7f09639798c0 (LWP 1471)):
[KCrash Handler]
#6  0x00007f0963a0d441 in QSqlDatabase::close() () from /usr/lib/x86_64-linux-gnu/libQt5Sql.so.5
#7  0x00007f0963a0fab9 in QSqlDatabase::~QSqlDatabase() () from /usr/lib/x86_64-linux-gnu/libQt5Sql.so.5
#8  0x00007f0963a127ad in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Sql.so.5
#9  0x00007f095e96f019 in QHashData::free_helper(void (*)(QHashData::Node*)) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f0963a0d197 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Sql.so.5
#11 0x00007f095e14c2e0 in __run_exit_handlers (status=1, listp=0x7f095e4d35d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83
#12 0x00007f095e14c33a in __GI_exit (status=<optimized out>) at exit.c:105
#13 0x00007f095065fd53 in QXcbConnection::processXcbEvents() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#14 0x00007f095eb14699 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f095f4218ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f095f426d4f in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x00007f095eae63b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f095eae833c in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f095eb3c083 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f095af4e7d7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f095af4ea40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f095af4eaec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f095eb3c48f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007f095eae40fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007f095eaec90c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x000055fe737bdf1f in ?? ()
#27 0x00007f095e1323f1 in __libc_start_main (main=0x55fe737bd3b0, argc=2, argv=0x7fff71229ea8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff71229e98) at ../csu/libc-start.c:291
#28 0x000055fe737be29a in _start ()
Comment 2 Marco Martin 2017-03-17 15:36:09 UTC

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