[Desktop-packages] [Bug 987220] Re: System does not power off reliably when Shut Down chosen from GUI
dear anders why do you mean Is it confirmed that the power down hang problem is caused by the nvidia driver. as you wrote? If you take a look at this discussion you can see, not only nvidia systems are affcected. I see the same behavior on MSI H61M-P30 (B3) with Sandybridge Desktop (GT1). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/987220 Title: System does not power off reliably when Shut Down chosen from GUI Status in The Session Menu: Incomplete Status in “gnome-session” package in Ubuntu: Invalid Status in “indicator-session” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Invalid Status in “gnome-session” source package in Precise: Invalid Status in “indicator-session” source package in Precise: Invalid Status in “linux” source package in Precise: Confirmed Status in “upstart” source package in Precise: Invalid Bug description: Shutting down the computer using the menue does not work always correct. It often does not complete turn off the computer. The power LED and the LED of the bluetooth unit remain on. Also the fan is still running and won't stop. Shutting down the computer with sudo shutdown -h now using the terminal works fine. I am using a Dell Inspiron 1720. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-session 0.3.96-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Mon Apr 23 12:26:10 2012 ExecutablePath: /usr/lib/indicator-session/gtk-logout-helper InstallationMedia: Kubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: indicator-session UpgradeStatus: Upgraded to precise on 2012-04-21 (1 days ago) --- ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) NonfreeKernelModules: nvidia Package: upstart PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Tags: precise Uname: Linux 3.2.0-24-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/987220/+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 987220] Re: no complete shutdown
it's not only a notebbok related issue i see the similar behavior on MSI H61M-P22(B3) mainboard. The the screen will be turned off but the CPU fan will be slowed but never going off. I tested this with booting from Ubuntu 12.04 distribution DVD and and Try Ubuntu. Both power off just after start and power off after 30 min playing with firefox and libreoffice just powering the system off completely. Probably some regression during recent updates? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/987220 Title: no complete shutdown Status in The Session Menu: Incomplete Status in “gnome-session” package in Ubuntu: Incomplete Status in “indicator-session” package in Ubuntu: Incomplete Status in “linux” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Confirmed Bug description: Shutting down the computer using the menue does not work always correct. It often does not complete turn off the computer. The power LED and the LED of the bluetooth unit remain on. Also the fan is still running and won't stop. Shutting down the computer with sudo shutdown -h now using the terminal works fine. I am using a Dell Inspiron 1720. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-session 0.3.96-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Mon Apr 23 12:26:10 2012 ExecutablePath: /usr/lib/indicator-session/gtk-logout-helper InstallationMedia: Kubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: indicator-session UpgradeStatus: Upgraded to precise on 2012-04-21 (1 days ago) --- ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) NonfreeKernelModules: nvidia Package: upstart PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Tags: precise Uname: Linux 3.2.0-24-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/987220/+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 831624] Re: AIM account Connection can't be established error
2deschmit: same problem by me, after your buddy just sends you a message you see the contact, im not sure if it's also regression or not, have too few AIM contacts. I'll check this in lucid soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/831624 Title: AIM account Connection can't be established error Status in Adium Instant Messenger: New Status in BitlBee: Confirmed Status in Pidgin: New Status in Telepathy Haze: New Status in “empathy” package in Ubuntu: Confirmed Status in “pidgin” package in Ubuntu: Confirmed Bug description: starting today, getting red box with Connection can't be established for my AIM account debug logs show SSL Cert error: Chain is VALID Checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US Also checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US haze_notify_message: error: SSL Certificate Error haze_notify_message: Unable to validate certificate haze_notify_message: The certificate for api.screenname.aol.com could not be validated. The certificate chain presented is invalid. Failed to verify certificate for api.screenname.aol.com Connection error on 0x1532d40 (reason: 0 description: Error requesting https://api.screenname.aol.com/auth/clientLogin: Unable to connect to api.screenname.aol.com: SSL peer presented an invalid certificate) connecting using pidgin works fine. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.1.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Mon Aug 22 13:42:56 2011 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Release Candidate amd64 (20100419.1) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-07-13 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/adium/+bug/831624/+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 831624] Re: AIM account Connection can't be established error
it's a regression, lucid is not affected, we are probably need to open a new bug for this issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/831624 Title: AIM account Connection can't be established error Status in Adium Instant Messenger: New Status in BitlBee: Confirmed Status in Pidgin: New Status in Telepathy Haze: New Status in “empathy” package in Ubuntu: Confirmed Status in “pidgin” package in Ubuntu: Confirmed Bug description: starting today, getting red box with Connection can't be established for my AIM account debug logs show SSL Cert error: Chain is VALID Checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US Also checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US haze_notify_message: error: SSL Certificate Error haze_notify_message: Unable to validate certificate haze_notify_message: The certificate for api.screenname.aol.com could not be validated. The certificate chain presented is invalid. Failed to verify certificate for api.screenname.aol.com Connection error on 0x1532d40 (reason: 0 description: Error requesting https://api.screenname.aol.com/auth/clientLogin: Unable to connect to api.screenname.aol.com: SSL peer presented an invalid certificate) connecting using pidgin works fine. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.1.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Mon Aug 22 13:42:56 2011 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Release Candidate amd64 (20100419.1) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-07-13 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/adium/+bug/831624/+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 831624] Re: AIM account Connection can't be established error
is it not the same? https://bbs.archlinux.org/viewtopic.php?pid=749693 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/831624 Title: AIM account Connection can't be established error Status in Adium Instant Messenger: New Status in BitlBee: New Status in Pidgin: New Status in “empathy” package in Ubuntu: Confirmed Status in “pidgin” package in Ubuntu: Confirmed Bug description: starting today, getting red box with Connection can't be established for my AIM account debug logs show SSL Cert error: Chain is VALID Checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US Also checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O=VeriSign, Inc.,C=US haze_notify_message: error: SSL Certificate Error haze_notify_message: Unable to validate certificate haze_notify_message: The certificate for api.screenname.aol.com could not be validated. The certificate chain presented is invalid. Failed to verify certificate for api.screenname.aol.com Connection error on 0x1532d40 (reason: 0 description: Error requesting https://api.screenname.aol.com/auth/clientLogin: Unable to connect to api.screenname.aol.com: SSL peer presented an invalid certificate) connecting using pidgin works fine. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.1.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Mon Aug 22 13:42:56 2011 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Release Candidate amd64 (20100419.1) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-07-13 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/adium/+bug/831624/+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
