Software Center and Update Manager will not start after downloading Full Circle Magazine

Bug #929910 reported by Frederick L Shope
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After a routine software update via the update manager and after downloading Full Circle Magazine, I found that neither the software center nor the update manager would start when clicked on the launcher. The software center seemed to have hung during the Full Circle Magazine install, and I killed it after about 15 min. Afterwards, Full Circle Magazine opened OK and seemed to readable.

The update manager does report the following error message:

"Could not initialize the package information
An unresolvable problem occurred while initializing the package information.
Please report this bug against the 'update-manager' package and include the following error message:

'E:Opening /etc/apt/sources.list.d/private-ppa.launchpad.net_commercial-ppa-uploaders_fullcircle-issue-56_ubuntu.list - ifstream::ifstream (13: Permission denied)'"

I tried both warm and cold reboots.

I tried running 'ubuntu-bug update-manager' in terminal, but only received the following message:

"Could not determine the package or source package name."

I also tried running ubuntu-bug with the process ID for the update manager from the system monitor, but just received the following message.

"The specified process ID does not belong to a program."

All of the above error conditions are repeatable.

I am reporting this as bug per instructions from the above error messages.

Thank you.

Revision history for this message
Frederick L Shope (flshope) wrote :

I found that the file

 /etc/apt/sources.list.d/private-ppa.launchpad.net_commercial-ppa-uploaders_fullcircle-issue-56_ubuntu.list

only had root read permission, unlike the rest of the files in that directory. When I added universal read permission, the software center and the update manager started running again. This solved my problem.

My original bug report is probably inappropriate, but perhaps the default permissions for the above file need to include universal read permission.

Sorry for any inconvenience here.

My problem is solved.

Revision history for this message
RedSingularity (redsingularity) wrote :

Closing report.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in update-manager (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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