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 478266 - crash in CD/DVD Creator: search for file
crash in CD/DVD Creator: search for file
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-19 04:38 UTC by sok
Modified: 2007-10-05 14:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sok 2007-09-19 04:38:17 UTC
What were you doing when the application crashed?
search for file


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: crystalsvg

Memory status: size: 680071168 vsize: 680071168 resident: 64253952 share: 29761536 rss: 64253952 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190129435 rtime: 3850 utime: 3439 stime: 411 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496376896 (LWP 2924)]
[New Thread 1157658960 (LWP 6514)]
[New Thread 1136679248 (LWP 6410)]
[New Thread 1126189392 (LWP 6409)]
[New Thread 1115699536 (LWP 6408)]
[New Thread 1094719824 (LWP 6407)]
[New Thread 1084229968 (LWP 6406)]
[New Thread 1105209680 (LWP 6405)]
(no debugging symbols found)
0x0000003def2c82e6 in poll () from /lib64/libc.so.6

Thread 2 (Thread 1157658960 (LWP 6514))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strstr
    from /lib64/libc.so.6
  • #4 ??
  • #5 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #7 gnome_vfs_directory_visit_uri
    from /usr/lib64/libgnomevfs-2.so.0
  • #8 ??
  • #9 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #10 start_thread
    from /lib64/libpthread.so.0
  • #11 clone
    from /lib64/libc.so.6


----------- .xsession-errors (9 sec old) ---------------------
(nautilus:5629): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)

Соединение с сервисом [    ###      ]
Соединение с сервисом [   ###       ]
Соединение с сервисом [  ###        ]
Соединение с се
Файл протокола поможет, вам, решить проблему.
Предупреждение менеджера окон: Received a _NET_WM_MOVERESIZE message for 0x1201479 (Созда); these messages lack timestamps and therefore suck.
Предупреждение менеджера окон: Received a _NET_WM_MOVERESIZE message for 0x1201a9b (sok - Об); these messages lack timestamps and therefore suck.
Предупреждение менеджера окон: Received a _NET_WM_MOVERESIZE message for 0x1201a9b (sok - Об); these messages lack timestamps and therefore suck.
--- Hash table keys for warning below:
--> file:///home/sok
(nautilus:6380): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Предупреждение менеджера окон: Received a _NET_WM_MOVERESIZE message for 0x1205354 (Music - О); these messages lack timestamps and therefore suck.
(nautilus:2924): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
--------------------------------------------------
Comment 1 palfrey 2007-10-05 14:30:32 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 454799 ***