Bug 488099 – crash in Open Folder: A normal shutdown was in...

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 488099 - crash in Open Folder: A normal shutdown was in...


Summary:	crash in Open Folder: A normal shutdown was in...


Status:	RESOLVED DUPLICATE of bug 386858

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-19 00:34 UTC by daxene
Modified:	2007-10-19 22:07 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description daxene 2007-10-19 00:34:26 UTC

Version: 2.18.3

What were you doing when the application crashed?
A normal shutdown was in progress.


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 74743808 vsize: 74743808 resident: 10457088 share: 8650752 rss: 10457088 rss_rlim: 4294967295
CPU usage: start_time: 1192753928 rtime: 18 utime: 14 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 -1208891680 (LWP 3297)]
[New Thread -1233130608 (LWP 3392)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 171286

Thread 2 (Thread -1233130608 (LWP 3392))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gnome_vfs_uri_unref
from /usr/lib/libgnomevfs-2.so.0
#5 g_list_foreach
from /lib/libglib-2.0.so.0
#6 gnome_vfs_uri_list_unref
from /usr/lib/libgnomevfs-2.so.0
#7 gnome_vfs_uri_list_free
from /usr/lib/libgnomevfs-2.so.0
#8 ??
from /usr/lib/libgnomevfs-2.so.0
#9 ??
#10 ??
from /usr/lib/libgnomevfs-2.so.0
#11 ??
#12 ??
from /usr/lib/libgnomevfs-2.so.0
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
from /usr/lib/libgnomevfs-2.so.0
#18 ??
#19 ??
#20 ??
from /usr/lib/libgnomevfs-2.so.0
#21 ??
#22 ??
from /usr/lib/libgnomevfs-2.so.0
#23 ??
#24 ??
from /usr/lib/libgnomevfs-2.so.0
#25 ??
#26 ??



----------- .xsession-errors ---------------------
alarm-queue.c:551 (load_alarms) - Setting Call backs 
alarm-notify.c:316 (cal_opened_cb) file:///home/dean/.evolution/calendar/local/system - Calendar Status 0
alarm-queue.c:1998 (alarm_queue_add_async) - 0x8e85530
alarm-queue.c:585 (load_alarms_for_today) - From Thu Oct 18 19:32:15 2007
 to Thu Oct 18 19:32:15 2007
alarm-queue.c:522 (load_alarms) 
alarm-queue.c:551 (load_alarms) - Setting Call backs 
alarm-notify.c:316 (cal_opened_cb) file:///home/dean/.evolution/tasks/local/system - Calendar Status 0
alarm-queue.c:1998 (alarm_queue_add_async) - 0x8ea37b0
alarm-notify.c:316 (cal_opened_cb) contacts:/// - Calendar Status 0
alarm-queue.c:585 (load_alarms_for_today) - From Thu Oct 18 19:32:X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x64
--------------------------------------------------

Comment 1 Christian Kirbach 2007-10-19 22:07:05 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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