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
--
(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 -1251886
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 th
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
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,
Tu
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
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
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/li
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
"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/mailm
[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
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: na
12 matches
Mail list logo
