[Discover] [Bug 392737] Ability to use discover with LXQt

[Nate Graham]

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

--- Comment #4 from Nate Graham  ---
And looks like it's been fixed in Debian already!

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

[Discover] [Bug 392737] Ability to use discover with LXQt

[Aleix Pol]

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

--- Comment #3 from Aleix Pol  ---
Your bug report made me realise we were including unnecessary stuff, should be
included in the next discover 5.12 release.

https://commits.kde.org/discover/938da4ecc3261bc3bfd0e51891a09f9f117a2c5c

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

[Discover] [Bug 392737] Ability to use discover with LXQt

[robert]

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

--- Comment #2 from robert  ---
Thank you Nate, opened this bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894857

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

[Discover] [Bug 392737] Ability to use discover with LXQt

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 CC||n...@kde.org
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Nate Graham  ---
Yes, Discover should definitely work in other desktop environments. However,
what you describe is a packaging issue in Debian; packages that are required
aren't getting installed by default, boo! This is probably masked by the fact
that the missing packages are always installed for other reasons in a KDE
Plasma environment, so nobody noticed that the Discover packaging wasn't
marking them as dependencies correctly. Please report this downstream to the
Debian folks. Thanks for the bug report!

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