solution ici : https://bbs.archlinux.org/viewtopic.php?id=148033
--
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'
S
Same problem with debian 9. I had no problem with debian 8.
--
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
Present in 16.10.
--
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:
Invalid
Status in systemd p
Still present in 16.04:
4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:29:54 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
--
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
T
@monochromec,
David's bug appears to be here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640200
--
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:
r
Hi David,
As this issue is still persisting (and none of the above work-arounds
worked for me): What's the bug # of the new bug you filed a few days
ago?
Thanks for your help!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: systemd
Status: Incomplete => Invalid
--
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
I am experiencing the same problem on a new install of 16.10 AMD 64 Gateway
laptop. I did report it as a separate bug but I am adding my name to this one
also.
Thanks,
It may have something to do with the timing or swap. I hope someone takes
notice and replies :)
thanks,
David
** Changed in
This bug is affecting my Dell 7010 desktop machine, after a fresh
install of Ubuntu 16.10. Never had this problem during testing. Smells
like a regression...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hi all
I am running Ubuntu 16.04 which I have upgraded from ubuntu 15.10 and I am
still facing the same issue is after shutdown,the system hangs and I have to
manually do hard shutdown.I have tried lots of solutions then came to this bug
,will try swap off but I guess this is not the permanent
This bug is still present in Xenial. I have 4 different machines which
are affected by this bug.
--
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
This bug appears to now be fixed for me, at least in initial testing.
--
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 Shutdow
I had the same problem but it started after I uncomment the following
line in the /etc/default/grub file:
#GRUB_TERMINAL=console.
I commented it again and the PC start to shutdown again without
problems.
I commented this line at first because I had a problem with my screen
resolution mode... it
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:
This is not a trivial matter. It needs to be backported.
On Mon, Jun 13, 2016 at 1:25 AM, Danny Yates
wrote:
> Since there hasn't been an answer for a month, I'll ask the question
> again...
>
> Is there any chance that this will be backported for Xenial? At the
> moment, folks on an LTS release
Since there hasn't been an answer for a month, I'll ask the question
again...
Is there any chance that this will be backported for Xenial? At the
moment, folks on an LTS release are struggling to cleanly shut their
machines down.
--
You received this bug notification because you are a member of
Thanks. Will it backport to 16.04?
L
On Thu, May 5, 2016 at 8:04 PM, Martin Pitt wrote:
> > "* On shutdown, unmount /tmp before disabling swap. (Closes: #788303)"
>
> This fix is in xenial-proposed now, for the record.
>
> --
> You received this bug notification because you are subscribed to t
Dear all, turns out, my system was suffering from completely different
bug with similar symptoms. It was a problem with the motherboard BIOS. I
upgraded the BIOS and the bug went away. I'm taking myself off the
mailing list for this bug.
If you're suffering from a similar issue even after the fix
> "* On shutdown, unmount /tmp before disabling swap. (Closes: #788303)"
This fix is in xenial-proposed now, for the record.
--
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/1
Again: If you are affected by a shutdown hang, due to the swap issue or
otherwise, please file a new bug.
--
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:
reb
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
Will it be ported (systemd 229-5, that should fix swap issue) to Ubuntu
16.04 ?
--
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 targ
This could be https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788303
then. But really, please file new bugs -- the same symptom ("long
shutdown" or similar) might apear the same, but over time we've seen
wildly different root causes.
** Changed in: systemd
Status: New => Invalid
** Bug w
** Attachment added: "mem.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4649398/+files/mem.txt
--
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
This still happens in 16.04 LST! As it was described several times above
the shutdown process somehow blocks/gets in a deadlock when un-mounting
the swap partitions. I did not understood exactly what happens but the
recovery console clearly shows that the swap space is still on and
vailable and the
On Wed, Apr 27, 2016 at 04:49:37PM -, winnie wrote:
> Please reopen this issue.
File a new bug for your issue, as Martin indicated.
> Systemd doesn't offer much for shutdown debugging
It does, as documented in the README that Martin pointed out in this bug.
This would perhaps be more obviou
Please reopen this issue. I can reproduce this on several sligthly different
boxes which are installed from scratch. I didn't find a good way to reproduce
this reliably. It does however happen regulary on reboot/shutdown. My guess is
about every 5th time.
I am able to switch to tty1 but typing
This or an identical-looking bug affects all of our test machines
running Ubuntu 16.04. The machines are also fully patched.
It's not consistent, the bug seems to happen sporadically. It must be
some sort of race condition. I can either reproduce it or not, on the
same machine, as the same user, r
> Steve, do you still have this problem on later Ubuntu versions?
No, this issue is not reproducible for me in xenial. Marking as fixed.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seed
> I've also noticed this in Virtualbox, particularly after installation
is complete that it won't reboot.
That sounds like it would affect the live system with ubiquity, rather
than an installed system? Or did I misunderstand this? Shutdown on the
live system has always been brittle particularly i
I've definitely reproduced this as recently as today on a real machine on
16.04 (fully up to date) with similar symptoms described as reaching the
shutdown target and then just hanging for a while.
I also uses sysrq to recover at that point.
I've also noticed this in Virtualbox, particularly afte
Steve, do you still have this problem on later Ubuntu versions? Please
follow "Debugging boot/shutdown problems" in
/usr/share/doc/systemd/README.Debian.gz and check if there are any
hanging jobs at shutdown. Capturing a screen photo of "journalctl -b" in
the rescue shell might also be enlightenin
i highly suspect some old setting/config left behind:
- use gtkorphan to purge possible unused package(s)
- clean the system with bleachbit (as root; but optin carefully the settings)
and as a reminder, always 'purge' to get rid of old settings which
disturb the system and give unexpected troubles
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
Did not have this on 15.10, but I am having this issue on 16.04.
--
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'
S
I have the same problem on power off (not reboot) when upgraded to 16.04
LTS. Was not an issue in 15.10.
--
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:
rebo
Now have this present in Xenial
--
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
@dino99:
The problem is present in Xenial. Nothing changed after I upgraded to Ubuntu
16.04 LTS preview.
** Tags added: xenial
--
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/bug
This problem is gone with xenial on my system. This was a transitional
issue.
** Tags removed: xenial
--
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
Hi All,
did anyone find at least a workaround to automate the shutdown process (while
waiting for the issue to be fixed) ?
Thanks
--
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/
Sorry my mistake.
#ShutdownWatchdogSec=10min
#DefaultTimeoutStopSec=90s
Thanks Daniel for pointing out my mistake.
--
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
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
My system (15.10 with full updates) has
#ShutdownWatchdogSec=10min
(and systemd-system.conf man page confirms the 10min default timeout)
and I still have the issue.
turning swap off before reboot
_OR_
sudo systemctl reboot
works without any issues, and I get an immediate reboot.
--
You re
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
I guess i have found cause and solution. It's timeout.
In logs after running system with systemd.log_level=debug I have:
Mar 09 21:45:25 misio systemd[1]:
dev-disk-by\x2duuid-f7d9f751\x2dc42a\x2d40cf\x2dbfb1\x2d218c90c07b10.swap:
Forked /sbin/swapoff as 4403
...
And exactly 90s later:
Mar 09
On Tue, Mar 08, 2016 at 09:09:46AM -, dino99 wrote:
> Xenial is also affected: reboot & shutdown, the lock usually ends by
> itself 10_20 seconds later, but sometimes it does not ends at all.
> Looks like its due to "lockfile-progs" which is described as:
lockfile-progs is a set of tools that
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
This bug has reappeared for me, even after removing the older kernels.
--
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 Shutdo
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
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'
S
Xenial is also affected: reboot & shutdown, the lock usually ends by
itself 10_20 seconds later, but sometimes it does not ends at all.
Looks like its due to "lockfile-progs" which is described as:
***
These programs use liblockfile to perform the file locking and
unlocking, so they are guara
** Tags added: xenial
--
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 systemd p
I did the "swapoff workaround" a number of times and not always it
worked...
Probably the swap handling is only part of the problem...
--
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.
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'm just wondering if we could set some timeout for the shutdown in the
systemd configuration files.
I tried to add the following to the /usr/lib/systemd/user/shutdown.target
config:
JobTimeoutSec=30
JobTimeoutAction=poweroff-force
but unfortunately it has no effect.
--
You received this bug n
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
I can confirm too that the issue is probably something to do with the
swap usage.
My first guess was that the problem has something to do with the
system's update, but seems that real cause is the swap usage. The
shutdown usually goes fine when the system is used only for a short time
and fails af
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
Tried Adam's workaround: if I do
swapoff
and then shutdown, the system poweroff complete successfully.
--
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:
reb
Im also having this problem on 15.04 a fresh install
--
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 sys
I have similar problem.
I found workaround that usually allows me to shutdown system.
on debug-shell I run:
swapoff /dev/sda7
HDD start working and system poweroff few seconds later.
When system wasn't using swap before shutdown or i turn off swap before
shutdown it went off almost instantly.
** Attachment added: "jobs after Reached target Shutdown."
https://bugs.launchpad.net/systemd/+bug/1464917/+attachment/4583923/+files/jobs.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs
** Attachment added: "journalctl: Reached target Shutdown. at 23:17:50 dump at
23:24:34"
https://bugs.launchpad.net/systemd/+bug/1464917/+attachment/4583930/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I have the same problem with Ubuntu 15.10, fresh install on a Lenovo B50-10:
the system got stuck on shutdown or reboot (the last trace on screen, when I
press Esc, is "Reached target shutdown").
I've tried waiting a few minutes (at least 10 min), but nothing changed... Only
way to power off is
I have the same problem with Lubuntu 15.10 and it was a fresh install,
however my computer hangs on shut down and reboot. The alt sysRq only
works to reboot and it doesn't work if i've already reached the "reached
target shutdown" as my keyboard isn't responsive at that point.
i did the following
@xtrchessreal, I followed the recipe and removed everything but the most
recent kernel. However, my problem didn't go away. Seeing as the
symptoms are slightly different, I am probably suffering from a
different bug. Still no clue how to diagnose or fix it.
--
You received this bug notification b
@xtrchessreal I just tried a variant of what you said (I deleted
everything except the most recent kernel, and didn't keep the second
most latest) and it fixed it. I am now able to reboot without having
this bug any more.
--
You received this bug notification because you are a member of Ubuntu
To
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
I also have the same problem
After install ubuntu 15.04, I can't reboot / shutdown
It hangs on Reached target Shutdown
--
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
Same here. Fresh install, 15.10 server on Intel RST raid 1 fakeraid.
--
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
The same problem on 15.10 willy fresh install full format HDD :/ Sysrq does not
work for me too... Any idea please?
Thanks for your help!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launch
** Also affects: systemd
Importance: Undecided
Status: New
--
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
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 suffering from differe
@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
** Attachment added: "IMG_0766.JPG"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4537645/+files/IMG_0766.JPG
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.lau
My Dell workstation is a fresh install of 15.04, also. I'm having the
same problem. I've attached some screen shots that show the last
messages typically seen after I try REISUB.
** Attachment added: "IMG_0765.JPG"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/45
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
@xtrchessreal, yes, alt+SysRq+ REISUB didn't work. It did help me out in
some other strange glitches. I think in this case, the USB drivers were
already shut off, and since I have a USB keyborad, it was unresponsive.
Maybe an analog / laptop keyboard would have worked.
--
You received this bug no
I have a hunch that this bug only occurs on systems upgraded from a previous
Ubuntu version, perhaps with replacement of upstart with systemd, but not on
fresh Ubuntu 15.04 or 15.10 installations.
Everyone who is affected: is there anyone who started having this problem on a
fresh 15.04 or later
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
--
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 Shutdo
How is this resolved? I'm having same problem but with ubuntu15.10 with
kernel 4.2. Reboot works fine but when I try shutting down, I get to the
ubuntu purple splash screen with text saying reboot: powering down or
something like that and it just freeze. I waited like 4 hours and it's
stuck. I had
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
Syslog starting with initiating shutdown from gui and ending right
before hard shutdown.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4530150/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Tou
Martin Pitt, I've tried all the recipes, here is what booting with
"debug" shows after shutdown (attached image).
Unfortunately, for me, SysRq doesn't work, the and the keyboard is
completely unresponsive. Is there any way to dig out what happened from
system logs post-factum, after next login?
I
** Attachment removed: "Shutdown process (without splash screen)"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4512903/+files/shutdown.png
** Attachment added: "Shutdown process (without splash screen)"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/14
I can confirm that happens with 15.10 too.
Attached a screenshot that shows a successful shutdown process (without
splash screen). The red line marks the moment where the process hangs if
the shutdown fails.
The workaround with the SysRq key presented here worked for me:
http://askubuntu.com/a/67
Still happens in 15.10
--
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 package in Ubuntu:
Inco
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
Ugh, sorry, I should have said
sudo systemctl poweroff - not sudo systemctl shutdown
--
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 'Reache
So, my 15.04 does exactly the same thing when I
sudo shutdown now -r
Like I have for years, leaving me with a server I have to run to and manually
reboot.
However, after poking at the systemd docs I noticed it has its own
shutdown+reboot command
sudo systemctl reboot (or sudo systemctl shutdo
same problem here with toshiba satellite C55 and Xubuntu 15.04 It happens just
after a BIOS update (from window)
I had some issues in the past fater updating BIOS, it generaly fucked my GRUB
and my dual-boot
may it be related to X server?
[ 14193.953] (II) UnloadModule: "evdev"
[ 14193.964
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
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
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 Shutdo
Unfortunately, it only fixed it in the first reboot. The one now had
that problem again, even with vivid-proposed.
--
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
Tit
I can confirm that updating to vivid-proposed fixes that behavior.
--
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'
** Changed in: systemd (Ubuntu)
Status: Expired => Confirmed
--
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'
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bu
Your system isn't too happy because of bug 1452644. This is fixed in
vivid-proposed, but this hasn't made it into -updates yet. This causes
network mounts etc. to fail. That might be related to the shutdown
problems. To get this out of the way, could you install the -proposed
setserial and re-test?
100 matches
Mail list logo