kcm_driver_manager: Infinitely shows Collecting information

[john safix]

[Impact]

* libQapt needs apt-xapian-index in order to search for packages, otherwise it never returns a result.
* As a consequence Driver Manager doesn't find packages and is empty.
* Before, apt-xapian-index was installed as a dependence of Muon (libmuon), which is not included in the default install anymore.

[Test Case]

* Update libqapt and run `kcmshell5 kcm_driver_manager`.
* After some time (~1 minute) Driver Manager shows suggested packages.

[Regression Potential]

* Low, Driver Manager is useless as of now.
* The same fix was applied in Yakkety.

[Philip Muškovac (yofel)]

Thanks for taking your time to report this bug and helping to make Ubuntu better. Someone else also reported this on IRC, we'll look into it.

[Charles V. Wright (charles-v-wright)]

same @hear ,,,just confirming it affects some one else

Kubuntu-16.04 -mar-19/daily.ISO

plasma-5.5.4

Qt-5.5.1

KDE Frameworks 5.18.0

Kernel-4.4.0.15-genaric

kubuntu-driver-manager -15.10ubuntu3

Ubuntu-drivers on the CLI works as expected

VINNY

[Clay Weber (claydoh)]

If it helps debugging,, running kcmshell5 kcm_driver_manager
only shows the message "No frame loaded"

