Processes tab causes GLib error

[Frank Quist]

Binary package hint: gnome-system-monitor

This problem occurs often at my computer, but not all the time. I have not been able to find out what triggers this. When the bug is actually there, reproduction steps are:
1. Start Gnome-System-Monitor
2. Switch to Processes tab.

or, when the processes tab is the default tab when starting:
1. Start Gnome-System-Monitor

This causes an immediate crash with:

terminate called after throwing an instance of 'Glib::FileError'
Aborted (core dumped)

Ubuntu version number: 7.10 (gutsy)
Kernel: 2.6.22-14-generic

It might be of note that when starting gnome-system-monitor, the following warning is given:

** (gnome-system-monitor:8255): WARNING **: SELinux was found but is not enabled.

ProblemType: Bug
Architecture: i386
Date: Thu Jan 3 15:11:10 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gnome-system-monitor
NonfreeKernelModules: vmnet vmblock vmmon nvidia
Package: gnome-system-monitor 2.20.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gnome-system-monitor
ProcCwd: /home/frank
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-system-monitor
Uname: Linux Prometheus 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Frank Quist (frankquist)]

I was under the impression that I posted one (second reply, https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/180087/comments/2), but it can very well be that I messed it up, this being my first time reporting a bug. I used the link you gave for instructions when posting my report. If it's incomplete, could you specify what is not right?

[Pedro Villavicencio (pedro)]

Yes, the trace is missing some symbols, may you install the following debugging packages: libstdc++6-dbg, libgtk2.0-0-dbg, libglib2.0-0-dbg and get a new trace? Also a few easy steps for reproduce the crash would be good to have, thanks for the help.

[Frank Quist (frankquist)]

Earlier I did not know what made the difference between gnome-system-monitor crashing or not upon going to the processes tab. It seemed utterly random. Upon further testing I've noticed that it appears that the crash occurs when a terminal window is open (I usually have this open so that might explain why it happens often but not always). There could still be other factors, though. It does not matter whether it's gnome-terminal, xfce4-terminal or kterm (the Hotwire terminal does not cause a crash)

To reproduce, either:
1. Open gnome-system-monitor (terminal is not yet open)
2. Switch to processes tab
3. Open gnome-terminal
Program will immediately crash.

Or:
1. Open gnome-terminal
2. Open gnome-system monitor (terminal is already open)
3. Switch to processes tab
Program will immediately crash.

I hope this is of aid.

I will attach the backtrace after a restart... since it does not seem right now like the packages installed changed anything.

[Frank Quist (frankquist)]

Installing those packages seems only to have aggravated the symbol problem... backtrace attached

[Frank Quist (frankquist)]

I saw that one of the backtraces mentioned icons, so I figured I'd try if this bug was present for some icon sets but not others. Seems like that's the case. I don't know where to start on debugging the icon sets to find out in more detail of this problem, but I can make the steps to reproduce more specific:

1. Switch to one of the following icon themes: Tango, Gartoon, Rodent, Aqua-Glade_PNG, BlankOn, Gorilla or nuoveXT.2.2,
2. Open gnome-system-monitor (terminal is not yet open)
3. Switch to processes tab
4. Open gnome-terminal

Note that none of these is installed on an Ubuntu default install. Tango, Rodent and Gartoon are in Ubuntu's repository and were installed that way. Most probably, the others were downloaded off art.gnome.org, gnome-look.org or a similar site. Tango is: http://art.gnome.org/themes/icon/1150. I assume this problem is somehow related to gnome-system-monitor crashing on some conditions when icons are not found or broke.

Attached is an ls -lR on /usr/share/icons.

[Frank Quist (frankquist)]

Please disregard the Tango link to art.gnome.org I posted. It's an artifact from editing - a part I forgot to correct. Apologies for the noise.

[Pedro Villavicencio (pedro)]

I've followed the steps you said us but it works fine here i don't get a crash. Are you still facing the issue? To be confirmed by someone else. thanks you.

[Frank Quist (frankquist)]

I was still facing this issue, even on Hardy.

It did not occur until I made Hardy use my old home dir, which led me to believe the problem lied in .icons. Which it did. If I removed the Tango dir in frank/.icons it worked again. I have been able to reproduce this for another home user.

Upon investigation it seems as if that Tango dir contained weird icons. It seems to be some problem with links (the file system kind). I am not sure how I would archive this directory in order to have someone else be able to manipulate it, since archiving it would vanquish the links. Any suggestions for how I could help someone else replicate this would be appreciated. Possibly some kind of "ls" output that would allow someone to replicate the links?

This would appear to be some sort of fluke, so not really an important bug (how many people have weird links in their icons directories?) but still, Gnome-System-Monitor or the mechanism that loads these icons should be able to survive in case of issues like this and not break. This is especially the case since apparently even if I use a different theme than that Tango theme (which had the broken icon) the icon would affect it. This suggests other problems. Those icons should not break eachother.

In any case, deleting the icon for my home dir made me at least able to use my system monitor.

