Re: computer cann't shut down

2016-03-28 Thread David Niklas 
Perhaps terminator has got to your machine?
Perhaps you may have disobeyed DRM and now they are out to get you!
Or, you may have been deemed a "threat to the free world".
(Just had to write those jokes).

Sincerely, David

Re: systemd troubleshooting (was ... Re: computer cann't shut down)

2016-03-28 Thread David Wright 
On Mon 28 Mar 2016 at 17:02:46 (+0100), Lisi Reisz wrote:
> On Monday 28 March 2016 16:37:16 David Wright wrote:
> > I'm not interested
> > in spending my time answering your easy-to-pose rhetorical questions
> 
> The whole point of rhetorical questions is that they are not in fact 
> questions 
> and do not require an answer, and more than any other type of statement.

Strictly that is true. However, questions on a mailing list like
this one are posed in different ways. Some are directly asking for
information, some are anything but, and there's a spectrum in
between. My saying "rhetorical question" is a shorthand way (two
words) of giving you an idea of where on that spectrum I think
questions lie.

>From the wiki: "Though a rhetorical question does not require a direct
answer, in many cases it may be *intended to start a discussion* or at
least draw an acknowledgement that the listener understands the
intended message." (my emphasis.)

Cheers,
David.

Re: systemd troubleshooting (was ... Re: computer cann't shut down)

2016-03-28 Thread Lisi Reisz 
On Monday 28 March 2016 16:37:16 David Wright wrote:
> I'm not interested
> in spending my time answering your easy-to-pose rhetorical questions

The whole point of rhetorical questions is that they are not in fact questions 
and do not require an answer, and more than any other type of statement.

Lisi

Re: systemd troubleshooting (was ... Re: computer cann't shut down)

2016-03-28 Thread David Wright 
On Mon 28 Mar 2016 at 20:58:13 (+1300), chrisb@localhost.localdomain wrote:
> On Wed, Mar 23, 2016 at 10:00:53AM -0500, David Wright wrote:
> > Now, every time there's a security fix, you're going to be quizzed
> > over what to do about your modified configuration file because Debian
> > wants to overwrite your modified /etc/systemd/system/foo.target.
> 
> Umm, guess what the normal current behaviour is.
> 
> > Or at some time in the future, you decide to revert to the Debian
> > version. 
> 
> It's more often than not a particular feature or option you want to 
> change, right? 
> 
> > You have to juggle the files /etc/systemd/system/foo.target
> > and /etc/systemd/system/foo.target.orig instead of just removing
> > the link /etc/systemd/system/foo.target -> /lib/systemd/system/foo.target
> > 
> > > or
> > > /usr/share/doc/systemd/system/halt.target.default ?
> 
> You do comment your configuration files, right? 
> Also do you delete old configuration options or comment out the line?
> 
> [snipped personal preference stuff]

Snip away. I said in my posting
https://lists.debian.org/debian-user/2016/03/msg01032.html
that I was expressing my own views on the way links are placed in
/etc/systemd/ to override the defaults in /lib/systemd/.
John Hasler asked a specific question, albeit rather open-ended,
which I answered in specific terms, making necessary assumptions.
If you don't like the methods, don't use them. I'm not interested
in spending my time answering your easy-to-pose rhetorical questions
(two of which immediately follow a line that I didn't write) with
well-thought out replies.

After all, you haven't clarified your point in the same post.

Cheers,
David.

Re: systemd troubleshooting (was ... Re: computer cann't shut down)

2016-03-28 Thread chrisb 
On Wed, Mar 23, 2016 at 10:00:53AM -0500, David Wright wrote:
> Now, every time there's a security fix, you're going to be quizzed
> over what to do about your modified configuration file because Debian
> wants to overwrite your modified /etc/systemd/system/foo.target.

Umm, guess what the normal current behaviour is.

> Or at some time in the future, you decide to revert to the Debian
> version. 

It's more often than not a particular feature or option you want to 
change, right? 

> You have to juggle the files /etc/systemd/system/foo.target
> and /etc/systemd/system/foo.target.orig instead of just removing
> the link /etc/systemd/system/foo.target -> /lib/systemd/system/foo.target
> 
> > or
> > /usr/share/doc/systemd/system/halt.target.default ?

You do comment your configuration files, right? 
Also do you delete old configuration options or comment out the line?

[snipped personal preference stuff]

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: systemd troubleshooting (was ... Re: computer cann't shut down)

2016-03-23 Thread David Wright 
On Wed 23 Mar 2016 at 08:16:18 (-0500), John Hasler wrote:
> David Wright writes:
> > you have to take on trust, or check, that bar="some value" is
> > the default configured, or set elsewhere, for foo. OTOH, when
> > you copy /lib/systemd/system/... to /etc, you know you've got
> > hold of the default configuration. IOW, it's self-documenting.
> 
> Why is that better than /etc/systemd/system/halt.target.orig

To answer that, I have to make some unwritten assumptions.

I assume you mean that there will be some files
/etc/systemd/system/foo.target
/etc/systemd/system/bar.target
supplied by Debian, and that when you make a change, you write a new
/etc/systemd/system/foo.target and retain the previous/Debian version
as /etc/systemd/system/foo.target.orig, ok?

Now, every time there's a security fix, you're going to be quizzed
over what to do about your modified configuration file because Debian
wants to overwrite your modified /etc/systemd/system/foo.target.

Or at some time in the future, you decide to revert to the Debian
version. You have to juggle the files /etc/systemd/system/foo.target
and /etc/systemd/system/foo.target.orig instead of just removing
the link /etc/systemd/system/foo.target -> /lib/systemd/system/foo.target

> or
> /usr/share/doc/systemd/system/halt.target.default ?

I wrote "you know you've got hold of the default configuration".
You don't *know* that /usr/share/doc/systemd/system/foo.target.default
is the default configuration; foo never consults it. To *know* whether
it has the same contents, you have to
cmp /usr/share/doc/systemd/system/foo.target.default 
/lib/systemd/system/foo.target

To revert your change back to the Debian version, it would be foolish
to blindly copy /usr/share/doc/systemd/system/foo.target.default
over /etc/systemd/system/foo.target. Would you accept a bug report
for foo where some of the configuration files being actively used were
merely copies of documentation files?

So I *like* the scheme where /lib/systemd/system/foo.target is the
self-documenting default because the system actually reads that file,
unless the sysadmin has put a link in /etc/systemd/system/foo.target
to override it.

In both your examples, consider how easy it is to tell what changes
you have made over time.

In the first case, you have to list all the /etc files that end with
(you hope) [-.]orig [-.]original [-.]old [-.]previous [-.]default etc.

In the second, you have to cmp all the files in /etc with the files
in /usr/share/doc/systemd/system/ remembering 1) to handle any
file-not-found errors, 2) that you hopefully checked that there *was*
a default in the documentation, and 3) if there wasn't, you wrote one,
but now where did you put it because you can't write to /usr/share/doc.

Cheers,
David.

Re: systemd troubleshooting (was ... Re: computer cann't shut down)

2016-03-23 Thread John Hasler 
David Wright writes:
> you have to take on trust, or check, that bar="some value" is
> the default configured, or set elsewhere, for foo. OTOH, when
> you copy /lib/systemd/system/... to /etc, you know you've got
> hold of the default configuration. IOW, it's self-documenting.

Why is that better than /etc/systemd/system/halt.target.orig or
/usr/share/doc/systemd/system/halt.target.default ?
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: systemd troubleshooting (was ... Re: computer cann't shut down)

2016-03-23 Thread David Wright 
On Wed 23 Mar 2016 at 21:53:15 (+1300), chrisb@localhost.localdomain wrote:
> On Mon, Mar 21, 2016 at 10:44:24AM -0700, Lotek wrote:
> > On 03/19/2016 05:40 AM, lina wrote:
> > >Every time since I installed the system,
> > >
> > >every time I tried Shut Down, it mainly restart again.
> > >
> > >I checked online and tried several methods but still don't work.
> > >
> > >Can anyone suggest me how to solve it.
> > >
> > >Thanks,
> > 
> > The problem might be with systemd.  Check the link
> > "/lib/systemd/system/@ctrl-alt-del.target".  If it points to
> > "reboot.target", copy the "@ctrl-alt-del.target" link to
> > "/etc/systemd/system".  Then point the new link to

  ↑↑↑

> > "/lib/systemd/system/halt.target".
> 
> *groan* so configuration is not confined to /etc/ anymore?

I don't follow youo.

> If everything works with systemd it's great, but otherwise 
> it is a PITA esp, with Debian only changes where the normal
> info doesn't apply. 

I quite like this scheme. When you have a configuration file
like /etc/foo.conf which contains

# bar="some value"

you have to take on trust, or check, that bar="some value" is
the default configured, or set elsewhere, for foo. OTOH, when
you copy /lib/systemd/system/... to /etc, you know you've got
hold of the default configuration. IOW, it's self-documenting.

Cheers,
David.

systemd troubleshooting (was ... Re: computer cann't shut down)

2016-03-23 Thread chrisb 
On Mon, Mar 21, 2016 at 10:44:24AM -0700, Lotek wrote:
> On 03/19/2016 05:40 AM, lina wrote:
> >Every time since I installed the system,
> >
> >every time I tried Shut Down, it mainly restart again.
> >
> >I checked online and tried several methods but still don't work.
> >
> >Can anyone suggest me how to solve it.
> >
> >Thanks,
> 
> The problem might be with systemd.  Check the link
> "/lib/systemd/system/@ctrl-alt-del.target".  If it points to
> "reboot.target", copy the "@ctrl-alt-del.target" link to
> "/etc/systemd/system".  Then point the new link to
> "/lib/systemd/system/halt.target".

*groan* so configuration is not confined to /etc/ anymore?
If everything works with systemd it's great, but otherwise 
it is a PITA esp, with Debian only changes where the normal
info doesn't apply. 

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: computer cann't shut down

2016-03-21 Thread Jimmy Johnson 

On 03/19/2016 07:40 PM, lina wrote:

shutdown -h now

doesn't work. it still reboot.


Lina is it rebooting to grub or the linux system you are trying to shutdown?
--
Debian Jessie - KDE 4.14.2  - EXT4 - AMD64 at sda9
Registered Linux User #380263

Re: computer cann't shut down

2016-03-21 Thread Lotek 

On 03/19/2016 05:40 AM, lina wrote:

Every time since I installed the system,

every time I tried Shut Down, it mainly restart again.

I checked online and tried several methods but still don't work.

Can anyone suggest me how to solve it.

Thanks,


The problem might be with systemd.  Check the link 
"/lib/systemd/system/@ctrl-alt-del.target".  If it points to 
"reboot.target", copy the "@ctrl-alt-del.target" link to 
"/etc/systemd/system".  Then point the new link to 
"/lib/systemd/system/halt.target".

Re: computer cann't shut down

2016-03-20 Thread Michael Milliman 



On 03/20/2016 03:40 AM, Adam Wilson wrote:

On Sun, 20 Mar 2016 05:28:55 +0100
Jerome BENOIT  wrote:


Hello Forum:

On 20/03/16 04:42, Michael Milliman wrote:


On 03/19/2016 09:40 PM, lina wrote:

shutdown -h now

doesn't work. it still reboot.
   

This sounds like an issue with the hardware or BIOS not with the
Debian OS, or with the Desktop environment.  Though I have not had
this problem, I have had several others related to
shutdown/reboot/suspend/hibernate on various machines, but I know
for a fact that all such problems have been with the hardware/BIOS,
not the Debian software.  I don't know enough about the iMac to
offer anything more.

Does recent iMac have a BIOS ?


What do you mean by this?

Of course Macs have *initialisation firmware* (about which I know
nothing) but not necessarily MBR BIOS as seen on PCs.
And indeed, I also know little or nothing about iMacs, and so BIOS may 
well be the wrong term, but there must be some sort of firmware for 
booting and handling low-level stuff.  Nevertheless, should Macs not 
handle the low level stuff the way a PC BIOS does, then my bet is on 
some sort of hardware problem.


--
Mike

Re: computer cann't shut down

2016-03-20 Thread lina 
>> >> Every time since I installed the system,
>> >
>> > Which one?  Jessie?  Testing (Stretch)?, Unstable?
>> >
>>
>> Jessie stable;
>>
>> > Which desktop, if any?
>>
>> on my new iMac.
>>
>> >
>> > What computer?
>> >
>> > During the install, what options did you choose?  Or did you just
>> > use the defaults?
>>
>> most use default, except partition.
>
> This is probably irrelevant to the issue, but what is your partition
> scheme?

Filesystem  Size  Used Avail Use% Mounted on
/dev/sda4   641M  235M  360M  40% /
udev 10M 0   10M   0% /dev
tmpfs   1.6G  9.1M  1.6G   1% /run
/dev/sda819G  3.7G   14G  22% /usr
tmpfs   3.9G   68K  3.9G   1% /dev/shm
tmpfs   5.0M  4.0K  5.0M   1% /run/lock
tmpfs   3.9G 0  3.9G   0% /sys/fs/cgroup
/dev/sda13  181M   32M  136M  20% /boot
/dev/sda11  547M  600K  507M   1% /tmp
/dev/sda12  3.7G  7.6M  3.4G   1% /usr/local
/dev/sda15  393G   71M  373G   1% /scratch
/dev/sda715G  2.4G   12G  17% /home
/dev/sda1   197M   16M  182M   8% /boot/efi
/dev/sda9   3.7G  1.3G  2.2G  37% /var
/dev/sda10  6.3G   15M  6.0G   1% /var/local
tmpfs   788M  4.0K  788M   1% /run/user/116
tmpfs   788M  8.0K  788M   1% /run/user/1000

Re: computer cann't shut down

2016-03-20 Thread Adam Wilson 
On Sun, 20 Mar 2016 05:31:18 -0400
Gene Heskett  wrote:

> On Sunday 20 March 2016 04:43:17 Adam Wilson wrote:
> 
> > On Sat, 19 Mar 2016 20:50:05 +0800
> >
> > lina  wrote:  
> > > I tried
> > >
> > > 1] systemctl poweroff
> > >
> > >
> > > 2] GRUB_CMDLINE_LINUX_DEFAULT="quiet"
> > >
> > > to quite splash acpi=force
> > >  
> Thats a typu, s/b quiet.  But I always take that and "splash" out as
> I want to be able to see whats complaining during the boot.  Yes, it
> does slow the boot by spitting out all that text, but I don't mind.

I'm pretty sure it doesn't slow down the boot regardless of whether you
have all the text displayed ("text" or blank) or not ("quiet"). My
system takes exactly the same amount of time to boot regardless of
whether I am using "quiet" or not.

It may *seem* to be slower due to the text, but this is not the case.


pgplwU2viO6Gx.pgp
Description: OpenPGP digital signature

Re: computer cann't shut down

2016-03-20 Thread Gene Heskett 
On Sunday 20 March 2016 04:43:17 Adam Wilson wrote:

> On Sat, 19 Mar 2016 20:50:05 +0800
>
> lina  wrote:
> > I tried
> >
> > 1] systemctl poweroff
> >
> >
> > 2] GRUB_CMDLINE_LINUX_DEFAULT="quiet"
> >
> > to quite splash acpi=force
> >
Thats a typu, s/b quiet.  But I always take that and "splash" out as I 
want to be able to see whats complaining during the boot.  Yes, it does 
slow the boot by spitting out all that text, but I don't mind.

> > The syslog error is as below:
> >
> > Mar 19 20:04:36 debian kernel: [0.221101] ACPI Error: No handler
> > for Region [CMS0] (88026e048e00) [SystemCMOS]
> > (20140424/evregion-163)
> > Mar 19 20:04:36 debian kernel: [0.221104] ACPI Error: Region
> > SystemCMOS (ID=5) has no handler (20140424/exfldio-297)
> > Mar 19 20:04:36 debian kernel: [0.221106] ACPI Error: Method
> > parse/execution failed [\_SB_.PCI0._INI] (Node 88026e04e8d8),
> > AE_NOT_EXIST (20140424/psparse-536)
> > Mar 19 20:04:36 debian kernel: [   11.093996] EXT4-fs (sda4):
> > re-mounted. Opts: errors=remount-ro
> > Mar 19 20:04:36 debian lightdm[856]: ** (lightdm:856): WARNING **:
> > Error getting user list from org.freedesktop.Accounts:
> > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> > org.freedesktop.Accounts was not provided by any .service files
> > Mar 19 20:04:40 debian lightdm[856]: ** (process:902): WARNING **:
> > Error getting user list from org.freedesktop.Accounts:
> > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> > org.freedesktop.Accounts was not provided by any .service files
> > Mar 19 20:05:00 debian lightdm[856]: ** (process:987): WARNING **:
> > Error getting user list from org.freedesktop.Accounts:
> > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> > org.freedesktop.Accounts was not provided by any .service files
> > Mar 19 20:09:18 debian kernel: [  300.212411] mce: [Hardware Error]:
> > Machine check events logged
> > Mar 19 20:42:35 debian org.a11y.atspi.Registry[978]:
> > g_dbus_connection_real_closed: Remote peer vanished with error:
> > Underlying GIOStream returned 0 bytes on an async read
> > (g-io-error-quark, 0). Exiting.
> > Mar 19 20:43:46 debian kernel: [0.237081] ACPI Error: No handler
> > for Region [CMS0] (88026e048e00) [SystemCMOS]
> > (20140424/evregion-163)
> > Mar 19 20:43:46 debian kernel: [0.237084] ACPI Error: Region
> > SystemCMOS (ID=5) has no handler (20140424/exfldio-297)
> > Mar 19 20:43:46 debian kernel: [0.237086] ACPI Error: Method
> > parse/execution failed [\_SB_.PCI0._INI] (Node 88026e04e8d8),
> > AE_NOT_EXIST (20140424/psparse-536)
> > Mar 19 20:43:46 debian kernel: [   11.975204] EXT4-fs (sda4):
> > re-mounted. Opts: errors=remount-ro
> > Mar 19 20:43:46 debian lightdm[854]: ** (lightdm:854): WARNING **:
> > Error getting user list from org.freedesktop.Accounts:
> > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> > org.freedesktop.Accounts was not provided by any .service files
> > Mar 19 20:43:50 debian lightdm[854]: ** (process:906): WARNING **:
> > Error getting user list from org.freedesktop.Accounts:
> > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> > org.freedesktop.Accounts was not provided by any .service files
> > Mar 19 20:44:24 debian lightdm[854]: ** (process:991): WARNING **:
> > Error getting user list from org.freedesktop.Accounts:
> > GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> > org.freedesktop.Accounts was not provided by any .service files
> > Mar 19 20:48:27 debian kernel: [  300.204379] mce: [Hardware Error]:
> > Machine check events logged
>
> This does not look good.


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: computer cann't shut down

2016-03-20 Thread Adam Wilson 
On Sat, 19 Mar 2016 20:50:05 +0800
lina  wrote:

> I tried
> 
> 1] systemctl poweroff
> 
> 
> 2] GRUB_CMDLINE_LINUX_DEFAULT="quiet"
> 
> to quite splash acpi=force
> 
> The syslog error is as below:
> 
> Mar 19 20:04:36 debian kernel: [0.221101] ACPI Error: No handler
> for Region [CMS0] (88026e048e00) [SystemCMOS]
> (20140424/evregion-163)
> Mar 19 20:04:36 debian kernel: [0.221104] ACPI Error: Region
> SystemCMOS (ID=5) has no handler (20140424/exfldio-297)
> Mar 19 20:04:36 debian kernel: [0.221106] ACPI Error: Method
> parse/execution failed [\_SB_.PCI0._INI] (Node 88026e04e8d8),
> AE_NOT_EXIST (20140424/psparse-536)
> Mar 19 20:04:36 debian kernel: [   11.093996] EXT4-fs (sda4):
> re-mounted. Opts: errors=remount-ro
> Mar 19 20:04:36 debian lightdm[856]: ** (lightdm:856): WARNING **:
> Error getting user list from org.freedesktop.Accounts:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.Accounts was not provided by any .service files
> Mar 19 20:04:40 debian lightdm[856]: ** (process:902): WARNING **:
> Error getting user list from org.freedesktop.Accounts:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.Accounts was not provided by any .service files
> Mar 19 20:05:00 debian lightdm[856]: ** (process:987): WARNING **:
> Error getting user list from org.freedesktop.Accounts:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.Accounts was not provided by any .service files
> Mar 19 20:09:18 debian kernel: [  300.212411] mce: [Hardware Error]:
> Machine check events logged
> Mar 19 20:42:35 debian org.a11y.atspi.Registry[978]:
> g_dbus_connection_real_closed: Remote peer vanished with error:
> Underlying GIOStream returned 0 bytes on an async read
> (g-io-error-quark, 0). Exiting.
> Mar 19 20:43:46 debian kernel: [0.237081] ACPI Error: No handler
> for Region [CMS0] (88026e048e00) [SystemCMOS]
> (20140424/evregion-163)
> Mar 19 20:43:46 debian kernel: [0.237084] ACPI Error: Region
> SystemCMOS (ID=5) has no handler (20140424/exfldio-297)
> Mar 19 20:43:46 debian kernel: [0.237086] ACPI Error: Method
> parse/execution failed [\_SB_.PCI0._INI] (Node 88026e04e8d8),
> AE_NOT_EXIST (20140424/psparse-536)
> Mar 19 20:43:46 debian kernel: [   11.975204] EXT4-fs (sda4):
> re-mounted. Opts: errors=remount-ro
> Mar 19 20:43:46 debian lightdm[854]: ** (lightdm:854): WARNING **:
> Error getting user list from org.freedesktop.Accounts:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.Accounts was not provided by any .service files
> Mar 19 20:43:50 debian lightdm[854]: ** (process:906): WARNING **:
> Error getting user list from org.freedesktop.Accounts:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.Accounts was not provided by any .service files
> Mar 19 20:44:24 debian lightdm[854]: ** (process:991): WARNING **:
> Error getting user list from org.freedesktop.Accounts:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.Accounts was not provided by any .service files
> Mar 19 20:48:27 debian kernel: [  300.204379] mce: [Hardware Error]:
> Machine check events logged

