System Settings->Digital Kamera Error occurred leaving orphaned control module

Darin,

some packages are stuck in the "proposed-rejected" upload-queue.

https://launchpad.net/ubuntu/xenial/+queue?queue_state=4&queue_text=

These look relevant to me:

 * libkf5kexiv2
 * libkf5kdcraw

cross-check with packages-list:

http://packages.ubuntu.com/search?keywords=libkf5kexiv2&searchon=names&suite=all&section=all
http://packages.ubuntu.com/search?keywords=libkf5kdcraw&searchon=names&suite=all&section=all

Should think these two need attn. Tks. for the report.

By the way, I'm really greatly interested if the ppa-purge is always sucessful if you use those staging ppa's ?

Could you return the output of:

dpkg-query -l libkf5kexiv2

dpkg-query -l libkf5kkdcraw

Outputs:

 dpkg-query -l libkf5kexiv2

dpkg-query: no packages found matching libkf5kexiv2

dpkg-query -l libkf5kkdcraw

dpkg-query: no packages found matching libkf5kkdcraw

As for the ppa purge test, shall I test the PPA purge for all xenial staging and landing PPA's? I assume I should test one at a time with a reboot in between?

Well, in general you should have to decide (think) which package repository will be in lead.

So, staging should always be the highest level. Next level would be landing. Lowest level is standard repository w/o any manually installed packages from "proposed". Hard to give a recommondation here. So well, if you have packages installed from proposed (Kub's) for testing-purposes and feedback you can leave this repository ativated during the ppa-purge process. Any conflicts have to be resolved manually. In some terms "proposed" is highly dangerous, mainly if packages get rolled back to previous status.

Sometimes it's helpful to create a Virtualbox-machine to play this through. The funniest event for me recently was having no desktop at all but ALT+F2 worked and I could go on with Konsole, like sudo atp-get -f install. ;-)

Conflicts should always preferably be solved on the lowest level. Like pushing in the new version of kubuntu-desktop. This drags in unwanted packages now.

In general I think your report is valid, thus added the tag "unmet-dependcies" whereas fixing this may also resolve Gwenview not coming in.

sudo ppa-purge ppa:kubuntu-ppa/staging-kdeapplications

<.... long list of packages to revert....>

Text at the end:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gwenview : Depends: libkf5kipi30.0.0 (>= 15.12.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
/usr/sbin/ppa-purge: line 191: aptitude: command not found
Warning: Something went wrong, packages may not have been reverted

Looks like the Gwenview issue...

sudo ppa-purge ppa:kubuntu-ppa/staging-frameworks

...

PPA purged successfullty.

https://launchpad.net/ubuntu/xenial/+queue?queue_state=3&queue_text=libkf5kipi

It's stuck in Uploads-"proposed"-queue.

sudo ppa-purge ppa:kubuntu-ppa/staging-plasma

Updating packages lists
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/xenial/universe/binary-i386/Packages Writing more data than expected (9424944 > 9424155) [IP: 91.189.91.23 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

Warning: apt-get update failed for some reason

sudo ppa-purge ppa:kubuntu-ppa/staging-plasma

PPA purged successfully after reboot.

So I tried applications again:

udo ppa-purge ppa:kubuntu-ppa/staging-kdeapplications

Updating packages lists
PPA to be removed: kubuntu-ppa staging-kdeapplications
Warning: Could not find package list for PPA: kubuntu-ppa
staging-kdeapplications

Rebooting and removing landing next....

sudo ppa-purge ppa:kubuntu-ppa/ppa-landing

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 kde-config-screenlocker : Breaks: plasma-workspace (< 4:5.5~) but 4:5.4.3-0ubuntu1 is to be installed
 libkscreenlocker5 : Breaks: plasma-workspace (< 4:5.5~) but 4:5.4.3-0ubuntu1 is to be installed
E: Unable to correct problems, you have held broken packages.
/usr/sbin/ppa-purge: line 191: aptitude: command not found
Warning: Something went wrong, packages may not have been reverted

Trying another reboot....

sudo ppa-purge ppa:kubuntu-ppa/staging-misc
...
PA purged successfully

That was the last of the PPA's -all reverted and the system is still functional.

Status changed to 'Confirmed' because the bug affects multiple users.

It looks like kamera is using the qt4 package configuration which doesn't override the path to the correct qt5 location

This bug was fixed in the package kamera - 4:15.12.3-1~2ubuntu1

---------------
kamera (4:15.12.3-1~2ubuntu1) yakkety; urgency=medium

  * Merge with debian git (LP: #1556540)

 -- Philip Muškovac <email address hidden> Mon, 02 May 2016 17:58:42 +0200

I just now installed kamera - 4:15.12.3-1~2ubuntu1 (plus dependencies libgphoto2-6_2.5.10-2 and libgphoto2-port12_2.5.10-2) from preliminary Ubuntu 16.10 packages.

I can confirm that this bug is not present any more in kamera - 4:15.12.3-1~2ubuntu1.

Philip Muškovac: Many thanks for your effort!

Hi
Any ideas when the fix will be available in 16.04 repos? Installing packages from next release does not seem to be good solution, this meant to be stable release after all.

Hello Darin, or anyone else affected,

Accepted kamera into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kamera/4:15.12.3-0ubuntu1.1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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!

I just now tested package "kamera" version 15.12.3-0ubuntu1.1 from the xenail-proposed repository.

I can confirm that the bug present in version 15.12.3-0ubuntu1 is fixed in 15.12.3-0ubuntu1.1.

Thank you for the quick response!

Also confirming the Kamera: Digital camera window from the proposed PPA works. I successfully selected a camera model but I have not attempted to interface my camera (it's home but I am not). Will try later tonight.

I have the same problem in kubuntu 16.04 LTS. What can I do to fix this problem?

This bug was fixed in the package kamera - 4:15.12.3-0ubuntu1.1

---------------
kamera (4:15.12.3-0ubuntu1.1) xenial; urgency=medium

  * Switch to the qt5 build system so the installation paths are correct
    (LP: #1556540)

 -- Philip Muškovac <email address hidden> Mon, 02 May 2016 18:08:49 +0200

The verification of the Stable Release Update for kamera 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.