virtual machine’s network problem with fedora 16

facing issue with network in virtual machines (with virt-manager) in Fedora 16. It was always failed to boot. There is work around:-

$systemctl status dnsmasq.service

$systemctl stop dnsmasq.service

$systemctl disable dnsmasq.service

now virt-manager will be happy.


some of bug fixes for fedora 16 before release

during regular use of pre-release system, it is really good to know that something is fixed quickly. Lokalize is major application for translation. I am using gnome 3 on desktop and there were two major bugs from last week.

1) QT applications failed to select properly, when using in gnome -shell (Bug  ) – FIXED with qt-4.8.0-0.17.rc1.fc16

2)  ibus failed to work with gnome and kde (all applications) with Ctrl+Space (Bug – FIXED with ibus-1.4.0-4.fc16

If you are using Pre-Release system, then please update ASAP to get those updates with yum

Kpackagekit – > apper:

recently kpackagekit moved to apper. Now Fedora 16 has apper as GUI of packagekit for KDE desktop. While new interface has various new feature, but there are still some bug exist (I am tester, so feature you can look here yourself).

Fuzzy Strings in apper:

??? instead of Translation in kpackagekit:

XKB keyboard layouts and IBus:

While integration of IBus with gnome continue in Fedora 16 (from Fedora 15). Fedora 16 has bug for Indic locales that there duplicate entries in IBus Preference menu regarding keyboard layouts like

Hindi Inscript (m17n)

Hindi  – Which is from XKB and basically inscript

So there are two problem:

1) XKB has no detail about layout, it is just saying “HINDI”

2) it is already exist in m17n-contrib and people are using with iBus from long time. So there are two layouts for same purpose.

if you have any comment please update bug report:

It was busy day as Fedora QA team member, there are around 2 new bug files, both were duplicate, Fedora i18 Meeting has great discussion regarding bugs and i18n/translation release-criteria (Fedora i18n Meeting log)

grub2 recovery for Fedora 16


Previously ‘grub’ was installed. With Fedora 16 upgrade I thought to try ‘grub2’. grub and grub2 had package conflict, for which I need to remove ‘grub’ package before installing grub2. After installing grub2, there were few configurations, which I need to made to work it properly (I learnt that later after failing to boot and using rescue mode)

1) install grub2 as following

$ yum remove grub -y

$yum install grub2 –y

2) you need to create grub.cfg file manually with following command (and it is not in /etc/grub(2).cfg)

grub2-mkconfig -o /boot/grub2/grub.cfg

(it detected Windows, Linux (Fedora, Linux Mint) automatically and added to configuration file)

3) install grub2 to MBR

grub2-install /dev/sda

Now it is complete and showing many kernel with Windows and Linux Mint.

Fedora GRUB2 Link

connect virtualization fedora server from ubuntu client

I was trying to access Fedora Virtualization server with qmeu+ssh from Ubuntu client

Server: Fedora 15 (running libvirtd)

Client: virt-manager connect with Server

1) install virt-manager to client

2)  Add connection  (File->Add Connection)

3)  Select ‘connect to Remote Host’ and select ssh with host IP or Address

if you get error like

Unable to open a connection to the libvirt management daemon.

Libvirt URI is: qemu+ssh://root@XX.XX.XX.XX/???

Verify that:
 – The ‘libvirt-bin’ package is installed
 – The ‘libvirtd’ daemon has been started
 – That you have access to ‘/var/run/libvirt/libvirt-sock’

then try following workaround:

ssh-copy-id -i /home/USER/.ssh/ root@XX.XX.XX.XX

(you may need to create Key with ssh-keygen -t rsa)


After doing this you need to DELETE old connection (virt-manager) and Add connection, otherwise it will not work

NetworkManager issues with Fedora 15

Fedora 15 works very well on Sony YB (AMD fusion) laptop, including sound, graphics, network, bluetooth.

After updating NetworkManager from:




to Next update 0.8.999-3:




Fedora Bug: 708445

it is not effecting all machines, but many people reported that same issue.

you need to download packages (on other machine) and update on effected machine.

Another NetworkManager Crashing issue with same version is Bug 708626

lokalize Junk data with qt 4.7.1 – workaround 2 (fedora)

when lokalize crash problem was fixed, then New problem arrived – Junk data in translated field

(check video here)

Steps to Reproduce:
1. run lokalize with translation file (PO file)
2. input something in local language (other than English)
3. Use BackSpace to delete some (not all)
5. Page Down (Move to next string)
6. Page Up (Move back to original String

Actual results:
Junk data inserted in text field automatically, which is not typed

Expected results:
Only Text should be there, which is typed, works fine with BackSpace

KDE bug 249373, kde-i18n mailing list discussion

OpenSUSE, kbuntu and Arch Linux user confirmed that problem.

Fedora workaround for this is below (on Fedora 14):
1) yum remove qt (it will remove whole kde, will not effect much if you are using other than KDE desktop)
2) yum remove kdelibs-common
3) Disable fedora-updates.repo (/etc/yum.repos.d/fedora-updates.repo)  (enabled=0)
4) yum install kdesdk (or other package which you want to install for kde)

Now your lokalize should work normal (qt-4.7.0-3.fc14.x86_64 from fedora 14 Released repo), but note 
that you are not going to get any update for your system (which includes security fixes also)

Nokia provide fix (Crash issue) for qt-4.7.2, but that patch was backport to 4.7.1 for many
distribution. Nobody respond to bug yet (from Nokia).

lokalize crash with qt 4.7.1 – workaround

lokalize is crashing from last few weeks in latest qt-4.7.1

Fedora Bug:

Upstream KDE Bug:

Nokia qt bug:

for Fedora, you need to downgrade your ‘qt’ packages for ‘qt-4.7.0-8′ or eariler,

which you can download from Koji or Simple way is:

$yum downgrade qt*


lokalize is crashing from last few weeks in latest qt-4.7.1.

Fedora Bug:

Upstream KDE Bug:

Nokia qt bug:

for Fedora, you need to downgrade your ‘qt’ packages for ‘qt-4.7.0-8’ or eariler,

which you can download from Koji or Simple way is:

$yum downgrade qt*

meanwhile Kevin Kofler confirm that qt is fixed by upstream (commit). So fix should be available in

fedora soon.