This does not look good.


pgpnMBd5bLLut.pgp
Description: OpenPGP digital signature

Re: computer cann't shut down

2016-03-20 Thread Adam Wilson 
On Sat, 19 Mar 2016 22:00:46 +0800
lina  wrote:

> p# shutdown -f now
> Code should not be reached 'Unhandled option' at
> ../src/systemctl/systemctl.c:6316, function shutdown_parse_argv().
> Aborting.
> Aborted

Try running "poweroff" as root.


pgpFdiK9O0GrX.pgp
Description: OpenPGP digital signature

Re: computer cann't shut down

2016-03-20 Thread Adam Wilson 
On Sun, 20 Mar 2016 10:42:54 +0800
lina  wrote:

> On Sun, Mar 20, 2016 at 12:19 AM, Patrick Bartek
>  wrote:
> > On Sat, 19 Mar 2016, lina wrote:
> >  
> >> Every time since I installed the system,  
> >
> > Which one?  Jessie?  Testing (Stretch)?, Unstable?
> >  
> 
> Jessie stable;
> 
> > Which desktop, if any?  
> 
> on my new iMac.
> 
> >
> > What computer?
> >
> > During the install, what options did you choose?  Or did you just
> > use the defaults?  
> 
> most use default, except partition.

This is probably irrelevant to the issue, but what is your partition
scheme?


