[Bug 66597] Re: EDGY nautilus crash when GNOME starts

2007-02-24 Thread Sebastien Bacher
no update from the submitter and the other crashes look likes different
problems than that one, closing the bug, feel free to reopen with the
asked information if you still get the problem

** Changed in: nautilus (Ubuntu)
   Importance: Undecided = Medium
   Status: Needs Info = Rejected

-- 
EDGY nautilus crash when GNOME starts
https://launchpad.net/bugs/66597

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 66597] Re: EDGY nautilus crash when GNOME starts

2007-02-23 Thread Juan José
(gdb) run
Starting program: /usr/bin/nautilus 
[Thread debugging using libthread_db enabled]
[New Thread -1226512720 (LWP 8280)]
GTK Accessibility Module initialized
Bonobo accessibility support initialized
[New Thread -1235100768 (LWP 8289)]
[New Thread -1243493472 (LWP 8290)]
[New Thread -1251886176 (LWP 8291)]
[New Thread -1260278880 (LWP 8292)]
[New Thread -1268671584 (LWP 8293)]
[New Thread -1277064288 (LWP 8294)]
[New Thread -1285456992 (LWP 8295)]
[New Thread -1293849696 (LWP 8296)]
[New Thread -1302242400 (LWP 8297)]
[New Thread -1310635104 (LWP 8298)]

(nautilus:8280): libgnomevfs-WARNING **: Cannot load module `/usr/lib
/gnome-vfs-2.0/modules/libmapping.so' (/usr/lib/gnome-
vfs-2.0/modules/libmapping.so: cannot open shared object file: File or
directory not found)

(nautilus:8280): libgnomevfs-WARNING **: Cannot load module `/usr/lib
/gnome-vfs-2.0/modules/libmapping.so' (/usr/lib/gnome-
vfs-2.0/modules/libmapping.so: cannot open shared object file: File or
directory not found)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226512720 (LWP 8280)]
0xb768bc47 in g_str_hash () from /usr/lib/libglib-2.0.so.0



(gdb) thread apply all bt

