[kopete] [Bug 414273] New: Kopete segfaults when going online

2019-11-18 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=414273

Bug ID: 414273
   Summary: Kopete segfaults when going online
   Product: kopete
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kopete-bugs-n...@kde.org
  Reporter: sh...@sorbom.com
  Target Milestone: ---

Application: kopete (1.13.0)

Qt Version: 5.13.1
Frameworks Version: 5.63.0
Operating System: Linux 4.15.0-66-generic x86_64
Distribution: KDE neon User Edition 5.17

-- Information about the crash:
- What I was doing when the application crashed:
At the kopete main window, I selected the "online" status to login to my XMPP
account.
- Custom settings of the application:
I am using an XMPP Account at im.koderoot.net, which kopete claims has a
self-signed certificate.
I had also recently cleared out my google talk account.

The crash started happening after kopete asked me to accept koderoot's
self-signed certificate

-- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbf0614a880 (LWP 6344))]

Thread 7 (Thread 0x7fbecbd93700 (LWP 6357)):
#0  0x7fbef8dff649 in g_mutex_lock () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fbef8db8b33 in g_main_context_prepare () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbef8db94fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbef8db96dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbf012fb9db in QEventDispatcherGlib::processEvents
(this=0x7fbebc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fbf0129beaa in QEventLoop::exec (this=this@entry=0x7fbecbd92c60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#6  0x7fbf010b73ca in QThread::exec (this=this@entry=0x562396df2170) at
thread/qthread.cpp:531
#7  0x7fbece0f1090 in XMPP::NetTrackerThread::run (this=0x562396df2170) at
./protocols/jabber/libiris/src/irisnet/corelib/netinterface.cpp:168
#8  0x7fbf010b8b72 in QThreadPrivate::start (arg=0x562396df2170) at
thread/qthread_unix.cpp:360
#9  0x7fbefaf566db in start_thread (arg=0x7fbecbd93700) at
pthread_create.c:463
#10 0x7fbf009b588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7fbecc594700 (LWP 6356)):
#0  0x7fbf009a8bf9 in __GI___poll (fds=0x7fbec4004e90, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fbef8db95c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbef8db96dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbf012fb9db in QEventDispatcherGlib::processEvents
(this=0x7fbec4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fbf0129beaa in QEventLoop::exec (this=0x7fbec4003ce0, flags=...) at
kernel/qeventloop.cpp:225
#5  0x7fbecda452f1 in QCA::SyncThread::run() () from
/usr/lib/x86_64-linux-gnu/libqca-qt5.so.2
#6  0x7fbf010b8b72 in QThreadPrivate::start (arg=0x562396dc0460) at
thread/qthread_unix.cpp:360
#7  0x7fbefaf566db in start_thread (arg=0x7fbecc594700) at
pthread_create.c:463
#8  0x7fbf009b588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fbed4ffd700 (LWP 6350)):
#0  0x7fbefaf5c9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x562396b5ee48) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x562396b5edf8,
cond=0x562396b5ee20) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x562396b5ee20, mutex=0x562396b5edf8) at
pthread_cond_wait.c:655
#3  0x7fbed60b62cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7fbed60b5ff7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7fbefaf566db in start_thread (arg=0x7fbed4ffd700) at
pthread_create.c:463
#6  0x7fbf009b588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fbee5dc8700 (LWP 6349)):
#0  __GI___pthread_getspecific (key=4) at pthread_getspecific.c:56
#1  0x7fbef8de1680 in g_thread_self () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbef8db845c in g_main_context_acquire () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbef8db9485 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbef8db96dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fbf012fb9db in QEventDispatcherGlib::processEvents
(this=0x7fbed8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fbf0129beaa in QEventLoop::exec (this=this@entry=0x7fbee5dc7d20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#7  0x7fbf010b73ca in QThread::exec (this=) at

[systemsettings] [Bug 395401] [evdev] Mouse settings are not loaded up at login

2018-11-30 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=395401

--- Comment #25 from Shawn Sörbom  ---
Bug still exists in 5.14.4. Has there been any progress in tracking it down?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 399580] Kwin Aborts after disabling Laptop monitor

2018-11-10 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=399580

Shawn Sörbom  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |---
 Status|NEEDSINFO   |REPORTED

--- Comment #6 from Shawn Sörbom  ---
See Comment 4

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts

2018-10-31 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=398847

Shawn Sörbom  changed:

   What|Removed |Added

 CC||sh...@sorbom.com

--- Comment #8 from Shawn Sörbom  ---
Same issue on KDE Neon 5.14.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 395401] [evdev] Mouse settings are not loaded up at login

2018-10-27 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=395401

--- Comment #23 from Shawn Sörbom  ---
Bug Still exists in 5.14.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 399580] Kwin Aborts after disabling Laptop monitor

