USC doesn't use the Opinion status, and even if it did, it wouldn't apply to a straightforward parsing error.
This might be a side-effect of the use of commas to separate package names in custom lists. <https://wiki.ubuntu.com/SoftwareCenter#custom- list> ** Project changed: software-center => software-center (Ubuntu) ** Changed in: software-center (Ubuntu) Status: Opinion => Confirmed ** Changed in: software-center (Ubuntu) Importance: Wishlist => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1185400 Title: USC won't open local files with commas in the filenames Status in “software-center” package in Ubuntu: Confirmed Bug description: With Ubuntu Software Center 5.6.0 (Ubuntu 13.04) NOTE: This bug first manifested itself when I found myself unable to install from gvfs (nautilus mounted) CIFS shares. This could possibly (probably?) be due to an USC identifying legal dir/file name characters as illegal, or interpreting the dir/filename as a search request rather than as a file location To replicate this bug: I have a CIFS server named "oldman", a share called "completed". When I browse to this share in nautilus it creates the GVFS mount as: "/var/run/user/michael/gvfs/smb-share:server=oldman,share=completed/" When I open the .deb file (double click in Nautilus) i get the following error: 'No items match "/var/run/user/michael/gvfs/smb-share:server=oldman,share=completed/uplink-linux-1.6.0-2-amd64-1344894496.deb" Suggestions: - Check that your spelling is correct. Did you mean: <such and such*>' * can't be buggered typing the whole thing See first error image (attached to this post). Note that the file location is in the top right of the image in the search box. This is the full valid file location/name. If I copy and paste the contents of the search box into a terminal (it is not nautilus mangling it): "michael@neffo:~$ ls -l /var/run/user/michael/gvfs/smb-share:server=oldman,share=completed/uplink-linux-1.6.0-2-amd64-1344894496.deb -rwx------ 1 michael michael 21907452 May 29 21:34 /var/run/user/michael/gvfs/smb-share:server=oldman,share=completed/uplink-linux-1.6.0-2-amd64-1344894496.deb michael@neffo:~$ " If I copy the .deb file to the local disk (~/Downloads), it allows me to install as expected (see a second post for an image). This is not a file permissions issue either: "michael@neffo:~$ ls -l ~/Downloads/uplink-linux-1.6.0-2-amd64-1344894496.deb -rwx------ 1 michael michael 21907452 May 29 21:34 /home/michael/Downloads/uplink-linux-1.6.0-2-amd64-1344894496.deb michael@neffo:~$" Renaming the local file as "bleh=uplink- linux-1.6.0-2-amd64-1344894496.deb" and "bleh:uplink- linux-1.6.0-2-amd64-1344894496.deb" did not produce the bug. Renaming the file with a comma as "bleh,uplink- linux-1.6.0-2-amd64-1344894496.deb" produced the bug as seen in this post. It seems as though the comma is the problem character. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1185400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
