Is anybody else bothered by the latest BZ changes? Where does one select the Fedora release to limit search results to? And how does one figure out where to select kernel or dracut? Those scroll lists are much too difficult to find anything in, overscrolling nearly always except doing one line at a time, which would take an eternity to locate anything not starting with z or a.
I'm trying to figure out if anyone else has filed a bug that dracut builds F21 32 bit Athlon/VIA chipset initrds without any storage driver (pata_via needed) sometime after kernel 4.1.4 was replaced with whatever came next. 4.1.4 works, but 4.1.7 produces emergency shell for failure to find root device whether root=LABEL= or root=devname or root=UUID= on cmdline. Also, rebooting attemps from the emergency shell utterly fail, and this after taking more than 3 minutes just to reach the emergency shell after selecting a Grub stanza.
Dne 1.10.2015 v 09:38 Felix Miata napsal(a):
Is anybody else bothered by the latest BZ changes? Where does one select the Fedora release to limit search results to? And how does one figure out where to select kernel or dracut? Those scroll lists are much too difficult to find anything in, overscrolling nearly always except doing one line at a time, which would take an eternity to locate anything not starting with z or a.
I'm trying to figure out if anyone else has filed a bug that dracut builds F21 32 bit Athlon/VIA chipset initrds without any storage driver (pata_via needed) sometime after kernel 4.1.4 was replaced with whatever came next. 4.1.4 works, but 4.1.7 produces emergency shell for failure to find root device whether root=LABEL= or root=devname or root=UUID= on cmdline. Also, rebooting attemps from the emergency shell utterly fail, and this after taking more than 3 minutes just to reach the emergency shell after selecting a Grub stanza.
Does http://bugz.fedoraproject.org/dracut work for you?
Vít
Vít Ondruch composed on 2015-10-01 04:22 (UTC-0400):
Does http://bugz.fedoraproject.org/dracut work for you?
Marginally better than nothing:
doesn't any kind of list in SeaMonkey (maybe because of noscript?) tiny gray (painful) text no way to choose sort order no way to say only bugs newer than specified date
Nothing found in that list on point I was looking for.
Dne 1.10.2015 v 10:53 Felix Miata napsal(a):
Vít Ondruch composed on 2015-10-01 04:22 (UTC-0400):
Does http://bugz.fedoraproject.org/dracut work for you?
Marginally better than nothing:
doesn't any kind of list in SeaMonkey (maybe because of noscript?) tiny gray (painful) text no way to choose sort order no way to say only bugs newer than specified date
Nothing found in that list on point I was looking for.
You can follow the "open bugs" link, which redirects to BZ and then "Edit search as you wish"
Vít
On Thu, 2015-10-01 at 04:53 -0400, Felix Miata wrote:
doesn't any kind of list in SeaMonkey (maybe because of noscript?)
Yeah, the fact is that NoScript is incompatible with the Internet... probably that's not how the web should be, but it is how it is....
For those of us not blocking the scripts, the Bugzilla upgrade is a huge improvement. Those gigantic combo boxes were horrible to use; typeahead find is way nicer. I smile each time I use it; eventually I will get used to it, but for now, being able to easily move bugs between components for the first time is still a huge deal to me. Maybe you could whitelist RH Bugzilla? I think I trust Red Hat not to collect data on me for behavioral advertising, or mine Bitcoin on my computer, or use my computer to DoS Oracle....
Michael
On 10/01/2015 09:38 AM, Felix Miata wrote:
Is anybody else bothered by the latest BZ changes? Where does one select the Fedora release to limit search results to?
Under Custom Search:
https://bugzilla.redhat.com/buglist.cgi?classification=Fedora&component=...
And how does one figure out where to select kernel or dracut?
You type “dra” in the component field and select it from the drop-down list. (You need to enable Javascript for this to work.)
Is anybody else bothered by the latest BZ changes? Where does one select the Fedora release to limit search results to? And how does one figure out where to select kernel or dracut? Those scroll lists are much too difficult to find anything in, overscrolling nearly always except doing one line at a time, which would take an eternity to locate anything not starting with z or a.
I'm trying to figure out if anyone else has filed a bug that dracut builds F21 32 bit Athlon/VIA chipset initrds without any storage driver (pata_via needed) sometime after kernel 4.1.4 was replaced with whatever came next. 4.1.4 works, but 4.1.7 produces emergency shell for failure to find root device whether root=LABEL= or root=devname or root=UUID= on cmdline. Also, rebooting attemps from the emergency shell utterly fail, and this after taking more than 3 minutes just to reach the emergency shell after selecting a Grub stanza.
I too noticed the advanced search to be severely broken or at least confusing. Under the Component field it tells you to "Click to list all components" but what exactly are you supposed to click? At the time I tried, typing in the Component field did not get me a reduced list like it did before so I eventually had to use a simple search and the sort by the component column. Now however it appears that entering text into the Component field does cause a list to appear for those that match. I still think the "Click to.." message is confusing. Some of my confusion may just be due to the incredibly slow response time, Now I've played again with it a bit and Firefox is reporting that the script has become unresponsive.
It certainly doesn't seem very usable to me. I didn't file a bug on BZ because I wasn't sure where exactly one does that.
-- John Florian
On 10/01/2015 02:07 PM, John Florian wrote:
Is anybody else bothered by the latest BZ changes? Where does one select the Fedora release to limit search results to? And how does one figure out where to select kernel or dracut? Those scroll lists are much too difficult to find anything in, overscrolling nearly always except doing one line at a time, which would take an eternity to locate anything not starting with z or a.
I'm trying to figure out if anyone else has filed a bug that dracut builds F21 32 bit Athlon/VIA chipset initrds without any storage driver (pata_via needed) sometime after kernel 4.1.4 was replaced with whatever came next. 4.1.4 works, but 4.1.7 produces emergency shell for failure to find root device whether root=LABEL= or root=devname or root=UUID= on cmdline. Also, rebooting attemps from the emergency shell utterly fail, and this after taking more than 3 minutes just to reach the emergency shell after selecting a Grub stanza.
I too noticed the advanced search to be severely broken or at least confusing. Under the Component field it tells you to "Click to list all components" but what exactly are you supposed to click? At the time I tried, typing in the Component field did not get me a reduced list like it did before so I eventually had to use a simple search and the sort by the component column. Now however it appears that entering text into the Component field does cause a list to appear for those that match. I still think the "Click to.." message is confusing. Some of my confusion may just be due to the incredibly slow response time, Now I've played again with it a bit and Firefox is reporting that the script has become unresponsive.
For me I can click on that an I see "Working" then eventually a list appears. But it's slow as you might expect for bringing up so many components.
-
Felix Miata -
Florian Weimer -
John Florian -
Michael Catanzaro -
Orion Poplawski -
Vít Ondruch