Philips GoGear Vibe MP3 Player is not properly recoginized

[lebechec]

just did an update to 13.04 from version 12 and now my Philips GoGear Vibe MP3 Player is not properly recoginized. In version 12 the folders were visible and music could be copied to the player. In 13.04 when I select the GoGear, the only icon is for Internal Storage - with no folders listed. Is there a driver that is needed so the player can be recognized? thanks.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1214765/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

lebechec, thank you for reporting this bug to Ubuntu. Raring reached EOL on January 27, 2014.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this an issue in a supported release? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1214765

[nilsolaris (nilsolaris)]

Why has this problem not been corrected yet ? I have used GoGear with ubuntu for years. Moving files to other computers in order to load on to GoGear is becoming a huge annoyance.

[penalvch (penalvch)]

nilsolaris, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Roberto González Correa (rob-e-gonzlez)]

Cristopher:

I can confirm that this issue is currently affecting Trusty (64 bits) too. I'm going to open a new report by this weekend. Should I suscribe you to it when I get this done?

Regards.

[penalvch (penalvch)]

Roberto González Correa, please feel free to subscribe me to the new report.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]