Bug 868472

Summary: [abrt] mate-file-manager-1.4.0-12.fc18: handle_error: Process /usr/bin/caja was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Dan Mashal <dan.mashal>
Component: mate-file-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: a15y87, affix, akshayvyas29, alt.rdp, billyestuvoaqui, brian, bugzilla, dan.mashal, davidz, joey10946, ktim888, leigh123linux, markwilt, me, naipaul_ojar, raul_chirea, rdieter, redhat, satellitgo, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c4b60b75bcdfbe47c7261839ea875de658947453
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-23 08:03:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 868538    
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: xsession_errors
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds
none
File: build_ids none

Description Dan Mashal 2012-10-20 03:56:00 UTC 
Version-Release number of selected component:
mate-file-manager-1.4.0-12.fc18

Additional info:
libreport version: 2.0.16
abrt_version:   2.0.16
backtrace_rating: 4
cmdline:        caja
crash_function: handle_error
kernel:         3.6.2-2.fc18.x86_64

truncated backtrace:
:Thread no. 1 (8 frames)
: #4 handle_error at xcb_io.c:212
: #5 handle_response at xcb_io.c:324
: #6 _XEventsQueued at xcb_io.c:363
: #7 XPending at Pending.c:55
: #8 gdk_check_xpending at gdkevents-x11.c:159
: #9 gdk_event_check at gdkevents-x11.c:2378
: #10 g_main_context_check at gmain.c:3169
: #13 gtk_main at gtkmain.c:1257
Comment 1 Dan Mashal 2012-10-20 03:56:02 UTC 
Created attachment 630341 [details]
File: core_backtrace
Comment 2 Dan Mashal 2012-10-20 03:56:03 UTC 
Created attachment 630342 [details]
File: environ
Comment 3 Dan Mashal 2012-10-20 03:56:04 UTC 
Created attachment 630343 [details]
File: limits
Comment 4 Dan Mashal 2012-10-20 03:56:06 UTC 
Created attachment 630344 [details]
File: backtrace
Comment 5 Dan Mashal 2012-10-20 03:56:07 UTC 
Created attachment 630345 [details]
File: cgroup
Comment 6 Dan Mashal 2012-10-20 03:56:09 UTC 
Created attachment 630346 [details]
File: xsession_errors
Comment 7 Dan Mashal 2012-10-20 03:56:10 UTC 
Created attachment 630347 [details]
File: maps
Comment 8 Dan Mashal 2012-10-20 03:56:11 UTC 
Created attachment 630348 [details]
File: dso_list
Comment 9 Dan Mashal 2012-10-20 03:56:13 UTC 
Created attachment 630349 [details]
File: proc_pid_status
Comment 10 Dan Mashal 2012-10-20 03:56:14 UTC 
Created attachment 630350 [details]
File: var_log_messages
Comment 11 Dan Mashal 2012-10-20 03:56:15 UTC 
Created attachment 630351 [details]
File: open_fds
Comment 12 Dan Mashal 2012-10-20 03:56:17 UTC 
Created attachment 630352 [details]
File: build_ids
Comment 13 Ryan Petersen 2012-10-21 10:31:13 UTC 
Problem occured while changing monitor resolution from 1280x1024 to 1024x768 while in the MATE Desktop Environment.
Switching back to 1280x1024 did not reproduce the problem. Switching back to 1024x768 from the higher resolution reproduces the problem.


backtrace_rating: 4
Package: mate-file-manager-1.4.0-12.fc19
Architecture: i686
OS Release: Fedora release 19 (Rawhide)
Comment 14 Dan Mashal 2012-10-23 04:59:56 UTC 
Installing clearlooks-compact-gnome-theme does help. 

However it does not fix the problem. (There is a combination of problems here.)
Comment 15 leigh scott 2012-10-25 20:11:43 UTC 
Is this problem happening on hardware or VM?
Comment 16 Dan Mashal 2012-10-25 20:12:46 UTC 
vm, I'm working with upstream to resolve this.
Comment 17 Dan Mashal 2012-10-28 00:50:44 UTC 
This is caused by DBus.