pgpwBOk19Tx7G.pgp
Description: OpenPGP digital signature

Re: computer cann't shut down

2016-03-20 Thread Adam Wilson 
On Sun, 20 Mar 2016 05:28:55 +0100
Jerome BENOIT  wrote:

> Hello Forum:
> 
> On 20/03/16 04:42, Michael Milliman wrote:
> > 
> > 
> > On 03/19/2016 09:40 PM, lina wrote:  
> >> shutdown -h now
> >> 
> >> doesn't work. it still reboot.
> >>   
> > This sounds like an issue with the hardware or BIOS not with the
> > Debian OS, or with the Desktop environment.  Though I have not had
> > this problem, I have had several others related to
> > shutdown/reboot/suspend/hibernate on various machines, but I know
> > for a fact that all such problems have been with the hardware/BIOS,
> > not the Debian software.  I don't know enough about the iMac to
> > offer anything more.  
> 
> Does recent iMac have a BIOS ?


What do you mean by this?

Of course Macs have *initialisation firmware* (about which I know
nothing) but not necessarily MBR BIOS as seen on PCs.


pgpD2s_61UvYA.pgp
Description: OpenPGP digital signature

Re: computer cann't shut down

2016-03-20 Thread Adam Wilson 
On Sun, 20 Mar 2016 00:16:38 +
Lisi Reisz  wrote:

