test May 2009

test@lists.fedoraproject.org

190 participants
362 discussions

media key behavior?
by Tom Horsley 08 May '09

08 May '09

I was just playing with my new keyboard, and I noticed a strange difference between fedora 10 and fedora 11: On fedora 10, the mute and volume keys seem to briefly pop up a little volume control to reflect the status. (As far as I know, I did nothing to configure this to happen and I actually wish it wouldn't :-). On fedora 11, the same keys do nothing. Anyone know what is going on here (and who is arranging to hook up those volume keys to something)? Some strange hal connection maybe? Most of the other extra buttons (with labels like mail and search and wot-not) show up in xev as keycodes with no associated keysyms. Thankfully, the Power and Sleep buttons don't seem to be attached to anything :-).

3 5

Rawhide Install Broken.
by Chuck Forsberg WA7KGX 07 May '09

07 May '09

Today's Rawhide pxeboot install wedges with a black screen after the loaded kernel starts and one would expect to see a X screen. This is with Intel Core Duo Gigabyte ga-ep45-ud3p and Nvidia 9600GT. I tried the boot.iso disk route and got the same result. Boot.iso and text install got an unhandled exception when I selected custom disk layout. Boot.iso with basic vga didn't work either. -- Chuck Forsberg caf(a)omen.com www.omen.com 503-614-0430 Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 FAX 629-0665

3 3

Re: Bug workflow page revised
by Allen Kistler 07 May '09

07 May '09

Adam Williamson wrote: > On Thu, 2009-05-07 at 08:39 -0700, Adam Williamson wrote: >>> If the ON_QA state isn't meaningful for Fedora then this state machine >>> probably needs some adjustment for that, but it's not insane on its >>> own terms. >> >> The ON_QA / FAILS_QA loop doesn't make too much sense for Fedora as >> there is no paid QA group wired into this loop. 'QA' is the reporter. >> >> I think it should just be a simple setup as the reporter describes; >> reporters should be allowed to set bugs back to ASSIGNED from MODIFIED. > > Ug, sorry - I'm thinking too much about Rawhide here. The ON_QA loop is > of course used for Fedora in stable release updates. > > I think the question comes down to "should the onus / ability to return > a bug to ASSIGNED when it fails testing be on the reporter or maintainer > or both". Thoughts? I know you had ON_QA in the flow diagram in the original post, so if you're adding it, adjust the following comments as appropriate. My thoughts are to allow both maintainers and reporters to send a MODIFIED report back to ASSIGNED. First, some maintainers might only check on reports in the ASSIGNED state. The only way they know to keep working on a bug is if someone moves the report back to ASSIGNED for them. It's anti-productive to prevent reporters from doing this. Posting comments doesn't work for reasons that may include assignees setting email options to ignore comments. Second, some reporters seem to figure that all they have to do is report bugs. They never track or follow-up on even their own reports. It's anti-productive to exclude maintainers from the management of the reports filed against their own components.

1 0

gnome run application autocomplete problem.
by Adrin Jalali 07 May '09

07 May '09

