[lug] D-bus/KDE Debugging (was Tracing Permission Problems)

[Davide Del Vento]

Now that I think about it, I remember seeing this bug (white tooltips)
in one of the several tests that I did after Gnome 3 came out. I think
I saw it OpenOffice (back then not yet forked from LibreOffice) but
don't remember more details. I am sure it wasn't Fedora. So, if you
know OpenOffice used D-bus, I suggest reporting the bug to D-bus.

Otherwise, even if it's D-bus issue, reporting it to Fedora can still
help, since they may implement a workaround like you did. I'd not
suggest reporting it to both places, unless the D-bus maintainer in
Fedora closes the bug telling you to do so.

Cheers,
Davide

On Sun, Dec 13, 2015 at 1:51 PM,  <stimits at comcast.net> wrote:
> It looks like there is a bug which is probably D-bus or its configuration on
> Fedora 23 itself. However, I'm not sure if I report this as a Fedora 23 bug
> or a D-bus bug.
>
> It turns out that under KDE spin of Fedora 23 there are many applications
> (such as gimp, inkscape, and kicad) which all fail with unset tool tip text
> color during mouse hover-over...these all display white text on white
> background, but all work correctly if I first su to myself or sudo as myself
> (or any other user). Looking at the dbus-monitor I can see things like
> failure to check "~/.local/share/applications/kicad.desktop" for non-sudo
> failed tool tip text, along with a lot of other irrelevant checks which just
> don't even occur if I first su to myself (like http and completely
> irrelevant strings when starting the app without sudo). The failed logs are
> large in comparison with a very short dbus-monitor log for the working
> version.
>
> So my question is this...for reporting purposes is it a Fedora 23 bug for
> configuration scripts which are not part of D-bus? Or is it a D-bus problem?
> Or do I report it as a bug to both Fedora and D-bus? It just seems like its
> a good way to get the bug ignored, but learning new applications is mostly
> pointless without the help text. My workaround is going through the KDE
> menus and editing to run everything with symptoms as sudo myself...that's a
> pretty bad workaround.
>
> Thanks!
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety