[Kernel-packages] [Bug 1397487] [NEW] Philips GoGear Vibe MP3 Player is not properly recoginized on Ubuntu 14.04
Public bug reported: I have a Philips GoGear Vibe Mp3 player that worked fine on Ubuntu 12.04. Recently, I installed Ubuntu 14.04 LTS (64 bits) on the same machine and my deviced didn't work properly anymore: when I open it, I see an icon named 'Internal Storage' inside. If I right-click outside the icon (but inside the GoGear Vibe folder) to see GoGear properties, Nautilus says it only has 1 element, with a size of 0 bytes. Also, if I ask for GoGear's permissions, Nautilus says they couldn't be determined. If I open 'Internal Storage', nautilus only shows an empty folder (no files inside, see the attached screenshots for details). On Ubuntu 12.04, I opened my device and all it's content was shown directly without any problem. Also, there wasn't any 'Internal Storage' icon. This is probably related to bug 1214765, and question 228269. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rfg1905 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 28 23:24:24 2014 HibernationDevice: RESUME=UUID=291b3f8a-4d92-4e7f-8286-775f98ccf271 InstallationDate: Installed on 2014-11-22 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CL.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=0bbaee34-88b2-46e9-9fd2-9d7efa698bdc ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: K8M800-M2 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/18/2005:svn:pn:pvr:rvn:rnK8M800-M2:rvr:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: This is what I see inside my device https://bugs.launchpad.net/bugs/1397487/+attachment/4270496/+files/Screenshots.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1397487 Title: Philips GoGear Vibe MP3 Player is not properly recoginized on Ubuntu 14.04 Status in linux package in Ubuntu: New Bug description: I have a Philips GoGear Vibe Mp3 player that worked fine on Ubuntu 12.04. Recently, I installed Ubuntu 14.04 LTS (64 bits) on the same machine and my deviced didn't work properly anymore: when I open it, I see an icon named 'Internal Storage' inside. If I right-click outside the icon (but inside the GoGear Vibe folder) to see GoGear properties, Nautilus says it only has 1 element, with a size of 0 bytes. Also, if I ask for GoGear's permissions, Nautilus says they couldn't be determined. If I open 'Internal Storage', nautilus only shows an empty folder (no files inside, see the attached screenshots for details). On Ubuntu 12.04, I opened my device and all it's content was shown directly without any problem. Also, there wasn't any 'Internal Storage' icon. This is probably related to bug 1214765, and question 228269. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rfg1905 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 28 23:24:24 2014 HibernationDevice: RESUME=UUID=291b3f8a-4d92-4e7f-8286-775f98ccf271 InstallationDate: Installed on 2014-11-22 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CL.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=0bbaee34-88b2-46e9-9fd2-9d7efa698bdc ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 RfKill: SourcePackage: linux
[Kernel-packages] [Bug 1214765] Re: Philips GoGear Vibe MP3 Player is not properly recoginized
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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1214765 Title: Philips GoGear Vibe MP3 Player is not properly recoginized Status in “linux” package in Ubuntu: Incomplete Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1388430] Re: nvidia-settings closes when pressing 'Apply' button, but changes aren't applied
1) As Nvidia Customer Care team suggested, I manually installed driver 304.123 (instructions at http://askubuntu.com/questions/451221/ubuntu-14-04-install-nvidia-driver, answer nº 23). 2) Running gksudo nvidia-settings enabled me to change my screen resolution, but my nettings were not being preserved after rebooting my machine. 3) I went to System Settings -- Monitors, and changed my screen resolution from there. My new settings were preserved after rebooting this time. It seems driver 304.123 solves the issue, but it's not available for Trusty yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1388430 Title: nvidia-settings closes when pressing 'Apply' button, but changes aren't applied Status in “nvidia-settings” package in Ubuntu: New Bug description: 1. I recently did a fresh install of Ubuntu 14.04 (64 bits) on my machine, which has an Nvidia GeForce 6200 graphics card. When I try to change the screen resolution, changes are not being applied and nvidia-settings is closing when I press the 'Apply' button. 2. I run nvidia-settings in a terminal, and I got the following error message after pressing the 'Apply' button (see the attached file): The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 528 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 3. This seems to be a duplicate of Bug #1273652. 4. I contacted Nvidia custom care support, and they suggested me to try the latest driver version (304.123). Unfortunately, when I checked nvidia-graphics-drivers-304 at Launchpad, I found it's only available for Utopic, Precise, and Vivid (indeed, it doesn't appear in my Additional Drivers wizard). If you help me to install version 304.123 on my system, I'll give Nvidia Linux maintainers all the feedback they are requesting from me, and I'll be in a better condition to colaborate with you to solve this issue (installation instructions provided by Nvidia website are hard for me to follow). Feel free to e-mail me if you think I can help in any way. 5. You can find additional information about similar issues in the following links: http://askubuntu.com/questions/412181/nvidia-settings-received-an-x-window-system-error-error-was-badvalue-intege http://askubuntu.com/questions/452030/nvidia-settings-does-not-work-since-upgrade-to-14-04 http://www.nvnews.net/vbulletin/showthread.php?t=76073 6. System settings: OS version: Ubuntu 14.04 LTS (64 bits) Nvidia driver version: 304.117 nvidia-settings version: 331.20-0ubuntu8 P.S: apparently, this is not the first time a bug like this affects nvidia-settings on Ubuntu. If you read the comments at the second and third links in point 5 (above), there is people who solved the issue after they installed an nvidia-settings package which version number matches the driver one (or vice-versa). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 1 14:33:26 2014 InstallationDate: Installed on 2014-11-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1388430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1273652] Re: apply of multi-monitor setting results in crash
Regarding the issue I commented above, I could fix it by manually installing driver 304.123. Please, refer to Bug #1388430 for details. I hope this can help you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1273652 Title: apply of multi-monitor setting results in crash Status in “nvidia-settings” package in Ubuntu: Confirmed Bug description: After the recent update of nvidia settings, I am not able to apply new monitor setting via nvidia settings anymore. After configuration of X Server Display Configuration hit hit the apply button and then the program simply quit. A workaround is to click on Save to X Configuration file and restart the computer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-settings 331.20-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Jan 28 12:51:27 2014 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1273652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1388430] Re: nvidia-settings closes when pressing 'Apply' button, but changes aren't applied
1) I have installed driver 304.123 from Nvidia following the instructions provided at http://askubuntu.com/questions/451221/ubuntu-14-04-install-nvidia-driver 2) I got the following error message: The distribution-provided pre-install script failed! Continue installation anyway? I chose 'Yes' and the installation process continued and finished, apparently, successfully. 3) I sent the log file (same file I attach here) to Nvidia Customer Care support team, and I'm waiting for their feedback now. 4) I was able to change my screen resolution (run gksudo nvidia- settings, because changing my screen resolution requires root privileges), so 304.123 seems to solve the issue. If Nvidia technicians confirm that everything is ok, I think 304.123 should be made available for Trusty, so any user who need it could install it with the 'Additional Drivers' wizard. It's all for now. ** Attachment added: nvidia-installer.log https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1388430/+attachment/4252313/+files/nvidia-installer.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1388430 Title: nvidia-settings closes when pressing 'Apply' button, but changes aren't applied Status in “nvidia-settings” package in Ubuntu: New Bug description: 1. I recently did a fresh install of Ubuntu 14.04 (64 bits) on my machine, which has an Nvidia GeForce 6200 graphics card. When I try to change the screen resolution, changes are not being applied and nvidia-settings is closing when I press the 'Apply' button. 2. I run nvidia-settings in a terminal, and I got the following error message after pressing the 'Apply' button (see the attached file): The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 528 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 3. This seems to be a duplicate of Bug #1273652. 4. I contacted Nvidia custom care support, and they suggested me to try the latest driver version (304.123). Unfortunately, when I checked nvidia-graphics-drivers-304 at Launchpad, I found it's only available for Utopic, Precise, and Vivid (indeed, it doesn't appear in my Additional Drivers wizard). If you help me to install version 304.123 on my system, I'll give Nvidia Linux maintainers all the feedback they are requesting from me, and I'll be in a better condition to colaborate with you to solve this issue (installation instructions provided by Nvidia website are hard for me to follow). Feel free to e-mail me if you think I can help in any way. 5. You can find additional information about similar issues in the following links: http://askubuntu.com/questions/412181/nvidia-settings-received-an-x-window-system-error-error-was-badvalue-intege http://askubuntu.com/questions/452030/nvidia-settings-does-not-work-since-upgrade-to-14-04 http://www.nvnews.net/vbulletin/showthread.php?t=76073 6. System settings: OS version: Ubuntu 14.04 LTS (64 bits) Nvidia driver version: 304.117 nvidia-settings version: 331.20-0ubuntu8 P.S: apparently, this is not the first time a bug like this affects nvidia-settings on Ubuntu. If you read the comments at the second and third links in point 5 (above), there is people who solved the issue after they installed an nvidia-settings package which version number matches the driver one (or vice-versa). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 1 14:33:26 2014 InstallationDate: Installed on 2014-11-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1388430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1273652] Re: apply of multi-monitor setting results in crash
I have a similar issue with Ubuntu 14.04 (64 bits) and Nvidia driver 304.117 (please, refer to Bug #1388430 for details). I spoke to Nvidia Customer Care support and they are requesting me to install another driver version (304.123) from Nvidia web site. Unfortunately, installation instructions are hard for me to follow, so I would need some help in order to test this driver version and give the technicians a proper feedback. If someone thinks that this could help to solve the issue, please feel free to e-mail me and I'll do my best to colaborate. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1273652 Title: apply of multi-monitor setting results in crash Status in “nvidia-settings” package in Ubuntu: Confirmed Bug description: After the recent update of nvidia settings, I am not able to apply new monitor setting via nvidia settings anymore. After configuration of X Server Display Configuration hit hit the apply button and then the program simply quit. A workaround is to click on Save to X Configuration file and restart the computer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-settings 331.20-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Jan 28 12:51:27 2014 InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1273652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1388430] [NEW] nvidia-settings closes when pressing 'Apply' button, but changes aren't applied
Public bug reported: 1. I recently did a fresh install of Ubuntu 14.04 (64 bits) on my machine, which has an Nvidia GeForce 6200 graphics card. When I try to change the screen resolution, changes are not being applied and nvidia-settings is closing when I press the 'Apply' button. 2. I run nvidia-settings in a terminal, and I got the following error message after pressing the 'Apply' button (see the attached file): The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 528 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 3. This seems to be a duplicate of Bug #1273652. 4. I contacted Nvidia custom care support, and they suggested me to try the latest driver version (304.123). Unfortunately, when I checked nvidia-graphics-drivers-304 at Launchpad, I found it's only available for Utopic, Precise, and Vivid (indeed, it doesn't appear in my Additional Drivers wizard). If you help me to install version 304.123 on my system, I'll give Nvidia Linux maintainers all the feedback they are requesting from me, and I'll be in a better condition to colaborate with you to solve this issue (installation instructions provided by Nvidia website are hard for me to follow). Feel free to e-mail me if you think I can help in any way. 5. You can find additional information about similar issues in the following links: http://askubuntu.com/questions/412181/nvidia-settings-received-an-x-window-system-error-error-was-badvalue-intege http://askubuntu.com/questions/452030/nvidia-settings-does-not-work-since-upgrade-to-14-04 http://www.nvnews.net/vbulletin/showthread.php?t=76073 6. System settings: OS version: Ubuntu 14.04 LTS (64 bits) Nvidia driver version: 304.117 nvidia-settings version: 331.20-0ubuntu8 P.S: apparently, this is not the first time a bug like this affects nvidia-settings on Ubuntu. If you read the comments at the second and third links in point 5 (above), there is people who solved the issue after they installed an nvidia-settings package which version number matches the driver one (or vice-versa). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-settings 331.20-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 1 14:33:26 2014 InstallationDate: Installed on 2014-11-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: Terminal Output from nvidia-settings https://bugs.launchpad.net/bugs/1388430/+attachment/4250915/+files/Terminal%20Output%20from%20nvidia-settings -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1388430 Title: nvidia-settings closes when pressing 'Apply' button, but changes aren't applied Status in “nvidia-settings” package in Ubuntu: New Bug description: 1. I recently did a fresh install of Ubuntu 14.04 (64 bits) on my machine, which has an Nvidia GeForce 6200 graphics card. When I try to change the screen resolution, changes are not being applied and nvidia-settings is closing when I press the 'Apply' button. 2. I run nvidia-settings in a terminal, and I got the following error message after pressing the 'Apply' button (see the attached file): The program 'nvidia-settings' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 528 error_code 2 request_code 158 minor_code 25) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 3. This seems to be a duplicate of Bug #1273652. 4. I contacted Nvidia custom care support, and they suggested me to try the latest driver version (304.123).
