Bug 888696 - [abrt] mate-system-monitor-1.5.0-2.fc18: g_settings_schema_get_value: Process /usr/bin/mate-system-monitor was killed by signal 5 (SIGTRAP)
Summary: [abrt] mate-system-monitor-1.5.0-2.fc18: g_settings_schema_get_value: Process...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mate-system-monitor
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Mashal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f7537fb2ac559cce49a97f5cf4b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-19 09:29 UTC by TNO-reg
Modified: 2013-08-04 23:04 UTC (History)
5 users (show)

Fixed In Version: mate-system-monitor-1.6.1-1.fc18
Clone Of:
Environment:
Last Closed: 2013-08-04 23:02:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (33.97 KB, text/plain)
2012-12-19 09:29 UTC, TNO-reg
no flags Details
File: core_backtrace (1.04 KB, text/plain)
2012-12-19 09:30 UTC, TNO-reg
no flags Details
File: dso_list (7.96 KB, text/plain)
2012-12-19 09:30 UTC, TNO-reg
no flags Details
File: environ (1.46 KB, text/plain)
2012-12-19 09:30 UTC, TNO-reg
no flags Details
File: limits (1.29 KB, text/plain)
2012-12-19 09:30 UTC, TNO-reg
no flags Details
File: maps (37.33 KB, text/plain)
2012-12-19 09:30 UTC, TNO-reg
no flags Details
File: open_fds (469 bytes, text/plain)
2012-12-19 09:30 UTC, TNO-reg
no flags Details
File: proc_pid_status (931 bytes, text/plain)
2012-12-19 09:30 UTC, TNO-reg
no flags Details
File: var_log_messages (1.27 KB, text/plain)
2012-12-19 09:30 UTC, TNO-reg
no flags Details
Extends color for up to 24 CPU threads (1.71 KB, patch)
2013-05-06 17:18 UTC, Patrick Monnerat
no flags Details | Diff

Description TNO-reg 2012-12-19 09:29:53 UTC
Description of problem:
Mate-system-nomitor crashes at start

Version-Release number of selected component:
mate-system-monitor-1.5.0-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        mate-system-monitor
crash_function: g_settings_schema_get_value
executable:     /usr/bin/mate-system-monitor
kernel:         3.6.11-3.fc18.x86_64
uid:            1000
xsession_errors: (mate-system-monitor:1977): GLib-GIO-ERROR **: Settings schema 'org.mate.system-monitor' does not contain a key named 'cpu-color4'

Truncated backtrace:
Thread no. 1 (5 frames)
 #2 g_settings_schema_get_value at gsettingsschema.c:640
 #3 g_settings_schema_key_init at gsettingsschema.c:751
 #4 g_settings_get_value at gsettings.c:1079
 #5 g_settings_get_string at gsettings.c:1559
 #6 procman_data_new at procman.cpp:288

Comment 1 TNO-reg 2012-12-19 09:29:58 UTC
Created attachment 665989 [details]
File: backtrace

Comment 2 TNO-reg 2012-12-19 09:30:01 UTC
Created attachment 665990 [details]
File: core_backtrace

Comment 3 TNO-reg 2012-12-19 09:30:04 UTC
Created attachment 665991 [details]
File: dso_list

Comment 4 TNO-reg 2012-12-19 09:30:06 UTC
Created attachment 665992 [details]
File: environ

Comment 5 TNO-reg 2012-12-19 09:30:11 UTC
Created attachment 665993 [details]
File: limits

Comment 6 TNO-reg 2012-12-19 09:30:14 UTC
Created attachment 665994 [details]
File: maps

Comment 7 TNO-reg 2012-12-19 09:30:16 UTC
Created attachment 665995 [details]
File: open_fds

Comment 8 TNO-reg 2012-12-19 09:30:19 UTC
Created attachment 665996 [details]
File: proc_pid_status

Comment 9 TNO-reg 2012-12-19 09:30:21 UTC
Created attachment 665997 [details]
File: var_log_messages

Comment 10 Nelson Marques 2012-12-22 17:03:20 UTC
I can't replicate this issue; Anyway you can check if selinux is enabled and test with it disabled, so we can see if SELinux is an issue and fix it ?

PS: I have SELinux always disabled, that might be the itch.

Comment 11 Dan Mashal 2012-12-24 06:07:11 UTC
I'm not a huge fan of 3.6-11. Could you try one kernel back?

Also do you get any package updates if you do "su -c yum distro-sync @mate --enablerepo=updates-testing'" 

Let me know if either of those helps.

Comment 12 Fedora Update System 2013-03-03 23:52:28 UTC
mate-system-monitor-1.5.1-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/mate-system-monitor-1.5.1-1.fc17

Comment 13 Fedora Update System 2013-03-03 23:52:38 UTC
mate-system-monitor-1.5.1-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mate-system-monitor-1.5.1-1.fc18

Comment 14 Fedora Update System 2013-03-04 22:32:55 UTC
Package mate-system-monitor-1.5.1-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mate-system-monitor-1.5.1-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-3394/mate-system-monitor-1.5.1-1.fc18
then log in and leave karma (feedback).

Comment 15 Fedora Update System 2013-03-12 08:45:42 UTC
mate-system-monitor-1.5.1-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 16 Fedora Update System 2013-03-12 08:55:38 UTC
mate-system-monitor-1.5.1-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 17 Patrick Monnerat 2013-05-06 17:18:43 UTC
Created attachment 744277 [details]
Extends color for up to 24 CPU threads

Our very last interactive server has 24 CPU threads, thus reaching the new limit of 16 :-(
The attached patch extends colors for up to 24 threads, but I think nowadays an additional extension to 32 CPU threads won't be silly.

Comment 18 Wolfgang Ulbrich 2013-06-29 14:37:39 UTC
Patrick,
can you do a pull request at github?

Comment 19 Patrick Monnerat 2013-07-01 14:54:46 UTC
Done: https://github.com/mate-desktop/mate-system-monitor/pull/21

Comment 21 Fedora Update System 2013-07-26 14:34:24 UTC
mate-system-monitor-1.6.0-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mate-system-monitor-1.6.0-2.fc18

Comment 22 Fedora Update System 2013-07-26 23:02:15 UTC
Package mate-system-monitor-1.6.0-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mate-system-monitor-1.6.0-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-13688/mate-system-monitor-1.6.0-2.fc18
then log in and leave karma (feedback).

Comment 23 Fedora Update System 2013-08-02 12:57:32 UTC
mate-system-monitor-1.6.1-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/mate-system-monitor-1.6.1-1.fc19

Comment 24 Fedora Update System 2013-08-02 12:57:44 UTC
mate-system-monitor-1.6.1-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mate-system-monitor-1.6.1-1.fc18

Comment 25 Fedora Update System 2013-08-04 23:02:28 UTC
mate-system-monitor-1.6.1-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 26 Fedora Update System 2013-08-04 23:04:12 UTC
mate-system-monitor-1.6.1-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.