2018-10-26 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=399580

Shawn Sörbom  changed:

   What|Removed |Added

Summary|Kwin Crashes after  |Kwin Aborts after disabling
   |disabling Laptop monitor|Laptop monitor

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 399580] Kwin Crashes after disabling Laptop monitor

2018-10-26 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=399580

--- Comment #4 from Shawn Sörbom  ---
Attaching to process 1650
[New LWP 1651]
[New LWP 1652]
[New LWP 1653]
[New LWP 1673]
[New LWP 1674]
[New LWP 1675]
[New LWP 1677]
[New LWP 1679]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f4fbae78cf6 in __GI_ppoll (fds=fds@entry=0x5629cf27c5f8,
nfds=nfds@entry=14, timeout=, timeout@entry=0x7ffeafcf32d0,
sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
39  ../sysdeps/unix/sysv/linux/ppoll.c: No such file or directory.
(gdb) continue
Continuing.
[New Thread 0x7f4f70d7f700 (LWP 2637)]
[New Thread 0x7f4f9260a700 (LWP 2638)]
[Thread 0x7f4f9260a700 (LWP 2638) exited]
[Thread 0x7f4f70d7f700 (LWP 2637) exited]
[Thread 0x7f4fa3c1a700 (LWP 1651) exited]

Thread 1 "kwin_wayland" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) continue
Continuing.
[Thread 0x7f4fa25bf700 (LWP 1653) exited]
[Thread 0x7f4f7c972700 (LWP 1679) exited]
[Thread 0x7f4f7d974700 (LWP 1677) exited]
[Thread 0x7f4f8a577700 (LWP 1675) exited]
[Thread 0x7f4fa2dc0700 (LWP 1652) exited]
[Thread 0x7f4fbe239cc0 (LWP 1650) exited]
[Thread 0x7f4f9172f700 (LWP 1673) exited]
[Inferior 1 (process 1650) exited with code 0375]


Weird. Kwin didn't crash -- it was aborted is there anywhere else I should
look?
Sorry this took so long.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 395401] [evdev] Mouse settings are not loaded up at login

2018-10-26 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=395401

--- Comment #22 from Shawn Sörbom  ---
Bug still exists in Plasma 5.14.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 399580] Kwin Crashes after disabling Laptop monitor

2018-10-10 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=399580

--- Comment #3 from Shawn Sörbom  ---
Nevermind, I found the info I needed via google search. I should be able to get
you a backtrace within 24 hours.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 399580] Kwin Crashes after disabling Laptop monitor

2018-10-10 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=399580

--- Comment #2 from Shawn Sörbom  ---
How can I get a backtrace on kwin? What logs should I check?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 399580] New: Kwin Crashes after disabling Laptop monitor

2018-10-09 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=399580

Bug ID: 399580
   Summary: Kwin Crashes after disabling Laptop monitor
   Product: kwin
   Version: 5.14.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: sh...@sorbom.com
  Target Milestone: ---

SUMMARY
Attempting to disable laptop monitor crashes the current login Session under
wayland
Setup: one docked laptop and one external monitor

STEPS TO REPRODUCE
1. Set session type to kwin wayland and login
2. open system settings display module
3. select laptop screen
4. Uncheck the "Enabled" checkbox
5. Click Apply

OBSERVED RESULT
Both monitors go black for a second and then I am returned to the SDDM login
screen.

