I`m running openSUSE 11.2, with GNOME 2.28 - made a fresh install.
Everything went smooth and nice, and I did not made any changes to my system, when I saw that GNOME System Monitor freezes when clicking on the "System" tab.
Happens on Jessie AMD64 with mate, I can't go to a tty to kill mate system monitor, mouse stop working, keyboard stop working. I tried changing the theme, and now it freeze opening mate system monitor.
I have configured my system to suspend whenever I close the lid, by using the Power Management applet provided by my desktop manager (see my later comment). However, sometimes, when I reopen the lid, I see that the laptop is switched on but it won't resume, while the CPU heats up. I must shutdown forcefully. What could be causing this?
I have found this thread [URL] .... in regard to OpenSUSE. Is it relevant for Debian as well?
System info: - Debian GNU/Linux: 8.1 - Linux Kernel 3.16.0-4-amd64 - MATE desktop 1.8.1 - GNOME Shell 3.14.4
Clarified that the suspend is a user-level setting.
who is having issues with lockups check their /var/log/messages for this
May 28 11:41:21 shayne dbus: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' May 28 11:41:21 shayne dbus: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status' for details. May 28 11:41:21 shayne dbus: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Lubuntu 11.04 on laptop (PIII ATI Rage Mobility). Playing a WMV or MPEG file, system freezes when playback ends. I have not tried any other formats.
I looked at mplayer Preferences
In the Player tab, "Video Output" was blank - I set it to "x11"
This corrected the freeze problem, at least the first time that I tried it. However, it did not seem to persist through multiple plays of the MPEG file, whether or not accompanied by an mplayer quit and rerun or a reboot, even though I did not change the parameters. I tried setting vo=x11 in the etc/mplayer/config file, but that did not help. It is sporadic. It will work a few times with the MPEG file, then hang, for no apparent reason. One thing it does seem to do consistently is hang on the WMV file, regardless of the vo setting, and on both files, when vo is not specified (what I started with). This is a time-consuming task, with a reboot on every failure, and I have run out of ideas on what to try next. When it hangs on the MPEG file I noticed that the elapsed time ends up at 20 sec, even though the video total time is 16 sec. When it doesn't hang, the elpased time goes to 20 sec, then returns to 16 sec.
Last friday I went home from work and just turned off my monitor, as a program I had written needed to run a durability test over the weekend. Unfortunately it seems that the moment I turned off my monitor, Linux just froze, quite evidently as it said this morning that the time was still Friday 17:13.
From the syslog I got the following on that time:
What this means and what I can do? It's not the first time it crashes as soon as I turn my monitor off.
can anyone please tell me which package provides the gnome system monitor applet (the one which can display cpu load and disk I/O in the tray)?I run XFCE on F14/x64 and would like to display it using the XfApplet.
What i've tried already: *) Installed the "GNOME Desktop Environment" --> Nothing changed *) did a yum provides "/usr/lib64/bonobo/servers/*" to check which packages are providing applets - didn't found anything which sounds like the system monitor applet
The XfApplet shows up a bunch of available applets but not the system monitor ...
Since one of the recent updates, I cannot close the System Monitor anymore. Opening it, no problem. All processes are listed just fine and I can force close anything that gives me trouble but... When I want to close System Monitor again, nothing. Qtrl + Q, the X close button at the top right, Alt + F4... all do nothing. And although each time I see some disk activity, there is nothing in the logs.
Another thing I notice is that both dbus-daemon and gnome-system-monitor use about 40% CPU time each, taking the system to 100% CPU usage all the time.Luckily, I have System Monitor open so I can select the process gnome-system-monitor from the list and hit Terminate Process. I did not find anything about it in these forums. Anyone noticed this too or am I the only one?
since a few days (maybe one week and after an automatic upgrade), I could see a strange behavior of gnome-system-monitor. After a boot, everything is normal. But if I log-out, and then log-in again, the problem begins. Impossible to close the gnome-system-monitor window (by clicking on the window upper-right close button). I have to terminate the process. And this process takes about 50% of CPU. In the same time, a dbus-deamon process takes the other 50%. When I terminate gnome-system-monitor process, the CPU use drops down to 6%.
I'm using Ubuntu 10.10 server edition on AMD 64-bit machine. When I try to open system monitor(system->administration->system monitor) it's not starting. Then i use console to open system monitor using command #gnome-system-monitor then it gave me the following error on the console.** (gnome-system-monitor:19279): WARNING **: SELinux was found but is not enabled.
In the gnome-system-monitor, on the "Processes" tab in the "View" menu, I should be able to choose between "Active Processes", "All Processes", and "My Processes". The chooses are all greyed out and I am only able to view "My Processes".I launched the app as root and had the same lack of choice.I also disabled SELinux and rebooted the machine.
9.10 Problem with Graphics/3D and other I have a Thinkpad T42, 1.7GHz, 1Gb Ram and a Radeon 7500 Graphics card. Everything that I am having trouble with works just fine in Ubuntu 9.04(except for the sound). There are two problems that I think are linked or really the same. First off, When I turn off Compiz(Compiz works by default) then gnome-system-monitor does not work properly. At least the graphics side of it; the window appears black with random lines running threw it. The same thing will happen to Gnome-do if Compiz is off.
The second problem is getting 3d support to work. I installed and tried to run blender and I got this from the terminal:
[Code]...
Then it ether does not open or the computer locks up completely and I have to force a shutdown. Which ever one it does I do not get my desired results. When trying to do chess in 3D it tells that I have 'No Python OpenGL support'. So I install the python-opengl package from the repositories; the program now just errors on start and I had to uninstall python-opengl to get Chess to work again. I have tried all this with Compiz on and off with the same results. Anyways thats about it, unless somebody knows how to setup the sound so a program won't lock it from other, then thats all I am having trouble with.
I have updated Opensuse 11.3 to 11.4. I have also updated to the latest NVIDIA drivers. Now, when Gnome desktop starts it freezes: it draws all the shortcuts on the desktop but I cannot use my wired mouse to click anything as if the desktop has freezed. The cursor shows that something is loading. I cannot also use Ctl + F2 to start xterm... But I can use Ctl + Alt + F12, so the keyboard is working.
It should give me daily internet usage stats something/vaguely like this:-I have tried ntop and darkstat ,but they were too complicated and cannot be launched from notification area like this..Also tried using KtrafficAnlyzer by installing KDE core, i am not very amused by the idea of having to install a massive run time file package for a simple tool.
I have OpenSuSe 11.2 64-bit installed on my HP Compaq 6730s laptop. When I'm trying to switch user black screen appears and my system does not react on any key combinations (ctrl+alt+del; ctrl+alt+F7 ...). This was not reproduced before ATI driver installation.
# uname -a Linux xela 2.6.31.5-0.1-desktop #1 SMP PREEMPT 2009-10-26 15:49:03 +0100 x86_64 x86_64 x86_64 GNU/Linux
Cisco vpn client would freeze the system. The only way to recover is to do a hard reset. The funny thing is I had it working before, so it may be random. However, it just happened 3 times in a row and I haven't tried again. I'll try again tonight. I'm pretty sure I'm running the latest client for 64bit linux systems. I'll confirm that when I get a chance, as well as my kernel.
I upgraded my Dell 2.53G machine from 10.3 to 11.2 (KDE desktop). Everything seemed fine for the first day. Then the whole desktop froze. No screen update, no keyboard, and, though you could see the mouse move, clicking didn't do anything. The only way out was to pull the plug.
After multiple attempts at fixing it failed, I repartitioned the disk and tried a "clean install". Everything worked for about 2 hours. The system is currently frozen. The harddrive is quiet. The only "3rd party app" was Adobe Flash, pulled from the Non-OSS repository.
i have running more than 50 servers with openSUSE 11.2 for a long time without any problems. After upgrading 30 server to 11.3 some of them are freeezing after one or two days. I can ping, but i cannot log in. At the console i can type in the user and the nothing happens, system has to reboot.
All servers are Hewlett Packard Proliant G4,G5,G6 with 32bit and 64bit. No errors or hints in the systemlog.
I love opensuse as it's much snappier than MINT. But my system 11.3 is freezing while booting. I pressed ESC during splash and can see messages on the screen. The last message is ATA3 Exception EMASK. I have uploaded the /var/boot.msg here klogd 1.4.1, log source = ksys - Suse Freeze - CuQAd3dg - Pastebin. There are no other log files!
I've installed SLES 11 SP1 as a VM on my Hyper-V/Win2008R2, HP DL380G6 QuadCore, total 18GB RAM, 4GB assigned to the VM. The installation does not include a gui and everything works as expected. The hv-modules are visible but the systems freezes while I - backup the system with Symantec BackupExec 2010/RALUS - run an rsync from my physical P DL360G5 I have to powercyle the VM to reestablish a connection i.e. to CUPS by browser or to open a new session by ssh. Why SLES crashes on hyper-V or what I can do here?
The system frequently freezes the screen. The mouse is still moveable but there is no reaction on any click. Keyboard does not work either (pushing Num-Lock does not toggle the Num-Lock light on the keyboard). However, Alt-Print-b works for a reboot. The only other way out is to turn of the computer.I had this effect some time ago where I thought it was a problem due to the NVIDIA graphics driver. Since then, I changed back to the standard VESA driver and thought the problem would be gone. Just a thought
I toggled through the log files in /var/log which had the file date/time of the crash but I could not find any hint.Which log files could I look as well to dig for the problem? Or any idea for such an effect?
I'd like to solve a little problem that I have connecting my notebook with an external VGA monitor.Everything seems to work fine, but when I close the laptop monitor, also the external monitor shuts down.I've tried to find different energy-saving setting for laptop display and external monitor. with no luck...My video card is an ATI Radeon Xpress 200M. On the ATI website there is no catalist control center for linux. (It would be very useful). So, for now, I can only use the display options on the panel.
i am using DELL XPS STUDIO 1650 with configuration
Processor Intel Core2 Duo Processor P8700 (2.53GHz/ 1066 FSB/ 3MB Cache) Memory 3GB (2 X 2GB) Dual Channel 1066MHz DDR3 SDRAM Hard Drive 320GB 7200RPM SATA Hard Drive Video Card 512MB ATI Mobility Radeon HD 3670 Wireless Network Card Intel WiFi Link 5100 (802.11a/g/n) Half Mini-card
i have installed the new 11.2 OS, every thing went well until i switched on the desktop effect, when i clicked the apply button the whole system freezed, i had to manually switch of the system and re-started. everything went well until the username and password was entered, at the time of the progress bar the system dint respond, but the curser was moving but very slow moment was observed. i tried to repair the system with the repair system option, i tried repairing the file system i got the following error after pressing the help button
"error detected
the Ext4 file system of the partion /dev/sda6 is corrupted. to repair the file system, press repair"
and the second sda7 with the error "the Ext4 file system of the partion /dev/sda6 is corrupted. to repair the file system, press repair"
i pressed the repair button but nothing happen. and i even tried to re install the OS, the same problem exists.
Im running opensuse 11.2 on Linux 2.6.31.5-0.1 64Bit, KDE 4.3.1 with 4GB RAM, Intel duo core processor with Intel graphics card. I initially had opensuse 11.1, which i removed and installed 11.2. Initially everything.Then came the problem, the system starts up fine but then after a few hours freezes, monitor powers off and it wont accept commands from the keyboard or mouse. Meanwhile the lights (caps lock, numeric and scroll) on the keyboard blink. The power light is still on and i can hear the hard disk turning.
I have to forcefully turn the power off and restart but can freeze again after random periods.I do lengthy and demanding computations and its common for the PC to run for weeks without turning it off.
GNOME system monitor is constantly freezing and not responding when i click on first tab 'System' Do somebody knows some workarounds for this issue? It's the same on freshly installed system and also on updated GNOME 2.28 from stable repository.Sometimes on second or third atempt it is working, but i cannot accept such an level of unstability and bugs, discovered on daily basis of testing openSUSE 11.2. There are much more very basic issues in this release which are normal for beta stage, but not for almost 3 moths old system...
I've been using this scanner on various suse builds all the way back to version 8. This week I installed OpenSuse on a brand new computer and when I run xsane, I receive these messages.
[Code]....
The scanner will scan for a few seconds and then the entire system freezes up.