Report a devil in my Ubuntu?

[fatharraxman]

from time to time not always I log in to my Ubuntu, start few works then it auto reboot by itself, why? then every thing go smooth, every thing is working greatly, some days there is nothing like this happen today it happened once, I checked every thing no pitfalls any where? should I report a devil in my system

[labinnsw]

What is the brand of your computer and motherboard?

[nolag]

What apps where you running? What kernel version do you have? How much RAM do you have? How much swap? Please provide more info, it is hard to tell from what you have mentioned.

[mastablasta]

check the capacitors on your motherboard if they are bulged. this kind of issue you describing is usually caused by this or by failing power supply unit.

[fatharraxman]

Sorry
The slow response drew me to track answers from ICR chat but was not persuading to me (a bug?) .
I am using hp mini 110-1100 it is new and worked for three months with windows 7 starter before I erase windows into only Ubuntu desktop Maverik Meerkat 32-bit, it got 1gb RAM, 1.6 GHz, 1.6 GHz atom intel processor 130 free hard-disk, the Ubuntu was well and all basic problems were solved easily, I installed netbook interface and KDE to check sometimes, since 28 Oct, 5 days ago I obseved that when I restart or shut down and open computer again there is no pproblem until I open any application (Evolution,Terminal,any game, any browser, and so any application) the system auto-log out (as if the application I open got a log out button)into username screen, so I choose username and log in and every thing go as normal !!! it only do that once at a session, but a new session will make it (restart or shut down), then gradually it started to be slower on start up, take a longer time at 'hp trade mark screen' where there is no response to any ctrl+alt+fsomething, I counted that to be an increasing time on start up, then it start to third problem after prolonged hibernate : a chaotic screen with black square at the quarter left of the screen , this happened three times and only restart will remove it to repeat the circle, all these problems occurred in a Sequential phenomena that terrified me if continued on who could expect what will happen so on
any help?
please

[labinnsw]

Just to test if the problem is really with the OS. Free up a little space on the hard drive if possible and install something in that space. (Ubuntu, Mint, Fedora, SUSE or any other distro) Test everything over a periiod of time. If you do not encounter any problems, then you can rule out hardware.

The problem sounds to me like it is hardware related, but you are using hardware that I never heard of any problems with.

[fatharraxman]

df -h

Filesystem Size Used Avail Use% Mounted on
/dev/sda1 144G 14G 124G 10% /
none 492M 288K 491M 1% /dev
none 497M 7.6M 490M 2% /dev/shm
none 497M 432K 497M 1% /var/run
none 497M 4.0K 497M 1% /var/lock
/dev/sdb1 1.9G 1.7G 285M 86% /media/F9B9-FF2F
/dev/sdc1 961M 186M 775M 20% /media/Memory card
is his memory not enough or di I misunderstand you sir?

[ldarby]

HP not linux friendly but usually there is a log event that helps identify the problem. With this kind of issue, my approach is to delete all the files in /var/log to get a clean start (sudo rm /var/log/*log* messages ) then reboot (init 6). As soon as it comes up, log in and capture all the logs (cat /var/log/*log* messages >/tmp/all.log)
go through /tmp/all.log file and delete anything that looks OK or not relevant) then investigate whatever remains.
The suspend resume issue might be completely separate from the crashes, but that event will definitely leave records in the logs of what happened. Look closely at the kernel log.
When you do reboot, look closely at screen messages. Latest kernels don't do boot logging as well as in the past so there may be messages here you won't see in the logs.

[fatharraxman]

HP not linux friendly but usually there is a log event that helps identify the problem. With this kind of issue, my approach is to delete all the files in /var/log to get a clean start (sudo rm /var/log/*log* messages ) then reboot (init 6). As soon as it comes up, log in and capture all the logs (cat /var/log/*log* messages >/tmp/all.log)
go through /tmp/all.log file and delete anything that looks OK or not relevant) then investigate whatever remains.
The suspend resume issue might be completely separate from the crashes, but that event will definitely leave records in the logs of what happened. Look closely at the kernel log.
When you do reboot, look closely at screen messages. Latest kernels don't do boot logging as well as in the past so there may be messages here you won't see in the logs.

It is very difficult to me to understand what you are talking about am new in linux and need a step by step instructions please

[ldarby]

understanding what the logs are telling you is an essential skill for working with Linux. Anytime a linux system does something you don't understand or don't want it to the first step to solving this in every case is to look at the logs in /var/log and see if there is a hint as to what went wrong. I gave you some specific commands to run to reduce the amount of messages you have to look at. log in to ubuntu, start a shell applications/accessories/terminal and type in all the commands I gave you ie "sudo rm /var/log/*log* messages". this will produce a temporary combined log file for you to edit. start the editor gedit and open /tmp/all.log. you will see things that the system records in the logs. You have to determine if any of the messages are relevant to the problem you are having.