> On Saturday 19 March 2016 23:37:05 Patrick Bartek wrote:
> > On Sat, 19 Mar 2016, David Christensen wrote:  
> > > On 03/19/2016 05:40 AM, lina wrote:  
> > > > Every time since I installed the system,
> > > >
> > > > every time I tried Shut Down, it mainly restart again.
> > > >
> > > > I checked online and tried several methods but still don't work.
> > > >
> > > > Can anyone suggest me how to solve it.  
> > >
> > > I'm having the same issue:
> > >
> > >  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818311
> > >
> > > So far, no progress in resolving it.  
> >
> > No problem here.  'shutdown -h now' (as root) works as it should.
> > Wheezy 64-bit, fully up-to-date; no desktop environments installed,
> > just Openbox window manager.  System boots to terminal, login
> > there, then startx. I like to keep things simple.
> >
> > Maybe, problem is related to a desktop environment.
> >
> > B  
> 
> No, I use a desktop, and have a desktop installed on several other
> computers I administer.  3 x Wheezy, 2 x Jessie.  TDE, variously
> 14.0.3 and 3.5.13.2. All shut down without a problem. 

I can concur. I run one Stretch machine (an ASUS N43SL) with MATE and
one Jessie machine (an ASUS Zenbook UX51vz) with MATE. Both shut down
perfectly.


