@seth hikari. Thanks. I had do it in new bug 580867.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
The original bug reported is fixed, if you are still having problems you
should file another bug.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
and the dmesg attachment...
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/48461905/dmesg.txt
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
For me shutdown don't works. PC stopped a few seconds then restart. Solutions :
press the powerbutton or press 'c' in the grub menu (grub-pc) and command
'halt'.
No /etc/default/kexec in my /
What stop on runlevel [06] is doing ? Do i try it ?
Uname -a : 2.6.32-22-generic #33-Ubuntu SMP Wed Apr
For me, shutdown works now with the latest Lucid version, on both
platforms (32 and 64 bit). No more problems, as far as I can see.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
For me it was kexec
/etc/default/kexec -> LOAD_KEXEC=false
# Defaults for kexec initscript
# sourced by /etc/init.d/kexec and /etc/init.d/kexec-load
# Load a kexec kernel (true/false)
LOAD_KEXEC=false
# Kernel and initrd image
KERNEL_IMAGE="/vmlinuz"
INITRD="/initrd.img"
# If empty, use curren
In my case, I resolved it that way:
NetworkManager blocked poweroff.
Solution (in my case):
--- /etc/init/network-manager.conf.orig 2010-05-03 14:56:09.745071317 +0200
+++ /etc/init/network-manager.conf 2010-05-03 14:56:43.075152939 +0200
@@ -8,6 +8,7 @@
start on (local-filesystems
On my pc and laptop, selecting shut down, or restart from the menu has
no effect" but this is not something that repeats all the time
The culprit in my case seems to be cause by the OOo quickstarter
every times the problem happens all I have to do is exit the quickstarter and
do the shutdown and
For me the problem still persists, as well. And according to the Ubuntu
home page the installer from the NVidia driver won't work in the current
state of affairs. So I am stuck with the Ubuntu driver for my Geforce
7900GTX. Anything else I can test ...?
--
[lucid] unable to shutdown
https://bugs.
@nano:
i can't. the hardware drivers thingie does not offer any drivers for my
card. i installed the fglrx drivers manually, but they do not seem to
fit to my hardware (ATI Technologies Inc RS690M).
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notifi
@Magnus Kulke
Try to install the proprietary driver for your video card.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
i have this problem on an 'hp compaq 6715s' laptop. the update to
2.6.32-21-generic did not help.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
I think this bug is related to the default video driver. I had the
problem because a bug prevented me have the fglrx proprietary driver.
When I install the fglrx I solved the problem even with the kernel
2.6.32-19. I think it could be an interesting track for this bug.
--
[lucid] unable to shutdo
@Fabio
You are experiencing a different bug that you should report, this bug
would not let you finish shutting down ever from the terminal.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
My Acer 3810T does not shut down/restart/close session from GUI, with kernel
2.6.32-20 (64bit).
In order to switch off the laptop I need to open a terminal and type 'sudo
poweroff'.
I think the problem is related to grants on the user applet...
--
[lucid] unable to shutdown
https://bugs.launc
** Tags added: iso-testing
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/li
Yes! It is here! 2.6.32-20 Fixed this problem, I hope that it does the
same for all of you!
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubu
I think it is confirmed.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
You have done it just fine if you got the Kernel to install I only had
to follow the Ubuntu instructions because of a Kernel Panic at boot.
This confirms the issue is fixed in Upstream, Backport maybe?
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug not
@Seth Hikari, yes.
But I installed the kernel v2.6.34-rc1 from http://kernel.ubuntu.com,
just to test, and the problem disappeared. Tomorrow I'll try to test the
right way to do like you mentioned a few posts behind.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You receiv
@Vanishing I have tested teh 32.19 Kernel and the problem still exists
for me, may be different bug but grats for you
Problem is not in the new R3 kernel either
@Nano , does it hang there until you remove the power?
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You receiv
This was solved for me by upgrading to the newest kernel(32.19).
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
Like this:
init: Disconnected from system bus
init: plymouth post-start process (12485) killed by TERM signal
in Dell Inspiron 1750.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
If some one whom this effects would like to test to see if the problem
exists in Fedora 12( updated so as to have 2.6.32 not 2.6.31 ) and see
if the problem is there as well that would be great, also Fedora alpha
but I am not to sure on the kernel version.
--
[lucid] unable to shutdown
https://bu
Yay a breakthrough! I have finished the upstream testing and confirmed
that this bug is not present in the Linux kernel 2.6.34-rc2.
I hope that a backport of kernel 2.6.33 into Lucid which I believe was
already planed to be an option will fix this issue.
I encourage all who are experiencing this
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (ext
gfx port 0)
00:05.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE
port 1)
00:06.0 PCI bridge: Advanced Micro Devices [AMD] RS7
This time I tried to shutdown the system remotely only by a ssh
connection. The first "shutdown -hP now" brought up the now familiar
screen with
Ubuntu 10.04
. . . .
with those four dots changing their color and closed the ssh connection
but the system hung there, anyway. I had to connect to t
The problem still exists for me. Reboot works, Shutdown ends the GUI,
but the screen with 10.04 and the four dots stay visible forever. I
connected to the box from my laptop via ssh and looked for zombies in
"top" but couldn't find any. So the system was still running and
accessible with ssh. Issui
looks like you were not suffering from the same bug, still have issues
on the latest build that I think may be caused with a problem with
ralink wirless chips. As I get a traceback dealing with RT2600 drivers
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this b
I just tried the 64 version of ubuntu 10.04, both shutdown and reboot works,
but it freezes for 10 secs or so before it really shutdown/reboot..
here is lspci:
vanish...@vanishing:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory
Controller Hub (rev 07)
00:02.0 VGA co
Could everyone this effects please attach output from
lspci
Thanks
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
I have a Acer K70A - powerdown works perfekt in Karmic (and before).
Powerdown in Lucid -> Reboot.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Samething happens to my t500 lucid install, 32 bit..
init errors when shutdown
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
I have 2.6.34-020634rc1-generic kernel and lucid hangs on shutdown
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
I confirm this on my IBM X200.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
this is the same bug as this right? -->
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/418509?comments=all
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
I experience a similar problem an a Lucid system (32 bit) installed with
the Alpha 2 ISO and updated via apt ever since.
sudo reboot now
works, but
sudo shutdown -hP now
only ends the GUI, leaving a completely blank screen.
C+A+D produced a message about alsa-mixer for a split-second, then the
me too, I have Thinkpad T500, I have to hold shutdown button to turn off
laptop
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
OH! I know what this is! maybe... So one time when I noticed that my
computer booted with networking disabled I am able to shut down.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I get periodic partial closing - exits "X" and then hangs on a line
(something like error 15 - I will document next time it happens). No
recourse but to power off manually. This happens on 2 different
machines - and yes I have uninstalled Plymouth.
--
[lucid] unable to shutdown
https://bugs.lau
Now it seems while it is stuck if I press ctr-alt-delete I get alsa-mixer-save
(foo#) caught signal 1
Every time I hit it same thing with different. process ID
That should help
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you ar
@Surbhi Palande
Yes I have just re-upgaded to Lucid again and this bug still persists in the
daily builds.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
On Portégé R600-10Q shutdown freezes with:
init: Disconnected from system bus
init: plymouth post-start process (12485) killed by TERM signal
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Seth Hikari, Thanks for the video and the bug report. Can you please
confirm if this problem persists for the latest Lucid image (i.e daily
build or alpha 2) ?
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubun
@Christopher, your problem seems to be different than this bug. Please
file another bug for your issue.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Same with both computers with Lucid partitions. The desktop has a
GeForce 6400 graphic card and will no longer boot. It hangs; displaying
the desktop after several minutes (previously about 12 seconds) and has
nothing in the panels.
I cannot boot at all on that computer in Recovery mode but can ac
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Yes this is what I see too most of the time. I believe it is the same
bug.
--
[lucid] unable to shutdown
https://bugs.launchpad.net/bugs/498607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
On my laptop (Acer Aspire 5535) the shutdown or reboot say's:
hal main process (683) terminated with status 1
avahi-deamon main process (688) terminated with status 255
modem-manager: caught signal 15, shutting down
init: Disconnected from system bus
After this nothing happens and I must switch t
** Attachment added: "lowed_sucked_failed"
http://launchpadlibrarian.net/36978934/lowed_sucked_failed
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/36978935/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/36978936/AplayDevices
50 matches
Mail list logo
