On Sunday 19 April 2009 12:54:00 pm Dimitrios Symeonidis wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. You reported this bug a while ago and there hasn't been > any activity in it recently. We were wondering if this is still an issue > for you. Can you try with the latest Ubuntu release? Thanks in advance. > > ** Visibility changed to: Public > > ** Changed in: vbetool (Ubuntu) > Status: New => Incomplete I don't have any negative to report. I am not as experienced as I should be using a beta, but I am, because of the components in my computer. It is quite an advanced MB and a AMD Quad, which is not that remarkable anymore. I couldn't even get a screen with Intrepid and changed to Jaunty as a result.
I report all bugs with the information my computer compiles. I do not always understand what has happened and cannot comment. But in case I did not give enough system information with the report I made, I am currently using KDE 4.2.2, Jaunty Beta, 9600 AMD Quad Core, 8gb SDRAM ECC, 9600 nvidia Gforce w/512mb DDR3, 800W BFG Power Supply, ASUS M3N-HT Mempipe Motherboard with nvidia 780a chip. I use the on-board 8.1 sound. I don't even know if any of this information is important, however, on the Kubuntu Users List, I recently read a post indicating lacking information on a bug report. Is it better if I include all this information, or what is preferred. Also, since I am so inexperienced, would you rather I not make reports, or are they helpful? I really want to help and will contribute more as I learn. Steven -- vbetool crashed with signal 5 https://bugs.launchpad.net/bugs/192101 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
