RFC: Multipath testing as a (optional?) criteria for RC?
by Phil Knirsch
Hi guys.
I'd like to open up the discussion about getting multipath testing as a
(optional) criteria for RC.
I understand that the typical Fedora user most likely will never
encounter or use multipath, but as we do have server users for Fedora
there might be some merit to it.
We've ran into this on the ppc64 side the last few releases where we did
test this during our alpha, beta and rc checks and worked with the
respective maintainers to fix the issues we found.
So if there is an interest to make this a general test case we'd
certainly be able to provide a QE template with all the necessary steps.
And as mentioned, even if it's not going to be a blocking criteria maybe
having it as included as an optional test case might still be worth it.
Let me know what you guys think.
Thanks & regards, Phil
--
Philipp Knirsch | Tel.: +49-711-96437-470
Manager Core Services | Fax.: +49-711-96437-111
Red Hat GmbH | Email: Phil Knirsch <pknirsch(a)redhat.com>
Wankelstrasse 5 | Web: http://www.redhat.com/
D-70563 Stuttgart, Germany
10 years, 11 months
libreport not working on alpha?
by Chris Murphy
I'm getting crashes in anaconda, and the "An unknown error has occurred" box appears, when I click Report Bug, the box vanishes, then returns. I cannot proceed and report the bug. Is anyone else seeing this? I thought this was an alpha blocking type of bug?
Chris Murphy
10 years, 11 months
my impressions of F19A, from Radeon testing day
by DJ Delorie
Not sure how many of these are specific to the Radeon driver, but I
kept notes as I went through the whole install/test process, and I'm
including them here in case they help anyone. I'm available for more
detailed testing if needed.
hardware:
Intel six-core i7-EE, 24GB RAM, Gigabyte GA-X58A-UD3R motherboard
ATI Radeon HD 6870 with four monitors (one 30", two rotated 20", one 23")
My monitor setup is: one 30" 2560x1600 in the middle, one 20"
1200x1600 (rotated) on each side, and the 1080p way off on the right.
Basic install went OK.
"Welcome" dialog is on rightmost monitor, not main monitor (the black
Gnome menu is on main monitor).
After the screen saver kicked in, it wasn't obvious how to leave the
giant clock screen (none of the usual key presses or mouse clicks did
anything). Only later was I shown the up-arrow thing but clicking on
it did nothing. Eventually I tried swiping it which worked after a
few tries. Swiping a clock up a 30" monitor isn't the most natural
way to disable a screensaver.
No options in keyboard layout window - it brought up a blank list and
made me "pick" one.
It then asks to create local account despite already doing so in
anaconda. Could not skip or re-enter same data. Anaconda should tell
you that the account you create *there* is *not* an admin, and that
you will be *required* to create yet another account later, which *is*
an admin.
After "start gnome", main screen went solid white until ESC pressed.
Only later did I realize it was supposed to play a movie (sound wasn't
configured yet). The movie tells me to press a key that doesn't exist
on my keyboard.
Resizing firefox is VERY slow - about 2-3 FPS.
analog 5.1 "test speakers" emits no output to subwoofer (the other 5
speakers worked fine)
Digital spdif output does not have options for surround sound *at all*
(the hardware is known-good under F17).
Xrandr settings should be site-wide, not personal (esp, they're
ignored for the greeter screen). The greeter is hard to use because
you can't keep track of where the cursor is due to the misconfigured
screens.
Xrandr changes turn the screen to random garbage for a few seconds
before reconfiguring.
Xrandr display setup app doesn't work right for four monitors - it
requires pairs of monitors to be touching, making it difficult to set
up. Example: if you change the rotation for the #3 monitor, you can't
place it next to the #1 monitor - just next to the #4 monitor (or very
far away from it). In my case, #3 was the one to the left of the main
monitor, which took a few minutes to do. I've played puzzle games on
my phone which were less tricky than using this app.
Also, the monitor icons are very tiny - like, 5mm tall on my 30"
monitor.
At some points, gnome brought up a light-grey-on-lighter-grey themed
dialog, which looks like a disabled dialog and is hard to read.
I could not find out how to update the system software with gnome3.
No notifications popped up, and there were no apps to "check for
software updates". The software install tool didn't have such an
option. I ended up running "yum update" from a terminal (which did
update software).
totem segfaults running NET_MAN.ogg (known bug)
pymol starts on the wrong monitor - it starts on the far right
monitor, not the main monitor.
pymol transparency demo doesn't work
- and coredumps on exit
tuxkart - native screen resolution (2560x1600) is not offered,
"fullscreen" core dumps.
hmmm... right side monitor is now a clone of left side monitor after
this test. (fixed by switch-user)
xonitic corrupts xrandr settings - switches everything to "mirrored"
mode, which means every screen has the same game on it, two of them
sideways and all of them distorted. *Not* fixed by switch-user.
0ad isn't playable - the "ok" button to start the game is drawn on a
spot on my desktop that doesn't map to a monitor, so I can't click it.
Minecraft won't run. I assume this is due to an interaction between
an old gaming library on their part and the use of our java instead of
oracle's (i.e. it's a standard setup, not my usual custom one), but
the traceback was in the xrandr setup routines.
--
All in all, I found F19A's Gnome to be just as hard to use as I
recalled in F17 and F18, and support for my four-monitor setup to be
just as poor as in the past. Perhaps F19 would run fine on a tablet
but it's a non-starter for me without heavy customization.
10 years, 11 months
Question regarding bug filing on gnome components
by Michael Knepher
I'm running Fedora 19 alpha, and have a question on the most appropriate
place to file bugs on gnome components like epiphany and gedit. Should I
file in the Fedora bugzilla or directly to the Gnome bugzilla?
Michael Knepher
10 years, 11 months
Fedora-19-Alpha-x86_64-DVD.iso will not boot on VMWare Fusion
by Jay Finger
I'm contacting this list per instructions on
https://fedoraproject.org/wiki/F19_Alpha_release_announcement. I'll gladly
file a bugzilla for this if you send me pointers...
I run VMWare Fusion on a MacBook Pro (2011 model). Fusion says "Version
5.0.3 (1040386)". It is up to date (I just checked for updates).
When trying to install a new VM and booting
from Fedora-19-Alpha-x86_64-DVD.iso it hangs for a couple of minutes. Then
finally says
dracut-initqueue[326]: Warning: Could not boot.
Starting Dracut Emergency Shell...
Generating "/run/initramfs/sosreport.txt"
Entering emergency mode. Exit the shell to continue.
And a bit ore that I'm not bothering to type. I haven't yet saved the
sosreport.txt: let me know if you would like it, or would like for me to
file a bug. Obviously I'm hoping our response will be "We know, we've
fixed it in the next ISO..." :) But I'm happy to help troubleshoot, just
direct me.
Thanks,
Jay Finger
10 years, 11 months
f19alpha, hang "booting a command list"
by Chris Murphy
I'm stumped on how to get more information during the boot process. At this point I don't have enough information to file a bug.
F18 works OK on this computer. Even with 3.9 kernels with a regression related to fb or nouveau, I still get kernel messages during boot. But not with F19 alpha. When I remove 'quiet rhgb' parameters when booting, all I get is "Booting a command list" and then nothing, just that same text on a black background. The light on the USB stick flashes for about 1.5 minutes, then stops. And the computer gets really hot, and the fans eventually shoot up to max and the thing sounds like a hairdryer.
I've tried two USB sticks. And the image has been verified with sha256.
Chris Murphy
10 years, 11 months
F18, F19 webalizer problem?
by Cristian Sava
Hi all,
Webalizer is enabled via /etc/sysconfig/webalizer but I don't understand
why /etc/cron.daily/00webalizer has this line:
[ "z$WEBALIZER_CRON" != "zyes" ] && exit 0
that I think it should be (and it is working this way)
[ "$WEBALIZER_CRON" != "yes" ] && exit 0
What is the mistery?
C.Sava
10 years, 11 months
Revised Beta criteria up
by Adam Williamson
Just a heads-up, folks - I completed the Beta criteria revisions,
following the general model from Alpha (as previously discussed in
thread "Major criteria re-write / re-design proposal"), and put the
revised version into place just in time for tomorrow's first Beta
blocker review meeting. Of course, please call out any errors /
omissions etc!
https://fedoraproject.org/wiki/Fedora_19_Beta_Release_Criteria
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
10 years, 11 months
fedup testing
by Ed Greshko
I wanted to do some fedup testing and used....
fedup-cli --network 19 --debuglog /root/fed.log
This failed with...
zlib-1.2.7-10.fc19.x86_64.rpm | 88 kB 00:00:00
getting boot images...
Traceback (most recent call last):
File "/bin/fedup-cli", line 285, in <module>
main(args)
File "/bin/fedup-cli", line 236, in main
raise NotImplementedError("use --instrepo or --skipkernel")
NotImplementedError: use --instrepo or --skipkernel
What is the proper --instrepo to use for testing at this point?
--
The only thing worse than a poorly asked question is a cryptic answer.
10 years, 11 months
