same problems in Herd 2 as in Herd 1
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I am getting exactly the same problems when attempting to install from the DESKTOP version of Feisty herd 2 that I observed in herd 1.
Here is a list.
1) When booting from the DESKTOP (live) CD (also observe same thing once the O/S is installed to the hard drive), I get 2 row of blue dots, etc. running horizonally across the screen when the boot up scroll bar get to about half the way across from left to right and just before it is ready to proceed into the next part of the boot sequence. I also get this same thing if I attempt safe video mode.
2) Once I get the DESKTOP (live) CD booted to the desktop and start the installation process to the hard drive, when I get to the partitioning portion, if I choose to save the partitioning information (as opposed to choosing the close button), the partitioning will lock up and will not proceed unless I hit the X button at top right of diagonal and then choose to cancel the save partition information process. If I initially just choose the close button the partitioning will proceed. Please note that this is a manual partitioning.
3) When I get to the screen where I am supposed to fill in the user name, password, etc. the screen has a blank/black section at the bottom of the screen about 2 inches high and runs across the entirety of the bottom of the screen from left to right side. I have to pull the diagonal up the screen in order to see the buttons once I had filled out the information/
4) Also, during the process of attempting to install the O/S to the hard drive, I notice that there are 2 blue horizontal shaped boxes present in the PANEL. One is located about where the word "applications" is and ends at about where the word "System" is. And the other one is over on the panel about 3 inches from the first one and is slightly shorter than the first one.
5) Once I get the O/S installed to the hard drive, I can not sucessfully get into the login window function under system/
6) When I attempt to download and install the available updates as shown by the amber * on the panel bar, I am told to do a distribution updates, but when I click on the button that is shown to do the distribution update, it gives a message that says that it can not do this.
I would like to help with the testing of Feisty, BUT I can not understand why all of these very same problems that I have report previously from herd 1 are still present on the herd 2 release.
Thanks.
| Andrew Ash (ash211) wrote | #1 |
| Brian Murray (brian-murray) wrote | #2 |
Which, if any, of these bugs are regressions from Edgy?
1) Graphics corruption is usually related to hardware. Could you please provide some information about your hardware?
2) There is currently a major bug in the partitioning, bug 76796, though I think that bug may be related to automatic partitioning, and therefore not relevant to you.
3) That seems to be a bug in gdm. Could you please check for another bug to add information to at https:/
4) A screenshot would be very useful here. If you could please attach one, that would be great. That would also help out for #3 too.
5) I'm not sure where to point you on this one.
6) There is currently massive breakage in the feisty repos because of porting python 2.4->2.5 I wouldn't recommend upgrading until this becomes less of a problem. You can monitor the situation at irc.freenode.net #ubuntu+1 , specifically the channel message.
I'm sorry there hasn't been much improvement in this area for you. The transition from herd 1 to herd 2 is more about getting the new features into the repos than the bugfixing aspect of the release. Unfortunately, there are just not enough developers to do both! Bug reports such as yours ARE valued, so please continue filing them.
One thing that may get these fixed faster is to file each bug individually. It's rather difficult to work with multibug reports such as this one just because of the way bugtracking systems are set up. Each bug is assigned a package it affects, and importance/status information. But when there are multiple independent problems, it becomes difficult to make use of these fields for the bug.
I would recommend that you check each of these bugs individually and then file them separately. That would help the developers out immensely. Thanks!
PS-please make sure to follow up on bugs once you file them. Check bug 67274! I would recommend registering your email address with launchpad so you can be notified of updates to bugs.