[konsole] [Bug 388188] New: continuing...

Sun Dec 24 01:45:08 UTC 2017

https://bugs.kde.org/show_bug.cgi?id=388188

            Bug ID: 388188
           Summary: continuing...
           Product: konsole
           Version: 16.12.3
          Platform: Mageia RPMs
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: konsole-devel at kde.org
          Reporter: gerald.david at gmx.com
  Target Milestone: ---

Application: konsole (16.12.3)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.9.56-desktop-1.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed: bugreport popup; please see
backtrace. Was online with wifi using drakconnect to setup wlp3s0b1 on house 5G
wifi using wpa2. Viewed contents of htop and noticed under /sbin/init/|
                                |-sbin/ifplugd -I -b -i wlp3s0b1 -c
/etc/wpa_supplicant.conf -D wext

I use drakconnect to setup & then takedown interfaces each time as they seem to
be populated with settings that I do not choose or use in my house wifi
connection, and the strange settings that reappear constantly seem to increase
with the amount of time I am online & typically appear if I forget them
unattended for any length of time. I do not use any wext extensions.

After viewing this in htop I then tried connecting using a linksys usb (uses
ndiswrapper), used drakconnect to set up connection. Opened and found 5G
connection populated, (typically only uses 2.4G, (but thats another looping
story), pressed connect & DrK popped up, asking for a bug report. Took
screenshot of htop, please see attached, and promptly reported. drakconnect
reports a successful 2.4G connection... may I LOL here..? ;)

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa7ad486800 (LWP 14519))]

Thread 3 (Thread 0x7fa78989f700 (LWP 14528)):
#0  0x00007fa7a6186c4f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x00007fa7914b2e2b in util_queue_thread_func () from
/usr/lib64/dri/nouveau_dri.so
#2  0x00007fa7914b2b97 in impl_thrd_routine () from
/usr/lib64/dri/nouveau_dri.so
#3  0x00007fa7a618166d in start_thread () from /lib64/libpthread.so.0
#4  0x00007fa7acf3ed4d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fa7929b5700 (LWP 14527)):
#0  0x00007fa7acf32f0d in poll () from /lib64/libc.so.6
#1  0x00007fa7a5c5ec94 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x00007fa7a5c5ed9c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x00007fa7a9b0fe2b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib64/libQt5Core.so.5
#4  0x00007fa7a9abb49a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib64/libQt5Core.so.5
#5  0x00007fa7a98f53bc in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x00007fa7ad557635 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#7  0x00007fa7a98f9ff9 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x00007fa7a618166d in start_thread () from /lib64/libpthread.so.0
#9  0x00007fa7acf3ed4d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fa7ad486800 (LWP 14519)):
[KCrash Handler]
#6  0x00007fa7a928f1a9 in KNotification::id() () from
/lib64/libKF5Notifications.so.5
#7  0x00007fa7a92917c9 in
KNotificationManager::notifyPluginFinished(KNotification*) () from
/lib64/libKF5Notifications.so.5
#8  0x00007fa7a9291bdc in KNotificationManager::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libKF5Notifications.so.5
#9  0x00007fa7a9ae8859 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#10 0x00007fa7a92bb49f in KNotificationPlugin::finished(KNotification*) () from
/lib64/libKF5Notifications.so.5
#11 0x00007fa7a92a351c in NotifyByPopup::onPassivePopupDestroyed() () from
/lib64/libKF5Notifications.so.5
#12 0x00007fa7a9ae8859 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#13 0x00007fa7a9ae8f6f in QObject::destroyed(QObject*) () from
/lib64/libQt5Core.so.5
#14 0x00007fa7aa6a10c1 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5
#15 0x00007fa7a9293319 in KPassivePopup::~KPassivePopup() () from
/lib64/libKF5Notifications.so.5
#16 0x00007fa7a9ae93e0 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#17 0x00007fa7aa6a54b3 in QWidget::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#18 0x00007fa7aa79efbe in QFrame::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#19 0x00007fa7aa662d0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#20 0x00007fa7aa667e76 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#21 0x00007fa7a9abd628 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#22 0x00007fa7a9abf44b in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#23 0x00007fa7a9b0f9f3 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#24 0x00007fa7a5c5eac7 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#25 0x00007fa7a5c5ecf8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#26 0x00007fa7a5c5ed9c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#27 0x00007fa7a9b0fe06 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib64/libQt5Core.so.5
#28 0x00007fa7a9abb49a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib64/libQt5Core.so.5
#29 0x00007fa7a9ac37e1 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#30 0x00007fa7ad223955 in kdemain () from /lib64/libkdeinit5_konsole.so
#31 0x00007fa7ace69600 in __libc_start_main () from /lib64/libc.so.6
#32 0x0000000000400719 in _start ()

Possible duplicates by query: bug 388181.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.