it got closed because it has been incomplete and waiting for a debug
stacktrace for weeks, you can reopen if you provide one, the apport one
is useless since it has not debug information
** Changed in: glib2.0 (Ubuntu)
Status: New => Invalid
--
MCC Segmentation Fault
https://bugs.launchpa
um there is a backtrace attached? Why did this bug get closed?
** Changed in: glib2.0 (Ubuntu)
Status: Invalid => New
--
MCC Segmentation Fault
https://bugs.launchpad.net/bugs/273159
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assign
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 t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mythbuntu-control-centre (Ubuntu)
Status: New => Won't Fix
--
MCC Segmentation Fault
https://bugs.launchpad.net/bugs/273159
You received this bug notification because you are a member of Ubuntu
De
