Re: a stop job is running for user manager

> > > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: >> >> > >> Since upgrading to Debian 11 I sometimes see "a stop job is running >> >> > >> for >> >> > >> user manager..." on shutdown and it waits 9

Re: a stop job is running for user manager

0), Richmond wrote: > >> > >> Since upgrading to Debian 11 I sometimes see "a stop job is running > >> > >> for > >> > >> user manager..." on shutdown and it waits 90 seconds. The last comment > >> > >> in th

Re: a stop job is running for user manager

error if any relates to the delay. > > 2022-02-18, pn, 03:28 David Wright rašė: >> >> On Thu 17 Feb 2022 at 13:44:46 (+), Richmond wrote: >> > David Wright writes: >> > > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: >> > >> S

Re: a stop job is running for user manager

(+), Richmond wrote: > > David Wright writes: > > > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: > > >> Since upgrading to Debian 11 I sometimes see "a stop job is running for > > >> user manager..." on shutdown and it waits 90 seconds.

Re: a stop job is running for user manager

On Thu 17 Feb 2022 at 13:44:46 (+), Richmond wrote: > David Wright writes: > > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: > >> Since upgrading to Debian 11 I sometimes see "a stop job is running for > >> user manager..." on shutdown and

Re: a stop job is running for user manager

David Wright writes: > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >> user manager..." on shutdown and it waits 90 seconds. The last comment >> in this thread says "Insta

Re: a stop job is running for user manager

David Wright writes: > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >> user manager..." on shutdown and it waits 90 seconds. The last comment >> in this thread says "Insta

Re: a stop job is running for user manager

On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: > Since upgrading to Debian 11 I sometimes see "a stop job is running for > user manager..." on shutdown and it waits 90 seconds. The last comment > in this thread says "Installing systemd from backsports solved

Re: A stop job is running for...

On 12/05/2015 01:21 AM, Himanshu Shekhar wrote: Well, Google shall help! The two articles seem much technical for a kid like me. Still, the content made me feel that there shall be something convincing, which is why I posted it on this mail. 1.

Re: A stop job is running for...

ther 90 seconds and nothing else > >> happens (for hours). eg > >> > >> [ <*> ] A stop job is running for Manage, Install and Generate Color > >> Profiles (34min 54s / 36min)_ > >> > >> Fortunately, that hasn't happened for a few months. It

Systemd debugging (was ... Re: A stop job is running for...)

On Thu, Dec 03, 2015 at 10:07:01PM +0100, Michael Biebl wrote: > Two issues that come to mind here: > a/ cups-browsed.service declares a dependency on avahi-daemon.service. > So it should be stopped before avahi-daemon. But apparently you don't > have any avahi-daemon process anymore. > Would be

Re: A stop job is running for...

Well, Google shall help! The two articles seem much technical for a kid like me. Still, the content made me feel that there shall be something convincing, which is why I posted it on this mail. 1. https://lists.fedoraproject.org/pipermail/users/2014-February/446722.html # for NTP 2.

Re: A stop job is running for...

On Thu, 03 Dec 2015, David Wright wrote: > Which data do you mean? For example, a database server[1] which has a transaction outstanding or needs a long time to write to disk for an orderly shutdown. > By the time these Stop jobs start running, there are just system > processes running. I don't

Re: A stop job is running for...

HTTP; Thu, 3 Dec 2015 02:17:13 -0800 (PST) Received: by 10.202.67.66 with HTTP; Thu, 3 Dec 2015 02:17:13 -0800 (PST) In-Reply-To: <565d0045.4040...@comcast.net> References: <565d0045.4040...@comcast.net> Date: Thu, 3 Dec 2015 15:47:13 +0530 Message-ID: Subject: Re: A stop job is running

Re: A stop job is running for...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Dec 03, 2015 at 05:50:09AM -0500, Gene Heskett wrote: > On Thursday 03 December 2015 02:41:57 Nicolas George wrote: [...] > > Libre Software development is a meritocracy, not a democracy [...] Hm. Somehow I feel that while true, this is

Re: A stop job is running for...

On Thursday 03 December 2015 02:41:57 Nicolas George wrote: > Le duodi 12 frimaire, an CCXXIV, Gene Heskett a écrit : > >But it bugs the heck out of me that the guy/gal > > doing the codeing doesn't watch the user lists, so it all has to > > wait on someone qualified enough to

