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

shawnk...@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |shawnk...@gmail.com

--- Comment #11 from shawnk...@gmail.com ---
(In reply to Jonathan Chun from comment #9)
> Update. After going crazy and testing a bunch of stuff out, I wasn't able to
> figure out what the problem was because everything looked OK.
> 
> Then... it magically fixed itself after I started playing around with
> Python's libunity bindings/dbus/building my own electron app to see if I can
> reproduce it, I noticed the badge counters were working perfectly! Extremely
> confused, I went back and looked through to see where I went wrong(right?).
> 
> Turns out, you need to:
> sudo apt-get install libunity-dev
> 
> on Kubuntu/KDE Neon. I had previously thought that I might have been missing
> libunity on my system, so I did
> apt search libunity
> 
> This gave me a TON of results, a lot of which I already had installed such
> as libunity-protocol-private0, libunity-core-6.0-9, libunity9, so I
> mistakenly assumed I was OK on that front. Who would have guessed that
> libunity-dev is required as well... 
> 
> In any case, I've marked this resolved. There are still other issues with
> the unity launcher API only working with specifically named files and
> flatpak/snapstore/etc changing it and breaking compatibility, but thanks to
> all the effort I put into troubleshooting this, I think I have an idea of
> how to resolve that as well. 
> 
> Thank you for your patience Michail!
> 
> -----
> 
> One thing to consider. I don't know what the standard is for apt
> dependencies, but if a major feature like unity launcher API doesn't work
> without the libunity-dev package, perhaps it should either 1. be documented
> in FAQ, or 2. added to the package requirements?
> 
> Depends: plasma-desktop, plasma-pa, plasma-workspace (>= 4:5.9.0~), libc6
> (>= 2.14), libkf5activities5, libkf5archive5, libkf5configcore5,
> libkf5configgui5, libkf5coreaddons5, libkf5crash5, libkf5dbusaddons5,
> libkf5declarative5, libkf5globalaccel5, libkf5guiaddons5, libkf5i18n5,
> libkf5iconthemes5, libkf5newstuff5, libkf5notifications5, libkf5package5,
> libkf5plasma5, libkf5plasmaquick5, libkf5quickaddons5, libkf5service5,
> libkf5waylandclient5, libkf5windowsystem5, libkf5xmlgui5, libqt5core5a (>=
> 5.14.1+dfsg), libqt5dbus5 (>= 5.14.1+dfsg), libqt5gui5 (>= 5.14.1+dfsg),
> libqt5qml5 (>= 5.14.1), libqt5quick5 (>= 5.14.1), libqt5widgets5 (>=
> 5.14.1+dfsg), libqt5x11extras5, libstdc++6 (>= 5), libx11-6, libxcb-randr0,
> libxcb1

this problem still exists on Arch and installing libunity doesn't work any
more.

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

Reply via email to