[migash.r (migash-r)]

Hi guys,

I get EXACTLY the same error when trying to switch to the processes tab. I think I have found the root of the problem - it seems that when I have Firefox running, the system monitor crashes. However, when it is not running, the system monitor works fine, I can see the processes tab without any problems..

However, when starting from terminal, it still displays the warning "SELinux was found but not enabled."
As for the Firefox, I think the issue might be that lately I have replaced the default system icons with some custom from gnome-look.org, but I didn't like the icon for Firefox. So, I downloaded another custom icon as PNG image and saved it as SVG, and overwritten the original SVG icons for Firefox.

Therefore, I guess this might be causing the problems in my case, looks like the problem is broken icons. I'll try to fix the icons just to be sure.

Anyway, though this looks like a user-caused problem, I think the gnome-system-monitor still might get fixed so that it won't crash when something like this happens, perhaps just don't display any icons..?

[migash.r (migash-r)]

ok, so I have reinstalled the icon theme and gnome-system-monitor does not crash any more when Firefox is running, so I guess this bug report might as well be closed..
invalid icons crash gnome-system-monitor at the processes tab.

[satkata (satkata-deactivatedaccount-deactivatedaccount-deactivatedaccount)]

I am using up-to-date Hardy and gnome-system-monitor crashed after trying to switch in the processes tab from "show my processes" to "show all processes". The app crashed immediately.

now I can not start it anymore it gives me following on the cli:
satkata@satmobile:~$ gnome-system-monitor

** (gnome-system-monitor:7518): WARNING **: SELinux was found but is not enabled.

terminate called after throwing an instance of 'Glib::FileError'
Aborted (core dumped)
satkata@satmobile:~$

[satkata (satkata-deactivatedaccount-deactivatedaccount-deactivatedaccount)]

Yep, Sorry, I hadn't read all the comments. It was one of my icon themes. I switched now to pure tango-icons and everything is working fine, no crashes.

But it shows following on start: (the second warning)

satkata@satmobile:~$ gnome-system-monitor

** (gnome-system-monitor:7591): WARNING **: SELinux was found but is not enabled.

** (gnome-system-monitor:7591): WARNING **: Cannot get volume for mount point '/root/.gvfs'

[Sebastien Bacher (seb128)]

closing since the comment indicate icon theme issues and the software works correctly when using the standard one

[Frank Quist (frankquist)]

I do think it's a bug in the software. It should not crash on an invalid icon. Furthermore, from my testing it was obvious this happened to much more than just one icon theme - there's just lots of improper ones around. A small issue with an icon theme should not crash the entire system monitor. It doesn't crash Nautilus either.

[Sebastien Bacher (seb128)]

could you attach the icon creating the issue? the bug in its current form lacks details to be worked correctly

[BandD (swords-into-plowshares)]

I have this same exact problem with an Icon set I made by combining icons from Crashbit and NouveXT2.2. I had this same icon set working fine under Gutsy.

I too think this is a bug in the gnome-system-monitor. No other programs crash because of icon discrepancies. The program should be worked to ignore or inherit different icons when it encounters something different than it expects. It's going to be very difficult to find the faulty icon, and we shouldn't have to use 'standard' icons just to get the system-monitor to work. If all else fails, maybe the system monitor should just force use the icons from /usr/share/icons/gnome rather than using the user's defined icon set. At least then the program would work.

[BandD (swords-into-plowshares)]

Well I was able to fix the problem AND keep my icon set, though the average user isn't going to want to go through the hassle of this VERY ugly fix.

It seems that the system monitor doesn't like to use .svg images as icons; rather it likes .png images. So to resolve this issue I had to 'hide' my firefox icon originally found in /home/.icons/custom_set/scalable/apps/firefox.svg in a new folder I created within that same director (named whatever you choose, I choose "firefox". Then I tracked down where the default firefox icons were kept, which was in /usr/lib/firefox-3.0b5/icons/. I think the really important one here is mozicon128.png as /usr/share/pixmaps/firefox-3.0 is linked to mozicon128.png. So I opened up Gimp and saved my original firefox.svg icon as a 128px x 128px .png (and as a 16x16 and 48x48, just to be safe as files of these sizes also exist in /usr/lib/firefox-3.0b5/icons/) named mozicon128.png (and mozicon16.png and mozicon50.png) to a convenient folder. Then I replaced the files in /usr/lib/firefox-3.0b5/icons/ with my newly created files--you need root privileges for this. The last thing I had to do was change the path for my firefox panel launcher. For this I choose my original .svg icon in it's newly created folder in /home/.icons.../firefox/.

So now firefox and the system monitor work together in harmony. But it took me an hour of looking for the various icons and testing different situations out. If someone follows my instructions here, then they will probably be ready to go in 15-20 minutes, maybe less. But it is an awful lot of work and if other icons cause similar issues then the whole process will start over again.