Hi, running F11 when I want to run an application using Alt+F2 dialog, if the dialog understands that only one application beginning with the typed characters exists, it completes it and you should continue character after that name, for example if I decide to run gnome-terminal, I type gnome-terminal and I see that the typed word is: gnome-terminalnal (this happens only if I type fast) Best, Adrin. # rpm -qa | grep gnome libgnomeprintui22-2.18.4-1.fc11.x86_64 gnome-python2-libegg-2.25.3-3.fc11.x86_64 gnome-panel-2.26.1-2.fc11.x86_64 gnome-mag-0.15.6-1.fc11.x86_64 gnome-python2-bonobo-2.26.1-1.fc11.x86_64 gnome-media-libs-2.26.0-6.fc11.x86_64 gnome-python2-gtksourceview-2.26.0-3.fc11.x86_64 gnome-terminal-2.26.1-1.fc11.x86_64 gnome-session-xsession-2.26.1-1.fc11.x86_64 libgail-gnome-1.20.1-2.fc11.x86_64 gnome-disk-utility-libs-0.3-0.5.20090415git.fc11.x86_64 gnome-applet-netspeed-0.15.2-2.fc11.x86_64 libgnomecups-0.2.3-5.fc11.x86_64 gnome-packagekit-2.27.2-0.2.20090414git.fc11.x86_64 gnome-applet-jalali-calendar-1.6.7-1.fc11.noarch gnome-user-docs-2.26.1-1.fc11.noarch gnome-speech-0.4.25-2.fc11.x86_64 gnome-backgrounds-2.24.1-1.fc11.noarch gnome-python2-canvas-2.26.1-1.fc11.x86_64 libgnomeui-2.24.1-1.fc11.x86_64 gnome-mount-0.8-5.fc11.x86_64 gnome-pilot-2.0.17-2.fc11.x86_64 gnome-sharp-2.24.0-3.fc11.x86_64 gnome-python2-desktop-2.26.0-3.fc11.x86_64 libopenraw-gnome-0.0.5-3.fc11.x86_64 gnome-python2-gtkhtml2-2.25.3-3.fc11.x86_64 gnome-settings-daemon-2.26.1-3.fc11.x86_64 gnome-menus-2.26.1-1.fc11.x86_64 compiz-fusion-gnome-0.7.8-8.fc11.x86_64 gnome-keyring-pam-2.26.1-1.fc11.x86_64 gnome-applets-2.26.1-3.fc11.x86_64 gnome-python2-gnomeprint-2.26.0-3.fc11.x86_64 gnome-python2-gtkspell-2.25.3-3.fc11.x86_64 gnome-desktop-2.26.1-4.fc11.x86_64 gnome-screensaver-2.26.1-2.fc11.x86_64 gnome-panel-libs-2.26.1-2.fc11.x86_64 gnome-icon-theme-2.26.0-2.fc11.noarch compiz-gnome-0.7.8-18.fc11.x86_64 libgnomekbd-2.26.0-1.fc11.x86_64 libgnomecanvas-2.26.0-1.fc11.x86_64 gnome-themes-2.26.1-1.fc11.noarch gnome-power-manager-2.26.1-2.fc11.x86_64 gnome-python2-gnomekeyring-2.26.0-3.fc11.x86_64 gnome-desktop-sharp-2.26.0-1.fc11.x86_64 fedora-gnome-theme-8.0.0-9.fc11.noarch gnome-disk-utility-0.3-0.5.20090415git.fc11.x86_64 gnome-applet-sensors-2.2.1-2.fc11.x86_64 gnome-doc-utils-stylesheets-0.16.1-1.fc11.noarch libgnome-2.26.0-1.fc11.x86_64 gnome-python2-gnome-2.26.1-1.fc11.x86_64 gnome-session-2.26.1-1.fc11.x86_64 NetworkManager-gnome-0.7.1-3.git20090414.fc11.x86_64 gnome-python2-libwnck-2.26.0-3.fc11.x86_64 gnome-python2-gnomevfs-2.26.1-1.fc11.x86_64 gnome-utils-2.26.0-1.fc11.x86_64 libgnomeprint22-2.18.6-1.fc11.x86_64 PolicyKit-gnome-libs-0.9.2-3.fc11.x86_64 gnome-python2-gconf-2.26.1-1.fc11.x86_64 gnome-bluetooth-libs-2.27.4-4.fc11.x86_64 gnome-python2-applet-2.26.0-3.fc11.x86_64 PolicyKit-gnome-0.9.2-3.fc11.x86_64 gnome-python2-extras-2.25.3-3.fc11.x86_64 gnome-vfs2-2.24.1-2.fc11.x86_64 gnome-user-share-2.26.0-2.fc11.x86_64 gnome-bluetooth-2.27.4-4.fc11.x86_64 gnome-games-help-2.26.1-2.fc11.noarch gnome-sharp-devel-2.24.0-3.fc11.x86_64 gnome-media-2.26.0-6.fc11.x86_64 gnome-system-monitor-2.26.1-2.fc11.x86_64 gnome-python2-2.26.1-1.fc11.x86_64 gnome-mime-data-2.18.0-4.fc11.noarch gnome-disk-utility-ui-libs-0.3-0.5.20090415git.fc11.x86_64 gnome-games-2.26.1-2.fc11.x86_64 gnome-keyring-2.26.1-1.fc11.x86_64