Thread 11 (Thread -1310635104 (LWP 8298)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76dfa8c in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7310113 in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x081f3af0 in ?? ()
#4  0x081bd168 in ?? ()
#5  0xb1e143b8 in ?? ()
#6  0xb76d61e4 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0xb76decc0 in __pthread_mutex_unlock_usercnt ()
   from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb1e143c8 in ?? ()
#9  0xb767fdef in g_queue_peek_tail_link () from /usr/lib/libglib-2.0.so.0
Previous frame inner to this frame (corrupt stack?)

Thread 10 (Thread -1302242400 (LWP 8297)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76dfa8c in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7310113 in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x081f3af0 in ?? ()
#4  0x081bd168 in ?? ()
#5  0xb26153b8 in ?? ()
---Type return to continue, or q return to quit---
#6  0xb76d61e4 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0xb76decc0 in __pthread_mutex_unlock_usercnt ()
   from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb26153c8 in ?? ()
#9  0xb767fdef in g_queue_peek_tail_link () from /usr/lib/libglib-2.0.so.0
Previous frame inner to this frame (corrupt stack?)

Thread 9 (Thread -1293849696 (LWP 8296)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76dfa8c in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7310113 in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x081f3af0 in ?? ()
#4  0x081bd168 in ?? ()
#5  0xb2e163b8 in ?? ()
#6  0xb76d61e4 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0xb76decc0 in __pthread_mutex_unlock_usercnt ()
   from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb2e163c8 in ?? ()
#9  0xb767fdef in g_queue_peek_tail_link () from /usr/lib/libglib-2.0.so.0
Previous frame inner to this frame (corrupt stack?)

Thread 8 (Thread -1285456992 (LWP 8295)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76dfa8c in pthread_cond_timedwait@@GLIBC_2.3.2 ()
---Type return to continue, or q return to quit---
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7310113 in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x081f3af0 in ?? ()
#4  0x081bd168 in ?? ()
#5  0xb36173b8 in ?? ()
#6  0xb76d61e4 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0xb76decc0 in __pthread_mutex_unlock_usercnt ()
   from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb36173c8 in ?? ()
#9  0xb767fdef in g_queue_peek_tail_link () from /usr/lib/libglib-2.0.so.0
Previous frame inner to this frame (corrupt stack?)

Thread 7 (Thread -1277064288 (LWP 8294)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76dfa8c in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7310113 in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x081f3af0 in ?? ()
#4  0x081bd168 in ?? ()
#5  0xb3e183b8 in ?? ()
#6  0xb76d61e4 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0xb76decc0 in __pthread_mutex_unlock_usercnt ()
   from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb3e183c8 in ?? ()
---Type return to continue, or q return to quit---
#9  0xb767fdef in g_queue_peek_tail_link () from /usr/lib/libglib-2.0.so.0
Previous frame inner to this frame (corrupt stack?)

Thread 6 (Thread -1268671584 (LWP 8293)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76dfa8c in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7310113 in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x081f3af0 in ?? ()
#4  0x081bd168 in ?? ()
#5  0xb46193b8 in ?? ()
#6  0xb76d61e4 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0xb76decc0 in __pthread_mutex_unlock_usercnt ()
   from /lib/tls/i686/cmov/libpthread.so.0
#8  0xb46193c8 in ?? ()
#9  0xb767fdef in g_queue_peek_tail_link () from /usr/lib/libglib-2.0.so.0
Previous frame inner to 

[Bug 66597] Re: EDGY nautilus crash when GNOME starts

2007-01-26 Thread Jim Robinson
I apparently experienced the same problem. After running the latest round of 
upgrades I restarted my computer. Once the desktop loaded an icon appeared in 
the system tray stateing that a program had crashed. I clicked the icon and it 
identified nautilus as the program that crashed. I searched the bugs and found 
this bug report to be exactly the same as what happened to me.
I ran the backtrace as stated above but it did not crash. It simply opened up a 
nautilus window. It only crashed when the desktop loaded and there were no 
nautilus windows or programs active that I was aware of, so I cannot reproduce 
the crash.

I have attached my initial crash report in case it helps at all, but the
backtrace did not cause nautilus to crash.

** Attachment added: Nautilus Crash
   http://librarian.launchpad.net/5906839/_usr_bin_nautilus.1000.crash

-- 
EDGY nautilus crash when GNOME starts
https://launchpad.net/bugs/66597

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 66597] Re: EDGY nautilus crash when GNOME starts

2006-11-23 Thread Sebastien Bacher
how do you know that's the same bug?

-- 
EDGY nautilus crash when GNOME starts
https://launchpad.net/bugs/66597

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 66597] Re: EDGY nautilus crash when GNOME starts

2006-11-15 Thread ulugeyik
I have same exact problem after upgrading a thinkpad X32 to edgy:
'The application nautilus has quit unexpectedly.'
This pops up continuously. Bug buddy was not too helpful in sending out a bug.
I tried what you suggested above, the output is pasted below. It is a very 
annoying error.
Thanks,
Turgut

[EMAIL PROTECTED]:~$ gnome-session-remove nautilus
Removing 'nautilus' from the session

(gnome-session-remove:5611): GLib-CRITICAL **: g_shell_parse_argv: assertion 
`co mmand_line != NULL' failed
(gdb) thread apply all bt

Thread 13 (Thread -1347589200 (LWP 5696)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76f8eec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb733d5dc in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x0828b438 in ?? ()
#4  0x08196030 in ?? ()
#5  0xafad6384 in ?? ()
#6  0x in ?? ()

Thread 12 (Thread -1339196496 (LWP 5695)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76f8eec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb733d5dc in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x0828b438 in ?? ()
#4  0x08196030 in ?? ()
#5  0xb02d7384 in ?? ()
#6  0x in ?? ()

Thread 11 (Thread -1330803792 (LWP 5694)):
#0  0xe410 in __kernel_vsyscall ()
---Type return to continue, or q return to quit---
#1  0xb76f8eec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb733d5dc in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x0828b438 in ?? ()
#4  0x08196030 in ?? ()
#5  0xb0ad8384 in ?? ()
#6  0x in ?? ()

Thread 10 (Thread -1322411088 (LWP 5693)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76fb56b in __read_nocancel () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb6dd7110 in ?? () from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#3  0x001c in ?? ()
#4  0x08484800 in ?? ()
#5  0x2000 in ?? ()
#6  0xb7992eec in ?? () from /usr/lib/libgnomevfs-2.so.0
#7  0x0845c198 in ?? ()
#8  0x in ?? ()

Thread 9 (Thread -1314018384 (LWP 5692)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76f8eec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
---Type return to continue, or q return to quit---
#2  0xb733d5dc in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x0828b438 in ?? ()
#4  0x08196030 in ?? ()
#5  0xb1ada384 in ?? ()
#6  0xb76abd4a in g_static_rec_mutex_lock () from /usr/lib/libglib-2.0.so.0
#7  0xb767ad8c in g_async_queue_push_sorted () from /usr/lib/libglib-2.0.so.0
#8  0xb76ae4ce in g_thread_pool_free () from /usr/lib/libglib-2.0.so.0
#9  0xb76ac5a2 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#10 0xb76f6341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0xb74f04ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 8 (Thread -1305625680 (LWP 5691)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76f8eec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb733d5dc in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x0828b438 in ?? ()
#4  0x08196030 in ?? ()
#5  0xb22db384 in ?? ()
#6  0xb7697eec in g_free () from /usr/lib/libglib-2.0.so.0
#7  0xb767ad8c in g_async_queue_push_sorted () from /usr/lib/libglib-2.0.so.0
#8  0xb76ae4ce in g_thread_pool_free () from /usr/lib/libglib-2.0.so.0
#9  0xb76ac5a2 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
---Type return to continue, or q return to quit---
#10 0xb76f6341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0xb74f04ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 7 (Thread -1297232976 (LWP 5690)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76f8eec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb733d5dc in ?? () from /usr/lib/libgthread-2.0.so.0
#3  0x0828b438 in ?? ()
#4  0x08196030 in ?? ()
#5  0xb2adc384 in ?? ()
#6  0xb7697eec in g_free () from /usr/lib/libglib-2.0.so.0
#7  0xb767ad8c in g_async_queue_push_sorted () from /usr/lib/libglib-2.0.so.0
#8  0xb76ae4ce in g_thread_pool_free () from /usr/lib/libglib-2.0.so.0
#9  0xb76ac5a2 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#10 0xb76f6341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#11 0xb74f04ee in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 6 (Thread -1288840272 (LWP 5689)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb76f8eec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb733d5dc in ?? () from /usr/lib/libgthread-2.0.so.0
---Type return to continue, or q return to quit---
#3  0x0828b438 in ?? ()
#4  0x08196030 in ?? ()
#5  0xb32dd384 in ?? ()
#6  0xb7697eec in g_free () from /usr/lib/libglib-2.0.so.0
#7  0xb767ad8c in g_async_queue_push_sorted () from /usr/lib/libglib-2.0.so.0
#8  0xb76ae4ce in g_thread_pool_free () from /usr/lib/libglib-2.0.so.0
#9  0xb76ac5a2 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#10 0xb76f6341 in start_thread () from 

Re: [Bug 66597] Re: EDGY nautilus crash when GNOME starts

2006-10-18 Thread Sebastien Bacher
Le mardi 17 octobre 2006 à 23:11 +, Ron O a écrit :
 when you told me to do gnome-session-remove nautilus , it dosnt do
 anything, it just..its blank

it's to prevent nautilus restarting again if it's running with the
session, which seems to not be the case so running gdb directly is fine

-- 
EDGY nautilus crash when GNOME starts
https://launchpad.net/bugs/66597

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 66597] Re: EDGY nautilus crash when GNOME starts

2006-10-17 Thread Sebastien Bacher
Thanks for your bug. Could you get a backtrace with nautilus-dbg and 
libgtk2.0-0-dbg installed?
From a command line:
- gnome-session-remove nautilus
- gdb nautilus
(gdb) run
... crash
(gdb) thread apply all bt

Copy that and the messages you get on the command line to a comment

** Changed in: nautilus (Ubuntu)
 Assignee: (unassigned) = Ubuntu Desktop Bugs
   Status: Unconfirmed = Needs Info

-- 
EDGY nautilus crash when GNOME starts
https://launchpad.net/bugs/66597

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 66597] Re: EDGY nautilus crash when GNOME starts

2006-10-17 Thread Ron O
[EMAIL PROTECTED]:~$ gnome-session-remove nautilus
(this just hangs there, i just ctrl c it)



[EMAIL PROTECTED]:~$ gdb nautilus
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as i486-linux-gnu...(no debugging symbols found)
Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.

(gdb) run
Starting program: /usr/bin/nautilus
(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)
---Type return to continue, or q return to quit---
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1225770336 (LWP 6508)]
(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)
---Type return to continue, or q return to quit---
(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)
---Type return to continue, or q return to quit---
(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)
[New Thread -1227244640 (LWP 6515)]



Program received signal SIGINT, Interrupt.
[Switching to Thread -1225770336 (LWP 6508)]
0xe410 in __kernel_vsyscall ()
(gdb) thread apply all bt

Thread 2 (Thread -1227244640 (LWP 6515)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb750f803 in poll () from /lib/tls/i686/cmov/libc.so.6
#2  0xb76c6813 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#3  0xb76c6b89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#4  0xb77b57e0 in link_set_io_thread () from /usr/lib/libORBit-2.so.0
#5  0xb76e138f in g_thread_create_full () from /usr/lib/libglib-2.0.so.0
#6  0xb772f504 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb751951e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread -1225770336 (LWP 6508)):
#0  0xe410 in __kernel_vsyscall ()
#1  0xb7732816 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb77988e9 in giop_recv_buffer_get () from /usr/lib/libORBit-2.so.0
#3  0xb779d33d in ORBit_small_invoke_stub () from /usr/lib/libORBit-2.so.0
#4  0xb779d53e in ORBit_small_invoke_stub_n () from
/usr/lib/libORBit-2.so.0
#5  0xb77a9d32 in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
#6  0xb77d681a in Bonobo_ActivationContext_activateMatchingFull ()
   from /usr/lib/libbonobo-activation.so.4
#7  0xb77d9139 in bonobo_activation_activate ()
   from /usr/lib/libbonobo-activation.so.4
---Type return to continue, or q return to quit---
#8  0xb77d9390 in bonobo_activation_activate_from_id ()
   from /usr/lib/libbonobo-activation.so.4
#9  0x08069f89 in 

[Bug 66597] Re: EDGY nautilus crash when GNOME starts

2006-10-17 Thread Sebastien Bacher
Program received signal SIGINT, Interrupt., that doesn't look like a
crash, rather stopped by user action. Are you sure it crashed?

-- 
EDGY nautilus crash when GNOME starts
https://launchpad.net/bugs/66597

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 66597] Re: EDGY nautilus crash when GNOME starts

2006-10-17 Thread Ron O
On Tue, 17 Oct 2006 16:39:06 -0400, Sebastien Bacher [EMAIL PROTECTED]  
wrote:

 Program received signal SIGINT, Interrupt., that doesn't look like a
 crash, rather stopped by user action. Are you sure it crashed?


I thought i noted that i did that, since it wouldnt go? As soon as gnome  
loads, nautilus error box comes up.

-- 
EDGY nautilus crash when GNOME starts
https://launchpad.net/bugs/66597

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 66597] Re: EDGY nautilus crash when GNOME starts

2006-10-17 Thread Sebastien Bacher
what doy you mean wouldn't go? gdb will catch the crash instead of
bug-buddy and you can get the backtrace as described before

-- 
EDGY nautilus crash when GNOME starts
https://launchpad.net/bugs/66597

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 66597] Re: EDGY nautilus crash when GNOME starts

2006-10-17 Thread Ron O
when you told me to do gnome-session-remove nautilus , it dosnt do
anything, it just..its blank

-- 
EDGY nautilus crash when GNOME starts
https://launchpad.net/bugs/66597

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs