[SOLVED] Shutdown in X seconds! Hey where did that come from??
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware, Debian, LFS, Ubuntu, Solaris
Posts: 11
Rep:
Quote:
Originally Posted by gezley
What does ps afx tell you when this dialog box appears? (If the dialog box prevents you opening a terminal in KDE then switch to a virtual console instead, with Ctrl+Alt+F2 or F3.) Don't cancel the dialog box - ps afx should show you which process is invoking it.
Can you post the output from gezley's suggestion? It might give you a hint as to what's going on.
Yes it is a good suggestion. But as I said I am trying it in safe mode for the mo as a way of eliminating/confirming possible KDE problem or setting. Next time it happens and I am around will give it a go.
Ok, so latest update. Just tried to shutdown again. This is the output from ps auf when the shutdown dialogue appears.
And the output from the command I suggested was ... ?
Quote:
Suggestions??
I consider it impolite to demand other suggestions while riding roughshod over the suggestions already offered. Please pay me the courtesy of reading my earlier suggestion a little more carefully, and then come back for more suggestions if the output from that command does not throw light on your problem.
Last edited by Gerard Lally; 08-30-2012 at 07:05 PM.
Back again. Have not forgotten, just waiting for the inevitable to happen again. Thanks for the suggestions. emgee_1, gauchao & vtel57... yes that had occurred to me too, was just trying to elminate software issues first. However I have got my lm-sensors up and running and will check temps alongside any software issues.
So I had the shutdown dialogue pop up again. However, someone else was at my computer at the time and before I had chance to switch to vt I think he cancelled it (not sure, it was a bit quick and I did not have time to confirm or otherwise as I needed to switch to vt quickly). So this output may or may NOT contain evidence of the problem. Maybe you guys can just give it a look over and see if you can see anything obvious? If not will have to try again on the next occurrence.
it8718-isa-0290
Adapter: ISA adapter
in0: +1.33 V (min = +0.00 V, max = +4.08 V)
in1: +1.95 V (min = +0.00 V, max = +4.08 V)
in2: +3.15 V (min = +0.00 V, max = +4.08 V)
in3: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM
in4: +2.98 V (min = +0.00 V, max = +4.08 V)
in5: +2.59 V (min = +0.00 V, max = +4.08 V)
in6: +0.10 V (min = +0.00 V, max = +4.08 V)
in7: +3.15 V (min = +0.00 V, max = +4.08 V)
Vbat: +3.10 V
fan1: 1854 RPM (min = 10 RPM)
fan2: 0 RPM (min = 10 RPM) ALARM
temp1: +47.0�C (low = +127.0�C, high = +127.0�C) sensor = thermistor
temp2: +51.0�C (low = +127.0�C, high = +127.0�C) sensor = thermistor
temp3: +55.0�C (low = +127.0�C, high = +127.0�C) sensor = thermal diode
cpu0_vid: +1.250 V
About the two ALARMS. The one at in3. I have no idea what this is but since installing lm-sensors a few days ago it has always showed this. And fan2. 0 rmp. I have two fans in my system, one case fan and one cpu fan. They are both running so assume this is some error. (and visually checked this was still the case straight after getting the shutdown dialogue).
And 'last x'
Code:
wtmp begins Wed Sep 5 07:44:43 2012
And finally 'last'
Code:
mrt pts/3 :0 Wed Sep 5 09:05 still logged in
mrt pts/2 :0 Wed Sep 5 08:36 still logged in
mrt pts/1 :0 Wed Sep 5 07:48 still logged in
Ok that is it. Like I said though the evidence might not even be in here.
Well I'm going to mark this as solved. I am very embarrassed to have to confess this (but I guess everything is easy if you already know) but after the last time I realised that Ktorrent had just finished downloading. A quick dig soon found an option to shut down the computer after all downloads have completed, oops.
I have confirmed this is the culprit by doing some other quick downloads and the dialogue appears upon completion.
Interestingly enough 'last x' does not show anything even after letting the the shutdown complete. I tried several times but it does not show the culprit.
Code:
$last
mrt pts/3 :0 Wed Sep 5 11:00 still logged in
mrt pts/2 :0 Wed Sep 5 10:51 still logged in
mrt pts/1 :0 Wed Sep 5 10:49 still logged in
mrt pts/0 :0 Wed Sep 5 10:49 still logged in
mrt :0 Wed Sep 5 10:48 still logged in
reboot system boot 2.6.37.6-smp Wed Sep 5 10:48 (00:12)
root tty2 Wed Sep 5 10:34 - 10:35 (00:00)
mrt pts/1 :0 Wed Sep 5 10:20 - 10:46 (00:26)
mrt pts/0 :0 Wed Sep 5 10:20 - 10:46 (00:26)
mrt :0 Wed Sep 5 10:19 - 10:46 (00:27)
reboot system boot 2.6.37.6-smp Wed Sep 5 10:19 (00:27)
(note 'last x' lists nothing, hence the 'last' only command.
Any ideas why ktorrent is not shown as calling shutdown??
Well thanks for all the help and suggestions. Got there in the end.
Thanks again to all, BashTin.
Last edited by BashTin; 09-04-2012 at 10:08 PM.
Reason: typo, can't spell
I'm laughing, but not at you, BashTin; with you is more accurate. I've been here, done this before; as I'm sure most of us have from time to time. It's nothing to be embarrassed about. Operating systems are complicated things. There aren't many around who know everything about them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
