Activity log for bug #331891

Date Who What changed Old value New value Message
2009-02-20 03:48:05 derbeyer bug added bug
2009-02-20 03:48:05 derbeyer bug added attachment 'Dependencies.txt' (Dependencies.txt)
2009-02-20 03:48:05 derbeyer bug added attachment 'DpkgTerminalLog.txt' (DpkgTerminalLog.txt)
2009-02-20 14:24:15 Jamie Strandboge who_made_private derbeyer-yo
2009-02-22 14:50:34 Marcus Asshauer gconf: status New Incomplete
2009-02-22 14:50:34 Marcus Asshauer gconf: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks!
2009-03-09 21:20:52 Sebastien Bacher gconf: status Incomplete Invalid
2009-03-09 21:20:52 Sebastien Bacher gconf: importance Undecided Medium
2009-03-09 21:20:52 Sebastien Bacher gconf: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.