pgpbVbO9LEYls.pgp
Description: OpenPGP digital signature

Re: computer cann't shut down

2016-03-20 Thread lina 
I tried shutdown -hP now

not work.

As I mentioned in another thread. This is a new iMac, I have installed
debian but still keep the Mac OS.

There is no problem to shut it down when I was in Mac OS.

But in debian, no way I can really shut down except switching off the power.

I tried to enter the BIOS, but the CMD-OPT-O-F doesn't work. will do a
further search and thanks again for suggestions.

On Sun, Mar 20, 2016 at 12:24 PM, メット  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi,
> Did u try the P switch?
>
> shutdown -hP now
>
> Hth
>
> On 2016年3月20日 12:42:27 JST, Michael Milliman  
> wrote:
>>
>>
>>On 03/19/2016 09:40 PM, lina wrote:
>>> shutdown -h now
>>>
>>> doesn't work. it still reboot.
>>>
>>This sounds like an issue with the hardware or BIOS not with the Debian
>>
>>OS, or with the Desktop environment.  Though I have not had this
>>problem, I have had several others related to
>>shutdown/reboot/suspend/hibernate on various machines, but I know for a
>>
>>fact that all such problems have been with the hardware/BIOS, not the
>>Debian software.  I don't know enough about the iMac to offer anything
>>more.
>>>
>>> On Sun, Mar 20, 2016 at 8:16 AM, Lisi Reisz 
>>wrote:
 On Saturday 19 March 2016 23:37:05 Patrick Bartek wrote:
> On Sat, 19 Mar 2016, David Christensen wrote:
>> On 03/19/2016 05:40 AM, lina wrote:
>>> Every time since I installed the system,
>>>
>>> every time I tried Shut Down, it mainly restart again.
>>>
>>> I checked online and tried several methods but still don't work.
>>>
>>> Can anyone suggest me how to solve it.
>> I'm having the same issue:
>>
>>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818311
>>
>> So far, no progress in resolving it.
> No problem here.  'shutdown -h now' (as root) works as it should.
> Wheezy 64-bit, fully up-to-date; no desktop environments installed,
>>just
> Openbox window manager.  System boots to terminal, login there,
>>then
> startx. I like to keep things simple.
>
> Maybe, problem is related to a desktop environment.
>
> B
 No, I use a desktop, and have a desktop installed on several other
>>computers I
 administer.  3 x Wheezy, 2 x Jessie.  TDE, variously 14.0.3 and
>>3.5.13.2.
 All shut down without a problem.

 Lisi

>>
>>--
>>Mike
> -BEGIN PGP SIGNATURE-
> Version: APG v1.1.1
>
> iQE9BAEBCgAnBQJW7iYaIBxNZXR0IEhlbF9LZWl0YWkgPG1ldHRAcG1hcnMuanA+
> AAoJEPao4OPC92NkPr8H/jlfwqZDy1X0fhPLt2sNpyrYv4KastEFq+5WxMJbhkIo
> MvnDMTE8ikylCCr/b0EMoko/i/wI/wm04uCctqImDGxoaivs6vm5ck0xroP7SzsB
> 31HMhduDnPSFZDcFgpVXetLOmKyxGwGpZtIAOU34tbfzDCopx2IPD5bA0p1AbwzJ
> b2gbreZ0596lNobvRxCfGm/Ksp5q2n08pjaa8JHvBsGqn7HqmHWEyfvdY8Dl2NsK
> whCEU266XKe2Z+7PboM8EBU/t0T5Lunv9GEUkUFCqfGxO1BEZSayMhOQq1RR5SBY
> z0eOdt+iLDfvZLy4DmpQgoiOT9OYBV4uAbuAJTD3fug=
> =Y/rc
> -END PGP SIGNATURE-
>

Re: computer cann't shut down

2016-03-20 Thread lina 
They have openFirmware. I will try it.

THanks,

On Sun, Mar 20, 2016 at 12:28 PM, Jerome BENOIT
 wrote:
> Hello Forum:
>
> On 20/03/16 04:42, Michael Milliman wrote:
>>
>>
>> On 03/19/2016 09:40 PM, lina wrote:
>>> shutdown -h now
>>>
>>> doesn't work. it still reboot.
>>>
>> This sounds like an issue with the hardware or BIOS not with the
>> Debian OS, or with the Desktop environment.  Though I have not had
>> this problem, I have had several others related to
>> shutdown/reboot/suspend/hibernate on various machines, but I know for
>> a fact that all such problems have been with the hardware/BIOS, not
>> the Debian software.  I don't know enough about the iMac to offer
>> anything more.
>
> Does recent iMac have a BIOS ?
>
> Jerome
>
>>>
>>> On Sun, Mar 20, 2016 at 8:16 AM, Lisi Reisz 
>>> wrote:
 On Saturday 19 March 2016 23:37:05 Patrick Bartek wrote:
