The packages in -proposed work for me.
In Xenial muon 4:5.6.0-0ubuntu1.16.04.1
In Yakkety muon 4:5.6.0-0ubuntu1.16.10.1
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
I notice now that software-properties-kde is included in the kubuntu
desktop seed for both xenial and yakkety. Also included in the seed is
apturl-kde, which depends on s-p-k. Therefore, s-p-k should already be
there on a clean install. It may make sense to remove it before
installing proposed for
** Description changed:
- Muon 5.6.0-0ubuntu1
+ [Impact]
- Muon assumes that software-properties-kde is available and is using it
- to manage package sources (Settings -> Configure Software Sources).
+ It is not possible to edit software sources through Muon because
+ software-properties-kde
** Description changed:
- Driver manager shows only "Collecting information about your system". It
- happens when started from both"System setting" and console (kcmshell5
- kcm_driver_manager). The bug is similar to
- https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-
-
** Tags removed: ubuntu-sponsors
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to Kubuntu PPA.
https://bugs.launchpad.net/bugs/1530523
Title:
kcm_driver_manager: Infinitely shows Collecting information
To manage notifications about this
The fix (adding a recommends for apt-xapian-index) has been released for
yakkety in libqapt-3.0.2-0ubuntu3 but not for xenial.
I attach a debdiff of the same change, adapted to xenial.
** Patch added: "add recommends apt-xapian-index"
Is anybody still affected by this bug? This has been solved in apt-
xapian-index 0.47ubuntu8.3 available in xenial-updates.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to libqapt in Ubuntu.
https://bugs.launchpad.net/bugs/1530523
Title:
There are multiple problems:
* DriverManager emits signal in the constructor, so it fails and nobody notices.
* The qaptFailed signal is not connected (wouldn't be received anyway, see
above)
* message "Collecting information..." would have hidden any error message
See attachment
Now, when