SELinux error on every policy package update
by Suvayu Ali
Hi,
I have been having this weird problem; everytime I there is a
selinux-policy update, I get the following error:
libsepol.print_missing_requirements: hotplug's global requirements
were not met: bool init_systemd (No such file or directory).
libsemanage.semanage_link_sandbox: Link packages failed (No such file
or directory).
semodule: Failed!
FWIW, this machine was updated from F17 to F19 with yum. I tried
searching for the error above, but could not make sense of what I found.
Any ideas?
--
Suvayu
Open source is the future. It sets us free.
10 years, 9 months
Continual reboots with 3.10.X and 3.11.X kernels
by Richard Shaw
I managed to get through a couple of kernel updates before performing a
reboot. Booting either the installed 3.10 or 3.11 kernel makes it through
the majority of the systemd startup but then reboots.
Anyone else seeing this?
$ rpm -qa kernel
kernel-3.9.9-201.fc18.x86_64
kernel-3.9.11-200.fc18.x86_64
kernel-3.9.10-200.fc18.x86_64
Thanks,
Richard
10 years, 9 months
What the heck is all this?
by Tom Horsley
Just got this output from a yum update this morning:
...
Cleanup : glib2-2.36.3-2.fc19 52/74
Cleanup : python-fedora-0.3.32.3-2.fc19.noarch 53/74
/var/tmp/rpm-tmp.dtrblY: line 1: fg: no job control
error: %preun(kde-settings-kdm-19-23.fc19.noarch) scriptlet failed, exit status 1
Error in PREUN scriptlet in rpm package kde-settings-kdm-19-23.fc19.noarch
Cleanup : gstreamer1-plugins-base-1.0.8-1.fc19.x86_64 54/74
error: kde-settings-kdm-19-23.fc19.noarch: erase failed
Cleanup : libvirt-daemon-driver-qemu-1.0.5.4-1.fc19.x86_64 55/74
Cleanup : libvirt-daemon-driver-lxc-1.0.5.4-1.fc19.x86_64 56/74
...
Failed:
kde-settings-kdm.noarch 0:19-23.fc19
[root@tomh ~]# rpm -q kde-settings-kdm
kde-settings-kdm-19-23.fc19.noarch
kde-settings-kdm-19-23.1.fc19.noarch
So what is busted on my system? I have a feeling I shouldn't
have two different versions of the same rpm showing up as installed
at the same time.
10 years, 9 months
Fedora won't boot with 3.10.4 kernel and akmod
by Junayeed Ahnaf
Hello,
I installed akmod for my graphics driver (AMD radeon) on kernel 3.9.9 , then the catalyst version was 13.6 beta . Now the kernel has upgraded and so did the driver (it is 13.8beta now, which has kernel 3.10x support), but I can not boot into the newer kernels. It logs out with an error.
I'm still forced to use 3.9.9 kernel, any suggestion?
Junayeed Ahnaf Nirjhor
10 years, 9 months
Shortcut key combinations does not work in LibreOffice
by Shahab Shahsavari Alavidjeh
I don't know when it begins but somewhere in the row I started to notice
that when I change Keyboard Layout to Farsi (Persian) Shortcut key
combinations (all of them with Ctrl and Alt) does not respond at all in all
LibreOffice applications.
when ever I want to Copy or Paste I have to change back to English Layout.
10 years, 9 months
unable to execute Wine 32 bits in Fedora 64 bits
by Skander Bahloul
Hi,
I try to install and execute wine 32 bits in Fedora 64 bits but i don't succeed.
Indeed, i always have the error message "unable to execute 32 bit binary".
Could you help me.
Thank you very much!
Best regards,
10 years, 9 months
Failed install from KDE live DVD
by Robin Laing
My daughter wanting to upgrade before going to school downloaded the
Live KDE image and it runs on her laptop. Tried the install to upgrade
from her present installed version (15) and cannot get it to work.
She doesn't want to reformat/destroy her present partition system so she
selected the partition and went into the custom mode. Selected all her
present partitions, / /boot /tmp /home /home/{hers} and tried to
continue. Program wouldn't let her select the / partition for the
installation.
Error messages were that it couldn't delete the /dev/sda6 partition for / .
To confirm, the installer wanted to
1. Destroy format ext4
2. Destroy Device Luks (uuid)
3. Destroy Format Luks (uuid)
4. Destroy Device /dev/sda6
Then back to the installer with an error message that it cannot continue.
Kept getting an error so we deleted the / (sda6) partition using fdisk
and tried again.
Still no luck.
Tried not to use the /home/{hers} partition and it still wouldn't work.
We are now downloading the full Fedora 19 DVD.
Now it is going to be a late night.
--
Free, full feature astronomy program at
http://www.stellarium.org
Free Office Suite at
http://www.libreoffice.org
10 years, 9 months
KVM bridge wonkiness in Fedora19
by Lonni J Friedman
Greetings,
I'm attempting to get several virtual machines setup on a Fedora19
host system, with the traditional bridge network devices (br0, br1,
etc). I've done this many times before with older versions of Fedora
(16, 14, etc), and it just works. However, for reasons that I cannot
figure out, the bridge doesn't seem to be working in Fedora19. While
I can successfully connect to the outside world (local network +
internet) from inside a VM, nothing can communicate with the VM from
outside (local network). I'm referring to something as trivial as
pinging. From inside the VM, I can ping anything successfully (0%
packet loss). However, from outside the VM (on the host, or any other
system on the same network), I see 100% packet loss when pinging the
IP address of the VM.
My first question is simply, does anyone else have this working
successfully in F19? And if so, what steps did you need to follow?
I'm not using NetworkManager at all, its all the network service.
There are no firewalls involved anywhere (iptables & firewall services
are currently disabled). Here's the current host configuration:
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.38eaa792efe5 no em2
vnet1
br1 8000.38eaa792efe6 no em3
br2 8000.38eaa792efe7 no em4
vnet0
virbr0 8000.525400db3ebf yes virbr0-nic
# more /etc/sysconfig/network-scripts/ifcfg-em2
TYPE=Ethernet
BRIDGE="br0"
NAME=em2
DEVICE="em2"
UUID=aeaa839e-c89c-4d6e-9daa-79b6a1b919bd
ONBOOT=yes
HWADDR=38:EA:A7:92:EF:E5
NM_CONTROLLED="no"
# more /etc/sysconfig/network-scripts/ifcfg-br0
TYPE=Bridge
NM_CONTROLLED="no"
BOOTPROTO=dhcp
NAME=br0
DEVICE="br0"
ONBOOT=yes
# ifconfig em2 ;ifconfig br0
em2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::3aea:a7ff:fe92:efe5 prefixlen 64 scopeid 0x20<link>
ether 38:ea:a7:92:ef:e5 txqueuelen 1000 (Ethernet)
RX packets 100093 bytes 52354831 (49.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 25321 bytes 15791341 (15.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xf7d00000-f7e00000
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.31.99.226 netmask 255.255.252.0 broadcast 10.31.99.255
inet6 fe80::3aea:a7ff:fe92:efe5 prefixlen 64 scopeid 0x20<link>
ether 38:ea:a7:92:ef:e5 txqueuelen 0 (Ethernet)
RX packets 19619 bytes 1963328 (1.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 11 bytes 1074 (1.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Relevant section from /etc/libvirt/qemu/foo.xml (one of the VMs with
this problem):
<interface type='bridge'>
<mac address='52:54:00:26:22:9d'/>
<source bridge='br0'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
</interface>
I can provide additional information, if requested. thanks!
10 years, 9 months
Fedora 19 update error
by Roger
sudo yum update detects all necessary Fedora 19 updates but errors out
with v8.
I think v8 requires both i686 and x86_64 because it fails without the
i686 version.
yum whatprovides v8:
1:v8-3.14.5.10-1.fc19.i686 : JavaScript Engine
Repo : fedora
1:v8-3.14.5.10-1.fc19.x86_64 : JavaScript Engine
Repo : fedora
1:v8-3.17.6.14-2.fc19.x86_64 : JavaScript Engine
Repo : fedora-chromium-stable
1:v8-3.14.5.10-1.fc19.x86_64 : JavaScript Engine
Repo : installed
yum list v8 reports:
v8.x86_64 1:3.14.5.10-1.fc19 installed
Available Packages
v8.i686 1:3.14.5.10-1.fc19 fedora
v8.x86_64 1:3.17.6.14-2.fc19 fedora-chromium-stable
I have been using sudo yum update --skip-broken --exclude v8.* to get
remaining updates
Is it safe to delete the fedora repo versions which seem earlier than
the google-chromium version?
Quite puzzled what to do here and would greatly appreciate some help please.
Thanks in advance
Roger
10 years, 9 months
Re: unable to execute Wine 32 bits in Fedora 64 bits
by Reindl Harald
please do not top-post
Am 06.08.2013 23:22, schrieb Skander Bahloul:
> Yes i install wine.i686 but i can execute it because my fedora is 64.
>
> ----- Mail original -----
> De: "Reindl Harald" <h.reindl(a)thelounge.net>
> À: "Community support for Fedora users" <users(a)lists.fedoraproject.org>
> Cc: "Skander Bahloul" <skander.bahloul(a)eleves.ec-nantes.fr>
> Envoyé: Mardi 6 Août 2013 22:51:32
> Objet: Re: unable to execute Wine 32 bits in Fedora 64 bits
>
> Am 06.08.2013 22:38, schrieb Skander Bahloul:
>> I try to install and execute wine 32 bits in Fedora 64 bits but i don't succeed.
>> Indeed, i always have the error message "unable to execute 32 bit binary"
>
> the output of "rpm -qa | grep wine" would be helpful
>
> you must install wine.i686 for 32 Bit windows apps
> wine.x86_64 is for 64bit apps
"i install wine.i686 but i can execute it because my fedora is 64" makes no sense
Fedora is multilib, Windows-Apps are mostly 32bit
so you need *wine.i686* for ordianry windows applications
wine.i686 has all the needed i686 libraries as dependency
again:
the output of "rpm -qa | grep wine" would be helpful
10 years, 9 months