> On Sat, 19 Mar 2016, David Christensen wrote:
>> On 03/19/2016 05:40 AM, lina wrote:
>>> Every time since I installed the system,
>>>
>>> every time I tried Shut Down, it mainly restart again.
>>>
>>> I checked online and tried several methods but still don't
>>> work.
>>>
>>> Can anyone suggest me how to solve it.
>> I'm having the same issue:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818311
>>
>> So far, no progress in resolving it.
> No problem here.  'shutdown -h now' (as root) works as it
> should. Wheezy 64-bit, fully up-to-date; no desktop
> environments installed, just Openbox window manager.  System
> boots to terminal, login there, then startx. I like to keep
> things simple.
>
> Maybe, problem is related to a desktop environment.
>
> B
 No, I use a desktop, and have a desktop installed on several
 other computers I administer.  3 x Wheezy, 2 x Jessie.  TDE,
 variously 14.0.3 and 3.5.13.2. All shut down without a problem.

 Lisi

>>
>

Re: computer cann't shut down

2016-03-19 Thread メット 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,
Did u try the P switch?

shutdown -hP now

Hth

On 2016年3月20日 12:42:27 JST, Michael Milliman  
wrote:
>
>
>On 03/19/2016 09:40 PM, lina wrote:
>> shutdown -h now
>>
>> doesn't work. it still reboot.
>>
>This sounds like an issue with the hardware or BIOS not with the Debian
>
>OS, or with the Desktop environment.  Though I have not had this
>problem, I have had several others related to
>shutdown/reboot/suspend/hibernate on various machines, but I know for a
>
>fact that all such problems have been with the hardware/BIOS, not the
>Debian software.  I don't know enough about the iMac to offer anything
>more.
>>
>> On Sun, Mar 20, 2016 at 8:16 AM, Lisi Reisz 
>wrote:
>>> On Saturday 19 March 2016 23:37:05 Patrick Bartek wrote:
 On Sat, 19 Mar 2016, David Christensen wrote:
> On 03/19/2016 05:40 AM, lina wrote:
>> Every time since I installed the system,
>>
>> every time I tried Shut Down, it mainly restart again.
>>
>> I checked online and tried several methods but still don't work.
>>
>> Can anyone suggest me how to solve it.
> I'm having the same issue:
>
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818311
>
> So far, no progress in resolving it.
 No problem here.  'shutdown -h now' (as root) works as it should.
 Wheezy 64-bit, fully up-to-date; no desktop environments installed,
>just
 Openbox window manager.  System boots to terminal, login there,
>then
 startx. I like to keep things simple.

 Maybe, problem is related to a desktop environment.

 B
>>> No, I use a desktop, and have a desktop installed on several other
>computers I
>>> administer.  3 x Wheezy, 2 x Jessie.  TDE, variously 14.0.3 and
>3.5.13.2.
>>> All shut down without a problem.
>>>
>>> Lisi
>>>
>
>--
>Mike
-BEGIN PGP SIGNATURE-
Version: APG v1.1.1

iQE9BAEBCgAnBQJW7iYaIBxNZXR0IEhlbF9LZWl0YWkgPG1ldHRAcG1hcnMuanA+
AAoJEPao4OPC92NkPr8H/jlfwqZDy1X0fhPLt2sNpyrYv4KastEFq+5WxMJbhkIo
MvnDMTE8ikylCCr/b0EMoko/i/wI/wm04uCctqImDGxoaivs6vm5ck0xroP7SzsB
31HMhduDnPSFZDcFgpVXetLOmKyxGwGpZtIAOU34tbfzDCopx2IPD5bA0p1AbwzJ
b2gbreZ0596lNobvRxCfGm/Ksp5q2n08pjaa8JHvBsGqn7HqmHWEyfvdY8Dl2NsK
whCEU266XKe2Z+7PboM8EBU/t0T5Lunv9GEUkUFCqfGxO1BEZSayMhOQq1RR5SBY
z0eOdt+iLDfvZLy4DmpQgoiOT9OYBV4uAbuAJTD3fug=
=Y/rc
-END PGP SIGNATURE-

Re: computer cann't shut down

2016-03-19 Thread Jerome BENOIT 
Hello Forum:

On 20/03/16 04:42, Michael Milliman wrote:
> 
> 
> On 03/19/2016 09:40 PM, lina wrote:
>> shutdown -h now
>> 
>> doesn't work. it still reboot.
>> 
> This sounds like an issue with the hardware or BIOS not with the
> Debian OS, or with the Desktop environment.  Though I have not had
> this problem, I have had several others related to
> shutdown/reboot/suspend/hibernate on various machines, but I know for
> a fact that all such problems have been with the hardware/BIOS, not
> the Debian software.  I don't know enough about the iMac to offer
> anything more.

Does recent iMac have a BIOS ?

Jerome

>> 
>> On Sun, Mar 20, 2016 at 8:16 AM, Lisi Reisz 
>> wrote:
>>> On Saturday 19 March 2016 23:37:05 Patrick Bartek wrote:
 On Sat, 19 Mar 2016, David Christensen wrote:
> On 03/19/2016 05:40 AM, lina wrote:
>> Every time since I installed the system,
>> 
>> every time I tried Shut Down, it mainly restart again.
>> 
>> I checked online and tried several methods but still don't
>> work.
>> 
>> Can anyone suggest me how to solve it.
> I'm having the same issue:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818311
> 
> So far, no progress in resolving it.
 No problem here.  'shutdown -h now' (as root) works as it
 should. Wheezy 64-bit, fully up-to-date; no desktop
 environments installed, just Openbox window manager.  System
 boots to terminal, login there, then startx. I like to keep
 things simple.
 
 Maybe, problem is related to a desktop environment.
 
 B
>>> No, I use a desktop, and have a desktop installed on several
>>> other computers I administer.  3 x Wheezy, 2 x Jessie.  TDE,
>>> variously 14.0.3 and 3.5.13.2. All shut down without a problem.
>>> 
>>> Lisi
>>> 
>

