[Bug 362409] Re: nautilus crashed with SIGSEGV in __libc_start_main()

2010-03-22 Thread Sebastien Bacher
could you open a new bug if you still get the issue? ** Changed in: nautilus (Ubuntu) Status: In Progress = Fix Released -- nautilus crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/362409 You received this bug notification because you are a member of Ubuntu

[Bug 362409] Re: nautilus crashed with SIGSEGV in __libc_start_main()

2010-03-20 Thread ar57
** Changed in: nautilus (Ubuntu) Status: Fix Released = Fix Committed ** Changed in: nautilus (Ubuntu) Status: Fix Committed = In Progress -- nautilus crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/362409 You received this bug notification because you

[Bug 362409] Re: nautilus crashed with SIGSEGV in __libc_start_main()

2010-03-20 Thread Dave H
Just upgraded from Karmic to Lucid. Happened on first reboot, this is the 2nd time on the 3rd reboot. Gnome Desktop didn't come up on the 2nd reboot, had to do a recovery repair. Lenovo S10e Netbook -- nautilus crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/362409

Re: [Bug 362409] Re: nautilus crashed with SIGSEGV in __libc_start_main()

2009-05-14 Thread Frits van Dee
i do not get this bug anymore. 2009/5/13 Sebastien Bacher seb...@ubuntu.com do you still get the bug in jaunty? -- nautilus crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/362409 You received this bug notification because you are a direct subscriber of the bug.

[Bug 362409] Re: nautilus crashed with SIGSEGV in __libc_start_main()

2009-05-13 Thread Sebastien Bacher
do you still get the bug in jaunty? -- nautilus crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/362409 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list

Re: [Bug 362409] Re: nautilus crashed with SIGSEGV in __libc_start_main()

2009-05-13 Thread Shantanu
nope.. it seems to work fine now.. 2009/5/13 Sebastien Bacher seb...@ubuntu.com do you still get the bug in jaunty? -- nautilus crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/362409 You received this bug notification because you are a direct subscriber of the

[Bug 362409] Re: nautilus crashed with SIGSEGV in __libc_start_main()

2009-05-13 Thread Sebastien Bacher
closing since that works correctly now ** Changed in: nautilus (Ubuntu) Status: Incomplete = Fix Released -- nautilus crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/362409 You received this bug notification because you are a member of Ubuntu Desktop Bugs,

Re: [Bug 362409] Re: nautilus crashed with SIGSEGV in __libc_start_main()

2009-05-13 Thread uschaibl
Am Mittwoch, den 13.05.2009, 09:48 + schrieb Sebastien Bacher: do you still get the bug in jaunty? Hello, I had this bug after upgrading from Intrepid. So I made a fresh install of Jaunty. Now it works perfect. Greetings Uwe -- nautilus crashed with SIGSEGV in __libc_start_main()

[Bug 362409] Re: nautilus crashed with SIGSEGV in __libc_start_main()

2009-04-18 Thread Kether2
the same problem happened right now, after the update. -- nautilus crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/362409 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list

[Bug 362409] Re: nautilus crashed with SIGSEGV in __libc_start_main()

2009-04-17 Thread Stuart Brown
Problem occured on the first clean boot after the most recent (0857 British Summer Time, 17 April 2009) set of distribution updates. As far as I can see, it is purely a function of the updates. -- nautilus crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/362409 You

[Bug 362409] Re: nautilus crashed with SIGSEGV in __libc_start_main()

2009-04-16 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Visibility changed to: