[Desktop-packages] [Bug 1738442] [NEW] When installing a printer, the process gets stuck at "Loading drivers database..."
*** This bug is a duplicate of bug 1721704 *** https://bugs.launchpad.net/bugs/1721704 Public bug reported: When installing a printer, the process gets indefinitely stuck at "Loading drivers database..." ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-control-center 1:3.18.2-1ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 15 17:22:04 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-09-29 (76 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** This bug has been marked a duplicate of bug 1721704 Printer settings stuck on loading drivers database -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1738442 Title: When installing a printer, the process gets stuck at "Loading drivers database..." Status in gnome-control-center package in Ubuntu: New Bug description: When installing a printer, the process gets indefinitely stuck at "Loading drivers database..." ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-control-center 1:3.18.2-1ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 15 17:22:04 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-09-29 (76 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1738442/+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
[Desktop-packages] [Bug 1235549] Re: Lock Screen is extremely slow
Hello, Has there been any development with this issue? I am having the same problem when trying to unlock my Ubuntu 16.04 Gnome. Takes about 10 seconds to show me the desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1235549 Title: Lock Screen is extremely slow Status in gdm package in Ubuntu: Confirmed Bug description: When my system has a message in my user session but my screen is locked, such as if my Google account needs to authenticate again using the GNOME Online Accounts manager, this will often cause the entire GDM to slow down or freeze up entirely, making quick and easy access to my system not so quick-and-easy. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gdm 3.8.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Fri Oct 4 23:51:17 2013 InstallationDate: Installed on 2013-10-04 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Beta amd64 (20130926) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1235549/+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
[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
Right, thanks Michael. I missed that part. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: New Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+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
[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
Launchpad says alsa package was updated for the last time on 2013-10-20. Is it true that Linux/Ubuntu does not have any sound development for 4 years?? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: New Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+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
[Desktop-packages] [Bug 1723150] [NEW] [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Very low front headphones volume
Public bug reported: The sound is barely heard in Ubuntu 16.0 from the green front headphone jack. In a dual boot setup with Windows, on Windows, the sound is perfect. Standard solutions found across forums on the Internet do not seem to help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aserov 1843 F pulseaudio /dev/snd/controlC1: aserov 1843 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 12 17:04:24 2017 InstallationDate: Installed on 2017-09-29 (12 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2016 dmi.bios.vendor: Alienware dmi.bios.version: A10 dmi.board.name: 09G12C dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.modalias: dmi:bvnAlienware:bvrA10:bd10/11/2016:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn09G12C:rvrA00:cvnAlienware:ct3:cvr: dmi.product.name: Alienware Area-51 R2 dmi.sys.vendor: Alienware ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1723150 Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Very low front headphones volume Status in alsa-driver package in Ubuntu: New Bug description: The sound is barely heard in Ubuntu 16.0 from the green front headphone jack. In a dual boot setup with Windows, on Windows, the sound is perfect. Standard solutions found across forums on the Internet do not seem to help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aserov 1843 F pulseaudio /dev/snd/controlC1: aserov 1843 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 12 17:04:24 2017 InstallationDate: Installed on 2017-09-29 (12 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [Alienware Area-51 R2, Creative CA0132, Green Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2016 dmi.bios.vendor: Alienware dmi.bios.version: A10 dmi.board.name: 09G12C dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.modalias: dmi:bvnAlienware:bvrA10:bd10/11/2016:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn09G12C:rvrA00:cvnAlienware:ct3:cvr: dmi.product.name: Alienware Area-51 R2 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1723150/+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
[Desktop-packages] [Bug 1323351] Re: Cannot create a Facebook account with gnome-control-center online-accounts panel
Hi! In my case, after a successful Facebook login I get the following error: == Error creating account Error getting identity: Could not parse response == -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1323351 Title: Cannot create a Facebook account with gnome-control-center online- accounts panel Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Always have empty login dialog when adding Facebook account. The following log are displayed in terminal when trying to add a FB account (see full log on joined log file): (gnome-control-center.real:16388): goa-DEBUG: > GET /dialog/oauth?response_type=token_uri=https%3A%2F%2Fwww.facebook.com%2Fconnect%2Flogin_success.html_id=297654143624603=user_events%2Cread_mailbox%2Cxmpp_login%2Cemail HTTP/1.1 (gnome-control-center.real:16388): goa-DEBUG: < HTTP/1.1 302 forced.302 (gnome-control-center.real:16388): goa-DEBUG: < Location: https://www.facebook.com/v1.0/dialog/oauth?redirect_uri=https%3A%2F%2Fwww.facebook.com%2Fconnect%2Flogin_success.html=user_events%2Cread_mailbox%2Cxmpp_login%2Cemail_type=token_id=297654143624603&_rdr (gnome-control-center.real:16388): goa-DEBUG: > GET /v1.0/dialog/oauth?redirect_uri=https%3A%2F%2Fwww.facebook.com%2Fconnect%2Flogin_success.html=user_events%2Cread_mailbox%2Cxmpp_login%2Cemail_type=token_id=297654143624603&_rdr HTTP/1.1 (gnome-control-center.real:16388): goa-DEBUG: < HTTP/1.1 500 Internal Server Error (gnome-control-center.real:16388): goa-DEBUG: < P3P: CP="Facebook does not have a P3P policy. Learn why here: http://fb.me/p3p; Packages version: gnome-control-center 1:3.6.3-0ubuntu56.1 libgoa-1.0-0b:amd64 3.10.3-0ubuntu1 libgoa-1.0-common 3.10.3-0ubuntu1 libgoa-backend-1.0-1:amd64 3.10.3-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1323351/+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
[Desktop-packages] [Bug 1721739] [NEW] All CPUs > 4 are shown in red
Public bug reported: Every CPU after 4 CPUs is shown with the same color in the Resources plot. It is impossible to distinguish their load. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-system-monitor 3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 6 12:14:59 2017 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "A case of 12 CPUs" https://bugs.launchpad.net/bugs/1721739/+attachment/4963537/+files/Screenshot%20from%202017-10-06%2012-17-19.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1721739 Title: All CPUs > 4 are shown in red Status in gnome-system-monitor package in Ubuntu: New Bug description: Every CPU after 4 CPUs is shown with the same color in the Resources plot. It is impossible to distinguish their load. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-system-monitor 3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 6 12:14:59 2017 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2017-09-29 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1721739/+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
[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
@sevenzig: I have followed your advice, but unless I messed something up in or before the process, it didn't help. Nothing changed... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: New Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+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
[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
@sevenzig: Did you add the option " snd-hda-intel position_fix=1 " as well? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: New Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+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