[Rohan Garg (rohangarg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1530523

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[lnxusr (bjwest)]

 Production was released yesterday, and this bug is still present.

[Marcus Zuber (marcus-zuber)]

ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2014-08-17 (614 days ago)
InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Package: kubuntu-driver-manager 15.10ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Tags: xenial
UbuntuDriversList:
 == cpu-microcode.py ==
 driver : amd64-microcode - distro non-free
Uname: Linux 4.4.0-21-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev roccat sambashare sudo
_MarkForUpload: True

[Marcus Zuber (marcus-zuber)]

apport information

[Marcus Zuber (marcus-zuber)]

apport information

[Marcus Zuber (marcus-zuber)]

apport information

[Marcus Zuber (marcus-zuber)]

apport information

[Josh (jgvidals)]

Is there any update on this? I'm having some graphical issues and need the nvidia driver up.

[Stephen Stewart (s-g-stewart1)]

Same, have graphics issues now in 16.04 that I never had in 15.10. Because this doesn't work I can't install all of Intels microcode to fix the issues.

[Ashley Gaterell (ash-gaterell)]

Just installed Kubuntu 16.04, I am also getting this issue. Let me know if you require any information.

[John H Ring IV (johnhringiv)]

For those needing an immediate workaround note that the CLI version is fully functional. (I used it to install Intel microcode and nvidia drivers). The name of the CLI program is ubuntu-drivers for those that don't know.

[Nikola Snele (n-schnelle)]

Guys you can install drivers/microcode from muon package manager or with apt-get.

Install muon and then search for microcode/nvidia and install needed packages.

[Rick Timmis (rick-timmis)]

Investigations into the problem reveal that kcmshell5 appears to be waiting for qapt..

<ubottu> bug 1530523 in kubuntu-driver-manager (Ubuntu) "kcm_driver_manager: Infinitely shows Collecting information" [High,Incomplete] https://launchpad.net/bugs/1530523
[21:28] <sick_rimmit> Oh ah right
[21:30] <sick_rimmit> Can you reproduce it on your machine ?
[21:30] <sick_rimmit> I am on 15.10 here right now
[21:30] <clivejo> yes
[21:31] <sick_rimmit> OK..
[21:31] <clivejo> I think it does same on 15.10
[21:31] <clivejo> can you try?
[21:31] <sick_rimmit> Nope works for me
[21:31] <clivejo> hummm
[21:31] <clivejo> so whats changed!
[21:31] <sick_rimmit> try calling it from the command line, see what output you get
[21:32] <clivejo> nothing
[21:32] <sick_rimmit> hmmm
[21:32] <sick_rimmit> did your new builds of libqapt make it into Xenial, the one for muon ?
[21:32] [Notice] -kubuntu-ci to #kubuntu-devel- Project wily_unstable_parley build #142: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/wily_unstable_parley/142/
[21:32] <clivejo> yes
[21:32] <sick_rimmit> hmmm not that then
[21:32] <sick_rimmit> Odds are that kcm is using libqapt in a similar way to muon
[21:33] <sick_rimmit> try calling it again but this time with strace
[21:33] <sick_rimmit> strace kcm-manager or whatever its called
[21:33] <clivejo> the only change to libqapt was to make it emmit signals
[21:33] <sick_rimmit> that would fit the frame
[21:33] <sick_rimmit> I mean the previous version
[21:34] <sick_rimmit> where it didn't emit them
[21:34] <clivejo> thats why muon was crashing
[21:34] <sick_rimmit> If kcm has a slot awaiting a signal then et voila! stuck code
[21:34] <sick_rimmit> ok don;t worry too much about that
[21:34] <sick_rimmit> can you get strace to run kcm
[21:34] <-- Maxiride_ (~Maxiride@178.162.211.232) has left this server (Quit: Konversation terminated!).
[21:35] [Notice] -kubuntu-ci to #kubuntu-devel- Project wily_unstable_kactivities build #190: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/wily_unstable_kactivities/190/
[21:37] <clivejo> it runs and gets stuck
[21:37] <clivejo> strace keeps displaying this over and over
[21:37] <clivejo> http://paste.ubuntu.com/16088409/
[21:39] * sick_rimmit grabs monacle
[21:40] --> Blizzz (~blizzz@ubuntu/member/blizzz) has joined this channel.
[21:40] <sick_rimmit> If you sit for a few seconds hands off machine does it continue output
[21:41] <clivejo> yes
[21:41] <sick_rimmit> strace is a Stack trace utility so it picks up mouse, kdb, everything really
[21:41] <clivejo> just sits there doing that
[21:41] <clivejo> until I close the window
[21:41] <sick_rimmit> Ok so it is stuck in a loop doing something
[21:42] <sick_rimmit> question is what ?
[21:42] <sick_rimmit> so run it again without strace then ps uax to find its process id
[21:42] <clivejo> was hoping you could answer that
[21:42] <sick_rimmit> then lets try lsof
[21:42] * sick_rimmit needs man pages
[21:43] <sick_rimmit> ah yes
[21:44] <sick_rimmit> lsof -p <pid>
[21:44] <sick_rimmit> that will tell us what it is doing
[21:45] <-- SilentGh1 (~SilentGho@unaffiliated/silentghost) has left this server (Ping timeout: 246 seconds).
[21:45] <-- adrian (~adria...

[Rick Timmis (rick-timmis)]

In 16.04 lsof shows kcmshell5 stopped at /tmp/qapt-sock-blah...blah

where as in the working version on 15.10 it passes that and drops out of process with

kcmshell5 5100 ricktimmis 59u unix 0x00000000 0t0 82414 /tmp/qapt-sock-6b32908485534dfc9082102650209275
kcmshell5 5100 ricktimmis 60u 0000 0,11 0 8236 anon_inod

Hope this helps pointing in the right direction

[YAFU (yafu)]

Why does this is marked as "incomplete" and still not have anyone assigned?
Dude, this is important. What other information do you need to try to fix this?

[Rohan Garg (rohangarg)]

I did a bit of debugging with clivejo on IRC and it /seems/ to me that this is a qapt issue, or how qapt gets setup via the Driver Manager. I've asked clivejo to co-ordinate with the QApt maintainer.

[YAFU (yafu)]

Thank you. If you need us to do tests or some system information, you just ask here please.

[Val (pubalapoub)]

Thanks for the information Rick, I'm posting here part of what strace displays about 'kcmshell5 kcm_driver_manager', as <clivejo> did, but this part may be the most interesting one:

http://paste.ubuntu.com/16256627/

Notes:
- The missing "file or directory" at the beginning is just here to help developers locate kcm_driver_manager's activity/progress.
- Everything occurring afterwards that I didn't paste is very similar to the last few visible lines.

Hope this helps a bit.

[Carlo Vanini (silhusk)]

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 it's stuck "Collecting information" try to run:
systemctl status dbus
if you see anything like
Activated service 'org.debian.AptXapianIndex' failed: Launch helper exited with unknown return code 1
then it's Bug #1579834

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "fix signals for backend failure reporting" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Francesc Vicent (fransex)]

Before applying Carlo's patch but with update-apt-xapian-index-dbus corrected according to Bug #1579834 this is what I get from 'systemctl status dbus':

dbus[958]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.66" (uid=0 pid=2152 comm="/usr/bin/python3 /usr/share/apt-xapian-index/updat") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.254" (uid=1001 pid=29622 comm="/usr/bin/systemsettings5 ")

[yossarian_uk (morgancoxuk)]

This seems to have returned in 16.04 (with ubuntu-graphics package installed)

[Francesc Vicent (fransex)]

That's when it started to appear, as per its description.

[Feathercoin (wrapperband)]

I have "upgraded" to 16.04 and am suffering this bug, it is urgent and critical.

[syrtis (slyphere)]

Hello, I solved this problem by rebuilding the "Xapian index" using:

sudo update-apt-xapian-index

Now the Driver Management works again.

[Rafael Jesus Alcantara Perez (rafa-dedaloingenieros)]

I've done the same that #28 and now it detects my devices. Thanks.

[DaytonaJohn (daytonajra)]

#28 worked for me, also!!!

[dj_segfault (djsegfault)]

#28 worked for me too. Thank you syrtis

[Nick B. (futurepilot)]

Confirming, sudo update-apt-xapian-index works

On Thursday, June 30, 2016 2:45:55 PM EDT syrtis wrote:
> Hello, I solved this problem by rebuilding the "Xapian index" using:
>
> sudo update-apt-xapian-index
>
> Now the Driver Management works again.

[cooloutac (cooloutac)]

I tired that command but it says command not found on my system. Using latest kubuntu iso installed today.

[Kyle Gottfried (spitfire1900)]

Can also confirm #28 worked for me.

[Kyle Gottfried (spitfire1900)]

The command update-apt-xapian-index is available from the apt-xandian-index package.

[Philip Muškovac (yofel)]

Thanks a lot for figuring this out. That apt-xapian-index vanished from the image went unnoticed for 16.04. I added it back for yakkety just now so we can check if this works on tomorrow's live image.

[Launchpad Janitor (janitor)]

This bug was fixed in the package libqapt - 3.0.2-0ubuntu3

---------------
libqapt (3.0.2-0ubuntu3) yakkety; urgency=medium

  * libqapt3 should recommend apt-xapian-index for the package index
    access which is required for most operations (LP: #1530523)

 -- Philip Muškovac <email address hidden> Wed, 06 Jul 2016 09:43:26 +0000

[Val (pubalapoub)]

I confirm syrtis' solution solves the issue, however it seems to be temporary, as I got into the issue again some time after. Could it be linked to the installation of packages AFTER having run 'update-apt-xapian-index' (what I did)? Meaning 'update-apt-xapian-index' should be re-executed after each package install?

[DaytonaJohn (daytonajra)]

I just did some updates and noticed that I am back to the hung driver manager. As pubalapoub says, rerunning the update-apt-xapian-index fixes it again.

[shaikailash (steve-doc-brown)]

Hello. I just installed Kubuntu 16.04 and I have the same problem. That's quite bad since drivers are necessary to run wifi card and graphic card.
The command "sudo update-apt-xapian-index" is not found.
Thanks.

[Val (pubalapoub)]

@Shaikailash: the command line equivalent is to run "ubuntu-drivers devices" in a terminal.
Wait for a few seconds and you'll get a list of proposed drivers. Then install the package of your choice (could be 'nvidia-361' for e.g.).

[Kyle Gottfried (spitfire1900)]

Also, @Shaikailash, see comment 35: https://bugs.launchpad.net/ubuntu/+source/libqapt/+bug/1530523/comments/35

[Marco Dalla Libera (marco-dallas95)]

The bug is still present at this time in Kubuntu 16.04.1.
To fix it I had to enter the command in comment #35

[Flamewart (mojinopocoescozio)]

The bug is still present at Kubuntu 16.04.1

I tried what #28 proposed but didn't work, says "command not found". I leave the Konsole open for a minute and still no list appears as stated by #41

[Carlo Vanini (silhusk)]

Is anybody still affected by this bug? This has been solved in apt-xapian-index 0.47ubuntu8.3 available in xenial-updates.

[tgm1024 (tgm1024)]

Hi, I am experiencing this problem on a fresh install of Kubuntu 16.04/32bit x86 on an ancient Dell Vostro. Device manager simply hangs. Plugged in via cat5.

However, while I certainly had quite a bit of unix programming experience in the 80's and 90's {coughs, puts teeth in a glass, and takes a moment to yell "get off my lawn"}, I'm a noob at Linux and slowly inching my way into this apt-get mumblemumble business.

Can you tell me how to install the xenial-updates for Kubuntu (which I assume gets me the xapian packages?

Just blast out a few commandlines for me if you have a sec.

Thanks!

[Sami Nieminen (razerdog)]

I just installed fresh 16.04.1, fully upgraded it but still had to install apt-xapian-index and run update-apt-xapian-index.

I have xenial-updates-enabled. There is missing dependency on driver manager for apt-xapian-index and it seems to be mandatory to have.

[Thorsten Rochelmeyer (thorsten-1)]

It's still there. Kubuntu 16.04, all packages up to date.

[Roy Walmsley (roy-walmsley)]

Also confirming the bug is still present. Just installed a clean Kubuntu 16.04 system, fully updated. Tried to run the update-apt-xapian-index, which reported it not there. So had to install first, reboot, then run update. Now, driver manager works.

I'm surprised this bug is still present. It was reported right at the beginning of the year.

[Peter R (forums-oygle)]

Also confirming the bug is still present. Installed a clean Kubuntu 16.04.1 system, fully updated.

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

Copying over from bug 1643715 (which is not a dupe, but contained that helpful hint) comment #6

Well let's look at these the responsible package:

http://packages.ubuntu.com/xenial/kubuntu-driver-manager

http://packages.ubuntu.com/yakkety/kubuntu-driver-manager

It should jump into the eyes then... ('apt-x-i' missing in xenial)

Also interesting to see this comparision

http://packages.ubuntu.com/xenial-updates/libqapt3

http://packages.ubuntu.com/yakkety/libqapt3

The latter has 'apt-xapian-index' as "recommends"

Hoping this little reseach helps to get this going. ;-)

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

Also pointing at ->
bug 1612392 [sru] Muon: missing dependency on software-properties-kde

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

Um hold up. Correct me if I'm wrong, but I see that in BOTH cases, the yakkety version is a higher version number than xenial???????? How does that happen?

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

@ wxl: Well, than it needs to be added in BOTH cases. – Version no. in Yakkety is higher because of a change. Check back wt packaging-Ninjas (black belts) or look at the changelog.

[JPT (j-p-t)]

I've got this problem too, Xapian doesn't seem to be the cause.
Workaround that works for me is: 'start /usr/bin/kcmshell5 kcm_driver_manager' then run 'ubuntu-drivers list'
The driver list will appear in the kcm_driver_manager.
problem is, for me neither nouveau nor nvidia drivers work. but that's a different bug.

Fresh install of Kubuntu 16.4.1

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1530523

[Carlo Vanini (silhusk)]

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.

[Darin Miller (darinmiller)]

This issues is fixed when testing today's daily download (4/4/17).

[Mathew Hodson (mhodson)]

This has an easy work-around of installing apt-xapian-index.

[Serhiy (xintx-ua)]

I'd rather remove this driver manager. Xapian index was slow since I started using Ubuntu in 2008 and is slow to this day. I always remove it on fresh installations.

[Simon Quigley (tsimonq2)]

I uploaded a fix for this to Xenial and it's in the Unapproved queue now.

Unsubscribing ~ubuntu-sponsors as there's nothing left to do.

[Brian Murray (brian-murray)]

Hello john, or anyone else affected,

Accepted libqapt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libqapt/3.0.2-0ubuntu1.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[DaytonaJohn (daytonajra)]

I don't think this fixed it for me. Here are the details:
According to Synaptic Package Manager, I am running libqapt3 and libqapt3-runtime both at version 3.0.2-0ubuntu1.2
When I run the driver manager from the system settings, It does not show any drivers. Syslog shows:

Sep 1 15:13:03 jra-HP-ENVY-m7-Notebook-PC org.kubuntu.DriverManager[1733]: Traceback (most recent call last):
Sep 1 15:13:03 jra-HP-ENVY-m7-Notebook-PC org.kubuntu.DriverManager[1733]: File "/usr/lib/x86_64-linux-gnu/libexec/DriverManager_DBus", line 24, in <module>
Sep 1 15:13:03 jra-HP-ENVY-m7-Notebook-PC org.kubuntu.DriverManager[1733]: import dbus
Sep 1 15:13:03 jra-HP-ENVY-m7-Notebook-PC org.kubuntu.DriverManager[1733]: ModuleNotFoundError: No module named 'dbus'

Synaptic shows I have dbus version 1.10.6-1ubuntu3.3 installed from the devel section. I reinstalled dbus and still got the above error.

"Software & Updates" -> "Additional Drivers" shows that I am running nvidia driver version 375.66 and intel-microcode for the CPU.

I am running Kubuntu 16.04 on an HP envy laptop with Nvidia Geforce graphics and Intel I7 CPU.

[DaytonaJohn (daytonajra)]

I know you wanted tags, but I cannot find instructions on how to add tags and have no further time to spend on this right now. Sorry

[Carlo Vanini (silhusk)]

Hi John,

could you please check that you have the python3-dbus package installed?

For me libqapt 3.0.2-0ubuntu1.2 fixed the issue in Xenial.

[DaytonaJohn (daytonajra)]

     Yes, I do have that package installed. However, your email alerted
me to what my problem really is. I am doing development using python and
I have a private installation of python3.6. The DriverManager_DBus
script is getting my installation of python3. I tried installing the
"dbus-python" module for python 3.6, but it fails to install due to a
missing dependency on "dbus-glib-1" which does not seem to be available
anywhere.

     Anyway, modifying the DriverManager_DBus script to use
"/usr/bin/python3" instead of just "python3" results in a working driver
manager.

     So, your libqapt mod fixes the problem, but I found another way to
break it :-)

-John

On 09/02/2017 07:46 PM, Carlo Vanini wrote:
> Hi John,
>
> could you please check that you have the python3-dbus package installed?
>
> For me libqapt 3.0.2-0ubuntu1.2 fixed the issue in Xenial.
>

[Simon Quigley (tsimonq2)]

I can confirm that this successfully fixes the issue on a fully updated Kubuntu 16.04 install.

[Launchpad Janitor (janitor)]

This bug was fixed in the package libqapt - 3.0.2-0ubuntu1.2

---------------
libqapt (3.0.2-0ubuntu1.2) xenial; urgency=low

  * libqapt3 should depend on apt-xapian-index for the package index
    access which is required for most operations (LP: #1530523).

 -- Simon Quigley <email address hidden> Wed, 30 Aug 2017 04:30:26 -0500

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for libqapt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Simon Quigley (tsimonq2)]

Thank you for taking the time to report this bug and helping to make Kubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Kubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Kubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1530523

and any other logs that are relevant for this particular issue.

[Val (pubalapoub)]

Hi Simon, I can confirm the issue is solved (Kubuntu 16.04.4). Thanks!
The Driver Manager now quickly states that no proprietary pilots are available for my machine (which seems correct since I run with an AMD CPU & GPU).

[Nikola Snele (n-schnelle)]

Am 14.07.2018 13:14 schrieb "Val" <email address hidden>:

Hi Simon, I can confirm the issue is solved (Kubuntu 16.04.4). Thanks!
The Driver Manager now quickly states that no proprietary pilots are
available for my machine (which seems correct since I run with an AMD CPU &
GPU).

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1530523

Title:
  kcm_driver_manager: Infinitely shows Collecting information

Status in Kubuntu PPA:
  Incomplete
Status in libqapt package in Ubuntu:
  Incomplete
Status in libqapt source package in Xenial:
  Incomplete

Bug description:
  [Impact]

  * libQapt needs apt-xapian-index in order to search for packages,
otherwise it never returns a result.
  * As a consequence Driver Manager doesn't find packages and is empty.
  * Before, apt-xapian-index was installed as a dependence of Muon
(libmuon), which is not included in the default install anymore.

  [Test Case]

  * Update libqapt and run `kcmshell5 kcm_driver_manager`.
  * After some time (~1 minute) Driver Manager shows suggested packages.

  [Regression Potential]

  * Low, Driver Manager is useless as of now.
  * The same fix was applied in Yakkety.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1530523/+subscriptions

[Launchpad Janitor (janitor)]

[Expired for libqapt (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for Kubuntu PPA because there has been no activity for 60 days.]

[Mathew Hodson (mhodson)]

This was fixed in Xenial with libqapt 3.0.2-0ubuntu1.2 and in other releases with more recent packages. This shouldn't have been set to Incomplete.