Re: computer cann't shut down

2016-03-19 Thread Michael Milliman 



On 03/19/2016 09:40 PM, lina wrote:

shutdown -h now

doesn't work. it still reboot.

This sounds like an issue with the hardware or BIOS not with the Debian 
OS, or with the Desktop environment.  Though I have not had this 
problem, I have had several others related to 
shutdown/reboot/suspend/hibernate on various machines, but I know for a 
fact that all such problems have been with the hardware/BIOS, not the 
Debian software.  I don't know enough about the iMac to offer anything more.


On Sun, Mar 20, 2016 at 8:16 AM, Lisi Reisz  wrote:

On Saturday 19 March 2016 23:37:05 Patrick Bartek wrote:

On Sat, 19 Mar 2016, David Christensen wrote:

On 03/19/2016 05:40 AM, lina wrote:

Every time since I installed the system,

every time I tried Shut Down, it mainly restart again.

I checked online and tried several methods but still don't work.

Can anyone suggest me how to solve it.

I'm having the same issue:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818311

So far, no progress in resolving it.

No problem here.  'shutdown -h now' (as root) works as it should.
Wheezy 64-bit, fully up-to-date; no desktop environments installed, just
Openbox window manager.  System boots to terminal, login there, then
startx. I like to keep things simple.

Maybe, problem is related to a desktop environment.

B

No, I use a desktop, and have a desktop installed on several other computers I
administer.  3 x Wheezy, 2 x Jessie.  TDE, variously 14.0.3 and 3.5.13.2.
All shut down without a problem.

Lisi



--
Mike

Re: computer cann't shut down

2016-03-19 Thread lina 
On Sun, Mar 20, 2016 at 12:19 AM, Patrick Bartek  wrote:
> On Sat, 19 Mar 2016, lina wrote:
>
>> Every time since I installed the system,
>
> Which one?  Jessie?  Testing (Stretch)?, Unstable?
>

Jessie stable;

> Which desktop, if any?

on my new iMac.

>
> What computer?
>
> During the install, what options did you choose?  Or did you just use
> the defaults?

most use default, except partition.

>
>> every time I tried Shut Down, it mainly restart again.
>
> Through the desktop or terminal or both?  Have you tried as root, in a
> terminal: shutdown -h now
>
>> I checked online and tried several methods but still don't work.
>>
>> Can anyone suggest me how to solve it.
>
> More information needed.  Otherwise, I'd just be guessing.
>
> B
>

Re: computer cann't shut down

2016-03-19 Thread lina 
shutdown -h now

doesn't work. it still reboot.



On Sun, Mar 20, 2016 at 8:16 AM, Lisi Reisz  wrote:
> On Saturday 19 March 2016 23:37:05 Patrick Bartek wrote:
>> On Sat, 19 Mar 2016, David Christensen wrote:
>> > On 03/19/2016 05:40 AM, lina wrote:
>> > > Every time since I installed the system,
>> > >
>> > > every time I tried Shut Down, it mainly restart again.
>> > >
>> > > I checked online and tried several methods but still don't work.
>> > >
>> > > Can anyone suggest me how to solve it.
>> >
>> > I'm having the same issue:
>> >
>> >  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818311
>> >
>> > So far, no progress in resolving it.
>>
>> No problem here.  'shutdown -h now' (as root) works as it should.
>> Wheezy 64-bit, fully up-to-date; no desktop environments installed, just
>> Openbox window manager.  System boots to terminal, login there, then
>> startx. I like to keep things simple.
>>
>> Maybe, problem is related to a desktop environment.
>>
>> B
>
> No, I use a desktop, and have a desktop installed on several other computers I
> administer.  3 x Wheezy, 2 x Jessie.  TDE, variously 14.0.3 and 3.5.13.2.
> All shut down without a problem.
>
> Lisi
>

Re: computer cann't shut down

2016-03-19 Thread Lisi Reisz 
On Saturday 19 March 2016 23:37:05 Patrick Bartek wrote:
> On Sat, 19 Mar 2016, David Christensen wrote:
> > On 03/19/2016 05:40 AM, lina wrote:
> > > Every time since I installed the system,
> > >
> > > every time I tried Shut Down, it mainly restart again.
> > >
> > > I checked online and tried several methods but still don't work.
> > >
> > > Can anyone suggest me how to solve it.
> >
> > I'm having the same issue:
> >
> >  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818311
> >
> > So far, no progress in resolving it.
>
> No problem here.  'shutdown -h now' (as root) works as it should.
> Wheezy 64-bit, fully up-to-date; no desktop environments installed, just
> Openbox window manager.  System boots to terminal, login there, then
> startx. I like to keep things simple.
>
> Maybe, problem is related to a desktop environment.
>
> B

No, I use a desktop, and have a desktop installed on several other computers I 
administer.  3 x Wheezy, 2 x Jessie.  TDE, variously 14.0.3 and 3.5.13.2.  
All shut down without a problem. 

Lisi

Re: computer cann't shut down

2016-03-19 Thread Patrick Bartek 
On Sat, 19 Mar 2016, David Christensen wrote:

> On 03/19/2016 05:40 AM, lina wrote:
> > Every time since I installed the system,
> >
> > every time I tried Shut Down, it mainly restart again.
> >
> > I checked online and tried several methods but still don't work.
> >
> > Can anyone suggest me how to solve it.
> 
> I'm having the same issue:
> 
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818311
> 
> So far, no progress in resolving it.

No problem here.  'shutdown -h now' (as root) works as it should.
Wheezy 64-bit, fully up-to-date; no desktop environments installed, just
Openbox window manager.  System boots to terminal, login there, then
startx. I like to keep things simple.

Maybe, problem is related to a desktop environment.

B

Re: computer cann't shut down

2016-03-19 Thread David Christensen 

On 03/19/2016 05:40 AM, lina wrote:

Every time since I installed the system,

every time I tried Shut Down, it mainly restart again.

I checked online and tried several methods but still don't work.

Can anyone suggest me how to solve it.


I'm having the same issue:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818311


So far, no progress in resolving it.


David

Re: computer cann't shut down

