[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
I see this intermittently mostly after an internet session and I see at least 2 questions with total 5 upvotes on askubuntu.com concerning this hang on reboot or shut-down on 15.04 specifically. Most are hard booting after the hang. I found doing Ctrl+Alt+F1 followed by Ctrl+Alt+Del will continue the reboot. I will attempt to follow @Martin Pitt instructions and gain some log data if it is helpful to you. Please let me know if this is something you would like me to do. I referred to this bug#1464917 to those on askubuntu.com Just trying to help. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
So far I am unable to debug this. I need to some help to determine how. Is there a "shutdown log" I can view or post here. The problem is persistent now. Ctrl+Alt+F9 only worked once and I do not know how to capture this data. In every case I have to reboot using Sysrq REISUB and then immediately shutdown again to get laptop to shutdown properly. As I stated before it seems to only affect me when I have had an internet session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
I can't speak for all but I have noticed a few including me using the shutdown from the drop down at top right. Interesting note for my case - since I was not able to get debug info I decided to try a different browser so I switched from Chromium to Firefox and oddly have not had the problem since that switch. Firefox is just a temp for now, I am going to switch back and see if the problem persists with Chromium. If so Maybe Chromium has a background app that is hanging. I have not installed ANY of the Ubuntu extra feature Web Apps in Firefox where as Chromium has all my google apps integrated. How to capture the shutdown/poweroff dump data for debug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
You held down alt+SysRq and then typed REISUB one key at a time, and that didn't work? This: "Dec 5 09:31:21 deepblue systemd[1811]: shutdown.target: Fixing conflicting jobs shutdown.target/stop,shutdown.target/start by deleting job shutdown.target/stop" Looks like something is wrong but I am not expert - you might be onto something. I'm gonna do what you did and see what I get in Syslog. This still affects me in 15.04 and only when I run Chromium but every time I run Chromium SMH - I hate intermittent issues. Firefox does not cause this - go figure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
So far "unchecking running..." has not helped the hang situation for me, it was already unchecked. I unchecked the "use Hardware ..." too. I also closed all the peripheral apps like google voice, Hangouts, Unity Web apps. first. At some point I'll hit a breakthrough. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
My Ubuntu 15.04 is fresh installed using the frugal install method. Its a Sony Vaio VGN-FW250j and the bios is locked out, which is why I had to use the Frugal method. Its a dual boot system with Windows 7. The two share a Data drive for storage only. I wish I knew how to capture the shutdown data. I have not upgraded to 15.10 since someone confirmed its still doing it on that as well. The one odd thing for me is I tried to use a different browser than Chromium. I started using Firefox and the Target Reached Shutdown hang only hangs for a few seconds and then shutsdown on its own. But every time I bring up Chromium it hangs on shutdown or reboot and I have to use SYSRQ+alt+REISUB to reboot then wait until its up again just so I can shutdown properly. So I don't understand that and so far no one has been able to explain or repeat that to confirm it. It is very repeatable for me. My hunch is some background google app that is embedded with Chromium is the culprit, at least in my case. It may just be the beginning of a chain of events that happen to cause the hang but I don't know that because I can't capture the shutdown data. I need a forensics tool. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
@Gregory Kramida, I'll run a test with disabled background apps and reply with results...Thanks for the info On Sat, Dec 19, 2015 at 2:44 PM, Gregory Kramida <algomo...@gmail.com> wrote: > @xtrchessreal, if Chromium background processes are the culprit on your > platform, this would mean we are suffering from different issues. > Indeed, my symptoms are actually a bit different from what's described > in the original bug report -- I'm seeing the "Reached target Shutdown" > when I actually try to shut down, not reboot, and the system doesn't > fully shut down. My reboot works fine. > > You can try to disable Chromium background processes from running in the > background when Chromium is shut down (settings --> Show advanced > settings --> uncheck "Continue running ... "), and close chromium before > you reboot. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1464917 > > Title: > reboot hangs at 'Reached target Shutdown' > > Status in systemd package in Ubuntu: > Confirmed > > Bug description: > I rebooted my 15.04 system, and found it hanging indefinitely at the > plymouth shutdown screen. Hitting esc to reveal the console showed a > normal set of shutdown messages, ending with 'Reached target Shutdown' > (paraphrased from memory). > > The system never rebooted on its own. I had to use SysRq to finish > the shutdown. > > ProblemType: Bug > DistroRelease: Ubuntu 15.04 > Package: systemd 219-7ubuntu6 > ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 > Uname: Linux 3.19.0-20-generic x86_64 > ApportVersion: 2.17.2-0ubuntu1.1 > Architecture: amd64 > CurrentDesktop: Unity > Date: Sat Jun 13 11:53:10 2015 > InstallationDate: Installed on 2010-09-24 (1723 days ago) > InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 > (20100816.1) > MachineType: LENOVO 2306CTO > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic > root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 > SourcePackage: systemd > UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago) > dmi.bios.date: 10/25/2013 > dmi.bios.vendor: LENOVO > dmi.bios.version: G2ET97WW (2.57 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 2306CTO > dmi.board.vendor: LENOVO > dmi.board.version: Not Defined > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Not Available > dmi.modalias: > dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: > dmi.product.name: 2306CTO > dmi.product.version: ThinkPad X230 > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
FYI I filed a new Bug #1582011 as requested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
I ran dpkg --get-selections | grep linux-image to find old installations of the kernel images such as: linux-image3.19.0.15-generic the purged them with this command sudo apt-get purge linux-image-3.19.0-15-generic I did this for all old linux-images in the list from the dpkg --etc command above I deleted all but the current and the next most current, there were two linux-image-extra...etc that needed to be purged as well. These were listed with a "deinstall" parameter in the dpkg --etc list. I am not sure why those needed special attention but the rest auto purged the linux-image-extra...etc packages with the single: sudo apt-get purge linux-image-3.19.0-xx-generic command I then upgraded to 15.10 and I no longer have the "Reached target Shutdown" hang issue...at this time, caveat it hangs for a few seconds but not indefinitely for me. These are the only images currently installed now: dpkg --get-selections | grep linux-image linux-image-3.19.0-49-generic install linux-image-4.2.0-27-genericinstall linux-image-extra-3.19.0-49-generic install linux-image-extra-4.2.0-27-generic install linux-image-generic I would be interested if others have tried this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
I wonder if the so called Watchdog Hardware is on my machine at all. I looked for the conf files in /dev/watchdog and found no such directory. According to the website: https://www.freedesktop.org/software/systemd/man/systemd- system.conf.html The manual reads as though its assumed watchdog hardware is there. It states that, "These settings have no effect if a hardware watchdog is not available." I wonder if anyone assumed the case if it was not there? It is still my contention the swap management system is at fault here. I have run several tests loading my 3.7 gig ram and 8.1 gig swap then shutting all apps off. Monitoring with system monitor RAM returns to acceptable levels around .9 to 1.4 gig, however the swap never gets below 2 gig even after 30 mins of no load conditions, all apps closed. A swap management system appears to be absent minded. Turning swap off is the only way I get a clean reboot or shutdown sudo systemctl reboot or poweroff hang unless swap is cleared first and swapoff fails if data held in swap is larger than available RAM. I am tempted to use SyReq +REISUB just to reboot, why wait for the hang? I check system monitor before running the command below to shutdown to calculate whether the swapoff command will fail then decide how to proceed. sudo swapoff -a && systemctl poweroff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
Sweet!! nice find Adam! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
The issue came back for me a few shutdowns after I purged old kernel images as explained above. I was gonna wait until I've had more time before calling it successful at least for me as a work around but I tried Adam's idea too and so far it is working. When you 'sudo swapoff -a' it takes time on my machine for the system to do the switch. I hear the cpu fan run higher and the terminal screen is delayed in giving me the prompt back while the command is processed. I'm sure totally normal behavior. Then I shut down as usual and there is no delay at all, I see the message for a second maybe and then my machine is off. I first played around with the swappiness=0 but that made my machine hang for normal operations so I set it to 50 and then tried Adam's idea just before shutdown. I think a nice script would be cool to make until this issue is fixed officially. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
Tokes, Your description of behavior is exactly as mine. The longer up time the more it is likely to hang. Also when it hangs the cpu begins to crunch a lot of operations and the fan starts higher and higher rpm. I get the same fan behavior when I 'sudo swapoff -a' as stated above prior to my shutdown as I do when I simply try to shutdown without running 'sudo swapoff -a' command. The difference is the shutdown completes as it should if I take the time to run 'sudo swapoff -a' and wait for it to complete. Swap management does seem to be pointing toward the direction of the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
I am no expert but I looked into the systemd shutdown.target as well and found no parameters that can be changed. I also performed a swap test where I loaded the swap partition to over 54% roughly 4.2 gig while my ram was at 87% full. I have 3.7 gig ram available and 8.1 gig swap on my machine. I loaded the system using Gimp opening and entire folder of photos, opening a browser and streaming a youtube movie. I then closed all applications and waited for 20 minutes with the monitor open. The swap file did lose half of its stored data to about 2 gig but then it seemed to pause at that point for a long time, longer than I was willing to wait. I then ran: sudo swapoff -a && systemctl poweroff The swapoff process took another 10+ minutes and then the shutdown took place without the hang. It is my belief that the swap management app/function built into the OS is the issue or at least part of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
Have you tried @Adam idea turn your swap off just prior to shutdown, allow the command to process its a work around that seems to work for many. It may take 10+ minutes if a lot of data was being held in swap but it should shutdown. sudo swapoff -a && systemctl poweroff The amount of data held in swap must be lower than the amount available in Ram or the command will fail FYI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
I'm still using "sudo swapoff -a && systemctl poweroff" as a work around Does anyone know how this bug gets ASSIGNED to a task group? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582011] [NEW] Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"
Public bug reported: This bug has been affecting me since 15.04 Prior to shutdown I activate debug-shell 'systemctl start debug-shell' I have followed bug #1464917 and installed Xenial-proposed with systemd 229-4ubuntu5 package. I have finally collected shutdown info using vt9. Issues collecting info due to what I believe is a timeout where vt9 is not activated when ctl+alt+F9 is pressed. I was able to collect info in vt9 to file "shutdown.text" I appended outputs to file "shutdown.text" the following commands in this order: systemctl list-jobs >>shutdown.text systemctl --failed >>shutdown.text uname -a >>shutdown.text systemd --version >>shutdown.text lsblk >>shutdown.text blkid >>shutdown.text journalctl -b >>shutdown.text systemctl -all >>shutdown.text journalctl -xe >>shutdown.text After gaining these data I was only able to finish the reboot with the alt+Sysrq and REISUB which forces a reboot even when I just want to shutdown Each output I separated upon next boot by hand with a line # for easier perusing. As a workaround for shutdown/reboot I turn swap off, 'sudo swapoff -a && systemctl poweroff' or 'sudo swapoff -a && reboot' which occasionally fails if SWAP has more data than available RAM. In that latter case I am left waiting for the hang and then using alt+Sysrq+REISUB to reboot then shutdown again immediately upon boot before SWAP has a chance to gain data, then I can use any form of halt, poweroff or menu to shutdown. I have been unable to get answers from AskUbuntu or the above listed bug #1464917 "Reached target Shutdown" I am filing this bug per instructions requested in that bug. Other systemd bugs I have researched #788303 Debian bug reports, #2930 Github and #3087 Github. Thanks for your time and efforts to help with this issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 15 12:08:34 2016 ExecutablePath: /lib/systemd/systemd InstallationDate: Installed on 2015-06-29 (321 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Sony Corporation VGN-FW250J ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=b010e611-6efb-49a9-bff0-59b9533d659b ro resume=UUID=8bcb4169-f5ab-4ab6-b644-23e528088d41 usbcore.autosuspend=-1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to xenial on 2016-04-26 (18 days ago) dmi.bios.date: 07/25/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1090Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1090Y0:bd07/25/2008:svnSonyCorporation:pnVGN-FW250J:pvrC6011MLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FW250J dmi.product.version: C6011MLK dmi.sys.vendor: Sony Corporation ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "output to listed commands in description" https://bugs.launchpad.net/bugs/1582011/+attachment/4663446/+files/May%2015%20shutdown.text -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582011 Title: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1582011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
229-5 is set to release with 16.10 "Yakkety Yak" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
according to the changelog: http://metadata.ftp- master.debian.org/changelogs//main/s/systemd/systemd_229-5_changelog "systemd (229-5) unstable; urgency=medium" "* On shutdown, unmount /tmp before disabling swap. (Closes: #788303)" is supposed to fix the hang on shutdown. Provided that we are all experiencing the "same hang" issue. Reading this bug #1464917 then referenced #788303 which references #2930 https://github.com/systemd/systemd/issues/2930 which was merged with #3087 https://github.com/systemd/systemd/pull/3087 Just need to figure out when systemd 229-5 is stable released to Ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554803] Re: apparmor: missing stub hardware directories
Seth, Thanks for your effort and input to my question. Here is the output you requested :) x@x-NICEPUTER:~$ dpkg -l webbrowser-app | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= rc webbrowser-app 0.23+16.04.20160413-0ubuntu1 amd64Ubuntu web browser x@x-NICEPUTER:~$ dpkg -S /usr/share/apparmor/hardware/video.d dpkg-query: no path found matching pattern /usr/share/apparmor/hardware/video.d x@x-NICEPUTER:~$ Lemme know if there is anything else I can do Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554803 Title: apparmor: missing stub hardware directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1554803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554803] Re: apparmor: missing stub hardware directories
fyi after install of apparmor-easyprof-ubuntu: x@x-NICEPUTER:~$ dpkg -l webbrowser-app | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= rc webbrowser-app 0.23+16.04.20160413-0ubuntu1 amd64Ubuntu web browser x@x-NICEPUTER:~$ dpkg -S /usr/share/apparmor/hardware/audio.d apparmor-easyprof-ubuntu: /usr/share/apparmor/hardware/audio.d x@x-NICEPUTER:~$ dpkg -S /usr/share/apparmor/hardware/graphics.d apparmor-easyprof-ubuntu: /usr/share/apparmor/hardware/graphics.d x@x-NICEPUTER:~$ dpkg -S /usr/share/apparmor/hardware/video.d apparmor-easyprof-ubuntu: /usr/share/apparmor/hardware/video.d Thanks again and lemme know :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554803 Title: apparmor: missing stub hardware directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1554803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554803] Re: apparmor: missing stub hardware directories
I have the exact output (I'm also running 16.04 upgraded from 15.10) the originator published. If it was fixed in webbrowser-app package 16.04 then this would not be seen in 16.04. I agree this bug should be left open. I looked everywhere on AskUbuntu etc before finally asking and was referred to this bug. Thanks for your time and effort. :) How do I apply the apparmor-easyprof-ubuntu package? Is this a workaround or the fix? Should I remove and purge the current apparmor etc packages then reinstall? I also invite any here to post the proper steps to the answer to my question on AskUbuntu: http://askubuntu.com/questions/767272/apparmor-init-failed-exit-code-123/767686#767686 Once again thank you for your effort and time please let me know if there is anything I can provide to help. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554803 Title: apparmor: missing stub hardware directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1554803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582011] Re: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"
Update: I used a spare HDD on the same laptop and setup 16.04 LTS per Ubuntu Disk Partitioning recommendations as follows: Swap, /, and Home in that order. Grub is on the 1st Primary as boot, Swap, /, and Home are logical on the 1st extended. There are no other operating systems on this HDD. There is only this one HDD physically installed. With this HDD installed as described here I NO LONGER have issues during shutdown or reboot. If I physically install the original HDD as it is described in this bug description I Still DO have issues with the hang on shutdown and reboot. I cannot conclude anything but I speculate that the original HDD setup as /, Home, Swap in that order, or the config of fstab may have some significance to the issue. It has been over 2 months using this new HDD in my laptop without any hangs. There has never been a Target reached Shutdown hang since installing the new HDD. I waited to be sure the hang is gone before reporting any new data. I will keep this new hardware configuration and use the original HDD as a spare for future use. Thank you for all your efforts to resolve the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582011 Title: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1582011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
