After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 431188 - crash in CD/DVD Creator: Haha, I was putting up e...
crash in CD/DVD Creator: Haha, I was putting up e...
Status: RESOLVED DUPLICATE of bug 348161
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-18 23:44 UTC by sksallaj
Modified: 2007-04-19 03:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description sksallaj 2007-04-18 23:44:25 UTC 
What were you doing when the application crashed?
Haha, I was putting up emblems on my folder icon. :)


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2944.fc6 #1 SMP Tue Apr 10 18:46:45 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 100642816 vsize: 0 resident: 100642816 share: 0 rss: 26030080 rss_rlim: 0
CPU usage: start_time: 1176923736 rtime: 0 utime: 868 stime: 0 cutime:780 cstime: 0 timeout: 88 it_real_value: 0 frequency: 51

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208530176 (LWP 3158)]
(no debugging symbols found)
0x0094b402 in __kernel_vsyscall ()

+ Trace 128899

Thread 1 (Thread -1208530176 (LWP 3158))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 fm_directory_view_bump_zoom_level
  • #11 nautilus_file_ref
  • #12 nautilus_file_ref
  • #13 nautilus_icon_container_request_update_all
  • #14 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 POA_Nautilus_MetafileMonitor__init
  • #20 __libc_start_main
    from /lib/libc.so.6
  • #21 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
** (eggcups:3166): WARNING **: IPP request failed with status 1030
error getting update info:  Cannot open/read repomd.xml file for repository: livna
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
/lib/i386/libjavaplugin_nscp.so: cannot open shared object file: No such file or directoryclosing
** (nautilus:3158): WARNING **: destroyed file has call_when_ready pending
(nautilus:3158): GLib-GObject-CRITICAL **: g_object_unref: assertion `object->ref_count > 0' failed
** ERROR **: file fm-icon-container.c: line 157 (fm_icon_container_prioritize_thumbnailing): assertion failed: (NAUTILUS_IS_FILE (file))
aborting...
** (bug-buddy:3978): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-04-19 03:02:45 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 348161 ***