[Bug 1450155] Re: If X fails to start, Plymouth should redirect to a command line login
** Description changed: Hi, - After latest kernel upgrade on Trusty 14.04.2 LTS on two of my systems, - the system did not boot, it was locked on Plymouth splash screen. + After purge of old packages with command sudo aptitude purge ~c on + Trusty 14.04.2 LTS on two of my systems, the system did not boot, it was + locked on Plymouth splash screen. The culprit is that for a reason I don't know symlink /etc/X11/X was removed during the upgrade, and X failed to start. In that case Plymouth should just fall back to a prompt shell login, otherwise there's no way to log onto the machine except SSH... Steps to reproduce : DO : Remove symlink /etc/X11/X (it occurs sometimes during kernel upgrades, I did not identify the culprit but this is not the first time I see this) DO : Reboot EXPECT : After a failed attempt to start X, Plymouth should fall back to the command prompt ACTUAL : The user is locked up and the only ways to recover are to log via SSH or in failsafe mode. - It should obviously be better that the strange thing with the X link - removed would be fixed, but anyway this would be a safeguard. + The best would be to fix the original bug, i.e. symlink to X deleted + when purging old packages. This can occur on Ubuntu LTS upgraded w/ HWE + as the xserver-xorg package changed, while this won't occur on other + systems. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: plymouth 0.8.8-0ubuntu17.1 ProcVersionSignature: Ubuntu 3.16.0-36.48~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 29 20:28:50 2015 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationDate: Installed on 2014-09-08 (233 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: ASUS All Series ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-36-generic root=UUID=ef1513cf-ddee-4714-bc0b-a7f84529908e ro quiet splash ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-36-generic root=UUID=ef1513cf-ddee-4714-bc0b-a7f84529908e ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2205 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A 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.:bvr2205:bd02/12/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450155 Title: If X fails to start, Plymouth should redirect to a command line login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1450155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450155] [NEW] If X fails to start, Plymouth should redirect to a command line login
Public bug reported: Hi, After latest kernel upgrade on Trusty 14.04.2 LTS on two of my systems, the system did not boot, it was locked on Plymouth splash screen. The culprit is that for a reason I don't know symlink /etc/X11/X was removed during the upgrade, and X failed to start. In that case Plymouth should just fall back to a prompt shell login, otherwise there's no way to log onto the machine except SSH... Steps to reproduce : DO : Remove symlink /etc/X11/X (it occurs sometimes during kernel upgrades, I did not identify the culprit but this is not the first time I see this) DO : Reboot EXPECT : After a failed attempt to start X, Plymouth should fall back to the command prompt ACTUAL : The user is locked up and the only ways to recover are to log via SSH or in failsafe mode. It should obviously be better that the strange thing with the X link removed would be fixed, but anyway this would be a safeguard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: plymouth 0.8.8-0ubuntu17.1 ProcVersionSignature: Ubuntu 3.16.0-36.48~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 29 20:28:50 2015 DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth InstallationDate: Installed on 2014-09-08 (233 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: ASUS All Series ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-36-generic root=UUID=ef1513cf-ddee-4714-bc0b-a7f84529908e ro quiet splash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-36-generic root=UUID=ef1513cf-ddee-4714-bc0b-a7f84529908e ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2205 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A 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.:bvr2205:bd02/12/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450155 Title: If X fails to start, Plymouth should redirect to a command line login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1450155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355025] Re: After suspend/resume, no sound with pulseaudio
Hi, The trick is that I could reproduce exactly the same issue on my Dell Inspiron 1525 (without HDMI sound card) before I upgraded its Skype to version 4.3, as long as Skype was connected. So it does not seem to have anything to see with HDMI but with something else. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355025 Title: After suspend/resume, no sound with pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1355025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355025] Re: After suspend/resume, no sound with pulseaudio
Note that the bug only occurs when apps not compatible with PA 4.0 are started. With other apps the issue does not occur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355025 Title: After suspend/resume, no sound with pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1355025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355025] Re: After suspend/resume, no sound with pulseaudio
Hi, Analog is always selected (but it's true that my graphics card appears as a sound card, which might be the source of the issue). ** Changed in: pulseaudio (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355025 Title: After suspend/resume, no sound with pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1355025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355025] [NEW] After suspend/resume, no sound with pulseaudio
Public bug reported: HI, I've remarked the following bug, at least under KDE : DO : open your KDE session DO : launch an app which has not been set compliant with pulseaudio (for example, Skype 4.2, but in that case you need to log into the service so that it plays a sound - issue no longer reproducible with 4.3. This also works with Steam games like Civ5) DO : quit the app DO : suspend DO : wait some time, for example 15 minutes DO : resume DO : try to trigger a sound, anything (the sound tester applet in KDE is enough) EXPECT : you hear sound ACTUAL : no sound at all. Note that if you run pulseaudio -k, sound is partially restored... only for KDE apps. The only way to restore sound completely is to logout/login Reproducibility : always Tested on Kubuntu Trusty AMD64 My hardware : AMD Phenom x4 9850 8 GB RAM Asus M2N-SLI Deluxe NVidia GeForce 660 Ti ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julien 4967 F pulseaudio julien31643 F pulseaudio /dev/snd/controlC0: julien 4967 F pulseaudio julien31643 F pulseaudio CurrentDesktop: KDE Date: Mon Aug 11 08:42:19 2014 SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-03-20 (143 days ago) dmi.bios.date: 10/02/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1701 dmi.board.name: M2N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision1701:bd10/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355025 Title: After suspend/resume, no sound with pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1355025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331817] [NEW] Cannot send emails with KMail after upgrade to 4.13.1
Public bug reported: Hi, I've upgraded my KDE to version 4.13.1 from version 4.13.0 in Trusty. When I try to send an Email, I get the following error message : Notes : Impossible d'écrire dans le fichier de courrier électronique /home/julien/.local/share/akonadi_akonotes_resource_0/tmp/1403126018.R0.pcathlon64. The error comes from the fact the following directories were not created during the migration : ~/.local/share/akonadi_akonotes_resource_0/tmp ~/.local/share/akonadi_akonotes_resource_0/cur ~/.local/share/akonadi_akonotes_resource_0/new Workaround : create them. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: kmail 4:4.13.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jun 18 23:16:53 2014 SourcePackage: kdepim UpgradeStatus: Upgraded to trusty on 2014-03-20 (90 days ago) ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1331817 Title: Cannot send emails with KMail after upgrade to 4.13.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1331817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303285] Re: No sound after suspend/resume
OK looks like this has been fixed with latest KDE upgrades. ** Changed in: pulseaudio (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303285 Title: No sound after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303285] Re: No sound after suspend/resume
** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303285/+attachment/4069155/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303285 Title: No sound after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303285] [NEW] No sound after suspend/resume
Public bug reported: Hi, I'm using the following system : Kubuntu 14.04 AMD64 AMD Phenom 9850 Mobo Asus M2N-SLI Deluxe w/ chipset NForce 570 SLI The issue that after a resume I always have no sound. The culprit is likely to be pulseaudio, as once I've killed it sound partially reappears for KDE system sounds. However for other apps, like for example VLC, this does not work. I've also remarked something very strange, i.e. after a resume another pulseaudio process is always started, don't know why, so this may be the cause of a mess, and when we attempt to kill it sound is not redirected to the PA process which was launched prior the suspend. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julien26083 F pulseaudio julien27490 F pulseaudio /dev/snd/controlC0: julien26083 F pulseaudio /dev/snd/pcmC0D0p: julien26083 F...m pulseaudio CurrentDesktop: KDE Date: Sun Apr 6 11:56:45 2014 SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-03-20 (16 days ago) dmi.bios.date: 10/02/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1701 dmi.board.name: M2N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision1701:bd10/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: syslog.1 https://bugs.launchpad.net/bugs/1303285/+attachment/4069148/+files/syslog.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303285 Title: No sound after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286836] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has m
Workaround : sudo dpkg --purge libpostproc52:i386 Then reinstall libpostproc52. Rgds, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286836 Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1286836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277552] Re: libpostproc52 does not support multiarch
Workaround : sudo dpkg --purge libpostproc52:i386 Then reinstall libpostproc52. Rgds, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277552 Title: libpostproc52 does not support multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/kaffeine/+bug/1277552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302326] [NEW] cannot shutdown/suspend/restart from the GUI after latest libpam-systemd update
*** This bug is a duplicate of bug 1302264 *** https://bugs.launchpad.net/bugs/1302264 Public bug reported: Hi On two different computers, the first one upgraded two weeks ago to Trusty and the second one updated today after a Saucy fresh install, the suspend/login/restart features are disabled again from the GUI. Tests done : When launching gdbus, error is : julien@pcathlon64:~$ gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.CanReboot Erreur : GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Cannot launch daemon, file not found or permissions invalid When trying to reboot : julien@pcathlon64:~$ gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.Reboot true Erreur : GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Cannot launch daemon, file not found or permissions invalid However I got a new error : administrateur@pcathlon64:~$ sudo /lib/systemd/systemd-logind [sudo] password for administrateur: (null):error.c:319: Assertion failed in nih_error_get: context_stack != NULL The two computers are using Kubuntu/AMD64. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libpam-systemd 204-5ubuntu16 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Fri Apr 4 06:16:54 2014 ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-03-20 (14 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302326 Title: cannot shutdown/suspend/restart from the GUI after latest libpam- systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1302326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297363] Re: [FFe] Add cgmanager support
Hi, This fix causes a regression when /usr is not mounted on the same partition as /. See bug report 1301544 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297363 Title: [FFe] Add cgmanager support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1297363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301544] [NEW] cannot boot with latest systemd updates
Public bug reported: Hi, With latest systemd updates with cgmanager support, system won't boot if /usr is mounted on a different partition from /. The reason (that you can see when booting system in failsafe mode and trying to launch dpkg or anything and seeing that system is complaining) is that the system is trying to load library libcgmanager.so.0 while udev is not fully started and mountpoints not completely mounted. Workaround consists in copying libcgmanager.so.0 and libcgmanager.so.0.0.0 from /usr/lib/x86-64-linux-gnu to /lib/x86-64 -linux-gnu and everything is fine again. This regression was introduced when fixing bug 1297363 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu14 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 2 18:32:31 2014 SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-03-20 (12 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301544 Title: cannot boot with latest systemd updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1301544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277552] Re: libpostproc52 does not support multiarch
Same issue there ** Also affects: vlc Importance: Undecided Status: New ** Also affects: mplayer Importance: Undecided Status: New ** Also affects: kaffeine Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277552 Title: libpostproc52 does not support multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/kaffeine/+bug/1277552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277552] Re: libpostproc52 does not support multiarch
Same issue there ** Changed in: libpostproc (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277552 Title: libpostproc52 does not support multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/kaffeine/+bug/1277552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
Hi, I was using aptitude to manage packages... ** Attachment added: term.log https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+attachment/4053212/+files/term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
Attached /var/log/dpkg.log ** Attachment added: dpkg.log https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+attachment/4053213/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
which pam-auth-update : /usr/sbin/pam-auth-update For the yabause-qt it's an error in /var/lib/dpkg/available, nothing unofficial. I've removed it from /var/lib/dpkg/available and the warning is gone. Probably some encoding issue. Output of my debsums (some errors but nothing looks really critical) : administrateur@pcathlon64:~$ sudo debsums -s [sudo] password for administrateur: debsums: invalid line (1) in md5sums for devolo-dlan-cockpit: /mnt/repository/kolja/dune/software-packages/cockpit/obj.linux.rel/tmp.DwmJybAOOr/debian /mnt/repository/kolja/dune/software-packages/cockpit/source.linux debsums: missing file /usr/lib/i386-linux-gnu/libgphoto2/print-camera-list (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/AUTHORS (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/NEWS.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/README.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.9050 (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.9051.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.9052 (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.905C.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.913C.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.913D (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.adc65 (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.agfa-cl20 (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.aox.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.ax203-compression.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.ax203.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.canon.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.clicksmart310 (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.enigma13 (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.gsmart300 (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.iclick.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.jamcam (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.jl2005a.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.jl2005bcd-compression.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.jl2005c.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.konica (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.lg_gsm (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.mars.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.minolta-dimagev (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.mustek (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.panasonic (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.panasonic-coolshot (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.panasonic-l859 (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.pccam300 (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.pccam600 (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.ptp2.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.smal (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.sonix.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.sonydscf1 (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.soundvision (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.spca50x.gz (from libgphoto2-2:i386 package) debsums: missing file /usr/share/doc/libgphoto2-2/camlibs/README.sq905.gz
[Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
Once I've removed libgphoto2-2 : ^Cadministrateur@pcathlon64:~$ sudo debsums -s [sudo] password for administrateur: debsums: invalid line (1) in md5sums for devolo-dlan-cockpit: /mnt/repository/kolja/dune/software-packages/cockpit/obj.linux.rel/tmp.DwmJybAOOr/debian /mnt/repository/kolja/dune/software-packages/cockpit/source.linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
Hi, I've logged out and logged in and my logind session is still in a working state. I've run sudo pam-auth-update --package and everything is fine. Attached file /etc/pam.d/common-session ** Attachment added: common-session https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+attachment/4049329/+files/common-session ** Changed in: systemd (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
Hi, After reinstalling libpam-systemd:i386 systemd-logind does not start anymore, however if I remove it it starts again. So the issue really lies within the mix libpam:i386 and libpam:amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
And after re-running sudo pam auto-update --package everything was OK again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break
OK so after rebooting I got the issue with the suspend feature. I attach you the updated common-session file ** Attachment added: common-session https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+attachment/4050139/+files/common-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: Installing i386 and amd64 PAM stacks causes shutdown/logout/etc. to break To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
However with the update (and a restart) I've seen that the suspend/restart/shutdown icons are still grayed out in my lightdm, and that the suspend menu is still missing from my KDE, but things are better ** Changed in: systemd (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
Hi, To answer your questions : 1/ julien@pcathlon64:~$ aptitude search libpam-systemd i libpam-systemd - system and service manager - PAM module i libpam-systemd:i386 - system and service manager - PAM module (I tried to reinstall it, does not fix the problem) 2/ administrateur@pcathlon64:~$ sudo start systemd-logind [sudo] password for administrateur: systemd-logind stop/pre-start, process 4754 And when I do then ps aux|grep 4754, no process is returned. In my syslog, I get the following message : Mar 27 08:08:09 pcathlon64 dbus[1280]: [system] Activating service name='org.freedesktop.login1' (using servicehelper) Mar 27 08:08:09 pcathlon64 dbus[1280]: [system] Activated service 'org.freedesktop.login1' failed: Cannot launch daemon, file not found or permissions invalid OK I've found the issue : 1/ remove libpam-systemd:i386 and libsystemd-login0:i386 Now everything should be fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
Hi, I had both libpam-systemd:i386 and libpam-sytemd:amd64 on my AMD64 system and this confused PAM. The upstart job now works fine, I don't have the cannot start daemon. I didn't post the result of sudo start systemd-logind but it said started daemon systemd-logind or something like this. And just after that reboot and shutdown menu entries appeared in KDE but not the suspend one. The only wrong things remaining is that I cannot suspend from the GUI (but restart and shutdown appear in the KDE menu) and from lightdm suspend/reboot/shutdown entries are still disabled even after rebooting, restarting lightdm or reinstalling it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
To avoid this, it might be possible to set some kind of conflict between the i386 module and the amd64 module ? OK it smells, but this might be an option. What do you think ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
Hi, I've also fixed the issue for the suspend feature and lightdm feature by removing packages libpam-modules:i386 and libpam-cap:i386, which have the same kind of conflict as explained above. I don't know what happened during the upgrade, but it looks like the upgrade tool was a bit lost between i386 and amd64 packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
I've also found this in my syslog : Mar 26 07:46:00 pcathlon64 dbus[1249]: [system] Activating service name='org.freedesktop.login1' (using servicehelper) Mar 26 07:46:00 pcathlon64 dbus[1249]: [system] Activated service 'org.freedesktop.login1' failed: Cannot launch daemon, file not found or permissions invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
Also tried with qdbus with the following line (as I'm using KDE) : qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanReboot Error: org.freedesktop.DBus.Error.Spawn.ExecFailed Cannot launch daemon, file not found or permissions invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
Another stuff in my auth.log which may help : Mar 26 21:13:14 pcathlon64 sudo: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so: Ne peut ouvrir le fichier d'objet p artagé: Aucun fichier ou dossier de ce type Mar 26 21:13:14 pcathlon64 sudo: PAM adding faulty module: pam_cap.so -- On every login -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
After installing pamcap in 64 bits message PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so disappeared, however the issue is still there. :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
Hi, When launching gdbus, error is : julien@pcathlon64:~$ gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.CanReboot Erreur : GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Cannot launch daemon, file not found or permissions invalid When trying to reboot : julien@pcathlon64:~$ gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.Reboot true Erreur : GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Cannot launch daemon, file not found or permissions invalid julien@pcathlon64:~$ loginctl Failed to issue method call: Cannot launch daemon, file not found or permissions invalid Actually I had a similar bug with Saucy which has been fixed with an update of logind (now replaced with systemd) ** Changed in: systemd (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002981] Re: Aptdaemon fails to start
Oh and from my lightdm logs I also get the following messages : QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon QDBusError(org.freedesktop.DBus.Error.Spawn.ExecFailed, Cannot launch daemon, file not found or permissions invalid) QDBusError(org.freedesktop.DBus.Error.Spawn.ExecFailed, Cannot launch daemon, file not found or permissions invalid) QDBusError(org.freedesktop.DBus.Error.Spawn.ExecFailed, Cannot launch daemon, file not found or permissions invalid) QDBusError(org.freedesktop.DBus.Error.Spawn.ExecFailed, Cannot launch daemon, file not found or permissions invalid) Don't know if it is related... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002981 Title: Aptdaemon fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1002981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
Oh and from my lightdm logs I also get the following messages : QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon QDBusError(org.freedesktop.DBus.Error.Spawn.ExecFailed, Cannot launch daemon, file not found or permissions invalid) QDBusError(org.freedesktop.DBus.Error.Spawn.ExecFailed, Cannot launch daemon, file not found or permissions invalid) QDBusError(org.freedesktop.DBus.Error.Spawn.ExecFailed, Cannot launch daemon, file not found or permissions invalid) QDBusError(org.freedesktop.DBus.Error.Spawn.ExecFailed, Cannot launch daemon, file not found or permissions invalid) Don't know if it is related... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002981] Re: Aptdaemon fails to start
Sorry posted comment to the wrong bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002981 Title: Aptdaemon fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1002981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
Hi, For the output, it gives me the following : administrateur@pcathlon64:~$ sudo /lib/systemd/systemd-logind [sudo] password for administrateur: Watching system buttons on /dev/input/event1 (Power Button) Watching system buttons on /dev/input/event0 (Power Button) New seat seat0. Failed to save seat data for seat0: No such file or directory However it does not crash... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
** Changed in: systemd (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
Attached file. ** Attachment added: logind.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+attachment/4043358/+files/logind.txt ** Changed in: systemd (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
** Also affects: lightdm Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296938] [NEW] After latest upgrades, Akonadi's MySQL CPU usage is extremely high
Public bug reported: Hi, I've upgraded to Ubuntu Trusty last week, and since the update to KDE 4.12.95 my CPU usage is extremely high. The culprit is akonadi's MySQL process, which eats a lot of my CPU. My system : AMD Phenom 9850 x4 8 GB RAM Kubuntu 14.04 AMD64 Note that I've got 12000 emails in my box, and that I did not notice it with KDE 4.12.90, nor with Kubuntu Saucy. Rgds, ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: akonadi-server 1.11.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Mar 24 21:25:52 2014 ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: akonadi UpgradeStatus: Upgraded to trusty on 2014-03-20 (4 days ago) ** Affects: akonadi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296938 Title: After latest upgrades, Akonadi's MySQL CPU usage is extremely high To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1296938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] Re: cannot shutdown/suspend/restart from the GUI
** Package changed: shadow (Ubuntu) = lightdm (Ubuntu) ** Package changed: lightdm (Ubuntu) = systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295521] [NEW] cannot shutdown/suspend/restart from the GUI
Public bug reported: Hi, After I upgraded to Ubuntu Trusty, I've seen that it is no longer possible to suspend/shutdown/restart my system from the GUI. In other words within lightdm buttons to do so are grayed out, and within KDE it is the same. I had the same bug in Saucy beta and the culprit was the login component, and after its upgrade the issue was fixed. My system : Kubuntu 14.04 LTS AMD64 AMD Phenom 9850 8 GB RAM NVidia GeForce 660 Ti w/ NVidia 331 driver ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: login 1:4.1.5.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Fri Mar 21 07:21:52 2014 ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: Upgraded to trusty on 2014-03-20 (0 days ago) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295521 Title: cannot shutdown/suspend/restart from the GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1295521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295835] [NEW] qdbus is missing dependency over qdbus-qt5
Public bug reported: HI, Steps to reproduce : DO : perform an upgrade of Kubuntu with latest updates of qdbus. DO : remark that package qdbus-qt5 is normally not installed. DO : logout of KDE DO : login into KDE EXPECT : login runs fine ACTUAL : cannot login within KDE, with message qdbus cannot be started Now install qdbus-qt5 and everything is working fine. Note that if that package is missing when trying to run qdbus from the command line it complains it is missing a qt5 qdbus. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qdbus 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Fri Mar 21 21:14:11 2014 ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: qt4-x11 UpgradeStatus: Upgraded to trusty on 2014-03-20 (0 days ago) ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1295835 Title: qdbus is missing dependency over qdbus-qt5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1295835/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1286836] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has m
Same there -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286836 Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1286836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280719] Re: Latest libglib-2.0-0 or libc updates break X.org startup or restore
Invalid, is actually due to a bug within my hardware which occurs after some suspend/resume cycles. ** Changed in: glib2.0 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280719 Title: Latest libglib-2.0-0 or libc updates break X.org startup or restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1280719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280719] [NEW] Latest libglib-2.0-0 or libc updates break X.org startup or restore
Public bug reported: Hi, After latest update of the following components from 2014-02-14 : libglib-2.0-0 and libc-bin my X.org always crashes when resuming from a suspend, causing a hard reboot. The strange thing is that the next reboot causes the same thing, and afterwards everything is OK again. Note that the HDD light seems to be always on. I've checked my HDD against smartmontools with long self tests and all is OK on this side. The same apply for my graphic card with some tests. My system : Kubuntu 13.10 AMD64 AMD Phenom x4 9850 Mobo Asus M2N-SLI Deluxe with NForce 570 SLI chipset (*) 8 GB RAM NVidia GeForce 660 Ti with 2 GB of RAM and NVidia 319 binary driver. (*) - for the suspend/restore, I use the workaround detailed within bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878 . However my computer starts a normal resume after a suspend, and freezes when the Xorg server appears. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libglib2.0-0 2.38.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 16 08:19:30 2014 MarkForUpload: True SourcePackage: glib2.0 UpgradeStatus: Upgraded to saucy on 2013-09-27 (141 days ago) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280719 Title: Latest libglib-2.0-0 or libc updates break X.org startup or restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1280719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268409] [NEW] Please change dependencies for Boinc Cuda package
Public bug reported: Hi, Currently boinc-nvidia-cuda package depends on nvidia-current package, which relies itself on nvidia-304 driver. This version is outdated, especially for users who are at the same time steam users. So please change the dependency requirements so that it depends on nvidia-304 | nvidia-319 | nvidia-310 . This may require some live compilation at the time of install, but this would be much better. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: boinc-nvidia-cuda (not installed) ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Jan 12 23:46:21 2014 MarkForUpload: True SourcePackage: boinc UpgradeStatus: Upgraded to saucy on 2013-09-27 (107 days ago) ** Affects: boinc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268409 Title: Please change dependencies for Boinc Cuda package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1268409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171560] Re: 10de:1183 Suspend to RAM is broken
Hi, So yes on the computer on which I reported the issue the issue is also reproducible with Nouveau driver. Discussion URL (actually kernel bug) : https://bugzilla.kernel.org/show_bug.cgi?id=48951 Rgds, ** Bug watch added: Linux Kernel Bug Tracker #48951 http://bugzilla.kernel.org/show_bug.cgi?id=48951 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171560 Title: 10de:1183 Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171560] Re: 10de:1183 Suspend to RAM is broken
Hi Christopher, No, this is completely unrelated to NVidia graphics. My father uses an Intel Core i5 CPU with B75 chipset and the nvidia graphics blob, and he's not affected. The culprit is the NForce driver, as explained in the kernel mailing list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171560 Title: 10de:1183 Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171560] Re: 10de:1183 Suspend to RAM is broken
Hi, With the workaround I provided the bug is not there, but without it it is still there. Now as this bug has many duplicates you can close it, but please at least provide the workaround in Ubuntu release notes. Rgds -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171560 Title: 10de:1183 Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171560] Re: 10de:1183 Suspend to RAM is broken
Hi Christopher, Yes this is exactly the case, the bug is still not fixed. But in case you couldn't fix it until trusty release just publish the workaround as a release note, as it targets a rather old chipset model. Rgds, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171560 Title: 10de:1183 Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244562] [NEW] Eclipse based apps crash with libgobject
Public bug reported: When I start any Eclipse-based app (from Eclipse 3.x branch) I got a crash with message : # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5a73ac528, pid=22497, tid=140418638948096 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try ulimit -c unlimited before starting Java again # # An error report file with more information is saved as: # /home/jaubin/dev/mercurial/referentiels/hs_err_pid22497.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # With Eclipse IDE the IDE starts but crashes randomly thereafter. With RCP apps the same happens. I've attached a crash log, which may not be the exact one reported in this bug, but which contains the same info. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libglib2.0-0 2.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 25 09:38:18 2013 InstallationDate: Installed on 2013-07-10 (106 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: Upgraded to saucy on 2013-10-16 (8 days ago) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: hs_err_pid21745.log https://bugs.launchpad.net/bugs/1244562/+attachment/3890762/+files/hs_err_pid21745.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244562 Title: Eclipse based apps crash with libgobject To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1244562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244562] Re: Eclipse based apps crash with libgobject
*** This bug is a duplicate of bug 1241101 *** https://bugs.launchpad.net/bugs/1241101 Hi, Actually I do not have smartgit.sh at all... Could you attach it to the bug please ? Rgds, ** This bug has been marked a duplicate of bug 1241101 Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244562 Title: Eclipse based apps crash with libgobject To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1244562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057664] Re: [Asus M2N-SLI Deluxe] Suspend to RAM not working
*** This bug is a duplicate of bug 1181878 *** https://bugs.launchpad.net/bugs/1181878 Hi Rachelle, Actually I've posted another bug related to this one, as linked in the report. There I provide a workaround to the bug (issued from kernel.org) Rgds, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057664 Title: [Asus M2N-SLI Deluxe] Suspend to RAM not working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1057664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057664] Re: [Asus M2N-SLI Deluxe] Suspend to RAM not working
*** This bug is a duplicate of bug 1181878 *** https://bugs.launchpad.net/bugs/1181878 Hi, Actually I'm not using any longer i386 release on this computer, but it is not fixed either on AMD64. Bug this bug is a duplicate of bug 1237058 and marking it as duplicate (I provide a workaround in this bug) Rgds, Julien. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057664 Title: [Asus M2N-SLI Deluxe] Suspend to RAM not working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1057664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057664] Re: [Asus M2N-SLI Deluxe] Suspend to RAM not working
*** This bug is a duplicate of bug 1181878 *** https://bugs.launchpad.net/bugs/1181878 Sorry, the bug is actually not a duplicate. ** This bug has been marked a duplicate of bug 1181878 [M2N-SLI DELUXE] Plugging in Western Digital Caviar Black 500 GB / 1 TB prevents suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057664 Title: [Asus M2N-SLI Deluxe] Suspend to RAM not working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1057664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237058] Re: Computer freezes after resume
Not a bug, or fixed with kernel 3.11-12. The issue could also deal with my computer, which becomes sometimes unstable after having been switched on for quite a long time through a suspend/resume cycle, until I shut it down completely for a couple of hours. ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237058 Title: Computer freezes after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237058] [NEW] Computer freezes after resume
Public bug reported: Hi, I've noticed that after a resume, my computer often freezes or becomes unstable, forcing me to reboot. The regression occured after update to kernel 3.11.0-11-generic, and I've set the following line in my /etc/rc.local as a WA for bug 1181878 : echo 0 /sys/power/pm_async Otherwise my computer is not able to suspend at all. Bug was not present with kernel 3.11.0-9-generic My system : AMD Phenom 9850 M2N-SLI Deluxe (w/ chipset NForce 570) 8 GB RAM Nvidia GeForce 660Ti with driver NVidia-319 Kernel AMD64 Important notice : the bug does not occur if you suspend/resume just for a couple of seconds, but for a longer time it's almost always there... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-11-generic 3.11.0-11.17 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC1: julien 3693 F pulseaudio  /dev/snd/controlC0: julien 3693 F pulseaudio  /dev/snd/pcmC0D0p: julien 3693 F...m pulseaudio CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw' Date: Tue Oct 8 22:28:41 2013 HibernationDevice: RESUME=UUID=1e2e6306-5da1-44ae-98dd-d137e96a8425 IwConfig:  eth0 no wireless extensions.  eth1 no wireless extensions.  lono wireless extensions. Lsusb:  Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  Bus 002 Device 006: ID 046d:0928 Logitech, Inc. QuickCam Express  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=53dfbfeb-5955-48e2-9039-e6c3b9b219d0 ro ro quiet splash RelatedPackageVersions:  linux-restricted-modules-3.11.0-11-generic N/A  linux-backports-modules-3.11.0-11-generic N/A  linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-27 (10 days ago) WpaSupplicantLog: dmi.bios.date: 10/02/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1701 dmi.board.name: M2N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision1701:bd10/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Description changed: Hi, I've noticed that after a resume, my computer often freezes or becomes unstable, forcing me to reboot. The regression occured after update to kernel 3.11.0-11-generic, and I've set the following line in my /etc/rc.local as a WA for bug 1181878 : echo 0 /sys/power/pm_async Otherwise my computer is not able to suspend at all. Bug was not present with kernel 3.11.0-9-generic My system : AMD Phenom 9850 M2N-SLI Deluxe (w/ chipset NForce 570) 8 GB RAM Nvidia GeForce 660Ti with driver NVidia-319 Kernel AMD64 + Important notice : the bug does not occur if you suspend/resume just for + a couple of seconds, but for a longer time it's almost always there... + ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-11-generic 3.11.0-11.17 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: julien 3693 F pulseaudio - /dev/snd/controlC0: julien 3693 F pulseaudio - /dev/snd/pcmC0D0p: julien 3693 F...m pulseaudio +  USERPID ACCESS COMMAND +  /dev/snd/controlC1: julien 3693 F pulseaudio +  /dev/snd/controlC0: julien 3693 F pulseaudio +  /dev/snd/pcmC0D0p: julien 3693 F...m pulseaudio CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw' Date: Tue Oct 8 22:28:41 2013 HibernationDevice: RESUME=UUID=1e2e6306-5da1-44ae-98dd-d137e96a8425 IwConfig: - eth0 no wireless extensions. - - eth1 no wireless extensions. - - lono wireless extensions. +  eth0 no wireless extensions. + +  eth1 no wireless extensions. + +  lono wireless extensions. Lsusb: - Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Flash Card
[Bug 1181878] Re: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
Hi, I've unfortunately no way to get back that early, but the offending commit is listed in the bug report I've mentioned on kernel.org, see : http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=966f1212e1ac5fe3ddf04479d21488ddb36a2608 Rgds, ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181878 Title: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181878] Re: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
Hi, The bug never occured before Quantal. It has been a regression introduced with kernel 3.4 or 3.5 if I recall well (version mentioned in the bug report on kernel.org) Rgds, ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181878 Title: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232357] Re: lightdm (kde) : shutdown, reboot and suspend grayed out
Invalidated the ticket as it was related to a faultly logind shipped with systemd packages, and after update of it everything is fine again. ** No longer affects: lightdm ** Changed in: lightdm (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232357 Title: lightdm (kde) : shutdown, reboot and suspend grayed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1232357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232295] Re: pulse audio does not restore sound after suspend
pactl stat before ** Attachment added: pactl_stat_after https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+attachment/3851750/+files/pactl_stat_after -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232295 Title: pulse audio does not restore sound after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232295] Re: pulse audio does not restore sound after suspend
My pulse audio log file. I've noticed that I just need to kill PA. Phonon restarts it automatically. ** Attachment added: pulseverbose.log https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+attachment/3851747/+files/pulseverbose.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232295 Title: pulse audio does not restore sound after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232295] Re: pulse audio does not restore sound after suspend
I couldn'nt upgrade to latest adi driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232295 Title: pulse audio does not restore sound after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232295] Re: pulse audio does not restore sound after suspend
pactl list after ** Attachment added: pactl_list_after https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+attachment/3851749/+files/pactl_list_after -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232295 Title: pulse audio does not restore sound after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232295] Re: pulse audio does not restore sound after suspend
My system log from suspend to resume : Sep 30 20:39:01 pcathlon64 CRON[5976]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] [ -x /usr/lib/php5/sessionclean ] [ -d /var/lib/php5 ] /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)) Sep 30 20:39:21 pcathlon64 anacron[6099]: Anacron 2.3 started on 2013-09-30 Sep 30 20:39:21 pcathlon64 anacron[6099]: Normal exit (0 jobs run) Sep 30 20:39:46 pcathlon64 rtkit-daemon[3446]: The canary thread is apparently starving. Taking action. Sep 30 20:39:46 pcathlon64 rtkit-daemon[3446]: Demoting known real-time threads. Sep 30 20:39:46 pcathlon64 rtkit-daemon[3446]: Successfully demoted thread 5957 of process 5949 (n/a). Sep 30 20:39:46 pcathlon64 rtkit-daemon[3446]: Successfully demoted thread 5956 of process 5949 (n/a). Sep 30 20:39:46 pcathlon64 rtkit-daemon[3446]: Successfully demoted thread 5955 of process 5949 (n/a). Sep 30 20:39:46 pcathlon64 rtkit-daemon[3446]: Successfully demoted thread 5949 of process 5949 (n/a). Sep 30 20:39:46 pcathlon64 rtkit-daemon[3446]: Demoted 4 threads. Sep 30 20:39:46 pcathlon64 kernel: [ 6937.695767] PM: Syncing filesystems ... done. Sep 30 20:39:46 pcathlon64 kernel: [ 6937.833428] PM: Preparing system for mem sleep Sep 30 20:39:46 pcathlon64 kernel: [ 6937.833645] Freezing user space processes ... (elapsed 0.002 seconds) done. Sep 30 20:39:46 pcathlon64 kernel: [ 6937.836260] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Sep 30 20:39:46 pcathlon64 kernel: [ 6937.837610] PM: Entering mem sleep Sep 30 20:39:46 pcathlon64 kernel: [ 6937.837630] Suspending console(s) (use no_console_suspend to debug) Sep 30 20:39:46 pcathlon64 kernel: [ 6937.838025] sd 7:0:0:0: [sdh] Synchronizing SCSI cache Sep 30 20:39:46 pcathlon64 kernel: [ 6937.838235] sd 7:0:0:0: [sdh] Stopping disk Sep 30 20:39:46 pcathlon64 kernel: [ 6938.896994] sd 6:0:0:0: [sdc] Synchronizing SCSI cache Sep 30 20:39:46 pcathlon64 kernel: [ 6938.897158] sd 6:0:0:0: [sdc] Stopping disk Sep 30 20:39:46 pcathlon64 kernel: [ 6939.716103] sd 3:0:0:0: [sdb] Synchronizing SCSI cache Sep 30 20:39:46 pcathlon64 kernel: [ 6939.716240] sd 3:0:0:0: [sdb] Stopping disk Sep 30 20:39:46 pcathlon64 kernel: [ 6940.379985] sd 2:0:0:0: [sda] Synchronizing SCSI cache Sep 30 20:39:46 pcathlon64 kernel: [ 6940.380106] sd 2:0:0:0: [sda] Stopping disk Sep 30 20:39:46 pcathlon64 kernel: [ 6940.836536] i8042 kbd 00:0b: System wakeup enabled by ACPI Sep 30 20:39:46 pcathlon64 kernel: [ 6940.836557] i8042 aux 00:0a: System wakeup disabled by ACPI Sep 30 20:39:46 pcathlon64 kernel: [ 6940.836659] parport_pc 00:09: disabled Sep 30 20:39:46 pcathlon64 kernel: [ 6940.836766] serial 00:08: disabled Sep 30 20:39:46 pcathlon64 kernel: [ 6940.836769] serial 00:08: System wakeup disabled by ACPI Sep 30 20:39:46 pcathlon64 kernel: [ 6941.243328] PM: suspend of devices complete after 3402.997 msecs Sep 30 20:39:46 pcathlon64 kernel: [ 6941.243638] PM: late suspend of devices complete after 0.306 msecs Sep 30 20:39:46 pcathlon64 kernel: [ 6941.243871] forcedeth :00:09.0: System wakeup enabled by ACPI Sep 30 20:39:46 pcathlon64 kernel: [ 6941.259047] forcedeth :00:08.0: System wakeup enabled by ACPI Sep 30 20:39:46 pcathlon64 kernel: [ 6941.275079] ehci-pci :00:02.1: System wakeup enabled by ACPI Sep 30 20:39:46 pcathlon64 kernel: [ 6941.291063] ohci-pci :00:02.0: System wakeup enabled by ACPI Sep 30 20:39:46 pcathlon64 kernel: [ 6941.307153] PM: noirq suspend of devices complete after 63.468 msecs Sep 30 20:39:46 pcathlon64 kernel: [ 6941.307393] ACPI: Preparing to enter system sleep state S3 Sep 30 20:39:46 pcathlon64 kernel: [ 6941.308070] PM: Saving platform NVS memory Sep 30 20:39:46 pcathlon64 kernel: [ 6941.308098] Disabling non-boot CPUs ... Sep 30 20:39:46 pcathlon64 kernel: [ 6941.411131] smpboot: CPU 1 is now offline Sep 30 20:39:46 pcathlon64 kernel: [ 6941.515203] smpboot: CPU 2 is now offline Sep 30 20:39:46 pcathlon64 kernel: [ 6941.619270] smpboot: CPU 3 is now offline Sep 30 20:39:46 pcathlon64 kernel: [ 6941.620472] ACPI: Low-level resume complete Sep 30 20:39:46 pcathlon64 kernel: [ 6941.620537] PM: Restoring platform NVS memory Sep 30 20:39:46 pcathlon64 kernel: [ 6941.621981] PCI-DMA: Resuming GART IOMMU Sep 30 20:39:46 pcathlon64 kernel: [ 6941.621981] PCI-DMA: Restoring GART aperture settings Sep 30 20:39:46 pcathlon64 kernel: [ 6941.622303] LVT offset 0 assigned for vector 0xf9 Sep 30 20:39:46 pcathlon64 kernel: [ 6941.622309] microcode: CPU0: new patch_level=0x0183 Sep 30 20:39:46 pcathlon64 kernel: [ 6941.622349] Enabling non-boot CPUs ... Sep 30 20:39:46 pcathlon64 kernel: [ 6941.622386] smpboot: Booting Node 0 Processor 1 APIC 0x1 Sep 30 20:39:46 pcathlon64 kernel: [ 6941.633356] [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu Sep 30 20:39:46 pcathlon64 kernel: [ 6941.633357] perf: IBS APIC
[Bug 1232295] Re: pulse audio does not restore sound after suspend
pactl stat after ** Attachment added: pactl_stat_after https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+attachment/3851751/+files/pactl_stat_after ** Changed in: pulseaudio (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232295 Title: pulse audio does not restore sound after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232295] Re: pulse audio does not restore sound after suspend
pactl list before ** Attachment added: pactl_list_before https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+attachment/3851748/+files/pactl_list_before -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232295 Title: pulse audio does not restore sound after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232357] Re: lightdm (kde) : shutdown, reboot and suspend grayed out
This might be a policykit rule issue : https://bugzilla.redhat.com/show_bug.cgi?id=872797 ** Also affects: lightdm Importance: Undecided Status: New ** Bug watch added: Red Hat Bugzilla #872797 https://bugzilla.redhat.com/show_bug.cgi?id=872797 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232357 Title: lightdm (kde) : shutdown, reboot and suspend grayed out To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1232357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181878] Re: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
Hi, bug is still there with upstream... :-( ** Tags removed: needs-upstream-testing ** Tags added: kernel-bug-exists-upstream-v3.12 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181878 Title: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232357] [NEW] lightdm (kde) : shutdown, reboot and suspend grayed out
Public bug reported: Hi, I'm using lightdm with KDE team on Kubuntu Saucy. When you click the shutdown button within Lightdm interface, the shutdown, reboot and suspend buttons are actually grayed out so one could not reboot without using command line. Thus, it's impossible to do the same operations from within KDE as they turn out to be a simple disconnect, and the suspend menu entry is also missing from KDE menu. Rgds ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.17-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Sep 28 08:09:36 2013 MarkForUpload: True ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to saucy on 2013-09-27 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232357 Title: lightdm (kde) : shutdown, reboot and suspend grayed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1232357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232361] [NEW] after upgrade from raring, akonadi consumes a lot of CPU
Public bug reported: Hello, I've a Kubuntu install from Kubuntu raring, and after upgrading Akonadi (more specifically MySQL) started to eat a lot of CPU. Actually after resetting Akonadi everything went fine, i.e. shutting down Akonadi and Kontact, removing folder ~/.local/share/akonadi, restarting Akonadi and afterwards Kontact. I also add that I have 10k+ emails within Kontact. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: akonadi-server 1.10.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Sep 28 08:24:53 2013 MarkForUpload: True ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: akonadi UpgradeStatus: Upgraded to saucy on 2013-09-27 (0 days ago) ** Affects: akonadi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232361 Title: after upgrade from raring, akonadi consumes a lot of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1232361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232362] [NEW] libc6 breaks saucy upgrade from raring
Public bug reported: Hi, I'm using Kubuntu 13.10 saucy 64-bits, upgraded yesterday from Raring. During the upgrade, I got a message which broke the complete update, i.e. libc6 failed to configure because it could not replace files within /lib64, complaining with an error message like this : A copy of the C library was found in an unexpected directory: '/lib/x86_64-linux-gnu/libc-2.17.so' It is not safe to upgrade the C library in this situation; please remove that copy of the C library or get it out of '/lib/x86_64-linux-gnu' and try again. I could save my upgrade with a liveCD, removing the offending files, expanding the right libc with dpkg-deb -x, chrooting and running apt-get install -f. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libc6 2.17-93ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Sep 28 08:29:25 2013 Dependencies: gcc-4.8-base 4.8.1-10ubuntu4 libc6 2.17-93ubuntu1 libgcc1 1:4.8.1-10ubuntu4 multiarch-support 2.17-93ubuntu1 MarkForUpload: True ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: eglibc UpgradeStatus: Upgraded to saucy on 2013-09-27 (0 days ago) ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232362 Title: libc6 breaks saucy upgrade from raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1232362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181878] Re: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
Hi, Tested with kernel 3.11 after upgrading to saucy, and unfortunately this does not fix the bug. :-( ** Tags removed: kernel-bug-exists-upstream-v3.10-rc2 needs-upstream-testing ** Tags added: kernel-bug-exists-upstream-v3.11 saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181878 Title: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1232295] [NEW] pulse audio does not restore sound after suspend
Public bug reported: DO : log in (at least within KDE). DO : open an app which plays sound, and listen to sound. DO : stop the app started in previous step. DO : suspend DO : after resume, reopen the app, and try to play sound. EXPECT : sound appears, and you can listen to it. ACTUAL : sound does not work until pulseaudio is killed and restarted. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julien14059 F pulseaudio /dev/snd/controlC0: julien14059 F pulseaudio /dev/snd/pcmC0D0p: julien14059 F...m pulseaudio Date: Sat Sep 28 00:59:01 2013 MarkForUpload: True ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-09-27 (0 days ago) dmi.bios.date: 10/02/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1701 dmi.board.name: M2N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision1701:bd10/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1232295 Title: pulse audio does not restore sound after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1232295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171560] Re: Suspend to RAM is broken
Hi, Actually this is corresponds to Kernel bug #48951. Workaround is as follows : - Put in /etc/rc.d the following line (before exit 0) : echo 0 /sys/power/pm_async This works. The issue is related to NVidia MCP55 chipset. Rgds -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171560 Title: Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181878] Re: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
Hi, Here's a workaround for the bug, from kernel.org bug mentioned above : - Run as root : echo 0 /sys/power/pm_async (added to /etc/rc.local to be permanent) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181878 Title: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181878] Re: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181878 Title: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181878] Re: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
Hi, The kernel bug actually exists upstream, which is not surprising as the bug I referenced is marked as won't fix. However it turns out that there's one 1-line offending commit which broke everything, as stated in comment #10 of the bug. The commit is : http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=966f1212e1ac5fe3ddf04479d21488ddb36a2608 I can try a patched 3.8.0-xx kernel packaged for Ubuntu Raring with this fix, in order to test. Rgds, Julien. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181878 Title: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181878] Re: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
I've remarked that the change to udev rules proposed as a workaround
does not work, since attribute power/async is not even present under the
/sys tree.
My output for udevinfo for one of my HDDs :
administrateur@pcathlon64:~$ sudo udevadm info -a -p /sys/block/sda
[sudo] password for administrateur:
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device
'/devices/pci:00/:00:05.0/ata1/host0/target0:0:0/0:0:0:0/block/sda':
KERNEL==sda
SUBSYSTEM==block
DRIVER==
ATTR{ro}==0
ATTR{size}==1953525168
ATTR{stat}== 43323 186686 3049670 698632 4428 7667 293952
819040 144364 780504
ATTR{range}==16
ATTR{discard_alignment}==0
ATTR{events}==
ATTR{ext_range}==256
ATTR{events_poll_msecs}==-1
ATTR{alignment_offset}==0
ATTR{inflight}== 00
ATTR{removable}==0
ATTR{capability}==50
ATTR{events_async}==
looking at parent device
'/devices/pci:00/:00:05.0/ata1/host0/target0:0:0/0:0:0:0':
KERNELS==0:0:0:0
SUBSYSTEMS==scsi
DRIVERS==sd
ATTRS{rev}==05.0
ATTRS{type}==0
ATTRS{scsi_level}==6
ATTRS{model}==WDC WD1002FAEX-0
ATTRS{state}==running
ATTRS{queue_type}==simple
ATTRS{iodone_cnt}==0xbfa2
ATTRS{iorequest_cnt}==0xc6b7
ATTRS{queue_ramp_up_period}==12
ATTRS{timeout}==30
ATTRS{evt_media_change}==0
ATTRS{ioerr_cnt}==0x12
ATTRS{queue_depth}==31
ATTRS{vendor}==ATA
ATTRS{device_blocked}==0
ATTRS{iocounterbits}==32
looking at parent device
'/devices/pci:00/:00:05.0/ata1/host0/target0:0:0':
KERNELS==target0:0:0
SUBSYSTEMS==scsi
DRIVERS==
looking at parent device '/devices/pci:00/:00:05.0/ata1/host0':
KERNELS==host0
SUBSYSTEMS==scsi
DRIVERS==
looking at parent device '/devices/pci:00/:00:05.0/ata1':
KERNELS==ata1
SUBSYSTEMS==
DRIVERS==
looking at parent device '/devices/pci:00/:00:05.0':
KERNELS==:00:05.0
SUBSYSTEMS==pci
DRIVERS==sata_nv
ATTRS{irq}==21
ATTRS{subsystem_vendor}==0x1043
ATTRS{broken_parity_status}==0
ATTRS{class}==0x010185
ATTRS{consistent_dma_mask_bits}==32
ATTRS{dma_mask_bits}==32
ATTRS{local_cpus}==,,,,,,,000f
ATTRS{device}==0x037f
ATTRS{enable}==1
ATTRS{msi_bus}==
ATTRS{local_cpulist}==0-3
ATTRS{vendor}==0x10de
ATTRS{subsystem_device}==0x8239
ATTRS{numa_node}==0
ATTRS{d3cold_allowed}==1
looking at parent device '/devices/pci:00':
KERNELS==pci:00
SUBSYSTEMS==
DRIVERS==
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1181878
Title:
Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent
suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057664] Re: Suspend to RAM is broken
Workaround there : http://ubuntuforums.org/showthread.php?t=1978290 It'd be very nice that it is included within package pm-utils at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057664 Title: Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1057664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171560] Re: Suspend to RAM is broken
Found actual workaround there : http://ubuntuforums.org/showthread.php?t=1978290 Maybe it should be included in the default pm-utils package, as it seems to be a fairly common issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171560 Title: Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181878] Re: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
After re-reading the bug report I found out that the HDD brand there is not the culprit, as /dev/sdd points to a WD Caviar Blue. Anyway there's something fishy with the HDD driver there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181878 Title: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181878] [NEW] Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
Public bug reported:
This bug is actually related to bugs 1057664 and 1171560, and is an
upstream bug.
When I suspend my system to RAM, actually suspend does not work and
instead I get a blinking cursor, and after some time system turns back
again.
After some debugging, I've found this within the logs of dmesg :
[ 3476.964420] Suspending console(s) (use no_console_suspend to debug)
[ 3476.964837] sd 7:0:0:0: [sdd] Synchronizing SCSI cache
[ 3476.964860] sd 6:0:0:0: [sdc] Synchronizing SCSI cache
[ 3476.964952] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
[ 3476.964964] sd 2:0:0:0: [sda] Synchronizing SCSI cache
[ 3476.965068] sd 6:0:0:0: [sdc] Stopping disk
[ 3476.965087] sd 7:0:0:0: [sdd] Stopping disk
[ 3476.965121] sd 3:0:0:0: [sdb] Stopping disk
[ 3476.965141] sd 2:0:0:0: [sda] Stopping disk
[ 3476.982377] i8042 kbd 00:0b: System wakeup enabled by ACPI
[ 3476.982396] i8042 aux 00:0a: System wakeup disabled by ACPI
[ 3476.982486] parport_pc 00:09: disabled
[ 3476.982582] serial 00:08: disabled
[ 3476.982585] serial 00:08: System wakeup disabled by ACPI
[ 3507.790314] ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 3507.790320] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 3507.790322] ata8.00: failed command: STANDBY IMMEDIATE
[ 3507.790324] ata3.00: failed command: STANDBY IMMEDIATE
[ 3507.790329] ata8.00: cmd e0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 3507.790329] res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 3507.790334] ata3.00: cmd e0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 3507.790334] res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 3507.790335] ata8.00: status: { DRDY }
[ 3507.790337] ata3.00: status: { DRDY }
[ 3507.790339] ata8: hard resetting link
[ 3507.790340] ata8: nv: skipping hardreset on occupied port
[ 3507.790341] ata3: hard resetting link
[ 3507.790342] ata3: nv: skipping hardreset on occupied port
[ 3508.257491] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3508.257493] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3508.273615] ata8.00: configured for UDMA/133
[ 3508.273618] ata8.00: device reported invalid CHS sector 0
[ 3508.273629] ata8: EH complete
[ 3508.273634] sd 7:0:0:0: [sdd] START_STOP FAILED
[ 3508.273636] sd 7:0:0:0: [sdd]
[ 3508.273637] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 3508.273638] sd 7:0:0:0: [sdd]
[ 3508.273640] Sense Key : Aborted Command [current] [descriptor]
[ 3508.273642] sd 7:0:0:0: [sdd]
[ 3508.273643] Add. Sense: No additional sense information
[ 3508.273652] dpm_run_callback(): scsi_bus_suspend+0x0/0x40 returns 134217730
[ 3508.273657] PM: Device 7:0:0:0 failed to suspend async: error 134217730
[ 3508.273696] ata3.00: configured for UDMA/133
[ 3508.273698] ata3.00: device reported invalid CHS sector 0
[ 3508.273704] ata3: EH complete
[ 3508.273714] sd 2:0:0:0: [sda] START_STOP FAILED
[ 3508.273717] sd 2:0:0:0: [sda]
[ 3508.273718] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 3508.273720] sd 2:0:0:0: [sda]
[ 3508.273722] Sense Key : Aborted Command [current] [descriptor]
[ 3508.273723] sd 2:0:0:0: [sda]
[ 3508.273724] Add. Sense: No additional sense information
[ 3508.273734] dpm_run_callback(): scsi_bus_suspend+0x0/0x40 returns 134217730
[ 3508.273739] PM: Device 2:0:0:0 failed to suspend async: error 134217730
[ 3508.273787] PM: Some devices failed to suspend
The command sent to trigger these logs was :
echo 'mem' /sys/power/state
With pm-suspend they do not appear.
On my system, devices sda and sdc actually point to HDDs WD Caviar Black
with firmware 05.01D05. sdb and sdd point to other HDD models, not these
ones. And it turns out that I get errors with these specific devices,
sda and sdc. The bug is not always reproducible, sometimes suspend goes
well, but sometimes it doesn't. I suspect there's something wrong with
the commands sent to these devices.
The bug started to be reproducible with Ubuntu 12.10, prior to this
while I already owned these HDDs. The HDDs themselves are not culprit as
the suspend command works on MS Windows 7. And my configuration is also
not culprit as I tested with a raring liveCD and the result is the same.
I don't know who must be contacted in the kernel team in order to look
at this issue, if you could indicate me who this would help.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-21-generic 3.8.0-21.32
ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
Uname: Linux 3.8.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: julien 3629 F pulseaudio
/dev/snd/controlC0: julien 3629 F pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'iw'
Date: Mon May 20 01:48:34 2013
HibernationDevice: RESUME=UUID=1e2e6306-5da1-44ae-98dd-d137e96a8425
IwConfig:
eth0 no wireless extensions.
eth1 no
[Bug 1181878] Re: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
Actually this looks like a NVidia MCP5x bug, as explained there : http://marc.info/?l=linux-idem=136297331308023w=2 ** Bug watch added: Linux Kernel Bug Tracker #48951 http://bugzilla.kernel.org/show_bug.cgi?id=48951 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181878 Title: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181878] Re: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend
Seems to be related to this bug : https://bugzilla.kernel.org/show_bug.cgi?id=48951 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181878 Title: Driver for hdd Western Digital Caviar Black 500 GB / 1 TB prevent suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057664] Re: Suspend to RAM is broken
I upgraded my system to 64-bit and the bug no longer occurs (even without formatting). So I've very strong suspicion around something PAE- related... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057664 Title: Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1057664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1154660] Re: [LENOVO 7465CTO] suspend/resume failure
Same issue there. Maybe this is related to bug 1171560 which I affected to the kernel. Maybe this is a mistake. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1154660 Title: [LENOVO 7465CTO] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171560] Re: Suspend to RAM is broken
** Attachment added: Attached my pm-suspend.log file https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171560/+attachment/3650789/+files/pm-suspend.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171560 Title: Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171560] [NEW] Suspend to RAM is broken
Public bug reported: Hi, On my computer suspend to RAM is actually broken. Here's my system : AMD Phenom x4 9850 8 GB RAM Kubuntu Raring 32bits w/ PAE GeForce 660 Ti with NVidia 304 driver Actually when I suspend the OS to RAM a blinking cursor appears but the process is halted and the computer does not respond until a hard reboot is performed. Also tested with kernel 3.9rc6 and same behaviour happens, so it looks like an upstream bug. I think the regression actually occurred between Precise and Quantal, as under Precise things went smoothly while under Quantal behaviour as above occurred. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: julien 5770 F pulseaudio /dev/snd/controlC0: julien 5770 F pulseaudio /dev/snd/pcmC0D0p: julien 5770 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Apr 22 19:37:18 2013 HibernationDevice: RESUME=UUID=1e2e6306-5da1-44ae-98dd-d137e96a8425 IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lsusb: Bus 002 Device 002: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter Bus 002 Device 003: ID 046d:0928 Logitech, Inc. QuickCam Express Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name MarkForUpload: True ProcFB: ProcKernelCmdLine: root=UUID=53dfbfeb-5955-48e2-9039-e6c3b9b219d0 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-07 (14 days ago) WifiSyslog: WpaSupplicantLog: dmi.bios.date: 10/02/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1701 dmi.board.name: M2N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision1701:bd10/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171560 Title: Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171560] Re: Suspend to RAM is broken
Yes I'm also convinced it is an upstream bug. However I don't know which driver is faultly. I only know the following elements : - NVidia binary driver is not faultly. (I could test the same driver on another NVidia card and suspend fully worked) - None of my USB devices seem to be faultly (tried to unplug my webcam, but this did not change anything. Same thing with my Xbox controller) - The HP print driver is not faulty, other computers I have with the same driver running do not have the problem. - I suspect stg wrong with either the driver of my chipset, an NForce 570 SLI, or maybe the Sata controller driver, a JMicron XXX, as when I suspend the first hard disk (sda) is suspended but not the other ones. (I could test it with rebooting my computer and the first hard disk was not even recognized by my BIOS until I completely switched off the computer) Could you help me on that point please ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171560 Title: Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057664] Re: Suspend to RAM is broken
** Bug watch added: Email to joseph.salisbury@canonical # mailto:joseph.salisb...@canonical.com ** Also affects: linux via mailto:joseph.salisb...@canonical.com Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057664 Title: Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1057664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057664] Re: Suspend to RAM is broken
Added file pm-suspend.log. You can see suspend attempts before and after my upgrade, all failed actually. ** Attachment added: pm-suspend.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1057664/+attachment/3643229/+files/pm-suspend.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057664 Title: Suspend to RAM is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1057664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166988] Re: With latest xserver-xorg update, switching to VT does not work anymore
The issue was actually due to a combination of NVidia 304.XX driver with linux-image-3.8.0-17-generic. With latest NVidia 304 driver update, problem is gone. However this could be good that nvidia-current actually points to nvidia-310 instead of NVidia-304, but with latest kernel image NVidia-310 could not install... ** Changed in: linux (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166988 Title: With latest xserver-xorg update, switching to VT does not work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166988] Re: With latest xserver-xorg update, switching to VT does not work anymore
After remembering the history around this bug, this looks much more like a kernel bug than an xorg bug, as I've remarked the first black screen after upgrading to kernel 3.8.0-17. ** Package changed: xorg (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166988 Title: With latest xserver-xorg update, switching to VT does not work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166988] Re: With latest xserver-xorg update, switching to VT does not work anymore
Hi, Kernel bug exists upstream, actually. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166988 Title: With latest xserver-xorg update, switching to VT does not work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1166988] Re: With latest xserver-xorg update, switching to VT does not work anymore
I also highlight the point that the bug did not appear with kernel image 3.8.0-16. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1166988 Title: With latest xserver-xorg update, switching to VT does not work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
