GNOME Bugzilla – Bug 138986
Nautilus will crash on startup (AMD64 platform)
Last modified: 2005-05-06 17:01:46 UTC
Description of Problem:After installing Gnome 2.6 on my AMD64, Nautilus will crash when it starts. Steps to reproduce the problem: 1.I installed Gnome 2.6 on my pc 2.I restarted Gnome and later my pc itself 3.Both resulted in a Crash of Nautilus during the startup proces of Gnome. Actual Results:Nautilus will crash. I tried to re-compiled it but that had no result. It doesn't matter if I start it as user or as root. Expected Results: A fine working Gnome 2.6 installation. How often does this happen? Every time when I start Nautilus, no matter what I try. Additional Information: 'nautilus -c' give the following output: mario@Leviathan mario $ nautilus -c running nautilus_self_check_search_uri running nautilus_self_check_file_utilities running nautilus_self_check_file_operations FAIL: check failed in nautilus-file-operations.c, line 2606 evaluated: get_duplicate_name (" (copy)", 1) expected: (another copy) got: (copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2607 evaluated: get_duplicate_name ("foo", 1) expected: foo (copy) got: foo (kopie) FAIL: check failed in nautilus-file-operations.c, line 2608 evaluated: get_duplicate_name (".bashrc", 1) expected: .bashrc (copy) got: .bashrc (kopie) FAIL: check failed in nautilus-file-operations.c, line 2609 evaluated: get_duplicate_name (".foo.txt", 1) expected: .foo (copy).txt got: .foo (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2610 evaluated: get_duplicate_name ("foo foo", 1) expected: foo foo (copy) got: foo foo (kopie) FAIL: check failed in nautilus-file-operations.c, line 2611 evaluated: get_duplicate_name ("foo.txt", 1) expected: foo (copy).txt got: foo (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2612 evaluated: get_duplicate_name ("foo foo.txt", 1) expected: foo foo (copy).txt got: foo foo (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2613 evaluated: get_duplicate_name ("foo foo.txt txt", 1) expected: foo foo (copy).txt txt got: foo foo (kopie).txt txt FAIL: check failed in nautilus-file-operations.c, line 2614 evaluated: get_duplicate_name ("foo...txt", 1) expected: foo.. (copy).txt got: foo.. (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2615 evaluated: get_duplicate_name ("foo...", 1) expected: foo... (copy) got: foo... (kopie) FAIL: check failed in nautilus-file-operations.c, line 2616 evaluated: get_duplicate_name ("foo. (copy)", 1) expected: foo. (another copy) got: foo (kopie). (copy) FAIL: check failed in nautilus-file-operations.c, line 2617 evaluated: get_duplicate_name ("foo (copy)", 1) expected: foo (another copy) got: foo (copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2618 evaluated: get_duplicate_name ("foo (copy).txt", 1) expected: foo (another copy).txt got: foo (copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2619 evaluated: get_duplicate_name ("foo (another copy)", 1) expected: foo (3rd copy) got: foo (another copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2620 evaluated: get_duplicate_name ("foo (another copy).txt", 1) expected: foo (3rd copy).txt got: foo (another copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2621 evaluated: get_duplicate_name ("foo foo (another copy).txt", 1) expected: foo foo (3rd copy).txt got: foo foo (another copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2622 evaluated: get_duplicate_name ("foo (13th copy)", 1) expected: foo (14th copy) got: foo (13th copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2623 evaluated: get_duplicate_name ("foo (13th copy).txt", 1) expected: foo (14th copy).txt got: foo (13th copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2624 evaluated: get_duplicate_name ("foo (21st copy)", 1) expected: foo (22nd copy) got: foo (21st copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2625 evaluated: get_duplicate_name ("foo (21st copy).txt", 1) expected: foo (22nd copy).txt got: foo (21st copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2626 evaluated: get_duplicate_name ("foo (22nd copy)", 1) expected: foo (23rd copy) got: foo (22nd copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2627 evaluated: get_duplicate_name ("foo (22nd copy).txt", 1) expected: foo (23rd copy).txt got: foo (22nd copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2628 evaluated: get_duplicate_name ("foo (23rd copy)", 1) expected: foo (24th copy) got: foo (23rd copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2629 evaluated: get_duplicate_name ("foo (23rd copy).txt", 1) expected: foo (24th copy).txt got: foo (23rd copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2630 evaluated: get_duplicate_name ("foo (24th copy)", 1) expected: foo (25th copy) got: foo (24th copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2631 evaluated: get_duplicate_name ("foo (24th copy).txt", 1) expected: foo (25th copy).txt got: foo (24th copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2632 evaluated: get_duplicate_name ("foo foo (24th copy)", 1) expected: foo foo (25th copy) got: foo foo (24th copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2633 evaluated: get_duplicate_name ("foo foo (24th copy).txt", 1) expected: foo foo (25th copy).txt got: foo foo (24th copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2634 evaluated: get_duplicate_name ("foo foo (100000000000000th copy).txt", 1) expected: foo foo (copy).txt got: foo foo (100000000000000th copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2635 evaluated: get_duplicate_name ("foo (10th copy)", 1) expected: foo (11th copy) got: foo (10th copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2636 evaluated: get_duplicate_name ("foo (10th copy).txt", 1) expected: foo (11th copy).txt got: foo (10th copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2637 evaluated: get_duplicate_name ("foo (11th copy)", 1) expected: foo (12th copy) got: foo (11th copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2638 evaluated: get_duplicate_name ("foo (11th copy).txt", 1) expected: foo (12th copy).txt got: foo (11th copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2639 evaluated: get_duplicate_name ("foo (12th copy)", 1) expected: foo (13th copy) got: foo (12th copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2640 evaluated: get_duplicate_name ("foo (12th copy).txt", 1) expected: foo (13th copy).txt got: foo (12th copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2641 evaluated: get_duplicate_name ("foo (110th copy)", 1) expected: foo (111th copy) got: foo (110th copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2642 evaluated: get_duplicate_name ("foo (110th copy).txt", 1) expected: foo (111th copy).txt got: foo (110th copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2643 evaluated: get_duplicate_name ("foo (122nd copy)", 1) expected: foo (123rd copy) got: foo (122nd copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2644 evaluated: get_duplicate_name ("foo (122nd copy).txt", 1) expected: foo (123rd copy).txt got: foo (122nd copy) (kopie).txt FAIL: check failed in nautilus-file-operations.c, line 2645 evaluated: get_duplicate_name ("foo (123rd copy)", 1) expected: foo (124th copy) got: foo (123rd copy) (kopie) FAIL: check failed in nautilus-file-operations.c, line 2646 evaluated: get_duplicate_name ("foo (123rd copy).txt", 1) expected: foo (124th copy).txt got: foo (123rd copy) (kopie).txt running nautilus_self_check_directory (gnome_segv:27321): Gtk-WARNING **: Ignoring the separator setting Bug-buddy says the following: 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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x0000002a98df5a03 in waitpid () from /lib/libpthread.so.0
+ Trace 45672
Some people on the Gentoo forum suggested that I had to shutdown the fam-daemon. This, however, had no result. The version I installed is: nautilus-2.6.0
I have this same problem as well (on amd64). If a vfat or smbfs file system type have been mounted by /etc/fstab (the bug will not occur if you mount from the command line), Nautilus will not start. To get Nautilus to start, unmount of those file systems. (You can mount them again once Nautilus has started). Others have had this problem as well: http://bugs.gentoo.org/show_bug.cgi?id=46674
I'm on amd64 as well, but I am NOT using supermount. My /etc/fstab follows (note, if I uncomment ANY of the commented lines nautilus starts crashing again): /dev/sda1 /boot ext2 noauto,noatime 1 1 /dev/sda3 / ext3 noatime 0 0 /dev/sda2 none swap sw 0 0 /dev/discs/disc3/part1 /home ext3 noatime 0 0 #/dev/discs/disc2/part1 /mnt/windata ntfs user,noauto,umask=000 0 0 #/dev/discs/disc0/part1 /mnt/windows ntfs user,noauto,umask=000 0 0 #/dev/discs/disc0/part2 /mnt/dos msdos user,noauto,umask=000 0 0 /dev/cdroms/cdrom0 /mnt/cdrom iso9660 user,exec,noauto,ro 0 0 /dev/floppy/0 /mnt/floppy auto user,noauto 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0
I don't have any ntfs/vfat partition or any smb-share mounted. But Nautilus still crashes. This is my /etc/fstab: /dev/hda2 /boot ext2 noauto,noatime 1 1 /dev/hda3 / ext3 noatime 0 0 /dev/cdrom /mnt/cdrom iso9660 users,noauto,ro 0 0 /dev/hda4 /mnt/data ext3 users,noauto,noatime 0 0
I commentedout all my NFS shares in /etc/fstab and now it works. So NFS seem to couse trouble too. Even mount with the 'noauto' option had to be turned off.
Here's a backtrace with debugging symbols: (gdb) run Starting program: /usr/bin/nautilus (nautilus:28778): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", (nautilus:28778): Gtk-WARNING **: Unable to locate theme engine in module_path: "redmond95", Program received signal SIG32, Real-time event 32. 0x0000002a9936f07e in pthread_getconcurrency () from /lib/libpthread.so.0 (gdb) bt
+ Trace 45911
*** Bug 139758 has been marked as a duplicate of this bug. ***
This seems to stem from a buggy cvs version of glibc. See: http://bugs.gentoo.org/show_bug.cgi?id=46674 Is there anybody experiencing this bug who is NOT using Gentoo?
As I just posted on http://bugs.gentoo.org/show_bug.cgi?id=46674 , this bug occurs on Gentoo with the stable glibc-2.3.2. U I [ Found these USE variables in : sys-libs/glibc-2.3.2-r9 ] + + nls : unknown - - pic : Build position independent code. Needed for (prelink/hardened-gcc) - - build : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for creating build images and the first half of bootstrapping. - - nptl : If you want the Native POSIX Threading Library built into glibc I have no clue what nptl is, but I do NOT have it installed. Also, there are duplicates of this bug at http://bugzilla.gnome.org/show_bug.cgi?id=140348 and http://bugzilla.gnome.org/show_bug.cgi?id=135417
*** Bug 135417 has been marked as a duplicate of this bug. ***
*** Bug 140348 has been marked as a duplicate of this bug. ***
*** Bug 141337 has been marked as a duplicate of this bug. ***
*** Bug 141420 has been marked as a duplicate of this bug. ***
*** Bug 141510 has been marked as a duplicate of this bug. ***
*** Bug 142059 has been marked as a duplicate of this bug. ***
I just posted this on the Gentoo Bugzilla: The "users" option is what is doing it! When you have "users" or "user" set, Nautilus makes an icon on the desktop, and an entry in "Save in Folder" on the new save menu (click save in gedit 2.6). That is where the crash is occuring. Everyone, try removing "user" and "users" and see what you get.
Sorry to rain on your parade, but this is not nescssarily true; refer to gentoo bugzilla : http://bugs.gentoo.org/show_bug.cgi?id=46674 In my fstab, I have two entries with "users" which do not cause the segfault and 5 or so which do. In one case, there is negligible difference between a working line and three that dont : see below (this fstab works, uncommenting any lines breaks it). (amd64, kernel 2.6.5, gnome 2.6.1) # /etc/fstab: static file system information. # $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.13 2003/07/17 19:55:18 azarah Exp $ # <fs> <mountpoint> <type> <opts> <dump/pass> /dev/discs/disc0/part2 /boot ext2 noauto,noatime 1 1 /dev/discs/disc0/part3 / ext3 noatime 0 0 /dev/discs/disc0/part1 none swap sw 0 0 /dev/discs/disc2/part1 /arch vfat rw,umask=0000 0 0 /dev/discs/disc1/part1 /mnt/windrive ntfs rw,umask=0000 0 0 #/dev/cdroms/cdrom0 /mnt/cdrom auto noauto,ro,users,exec 0 0 /dev/sde2 /mnt/ipod vfat users,rw,umask=0000,noauto 0 0 #/dev/hdc1 /mnt/archive auto users,rw,umask=0000,noauto 0 0 /dev/sda1 /mnt/cf auto users,rw,umask=0000,noauto 0 0 #/dev/sdb1 /mnt/ms auto users,rw,umask=0000,noauto 0 0 #/dev/sdc1 /mnt/sd auto users,rw,umask=0000,noauto 0 0 #/dev/sdd1 /mnt/sm auto users,rw,umask=0000,noauto 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc defaults 0 0
Again refering to gentoo bugzilla: http://bugs.gentoo.org/show_bug.cgi?id=46674 To summarize: nautilus seems to take notice of fstab entries containing user,users or supermount (any others?). Having one or two such entries is no problem, however if fstab contains three or more such entries then I get the crash. It seems that there does not need to be anything special about these entries with regards to filesystem type etc (I've tried quite a few). It is sufficient that they are user mountable and number greater than or equal to three.
re: herbies comment; Nautilus on my system does not like *ANY* IDE entries with users as a flag; nor does it like my sdc entry (see above); any other two are fine, try a third and the segfault returns. Note that "sde" being my ipod is not connected at boot (normally) and, therefore the device sde is not in /dev at all.
execution fails on the asm "lea 0xffffffffffffff70(%rbp),%rdi". eh? (gdb) where
+ Trace 46873
which contains: GValue context_as_value = { 0 };
I can confirm the same problem with Fedora Core 2 on an AMD64. I had two CDROM entries and one for the floppy drive in /etc/fstab with the "owner" attribute: /dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 /dev/cdrom1 /mnt/cdrom1 udf,iso9660 noauto,owner,kudzu,ro 0 0 /dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0 If those are commented out, nautilus comes up. I have not tried reducing the _number_ of "owner" entries, I just dumped all three. Of course, that kind of screws up the usability of the CDs and floppy, doesn't it? System: Fedora Core 2 (kernel 2.6.5-1.358) Motherboard: ASUS K8V-SE, AMD Athlon64 2000+ RAM: 512MB Need any other info?
i started nautilus with GDB, this is what it looks like: ....-=cut=-.... Run till exit from #0 0x00000036c0139f8b in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0 0x00000036c0b2093c in GNOME_VFS_Daemon_getDrives () from /usr/lib/libgnomevfs-2.so.0 (gdb) finish Run till exit from #0 0x00000036c0b2093c in GNOME_VFS_Daemon_getDrives () from /usr/lib/libgnomevfs-2.so.0 0x00000036c0b46418 in gnome_vfs_volume_monitor_client_get_type () from /usr/lib/libgnomevfs-2.so.0 (gdb) finish Run till exit from #0 0x00000036c0b46418 in gnome_vfs_volume_monitor_client_get_type () from /usr/lib/libgnomevfs-2.so.0 Program received signal SIGSEGV, Segmentation fault. 0x00000036bac66f4b in free () from /lib/libc.so.6 ----- So, it looks like the problem originates from libgnomevfs. BTW: I'm a gentoo on amd64 user, and the segfault only occurs when there are more than 2 "user" entries in fstab.
examening the code in gnome-vfs-volume-monitor-daemon.c, i found out that loopback-devices are threated the same way as non-usermountable devices. So adding loop=/dev/loop1 to your fstab entry options will let nautilus ignore this entry. This is a nice workaround for now, but something goes wrong when adding the third removable device to nautilus on amd64 has to be fixed. Sadly, I'm kinda new to linux-command line debugging and don't have any idea how to debug a library. If someone could give me some hints, that would be great.
Ok, i spent some time on trying to debug the library. I got as far seeing the libgnome-vfs sourcecode in ddd. However, it did not halt at the breakpoint i set in the gnome-vfs-volume-monitor-deamon.c file. This has to do with the simple fact that this file is part of a CORBA deamon that gets called from the -client.c file, over CORBA. I tried attaching gdb to this deamon, but that didn't work for me. I debugged gnome-vfs-volume-monitor-client.c though. It creates an internal list of drives that it recieved from the CORBA deamon. then it wants to free the CORBA object with "CORBA_free (list);". At that point the segfault occurs.
Created attachment 28747 [details] [review] Patch to fix nautilus crasher on AMD64 I just got an AMD64 system this past weekend and was really bummed when I hit this same bug. I did some tracing and debugging and discovered the cause. It is actually an alignment bug in ORBit2 (in the code behind CORBA_free() as XiPHiaS mentioned). Essentially, gnome-vfs2 requests a list of removable media from the volume monitor daemon so that it knows what icons to show on the desktop (CD/DVD-ROM drives, floppy drives, zip drives, etc.). This takes place through a Corba call. The call returns a list of drives and information about the drives in a sequence of structures. The alignment of the structures and their data members are correct when they are constructed (demarshalled), however when the list is passed to CORBA_free() to free the memory used by the list, the code that frees each structure fails to take into account the proper alignment of each structure (8 bytes on AMD64). The result is that after the second item in the list, a point goes far enough astray to cause it to free() some bogus chunks of memory. I made a patch (attached) of a one-liner that should fix this. I don't think its the best way to fix it, but it works. The fix aligns the pointer properly before freeing a structure (within ORBit_freekids_via_TypeCode_T()). diff -Naur ORBit2-2.10.0/src/orb/orb-core/allocators.c ORBit2-2.10.0.1-cbl/src/orb/orb-core/allocators.c --- ORBit2-2.10.0/src/orb/orb-core/allocators.c 2003-07-07 13:11:31.000000000 +0000 +++ ORBit2-2.10.0.1-cbl/src/orb/orb-core/allocators.c 2004-06-16 04:11:27.642691407 +0000 @@ -59,6 +59,7 @@ } case CORBA_tk_except: case CORBA_tk_struct: + mem = ALIGN_ADDRESS (mem, tc->c_align); for (i = 0; i < tc->sub_parts; i++) { subtc = tc->subtypes [i]; mem = ALIGN_ADDRESS (mem, subtc->c_align);
Just tested this on my gentoo box, works a treat. Thanks ever so much for fixing this perotin, it was driving me crazy!
Thanks for finding it. The fix works on my Fedora Core 2 system.
This appears to be covered under http://bugzilla.gnome.org/show_bug.cgi? id=109799
Created attachment 28806 [details] [review] CORBA_tk_struct Alignment patch forward ported from bug 109799
Your right. However, that patch was only applied to the old ORBit and it wasn't fixed in ORBit2. Looks like that whole patch needs to be worked into ORBit2. I've adapted Matt Wilson's patch for bug 109799 to apply to ORBit2 and attached it. It patches cleanly against 2.10.x and fairly cleanly against HEAD. Unfortunately, I don't have access to my AMD64 right now. Can someone please try it and verify that won't cause a fire or give your gerbil cancer? Mario, could you please reassign this to the ORBit2 product?
Reassigning to ORBit2 as requested.
tested the new patch with ORBit-2.10.2 and nautilus-2.6.1 on gentoo amd64. No problems here.
Hi Herbie, can you confirm that 'make check' passes in ORBit2 with this patch ?
Chris - the changes look fine, can you commit with suitable ChangeLog to gnome-2-6 and HEAD branches, and I'll do a new stable release.
Sorry, I don't have a CVS account. Can you please check it in for me?
So - Chris, after looking at it; only the allocators.c part of it was necessary - since we do pre-alignment rather nicely in all the other cases anyway. I did a new release 2.10.3 with this fix (and another similar union alignment fix). Thanks for the great report.
*** Bug 146058 has been marked as a duplicate of this bug. ***
*** Bug 145914 has been marked as a duplicate of this bug. ***
*** Bug 145918 has been marked as a duplicate of this bug. ***
*** Bug 146086 has been marked as a duplicate of this bug. ***
*** Bug 145640 has been marked as a duplicate of this bug. ***
*** Bug 145651 has been marked as a duplicate of this bug. ***
*** Bug 145684 has been marked as a duplicate of this bug. ***
*** Bug 145745 has been marked as a duplicate of this bug. ***
*** Bug 145855 has been marked as a duplicate of this bug. ***
*** Bug 145872 has been marked as a duplicate of this bug. ***
*** Bug 145880 has been marked as a duplicate of this bug. ***
*** Bug 145881 has been marked as a duplicate of this bug. ***
*** Bug 145885 has been marked as a duplicate of this bug. ***
*** Bug 145883 has been marked as a duplicate of this bug. ***
*** Bug 145895 has been marked as a duplicate of this bug. ***
*** Bug 145945 has been marked as a duplicate of this bug. ***
*** Bug 145982 has been marked as a duplicate of this bug. ***
*** Bug 145983 has been marked as a duplicate of this bug. ***
*** Bug 146042 has been marked as a duplicate of this bug. ***
*** Bug 146047 has been marked as a duplicate of this bug. ***
*** Bug 146048 has been marked as a duplicate of this bug. ***
*** Bug 146057 has been marked as a duplicate of this bug. ***
*** Bug 146064 has been marked as a duplicate of this bug. ***
*** Bug 146166 has been marked as a duplicate of this bug. ***
*** Bug 145889 has been marked as a duplicate of this bug. ***
*** Bug 146277 has been marked as a duplicate of this bug. ***
*** Bug 145864 has been marked as a duplicate of this bug. ***
*** Bug 146614 has been marked as a duplicate of this bug. ***
*** Bug 147331 has been marked as a duplicate of this bug. ***
*** Bug 147351 has been marked as a duplicate of this bug. ***
*** Bug 147369 has been marked as a duplicate of this bug. ***
*** Bug 147750 has been marked as a duplicate of this bug. ***
*** Bug 147793 has been marked as a duplicate of this bug. ***
*** Bug 148223 has been marked as a duplicate of this bug. ***
*** Bug 148245 has been marked as a duplicate of this bug. ***
*** Bug 148343 has been marked as a duplicate of this bug. ***
*** Bug 148328 has been marked as a duplicate of this bug. ***
*** Bug 148259 has been marked as a duplicate of this bug. ***
*** Bug 148416 has been marked as a duplicate of this bug. ***
*** Bug 148429 has been marked as a duplicate of this bug. ***
*** Bug 148604 has been marked as a duplicate of this bug. ***
*** Bug 148525 has been marked as a duplicate of this bug. ***
*** Bug 148504 has been marked as a duplicate of this bug. ***
*** Bug 148631 has been marked as a duplicate of this bug. ***
*** Bug 148869 has been marked as a duplicate of this bug. ***
*** Bug 148872 has been marked as a duplicate of this bug. ***
*** Bug 148967 has been marked as a duplicate of this bug. ***
*** Bug 149217 has been marked as a duplicate of this bug. ***
*** Bug 148847 has been marked as a duplicate of this bug. ***
*** Bug 149406 has been marked as a duplicate of this bug. ***
*** Bug 149944 has been marked as a duplicate of this bug. ***
*** Bug 150006 has been marked as a duplicate of this bug. ***
*** Bug 150160 has been marked as a duplicate of this bug. ***
*** Bug 150554 has been marked as a duplicate of this bug. ***
*** Bug 151027 has been marked as a duplicate of this bug. ***
*** Bug 151322 has been marked as a duplicate of this bug. ***
*** Bug 151358 has been marked as a duplicate of this bug. ***
*** Bug 151992 has been marked as a duplicate of this bug. ***
*** Bug 152287 has been marked as a duplicate of this bug. ***
*** Bug 152865 has been marked as a duplicate of this bug. ***
*** Bug 153031 has been marked as a duplicate of this bug. ***
*** Bug 153034 has been marked as a duplicate of this bug. ***
*** Bug 153016 has been marked as a duplicate of this bug. ***
*** Bug 153666 has been marked as a duplicate of this bug. ***
*** Bug 153690 has been marked as a duplicate of this bug. ***
*** Bug 153762 has been marked as a duplicate of this bug. ***
*** Bug 154362 has been marked as a duplicate of this bug. ***
*** Bug 154319 has been marked as a duplicate of this bug. ***
*** Bug 154939 has been marked as a duplicate of this bug. ***
*** Bug 154951 has been marked as a duplicate of this bug. ***
*** Bug 154972 has been marked as a duplicate of this bug. ***
*** Bug 155548 has been marked as a duplicate of this bug. ***
*** Bug 155313 has been marked as a duplicate of this bug. ***
*** Bug 155798 has been marked as a duplicate of this bug. ***
*** Bug 155993 has been marked as a duplicate of this bug. ***
*** Bug 156073 has been marked as a duplicate of this bug. ***
*** Bug 156337 has been marked as a duplicate of this bug. ***
*** Bug 156202 has been marked as a duplicate of this bug. ***
*** Bug 156639 has been marked as a duplicate of this bug. ***
*** Bug 156723 has been marked as a duplicate of this bug. ***
*** Bug 155432 has been marked as a duplicate of this bug. ***
*** Bug 157493 has been marked as a duplicate of this bug. ***
*** Bug 157934 has been marked as a duplicate of this bug. ***
*** Bug 168482 has been marked as a duplicate of this bug. ***
*** Bug 303275 has been marked as a duplicate of this bug. ***