I, along with many others, have a frequent annoyance where SlowKeys
gets enabled in the X server. Yes, I can work around it by holding
down a shift key to turn it off again. But is there any way I can
permanently disable it? Some way of configuring the X server such that
it never enables SlowKeys? I'm getting *really* fed up with it, and no
one seems to know what's turning it on. It's certainly *not* being
enabled by me holding down shift. And the bug report implies that the
X server itself isn't capable of turning it on. So it must be an
application that's doing it. However, I'm not running anything that I
wasn't running in previous Fedora releases, but I never had this
problem until F17 :-(
"Java is a DSL for taking large XML files and converting them to stack
traces" -- Bulat Shakirzyanov
I have run into a gotcha with the ISP which will not provide Rails 3 on
a shared server.
Can someone please enlighten me as to why not. What are the problems?
Apologies for OT but google so far doesn't help.
By now, it is clear that F18 has not quite matched up to expectations.
The main problem appears to be the installer. Several people here have
expressed their intent to stick to F17 and give F18 a miss. While there
is always a small proportion that appear to say this every time a new
release is put out, there is a larger issue here for Fedora itself:
several of us can not update because fedup or even fedora-upgrade does
not work (and some of us do not want to try this out because failing
would mean dealing with the installer or going back to F17). However,
Fedora needs to have people try out the distribution to work through
kinks in all the packages, otherwise F19 will be equally bad if not
worse. But without installing F18, there is no way out to this problem.
Therefore, I would like to suggest that Fedora put this current
installer (F18) in abeyance and re-roll the release using the old
installer while the new one is fixed for F19 (after responding to the
feedback generated thus far). I am not sure how an update to the
installer in F18 will help since an install is needed for an update and
once updated, there is no need for the installer. The main benefit to
Fedora for such an approach will be that all the other features
introduced in F18 can be tried and evaluated.
Important Notice: This mailbox is ignored: e-mails are set to be
deleted on receipt. For those needing to send personal or professional
e-mail, please use appropriate addresses.
FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family!
Visit http://www.inbox.com/photosharing to find out more!
On 31 January 2013 23:34, Ed Greshko <Ed.Greshko(a)greshko.com> wrote:
> On 02/01/2013 06:19 AM, Mike Fleetwood wrote:
>> On my netbook I booted a test kernel 3.8.0-rc4+ I compiled. Now after
>> booting back into my regular Fedora kernel 3.6.11-5.fc17.i686.PAE my
>> wifi network device remains permanently disappeared. No wifi networks
>> displayed in Network Manager gui. Also the Network Manager syslog
>> messages make it look like the device has completely disappeared.
>> Suggestions for restoring wifi welcome.
>> Fragment of Network Manager syslog messages when working before
>> Jan 18 23:01:53 edge NetworkManager: <info> WiFi enabled by radio
>> killswitch; enabled by state file
>> Fragment of Network Manager syslog messages when broken after
>> Jan 28 18:43:26 edge NetworkManager: <info> WiFi disabled by
>> radio killswitch; enabled by state file
> yum install rfkill
> Then provide the output of "rfkill list"
Solved now. Bit of a brown paper bag moment. I must have unknowingly
disabled wifi, but exactly when I was testing that kernel.
# yum install rfkill
# rfkill list all
0: eeepc-wlan: Wireless LAN
Soft blocked: yes <-- HERE
Hard blocked: no
# rfkill unblock all
(Or press [Fn][F2]).
I was just a bit dismayed to see that software blocking wifi removes
the wifi device line from the output of lspci:
01:00.0 Network controller: Atheros Communications Inc. AR928X
Wireless Network Adapter (PCI-Express) (rev 01)
I've just setup a pair of Fedora 18 boxes that I could use
some help with getting them to join the active directory domain we have at
work (2008 I think).Â What I would like is for users in a particular
group in AD be allowed to log into the Fedora 18 boxes without me having
to create accounts (and manage passwords) on the Fedora boxes.Â Is
Thanks for any help!
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Just took the leap in to Fedora 18 from 17.
In Fedora 17, I simply added a custom rule in the old
system-config-firewall to point to a file that had a trust of the
libvirt based virbr0 interface.
The new system-config-firewall has me a bit confused....
I would like to keep the new firewalld and it's initial presumption that
my em1 and wlan0 interfaces are in the "public" zone generally not
allowing unsolicited inbound activity. This appears to be the default
I would like to associate the virbr0 interface, created by libvirtd, to
be considered part of the "internal" zone, since I "trust" my own VMs
talking to the host. But, what is the "supportable" method for
accomplishing this? There is no ifcfg- where I could put the firewall
Thanks in advance,
i'm trying to install my webcam SWEEX WC250 HD under Fedora 18.
i didn't find any driver for that so after reading posts, i discovered that
v4l2 tool could help me, but when i click on "lsusb output"
button...nothing happen... v4l-tool is 1.0.3
any idea ?
Windows 7 x64 / Fedora 17 x64
Apache 2.4.3 / OpenSSL 1.0.1c
after a while living with ubuntu, i'm moving back to fedora as of
F18, and would like some advice. i have an ASUS G74S with twin 750G
drives, but i want to replace the boot drive with an SSD, and install
F18 in such a way as to maximize the benefit of the SSD for booting
and (mostly) R/O storage.
a lot of my time will be spent doing lengthy compiles (kernel,
openembedded), so in addition to system content on the SSD, i'll want
to keep all of my source there as well, while the build directories
will be on the regular drive.
is there a recommendation for installing F18 in terms of separating
what's appropriate for the SSD versus what isn't? most of that is
fairly obvious, just wondering if anyone wrote up something about
their experience doing just that and how well it worked for them.
Robert P. J. Day Ottawa, Ontario, CANADA