[Bug 945378] Re: nautilus crashed with SIGSEGV in _IO_vfprintf_internal()

2012-03-08 Thread Sebastien Bacher
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945378 Title: nautilus crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: h

[Bug 945378] Re: nautilus crashed with SIGSEGV in _IO_vfprintf_internal()

2012-03-12 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. ** Changed in: nautilus (Ubuntu)

[Bug 945378] Re: nautilus crashed with SIGSEGV in _IO_vfprintf_internal()

2012-05-11 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/9453

[Bug 945378] Re: nautilus crashed with SIGSEGV in _IO_vfprintf_internal()

2012-05-12 Thread Benjamin
I have now publish my Bug 946598. It's still avalable in Ubuntu, if I switch between different desktops. LXDE <> Unity3d ** Changed in: nautilus (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubun

[Bug 945378] Re: nautilus crashed with SIGSEGV in _IO_vfprintf_internal()

2018-03-17 Thread Sebastien Bacher
there has been no such issue reported in years, assuming it doesn't exist in the current version of the code and closing ** Changed in: nautilus (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubun