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. Th
FYI I filed a new Bug #1582011 as requested.
--
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/1464917
Title:
reboot hangs at 'Reached target Shutdown'
Status in systemd:
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 collect
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 Versio
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,
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 t
229-5 is set to release with 16.10 "Yakkety Yak"
--
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/1464917
Title:
reboot hangs at 'Reached target Shutdown'
Status in systemd
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 a
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.ne
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
hardw
Sweet!! nice find Adam!
--
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/1464917
Title:
reboot hangs at 'Reached target Shutdown'
Status in systemd:
New
Status in system
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 i
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
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
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
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
abo
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 n
@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
wrote:
> @xtrchessreal, if Chromium background processes are the culprit on your
> platform, this would mean we are suf
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 shutdow
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 no
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
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 immediate
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
23 matches
Mail list logo
