Today's 64 bit rsync pxeboot install fails right after entering the root password. The message is: An error occurred attempting to load an installation interface component
className = PartitionTypeWindow
On Thu, 2009-04-09 at 16:24 -0700, Chuck Forsberg WA7KGX N2469R wrote:
Today's 64 bit rsync pxeboot install fails right after entering the root password. The message is: An error occurred attempting to load an installation interface component
className = PartitionTypeWindow
This is not bugzilla.
Your issue is known and fixed already.
On Thu, Apr 9, 2009 at 6:42 PM, Jesse Keating jkeating@redhat.com wrote:
On Thu, 2009-04-09 at 16:24 -0700, Chuck Forsberg WA7KGX N2469R wrote:
Today's 64 bit rsync pxeboot install fails right after entering the root password. The message is: An error occurred attempting to load an installation interface component
className = PartitionTypeWindow
This is not bugzilla.
Nor is bugzilla the fedora-test maillist. People are different, therefore so is their workflow. I think people on this list should be more accepting of this fact, especially since reading of fedora-test is advised early in the rawhide test process: http://fedoraproject.org/wiki/Releases/Rawhide#Testing_Rawhide
Your issue is known and fixed already.
Thanks for the info - you and a few select others on the planet actually knew that.
jerry
Jerry Amundson wrote:
On Thu, Apr 9, 2009 at 6:42 PM, Jesse Keating jkeating@redhat.com wrote:
On Thu, 2009-04-09 at 16:24 -0700, Chuck Forsberg WA7KGX N2469R wrote:
Today's 64 bit rsync pxeboot install fails right after entering the root password. The message is: An error occurred attempting to load an installation interface component
className = PartitionTypeWindow
This is not bugzilla.
Nor is bugzilla the fedora-test maillist. People are different, therefore so is their workflow. I think people on this list should be more accepting of this fact, especially since reading of fedora-test is advised early in the rawhide test process: http://fedoraproject.org/wiki/Releases/Rawhide#Testing_Rawhide
"First, read the fedora-test-list mailing list, where Rawhide users discuss the latest changes. You'll find discussion of significant changes and warnings of severe breakages here. Reading test-list daily is key to staying on top of Rawhide. Secondly, report all the bugs you find in Rawhide to Bugzilla. Remember to file bugs according to these best practices. Please remember that bugs should always be filed in Bugzilla. Reporting bugs on the mailing list or IRC is not sufficient, as these reports rapidly become lost in history."
Bugzilla really and truly is the place to report bugs. Anywhere else stands a much greater chance of getting lost.
-Eric
On Thu, Apr 9, 2009 at 7:59 PM, Eric Sandeen sandeen@redhat.com wrote:
Jerry Amundson wrote:
On Thu, Apr 9, 2009 at 6:42 PM, Jesse Keating jkeating@redhat.com wrote:
On Thu, 2009-04-09 at 16:24 -0700, Chuck Forsberg WA7KGX N2469R wrote:
Today's 64 bit rsync pxeboot install fails right after entering the root password. The message is: An error occurred attempting to load an installation interface component
className = PartitionTypeWindow
This is not bugzilla.
Nor is bugzilla the fedora-test maillist. People are different, therefore so is their workflow. I think people on this list should be more accepting of this fact, especially since reading of fedora-test is advised early in the rawhide test process: http://fedoraproject.org/wiki/Releases/Rawhide#Testing_Rawhide
"First, read the fedora-test-list mailing list, where Rawhide users discuss the latest changes. You'll find discussion of significant changes and warnings of severe breakages here. Reading test-list daily is key to staying on top of Rawhide. Secondly, report all the bugs you find in Rawhide to Bugzilla. Remember to file bugs according to these best practices. Please remember that bugs should always be filed in Bugzilla. Reporting bugs on the mailing list or IRC is not sufficient, as these reports rapidly become lost in history."
Bugzilla really and truly is the place to report bugs. Anywhere else stands a much greater chance of getting lost.
True, but my point is we should have more respect for the personal lives of everyone giving time here, and in all open source projects. In fact, were it up to me, the wording of the above snippet would be changed. But it's not, so it won't. (don't bother to give me the its-a-wiki-change-it crap)
I also find it ironic that this thread immediately invokes defensive, borderline demanding, responses from two @redhat.com addresses.
The greatest efficiency is for shit to work the first time. When it doesn't, we're here to help, but don't expect it to be more than what each person is capable of contributing.
jerry
Jerry Amundson wrote:
On Thu, Apr 9, 2009 at 7:59 PM, Eric Sandeen sandeen@redhat.com wrote:
Jerry Amundson wrote:
...
Bugzilla really and truly is the place to report bugs. Anywhere else stands a much greater chance of getting lost.
True, but my point is we should have more respect for the personal lives of everyone giving time here, and in all open source projects. In fact, were it up to me, the wording of the above snippet would be changed. But it's not, so it won't. (don't bother to give me the its-a-wiki-change-it crap)
I also find it ironic that this thread immediately invokes defensive, borderline demanding, responses from two @redhat.com addresses.
I'm sorry you took it that way from me; I hoped to clarify the documented best practices for bug reporting.
The greatest efficiency is for shit to work the first time. When it doesn't, we're here to help, but don't expect it to be more than what each person is capable of contributing.
And I'm here to help too - but on the flipside, don't expect developers who can help resolve these issues to constantly be scanning lists like this for bug reports, when bugzilla is the documented best place for them.
Thanks, -Eric
Eric Sandeen wrote:
Jerry Amundson wrote:
On Thu, Apr 9, 2009 at 6:42 PM, Jesse Keating jkeating@redhat.com wrote:
On Thu, 2009-04-09 at 16:24 -0700, Chuck Forsberg WA7KGX N2469R wrote:
Today's 64 bit rsync pxeboot install fails right after entering the root password. The message is: An error occurred attempting to load an installation interface component
className = PartitionTypeWindow
This is not bugzilla.
Nor is bugzilla the fedora-test maillist. People are different, therefore so is their workflow. I think people on this list should be more accepting of this fact, especially since reading of fedora-test is advised early in the rawhide test process: http://fedoraproject.org/wiki/Releases/Rawhide#Testing_Rawhide
"First, read the fedora-test-list mailing list, where Rawhide users discuss the latest changes. You'll find discussion of significant changes and warnings of severe breakages here. Reading test-list daily is key to staying on top of Rawhide. Secondly, report all the bugs you find in Rawhide to Bugzilla. Remember to file bugs according to these best practices. Please remember that bugs should always be filed in Bugzilla. Reporting bugs on the mailing list or IRC is not sufficient, as these reports rapidly become lost in history."
Bugzilla really and truly is the place to report bugs. Anywhere else stands a much greater chance of getting lost.
-Eric
but surely a quick email to this list to check if it's been fixed is ok before going through the convoluted bugzilla process? as like in this case a bugzilla would have been pointless?
phil
On Fri, 2009-04-10 at 10:16 +0100, psmith wrote:
but surely a quick email to this list to check if it's been fixed is ok before going through the convoluted bugzilla process? as like in this case a bugzilla would have been pointless?
Bugzilla wouldn't have been. First step is to search for an existing bug. If not found, and you file one, then future people running into this problem will find yours and find the relevant information.
https://bugz.fedoraproject.org makes it easy to look at existing bugs for a given component to quickly scan for a bug that matches what you're seeing. It's better to have dupes filed than to have none filed at all.
Jesse Keating jkeating@redhat.com writes:
https://bugz.fedoraproject.org makes it easy to look at existing bugs for a given component to quickly scan for a bug that matches what you're seeing. It's better to have dupes filed than to have none filed at all.
cool ... but I went to that site and got just a generic Fedora welcome page (not to mention a browser complaint about an invalid certificate). Where's the search functionality hiding exactly?
regards, tom lane
On Fri, 2009-04-10 at 11:03 -0400, Tom Lane wrote:
Jesse Keating jkeating@redhat.com writes:
https://bugz.fedoraproject.org makes it easy to look at existing bugs for a given component to quickly scan for a bug that matches what you're seeing. It's better to have dupes filed than to have none filed at all.
cool ... but I went to that site and got just a generic Fedora welcome page (not to mention a browser complaint about an invalid certificate). Where's the search functionality hiding exactly?
regards, tom lane
Oops, looks like there isn't a landing page with that URL. If you slap on a package name you'll get a bug list, eg:
http://bugz.fedoraproject.org/mysql
I accidentially added an https there, but it looks like the redirect goes to:
https://admin.fedoraproject.org/pkgdb/packages/bugs/mysql
On Fri, 2009-04-10 at 10:34 +0100, Frank Murphy (Frankly3D) wrote:
Not apparently for the OP.
Is there a "closed" bugzilla, ref. that can be checked?
No, apparently nobody filed the bug.
Jesse Keating wrote:
On Fri, 2009-04-10 at 10:34 +0100, Frank Murphy (Frankly3D) wrote:
Not apparently for the OP.
Is there a "closed" bugzilla, ref. that can be checked?
No, apparently nobody filed the bug.
then how was it fixed? someone obviously found it before they were able to fix it, and they didn't file a bug either.
phil