[Desktop-packages] [Bug 1844902] [NEW] Pulseaudio broken after update
Public bug reported: after the update on 21/9/19 of pulseaudio to 1:8.0-0ubuntu3.10 I get no sound and when killing the demon it restarts with the following error - [pulseaudio] main.c: pa_pid_file_create() failed. Reboot does not restore sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.4.0-157.185-generic 4.4.181 Uname: Linux 4.4.0-157-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 1745 F pulseaudio /dev/snd/controlC0: david 1745 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 22 11:05:48 2019 InstallationDate: Installed on 2017-01-03 (991 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: GKPPT10H.86A.0036.2012.1213.1503 dmi.board.name: DCP847SKE dmi.board.vendor: Intel Corporation dmi.board.version: G80890-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrGKPPT10H.86A.0036.2012.1213.1503:bd12/13/2012:svn:pn:pvr:rvnIntelCorporation:rnDCP847SKE:rvrG80890-102:cvn:ct3:cvr: ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1844902 Title: Pulseaudio broken after update Status in pulseaudio package in Ubuntu: New Bug description: after the update on 21/9/19 of pulseaudio to 1:8.0-0ubuntu3.10 I get no sound and when killing the demon it restarts with the following error - [pulseaudio] main.c: pa_pid_file_create() failed. Reboot does not restore sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.4.0-157.185-generic 4.4.181 Uname: Linux 4.4.0-157-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 1745 F pulseaudio /dev/snd/controlC0: david 1745 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 22 11:05:48 2019 InstallationDate: Installed on 2017-01-03 (991 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: GKPPT10H.86A.0036.2012.1213.1503 dmi.board.name: DCP847SKE dmi.board.vendor: Intel Corporation dmi.board.version: G80890-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrGKPPT10H.86A.0036.2012.1213.1503:bd12/13/2012:svn:pn:pvr:rvnIntelCorporation:rnDCP847SKE:rvrG80890-102:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1844902/+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 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu
On my system this bug appears to have been resolved since Chromium updated to Version 53.0.2785.143. I note that when I boot up the system, at the log-in screen that I get a dialogue box requesting the wireless network password which has not occurred in the past so not sure if something has also changed with gnome-keyring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1174162 Title: chrome-browser makes gnome-keyring-daemon use 100% cpu Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Bug description: After upgrading to 13.04, when starting the chromium browser, the gnome-keyring-daemon runs at full CPU load and the chromium-browser has no access to the stored passwords. The issue seems to be known (https://code.google.com/p/chromium/issues/detail?id=98601). I'm personally a bit surprised that Ubuntu 13.04 was released with such a serious problem. The frequently proposed workaround (e.g. https://plus.google.com/110130355317073712944/posts/PckhFj5HUn4) doesn't work because (a) there is no .gnome2/keyrings any more and (b) it's rather inresponsible to store your passwords unencryted. I found that killing gnome-keyring-server several times eventually gives you a working system. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mnl 18759 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140 InstallationDate: Installed on 2010-11-10 (900 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD) MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice wireshark WifiSyslog: Apr 29 07:28:34 lipp-nb wpa_supplicant[1803]: wlan0: WPA: Group rekeying completed with c0:25:06:24:93:e1 [GTK=CCMP] dmi.bios.date: 12/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDD Ver. F.20 dmi.board.name: 30DD dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.23 dmi.chassis.asset.tag: CNU9326SJY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6730b (GB990EA#ABD) dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1174162/+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 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu
I found that stopping the gnome-keyring process resulted in the PC running normally again until the screen lock came on. This resulted in been unable to unlock the screen again requiring dropping to a command line via Ctrl + Alt + F1 to allow a reboot. Therefore does Petar Bojovic's ugly fix cause the same issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1174162 Title: chrome-browser makes gnome-keyring-daemon use 100% cpu Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Bug description: After upgrading to 13.04, when starting the chromium browser, the gnome-keyring-daemon runs at full CPU load and the chromium-browser has no access to the stored passwords. The issue seems to be known (https://code.google.com/p/chromium/issues/detail?id=98601). I'm personally a bit surprised that Ubuntu 13.04 was released with such a serious problem. The frequently proposed workaround (e.g. https://plus.google.com/110130355317073712944/posts/PckhFj5HUn4) doesn't work because (a) there is no .gnome2/keyrings any more and (b) it's rather inresponsible to store your passwords unencryted. I found that killing gnome-keyring-server several times eventually gives you a working system. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mnl 18759 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140 InstallationDate: Installed on 2010-11-10 (900 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD) MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice wireshark WifiSyslog: Apr 29 07:28:34 lipp-nb wpa_supplicant[1803]: wlan0: WPA: Group rekeying completed with c0:25:06:24:93:e1 [GTK=CCMP] dmi.bios.date: 12/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDD Ver. F.20 dmi.board.name: 30DD dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.23 dmi.chassis.asset.tag: CNU9326SJY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6730b (GB990EA#ABD) dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1174162/+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 1433032] Re: Starting Chrome makes gnome-keyring-daemon loading 100% of a CPU thread for 5 at least mins
I have noticed the same behaviour - after boot and starting chrome the gnome-keyring-daemon process takes about 50% of CPU for about 5mins. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1433032 Title: Starting Chrome makes gnome-keyring-daemon loading 100% of a CPU thread for 5 at least mins Status in gnome-keyring package in Ubuntu: Confirmed Bug description: This is Ubuntu 14.04 LTS x64. I removed good amount of remembered passwords but there are no noticable changes. Chrome is v 40.0.2214.10 beta (64-bit) --- Regards respect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1433032/+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 1182007] Re: Failed to SUID root
Same problem here david-desktop signond[2482]: ../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available. Apr 17 07:15:21 david-desktop signond[2482]: ../../../../src/signond/credentialsaccessmanager.cpp 211 init Couldn't load AccessControlManager: apparmor-ac I am also having a system freeze with google talk after about ten minutes - not sure if related running 13:10 (32bit) updated from fresh install of 13.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1182007 Title: Failed to SUID root Status in “signon” package in Ubuntu: Confirmed Bug description: signond[7451]: ../../../../src/signond/signondaemon.cpp 360 init Failed to SUID root. Secure storage will not be available. This report appears in syslog each time Empathy tries and fails to connect to Google Talk using the google-talkplugin interface. It is not clear whether this SUID report is related to the Empathy failure. See bug #1168582 Google talk Requires Authorization after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1182007/+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
