[Bug 922010] Re: gedit crashed with SIGABRT in __libc_message()

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

[Bug 922010] Re: gedit crashed with SIGABRT in __libc_message()

2012-02-02 Thread David Henningsson
I don't remember exactly. I'll let you know next time it happens. ** Changed in: gedit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/922010

[Bug 922010] Re: gedit crashed with SIGABRT in __libc_message()

2012-02-02 Thread Sebastien Bacher
does it happen when using the fileselector then? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/922010 Title: gedit crashed with SIGABRT in __libc_message() To manage notifications

[Bug 922010] Re: gedit crashed with SIGABRT in __libc_message()

2012-02-02 Thread David Henningsson
I've seen it happen a few times, and it seems to happen when you open files, but it's not reproducible. ** Changed in: gedit (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. ht

[Bug 922010] Re: gedit crashed with SIGABRT in __libc_message()

2012-02-01 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: Public ** Cha