var_log_messages:
:Oct 27 16:50:51 localhost dbus-daemon[760]: dbus[760]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.44" (uid=1000 pid=1273 comm="caja ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=830 comm="/usr/sbin/console-kit-daemon --no-daemon ")
:Oct 27 16:50:51 localhost dbus[760]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.44" (uid=1000 pid=1273 comm="caja ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=830 comm="/usr/sbin/console-kit-daemon --no-daemon ")
:Oct 27 17:06:39 localhost dbus-daemon[744]: dbus[744]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=1169 comm="caja ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=811 comm="/usr/sbin/console-kit-daemon --no-daemon ")
:Oct 27 17:06:39 localhost dbus[744]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=1169 comm="caja ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=811 comm="/usr/sbin/console-kit-daemon --no-daemon ")
:Oct 27 17:06:55 localhost kernel: [  101.766366] traps: caja[1169] trap int3 ip:7f5f9fff4ca7 sp:7ffffbd3a550 error:0
:Oct 27 17:06:55 localhost abrt[1355]: Saved core dump of pid 1169 (/usr/bin/caja) to /var/spool/abrt/ccpp-2012-10-27-17:06:55-1169 (23568384 bytes)
:Oct 27 17:06:56 localhost dbus-daemon[744]: dbus[744]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.54" (uid=1000 pid=1357 comm="caja ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=811 comm="/usr/sbin/console-kit-daemon --no-daemon ")
:Oct 27 17:06:56 localhost dbus[744]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.54" (uid=1000 pid=1357 comm="caja ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=811 comm="/usr/sbin/console-kit-daemon --no-daemon ")


Changing /etc/dbus-1/system.conf to the following fixes the issue:

    <allow send_destination="org.freedesktop.DBus"
          send_interface="org.freedesktop.DBus"
          send_member="UpdateActivationEnvironment"/>
Comment 18 Dan Mashal 2012-10-29 04:50:52 UTC 
*** Bug 870852 has been marked as a duplicate of this bug. ***
Comment 19 Dan Mashal 2012-10-29 05:02:25 UTC 
*** Bug 868571 has been marked as a duplicate of this bug. ***
Comment 20 Dan Mashal 2012-10-30 06:26:15 UTC 
Found this which points to an unfixed bug in dbus-sharp upstream:

https://github.com/mono/dbus-sharp/issues/17
Comment 21 Dan Mashal 2012-11-10 09:27:50 UTC 
*** Bug 875276 has been marked as a duplicate of this bug. ***
Comment 22 Dan Mashal 2012-11-10 09:28:25 UTC 
*** Bug 874102 has been marked as a duplicate of this bug. ***
Comment 23 Dan Mashal 2012-11-13 10:22:13 UTC 
*** Bug 875917 has been marked as a duplicate of this bug. ***
Comment 24 satellitgo 2012-11-13 20:10:20 UTC 
took screenshot in mate 1.5.1

backtrace_rating: 4
Package: mate-file-manager-1.5.0-2.fc18
OS Release: Fedora release 18 (Spherical Cow)
Comment 25 Dan Mashal 2012-11-17 05:42:50 UTC 
Please see the following links for updates to this bug:

https://github.com/mate-desktop/mate-file-manager/issues/40
https://github.com/mate-desktop/mate-file-manager/issues/41