EXPECTED RESULT
Laptop monitor disables

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
If I try to disable the external monitor instead, everything works as expected.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 395401] [evdev] Mouse settings are not loaded up at login

2018-09-06 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=395401

--- Comment #16 from Shawn Sörbom  ---
Bug Still exists in Plasma 5.13.5, Applications 18.08.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 393662] Kopete Crashes on Program exit

2018-09-06 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=393662

--- Comment #2 from Shawn Sörbom  ---
Bug still exists in kopete version 18.08.1, Plasma 5.13.5. No change in
behavior.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 395401] [evdev] Mouse settings are not loaded up at login

2018-08-28 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=395401

--- Comment #15 from Shawn Sörbom  ---
I should note that whatever is causing the settings to not be applied doesn't
seem to affect kwin_wayland, at least as far as the left handed setting is
concerned.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 395401] [evdev] Mouse settings are not loaded up at login

2018-08-28 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=395401

Shawn Sörbom  changed:

   What|Removed |Added

 CC||sh...@sorbom.com

--- Comment #14 from Shawn Sörbom  ---
*** Bug 398004 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 398004] Mouse Does Not Maintain "Left Handed" setting after reboot

2018-08-28 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=398004

Shawn Sörbom  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||sh...@sorbom.com

--- Comment #1 from Shawn Sörbom  ---


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

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 398004] New: Mouse Does Not Maintain "Left Handed" setting after reboot

2018-08-28 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=398004

Bug ID: 398004
   Summary: Mouse Does Not Maintain "Left Handed" setting after
reboot
   Product: systemsettings
   Version: 5.13.4
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_mouse
  Assignee: unassigned-b...@kde.org
  Reporter: sh...@sorbom.com
CC: unassigned-b...@kde.org
  Target Milestone: ---

Steps to reproduce:
1. Open kcm_mouse module
2. Under "General" tab, set "Button Order" to "Left Handed" via radio button
(which works)
3. Reboot/restart session, mouse is right handed again, but,
4. Opening kcm_mouse still shows that the radio button is set to "Left Handed"
5. Reset to "Left Handed" works until session restart or reboot. 

NOTE: this bug seems similar to #87226

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 395394] New: Kontact crashes in Kwin_wayland

2018-06-14 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=395394

Bug ID: 395394
   Summary: Kontact crashes in Kwin_wayland
   Product: kontact
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: sh...@sorbom.com
  Target Milestone: ---

Started kontact normally in kwin_wayland
terminal output:
Using Wayland-EGL
WebEngine compiled with X11 support, however qpa backend is not xcb. This may
fail.
[7504:7531:0614/132938.621037:ERROR:gl_surface_qt.cpp(230)] eglGetProcAddress
not found.
No text-to-speech plug-ins were found.
Using the 'xdg-shell-v6' shell integration
[7504:7531:0614/132939.874890:ERROR:gl_surface_qt.cpp(299)] Requested OpenGL
implementation is not supported. Implementation: 0
Received signal 11 SEGV_MAPERR 
#0 0x7fbb541a91cf 
#1 0x7fbb52bcce17 
#2 0x7fbb541a96de 
#3 0x7fbb630ad4b0 
#4 0x7fbb52c37e42 
#5 0x7fbb52c220e8 
#6 0x7fbb54c68a8d 
#7 0x7fbb56cdd927 
#8 0x7fbb56ce08f0 
#9 0x7fbb56cdbe16 
#10 0x7fbb56cd9adf 
#11 0x7fbb56cdb022 
#12 0x7fbb56cdcbbd 
#13 0x7fbb541a98d9 
#14 0x7fbb541cada0 
#15 0x7fbb541cb7fd 
#16 0x7fbb541cbae7 
#17 0x7fbb541c7679 
#18 0x7fbb541edbcf 
#19 0x7fbb5420f71f 
#20 0x7fbb5420ad80 
#21 0x7fbb5eed26ba start_thread
#22 0x7fbb6317f41d clone
  r8:   r9: 0001 r10: 0080 r11:

 r12: 7fbb097f8ad0 r13:  r14: 7fbac400afb0 r15:
7fbb097f8ce0
  di:   si:   bp: 7fbb097f8ab0  bx:
