Version-Release number of selected component: nautilus-3.6.3-4.fc18 Additional info: backtrace_rating: 4 cmdline: nautilus -n core_backtrace: crash_function: _XAllocID executable: /usr/bin/nautilus kernel: 3.7.4-204.fc18.i686.PAE remote_result: 753368 uid: 1000 var_log_messages: Jan 26 16:39:45 localhost abrt[3915]: Saved core dump of pid 3410 (/usr/bin/nautilus) to /var/spool/abrt/ccpp-2013-01-26-16:39:44-3410 (74383360 bytes) Truncated backtrace: Thread no. 1 (10 frames) #5 _XAllocID at xcb_io.c:528 #6 XCreatePixmap at CrPixmap.c:56 #7 _cairo_xlib_surface_create_similar at cairo-xlib-surface.c:311 #8 _cairo_surface_create_similar_scratch at cairo-surface.c:470 #9 _cairo_surface_create_similar_solid at cairo-surface.c:865 #10 _cairo_default_context_push_group at cairo-default-context.c:168 #11 INT_cairo_push_group_with_content at cairo.c:515 #12 gdk_window_update_icon at gdkwindow-x11.c:3285 #13 gdk_x11_window_set_icon_list at gdkwindow-x11.c:3415 #15 gdk_window_set_icon_list at gdkwindow.c:10519 Potential duplicate: bug 708273
Created attachment 687900 [details] File: backtrace
Created attachment 687901 [details] File: cgroup
Created attachment 687902 [details] File: dso_list
Created attachment 687903 [details] File: environ
Created attachment 687904 [details] File: limits
Created attachment 687905 [details] File: maps
Created attachment 687906 [details] File: open_fds
Created attachment 687907 [details] File: proc_pid_status
log in ->log out -> log in backtrace_rating: 4 Package: nautilus-3.6.3-4.fc18 OS Release: Fedora release 18 (Spherical Cow)
Nautilus crashed at startup backtrace_rating: 4 Package: nautilus-3.6.3-4.fc18 OS Release: Fedora release 18 (Spherical Cow)
I tried to copy the text of a problem to be reported with abrt and paste it, but in trying to carry out this operation the shell crashes (which seems to have for a bug of nautilus). I actually pointed out the solution of some problems i encountered with gnome-shell. In one of these reports i have inserted a comment, hoping that it has to be noted. Thanks and best wishes. Congratulations to the distribution which, to be updated, and very very stable and well taken care of. I come from Debian (which is also very good) but not regret it. Avv. Marengoni. backtrace_rating: 4 Package: nautilus-3.6.3-4.fc18 OS Release: Fedora release 18 (Spherical Cow)
installed new updates, logged out and back in. See installed / updates below (have experienced this problem before after installing updates on FC18): Apr 25 20:34:05 Updated: 1:perl-parent-0.225-242.fc18.noarch Apr 25 20:34:05 Updated: perl-Pod-Perldoc-3.17.00-242.fc18.noarch Apr 25 20:34:06 Updated: 1:perl-Pod-Escapes-1.04-242.fc18.noarch Apr 25 20:34:06 Updated: 4:perl-libs-5.16.3-242.fc18.i686 Apr 25 20:34:06 Updated: 4:perl-macros-5.16.3-242.fc18.i686 Apr 25 20:34:06 Updated: perl-PathTools-3.39.2-242.fc18.i686 Apr 25 20:34:07 Updated: perl-Carp-1.26-242.fc18.noarch Apr 25 20:34:07 Updated: 1:perl-Module-Pluggable-4.00-242.fc18.noarch Apr 25 20:34:07 Updated: perl-threads-shared-1.40-242.fc18.i686 Apr 25 20:34:07 Updated: perl-Scalar-List-Utils-1.25-242.fc18.i686 Apr 25 20:34:07 Updated: perl-threads-1.86-242.fc18.i686 Apr 25 20:34:07 Updated: perl-Pod-Parser-1.51-242.fc18.noarch Apr 25 20:34:08 Updated: 1:perl-Pod-Simple-3.20-242.fc18.noarch Apr 25 20:34:18 Updated: 4:perl-5.16.3-242.fc18.i686 Apr 25 20:34:18 Updated: perl-Data-Dumper-2.135.06-242.fc18.i686 Apr 25 20:34:20 Updated: GConf2-3.2.6-2.fc18.i686 Apr 25 20:34:21 Updated: libgsf-1.14.24-4.fc18.i686 Apr 25 20:34:21 Updated: libxml2-python-2.9.1-1.fc18.i686 Apr 25 20:34:21 Updated: python-pycurl-7.19.0-13.1.fc18.i686 Apr 25 20:34:43 Updated: 1:java-1.7.0-openjdk-1.7.0.19-2.3.9.3.fc18.i686 backtrace_rating: 4 cmdline: nautilus -n core_backtrace: crash_function: _XAllocID executable: /usr/bin/nautilus kernel: 3.8.7-201.fc18.i686.PAE package: nautilus-3.6.3-4.fc18 reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT) uid: 500 ureports_counter: 1 xsession_errors:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
1. Installed system updates via "gpk-update-viewer". 2. Prompted to log out and back in for updates to take effect. 3. Logged back in. 4. Error occured. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: nautilus -n crash_function: _XAllocID executable: /usr/bin/nautilus kernel: 3.11.10-100.fc18.i686.PAE package: nautilus-3.6.3-4.fc18 reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.