[Bug 184053] Re: brasero crashed with SIGSEGV

2010-09-16 Thread Bug Watch Updater
** Changed in: brasero Status: Invalid = Expired ** Changed in: brasero Importance: Unknown = Critical -- brasero crashed with SIGSEGV https://bugs.launchpad.net/bugs/184053 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee.

[Bug 184053] Re: brasero crashed with SIGSEGV

2008-07-15 Thread Sebastien Bacher
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on

[Bug 184053] Re: brasero crashed with SIGSEGV

2008-06-30 Thread Pedro Villavicencio
ping? any response on this? upstream bug was closed because the lack of information, if there's no response here in a few weeks i'm going to close this too, thanks. ** Changed in: brasero (Ubuntu) Status: Triaged = Incomplete -- brasero crashed with SIGSEGV

[Bug 184053] Re: brasero crashed with SIGSEGV

2008-06-28 Thread Bug Watch Updater
** Changed in: brasero Status: Incomplete = Invalid -- brasero crashed with SIGSEGV https://bugs.launchpad.net/bugs/184053 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list

[Bug 184053] Re: brasero crashed with SIGSEGV

2008-04-28 Thread Bug Watch Updater
** Changed in: brasero Status: Unknown = Incomplete -- brasero crashed with SIGSEGV https://bugs.launchpad.net/bugs/184053 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list

[Bug 184053] Re: brasero crashed with SIGSEGV

2008-04-11 Thread Pedro Villavicencio
known upstream you can track it here: http://bugzilla.gnome.org/show_bug.cgi?id=524375 also a comment from upstream: Can you please explain the steps to crash brasero ? And please try brasero 0.7.1 maybe this bug is already fixed can you test the same with 0.7.1 and confirm that's fixed there?