[Touch-packages] [Bug 1441253] Re: hanging suspend job prevents shutdown
Had a couple of reports of this on System76 Machines. It appears this is manifests as an incomplete resume, where some job in the resume doesn't terminate, leading systemd to think the machine is still resuming, while at the same time the system appears to be up and running normally. This is a very frustrating problem for our users, because it prevents them from cleanly shutting down their computer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1441253 Title: hanging suspend job prevents shutdown Status in systemd package in Ubuntu: Won't Fix Bug description: poweroff (systemd poweroff) and reboot no longer work running sudo sytemd poweroff generates this: Failed to start poweroff.target: Transaction is destructive. journal log also shows: Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive. Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Output of systemctl list-jobs JOB UNITTYPE STATE 6009 suspend.target start waiting 6010 systemd-suspend.service start running 6014 anacron-resume.service start waiting ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Tue Apr 7 18:32:27 2015 MachineType: Hewlett-Packard HP EliteBook 8560w ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic root=UUID=90fa42f5-708d-4432-9241-315b9c08ba98 ro nomodeset rootflags=subvol=@ SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2015-03-02 (36 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441253] Re: hanging suspend job prevents shutdown
Had a couple of reports of this on System76 Machines. It appears this is manifests as an incomplete resume, where some job in the resume doesn't terminate, leading systemd to think the machine is still resuming, while at the same time the system appears to be up and running normally. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1441253 Title: hanging suspend job prevents shutdown Status in systemd package in Ubuntu: Won't Fix Bug description: poweroff (systemd poweroff) and reboot no longer work running sudo sytemd poweroff generates this: Failed to start poweroff.target: Transaction is destructive. journal log also shows: Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive. Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Output of systemctl list-jobs JOB UNITTYPE STATE 6009 suspend.target start waiting 6010 systemd-suspend.service start running 6014 anacron-resume.service start waiting ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Tue Apr 7 18:32:27 2015 MachineType: Hewlett-Packard HP EliteBook 8560w ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic root=UUID=90fa42f5-708d-4432-9241-315b9c08ba98 ro nomodeset rootflags=subvol=@ SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2015-03-02 (36 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Second affected system ** Attachment added: "cpuinfo-silw.txt" https://bugs.launchpad.net/oem-priority/+bug/1564156/+attachment/4640787/+files/cpuinfo-silw.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: New Status in System76: Triaged Status in llvm-toolchain-3.8 package in Ubuntu: In Progress Status in mesa package in Ubuntu: New Bug description: Currently it's impossible to install from xenial-desktop-amd64.iso on a wide range of hardware with Nvidia GPUs. The problem is invalid opcode(s) when using llvmpipe (the software opengl fallback, used when using Unity with the Nouveau driver). The result is that compiz crashes over and over; Upstart will continue to restart compiz till it gives up. To confirm whether this bug is happening, switch to a VT and check dmesg, in which you'll see something like: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 A workable solution seems to be to re-build mesa against llvm-3.6-dev, libclang-3.6-dev (rather that 3.8). This would get us a working Xenial ISO for the effected hardware. Post 16.04 release, this could be revisited, and mesa in Xenial could possibly switch back to llvm 3.8 once this issue is resolved. I have mesa test packages built against llvm 3.6 here: https://launchpad.net/~jderose/+archive/ubuntu/mesa/+packages I couldn't test the installation without a re-spun ISO, but I did confirm that after updating to the mesa packages in my PPA, I could again use Unity. So I'm pretty sure this will fix installing from the ISO as well. My hunch is that llvm 3.8 is generating invalid code during its JIT compilation for llvmpipe, but it could also be the result of memory corruption. Either way, building mesa against llvm 3.6 seems to be quick the fix. Note this is a regression from 14.04.4 and 15.10, both of which install fine on the hardware effected by this bug. For concrete examples of System76 hardware effected by this: 1) All Skylake laptops with 970m, 980m, and 980gtx GPUs 2) All Skylake and Haswell-E desktops with 970gtx and 980gtx GPUs (although strangely, things seem to work with when you connect to a monitor over HDMI, but always fails when connecting to a monitor over DisplayPort) Note that none of the above failed tested scenarios are using Optimus: all are using discrete GPU configurations. In my testing thus far on the effected hardware, the install always fails if you choose "Try Ubuntu without installing". The install usually seems to work when you choose "Install Ubuntu", but even this 2nd scenario sometimes fails (and when it does, you'll see the same "trap invalid opcode" bits in dmesg). Also note that so far I've only tested amd64, haven't tested i386. I suspect there is some deeper weirdness here, but at this point System76 is just trying to make sure we have a Xenial ISO from which customers can re-install Ubuntu. Old description === Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware. For example, from dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0 [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0 This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well. Although strangely, with some NVIDIA 900 series hardware we're not seeing this bug when using the nouveau driver. This will be investigated further. In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs. Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting). I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable: (1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems. (2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem. I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me. Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinkin
[Touch-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Attaching CPU info from two affected Desktop systems. ** Attachment added: "cpuinfo-leox.txt" https://bugs.launchpad.net/oem-priority/+bug/1564156/+attachment/4640786/+files/cpuinfo-leox.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe Status in OEM Priority Project: New Status in System76: Triaged Status in llvm-toolchain-3.8 package in Ubuntu: In Progress Status in mesa package in Ubuntu: New Bug description: Currently it's impossible to install from xenial-desktop-amd64.iso on a wide range of hardware with Nvidia GPUs. The problem is invalid opcode(s) when using llvmpipe (the software opengl fallback, used when using Unity with the Nouveau driver). The result is that compiz crashes over and over; Upstart will continue to restart compiz till it gives up. To confirm whether this bug is happening, switch to a VT and check dmesg, in which you'll see something like: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 A workable solution seems to be to re-build mesa against llvm-3.6-dev, libclang-3.6-dev (rather that 3.8). This would get us a working Xenial ISO for the effected hardware. Post 16.04 release, this could be revisited, and mesa in Xenial could possibly switch back to llvm 3.8 once this issue is resolved. I have mesa test packages built against llvm 3.6 here: https://launchpad.net/~jderose/+archive/ubuntu/mesa/+packages I couldn't test the installation without a re-spun ISO, but I did confirm that after updating to the mesa packages in my PPA, I could again use Unity. So I'm pretty sure this will fix installing from the ISO as well. My hunch is that llvm 3.8 is generating invalid code during its JIT compilation for llvmpipe, but it could also be the result of memory corruption. Either way, building mesa against llvm 3.6 seems to be quick the fix. Note this is a regression from 14.04.4 and 15.10, both of which install fine on the hardware effected by this bug. For concrete examples of System76 hardware effected by this: 1) All Skylake laptops with 970m, 980m, and 980gtx GPUs 2) All Skylake and Haswell-E desktops with 970gtx and 980gtx GPUs (although strangely, things seem to work with when you connect to a monitor over HDMI, but always fails when connecting to a monitor over DisplayPort) Note that none of the above failed tested scenarios are using Optimus: all are using discrete GPU configurations. In my testing thus far on the effected hardware, the install always fails if you choose "Try Ubuntu without installing". The install usually seems to work when you choose "Install Ubuntu", but even this 2nd scenario sometimes fails (and when it does, you'll see the same "trap invalid opcode" bits in dmesg). Also note that so far I've only tested amd64, haven't tested i386. I suspect there is some deeper weirdness here, but at this point System76 is just trying to make sure we have a Xenial ISO from which customers can re-install Ubuntu. Old description === Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware. For example, from dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0 [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0 This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well. Although strangely, with some NVIDIA 900 series hardware we're not seeing this bug when using the nouveau driver. This will be investigated further. In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs. Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting). I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable: (1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems. (2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem. I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me. Other likely culprits include nux, mesa, maybe even llvm, and pr
[Touch-packages] [Bug 1424485] [NEW] Plural case error in Ubuntu Phone lock screen
Public bug reported: On the lock screen for Unity 8, if you send one text message the lock screen says "One text messages sent". It should say "One text message sent" Running Ubuntu 14.10 r15 on Nexus 5. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.02+15.04.20150122.2~rtm-0ubuntu1 Uname: Linux 3.4.0-1-hammerhead armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Sun Feb 22 16:49:34 2015 InstallationDate: Installed on 2015-01-29 (24 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150129-030203) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1424485 Title: Plural case error in Ubuntu Phone lock screen Status in unity8 package in Ubuntu: New Bug description: On the lock screen for Unity 8, if you send one text message the lock screen says "One text messages sent". It should say "One text message sent" Running Ubuntu 14.10 r15 on Nexus 5. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.02+15.04.20150122.2~rtm-0ubuntu1 Uname: Linux 3.4.0-1-hammerhead armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Sun Feb 22 16:49:34 2015 InstallationDate: Installed on 2015-01-29 (24 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150129-030203) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1424485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