2016-03-19 Thread songbird 
Thomas Schmitt wrote:
> Hi,
>
>> p# shutdown -f now
>> Code should not be reached 'Unhandled option' at
>
> That's a rough way to tell that the option "-f" is not known.
>
> If i need to shutdown a machine (real or VM), i do as superuser
>
>   shutdown -h now
>
>
> Have a nice day :)

  ah, haha, thanks, typoed dangit!

  yes that should have been -h not -f...


  songbird

Re: computer cann't shut down

2016-03-19 Thread Patrick Bartek 
On Sat, 19 Mar 2016, lina wrote:

> Every time since I installed the system,

Which one?  Jessie?  Testing (Stretch)?, Unstable?

Which desktop, if any?

What computer?

During the install, what options did you choose?  Or did you just use
the defaults?

> every time I tried Shut Down, it mainly restart again.

Through the desktop or terminal or both?  Have you tried as root, in a
terminal: shutdown -h now

> I checked online and tried several methods but still don't work.
> 
> Can anyone suggest me how to solve it.

More information needed.  Otherwise, I'd just be guessing.

B

Re: computer cann't shut down

2016-03-19 Thread Thomas Schmitt 
Hi,

> p# shutdown -f now
> Code should not be reached 'Unhandled option' at

That's a rough way to tell that the option "-f" is not known.

If i need to shutdown a machine (real or VM), i do as superuser

  shutdown -h now


Have a nice day :)

Thomas

Re: computer cann't shut down

2016-03-19 Thread lina 
p# shutdown -f now
Code should not be reached 'Unhandled option' at
../src/systemctl/systemctl.c:6316, function shutdown_parse_argv().
Aborting.
Aborted

On Sat, Mar 19, 2016 at 9:19 PM, songbird  wrote:
> lina wrote:
>
>> Every time since I installed the system,
>>
>> every time I tried Shut Down, it mainly restart again.
>>
>> I checked online and tried several methods but still don't work.
>>
>> Can anyone suggest me how to solve it.
>
>   helps to know what version you are running, along
> with desktop or window manager.
>
>   under MATE there is an entry in the menu which
> allows for shut down.
>
>
>   or as root user i can use the command
>
> # shutdown -h now
>
>   which also works...
>
>
>   songbird
>

Re: computer cann't shut down

2016-03-19 Thread songbird 
lina wrote:

> Every time since I installed the system,
>
> every time I tried Shut Down, it mainly restart again.
>
> I checked online and tried several methods but still don't work.
>
> Can anyone suggest me how to solve it.

  helps to know what version you are running, along
with desktop or window manager.

  under MATE there is an entry in the menu which
allows for shut down.


  or as root user i can use the command

# shutdown -h now

  which also works...


  songbird

Re: computer cann't shut down

2016-03-19 Thread Andrew McGlashan 
On 19/03/2016 11:40 PM, lina wrote:
> Every time since I installed the system,
> 
> every time I tried Shut Down, it mainly restart again.

I had a weird situation with an ordinary desktop running Winblows; it
was fixed by removing the fancy Logitech keyboard and plugging in a more
simple one.  The /bad/ keyboard now lives on a server that is rarely
shutdown.

Cheers
A.



signature.asc
Description: OpenPGP digital signature

Re: computer cann't shut down

2016-03-19 Thread lina 
I tried

1] systemctl poweroff


2] GRUB_CMDLINE_LINUX_DEFAULT="quiet"

to quite splash acpi=force

The syslog error is as below:

Mar 19 20:04:36 debian kernel: [0.221101] ACPI Error: No handler
for Region [CMS0] (88026e048e00) [SystemCMOS]
(20140424/evregion-163)
Mar 19 20:04:36 debian kernel: [0.221104] ACPI Error: Region
SystemCMOS (ID=5) has no handler (20140424/exfldio-297)
Mar 19 20:04:36 debian kernel: [0.221106] ACPI Error: Method
parse/execution failed [\_SB_.PCI0._INI] (Node 88026e04e8d8),
AE_NOT_EXIST (20140424/psparse-536)
Mar 19 20:04:36 debian kernel: [   11.093996] EXT4-fs (sda4):
re-mounted. Opts: errors=remount-ro
Mar 19 20:04:36 debian lightdm[856]: ** (lightdm:856): WARNING **:
Error getting user list from org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
Mar 19 20:04:40 debian lightdm[856]: ** (process:902): WARNING **:
Error getting user list from org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
Mar 19 20:05:00 debian lightdm[856]: ** (process:987): WARNING **:
Error getting user list from org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
Mar 19 20:09:18 debian kernel: [  300.212411] mce: [Hardware Error]:
Machine check events logged
Mar 19 20:42:35 debian org.a11y.atspi.Registry[978]:
g_dbus_connection_real_closed: Remote peer vanished with error:
Underlying GIOStream returned 0 bytes on an async read
(g-io-error-quark, 0). Exiting.
Mar 19 20:43:46 debian kernel: [0.237081] ACPI Error: No handler
for Region [CMS0] (88026e048e00) [SystemCMOS]
(20140424/evregion-163)
Mar 19 20:43:46 debian kernel: [0.237084] ACPI Error: Region
SystemCMOS (ID=5) has no handler (20140424/exfldio-297)
Mar 19 20:43:46 debian kernel: [0.237086] ACPI Error: Method
parse/execution failed [\_SB_.PCI0._INI] (Node 88026e04e8d8),
AE_NOT_EXIST (20140424/psparse-536)
Mar 19 20:43:46 debian kernel: [   11.975204] EXT4-fs (sda4):
re-mounted. Opts: errors=remount-ro
Mar 19 20:43:46 debian lightdm[854]: ** (lightdm:854): WARNING **:
Error getting user list from org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
Mar 19 20:43:50 debian lightdm[854]: ** (process:906): WARNING **:
Error getting user list from org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
Mar 19 20:44:24 debian lightdm[854]: ** (process:991): WARNING **:
Error getting user list from org.freedesktop.Accounts:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Accounts was not provided by any .service files
Mar 19 20:48:27 debian kernel: [  300.204379] mce: [Hardware Error]:
Machine check events logged

computer cann't shut down

2016-03-19 Thread lina 
Every time since I installed the system,

every time I tried Shut Down, it mainly restart again.

I checked online and tried several methods but still don't work.

Can anyone suggest me how to solve it.

Thanks,