According to what is stated in upstream bug, brasero handles /tmp use
differently now, which basically means that this bug report can be
resolved / closed.
Is this the right way to deal with this ? Shall we close this bug report
according to what upstream did ?
Thanks.
--
You received this bug
** Changed in: brasero
Importance: Unknown => Low
--
Brasero gives confusing message ("No space left on resource") when device
containing /tmp is full
https://bugs.launchpad.net/bugs/359835
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Changed in: brasero
Status: Incomplete => Fix Released
--
Brasero gives confusing message ("No space left on resource") when device
containing /tmp is full
https://bugs.launchpad.net/bugs/359835
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Changed in: brasero
Status: New => Incomplete
--
Brasero gives confusing message ("No space left on resource") when device
containing /tmp is full
https://bugs.launchpad.net/bugs/359835
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Changed in: brasero
Status: Unknown => New
--
Brasero gives confusing message ("No space left on resource") when device
containing /tmp is full
https://bugs.launchpad.net/bugs/359835
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Thanks for reporting. I'm forwarding this issue upstream.
** Changed in: brasero (Ubuntu)
Importance: Undecided => Low
** Changed in: brasero (Ubuntu)
Status: New => Triaged
** Bug watch added: GNOME Bug Tracker #578733
http://bugzilla.gnome.org/show_bug.cgi?id=578733
** Also affec