So with that said, the System Monitor should be programmed to find more suitable icons if it doesn't like the one that is set as the user's preference. If it comes across a .svg then if should skip it and move on to the next directory until it finds a suitable .png file instead--as the panel, nautilus, and all other programs do. A .svg icon should not keep the system monitor from running. So I agree with Frank.

I've attached the icon causing the issue. The original path was /home/.icons/CURRENT ICON SET/scalable/apps/firefox.png

[Sebastien Bacher (seb128)]

you says that svg icons create the issue but you attached a png one, is that correct?

[BandD (swords-into-plowshares)]

Maybe that it the problem then. I pulled this icon out of an icon set I got from gnome-look.org as is with the .svg tag. But after looking at the file in detail, it is indeed a .png. So perhaps the problem is when a file labeled as .svg is actually a .png. Trying to open the .svg one in image viewer doesn't work. But if I rename it to firefox.png it works fine. So perhaps a mislabled icon is to blame.

[Magnentius (nieuwsgroep222)]

I received this error message " SELinux was found but is not enabled" from gnome-system-monitor too. So I searched for answers and I found via wikipedia this site which states that SELinux is not enabled in Ubuntu 8.04 by default. So the error message in gnome-system-monitor isn't an error message at all. To resolve the problem you'll have to install the SELinux package from synaptic or simply type at the konsole:

sudo apt-get install selinux

I wonder why the hell selinux isn't enabled by default. (see also http://ubuntuforums.org/showthread.php?p=4910260#post4910260)

[Andre5434 (andre5434)]

** (gnome-system-monitor:7591): WARNING **: SELinux was found but is not enabled.

** (gnome-system-monitor:7591): WARNING **: Cannot get volume for mount point '/root/.gvfs'

да, да, истинно так, ежели такое всплывает в терминале то нужно сменить тему значков..... установка SELinux мало что решила

[culmore (culmore)]

https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/180087

Thanks BandD I had the same problem as you and your tips helped me solve my problem. The following two 'icon' files existed:

/usr/share/pixmaps/firefox.png
/usr/share/pixmaps/firefox-3.0.png

The first of these firefox.png was the cause of the problem. When I moved it out of /usr/share/pixmaps the crash in the system monitor stopped happening. I could not view firefox.png with the gimp until i renamed it to firefox.svg. So somehow this 'misnamed icon' file got into my /usr/share/pixmaps directory.

But I don't think the process monitor should crash because a icon has a bad extension.

[eugenia (draeugeniasu)]

NO QUIERO INFORMACION ME CAMBIO DE CORREO

________________________________
De: culmore <email address hidden>
Para: <email address hidden>
Enviado: sábado, 20 de septiembre, 2008 19:35:26
Asunto: [Bug 180087] Re: Processes tab causes GLib error

https://bugs.launchpad.net/ubuntu/+source/gnome-system-
monitor/+bug/180087

Thanks BandD I had the same problem as you and your tips helped me solve
my problem. The following two 'icon' files existed:

/usr/share/pixmaps/firefox.png
/usr/share/pixmaps/firefox-3.0.png

The first of these firefox.png was the cause of the problem. When I
moved it out of /usr/share/pixmaps the crash in the system monitor
stopped happening. I could not view firefox.png with the gimp until i
renamed it to firefox.svg. So somehow this 'misnamed icon' file got into
my /usr/share/pixmaps directory.

But I don't think the process monitor should crash because a icon has a
bad extension.

** Attachment added: "firefox.png"
  http://launchpadlibrarian.net/17785276/firefox.png

--
Processes tab causes GLib error
https://bugs.launchpad.net/bugs/180087
You received this bug notification because you are subscribed to gnome-
system-monitor in ubuntu.

Status in “gnome-system-monitor” source package in Ubuntu: Invalid

Bug description:
Binary package hint: gnome-system-monitor

This problem occurs often at my computer, but not all the time. I have not been able to find out what triggers this. When the bug is actually there, reproduction steps are:
1. Start Gnome-System-Monitor
2. Switch to Processes tab.

or, when the processes tab is the default tab when starting:
1. Start Gnome-System-Monitor

This causes an immediate crash with:

terminate called after throwing an instance of 'Glib::FileError'
Aborted (core dumped)

Ubuntu version number: 7.10 (gutsy)
Kernel: 2.6.22-14-generic

It might be of note that when starting gnome-system-monitor, the following warning is given:

** (gnome-system-monitor:8255): WARNING **: SELinux was found but is not enabled.

ProblemType: Bug
Architecture: i386
Date: Thu Jan  3 15:11:10 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gnome-system-monitor
NonfreeKernelModules: vmnet vmblock vmmon nvidia
Package: gnome-system-monitor 2.20.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gnome-system-monitor
ProcCwd: /home/frank
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-system-monitor
Uname: Linux Prometheus 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux

      ____________________________________________________________________________________
¡Todo sobre Amor y Sexo!
La guía completa para tu vida en Mujer de Hoy.
http://mujerdehoy.telemundo.yahoo.com/