2 1

Bugzappers: requests from maintainers for special treatment
by Adam Williamson 07 May '09

07 May '09

Hi, guys. Just a general issue mail for Bugzappers: I've recently been talking to Seth Vidal, who wants special treatment for bugs in components he maintains (yum and createrepo): he's happy for them to be triaged according to the usual process, but he doesn't want the bugs changed from NEW to ASSIGNED. As a general principle, we should accept requests like this from the owners of components, because we're here for them and not vice versa; if our procedure doesn't work for them we should vary it so that what we do is helping them and not frustrating them. We have a regular triager for yum / createrepo who is aware of this (Jon Stanley), but anyone else who happens to touch yum / createrepo bugs in future, please follow this request. We used to have a Special Procedures wiki page for exceptions like this; it seems to have got pretty much lost in the recent wiki re-design. For now I've revised https://fedoraproject.org/wiki/BugZappers/Components_and_Triagers#Set_Compo… to add a new 'Special' column where we can add special instructions like this - I think that should be a good way to do it, as it's a high-visibility page that everyone should be looking at before triaging any given component. I envisage that short requests (like this one) can go directly in the table, longer ones could be added as footnotes (or to a separate page) and linked from the table. (I took out the statistics from it, as discussed at the last meeting, because they're obsolete and not helping anyone now, and the table would've been getting too wide with those in it). Does this seem sensible to everyone? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net

6 15

Re: Bug workflow page revised
by Allen Kistler 07 May '09

07 May '09

Adam Williamson wrote: > I just got a bit inspired by a QA meeting discussion, and have made > substantial revisions to > https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow .... So here's a question I've asked before (a couple months ago), but it really seems worth asking again. What happens when QA on a MODIFIED report fails? Shouldn't there be a path to send it back to ASSIGNED for rework? I do know that RH BZ currently doesn't allow it. So as a reporter, the only thing I can do if a proposed patch fails my retest is CLOSE the report. Doesn't that workflow seem broken by design?

3 3

No X after upgrade to xorg-x11-drv-nouveau-0.0.12-33.20090501gitf69b34a / nouveau_dri.so missing
by Niels Haase 07 May '09

07 May '09

Hello, after update today X won't start any more. The update included some X relevant packages: xorg-x11-drv-nouveau-0.0.12-33.20090501gitf69b34a.fc11.x86_64 xorg-x11-server-common-1.6.1-11.fc11.x86_64 xorg-x11-server-Xorg-1.6.1-11.fc11.x86_64 kernel-2.6.29.2-126.fc11.x86_64 The problem seems to be the missing nouveau_dri.so file. The last lines from Xorg.log: (EE) AIGLX error: dlopen of /usr/lib64/dri/nouveau_dri.so failed (/usr/lib64/dri/nouveau_dri.so: cannot open shared object file: No such file or directory) (EE) AIGLX: reverting to software rendering (II) AIGLX: Loaded and initialized /usr/lib64/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 Backtrace: Anyone else see this error? PS: https://bugzilla.redhat.com/show_bug.cgi?id=499570 -- Regards, Niels

4 3

rawhide report: 20090507 changes
by Fedora compose checker 07 May '09

07 May '09

