<table><tr><td style="">kossebau added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D11366">View Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D11366#226774" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D11366#226774</a>, <a href="https://phabricator.kde.org/p/mtijink/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@mtijink</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>Are you sure this is needed? It appears to transfer CanPause etc. just fine when I start an MPRIS player, without the patch.</p></div>
</blockquote>
<p>From the debug logs I looked at, I would still think this is needed. Even if it seems just one of a few issues which might need fixing.</p>
<p>While most players will change some of the properties after having been started, thus trigger the update signal, they do not need to do. Or if the KDE Connect MPRIS plugin is activated if the player is already running, then there might be even less state changes with related propertychanged signals coming in.</p>
<p>I left a qDebug() log in the updated (no longer crashing patch) which should show what I mean.</p>
<p>There also seems another issue which can be seen by that log: when closing and then starting a player again, there will be multiple invocations of <tt style="background: #ebebeb; font-size: 13px;">MprisControlPlugin::propertiesChanged(...)</tt>, as many times as the player had been restarted. Possibly the <tt style="background: #ebebeb; font-size: 13px;">OrgFreedesktopDBusPropertiesInterface</tt> & <tt style="background: #ebebeb; font-size: 13px;">OrgMprisMediaPlayer2PlayerInterface</tt> instances need some manual cleanup if a service disappears, otherwise they pile up for the same service name. But would be an orthogonal issue to the problem I am looking at.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Do I need the git-master gwenview to reproduce the issue?</p></blockquote>
<p>Yes, from as latest master as possible, <a href="https://phabricator.kde.org/D10972" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: line-through;">D10972</a>, which brought the MPRIS stuff to gwenview, only landed a day ago.</p>
<p>It seems that the set of MPRIS data used is resulting in unexpected states with the Android KDE Connect media payer remote control plugin. Which then shows almost no buttons for the actions.<br />
Sadly I have never done Android code, so cannot tell what could be wrong or even try to come up with patches. I just can tell that the Plasma media controller plugin works perfectly with Gwenview, so my initial working theory is that the issues are not in Gwenview :)</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><blockquote style="border-left: 3px solid #8C98B8;
color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D11366#226760" style="background-color: #e7e7e7;
border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;">D11366#226760</a>, <a href="https://phabricator.kde.org/p/kossebau/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;">@kossebau</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><p>Actually not yet completly tested, currently fighting to get my custom kdeconnect-kde build running. Seems installs of D-Bus service files into custom folders hides them from dbus server, despite being in XDG* var paths, so kdeconnectd is not started. Any hints how to solve that?</p></div>
</blockquote>
<p>You can start <tt style="background: #ebebeb; font-size: 13px;">kdeconnectd</tt> manually (located in <tt style="background: #ebebeb; font-size: 13px;">build/daemon</tt>). Not sure how it picks up plugins etc. in that case though.</p></blockquote>
<p>Thanks. Turned to something similar meanwhile, starting the custom installed one manually in a shell, also to get all debug log there.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R224 KDE Connect</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D11366">https://phabricator.kde.org/D11366</a></div></div><br /><div><strong>To: </strong>kossebau, KDE Connect<br /><strong>Cc: </strong>mtijink<br /></div>