[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.

2016-04-22 Thread João Pedro Sconetto via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353977

João Pedro Sconetto  changed:

   What|Removed |Added

 CC||sconetto.j...@gmail.com

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

[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.

2016-03-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353977

m...@eisgr.com changed:

   What|Removed |Added

 CC||m...@eisgr.com

--- Comment #9 from m...@eisgr.com ---
Still a problem in Kubuntu 15.10 (KDE 5.15.0/Qt 5.4.2)

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


[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.

2016-02-11 Thread Alexander Adam via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353977

Alexander Adam  changed:

   What|Removed |Added

 CC||bugs.kde.1...@antifarben.de

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


[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.

2016-01-19 Thread Judd West via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353977

Judd West  changed:

   What|Removed |Added

 CC||westjga...@live.com

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


[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.

2015-12-21 Thread David Edmundson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353977

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #7 from David Edmundson  ---
Bug in Qt. New releases should have fixes.

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


[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.

2015-12-21 Thread Jeff Trull via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353977

--- Comment #8 from Jeff Trull  ---
Would you mind posting that upstream bug report?  Would be nice to track it. 
Thanks!

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


[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.

2015-12-21 Thread Jeff Trull via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353977

Jeff Trull  changed:

   What|Removed |Added

 CC||jetr...@sbcglobal.net

--- Comment #6 from Jeff Trull  ---
I have this too, with similar stack trace.  Can we mark it "confirmed"?

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


[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.

2015-12-18 Thread Ian Proudler via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353977

Ian Proudler  changed:

   What|Removed |Added

 CC||i...@f2s.com

--- Comment #5 from Ian Proudler  ---
This may be related:

I have two monitors permanently connect. Recently (kubuntu 15.10) I have been
having problems where the main panel freezes. The icons are present but nothing
happens when you click on them. I have discovered that this can be rectified if
I disable one of the monitors and then re-enable it. In doing so krunner
crashes.

The KDE bug reporting app does not work. It will not let me select a related
bug. The saved back trace is:

Application: krunner (0.1)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-21-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:


-- Backtrace:
Application: krunner (krunner), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f455d8be800 (LWP 1736))]

Thread 3 (Thread 0x7f4549d17700 (LWP 1741)):
#0  0x7f455a3838dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4559875bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f455987774f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f454c061a39 in QXcbEventReader::run (this=0x1bbd6b0) at
qxcbconnection.cpp:1105
#4  0x7f455aa762be in QThreadPrivate::start (arg=0x1bbd6b0) at
thread/qthread_unix.cpp:337
#5  0x7f45585e26aa in start_thread (arg=0x7f4549d17700) at
pthread_create.c:333
#6  0x7f455a38eeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f453f69d700 (LWP 1763)):
#0  0x7f455a3838dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4557a631ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4557a632fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f455acad29b in QEventDispatcherGlib::processEvents
(this=0x7f45380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f455ac5375a in QEventLoop::exec (this=this@entry=0x7f453f69cda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f455aa713d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f455c878f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f455aa762be in QThreadPrivate::start (arg=0x1f1acc0) at
thread/qthread_unix.cpp:337
#8  0x7f45585e26aa in start_thread (arg=0x7f453f69d700) at
pthread_create.c:333
#9  0x7f455a38eeed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f455d8be800 (LWP 1736)):
[KCrash Handler]
#6  0x7f455a2bd267 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x7f455a2beeca in __GI_abort () at abort.c:89
#8  0x7f455a6e1b7d in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x7f455a6df9c6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x7f455a6dfa11 in std::terminate() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x7f455a6e055f in __cxa_pure_virtual () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x7f455af657ca in QPlatformScreen::physicalSize (this=)
at kernel/qplatformscreen.cpp:131
#13 0x7f455af9e212 in QScreen::physicalSize (this=this@entry=0x1bc09f0) at
kernel/qscreen.cpp:245
#14 0x7f455af9e2c9 in QScreen::physicalDotsPerInch (this=0x1bc09f0) at
kernel/qscreen.cpp:168
#15 0x7f455ce5db6b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#16 0x7f455ac8678a in QMetaObject::activate
(sender=sender@entry=0x7fff1bb0, signalOffset=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff1b998d00)
at kernel/qobject.cpp:3717
#17 0x7f455ac86f87 in QMetaObject::activate
(sender=sender@entry=0x7fff1bb0, m=m@entry=0x7f455b3b6580
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fff1b998d00) at kernel/qobject.cpp:3582
#18 0x7f455af7bdbf in QWindow::screenChanged
(this=this@entry=0x7fff1bb0, _t1=_t1@entry=0x1bc0020) at
.moc/moc_qwindow.cpp:626
#19 0x7f455af7ccb5 in QWindowPrivate::emitScreenChangedRecursion
(this=this@entry=0x1c0fee0, newScreen=newScreen@entry=0x1bc0020) at
kernel/qwindow.cpp:366
#20 0x7f455af7fcf3 in QWindowPrivate::setTopLevelScreen (this=0x1c0fee0,
newScreen=0x1bc0020, recreate=) at kernel/qwindow.cpp:387
#21 0x00407fe0 in ?? ()
#22 0x7f455ac86617 in QtPrivate::QSlotObjectBase::call (a=0x7fff1b998f50,
r=0x7fff1bb0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#23 QMetaObject::activate (sender=0x7fff1b40, signalOffset=,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff1b998f50)
at kernel/qobject.cpp:3702
#24 0x7f455ac86f87 in QMetaObject::activate 

[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.

2015-12-02 Thread Marcel Martin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353977

--- Comment #4 from Marcel Martin  ---
My C++ foo is limited, but I believe this is the relevant part of the
backtrace:

#10 0x7f53b3e02f31 in std::terminate() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x7f53b3e03a7f in __cxa_pure_virtual () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x7f53b46ce96a in QPlatformScreen::physicalSize (this=)
at kernel/qplatformscreen.cpp:131 
#13 0x7f53b47087b2 in QScreen::physicalSize (this=this@entry=0x26bd450) at
kernel/qscreen.cpp:245
#14 0x7f53b4708869 in QScreen::physicalDotsPerInch (this=0x26bd450) at
kernel/qscreen.cpp:168
#15 0x7f53b8d97c49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#16 0x7f53b43c59c9 in QMetaObject::activate (sender=sender@entry=0x289a100,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffcd4ccd7d0) at kernel/qobject.cpp:3716 

and 

#27 0x7f53b4708679 in QScreen::~QScreen (this=0x26bd450,
__in_chrg=) at kernel/qscreen.cpp:77
#28 0x7f53b46cef2a in QPlatformScreen::~QPlatformScreen (this=0x26bd1f0,
__in_chrg=) at kernel/qplatformscreen.cpp:57
#29 0x7f53a6cde769 in QXcbScreen::~QXcbScreen (this=0x26bd1f0,
__in_chrg=) at qxcbscreen.cpp:222 

QPlatformScreen::physicalSize is a pure virtual function. __cxa_pure_virtual is
an error handler that gets called when a pure virtual function is called. I
think this is what happens:

- QXcbScreen destructor is called (#29)
- which in turn calls QScreen destructor (#28)
- which in turn calls QPlatformScreen destructor (#27)
- which somehow triggers that a signal is emitted
- that signal then ends up being received by the QXcbScreen instance, which is
already destroyed

This could also explain the question marks in frame #15.

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