gnome-system-monitor crashes at startup

Bug #248788 reported by MattNewberry
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-system-monitor (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I get this error when starting up gnome-system-monitor:

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

Fontconfig error: "~/.fonts.conf", line 1: XML declaration not well-formed

** ERROR **: Child 26457 failed with status 256
aborting...
Aborted

I am running Ubuntu 8.04 amd64
gnome-system-monitor:
  Installed: 2.22.1-0ubuntu2
  Candidate: 2.22.1-0ubuntu2
  Version table:
 *** 2.22.1-0ubuntu2 0
        500 http://us.archive.ubuntu.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     2.22.0-1ubuntu3 0
        500 http://us.archive.ubuntu.com hardy/main Packages
     2.8.1-4 0
        500 http://amd64.debian.net sarge/main Packages

Revision history for this message
nine (niin-deactivatedaccount-deactivatedaccount) wrote :

Setting the package to gnome-system-monitor assuming fai was not intended. Please feel free to set it back if it was.

Revision history for this message
MattNewberry (matt-newberry) wrote :

Re-installed SElinux and fixed the SElinux error but still receive an error during gnome-system-monitor startup:

Fontconfig error: "~/.fonts.conf", line 1: XML declaration not well-formed

** ERROR **: Child 6093 failed with status 256
aborting...
Aborted

Have not been able to find a reference to Child 6093 with status 256

Revision history for this message
nine (niin-deactivatedaccount-deactivatedaccount) wrote :

I have the same error messages but I get no crash. So it is possible the error messages are not related to the crash.

Would you please install the apport-gtk package if you have not done so already? Then, if you make the crash happen again, you get a window to automatically create a second bug. It attaches all kinds of extra information about your system. There is more info about it here: https://wiki.ubuntu.com/Apport. The new bug is easier for the developers to see what is wrong.

If you find the new bug number, you can post it here, so we know it is the same thing. Thanks.

Revision history for this message
nine (niin-deactivatedaccount-deactivatedaccount) wrote :

Setting status to incomplete to indicate an apport report is asked for.

Changed in gnome-system-monitor:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gnome-system-monitor:
status: Incomplete → Invalid
Revision history for this message
MattNewberry (matt-newberry) wrote :

Interesting that apport causes a crash as well I will attach the report for both system monitor and apport. The first one is for system monitor.

Revision history for this message
MattNewberry (matt-newberry) wrote :

This is the report for the apport crash.

Revision history for this message
nine (niin-deactivatedaccount-deactivatedaccount) wrote :

Re-opening, as apport itself crashed, so no new bug will be filed automatically. I'm sorry about that. Would you please file a separate bug about apport crashing?

Changed in gnome-system-monitor:
status: Invalid → Incomplete
Revision history for this message
nine (niin-deactivatedaccount-deactivatedaccount) wrote :

@Matt: are you still having the issue? If so: please try double clicking the apport crash for gnome-system-monitor.

Revision history for this message
MattNewberry (matt-newberry) wrote : Re: [Bug 248788] Re: gnome-system-monitor crashes at startup

No the error in no longer occurring.

On Thu, Jul 31, 2008 at 9:28 AM, mouz <email address hidden> wrote:
> @Matt: are you still having the issue? If so: please try double clicking
> the apport crash for gnome-system-monitor.
>
> --
> gnome-system-monitor crashes at startup
> https://bugs.launchpad.net/bugs/248788
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "gnome-system-monitor" source package in Ubuntu: Incomplete
>
> Bug description:
> I get this error when starting up gnome-system-monitor:
>
> ** (gnome-system-monitor:26456): WARNING **: SELinux was found but is not enabled.
>
> Fontconfig error: "~/.fonts.conf", line 1: XML declaration not well-formed
>
> ** ERROR **: Child 26457 failed with status 256
> aborting...
> Aborted
>
> I am running Ubuntu 8.04 amd64
> gnome-system-monitor:
> Installed: 2.22.1-0ubuntu2
> Candidate: 2.22.1-0ubuntu2
> Version table:
> *** 2.22.1-0ubuntu2 0
> 500 http://us.archive.ubuntu.com hardy-updates/main Packages
> 100 /var/lib/dpkg/status
> 2.22.0-1ubuntu3 0
> 500 http://us.archive.ubuntu.com hardy/main Packages
> 2.8.1-4 0
> 500 http://amd64.debian.net sarge/main Packages
>

--
Matt Newberry
----------------------
Climate changes: Let's learn to adapt and understand that Mother
Nature does not need our help.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

closing the bug then, thanks.

Changed in gnome-system-monitor:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.