Will be fixed soon in 1.5 hopefully.
Comment 26 leigh scott 2012-11-18 23:55:43 UTC 
*** Bug 877821 has been marked as a duplicate of this bug. ***
Comment 27 Dan Mashal 2012-11-19 13:23:28 UTC 
*** Bug 877823 has been marked as a duplicate of this bug. ***
Comment 28 Fedora Update System 2012-11-19 13:30:39 UTC 
mate-file-manager-1.5.0-4.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mate-file-manager-1.5.0-4.fc18
Comment 29 Fedora Update System 2012-11-19 19:32:48 UTC 
Package mate-file-manager-1.5.0-4.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-file-manager-1.5.0-4.fc18'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-18487/mate-file-manager-1.5.0-4.fc18
then log in and leave karma (feedback).
Comment 30 Fedora Update System 2012-11-20 11:06:44 UTC 
mate-panel-1.5.1-1.fc18, mate-image-viewer-1.5.0-2.fc18, libmatewnck-1.5.0-1.fc18, libmatenotify-1.5.0-1.fc18, libmateweather-1.5.0-1.fc18, libmatekbd-1.5.0-1.fc18, libmatekeyring-1.5.0-1.fc18, mate-icon-theme-1.5.0-1.fc18, mate-dialogs-1.5.0-2.fc18, mate-doc-utils-1.5.0-1.fc18, mate-menus-1.5.0-1.fc18, mate-media-1.5.0-1.fc18, mate-system-monitor-1.5.0-1.fc18, mate-keyring-1.5.0-2.fc18, mate-settings-daemon-1.5.3-1.fc18, mate-control-center-1.5.0-2.fc18, mate-notification-daemon-1.5.0-1.fc18, mate-session-manager-1.5.0-1.fc18, mate-themes-1.5.0-1.fc18, mate-utils-1.4.0-4.fc18, mate-screensaver-1.5.0-3.fc18, mate-window-manager-1.5.2-7.fc18, mate-desktop-1.5.3-4.fc18, mate-power-manager-1.5.0-2.fc18, mate-file-manager-1.5.0-5.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2012-17936/mate-screensaver-1.5.0-3.fc18,mate-utils-1.4.0-4.fc18,mate-power-manager-1.5.0-2.fc18,mate-themes-1.5.0-1.fc18,mate-file-manager-1.5.0-5.fc18,mate-session-manager-1.5.0-1.fc18,mate-notification-daemon-1.5.0-1.fc18,mate-control-center-1.5.0-2.fc18,mate-settings-daemon-1.5.3-1.fc18,mate-window-manager-1.5.2-7.fc18,mate-keyring-1.5.0-2.fc18,mate-system-monitor-1.5.0-1.fc18,mate-media-1.5.0-1.fc18,mate-menus-1.5.0-1.fc18,mate-panel-1.5.1-1.fc18,libmatewnck-1.5.0-1.fc18,libmatenotify-1.5.0-1.fc18,libmateweather-1.5.0-1.fc18,libmatekbd-1.5.0-1.fc18,libmatekeyring-1.5.0-1.fc18,mate-icon-theme-1.5.0-1.fc18,mate-desktop-1.5.3-4.fc18,mate-dialogs-1.5.0-2.fc18,mate-doc-utils-1.5.0-1.fc18,mate-image-viewer-1.5.0-2.fc18
Comment 31 Fedora Update System 2012-11-23 08:03:11 UTC 
mate-panel-1.5.1-1.fc18, mate-image-viewer-1.5.0-2.fc18, libmatewnck-1.5.0-1.fc18, libmatenotify-1.5.0-1.fc18, libmateweather-1.5.0-1.fc18, libmatekbd-1.5.0-1.fc18, libmatekeyring-1.5.0-1.fc18, mate-icon-theme-1.5.0-1.fc18, mate-dialogs-1.5.0-2.fc18, mate-doc-utils-1.5.0-1.fc18, mate-menus-1.5.0-1.fc18, mate-media-1.5.0-1.fc18, mate-system-monitor-1.5.0-1.fc18, mate-keyring-1.5.0-2.fc18, mate-settings-daemon-1.5.3-1.fc18, mate-control-center-1.5.0-2.fc18, mate-notification-daemon-1.5.0-1.fc18, mate-session-manager-1.5.0-1.fc18, mate-themes-1.5.0-1.fc18, mate-utils-1.4.0-4.fc18, mate-screensaver-1.5.0-3.fc18, mate-window-manager-1.5.2-7.fc18, mate-desktop-1.5.3-4.fc18, mate-power-manager-1.5.0-2.fc18, mate-file-manager-1.5.0-5.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 32 Fedora Update System 2012-12-04 02:52:11 UTC 
mate-file-manager-1.5.2-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mate-file-manager-1.5.2-1.fc18
Comment 33 Fedora Update System 2013-01-11 23:14:50 UTC 
mate-file-manager-1.5.2-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 34 billyestuvoaqui 2013-01-13 18:17:11 UTC 
After updating, I get this error every 20 seconds:

https://bugzilla.redhat.com/show_bug.cgi?id=894572
Comment 35 Naipaul Ojar 2013-03-26 01:36:22 UTC 
I have mate-file-manager-1.5.4.1.fc18.x86_64 and I received the error tonight, which abrt, matched to this bug. So I did not upload the data.
Comment 36 Dan Mashal 2013-03-26 10:05:23 UTC 
Please update.
Comment 37 Brian J. Murrell 2013-12-11 16:57:33 UTC 
Fedora 20's abrt flagged a crash as this bug.  Can we get the Version: updated to 20 please so that this bug is tracked for F20 and closed EOL too prematurely?