https://bugs.kde.org/show_bug.cgi?id=366596
Gleb Popov <6year...@gmail.com> changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #28 from Gleb Popov <6year...@gmail.com> ---
This seems to be not relevant anymore. I don't see any hangup dbus processes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #27 from arrowdodger <6year...@gmail.com> ---
Not sure if this is relevant, but here are my findings
I **removed** all dbus files except dbus.dll and launched konversation. Upon
exit it hanged on QDBusServiceWatcher destructor.
Qt5C
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #26 from Albert Vaca ---
(In reply to Hannah von Reth from comment #24)
> - Running several versions of dbus should not cause an issue as dbus is
> configured to operate depending on its root directory.
DBus activation won't find the .servi
https://bugs.kde.org/show_bug.cgi?id=366596
Kåre Särs changed:
What|Removed |Added
CC||kare.s...@iki.fi
--- Comment #25 from Kåre Särs --
https://bugs.kde.org/show_bug.cgi?id=366596
Hannah von Reth changed:
What|Removed |Added
CC||vonr...@kde.org
--- Comment #24 from Hannah v
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #23 from Albert Vaca ---
Running several dbus daemons will certainly cause problems and avoiding that is
one of the challenges we will have to face. I personally think we should share
certain components (like dbus and Qt) across apps. But th
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #22 from arrowdodger <6year...@gmail.com> ---
>From what I know, the current course for KDE Apps on Windows is to have a
separate installer for each App. This means that each app would have its own
D-Bus stuff packaged in.
I'm concerned of h
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #21 from Jasem Mutlaq ---
DBus is already working under Windows and I tested it just fine with KStars, so
why change anything? There are a couple of areas where it not having DBus would
break functionality: Script Builder and Ekos Scheduler.
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #20 from Kevin Funk ---
> Your plan is to drop DBus? IMHO, DBus is not an annoying dependency that we
> want to get rid of, is a useful tool for inter-proc communication.
... iff your application *depends* on having multiple processes arou
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #19 from Jasem Mutlaq ---
Please do NOT drop DBus! KStars heavily relies of DBus for many things to work.
If DBus is gone, we might as well not release for Windows/OSX altogether as it
is not worth the effort.
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #18 from Albert Vaca ---
Your plan is to drop DBus? IMHO, DBus is not an annoying dependency that we
want to get rid of, is a useful tool for inter-proc communication.
Mac and Windows have their own inter-proc communication mechanisms. Idea
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #17 from arrowdodger <6year...@gmail.com> ---
Since this problem is present on Windows only, I'd rather continue with this
plan: https://www.mail-archive.com/kde-frameworks-devel@kde.org/msg34246.html
Actually I have it on my TODO already, j
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #16 from Albert Vaca ---
In one of the bugs I linked before [1] David Faure mentions asking Thiago about
it, to fix it in Qt. I don't know if there was any further conversation or an
open bug in Qt, though, because I didn't find it.
[1] htt
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #15 from Kevin Funk ---
FYI: I stopped working on this issue because I don't fully understand why we
get that hang on exit => thus don't know how to fix it properly either. Not
even sure at what level to fix (Qt or KF5).
The patches I poste
https://bugs.kde.org/show_bug.cgi?id=366596
Albert Vaca changed:
What|Removed |Added
CC||albertv...@gmail.com,
|
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #13 from Jasem Mutlaq ---
Git commit f38ff7cb890193cba6bcf8c50d48c7c9c22bd542 by Jasem Mutlaq.
Committed on 24/11/2016 at 17:55.
Pushed by mutlaqja into branch 'master'.
Temporary hack to solve kstars.exe remaining in the background due to
https://bugs.kde.org/show_bug.cgi?id=366596
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #12 from Jasem Mutlaq ---
I just emerged with Qt 5.8 and the bug is still there!! I first tried to emerge
KStars and upon exist, kstars.exe still remains in the background. Then I
emerged kate, and the exact same problem!
I thought this was
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #11 from Mateusz Mikuła ---
Apps freeze even with those 4 patches.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #10 from Sven Brauch ---
Well, you can apply the 4 patches listed above, then it works. Regarding
upstreaming them, I have no clue, sorry.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366596
arrowdodger <6year...@gmail.com> changed:
What|Removed |Added
CC||6year...@gmail.com
--
You ar
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #9 from Jasem Mutlaq ---
well, any updates on this topic? We released a Windows version of KStars and
users are complaining about this issue, the Windows port reception is critical
but this bug is one of the many show stoppers.
Is there any
https://bugs.kde.org/show_bug.cgi?id=366596
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #8 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #7 from Jasem Mutlaq ---
I just tested today and the issue is still there. So what's the plan here? Is
this intended to be fixed in Qt or KDE or what?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #6 from Kevin Funk ---
@Mateusz: I have another patch for kiconthemes which solves a similar
hang-on-exit. Please stay tuned, I'll upstream the patch asap.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #5 from Mateusz Mikuła ---
Hi,
Kevin Funk maybe it's not related to KDE since I'm trying to "integrate" KDE
with MSYS2 (could bebug with Qt, MinGW or whateber else).
I'm getting deadlock at return in every app that calls "KIconLoader::global
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #4 from Kevin Funk ---
Also:
https://phabricator.kde.org/D2546
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #3 from Kevin Funk ---
Related patches:
https://phabricator.kde.org/D1909
https://phabricator.kde.org/D2142
https://phabricator.kde.org/D2545
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366596
Kevin Funk changed:
What|Removed |Added
CC||kf...@kde.org
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=366596
Mateusz Mikuła changed:
What|Removed |Added
CC||mati...@gmail.com
--- Comment #1 from Mateusz
31 matches
Mail list logo