Fedora Quality Assurance Meeting
Time: 16:00 UTC (12 EDT)
Location: #fedora-meeting on irc.freenode.net
Just a quick reminder ... the QA meeting will be on a new day+time this week (see above). Proposed agenda to follow.
Bug Triage Meeting
Tuesday @ 15:00 UTC/11:00 AM EST
Agenda for 2009-07-028
#topic - Triage Metrics and FAS - Update on the status
adamw is getting an update from comphappy
#topic - Status on Critical path packages triage list
axrs using src package names, update from him.
#topic - Status on Kernel bug triage
Time to start doing. Get a couple of bugs assigned and going.
#topic - Bugzilla Semantics - Discuss the proposals and feedback
#topic - Announcements
#topic - Open Floor
Have a topic not mentioned so far? Bring it up here.
If you have something you would like added for the meeting tomorrow, please
reply to this email. Also, you can add items for future meetings here
----- "James Laska" <jlaska(a)redhat.com> wrote:
> With a defined test priority  now present in the results pages, I
> curious how you felt about using the class="wikitable sortable" to
> for easier sorting of test results.
That's a nice idea, it can help for larger tables.
Here is the outcome of the meeting today (previously announced on the
list. Naturally if there is disagreement in what was proposed it can be
discussed and considered for adjustment:
o we made sure there were enough blocker bug review meetings ahead of
each freeze and test release candidate creation
o we will not create Release Candidates if there are bugs remaining on
the the blocker list
o if we cannot create the Release Candidates because the blocker list is
not clear we will move to slip the release a week
o at the final blocker review on Monday, 2009-10-26 if the blocker list
is clear we will move forward with the release–regardless of what might
be found after the fact because of the inability to unwind PR activities
that have been set in motion.
Thanks again to everyone for their time!
Under Fedora 10, finger print reading worked with my supported aes1610
finger print device. GDM let me login with my finger.
Under Fedora 11 it no longer detects my reader at all. I fired up a Live
CD and it does not detect the reader either.
I don't see any bugzilla component for the fprint stuff. Where do we
Finally success with fedora 11 and Novatel MC950D
4G device. Did a firmware update, actual version
available at vodafone.de, using windows (wine did'nt
work, windows access software must be installed).
Using the yesterday NetworkManager mobile
broadband update, creation of the broadband
connection was very simple. There was one handicap:
Vodafone.de reports their incall number as *99***1#
That seems to be wrong, the NetworkManager suggests
*99#, and that works.
Thank to all for your help!
In fedora 11, I have problems with the Huawei E220/E270 3G
USB stick (vendor 12d1, product 1003).
As I have learned, the problem seems to be with the
NetworkManager. Here is the relevant debug info:
[root@T40 ~]# /sbin/service NetworkManager stopNetworkManager-Daemon
beenden: [ OK ]
[root@T40 ~]# NM_SERIAL_DEBUG=1 NM_PPP_DEBUG=1 /usr/sbin/NetworkManager
NetworkManager: <info> starting...
-- Error received: File exists
-- Original message: type=0x14 length=56 flags=<REQUEST,ACK,ATOMIC>
NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned
NetworkManager: <info> (eth0): new Ethernet device (driver: 'e100')
NetworkManager: <info> (eth0): exported as
NetworkManager: <info> (wlan1): driver supports SSID scans (scan_capa
NetworkManager: <info> (wlan1): new 802.11 WiFi device (driver:
NetworkManager: <info> (wlan1): exported as
NetworkManager: <info> (ttyS0): ignoring due to lack of mobile
NetworkManager: <info> (eth0): device state change: 1 -> 2
NetworkManager: <info> (eth0): bringing up device.
NetworkManager: <info> (eth0): preparing device.
NetworkManager: <info> (eth0): deactivating device (reason: 2).
NetworkManager: <info> (wlan1): device state change: 1 -> 2
NetworkManager: <info> (wlan1): bringing up device.
NetworkManager: <info> (wlan1): preparing device.
NetworkManager: <info> (wlan1): deactivating device (reason: 2).
NetworkManager: <info> (wlan1): device state change: 2 -> 3
NetworkManager: <info> (wlan1): supplicant interface state: starting
NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile
NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile
Any hints? Any suggestions?
after installing the current koji kernel for my x86_64 system (for
the purpose of testing video), very early in the boot process, i got
the following diagnostic flashing on the screen, followed by a total
JBD: barrier-based sync failed on dm-0:8 - disabling barriers
i powered down, powered back up, and got further into the boot process
up to the network initialization, then rapid flashing of ADDRCONF
messages on the screen, then another hang.
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday