Find the answer to your Linux question:
Results 1 to 9 of 9
I have installed Ubuntu as wubi (next to windows 7). When I expect the computer to shut down (as part of, you know, shutdown), it doesn't. All the programs end, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jun 2011
    Posts
    16

    Automatic shutdown does not work


    I have installed Ubuntu as wubi (next to windows 7). When I expect the computer to shut down (as part of, you know, shutdown), it doesn't. All the programs end, I am logged out, but I still have a picture on the screen (ubuntu default picture).

    Been using UNIX since 1988, been installing Ubuntu since, well, yesterday.

  2. #2
    Linux Newbie hans51's Avatar
    Join Date
    May 2011
    Posts
    136
    a few situations that caused such in my past months are

    - ANY text editor open with text UNsaved since last change
    - evolution email client currently online to send or receive email
    - some MAJOR system upgrades (as you may have after a new install and then first online update ALL

    a forced CLI halt
    usually forces shutdown even in above cases

    then boot and then after successful login to KDE wait for the system to be fully loaded (until disk activity ends) then do a regular shutdown

    then in all my cases it worked for future shutdowns
    you may also check your system configuration if "your shutdown" is configured to halt incl poweroff or just to logout without poweroff
    these are options to be configured or changed from default if needed

  3. #3
    Just Joined!
    Join Date
    Jun 2011
    Posts
    16
    My situation right now. Been stable for a few days. I choose logout, and then from the screen with the login box choose shut down. Login box and panel disappears, mouse and screen freezes, and 30 seconds later I shut down physically (because the computer didn't do it automatically).

    Been using UNIX since 1988, been installing Ubuntu since, well, yesterday.
    Last edited by anemone42; 07-07-2011 at 01:45 PM.

  4. #4
    Just Joined!
    Join Date
    Dec 2010
    Posts
    7
    I had a problem like this once but it was simply down to the fact WUBI ran within windows, for some reason it hadn't configured correctly on installation. Unfortunately I couldn't get it to work, my alternatives were VMware or Dual Boot - sorry

    When you boot backup are there any logs you can use for investigation - sorry I don't use ubuntu anymore but assume they are in /var/log/ - you probably know a lot more since you've been using unix a while (a lot longer than me)

  5. #5
    Just Joined!
    Join Date
    Jun 2011
    Posts
    16
    Quote Originally Posted by mcclunyboy View Post
    When you boot backup are there any logs you can use for investigation - sorry I don't use ubuntu anymore but assume they are in /var/log/ - you probably know a lot more since you've been using unix a while (a lot longer than me)
    Not sure what to look for, but yeah, there are a few log files. This is what it looks like right now:

    Code:
    -rw-r--r-- 1 root              root     118647 2011-07-13 19:32 dpkg.log
    -rw-r--r-- 1 root              root     356023 2011-07-14 21:43 udev
    -rw-r--r-- 1 root              root       6722 2011-07-14 21:43 boot.log
    -rw-r----- 1 root              adm       68328 2011-07-14 21:43 dmesg
    drwxrwx--T 2 root              gdm        4096 2011-07-14 21:43 gdm
    -rw-r--r-- 1 root              root     106389 2011-07-14 21:44 pm-powersave.log
    -rw-r--r-- 1 root              root      32046 2011-07-14 21:44 Xorg.0.log
    -rw-r----- 1 syslog            adm      444627 2011-07-14 21:47 kern.log
    -rw-r----- 1 syslog            adm      149196 2011-07-14 21:48 syslog.1
    drwxr-xr-x 2 root              lpadmin    4096 2011-07-14 21:51 cups
    -rw-r----- 1 syslog            adm        1470 2011-07-14 22:17 syslog
    -rw-r----- 1 syslog            adm        8014 2011-07-14 22:17 auth.log
    -rw-rw-r-- 1 root              utmp      86016 2011-07-14 22:31 wtmp

  6. #6
    Just Joined!
    Join Date
    Dec 2010
    Posts
    7
    I don't suppose there is anything in any of those logs? You could probably guess as well as i.

    try uninstalling wubi and re-installing as a last resort - i should state I am not incredibly experienced with it so it maybe worthwhile waiting for someone who knows more to answer

  7. #7
    Just Joined!
    Join Date
    Jul 2011
    Posts
    23
    instead of installing as a doble boot, that is what i think you have, try using a virtual machine like virtual box to run a os inside a os and handle it much easyer from there...

  8. #8
    Just Joined!
    Join Date
    Jun 2011
    Posts
    16
    Thank you for your suggestions. Seems like last resort. If somebody can show me, this is the only option?

  9. #9
    Just Joined!
    Join Date
    Jun 2011
    Posts
    16
    Okay, current state of affairs:

    lisea@ubuntu:~$ bin/rtcheck.sh
    -----------------------------------------------
    SUSPEND_MODULES="rt2800pci"
    -----------------------------------------------
    blacklist rt2800pci
    -----------------------------------------------
    parport_pc 32111 0
    rt2860sta 494649 1
    crc_ccitt 12595 1 rt2860sta
    parport 36746 3 parport_pc,ppdev,lp
    -----------------------------------------------
    lisea@ubuntu:~$
    lisea@ubuntu:~$ cat bin/rtcheck.sh
    #/bin/sh

    echo "-----------------------------------------------"
    cat /etc/pm/config.d/config
    echo "-----------------------------------------------"
    tail -n 1 /etc/modprobe.d/blacklist.conf
    echo "-----------------------------------------------"
    lsmod | grep rt
    echo "-----------------------------------------------"
    In part this was achieved through these commands:

    sudo modprobe -rf rt2800pci
    sudo modprobe -rf rt2860sta
    sudo modprobe rt2860sta
    I blacklisted rt2800pci first (meaning it won't be loaded in the future), then removed it right now with the 3 commands above. The computer froze as a result of the last command, but after boot it finally did what it was supposed to do.

    Success! My computer finally understands how a shutdown works!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •