[kate] [Bug 359032] kate crash when quitting because of a DBus request when a file dialog is open

[Christoph Cullmann via KDE Bugzilla]

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

Christoph Cullmann  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Christoph Cullmann  ---
>  I don't disagree. Until there grows some widespread habit of using DBus 
> calls programmatically, maybe?
=> Yeah, if that ever happens, perhaps, but for editing automation one more
should write the javascripts we support.

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

[kate] [Bug 359032] kate crash when quitting because of a DBus request when a file dialog is open

[RJVB via KDE Bugzilla]

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

--- Comment #5 from RJVB  ---
(In reply to Christoph Cullmann from comment #3)

> That makes no sense for me and I rather have such crashs than uglifying all
> our code base for no real reason. (if users script stuff via dbus + do GUI
> interactions during that scripts are running, they are doomed)

I don't disagree. Until there grows some widespread habit of using DBus calls
programmatically, maybe?

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

[kate] [Bug 359032] kate crash when quitting because of a DBus request when a file dialog is open

[RJVB via KDE Bugzilla]

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

RJVB  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|WONTFIX |---

--- Comment #4 from RJVB  ---
Answering my own question:

Application: kate (16.08.0)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.5.7-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.5 LTS

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9e4e6ef780 (LWP 22409))]

Thread 3 (Thread 0x7f9e3ad78700 (LWP 22410)):
#0  0x7f9e49203fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f9e45e61b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f9e45e6364f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f9e3e1fcb09 in QXcbEventReader::run (this=0xad1780) at
/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1325
#4  0x7f9e49bb8c99 in QThreadPrivate::start (arg=0xad1780) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/thread/qthread_unix.cpp:341
#5  0x7f9e45a3f184 in start_thread (arg=0x7f9e3ad78700) at
pthread_create.c:312
#6  0x7f9e4921137d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f9e2d363700 (LWP 22411)):
#0  0x7f9e49203fdd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f9e45526fe4 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7f9e280013c0, timeout=-1, context=0x7f9e28000990) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:4028
#2  g_main_context_iterate (context=context@entry=0x7f9e28000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3729
#3  0x7f9e455270ec in g_main_context_iteration (context=0x7f9e28000990,
may_block=may_block@entry=1) at
/build/buildd/glib2.0-2.40.2/./glib/gmain.c:3795
#4  0x7f9e49dd462b in QEventDispatcherGlib::processEvents
(this=0x7f9e280008c0, flags=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:419
#5  0x7f9e49d7e56a in QEventLoop::exec (this=this@entry=0x7f9e2d362e20,
flags=..., flags@entry=...) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/kernel/qeventloop.cpp:204
#6  0x7f9e49bb3f8b in QThread::exec (this=this@entry=0x7f9e4a45c400
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/thread/qthread.cpp:500
#7  0x7f9e4a1eb605 in QDBusConnectionManager::run (this=0x7f9e4a45c400
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/macports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/dbus/qdbusconnection.cpp:189
#8  0x7f9e49bb8c99 in QThreadPrivate::start (arg=0x7f9e4a45c400 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/thread/qthread_unix.cpp:341
#9  0x7f9e45a3f184 in start_thread (arg=0x7f9e2d363700) at
pthread_create.c:312
#10 0x7f9e4921137d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f9e4e6ef780 (LWP 22409)):
[KCrash Handler]
#6  0x0a41 in ?? ()
#7  0x7f9e49db4717 in cleanup (pointer=) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/include/QtCore/../../src/corelib/tools/qscopedpointer.h:54
#8  ~QScopedPointer (this=0x1a27588, __in_chrg=) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/include/QtCore/../../src/corelib/tools/qscopedpointer.h:101
#9  QObject::~QObject (this=, __in_chrg=) at
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.6.1/qtbase/src/corelib/kernel/qobject.cpp:893
#10 0x7f9e49db4849 in QObject::~QObject (this=0x1a27580,
__in_chrg=) at

[kate] [Bug 359032] kate crash when quitting because of a DBus request when a file dialog is open

[Christoph Cullmann via KDE Bugzilla]

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

Christoph Cullmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Christoph Cullmann  ---
Yes, it will still random crash thought we only use:

const QList urls = QFileDialog::getOpenFileUrls(m_mainWindow, i18n("Open
File"), cv->document()->url());

We would need really to guard all things on the stack for the current function,
here we are in a view manager member and Co.

That makes no sense for me and I rather have such crashs than uglifying all our
code base for no real reason. (if users script stuff via dbus + do GUI
interactions during that scripts are running, they are doomed)

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

[kate] [Bug 359032] kate crash when quitting because of a DBus request when a file dialog is open

[RJVB via KDE Bugzilla]

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

--- Comment #2 from RJVB  ---
Have you checked if this still works with the current code?

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

[kate] [Bug 359032] kate crash when quitting because of a DBus request when a file dialog is open

[Christoph Cullmann via KDE Bugzilla]

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

Christoph Cullmann  changed:

   What|Removed |Added

 CC||cullm...@kde.org

--- Comment #1 from Christoph Cullmann  ---
Actually, that blog is nice, but I don't really see how this is easily fixable.
If we get at some point such a dbus call, we would need to ensure we check for
all things on the stack to be still ok, e.g. is the view manager still there
and so on. See no real value in trying to fix that, actually.

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