Re: A stop job is running for...

On 12/03/2015 05:22 AM, Himanshu Shekhar wrote: The complete message is really important. Perhaps, I would investigate. Hello! I did give the complete messages. Both start with A stop job is running for... The endings are Make remote CUPS printers available locally and Network Time

Re: A stop job is running for...

On Wed 02 Dec 2015 at 16:59:23 (-0600), Don Armstrong wrote: > On Wed, 02 Dec 2015, Jape Person wrote: > > It's occurred to me that, though I have occasionally seen service > > shutown issues with sysv-init, they were never as pervasive or > > repetitve as it has been since switching to systemd as

Re: A stop job is running for...

On 12/03/2015 01:00 PM, Michael Biebl wrote: Am 03.12.2015 um 18:18 schrieb Jape Person: A stop job is running for... The endings are Make remote CUPS printers available locally and Network Time Synchronization I've checked for CUPS and NTP errors in the logs and have found nothing. I

Re: A stop job is running for...

Am 03.12.2015 um 21:21 schrieb Jape Person: > /usr/sbin/cupsd -l > root 715 0.0 0.1 250812 8680 ?Ssl 11:37 0:00 > /usr/sbin/cups-browsed > lp 993 0.0 0.0 78772 5584 ?S11:38 0:00 > /usr/lib/cups/notifier/dbus dbus:// > root 1114 0.0 0.0 43828

Re: A stop job is running for...

start with A stop job is running for... The endings are Make remote CUPS printers available locally and Network Time Synchronization I've checked for CUPS and NTP errors in the logs and have found nothing. I presume that's because this happens during shutdown, but haven't done enough re

Re: A stop job is running for...

Am 03.12.2015 um 18:18 schrieb Jape Person: > A stop job is running for... > > The endings are > > Make remote CUPS printers available locally > > and > > Network Time Synchronization > > I've checked for CUPS and NTP errors in the logs and have found no

Re: A stop job is running for...

Hi JP On Dec 3, 2015, at 9:18 AM, Jape Person <jap...@comcast.net> wrote: > On 12/03/2015 05:22 AM, Himanshu Shekhar wrote: >> The complete message is really important. Perhaps, I >> would investigate. > > Hello! > > I did give the complete messages. Both star

Re: A stop job is running for...

On 12/02/2015 06:06 AM, Martin Read wrote: On 02/12/15 03:07, James P. Wallen wrote: Thanks for your response, Sven. It's nice to know that someone else has seen this type of problem. I was thinking that this could be self-inflicted. Perhaps that's a little less likely now. So, is this

Re: A stop job is running for...

seconds is reached, the limit increases by another 90 seconds and nothing else happens (for hours). eg [ <*> ] A stop job is running for Manage, Install and Generate Color Profiles (34min 54s / 36min)_ Fortunately, that hasn't happened for a few months. It's very embarrassing when my laptop takes longer to close down than my wife's W10. Cheers, David.

Re: A stop job is running for...

