Tag Info

Hot answers tagged

3

I've interrupted an update (sudo apt-get dist-upgrade or an update during shut-down) multiple times by using Ctrl+C, but I've never tried doing a hard shut-down during an update, so I only see 2 solutions: This is the moment to get your system backup out of the closet and restore your system. I did this just yesterday and doing the restore and re-install ...


3

In command line you can do : sudo shutdown -h 23:30 Your computer will shut down at 23h30. sudo shutdown -P 45 Your computer will shut down in 45 minutes. Graphical tool EasyShutDown let you easily do the same :


1

I couldn't find anything, so I guess the shutdown script was corrupted. To fix it I did the following # which shutdown /sbin/shutdown # dpkg-query -S /sbin/shutdown upstart: /sbin/shutdown # apt-get install --reinstall upstart and now it works again. I guess the next thing is to find out, why those files get corrupted. Thx for the help


1

When your computer is plugged in, it gets its power from the mains. It uses this power to run the computer and to try to charge the battery. When you unplug it, the computer tries to get its operating power from the battery. The immediate Critical Battery Situation message means that, after all the time running on battery (seconds in this case), it has ...


1

I believe the 'ACPI PCC probe failed' is a separate issue from your display brightness. I base this hypothesis on the following: http://permalink.gmane.org/gmane.linux.power-management.general/56400 Similarly: http://comments.gmane.org/gmane.linux.acpi.devel/73411 You have stated you no longer see the 'ACPI' message after you upgraded You still see ...


1

If you have parameters other than "quiet splash" you can leave them in the line e.g. sudo gedit /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1" change to: GRUB_CMDLINE_LINUX_DEFAULT="usbcore.autosuspend=-1" The "usbcore.autosuspend=-1" allows me to place the laptop into suspend and hibernate modes - there ...


1

If you have docky installed this fixed the problem for both of my machines. Ubuntu 15.04 Unity + Docky, Plank, or Cairo-Dock (DOCKY) cd ~/.config/autostart nano docky.desktop add X-GNOME-Autostart-Delay=20 (IF YOU USE CAIRODOCK) cd ~/.config/autostart nano cairo-dock.desktop add X-GNOME-Autostart-Delay=20 Or you can just remove either one from ...


1

If you have docky installed this fixed the problem for both of my machines. Ubuntu 15.04 Unity + Docky, Cairo-Dock, or Plank (DOCKY) cd ~/.config/autostart nano docky.desktop add X-GNOME-Autostart-Delay=20 (IF YOU USE CAIRODOCK) cd ~/.config/autostart nano cairo-dock.desktop add X-GNOME-Autostart-Delay=20 Or you can remove either one from autostart. ...


1

OP has solved the problem: Thanks for replying. I have re-evaluated my strategy a little. I've just put a button in my launcher that runs the second script. This is much simpler and accomplishes the same thing.


1

Alright, so I stumbled upon the answer to my own question quite by accident. I probably should've mentioned this before, but I also tried to find out what keycode and keysym the power key was attached to through xev, but it registered nothing when the key was pressed. Anyhow, I just recently changed over from using the Xmonad window manager to the i3 ...


1

Restart machine In grub menu choose advanced option Select "recovery" item In window menu choose "root" Type: passwd user_name reboot Your grub menu is probably hidden - so you need to use keyboard (ESC) to see it :-) You can also use live-cd distro to do this task. mount your "/" partition (let say: /media/sda1), and use chroot /media/sda1. Then type ...



Only top voted, non community-wiki answers of a minimum length are eligible