Hans de Goede wrote:
> Build System wrote:
>> Updated Packages:
>> * Sun Oct 28 2007 Jeremy Katz <katzj(a)redhat.com> - 0.6.18-3
>> - Even better multilib fixing (#335161)
> How does this match with us being in freeze?
that was a blocker:
* Bug 335161: ASSIGNED - triad (Linus Walleij)
- multilib file conflicts in gnokii
Fix was incomplete, needs a rebuild. This prevents people from being
able to yum upgrade from F8Test3 to F8 final.
or are you talking about the "better fix" ?
I have use RedHat since 4.(something) and I like Fedora and hope to stay
with it. The issue I have is downtime to do a full re-install and get
things configured. In the past I have had problems with
missing/dropped/depreciate packages that have caused me headaches.
Issues with secondary repositories not creating new packages for the
latest FC until requested. And all the other fun things that keep
showing up on this forum. For home use, I cannot afford a second spare
With FC8 just about to come out, I am still waiting until I get F7
working at home for my wife to allow me to move her from FC4 on her
laptop. I cannot take more than a day to do this and she needs all her
applications up and running. But some of issues are are not the Fedora
teams fault, as the applications are provided by secondary repositories.
I came across this article that discusses rolling upgrades in contrast
to scheduled upgrades.
Now this is a pro-PCLinux discussion but some of the points brought up
are interesting. Of course they have been brought up on this and the
users lists before.
Reading about the changes to development in F8 and later versions of
Fedora, I wonder if it would be possible to look at doing a rolling
upgrade instead of a release?
I have always been under the impression that a rolling upgrade wasn't
possible. I believe, from experience that there could be some problems
but in general, I don't see it as impossible.
In some cases, the old configuration files just don't work with the new
At work I am still using FC6, again due to down time needed to do a
clean install and get all the applications working.
I have seen some cases of installing F7 rpms in FC6 and this makes me
think that it would be possible to implement F8 rpms in F7 and possibly
F9 rpms in F8 when it comes out. I guess what I am trying to say is
that by the time F9 is ready to be spun, the F8 repositories are
carrying most if not all the software of F9 and users would be at the F9
Just a thought to make users lives easier.
I'm able to connect to my (already configured) wpa connection, but not a new
64-bit WEP. Just keeps asking for the password (WEP password, not the
This is: rpm -q NetworkManager
i'm using the new 188.8.131.52-37.fc8 kernel with mine 00:1b.0 Audio device:
Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
Everything seems to work fine except for my microphone device.
Trying to use the alsa device i got:
Failed to construct test pipeline for 'gconfaudiosrc ! audioconvert !
audioresample ! gconfaudiosink profile=chat'
gconfaudiosrc ! audioconvert ! audioresample ! gconfaudiosink
profile=chat: Failed to connect stream: OK
Fedora Ambassadors Project
Thanks, Michael! I attached the log. HTH! But again: It works if I run
system-config-users over valgrind?!?!
2007/10/29, Michal Jaegermann <michal(a)harddata.com>:
> On Mon, Oct 29, 2007 at 09:17:00AM +0100, Guido Ledermann wrote:
> > How can I send the output to a file to post it here?
> To redirect both stout and stderr in bash:
> some_program >& /some/file
I have recently been upgrading my kernel from fc7 to fc8. I am able to boot from Fedora (2.6.20-1.2949.fc7). But I cannot boot from vmlinuz-184.108.40.206-26.fc8 or from the fedora 7.92 rescue CD. When I boot from the CD, it does recognize my boot drive (/dev/sdb), but not the partitions on the drive. I did note in the faq to put options libata ignore_hpa=1 into my modprob.conf file, and rebuilt a new initrd, but this did not work either. Also when booting from the 7.92 rescue CD i get following ominous dmesg output:
sd 4:0:0:0: [sdb] Add. Sense: Scsi parity error
end_request: I/O error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
Dev sdb: unable to read RDB block 0
sd 4:0:0:0: [sdb] Attached SCSI disk
At least I can still boot under fc7, but it would be nice to move forward. Any suggestions welcome.
Thanks very much,
Please note my controller, and loaded modules under the fc7 kernel. Entire dmesg under 7.92 rescue cd is attached.
[root@workstation boot]# lspci | grep ATA
00:10.0 IDE interface: nVidia Corporation MCP04 Serial ATA Controller (rev f2)
00:11.0 IDE interface: nVidia Corporation MCP04 Serial ATA Controller (rev f2)
[root@workstation ~]# lsmod | grep ata
ata_generic 12101 0
pata_amd 16845 6
sata_nv 24005 1
libata 112869 3 ata_generic,pata_amd,sata_nv
scsi_mod 141101 4 sr_mod,sg,libata,sd_mod
So I resumed by laptop from hibername this morning and was greeted by
a dialog to unlock the keyring. Unfortunately, right as the dialog
appeared, I had clicked the NM applet to check what wireless networks
were available. Both the NM applet and the gnome keyring dialog
opened at the same time, and apparently both tried to grab focus at
the same time. As a result, the GUI locked up--I was unable to do
anything but move the mouse cursor around.
I went to CTRL-ALT-F1 console, logged in, and did "killall nm-applet"
and that restored the desktop.
Is this a compiz bug? NM-applet bug? gnome-keyring bug?