Compose started at Thu May 7 06:15:04 UTC 2009 Updated Packages: DeviceKit-disks-004-2.fc11 -------------------------- * Fri May 01 2009 David Zeuthen <davidz(a)redhat.com> - 004-1.fc11 - Upstream release 004 * Fri May 01 2009 David Zeuthen <davidz(a)redhat.com> - 004-2.fc11 - Rebuild anaconda-11.5.0.50-1.fc11 ------------------------- * Wed May 06 2009 Chris Lumens <clumens(a)redhat.com> - 11.5.0.50-1 - Use storage objects throughout the partition editing UI code (#491806, - Verify filesystems after the live resize (katzj) - Verify with fsck after resizing filesystems (katzj) - IBM improvements to linuxrc.s390 (#475350) (dcantrell) - Write out correct hostname during LiveCD installs (#492515) (dcantrell) - Enter in hostname entry field advances to next screen (#494135) (dcantrell) - Check if we'll clear a partition after setting its format attr. (#499251) (dlehman) - Don't pass the default clearPartType value to the device tree. (dlehman) - Fix some logic errors in storage.partitioning.shouldClear. (dlehman) - Forward port various iscsi fixes from 5.4 iscsi work (hdegoede) - Avoid writing out NAME= in ifcfg files (#497485) (dcantrell) - Retry network configuration in loader (#492009) (dcantrell) - Make sure /boot ends up on the same disk as Apple Bootstrap (#497390). (clumens) - Handle that the default bootloader entry can sometimes be None (#496618). (clumens) - The PS3 bootloader allows booting from ext4 filesystems (#498539). (clumens) - Support LVM PE sizes > 128MB (#497733) (cristian.ciupitu) - Set ANACONDAVERSION on most livecd installs. (clumens) - getDependentDevices is in devicetree, not storage (#499144). (clumens) file-5.02-1.fc11 ---------------- * Wed May 06 2009 Daniel Novotny <dnovotny(a)redhat.com> 5.02-1 - new upstream version; drop upstreamed patches; this fixes #497913 firstboot-1.106-1.fc11 ---------------------- * Tue May 05 2009 Chris Lumens <clumens(a)redhat.com> 1.106-1 - Display an error message when the user doesn't supply a password (#480927). - Lots of translation updates. gnome-bluetooth-2.27.5-1.fc11 ----------------------------- * Wed May 06 2009 Bastien Nocera <bnocera(a)redhat.com> 2.27.5-1 - Update to 2.27.5 gnome-disk-utility-0.3-1.fc11 ----------------------------- * Fri May 01 2009 David Zeuthen <davidz(a)redhat.com> - 0.3-1.fc11 - Upstream release 0.3 gnome-power-manager-2.26.1-3.fc11 --------------------------------- * Wed May 06 2009 Richard Hughes <rhughes(a)redhat.com> - 2.26.1-3 - Backport a patch from upstream to fix backlight DPMS. - Fixes #498041 gnote-0.3.1-1.fc11 ------------------ * Wed May 06 2009 Rahul Sundaram <sundaram(a)fedoraproject.org> - 0.3.1-1 - new upstream release. Fixes rhbz #498739. Fix #499227 * Fri May 01 2009 Rahul Sundaram <sundaram(a)fedoraproject.org> - 0.3.0-1 - new upstream release. Includes applet and more plugins. gvfs-1.2.2-6.fc11 ----------------- * Wed May 06 2009 David Zeuthen <davidz(a)redhat.com> - 1.2.2-5 - Don't show drives that are supposed to be hidden (#498649) - Only automount if media or drive was just inserted - this fixes a problem with spurious automounts when partitioning/formatting * Wed May 06 2009 David Zeuthen <davidz(a)redhat.com> - 1.2.2-6 - Rebuild libatasmart-0.12-3.fc11 ----------------------- * Wed May 06 2009 Lennart Poettering <lpoetter(a)redhat.com> 0.12-3 - Update handling of one ST drive, add another quirk for a weird FUJITSU drive (rhbz 498284) libvirt-0.6.2-6.fc11 -------------------- * Wed May 06 2009 Mark McLoughlin <markmc(a)redhat.com> - 0.6.2-5.fc11 - Fix handling of <hostdev managed='yes'> (bug #499386) * Wed May 06 2009 Cole Robinson <crobinso(a)redhat.com> - 0.6.2-6.fc11 - Refresh qemu caps when getCapabilities is called (bug #460649) policycoreutils-2.0.62-12.2.fc11 -------------------------------- * Tue May 05 2009 Dan Walsh <dwalsh(a)redhat.com> 2.0.62-12.2 - Fix fixfiles to handle btrfs * Fri Apr 24 2009 Dan Walsh <dwalsh(a)redhat.com> 2.0.62-12.1 - Fix audit2allow -a to read /var/log/messages * Thu Apr 16 2009 Dan Walsh <dwalsh(a)redhat.com> 2.0.62-12 - Add semanage module support pygobject2-2.16.1-4.fc11 ------------------------ * Wed Apr 22 2009 Matthew Barnes <mbarnes(a)redhat.com> - 2.16.1-4.fc11 - Add patch for GNOME bug #566571 (classic vs new-style inheritance crash). python-virtinst-0.400.3-8.fc11 ------------------------------ * Wed May 06 2009 Cole Robinson <crobinso(a)redhat.com> - 0.400.3-8.fc11 - Fix PCI assignment (bz 499267) seamonkey-1.1.15-4.fc11 ----------------------- * Wed May 06 2009 Martin Stransky <stransky(a)redhat.com> 1.1.15-4 - build with -fno-strict-aliasing (#468415) smart-1.2-64.fc11 ----------------- * Thu Apr 16 2009 Axel Thimm <Axel.Thimm(a)ATrpms.net> - 1.2-64 - Fix premature returns in sha256 patch. * Wed Apr 15 2009 Axel Thimm <Axel.Thimm(a)ATrpms.net> - 1.2-62 - Fix sha256 and mdclean patches. * Sun Mar 22 2009 Axel Thimm <Axel.Thimm(a)ATrpms.net> - 1.2-60 - Update to 1.2. xorg-x11-drv-intel-2.7.0-4.fc11 ------------------------------- * Wed May 06 2009 <krh(a)madara.bos.redhat.com> - 2.7.0-4 - Pull in fixes from the 2.7 branch. Summary: Added Packages: 0 Removed Packages: 0 Modified Packages: 17 Broken deps for ppc64 ---------------------------------------------------------- cabal2spec-0.12-1.fc11.noarch requires ghc > 0:6.10.1-7

1 0

Linux askmethod... How? {SOLVED}
by Cannon, Andrew C 07 May '09

07 May '09

Message: 3 Date: Wed, 06 May 2009 18:10:16 -0400 From: Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com> Subject: Re: linux askmethod... how? To: For testers of Fedora Core development releases <fedora-test-list(a)redhat.com> Message-ID: <1241647816.12122.245.camel(a)ignacio.lan> Content-Type: text/plain; charset="us-ascii" On Wed, 2009-05-06 at 22:30 +0100, Cannon, Andrew C wrote: > > Okay, this is a very simple question, with probably a very simple > answer, but I cannot for the life of me work out how to put in the > alternative method 'linux askmethod' at the grub screen. > > When I boot from the CD, I get a brief flash of the text screen, and > then it goes to the blue screen with the four options on. I can press > F1 to F5, but I still can't get anywhere. The prompt will give the > vmlinuz bit, but when I delete that and type in linux askmethod, I > just get put back to the blue screen. > > I know I've missed something, but what? You no longer need the "linux" just the "askmethod". That is, you add askmethod to the kernel line already in place. -- Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com> PLEASE don't CC me; I'm already subscribed

1 0

yum question
by Rob Healey 07 May '09

07 May '09

Dear Seth: Thank you so much for the idea and the info on yum-plugin-changelog. It works great and for exactly what I wanted. Sincerely, Rob G. Healey

1 0

← Newer
1
...
26
27
28
29
30
31
32
...
37
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test May 2009