Wireless WPA2 Personal Missing
by Richi Plana
So I installed Werewolf on a laptop, and now I can't get wireless
working. I've set up WPA2 Personal Security and it worked with F7 +
NetworkManager. For now, I can't see the "WPA2 Personal" option in F8. I
thought that was one of the supported systems. Bug or known issue?
The second isn't a big problem but might be something the devs might be
interested in. I've a DLink DWL-G650 PCMCIA card and I used to use
madwifi's ath_pci module with it in F7. Worked like a charm. Apparently
in F8, there's a module that keeps getting loaded called ath5k.
Unfortunately, NetworkManager isn't picking up the interface when that
gets loaded. I rmmod it and modprobe ath_pci and everything seems to
work (except I can't get WPA2 Personal to work). Bug?
--
Richi Plana
16 years, 6 months
(It pains me to say) KDE and broken logout
by Paul Michael Reilly
First let it be known that I read every last character of the original
dreadful thread as a result of logout not working for me using the RC3
F8 bits (the live Fedora and KDE x86_64 spins). And I've confirmed that
my issue is definitely not GDM vs KDM.
The behavior I see after installing the KDE spin is that logout works
perfectly after I login for the first time. After the second and
subsequent logins I get empty air (nothing happens) when I click on the
Logout menu item.
I'll try posting a bug report (again) after traffic on redhat.com
subsides. Meanwhile, I've switched back to F7 since either no KDE or no
SUSPEND are both non-starters. But I do intend to dust off another
laptop/desktop to install Rawhide and gather more information on the
problem. To that end I'm open to suggestions for troubleshooting the issue.
-pmr
16 years, 6 months
Fedora 8 - Common Bugs and Known Issues
by Rahul Sundaram
Hi
As usual,
https://fedoraproject.org/wiki/Bugs/F8Common
Let me know if there are other common issues (with a reference to the
bugzilla report) and if there are any known workarounds to them. Just
add them yourself if you have wiki write access and we will review them
periodically. Thanks for your assistance.
=== CD/DVD Install Hangs ===
There appears to be an issue between ISOLINUX and certain BIOSes where
the USB keyboard does not work at the boot menu. This can be worked
around by holding down the "shift" key during bootup to force the
bootloader into text mode.
[http://bugzilla.redhat.com/239585 Bug 239585] - On certain systems, the
CD/DVD may hang during boot with message "Ready". Most of the bugs that
caused this are thought to be fixed.
=== Sun Java Bug ===
[https://bugzilla.redhat.com/show_bug.cgi?id=254144 Bug 254144] Fedora 8
includes [http://icedtea.classpath.org/wiki//Main_Page IcedTea], a free
and open source derivative of OpenJDK. Users trying to install Sun Java
might run across a bug with the Sun JVM that makes it incompatible with
the newer libX11 included in Fedora 8.
Workaround is [https://bugzilla.redhat.com/show_bug.cgi?id=254144#c14
documented]. We highly recommend using IcedTea instead.
=== Suspend/Resume Problem With Nvidia cards ===
Suspend option in the menu has been deliberately disabled in this
release on systems with Nvidia cards since the default "nv" Xorg driver
from Nvidia has a number of problems in handling of suspend and resume
correctly. If you wish to override this default, add a file that
contains ALLOW_NV_SUSPEND="yes" under /etc/pm/config.d
=== NetworkManager cannot connect to EAP-TLS secured wireless networks ===
[https://bugzilla.redhat.com/show_bug.cgi?id=323371 Bug 323371] - The
!NetworkManager 0.7 snapshot included in Fedora 8 cannot connect to
networks that use encrypted certificate files for authentication. A fix
will be available soon.
=== NetworkManager fails to see wireless networks with Intel 3945
chipsets ===
[https://bugzilla.redhat.com/show_bug.cgi?id=319071 Bug 319071] If you
have the Intel 3945 wireless chipset, you may experience trouble finding
and associating with wireless networks in NetworkManager. Try adding
{{{options iwl3945 disable_hw_scan=1
}}}
to /etc/modprobe.conf
=== Cannot start ssh: Service will not start after installation of the
x86_64 version ===
[https://bugzilla.redhat.com/364971 Bug 364971] - /usr/sbin/sshd:
Permission denied
This issue should be fixed by updating to the latest
selinux-targeted-policy which is greater than
selinux-policy-targeted-3.0.8-44.fc8
Rahul
16 years, 6 months
Deltarpms for F7 -> F8
by Jonathan Dieter
Deltarpms are now available for an upgrade from Fedora 7 to Fedora 8
(i386 only) using the yum-presto plugin. To use, first make sure your
Fedora 7 system is completely up-to-date and then follow the steps in:
http://fedoraproject.org/wiki/YumUpgradeFaq
The only change is that after step 3, add
deltaurl=http://lesloueizeh.com/f8/i386/fedora
to /etc/yum.repos.d/fedora.repo
If you have any questions, ask on #fedora on IRC or the mailing list.
To give you an idea of the savings, I've downloaded the entire 12G
Fedora 8 repository, and I only had to download 2.1G of rpms and drpms
applied against our local Fedora 7 repository.
Jonathan
16 years, 6 months
Re: After Fedora 8 comes Fedora 9!
by sean darcy
Jesse Keating wrote:
.................
>
> For those of you that were early adopters of Fedora 8 and joined the
> Rawhide bandwagon, but want to get off at the Fedora 8 stop, I suggest
> that you ensure your 'development' yum repo is disabled. For those of
> you that wish to continue to enjoy Rawhide, I suggest you ensure that
> your 'fedora', and any updates repos are disabled, and make sure that
> your development repo remains enabled.
OK. Did that. Now:
yum upgrade
Loading "refresh-updatesd" plugin
Could not retrieve mirrorlist
http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-8&arch=x86_64
error was
[Errno 14] HTTP Error 404: Not Found
rpm -qif fedora-updates.repo
Name : fedora-release Relocations: (not relocatable)
Version : 8 Vendor: Fedora Project
Release : 3 Build Date: Mon 29 Oct 2007
10:25:49 PM EDT
cat fedora-updates.repo
[updates]
name=Fedora $releasever - $basearch - Updates
failovermethod=priority
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/updates/$releasever/$basearch/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-relea...
enabled=1
...........
sean
16 years, 6 months
Smoothening SELinux Devel During F9 Cycle
by Warren Togami
I just spoke at length with dwalsh about ways we can smoothen
testing/development of SELinux during the F9 cycle. Here are ideas that
we came up with.
NOTE: I was wrong in believing that new things were confined late in the
F8 cycle. Dan said new things were confined even before Test1, just
nobody noticed until late. He said new things actually aren't confined
very often. He did however take responsibility for the -42 mistake,
which caused great distress during the past freeze.
These two rules should help to smoothen this out for the next cycle.
RULE #1:
=======
When new confines happen (or anything causing the default rules to be
more restrictive), Dan will write up an e-mail summary describing the
new restrictions and notify fedora-devel-announce. This is to set
expectations and make it easier for people to test for breakage and
submit reports to fine tune the selinux-policy. If we reach the final
freeze and a confined application is still broken, we can consider
unconfining it.
RULE #2:
=======
During the freeze period when rel-eng reviews and allows/denies changes,
Dan will write more explicit %changelog entries and poke rel-eng@ when
he wants a build to be included. The %changelog entries should make it
easier to test the changes and to make a determination whether we want
to allow it in the release.
Grow Awareness
==============
Additionally, we need to do more training/blog announcements/etc both to
Red Hat engineers and Fedora developers to not be so afraid of SELinux.
I know that I personally became a lot more comfortable with running
with enforcing mode only after he sat down and showed me how easy it is
to use audit2allow -M. We need to do more promotion of these VERY BASIC
SKILLS and how to file a proper AVC bug report.
All developers need to be comfortable about running with enforcing mode,
to help to fix the SELinux rules rather than live in denial.
(Lame pun?)
Warren Togami
wtogami(a)redhat.com
16 years, 6 months
Fedora 9 Feature suggestion - The start menu and caching
by Mark
Hey,
Fedora 8 has dropped the readahead program which was fine because it
wasn't speeding up anything at all (not in my experience) but i do
think we need some kind of a caching for the start menu and serveral
other programs.
This is the current case when you install fedora (any version) and go
to the start menu:
- Sometimes it doesn't even show up on the first click simply because
it still has to load/start(? just feels slow)
- When it pops up (the first time after boot) the icons are not there
at first.. they come quick but they should be pre cached
What would be best with the start menu:
- During boot the start menu and all it's icons (actually all the
default icons) should be cached so that the start menu pops up right
away when you click on it and all the icons are in place and vissible.
Now about the caching itself.
Wouldn't it be best to precache all the applications that are gonna be
started anyway? like:
- gome-desktop
- gnoma-panel
- the default gnome applets
- nautilus
- firefox
- the default mail client (forgot the name)
- the default wallpaper
- precache all the icons that where on the desktop in the last session
so they appear fast when gnome starts
- perhaps also GDM so that you don't see the picture building up like
you see at this moment in nearly all linux distributions.
- Also for gdm: perhaps a good idea to fade it in like in windows..
was also requested here:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/22903 but it
doesn't seem like they got far with it. it's not in gutsy (i didn't
see it).
And perhaps some less importand programs that get used often:
- Pidgin
- the most used irc client (whichever one that is)
- and probable a dozen more
So what do you think of those suggestions?
lets make Fedora 9 more user friendly than Fedora 8 (not that 8 or 7
are not friendly).
Btw.. what is gonna be the idea with Fedora 9? is it gonna be a
release with a ton of new features but no (or nearly no) improvements
to current features? or is it gonne be a release to improve all the
current features of fedora? that last part would be good for fedora.
Mark
16 years, 6 months
NFS Update and SELinux
by Richi Plana
Hi,
On F7, the latest nfs-utils update (1:1.1.0-4.fc7.x86_64) seems to be
resulting in a lot of SELinux denials (accesses to /dev/usbmon?).
Not knowing what to do next, I thought I'd ask at fedora-devel. Is there
something I should do that I'm not (ie. rebooting, restarting some
daemon, restorecon)? Is this a bug in nfs-utils?
selinux-policy-targeted? Is this some malicious software update?
I could use a little help in troubleshooting.
--
Richi Plana
16 years, 6 months
After Fedora 8 comes Fedora 9!
by Jesse Keating
The development cycle of Fedora 9 will begin in earnest tomorrow. This
will mark the first attempt at composing Rawhide with package builds
that target Fedora 9. There is quite a number of them built up
already, over 800. This will be a bumpy ride at first as we start to
see where all these builds gets us. In the next couple of weeks we the
project will work on setting a schedule for Fedora 9, start reviewing
proposed Features, and come up with an overall idea of what we'd like
to accomplish this time around.
For those of you that were early adopters of Fedora 8 and joined the
Rawhide bandwagon, but want to get off at the Fedora 8 stop, I suggest
that you ensure your 'development' yum repo is disabled. For those of
you that wish to continue to enjoy Rawhide, I suggest you ensure that
your 'fedora', and any updates repos are disabled, and make sure that
your development repo remains enabled.
During the development of Fedora 8 we experimented with a few things to
help users and developers of Fedora have a smooth ride through the
development cycle. Those experiments have worked out pretty well and
have been incorporated into the overall development strategy, as
oulined here:
http://fedoraproject.org/wiki/ReleaseEngineering/Overview As we look forward to Fedora 9 we hope to make the experience even more enjoyable and at the same time even more beneficial to all involved. I welcome suggestions and discussion on how to improve things, which is always a constant goal of mine.
So lets all sit back, relax, and enjoy a day of rest for Fedora 8.
Tomorrow it starts up all over again!
--
Jesse Keating
Fedora -- All my bits are free, are yours?
_______________________________________________
Fedora-devel-announce mailing list
Fedora-devel-announce(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-announce
16 years, 6 months
Removal of pam_console questions
by Linus Walleij
I read this some time ago:
http://fedoraproject.org/wiki/Releases/FeatureRemovePAMConsole
I guess libmtp and libnjb which I maintain need to be updated to work with
HAL ACLs. They both create a node /dev/libxxx-nnn and place a file in
/etc/security/console.perms.d/ each, like this:
<libnjb>=/dev/libnjb*
<console> 0600 <libnjb> 0600 root
However I am not certain as to how one migrate to HAL+ACLs for this, can
someone point to a package which is properly migrated already and tell
how it's basically done so I can have a look and fix this?
(If you wanna hack the packages in CVS since you think it's quicker to
just do it than explain how to do it, then just go ahead...)
Linus
16 years, 6 months