Summary: | Externally-opened files no longer open in existing window | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Nate Graham <nate> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bugs.kde.org, charles.gorand.dev, christoph, thomas, zmogas |
Priority: | NOR | ||
Version: | Git | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/kate/636af882e3c936411f56069585940901b39628d1 | Version Fixed In: | |
Sentry Crash Report: |
Description
Nate Graham
2019-08-08 20:33:33 UTC
Hmm, true, happens for me now, too. That means // application dbus interface if (QDBusConnection::sessionBus().interface()) { QDBusConnection::sessionBus().registerObject(QStringLiteral("/MainApplication"), this); } fails now and we have no dbus communication anymore :/ Git commit bf54ad697f3d8380bf9871cb73e928479b9476fb by Christoph Cullmann. Committed on 09/08/2019 at 19:19. Pushed by cullmann into branch 'master'. fix dbus session registration M +0 -5 kate/kateapp.cpp M +7 -1 kate/kateappadaptor.cpp https://commits.kde.org/kate/bf54ad697f3d8380bf9871cb73e928479b9476fb Please test this, this should perhaps be backported. Fixed for me! +1 for backporting to stable branch. Might even be worth a re-spin so we don't ship Kate 19.04 like this. Git commit 636af882e3c936411f56069585940901b39628d1 by Christoph Cullmann. Committed on 09/08/2019 at 19:24. Pushed by cullmann into branch 'Applications/19.08'. fix dbus session registration M +0 -5 kate/kateapp.cpp M +7 -1 kate/kateappadaptor.cpp https://commits.kde.org/kate/636af882e3c936411f56069585940901b39628d1 Backported to 19.08, should I do that for 19.04, too? I am actually not sure why it no longer works, perhaps Qt 5.13 bug/regression or now correct behavior? Er, yes, 19.08. :) 19.04 is not getting any new releases. *** Bug 412288 has been marked as a duplicate of this bug. *** *** Bug 375795 has been marked as a duplicate of this bug. *** I retagged Bug #375795 as a duplicate, although it's technically this one, that's a duplicate. I hope that is OK? *** Bug 415099 has been marked as a duplicate of this bug. *** |