Osamu Aoki writes:
> But I want one line solution :-)
>
> sudo sh -c "apt-get update && apt-get upgrade; shutdown -h now"
But there is the case where apt-get want a reply for the user and that
is 'N' :) !! Baka!!! :)
--
/\ ___
Hi,
On Mon, Dec 09, 2013 at 02:38:45PM +0100, Ralf Mardorf wrote:
> One way would be to use a script that runs e.g. apt-get and then the
> shutdown command.
>
> #!/bin/sh
> apt-get update
> apt-get upgrade
> shutdown -h now # or poweroff or halt
> > >> If you wa
an example:
*/$ sudo -i/**/
/**/# apt-get update; apt-get upgrade; shutdown -h now/**/
/*I would try it myself though. Hope this works.
With thanks,
Muntasim-Ul-Haque
Tony van der Hoff writes:
> On 09/12/13 15:16, Lisi Reisz wrote:
> > On Monday 09 December 2013 14:03:57 Muntasim-Ul-Haque wrote:
> >> I'm a Broadband Internet user and I'm billed for the time
> >> my Internet connection is active. Sometimes it happens that I've a
> >> large software to instal
On Monday, December 09, 2013 03:56:12 PM Tony van der Hoff wrote:
> On 09/12/13 15:16, Lisi Reisz wrote:
> > On Monday 09 December 2013 14:03:57 Muntasim-Ul-Haque wrote:
> >> I'm a Broadband Internet user and I'm billed for the time
> >> my Internet connection is active. Sometimes it happens that I
On 09/12/13 15:16, Lisi Reisz wrote:
> On Monday 09 December 2013 14:03:57 Muntasim-Ul-Haque wrote:
>> I'm a Broadband Internet user and I'm billed for the time
>> my Internet connection is active. Sometimes it happens that I've a
>> large software to install like the TeXworks, which is about 650MB
On Monday 09 December 2013 14:03:57 Muntasim-Ul-Haque wrote:
> I'm a Broadband Internet user and I'm billed for the time
> my Internet connection is active. Sometimes it happens that I've a
> large software to install like the TeXworks, which is about 650MB,
> I think. Or, the system up-gradation,
e the
> command and go to sleep. If the command execution completes and the
> Internet is still on, then it would be a waste of my Internet. That's
> why I needed a command that would shutdown the computer after the
> command execution. That's it. And thanks for your co
Muntasim-Ul-Haque writes:
> To Jorgensen: I'm a Broadband Internet user and I'm billed for the time
...
> command and go to sleep. If the command execution completes and the
> Internet is still on, then it would be a waste of my Internet. That's
> why I needed a
, then it would be a waste of my Internet. That's
why I needed a command that would shutdown the computer after the
command execution. That's it. And thanks for your concern.
With thanks,
Muntasim-Ul-Haque
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with
; >> sudo apt-get upgrade; sudo shutdown -h now
> >
> > Wrong, if the upgrade should take to long, then you need to type the
> > password after the upgrade. Better run
> >
> > $ sudo -i
> > # apt-get update ; apt-get upgrade ; shutdown -h now
> &
On 12/09/2013 03:30 PM, Ralf Mardorf wrote:
> On Mon, 2013-12-09 at 14:48 +0200, Lars Noodén wrote:
>> If you want it shut down regardless of the outcome of apt, then this
>> should do it:
>>
>> sudo apt-get upgrade; sudo shutdown -h now
>
> Wrong, if the
On Mon, 2013-12-09 at 14:48 +0200, Lars Noodén wrote:
> If you want it shut down regardless of the outcome of apt, then this
> should do it:
>
> sudo apt-get upgrade; sudo shutdown -h now
Wrong, if the upgrade should take to long, then you need to type the
password after
On Mon, 2013-12-09 at 14:10 +0100, Gian Uberto Lauri wrote:
> If you execute as root (better than using sudo) you can
> either issue from the # prompt
Andrei already pointed out on another thread how to use sudo and I
repeated it for this thread.
You can configure su to have a timeout too, but s
On Mon, 2013-12-09 at 14:16 +0100, Ralf Mardorf wrote:
> On Mon, 2013-12-09 at 13:11 +, Karl E. Jorgensen wrote:
> > Hi
> >
> > On Mon, Dec 09, 2013 at 05:42:17PM +0600, Muntasim-Ul-Haque wrote:
> > > Hi,
> > > I need a tool that would make sure that, my
On Mon, 2013-12-09 at 13:11 +, Karl E. Jorgensen wrote:
> Hi
>
> On Mon, Dec 09, 2013 at 05:42:17PM +0600, Muntasim-Ul-Haque wrote:
> > Hi,
> > I need a tool that would make sure that, my computer would shutdown after a
> > specific command has been executed. This t
Hi
On Mon, Dec 09, 2013 at 05:42:17PM +0600, Muntasim-Ul-Haque wrote:
> Hi,
> I need a tool that would make sure that, my computer would shutdown after a
> specific command has been executed. This tool would just wait for the Terminal
> for executing a command, like 'sudo apt
On Mon, 2013-12-09 at 13:02 +, Philip Ashmore wrote:
> but I think sudo has a timeout
sudo -i and then run a script, if you not explicitly configured it to
have a timeout it has got no timeout.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe
Muntasim-Ul-Haque writes:
> Hi,
> I need a tool that would make sure that, my computer would shutdown
> after a specific command has been executed. This tool would just wait
> for the Terminal for executing a command, like '/sudo apt-get upgrade/'
> and then a
On 09/12/13 11:42, Muntasim-Ul-Haque wrote:
> Hi,
> I need a tool that would make sure that, my computer would shutdown
> after a specific command has been executed. This tool would just wait
> for the Terminal for executing a command, like '/sudo apt-get upgrade/'
> and t
On Mon, 2013-12-09 at 17:42 +0600, Muntasim-Ul-Haque wrote:
> Hi,
> I need a tool that would make sure that, my computer would shutdown
> after a specific command has been executed. This tool would just wait
> for the Terminal for executing a command, like 'sudo apt-get upgrade&
On 12/09/2013 01:42 PM, Muntasim-Ul-Haque wrote:
> Hi,
> I need a tool that would make sure that, my computer would shutdown
> after a specific command has been executed. This tool would just wait
> for the Terminal for executing a command, like '/sudo apt-get upgrade/'
Hi,
I need a tool that would make sure that, my computer would shutdown
after a specific command has been executed. This tool would just wait
for the Terminal for executing a command, like '/sudo apt-get upgrade/'
and then after the command has been executed, my computer would
sh
On Mon, 04 Nov 2013 11:27:32 +0100
berenger.mo...@neutralite.org wrote:
> Hi.
>
> I have what seems an automated spam when I send a mail to the ml.
>
> It takes back the subject but adds it "Festival Shutdown : ". Am I the
> only one with this issue, please?
>
You are not the only one with this problem. If it frustrates
you, please bring it to the listmasters attention.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2013110
On Mon, Nov 04, 2013 at 11:27:32AM CET, berenger.mo...@neutralite.org said:
> Hi.
>
> I have what seems an automated spam when I send a mail to the ml.
>
> It takes back the subject but adds it "Festival Shutdown : ". Am I
> the only one with this issue, please?
>
Hi.
I have what seems an automated spam when I send a mail to the ml.
It takes back the subject but adds it "Festival Shutdown : ". Am I the
only one with this issue, please?
Here is the exact content of that spam:
Original Message
Subject: Festival Shutdown
xerxes kernel: [359196.088138]
Jun 25 06:55:05 xerxes logger: PWRWATCH sent array to standby
Jun 25 06:58:08 xerxes shutdown[14745]: shutting down for system halt
Jun 25 06:58:12 xerxes kernel: [359595.057889] xfce4-settings-[5152] general
protection ip:7f92494f7834 sp:7fff1acb40a0 error:0 in
one user (the other user are unaffected) there is no
more a command to restart or shutdown the computer in the user menu in
Gnome (I mean the one in the top-right corner).
Press Alt and click your username.
From some days the menu ends with the line suspend, while in the past
(and still for the
it is a little strange that the
> menu changed (the only thing I remember I have done was to use the suspend
> function, while I usually use the shutdown).
>
> I have struggled to look in the gnome options, but with no luck. And now I
> can understand the reason: it is an extens
ser are unaffected) there is no
> >> more a command to restart or shutdown the computer in the user menu in
> >> Gnome (I mean the one in the top-right corner).
> >
> > Press Alt and click your username.
> >
> >> > From some days the menu ends with
had never realized that what I see was not the normal plain
gnome.
I am pretty sure I have not turned it off, so it is a little strange that the
menu changed (the only thing I remember I have done was to use the suspend
function, while I usually use the shutdown).
I have struggled to look in t
On Saturday 08 June 2013 03:04 PM, Antti Talsta wrote:
On Sat, Jun 08, 2013 at 05:07:00AM -0400, A Fascilla wrote:
On my system on one user (the other user are unaffected) there is no
more a command to restart or shutdown the computer in the user menu in
Gnome (I mean the one in the top-right
On Sat, Jun 08, 2013 at 05:07:00AM -0400, A Fascilla wrote:
> On my system on one user (the other user are unaffected) there is no
> more a command to restart or shutdown the computer in the user menu in
> Gnome (I mean the one in the top-right corner).
Press Alt and click your username.
Hello
I am experiencing a strange effect since a few days and I could not found a
solution.
On my system on one user (the other user are unaffected) there is no more a
command to restart or shutdown the computer in the user menu in Gnome (I mean
the one in the top-right corner).
>From s
Using a loginmanager did the trick. Thanks!
But why? With startx the Desktop Environement should get the permissions
the user has on commandline, shouldn't it?
Best Regards
A. Maisch
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Cont
On Sun 31 Mar 2013 at 20:23:39 +0200, Armin Maisch wrote:
> When I want to log off from Xfce by using the xfce-dialog I find three
> buttons there: logoff (which is working as it should, reboot, which is
> just grey and unclickable and the shutdown-one, which is also grey and
>
On Sun, Mar 31, 2013 at 6:17 PM, Michael Biebl wrote:
>
> I would guess your session is not marked as active
> ck-list-sessions will tell you that.
>
> That is a problem of starting your X session via startx.
>
> My suggestion would be to use a display manager like gdm3 or lightdm.
Using a DM pro
I would guess your session is not marked as active
ck-list-sessions will tell you that.
That is a problem of starting your X session via startx.
My suggestion would be to use a display manager like gdm3 or lightdm.
Michael
--
Why is it that all of the instruments seeking intelligent life in th
nclickable and the shutdown-one, which is also grey and
unclickable.
Another interesting Point is that running "systemctl poweroff" after
logging off from Xfce as a normal user is shutting of the system as it
should do without any questions, but running it in a terminal window in
the started xf
Hi,
>> Ouch! Have you ruled out hardware? Have you tried booting from a
>> live-cd, knoppix, grml, something like that?
>
> Actually no, I have not ruled out hardware failure. In fact there are other
> unusual problems
> which may indicate a hardware failure. I did run the smartctl long self
On 2013-02-21 09:19, Chris Bannister wrote:
> Ouch! Have you ruled out hardware? Have you tried booting from a
> live-cd, knoppix, grml, something like that?
Actually no, I have not ruled out hardware failure. In fact there are
other unusual problems which may indicate a hardware failure. I did
complete boot. It takes on
> average 3.5 such restarts each time I start the machine for a boot
> to be finally successful.
>
> Furthermore, ever since I converted this machine on 2013-02-18
> Monday to dependency based booting, the shutdown process no longer
> is completed. It goes
be finally
successful.
Furthermore, ever since I converted this machine on 2013-02-18 Monday to
dependency based booting, the shutdown process no longer is completed.
It goes to run level 0, closes a number of processes, returns the line :
“INIT: no more processes left in this runlevel” and
I'd try adding
"""
ALL ALL=(root) NOPASSWD: /usr/sbin/xfsm-shutdown-helper
"""
to /etc/sudoers. I vaguely remember having a similar problem on a box
that had lived from sarge to squeeze and adding that line solved it.
However, another machine with a fresh in
On Thu 22 Nov 2012 at 23:18:21 +0100, Hartwig Atrops wrote:
> Any idea? XFCE configuration or window manager? I use XDM on this machine.
> The
> Sun with Squeeze is running KDM.
XDM does not co-operate with consolekit.
Search the list archives at
http://lists.debian.org/
using 'xdm', 'xfc
On Monday 19 November 2012 23:52:13 Go Linux wrote:
> --- On Mon, 11/19/12, Hartwig Atrops wrote:
> > From: Hartwig Atrops
> > Subject: Re: Wheezy, XFCE: system shutdown
> > To: debian-user@lists.debian.org
> > Date: Monday, November 19, 2012, 3:03 PM
> > On
On Mon 19 Nov 2012 at 17:12:53 +0100, Hartwig Atrops wrote:
> I have a configuration problem with Wheezy and XFCE and didn't find the
> appropriate docu:
>
> The Log-Out-Dialog (from the upper panel) offers "Log Out", "Restart"
> and "Shut Down" icons. But only "Log Out" is usable, the other tw
--- On Mon, 11/19/12, Hartwig Atrops wrote:
> From: Hartwig Atrops
> Subject: Re: Wheezy, XFCE: system shutdown
> To: debian-user@lists.debian.org
> Date: Monday, November 19, 2012, 3:03 PM
> On Monday 19 November 2012 20:05:15
> Go Linux wrote:
> > --- On Mon, 11/19/12
On Monday 19 November 2012 20:05:15 Go Linux wrote:
> --- On Mon, 11/19/12, Nate Bargmann wrote:
> > From: Nate Bargmann
> > Subject: Re: Wheezy, XFCE: system shutdown
> > To: debian-user@lists.debian.org
> > Date: Monday, November 19, 2012, 12:51 PM
> > * On
--- On Mon, 11/19/12, Nate Bargmann wrote:
> From: Nate Bargmann
> Subject: Re: Wheezy, XFCE: system shutdown
> To: debian-user@lists.debian.org
> Date: Monday, November 19, 2012, 12:51 PM
> * On 2012 19 Nov 12:46 -0600, Hartwig
> Atrops wrote:
>
> > xfce4-powe
* On 2012 19 Nov 12:46 -0600, Hartwig Atrops wrote:
> xfce4-power-mangager was missing, but installing it did not solve the problem.
>
> group settings: there is no group named *power* or similar. What would be the
> rigth group configuration?
My user is in the powerdev group. I get even the
t;Shut Down" icons. But only "Log Out" is usable, the
> > other two are
> > disabled.
> >
> > How can I enable the Shutdown button? Log out and login as
> > root again only for
> > shutdown - hmm, it works, but ...
>
> Did you check your group settin
--- On Mon, 11/19/12, Hartwig Atrops wrote:
> From: Hartwig Atrops
> Subject: Wheezy, XFCE: system shutdown
> To: debian-user@lists.debian.org
> Date: Monday, November 19, 2012, 10:12 AM
> Hi.
>
> I have a configuration problem with Wheezy and XFCE and
> didn't
Hi.
I have a configuration problem with Wheezy and XFCE and didn't find the
appropriate docu:
The Log-Out-Dialog (from the upper panel) offers "Log Out", "Restart"
and "Shut Down" icons. But only "Log Out" is usable, the other two are
disabled.
On Mon 08 Oct 2012 at 10:27:05 -0400, Stephen P. Molnar wrote:
> Debian 6.0.6 (64 bit)/KDE 4.4.5
>
> For some reason when I shutdown the system, either as a user or as
> root, the process hangs on:
>
> Currently running process (pstree):
>
> The only recourse I seem to
Debian 6.0.6 (64 bit)/KDE 4.4.5
For some reason when I shutdown the system, either as a user or as root,
the process hangs on:
Currently running process (pstree):
The only recourse I seem to have is to hit the reset button.
Reinstalling psmisc did not solve the problem.
Assistance in
On Thu, Sep 27, 2012 at 5:44 AM, Stan Hoeppner wrote:
> On 9/26/2012 11:14 AM, Artifex Maximus wrote:
>> On Sun, Sep 23, 2012 at 9:55 AM, Selim T. Erdogan
>> wrote:
>>> Artifex Maximus, 18.09.2012:
>>> Did you make any software updates to the system? I have a pretty old
>>> computer that is usin
I've changed my processor from E5200 to E8400. Since then my computer
>>>>> does not shutdown.
>>>>
>>>> It's possible that you damaged your board in the process.
>>>
>>> Thanks for your answer. I did it several times and otherwise works
On Sun, Sep 23, 2012 at 9:55 AM, Selim T. Erdogan
wrote:
> Artifex Maximus, 18.09.2012:
>> On Mon, Sep 17, 2012 at 8:29 PM, lee wrote:
>> > Artifex Maximus writes:
>> >
>> >> I've changed my processor from E5200 to E8400. Since then my computer
>
Have you found the problem yet?
On Thu, Sep 20, 2012 at 01:21:33PM -0700, Mike McClain wrote:
> Howdy,
>
> I'm on dialup using pppd and loosing the connection often in the
> middle of fetching mail or loading some URL in the browser. I'm hoping
> for suggestions to help me debug the problem.
Artifex Maximus, 18.09.2012:
> On Mon, Sep 17, 2012 at 8:29 PM, lee wrote:
> > Artifex Maximus writes:
> >
> >> I've changed my processor from E5200 to E8400. Since then my computer
> >> does not shutdown.
> >
> > It's possible that you
On Fri, 21 Sep 2012 12:40:20 -0700, Mike McClain wrote:
> On Fri, Sep 21, 2012 at 02:53:52PM +, Camale?n wrote:
>> You can try by adding/enabling "crtscts" and also the "modem" options
>> at the config file. depending on the hardware you're using, these were
>> to alleviate the kind of errors
On Fri, Sep 21, 2012 at 02:53:52PM +, Camale?n wrote:
> You can try by adding/enabling "crtscts" and also the "modem" options at the
> config file. depending on the hardware you're using, these were to alleviate
> the kind of errors you get although OTOH, dialup links are very unreliable,
> it
eliable,
it's quite usual to get random disconnects.
> I can see that sometimes my ISP seems to go to sleep but other
> times it appears to be some other problem and I just don't know how to
> gather the data to make an informed diagnosis.
>
> Any suggestions on h
to sleep but other
times it appears to be some other problem and I just don't know how to
gather the data to make an informed diagnosis.
Any suggestions on how to track pppd's shutdown with greater
resolution will be appreciated.
Thanks;
Mike
--
Satisfied user of Linux since 1997.
ns
which are not available when sold as stand-alone (separate) items.
> I still have no idea why system cannot shutdown with different CPU.
It does not have to be related but in your case it quite evident there's
a straight cause-effect relation. Given that shutting down problems are
On Mon, Sep 17, 2012 at 8:29 PM, lee wrote:
> Artifex Maximus writes:
>
>> I've changed my processor from E5200 to E8400. Since then my computer
>> does not shutdown.
>
> It's possible that you damaged your board in the process.
Thanks for your answer. I did it
On Mon, Sep 17, 2012 at 4:36 PM, Camaleón wrote:
> On Mon, 17 Sep 2012 11:48:53 +0200, Artifex Maximus wrote:
>
>> I've changed my processor from E5200 to E8400. Since then my computer
>> does not shutdown. Sometimes the display and motherboard LEDs become
>> blank b
Artifex Maximus writes:
> I've changed my processor from E5200 to E8400. Since then my computer
> does not shutdown.
It's possible that you damaged your board in the process.
> Sometimes the display and motherboard LEDs become blank but PSU cooler
> runs.
It's a fe
On Mon, 17 Sep 2012 11:48:53 +0200, Artifex Maximus wrote:
> I've changed my processor from E5200 to E8400. Since then my computer
> does not shutdown. Sometimes the display and motherboard LEDs become
> blank but PSU cooler runs. Sometimes Debian stops at System halted line
> an
Hello!
I've changed my processor from E5200 to E8400. Since then my computer
does not shutdown. Sometimes the display and motherboard LEDs become
blank but PSU cooler runs. Sometimes Debian stops at System halted
line and no blank screen and machine keeps running. I think that only
CPU c
ay system beeps - especially the one when the greeter is ready
/desktop/gnome/sound/event_sounds false
--- On Tue, 7/17/12, green wrote:
> From: green
> Subject: Re: Annoying Shutdown Beep
> To: debian-user@lists.debian.org
> Date: Tuesday, July 17, 2012, 2:31 PM
> Andrejs
Andrejs Igumenovs wrote at 2012-07-17 14:03 -0500:
> Please help anyone to disable the silly shutdown beep !
You could try creating file /etc/modprobe.d/local.conf with contents:
blacklist pcspkr
signature.asc
Description: Digital signature
Please help anyone to disable the silly shutdown beep !
Tried several options, didn't help. Also disabling the speaker via the BIOS is
not an option for me.
- Andrejs
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
On 16 July 2012 01:34, DJ Amireh wrote:
> I am having trouble with power management on my laptop. I cannot get suspend
> or shutdown to work, attempting either causes my laptop to have a black
> screen and not respond to any input and I am forced to manually shutdown by
> holding the
I am having trouble with power management on my laptop. I cannot get
suspend or shutdown to work, attempting either causes my laptop to have a
black screen and not respond to any input and I am forced to manually
shutdown by holding the power button. I am running Debian Squeeze with KDE.
Shutting
As of late, on my Debian Sid box, every bootup shows "recovering journal" on
all my ext3 filesystems. There ia often a bunch of orphaned inodes on the
/usr!
It is as if I hit the switch instead of an orderly halt shutdown.
System otherwise is OK.
Bug? Which package? Workaround (tri
On Mon, 2012-04-23 at 20:43 +, Camaleón wrote:
[...]
>
> Mmm... what worries me is why an fsck is even needed just because a non-
> vital application is not being closed gracefully on shutdown, that's not
> something I would consider worth for a fsck >:-?
>
> Ste
p it. It's just a bit too big to add to my
> current backup system.
Okay then :-)
>> > Is is perhaps possible that Gnome is writing out some config files in
>> > my home directory during shutdown and the system cuts power
>> > prematurely? I also noticed a
On Mon, 2012-04-23 at 12:07 -0700, Kelly Clowers wrote:
[...]
>
> Is it possible to shutdown vuze gracefully instead of killing java out
> from under it?
I couldn't find anything back when I wrote the script besides killing
java. But I just did another search and came up with &qu
y
> killall java
> sudo /sbin/shutdown -h +2
>
> vlc is started full screen with playlist file "play", the last item in
> the playlist tells vlc to exit. Then "killall java" is executed to tell
> vuze to terminate (failing to do so results in vuze complaining abo
t difference can be in shutting down from GNOME and doing
> >> it from the command line, mmm... >:-?
> >>
> >>
> > Is is perhaps possible that Gnome is writing out some config files in my
> > home directory during shutdown and the system cuts power prematur
ny difficulty.
>> I wonder what difference can be in shutting down from GNOME and doing
>> it from the command line, mmm... >:-?
>>
>>
> Is is perhaps possible that Gnome is writing out some config files in my
> home directory during shutdown and the system cuts power
On Thu, 2012-04-19 at 17:31 +, Camaleón wrote:
> On Wed, 18 Apr 2012 21:19:09 +0200, Steven Post wrote:
>
> > I have this really annoying problem when I shutdown the machine using
> > sudo /sbin/shutdown -h +1
> > The machine seems to properly shutdown, but I always (a
On Wed, 18 Apr 2012 21:19:09 +0200, Steven Post wrote:
> I have this really annoying problem when I shutdown the machine using
> sudo /sbin/shutdown -h +1
> The machine seems to properly shutdown, but I always (at least I think)
> get the message that a filesystem contains errors and
Le 4/19/12 2:35 PM, Olivier Sallou a écrit :
> Hi,
> I have a Debian (testing) virtual image above KVM, but I can't get the
> shutdown event work.
>
> I installed in my virtual image acpi-support (and acpi) packages to get
> acpi support and I tried to load the button ker
Hi,
I have a Debian (testing) virtual image above KVM, but I can't get the
shutdown event work.
I installed in my virtual image acpi-support (and acpi) packages to get
acpi support and I tried to load the button kernel module (as it seems
shutdown event maps to button event).
However, lo
Hi list,
I have this really annoying problem when I shutdown the machine using
sudo /sbin/shutdown -h +1
The machine seems to properly shutdown, but I always (at least I think)
get the message that a filesystem contains errors and needs to be
checked. When I use the shutdown option in Gnome, the
nually (by e-mail), you can choose what's best way for you:
http://www.debian.org/Bugs/Reporting.en.html
> I don't know in which package this bug is. (I never reported any Debian
> bugs before)
As the problem it presents when you're inside X (you can shutdown the
system on a tt
On Mon, 2012-03-19 at 11:20 +, Camaleón wrote:
> On Sun, 18 Mar 2012 21:44:35 +0100, Peter Baranyi wrote:
> If it used to work, I would report it.
>
you mean with the reportbug program? I don't know in which package this
bug is. (I never reported any Debian bugs before)
> > Debian unstable,
On Sun, 18 Mar 2012 21:44:35 +0100, Peter Baranyi wrote:
> I can only shut down my pc from a root terminal with 'poweroff' (or
> shutdown) but not from graphical environments.
>
> From Gnome2, sometimes it shuts down, sometimes I get back to gdm. From
> gdm, the shutdo
Hi,
I can only shut down my pc from a root terminal with 'poweroff' (or
shutdown) but not from graphical environments.
>From Gnome2, sometimes it shuts down, sometimes I get back to gdm. From
gdm, the shutdown action sometimes works, sometimes it just quits gdm.
In KDE 4.7.4, sh
On 2012-01-03, Bob Proulx wrote:
>
>> Now you say rebooting requires and entails the exact same electrical
>> event as a poweroff? I don't quite understand. You mean that reboot
>> powers off the machine, and then turns it back on again immediately,
>> whereas a
nderstand. You mean that reboot
> powers off the machine, and then turns it back on again immediately,
> whereas a shutdown/poweroff simply powers the machine off?
Isn't that the way that it works? I always thought that it did. All
of the behavior indicates to me that it does. But
ine, and then turns it back on again immediately,
whereas a shutdown/poweroff simply powers the machine off?
I'm talking soft reboot here, "shutdown -r now".
You must surely be talking hard reboot? I turn off my machine once a day, at
night. There have been no problems tur
Curt wrote:
> Bob Proulx wrote:
> > Just two months ago I had this exact same problem with a brand new
> > Intel motherboard. Searching the motherboard site for BIOS upgrades I
> > found that there was one available and in my case the changelog for it
> > listed reboot problems as one of the fixes
ne of the fixes. I upgraded the BIOS and
> my problem was resolved.
Reboot problems? I don't have any of those; sometimes when shutting down
the machine it will not power off.
I'm talking uniquely and exclusively about the electrical acpi event
that occurs after the shutdown procedure
Curt wrote:
> Periodically, for no reason I can fathom, or trace to a specific cause,
> when I shutdown my machine, it fails to power off. The shutdown
> procedure unrolls, or unfurls, as expected, but at the point where it
> says at the console "Will now halt," instead
uts down properly but periodically fails to power off.
> If its a nvidia or ati card you could have the dreaded issues of
> xorg-server not playing nicely. I just recently had to pin xorg-server
> in sid to be able to cleanly shutdown and reboot again. There are a
> bunch of bugs open in r
401 - 500 of 1694 matches
Mail list logo
