Bug 297699 - Muon software center is not listing all repository package listed in Muon package manager
Summary: Muon software center is not listing all repository package listed in Muon pac...
Status: RESOLVED DUPLICATE of bug 297700
Alias: None
Product: muon
Classification: Applications
Component: muon (show other bugs)
Version: 1.3.1
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Jonathan Thomas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-08 03:43 UTC by vipin balakrishnan
Modified: 2012-04-08 03:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vipin balakrishnan 2012-04-08 03:43:52 UTC
Hi 

This bug is reference to 297613. But not  same case. In my system (Kubuntu 12.04 Beta2), I have installed Google chrome. And it is added Google repository for easy update. I can able to see the list of Google chrome packages from the repository in  "muon package manager". But when open up the "Muon software center" I can only see a link on left side Google, While clicking on it no package is getting listed on right.

Similar case is for canonical partners repository. I can able to see the list of packages in "muon package manager" But not in "Muon software center".

Please find the image explanation below.

testcase1.png - Google repository not getting listed in Muon Software Center
testcase2.png - Google repository is getting listed in  Muon Package Manager
testcase3.png - Canonical partners repository not getting listed in Muon Software Center
testcase4.png - Canonical partners repository  getting listed in Muon Package Manager

Software details

Kubuntu 12.04 Beta2
KDE - Platform Version 4.8.2 (4.8.2)
Muon Software Center Version 1.3.1 "Daring Dalek"
Kernal : 3.2.0-22-generic-pae

I have attached testcases.zip contain the screenshot  for the issue.
 

Best Regards,
Vipin Balakrishnan.
Comment 1 vipin balakrishnan 2012-04-08 03:46:12 UTC

*** This bug has been marked as a duplicate of bug 297700 ***