Ubuntu
shotwell package

shotwell is pulling in unity-control-center and UOA on Ubuntu GNOME

Bug #1301712 reported by Tim Lunn
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
shotwell (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

0.18.0-0ubuntu3 added a Recommends on unity-control-center-signon.

This resulted in the entire unity-control-center/UOA stack getting pulled into the Ubuntu GNOME seed.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: shotwell 0.18.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Apr 3 14:03:35 2014
InstallationDate: Installed on 2012-09-23 (557 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922)
SourcePackage: shotwell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Tim Lunn (darkxst) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package shotwell - 0.18.0-0ubuntu4

---------------
shotwell (0.18.0-0ubuntu4) trusty; urgency=medium

  * Drop unity-control-center-signon from Recommends to Suggests, so we
    don't pull in that whole stack on non-unity desktops (LP: #1301712)
 -- Adam Conrad <email address hidden> Wed, 02 Apr 2014 21:49:18 -0600

Changed in shotwell (Ubuntu):
status: New → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

That change is buggy, without u-c-c-s you can't configure accounts for publishing. Anyway I guess it's up to the GNOME remix to decide if they want to ship buggy softwares by default...

Changed in shotwell (Ubuntu):
importance: Undecided → Low
Revision history for this message
Palmar Thorsteinsson (palmar) wrote :

Publishing does not work in Shotwell with Ubuntu GNOME 14.04 using package 0.18.0-0ubuntu4.

Although the reported bug is technically solved I agree with Sebastian Bacher that this is a buggy change.

Should there be a separate bug report for the regression or is this bug an appropriate place to discuss permanent fixes?

Revision history for this message
Jim Nelson (yorba-jim) wrote :

The open ticket for this problem is at bug #1314904.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.