F17 - font fille error
by Aaron Konstam
In F17 I try toopen firefoc and evolutiom the screen goes black except
for a message in the top right corner of the screen:
Can't open font file True.
Otherwise the ,machine in locked. This does not happen alll the time.
Can someone explain this?
--
=======================================================================
A man who turns green has eschewed protein.
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam(a)sbcglobal.net
11 years, 2 months
Custom Partition Fedora 18
by Mickey
Fedora 18
Why for HEAVENS did they change the custom partitioning in F18 from the
F17 and previous versions ?
Is there a Tutorial for Custom Partitioning for Fedora 18 ?
11 years, 2 months
is it possible to download a spec file only using yum?
by Ranjan Maitra
Hello,
I was wondering if it is possible to download a spec file using yum
or rpm only (without downloading the rpm)?
Many thanks and best wishes,
Ranjan
--
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!
11 years, 2 months
UEFI support from command line
by Kevin Wilson
Hi,
Is there a way to know without entering BIOS, whether your machine supoports
UEFI or not ? I would appreciate if someone with a machine with UEFI
support will check whether when running "dmidecode" you see UEFI in the output.
Regards,
Kevin Wilson
11 years, 2 months
NetworkManager update breaks DNS config
by Patrick O'Callaghan
I just updated F18 using yum. The updates
included NetworkManager-0.9.7.997-2.fc18.x86_64. This broke DNS client
services on my machine, i.e. I couldn' t browse, email, or do lookups on my
main machine, even though other local machines all continue to work. After
some head-scratching the problem appears to be that /etc/resolv.conf has
been changed to have 127.0.0.1 as the (only) nameserver. Since I' m not
running bind or anything similar, this means that DNS is effectively
banjaxed.
My resolv.conf is very simple (one entry, pointing to my router, which is
configured to point upstream correctly).
Manually editing resolv.conf fixed the issue temporarily, but I imaginethat
NM will shortly intervene to undo the change.
Just thought I'd alert people to this before they too are bitten. I'm
posting this from a VM which luckily has its own resolver.
poc
11 years, 2 months
wakeup after pm-hibernate
by Kevin Wilson
Hi,
How should I wake up after pm-hibernate on Fedora 18 ?
Is there some button/special combination of buttons I should use ?
rgs,
Kevin
11 years, 2 months
e1000e problem in Fedora 15
by Amit Karpe
Hi,
We having new HP Z820 workstation. Which have Intel 82574L &
82579LM gigabit network card.
While booting in Fedora 15 it just stuck. Following are output in Fedora
17 (where system boot with success.)
[root@localhost ldap_newhp]# lspci -nn | grep -i eth
00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit
Network Connection [8086:1502] (rev 05)
01:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit
Network Connection [8086:10d3]
Few lines from dmesg
[ 1633.233297] e1000e 0000:04:00.0: irq 73 for MSI/MSI-X
[ 1633.284094] e1000e 0000:04:00.0: irq 73 for MSI/MSI-X
[ 1633.285079] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1642.265283] e1000e 0000:04:00.0: irq 73 for MSI/MSI-X
[ 1642.316094] e1000e 0000:04:00.0: irq 73 for MSI/MSI-X
[ 1642.317556] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1647.280547] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow
Control: RX/TX
[ 1647.285563] e1000e 0000:04:00.0: eth0: 10/100 speed: disabling TSO
[ 1647.291153] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 1657.802008] eth0: no IPv6 routers present
In F15 pass ACPI=off to kernel then it boot without problem, but them
Ethernet card are not able to configure.
Any idea ?
--
Regards
Amit Karpe.
http://www.amitkarpe.com/
http://news.karpe.net.in/
11 years, 2 months
Re: Is it possible to have finger print authentication in F18?
by J.Witvliet@mindef.nl
Are you sure you want to use F.P.?
I tried it several years ago, i ditched it because too many false negatives.
Van: Rahul Sundaram [mailto:metherid@gmail.com]
Verzonden: Thursday, February 21, 2013 06:59 PM W. Europe Standard Time
Aan: Community support for Fedora users <users(a)lists.fedoraproject.org>
Onderwerp: Re: Is it possible to have finger print authentication in F18?
Hi
On Thu, Feb 21, 2013 at 1:09 AM, Frédéric Bron <frederic.bron(a)m4x.org<mailto:frederic.bron@m4x.org>> wrote:
I have a fingerprint reader and F18. The fingerprint reader does not
seem to be installed automatically with F18.
Check whether your hardware is supported at all
http://www.freedesktop.org/wiki/Software/fprint/libfprint/Supported%20dev...
Rahul
______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, word u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
11 years, 2 months
SELinux is preventing......
by EGO-II.1
I kep receiving messages like this every now and then....I'm just
wondering.....should I be concerned? Is there something I need to do to
get these alerts and warnings to cease? Any help would be appreciated!
Thanx!
EGO II
SELinux is preventing /usr/lib/systemd/systemd-hostnamed from open
access on the file /sys/devices/virtual/dmi/id/chassis_type.
***** Plugin catchall (100. confidence) suggests
***************************
If you believe that systemd-hostnamed should be allowed open access on
the chassis_type file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep systemd-hostnam /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
Additional Information:
Source Context system_u:system_r:systemd_hostnamed_t:s0
Target Context system_u:object_r:sysfs_t:s0
Target Objects /sys/devices/virtual/dmi/id/chassis_type [ file ]
Source systemd-hostnam
Source Path /usr/lib/systemd/systemd-hostnamed
Port <Unknown>
Host EDDIE2000
Source RPM Packages systemd-197-1.fc18.1.i686
Target RPM Packages
Policy RPM selinux-policy-3.11.1-78.fc18.noarch
Selinux Enabled True
Policy Type targeted
Enforcing Mode Enforcing
Host Name EDDIE2000
Platform Linux 3.7.8-202.fc18.i686 #1 SMP Fri
Feb 15 17:57:07 UTC 2013 i686 i686
Alert Count 2
First Seen 2013-02-20 21:46:01 EST
Last Seen 2013-02-20 21:46:01 EST
Local ID 667cee4a-e0d1-4fbd-8ce8-a516e584b6c3
Raw Audit Messages
type=AVC msg=audit(1361414761.615:346): avc: denied { open } for
pid=2333 comm="systemd-hostnam"
path="/sys/devices/virtual/dmi/id/chassis_type" dev="sysfs" ino=156
scontext=system_u:system_r:systemd_hostnamed_t:s0
tcontext=system_u:object_r:sysfs_t:s0 tclass=file
type=SYSCALL msg=audit(1361414761.615:346): arch=i386 syscall=open
success=no exit=EACCES a0=b77b0da4 a1=88000 a2=1b6 a3=b8ca4788 items=0
ppid=1 pid=2333 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0
sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=systemd-hostnam
exe=/usr/lib/systemd/systemd-hostnamed
subj=system_u:system_r:systemd_hostnamed_t:s0 key=(null)
Hash: systemd-hostnam,systemd_hostnamed_t,sysfs_t,file,open
audit2allow
#============= systemd_hostnamed_t ==============
allow systemd_hostnamed_t sysfs_t:file open;
audit2allow -R
#============= systemd_hostnamed_t ==============
allow systemd_hostnamed_t sysfs_t:file open;
11 years, 2 months