On 12/02/2015 06:06 AM, Martin Read wrote: The default and per-service timeout values for stopping a service (after which systemd gives up and sends fatal signals to all of the service's processes) are configurable; see the systemd-system.conf(5) and systemd.service(5) man pages for details.

Re: A stop job is running for...

On Wednesday 02 December 2015 06:06:09 Martin Read wrote: > On 02/12/15 03:07, James P. Wallen wrote: > > Thanks for your response, Sven. It's nice to know that someone else > > has seen this type of problem. I was thinking that this could be > > self-inflicted. Perhaps that's a little less

Re: A stop job is running for...

(for hours). eg [ <*> ] A stop job is running for Manage, Install and Generate Color Profiles (34min 54s / 36min)_ Fortunately, that hasn't happened for a few months. It's very embarrassing when my laptop takes longer to close down than my wife's W10. Cheers, David. Now *that* would be an

Re: A stop job is running for...

[ <*> ] A stop job is running for Manage, Install and Generate Color Profiles (34min 54s / 36min)_ Fortunately, that hasn't happened for a few months. It's very embarrassing when my laptop takes longer to close down than my wife's W10. Sounds like it could be hard to reproduce indeed.

Re: A stop job is running for...

Am 02.12.2015 um 18:05 schrieb Jape Person: > On 12/02/2015 10:49 AM, David Wright wrote: >> I have observed behaviour where, when the time limit of 90 seconds is >> reached, the limit increases by another 90 seconds and nothing else >> happens (for hours). eg >> >&

Re: A stop job is running for...

On 12/02/2015 01:21 PM, Gene Heskett wrote: On Wednesday 02 December 2015 06:06:09 Martin Read wrote: On 02/12/15 03:07, James P. Wallen wrote: Thanks for your response, Sven. It's nice to know that someone else has seen this type of problem. I was thinking that this could be self-inflicted.

Re: A stop job is running for...

Am 02.12.2015 um 18:58 schrieb Jape Person: > On 12/02/2015 12:17 PM, Michael Biebl wrote: >> In case you run into such a situation again, where a service is blocking >> the shutdown you can of course just use force and pull the plug or use >> sysrq b. >> But there is a nicer alternative: just hit

Re: A stop job is running for...

On 12/02/2015 02:04 PM, Michael Biebl wrote: Am 02.12.2015 um 18:58 schrieb Jape Person: On 12/02/2015 12:17 PM, Michael Biebl wrote: In case you run into such a situation again, where a service is blocking the shutdown you can of course just use force and pull the plug or use sysrq b. But

Re: A stop job is running for...

On Wed, 02 Dec 2015, Jape Person wrote: > It's occurred to me that, though I have occasionally seen service > shutown issues with sysv-init, they were never as pervasive or > repetitve as it has been since switching to systemd as the init > system. This is generally because sysv-init tends to not

Re: A stop job is running for...

On Wednesday 02 December 2015 14:02:50 Jape Person wrote: > On 12/02/2015 01:21 PM, Gene Heskett wrote: > > On Wednesday 02 December 2015 06:06:09 Martin Read wrote: > >> On 02/12/15 03:07, James P. Wallen wrote: > >>> Thanks for your response, Sven. It's nice to know that someone > >>> else has

Re: A stop job is running for...

On Thu, 3 Dec 2015 15:48:07 +1300 Chris Bannister wrote: > On Wed, Dec 02, 2015 at 08:12:24PM -0500, Gene Heskett wrote: > > > > In the meantime, its hit another 200 users, discouraging them from ever > > touching linux again. In that regard, we are our own worst

Re: A stop job is running for...

On Wednesday 02 December 2015 21:48:07 Chris Bannister wrote: > On Wed, Dec 02, 2015 at 08:12:24PM -0500, Gene Heskett wrote: > > In the meantime, its hit another 200 users, discouraging them from > > ever touching linux again. In that regard, we are our own worst > > enemy at times.

Re: A stop job is running for...

On Wednesday 02 December 2015 22:05:10 Neal P. Murphy wrote: > On Thu, 3 Dec 2015 15:48:07 +1300 > > Chris Bannister wrote: > > On Wed, Dec 02, 2015 at 08:12:24PM -0500, Gene Heskett wrote: > > > In the meantime, its hit another 200 users, discouraging them from > > >

Re: A stop job is running for...

Le duodi 12 frimaire, an CCXXIV, Gene Heskett a écrit : > But it bugs the heck out of me that the guy/gal > doing the codeing doesn't watch the user lists, so it all has to wait on > someone qualified enough to wade thru the bug reporter forms and > actually file the bug.

Re: A stop job is running for...

On Wed, Dec 02, 2015 at 08:12:24PM -0500, Gene Heskett wrote: > > In the meantime, its hit another 200 users, discouraging them from ever > touching linux again. In that regard, we are our own worst enemy at > times. Unfortunately, the oar I steer this ship with could be swapped > for a

Re: A stop job is running for...

On 12/02/2015 05:59 PM, Don Armstrong wrote: On Wed, 02 Dec 2015, Jape Person wrote: It's occurred to me that, though I have occasionally seen service shutown issues with sysv-init, they were never as pervasive or repetitve as it has been since switching to systemd as the init system. This is

Re: A stop job is running for...

On 02/12/15 03:07, James P. Wallen wrote: Thanks for your response, Sven. It's nice to know that someone else has seen this type of problem. I was thinking that this could be self-inflicted. Perhaps that's a little less likely now. So, is this behavior controlled by systemd? I'm not trying to

Re: A stop job is running for...

On 12/01/2015 09:47 AM, Sven Arvidsson wrote: On Mon, 2015-11-30 at 21:04 -0500, Jape Person wrote: Make remote CUPS printers available locally Network Time Synchronization For several weeks I've been seeing this stop job notification for these two items frequently when rebooting or shutting

Re: A stop job is running for...

On Mon, 2015-11-30 at 21:04 -0500, Jape Person wrote: > Make remote CUPS printers available locally > Network Time Synchronization > > For several weeks I've been seeing this stop job notification for > these > two items frequently when rebooting or shutting down two of my four > testing

A stop job is running for...

Make remote CUPS printers available locally Network Time Synchronization For several weeks I've been seeing this stop job notification for these two items frequently when rebooting or shutting down two of my four testing systems. The first notification counts all the way up to 1 min 30 sec

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Fri, Aug 15, 2014 at 7:46 AM, Chris Bannister cbannis...@slingshot.co.nz wrote: On Thu, Aug 14, 2014 at 10:35:11AM -0400, Tom H wrote: Stop in stop job isn't an adjective, it's a noun (or an attributive noun) just like office in office chair. Or it could be a verb, as in a command Stop

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On 20140814_1035-0400, Tom H wrote: On Thu, Aug 14, 2014 at 1:04 AM, Paul E Condon pecon...@mesanetworks.net wrote: In English, both 'stop job' and 'stopped job' are an adjective modifying a noun. The noun in both cases is 'job'. 'stop job' is a noun phrase expressing a type of job, and

RE: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

Hi, I interpret the quoted string in the Subject: header as being flawed use of English language. 'stop' should be 'stopped'. And, there is a That would definitely be clearer. I was interpreting it as some special systemd shutdown-ey thing which runs around trying to stop things, and

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Thu, Aug 14, 2014 at 10:35:11AM -0400, Tom H wrote: On Thu, Aug 14, 2014 at 1:04 AM, Paul E Condon pecon...@mesanetworks.net wrote: In English, both 'stop job' and 'stopped job' are an adjective modifying a noun. The noun in both cases is 'job'. 'stop job' is a noun phrase expressing

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Fri, 15 Aug 2014, Bonno Bloksma wrote: I wonder if the people developing this are paying attention to a development in de Windows environment where the latest thing is that de service can report back that it is indeed still trying to stop and not just hung and not reporting back. Windows

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On 8/15/14, Henrique de Moraes Holschuh h...@debian.org wrote: On Fri, 15 Aug 2014, Bonno Bloksma wrote: I wonder if the people developing this are paying attention to a development in de Windows environment where the latest thing is that de service can report back that it is indeed still

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Fri, 15 Aug 2014 09:19:48 + Bonno Bloksma b.blok...@tio.nl wrote: I wonder if the people developing this are paying attention to a development in de Windows environment where the latest thing is that de service can report back that it is indeed still trying to stop and not just hung

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Fri, Aug 15, 2014 at 09:38:14AM -0400, Steve Litt wrote: Some processes don't work well together, and systemd can maintain a database of such processes, perhaps in Postgres, to prevent one of those processes from running if the other is already running, unless the processes themselves tell

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

Le 12/08/2014 17:48, Michael Biebl a écrit : Am 12.08.2014 17:16, schrieb Hugo Vanwoerkom: Right. Debian Sid. 'halt' does not poweroff with systemd. Well, yeah. halt is not supposed to power off your system. But that is most likely not the issue Zenaan is having SAme thing wirh stop

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Fri, 15 Aug 2014, Erwan David wrote: Right. Debian Sid. 'halt' does not poweroff with systemd. The halt/reboot/poweroff binary shipped from sysvinit source will request a direct power-off, halt or reboot to the kernel. Just give it the -f option. And don't complain if this causes data

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Fri, 15 Aug 2014, Jonathan de Boyne Pollard wrote: Bonno Bloksma: I wonder if the people developing this are paying attention to a development in de Windows environment where the latest thing is that de service can report back that it is indeed still trying to stop and not just hung

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

Hi. On Sat, 16 Aug 2014 02:12:48 +1200 Chris Bannister cbannis...@slingshot.co.nz wrote: You mean systemd should shoulder some of the kernel's work? A database of conflicting processes is a half-measure. Moreover, an existing implementation of RDBMS older than systemd such as Postgres is

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On 8/14/14, Paul E Condon pecon...@mesanetworks.net wrote: I should stop. I really have very little firm knowledge of systemd, just opinions that make sense to me. (tm) That's TM for YOU son! It's formal english thank you very much. and (tm) is a very sloppy rendition!! I don't know that we can

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Thu, Aug 14, 2014 at 10:03:31PM +1000, Zenaan Harkness wrote: On 8/14/14, Paul E Condon pecon...@mesanetworks.net wrote: I should stop. I really have very little firm knowledge of systemd, just opinions that make sense to me. (tm) That's TM for YOU son! It's formal english thank you

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On 8/14/14, Darac Marjal mailingl...@darac.org.uk wrote: On Thu, Aug 14, 2014 at 10:03:31PM +1000, Zenaan Harkness wrote: On 8/14/14, Paul E Condon pecon...@mesanetworks.net wrote: I should stop. I really have very little firm knowledge of systemd, just opinions that make sense to me. (tm)

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

Zenaan Harkness writes: ChrisBanalGrammatistica, Grammatistica? Which language does this word belong to? Ancient Debianese, possibly pre-Vax era? -- /\ ___Ubuntu: ancient /___/\_|_|\_|__|___Gian Uberto Lauri_ African word

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Thu, Aug 14, 2014 at 1:04 AM, Paul E Condon pecon...@mesanetworks.net wrote: In English, both 'stop job' and 'stopped job' are an adjective modifying a noun. The noun in both cases is 'job'. 'stop job' is a noun phrase expressing a type of job, and must be some kind of geeky usage. OTOH,

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On 12/08/14 22:23, Lisi Reisz wrote: On Tuesday 12 August 2014 17:53:19 Martin Steigerwald wrote: But if the english meaning of the words give exact this difference, so well. In my understanding there never was much of a difference between halt and poweroff. I'm not quite clear what you are

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/14/2014 10:35 AM, Tom H wrote: On Thu, Aug 14, 2014 at 1:04 AM, Paul E Condon pecon...@mesanetworks.net wrote: In English, both 'stop job' and 'stopped job' are an adjective modifying a noun. The noun in both cases is 'job'. 'stop job'

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On 2014-08-14, Iain M Conochie i...@thargoid.co.uk wrote: Yet this is exactly what my 2 year old car does now. I halt at the lights and the engine powers off. Is this a bug? Depends. Given enough usage, a bug can become a feature. Some clever folks turn bugs into features, I reckon:

Grammatisticality: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Thu, 14 Aug 2014 16:14:09 +0200 sa...@eng.it wrote: Zenaan Harkness writes: ChrisBanalGrammatistica, Grammatistica? Which language does this word belong to? Ancient Debianese, possibly pre-Vax era? At this point, mightn't it be good to change the subject, just in case the original

Re: Grammatisticality: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On 8/15/14, Steve Litt sl...@troubleshooters.com wrote: On Thu, 14 Aug 2014 16:14:09 +0200 sa...@eng.it wrote: Zenaan Harkness writes: ChrisBanalGrammatistica, Grammatistica? Which language does this word belong to? Ancient Debianese, possibly pre-Vax era? At this point, mightn't it be

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Tue, Aug 12, 2014 at 2:51 PM, Paul E Condon pecon...@mesanetworks.net wrote: I interpret the quoted string in the Subject: header as being flawed use of English language. 'stop' should be 'stopped'. And, there is a bug in the script that fails to evaluate the variable USER and therefore

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Wed, Aug 13, 2014 at 11:15:22AM +1000, Zenaan Harkness wrote: On 8/13/14, Paul E Condon pecon...@mesanetworks.net wrote: I interpret the quoted string in the Subject: header as being flawed use of English language. 'stop' should be 'stopped'. And, there is a That would definitely be

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On 20140813_1033+0100, Darac Marjal wrote: On Wed, Aug 13, 2014 at 11:15:22AM +1000, Zenaan Harkness wrote: On 8/13/14, Paul E Condon pecon...@mesanetworks.net wrote: I interpret the quoted string in the Subject: header as being flawed use of English language. 'stop' should be 'stopped'.

systemd fails to poweroff - A stop job is running for Session 2 of user $USER

Debian sid systemd currently fails to poweroff for me XFCE (appears to) exit, the mouse point shows for a while, then the kernel/ shutdown log appears. The last message is: A stop job is running for Session 2 of user me Red asterisks (up to 3) appear to oscillate at left edge in an ascii wait

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

Am 12.08.2014 16:50, schrieb Zenaan Harkness: Debian sid systemd currently fails to poweroff for me XFCE (appears to) exit, the mouse point shows for a while, then the kernel/ shutdown log appears. The last message is: A stop job is running for Session 2 of user me Red asterisks (up

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

Zenaan Harkness wrote: Debian sid systemd currently fails to poweroff for me XFCE (appears to) exit, the mouse point shows for a while, then the kernel/ shutdown log appears. The last message is: A stop job is running for Session 2 of user me Red asterisks (up to 3) appear to oscillate

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Wed, 13 Aug 2014 00:50:31 +1000 Zenaan Harkness z...@freedbms.net wrote: Red asterisks (up to 3) appear to oscillate at left edge in an ascii wait for me animation. You're a lucky guy: I don't have even one asterisk (only a white underscore and a blinking cursor - on a laptop). But I'm not

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

Am 12.08.2014 17:16, schrieb Hugo Vanwoerkom: Right. Debian Sid. 'halt' does not poweroff with systemd. Well, yeah. halt is not supposed to power off your system. But that is most likely not the issue Zenaan is having -- Why is it that all of the instruments seeking intelligent life in the

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Tue, Aug 12, 2014 at 10:16:27AM -0500, Hugo Vanwoerkom wrote: Zenaan Harkness wrote: Debian sid systemd currently fails to poweroff for me XFCE (appears to) exit, the mouse point shows for a while, then the kernel/ shutdown log appears. The last message is: A stop job is running

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Tue, Aug 12, 2014 at 5:16 PM, Hugo Vanwoerkom hvw59...@care2.com wrote: Zenaan Harkness wrote: Debian sid systemd currently fails to poweroff for me XFCE (appears to) exit, the mouse point shows for a while, then the kernel/ shutdown log appears. The last message is: A stop job

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

Am Dienstag, 12. August 2014, 17:48:10 schrieb Michael Biebl: Am 12.08.2014 17:16, schrieb Hugo Vanwoerkom: Right. Debian Sid. 'halt' does not poweroff with systemd. Well, yeah. halt is not supposed to power off your system. Interestingly in the last ten years I have used halt exactly to

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Tue, Aug 12, 2014 at 10:50 AM, Zenaan Harkness z...@freedbms.net wrote: Debian sid systemd currently fails to poweroff for me XFCE (appears to) exit, the mouse point shows for a while, then the kernel/ shutdown log appears. The last message is: A stop job is running for Session 2

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

/ shutdown log appears. The last message is: A stop job is running for Session 2 of user me Red asterisks (up to 3) appear to oscillate at left edge in an ascii wait for me animation. Requires hard powercycle to poweroff. How might I debug this? Right. Debian Sid. 'halt

[OT] on wording of computer messages [was: Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER]

On Ma, 12 aug 14, 12:51:12, Paul E Condon wrote: I interpret the quoted string in the Subject: header as being flawed use of English language. 'stop' should be 'stopped'. And, there is a ... In a better formulated message, there should be a comma ',' between 'user' and '$USER'. Thus if the

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On Tuesday 12 August 2014 17:53:19 Martin Steigerwald wrote: But if the english meaning of the words give exact this difference, so well. In my understanding there never was much of a difference between halt and poweroff. I'm not quite clear what you are saying, but if you are saying that

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

is: A stop job is running for Session 2 of user me Red asterisks (up to 3) appear to oscillate at left edge in an ascii wait for me animation. Requires hard powercycle to poweroff. How might I debug this? https://lists.debian.org/debian-user/2014/07/msg01108.html I've been assuming

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On 8/13/14, Michael Biebl bi...@debian.org wrote: The last message is: A stop job is running for Session 2 of user me Red asterisks (up to 3) appear to oscillate at left edge in an ascii wait for me animation. eye of cylon (thanks to who mentioned that) Have you waited at least 90 secs

Re: systemd fails to poweroff - A stop job is running for Session 2 of user $USER

On 8/13/14, Paul E Condon pecon...@mesanetworks.net wrote: I interpret the quoted string in the Subject: header as being flawed use of English language. 'stop' should be 'stopped'. And, there is a That would definitely be clearer. I was interpreting it as some special systemd shutdown-ey thing