7fbac40165c0
  dx:   ax: 7fbb592aa138  cx: 7fbb097f88d0  sp:
7fbb097f88d0
  ip: 7fbb52c37e42 efl: 00010246 cgf: 002b0033 erf:
0004
 trp: 000e msk:  cr2: 
[end of stack trace]
Calling _exit(1). Core file will not be generated.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kopete] [Bug 393662] New: Kopete Crashes on Program exit

2018-04-29 Thread Shawn Sörbom
https://bugs.kde.org/show_bug.cgi?id=393662

Bug ID: 393662
   Summary: Kopete Crashes on Program exit
   Product: kopete
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kopete-bugs-n...@kde.org
  Reporter: sh...@sorbom.com
  Target Milestone: ---

Application: kopete (1.13.0)

Qt Version: 5.10.0
Frameworks Version: 5.45.0
Operating System: Linux 4.13.0-38-generic x86_64
Distribution: KDE neon User Edition 5.12

-- Information about the crash:
- What I was doing when the application crashed:
I was logged in to my XMPP and Google talk accounts. Iattempted to quit Kopete
from the address book window, which caused a segfault. 
I have tried this before.

-- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5a967c9940 (LWP 13062))]

Thread 5 (Thread 0x7f5a435e0700 (LWP 13105)):
#0  0x7f5a911d274d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5a89ec538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5a89ec549c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5a91b055cb in QEventDispatcherGlib::processEvents
(this=0x7f5a3c0204c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f5a91aac64a in QEventLoop::exec (this=this@entry=0x7f5a435dfbb0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f5a918cc554 in QThread::exec (this=this@entry=0x16d3cc0) at
thread/qthread.cpp:522
#6  0x7f5a6631cfc6 in XMPP::NetTrackerThread::run (this=0x16d3cc0) at
/workspace/build/protocols/jabber/libiris/src/irisnet/corelib/netinterface.cpp:168
#7  0x7f5a918d16eb in QThreadPrivate::start (arg=0x16d3cc0) at
thread/qthread_unix.cpp:376
#8  0x7f5a8bdb46ba in start_thread (arg=0x7f5a435e0700) at
pthread_create.c:333
#9  0x7f5a911de41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f5a60528700 (LWP 13097)):
#0  0x7f5a83182760 in __errno_location@plt () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#1  0x7f5a83192f6e in pa_read () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#2  0x7f5a89841a2e in pa_mainloop_prepare () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f5a898424a0 in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f5a89842560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f5a898507a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f5a831c1078 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#7  0x7f5a8bdb46ba in start_thread (arg=0x7f5a60528700) at
pthread_create.c:333
#8  0x7f5a911de41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f5a76dee700 (LWP 13065)):
#0  0x7f5a911d274d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5a89ec538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5a89ec549c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5a91b055cb in QEventDispatcherGlib::processEvents
(this=0x7f5a680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f5a91aac64a in QEventLoop::exec (this=this@entry=0x7f5a76dedc80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f5a918cc554 in QThread::exec (this=) at
thread/qthread.cpp:522
#6  0x7f5a918d16eb in QThreadPrivate::start (arg=0x107ac90) at
thread/qthread_unix.cpp:376
#7  0x7f5a8bdb46ba in start_thread (arg=0x7f5a76dee700) at
pthread_create.c:333
#8  0x7f5a911de41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f5a77fff700 (LWP 13064)):
#0  0x7f5a911d274d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5a89ec538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5a89ec549c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5a91b055cb in QEventDispatcherGlib::processEvents
(this=0x7f5a78c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f5a91aac64a in QEventLoop::exec (this=this@entry=0x7f5a77ffec50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f5a918cc554 in QThread::exec (this=) at
thread/qthread.cpp:522
#6  0x7f5a934922c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f5a918d16eb in QThreadPrivate::start (arg=0x7f5a93706d60) at
thread/qthread_unix.cpp:376
#8  0x7f5a8bdb46ba in start_thread (arg=0x7f5a77fff700) at
pthread_create.c:333
#9  0x7f5a911de41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f5a967c9940 (LWP 13062)):