I have Mythbuntu 10.04 installed on an exclusive HTPC and working great... until tonight. After letting the system update some packages (161 packages if I remember right), I suddenly have an issue where the graphical system won't start. After researching I found three error messages that might be causing that.
1. At the start of splash screen I see "UUID=xxxxxxxCD7 not ready yet or not present" I checked in /etc/fstab and found that this is the swap partition. I don't remember seeing this before so this could be the culprit.
2. I'm not at the computer in question right now but I saw a Plymouth error about "mountall" and then the message "plymouth command failed". Not sure if this could be the main error.
3. after a while (usually ca. 1-2 min) I receive thousands of errors of the kind "out of memory"... "kill process XXXX" (process vary wildly e.g. dbus-daemon, mysql, etc)... "process killed"..."respawning"
After error 3, I'm not able to switch to graphical console (ctrl-alt-F7). If I was in the graphical console at this moment, I simply can't switch to the CLI console. I'm always afraid of updating my system since I've seen lots of things breaking afterwards (usually the proprietary graphic drivers) but this is really strange.
Someone explain this to me. I often thought in the back of my head, how do I check if my drive is bad in Linux? I always excused it thinking well I guess besides gaming that's another reason to keep a windows partition around. I boot up yesterday and Gnome was acting weird. Then, it happened. "We have detected bad sectors in your hard drive." I thought, no, you're stupid, this hard drive is less than a year old (however it was a replacement for another one that died). So I reboot.
Boot back up - Different error message. But instead of getting it a few minutes after log in, I got it right away. "We have detected potential hard drive failure." Okay, Linux. Want to play this game? Booted to Vista, downloaded Seatools to test my Seagate drive. It failed... Swapped SATA cables... it failed... So I ask - how does Linux have this auto detect capability like that? As much as I love Ubuntu, I was like there's no way it could just magically tell like that without running the Seagate program. But alas, Ubuntu was dead on target.
Created application is working too slow, looks like there are a lot of memory leaks, there are a lot of pointers. Any effective tool for run-time errors and memory leaks detection in Visual Studio C++?
Is there a system admin tool for RHEL on montioring and logging system memory used and released that can dump to a log file?I'm having an issue with memory not being released when an application is closed. I need to have a tool monitor and log so I can troubleshoot to verify that it's an application not the OS.
Programs like aMSN, and controlling music volume, etc are gone in the upper-taskbar/panel. I think I accidentally managed to delete the whole upper panel, and created a new one. Still the programs I start up which suppose to appear in the upper panel, don't appear there. Any idea how to fix this, or to add those functions to the upper panel?
I have looked through many different forums and ..... tutorials on how to get Samba to work. I am new to Ubuntu (Linux in general). I am able to access my shared folders on my Windows 7 system with my Ubuntu system. I cannot access the shared files on my Ubuntu though on my Windows 7.
We just got a new rack server in at work, and it won't automatically detect the NIC Cards on the system, I can't seem to find any drivers on the internet for them as well. Would anyone know if they are avaliable?
I get this error when I run gedit as root in terminal. GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See GConf configuration system for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
So I looked around and found something about running a system check. Well I really couldn't find to much but I did find the command fsck and running it with the -n option this is what I got.
As you can see I have some orphaned inodes and these are probley from a Yast2 crashing a couple of times on me getting lockup because a repo was down or not responding.
I have two graphics cards in my computer. One is a crappy built-in nVidia GeForce 6150 SE, and the other is a high-end (as of 2008) GeForce in the 8000 range. I would like to use the latter, but I can't get anything to detect it. Testing which is in operation is easy: they have separate video outputs. I've tried changing the BIOS settings, but to no avail. I'm stumped. Could it be that my other card is dead? How could I test it? I'm fairly certain that it worked back when I used Windows, as I remember having to use my DVI-to-VGA converter (the other card's outputs are all DVI).
I need to write a small application which needs to detect if the system time is changed by an another application/user and perform some action as soon as it is detected (maybe log the data that time has changed, along with info about which application/user changed it).
How can this be achieved?
I have good programming experiences in shell script, c and beginner level in python. I don't need to know when it was changed, just need to know who/what changed it. The system uses NTP to sync the time, but it is also possible for anyone/any application to change the time(for eg: using the simple "date" command as well).
I've been trying to revive my old Acer Aspire 3680, which is supposed to have Acer InviLink 802.11b/g Wi-Fi CERTIFIED solution, supporting Acer SignalUp wireless technology, as shown is in Specification.The system simply doesn't detect Wi-fi and I don't know how to make it work.
I run a Centos server that quite a few people have access to. I trust every user on the system, but i've had problems before like one user's account gets hacked and someone starts using my box to DDOS. Each user has their own ip.. And I would like to write a script or use an existing solution (if one exists) to monitor number of tcp/udp connections each minute and see if it's unusually high. I don't want it to stop the flooding or anything, I just want to be notified by email or something.
Whenever someone copies a data Our system get very slow. Load average of system starts increasing. How would i find which process is causing the same. I have tried following top 10 CPU utilizing process command but it didn't help much.
ps -auxf | sort -nr -k 3 | head -10
My distribution detail.
# lsb_release -a LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch Distributor ID: EnterpriseEnterpriseServer
I've just installed 10.4 and it works like a charm. The only problem I have is that I've plugged my ipod touch 3g in and nothing happens. It seems like the system doesn't detect it. Opening rhythmbox nothing happens either.
Do i need to do any extra thing in order to have my ipod working?
The only thing I can see in the syslog is this message:
I'm new to linux and having a lot of problem, and I would really apprecaite the help. It all started when I connected my laptop to an LCD. Since then, my system doesn't detect its own screen. So I have to escape as the start of reboot and go to a recovery mode and select failsafe screen. Ubuntu then set to lowest graphic mode. It's no way to keep a set up for the long run. I've tried to reinstall Ubuntu from a CD but that doesn't work. .
I just installed Fedora 13 onto a "new" (to me) box, and everything seems mostly fine, except that I only seem to be able to use about 900.2 MiB of 991.4 MiB of RAM memory, according to System Monitor. I haven't set up a swap partition yet, so the problem became very, very, very obvious. When I get to about 890 MiB usage, everything goes very quickly downhill, locking up, etc. The peak I saw was 900.2 MiB. What's going on? Does this have anything to do with the system being 64-bit? Might the memory be bad?