libvirt from 0.7.7 to 0.8.2 in fc13 but no changelog in rpm
by Gianluca Cecchi
Hello,
just to notice that right today running yum I updated my libvirt related
packages from 0.7.7-5 (updated three weeks ago) to 0.8.2-1, but if I run
rpm -q --changelog libvirt I get only:
* Thu Jun 17 2010 Cole Robinson <crobinso(a)redhat.com> - 0.7.7-5.fc13
- Add qemu.conf options for audio workaround
- Fix parsing certain USB sysfs files (bz 598272)
...
While
# rpm -q libvirt
libvirt-0.8.2-1.fc13.x86_64
and
[root@ope46 gcecchi]# rpm -qi libvirt
Name : libvirt Relocations: (not relocatable)
Version : 0.8.2 Vendor: Fedora Project
Release : 1.fc13 Build Date: Mon 12 Jul 2010
05:53:48 PM CEST
Install Date: Wed 28 Jul 2010 08:52:10 AM CEST Build Host:
x86-17.phx2.fedoraproject.org
Group : Development/Libraries Source RPM:
libvirt-0.8.2-1.fc13.src.rpm
Size : 2548396 License: LGPLv2+
Signature : RSA/SHA256, Tue 13 Jul 2010 12:30:56 AM CEST, Key ID
7edc6ad6e8e40fde
Packager : Fedora Project
URL : http://libvirt.org/
Summary : Library providing a simple API virtualization
Description :
Libvirt is a C toolkit to interact with the virtualization capabilities
of recent versions of Linux (and other OSes). The main package includes
the libvirtd server exporting the virtualization support.
Due to the big improvements I thought to inform about this...
Anyway on
http://libvirt.org/news.html
I could find at least upstream changelog related information
Gianluca
13 years, 9 months
gtk library problems?
by Alex
Hi,
I'm running FC13 and when X starts, I see a few errors that I hoped
someone could help me troubleshoot:
(deja-dup-monitor:13186): GLib-GObject-CRITICAL **: g_value_get_uint: assertion
`G_VALUE_HOLDS_UINT (value)' failed
(polkit-gnome-authentication-agent-1:13183): GLib-GObject-WARNING **:
cannot register existing type `_PolkitError'
(polkit-gnome-authentication-agent-1:13183): GLib-CRITICAL **:
g_once_init_leave: assertion `initialization_value != 0' failed
(Pandora:13201): Gtk-WARNING **: Unable to locate theme engine in
module_path: "clearlooks",
The last one is from Pandora, the music application, which uses Adobe
Air. Perhaps it's related to that?
What is the 'libpk-gtk-module.so' module?
Gtk-Message: Failed to load module "pk-gtk-module":
libpk-gtk-module.so: cannot open shared object file: No such file or
directory
Gtk-Message: Failed to load module "canberra-gtk-module":
libcanberra-gtk-module.so: cannot open shared object file: No such
file or directory
** (nm-applet:13216): WARNING **: get_all_cb: couldn't retrieve system
settings properties: (2) The name
org.freedesktop.NetworkManagerSystemSettings was not provided by any
.service files.
changeLocale: *Default Language* != English (United States). Searching
without country..
changeLocale: Searching for language English in *any* country..
changeLocale: no message properties for Locale 'English (United
States)' (en_US), using 'English (default)'
(npviewer.bin:13923): Gtk-WARNING **: Unable to locate theme engine in
module_path: "clearlooks",
Am I missing some libraries?
Thanks,
Alex
13 years, 9 months
yum update problem?
by Richard Shaw
I was just updating and saw the following:
Updating : nautilus-2.30.1-4.fc13.x86_64 15/72
WARNING: failed to parse type name `boolean'
WARNING: invalid or missing type for schema
(/schemas/apps/nautilus/preferences/navigation_window_saved_maximized)
Is this a problem or something that can be safely ignored?
Thanks,
Richard
13 years, 9 months
Re: securing a fedora 12 pc on a lan
by James McKenzie
Steve Searle <steve(a)stevesearle.com> wrote:
>Sent: Jul 27, 2010 1:38 PM
>To: Community support for Fedora users <users(a)lists.fedoraproject.org>
>Subject: Re: securing a fedora 12 pc on a lan
>
>Around 06:32pm on Tuesday, July 27, 2010 (UK time), mike lan scrawled:
>
>> I've installed a Fedora 12 kde live cd on a local area network, that I want
>> to keep safe from hacking
>> ( specially from network admin. !!)
Not a good idea. This could be contrary to your company's IT policy.
>> Is a default fedora 12 install secure enough ?
>> or do i still take some measures to secure the pc ?
>
>It sounds like you are doing something that is probably contrary to your
>employers IT policy, but if you are concerned then unplug the network cable.
>
Honey Pot maybe....
James McKenzie
13 years, 9 months
Screensaver no longer working
by Jackson Byers
$ uname -r
2.6.32.14-127.fc12.i686.PAE
After a power-glitch in my home, my Screensaver is no longer working.
The power-glitch was very slight-- it didnt turn off my desktop.
System > Preferences > Screensaver
slider for "Regard the computer as idle after:"
variously set, from 1min to 17 min, nothing works.
both of following checked
Activate screensaver when computer is idle
lock screen when screensaver is active
I also run dpms, from xset -q:
DPMS (Energy Star):
Standby: 1200 Suspend: 1800 Off: 2400
DPMS is Enabled
Monitor is On
I have tried setting dpms to 0 0 0, no help on Screensaver.
Previously both the screensaver and dpms were working, now only dpms.
Any ideas?
Any CLI instead of the gui?
Jack
13 years, 9 months
Re: Thinkpad A22p/Improper Video on Install
by James McKenzie
JB <jb.123abc(a)yahoo.com> wrote:
>Sent: Jul 27, 2010 12:58 PM
>To: users(a)lists.fedoraproject.org
>Subject: Re: Thinkpad A22p/Improper Video on Install
>
>James Mckenzie <jjmckenzie51 <at> earthlink.net> writes:
>
>>
>> STOOPID question time from a long time Linux/UNIX sysadmin:
>>
>> How do I select the VESA video driver at the wonderful install screen?
>>
>> I don't readily see the ability to do this. Maybe I'm missing something.
>>
>> If it's in the docs, give me a section, I can read it myself and is a 'best
>left as an exercise for the student' :)
>>
>is that what you are asking about ?
>http://fedoraproject.org/wiki/Common_F13_bugs
>5 Hardware-related issues.
>Miscellaneous graphical problems.
>To use the vesa driver during installation, ...
Exactly. Thank you for the link and the fine reading opportunity.
Now to run the Live CD tonight.
If this works, onward to installing FC13.
James McKenzie
13 years, 9 months
f1 / firefox 3.5.9 / cnn news / markets.
by Reg Clemens
Starting yesterday (26July), I am having problems with Firefox 3.5.9
and CNN.news.
At the right of the display there are a number of options for subdisplays,
including the line 'Markets'.
In the past, this line has been expanded, and I see the market reports.
If not expanded I can click on it to open it.
As of yesterday the damn thing is dead.
Nothing I can do will open this line.
There seem to be some comments about 'logging in', but Ive tried this and
the damn thing is still dead.
Anyone else seeing this?
What is the solution?
I can go in the other room and check the market reports on the TV,
but I like seeing them while Im in CNN News.
--
Reg.Clemens
reg(a)dwf.com
13 years, 9 months
re: preupgrade failure problem with swap Solved
by Don Vogt
> ------------------------------
>
> Message: 15
> Date: Tue, 27 Jul 2010 09:10:30 +0000 (UTC)
> From: JB <jb.123abc(a)yahoo.com>
> Subject: fc13 preupgrade failure on swap
> To: users(a)lists.fedoraproject.org
> Message-ID: <loom.20100727T105136-975(a)post.gmane.org>
> Content-Type: text/plain; charset=us-ascii
>
> Don Vogt <dnvot <at> yahoo.com> writes:
>
> >
> > I have been using fedora since fedora 4 with great
> satisfaction. I tried to
> > do an fc12 to fc13 preupgrade. All
> > went fine until I was running anaconda ( I believe)
> with the install.img.
> > I got a pop-up that said the swap
> > device has not been created and that " The /etc/fstab
> on your upgrade
> > partition does not reference a valid
> > swap device" When I click OK the system reboots and
> the upgrade fails.
> > I have checked my swaps in the fc12 system and
> they seem OK, Top shows
> > the swap partitions are there " I
> > actually have three swap partition on two different
> drives. I checked
> > the swaps in fstab on fc12 using
> > findfs and they seem OK, UIIDs and /dev entries. I
> suspect that the upgrade
> > partition it refers to is in the install.img.
> > I have another partition with fc13, on which I
> used preupgrade to upgrade
> > from fc12 It was a very smooth procedure. That kind of
> rules out hard drive
> > problems. Unless something changed.
> > Does anyone have a suggestion on how to fix fstab, or
> what the problem
> > might be?
> > Also, is there a way to undo the preupgrade attempt,
> so I can try again?
> > Any other suggestions will be welcome.
> >
> Hi,
> please give us more info (do not cut/edit the output).
>
> Layout of both disks:
> # fdisk -l /dev/sda
> # fdisk -l /dev/sdb
>
> For F12 (the one you try to preupgrade) log in and get an
> output:
> # cat /etc/fstab
> For F13 (the one you already preupgrade-ed) log in and get
> an output:
> # cat /etc/fstab
>
> By the way:
> when you run preupgrade the next time (2nd, 3rd, etc) you
> are asked whether
> you want to continue from the point of previous
> stop/failure point or from
> the very beginning.
> IMPORTANT: I would advise you to stop changing anything on
> your machine (disk
> layout, swaps, /etc/fstab, etc) so that the data I ask you
> for above is true
> from that point on and we can help you !
> JB
>
>
>
>
> ------------------------------
>
I found an easy solution and completed the preupgrade last night.
First i tried adding a swap file, because the message said my fstab does not have a valid swap file. I thought it might be making a distinction between swap partitions and a swap file. That didn't make any difference.
I then commented out my swap partitions in the fc12 fstab and tried preupgrade again and it worked.
Sorry, I didn't get your message about not changing things until this morning.
In case you still want here are the outputs you asked for
sudo fdisk -l
Disk /dev/sda: 13.6 GB, 13601193984 bytes
255 heads, 63 sectors/track, 1653 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000bbbf3
Device Boot Start End Blocks Id System
/dev/sda1 * 1 261 2096451 6 FAT16
/dev/sda2 262 1653 11181240 f W95 Ext'd (LBA)
/dev/sda5 262 522 2096451 6 FAT16
/dev/sda6 523 783 2096451 6 FAT16
/dev/sda7 784 1000 1743021 6 FAT16
/dev/sda8 1001 1576 4626688+ 83 Linux
/dev/sda9 1621 1653 265041 82 Linux swap / Solaris
Disk /dev/sdb: 4303 MB, 4303272960 bytes
255 heads, 63 sectors/track, 523 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c786b
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 409 3285261 83 Linux
/dev/sdb2 410 523 915705 82 Linux swap / Solaris
Disk /dev/sdc: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d0450
Device Boot Start End Blocks Id System
/dev/sdc1 1 127 1020096 83 Linux
/dev/sdc2 128 2677 20482875 b W95 FAT32
/dev/sdc3 2678 6501 30716280 83 Linux
/dev/sdc4 6502 19237 102301920 5 Extended
/dev/sdc5 6502 10325 30716248+ 83 Linux
/dev/sdc6 10326 10580 2048256 82 Linux swap / Solaris
/dev/sdc7 * 10581 18987 67529196 83 Linux
/dev/sdc8 18988 19237 2008093+ 82 Linux swap / Solaris
from the upgraded system.
cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Tue Jul 27 05:06:07 2010
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=0c1a3c8c-1564-4b4a-979e-31f46199079e / ext3 defaults 1 1
UUID=3ab5d70f-8de3-4eaf-b30c-83a477bc4797 swap swap defaults 0 0
UUID=33a1e0cd-06cb-4e79-883d-f1ccf50e73c6 swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
13 years, 9 months
Gnome top bar apperance changed F13 updates
by Andrew Gray
I Just applied the latest F13 update and logged out and back-in
The Gnome top bar now appears to be too small showing underlines under
bar items
Yum.log tail
Jul 27 09:01:03 Updated: dbus-glib-0.86-3.fc13.x86_64
Jul 27 09:01:04 Updated: libuuid-2.17.2-6.fc13.x86_64
Jul 27 09:01:05 Updated: coreutils-libs-8.4-8.fc13.x86_64
Jul 27 09:01:09 Updated: coreutils-8.4-8.fc13.x86_64
Jul 27 09:01:10 Updated: libXext-1.1.2-2.fc13.x86_64
Jul 27 09:01:11 Updated: clutter-1.2.10-1.fc13.x86_64
Jul 27 09:01:12 Updated: 1:NetworkManager-glib-0.8.1-1.fc13.x86_64
Jul 27 09:01:13 Updated: perl-Git-1.7.2-1.fc13.noarch
Jul 27 09:01:18 Updated: git-1.7.2-1.fc13.x86_64
Jul 27 09:01:20 Updated: mysql-libs-5.1.48-2.fc13.x86_64
Jul 27 09:01:23 Updated: libvirt-client-0.8.2-1.fc13.x86_64
Jul 27 09:01:24 Updated: poppler-0.12.4-5.fc13.x86_64
Jul 27 09:01:26 Updated: mysql-5.1.48-2.fc13.x86_64
Jul 27 09:01:30 Updated: 1:NetworkManager-0.8.1-1.fc13.x86_64
Jul 27 09:01:31 Updated: libchamplain-0.4.6-1.fc13.x86_64
Jul 27 09:01:35 Updated: xulrunner-1.9.2.7-2.fc13.x86_64
Jul 27 09:01:44 Updated: nautilus-2.30.1-4.fc13.x86_64
Jul 27 09:01:45 Updated: nautilus-extensions-2.30.1-4.fc13.x86_64
Jul 27 09:01:46 Updated: libblkid-2.17.2-6.fc13.x86_64
Jul 27 09:01:49 Updated: setroubleshoot-server-2.2.91-1.fc13.x86_64
Jul 27 09:01:50 Installed: ebtables-2.0.9-5.fc13.x86_64
Jul 27 09:01:53 Updated: libvirt-0.8.2-1.fc13.x86_64
Jul 27 09:01:59 Updated: setroubleshoot-2.2.91-1.fc13.x86_64
Jul 27 09:02:03 Updated: util-linux-ng-2.17.2-6.fc13.x86_64
Jul 27 09:02:12 Updated: xulrunner-devel-1.9.2.7-2.fc13.x86_64
Jul 27 09:02:14 Updated: libchamplain-gtk-0.4.6-1.fc13.x86_64
Jul 27 09:02:22 Updated: 1:NetworkManager-gnome-0.8.1-1.fc13.x86_64
Jul 27 09:02:26 Updated: mysql-server-5.1.48-2.fc13.x86_64
Jul 27 09:02:27 Updated: poppler-glib-0.12.4-5.fc13.x86_64
Jul 27 09:02:27 Updated: poppler-utils-0.12.4-5.fc13.x86_64
Jul 27 09:02:28 Updated: libvirt-python-0.8.2-1.fc13.x86_64
Jul 27 09:02:36 Updated: gthumb-2.11.5-1.fc13.x86_64
Jul 27 09:02:38 Updated: dbus-glib-devel-0.86-3.fc13.x86_64
Jul 27 09:02:41 Updated: libpurple-2.7.2-1.fc13.x86_64
Jul 27 09:02:42 Updated: libisofs-0.6.34-1.fc13.x86_64
Jul 27 09:02:43 Updated: 1:cpuspeed-1.5-14.fc13.x86_64
Jul 27 09:02:44 Updated: libuuid-2.17.2-6.fc13.i686
Jul 27 09:02:44 Updated: libXext-1.1.2-2.fc13.i686
Jul 27 09:02:45 Updated: dbus-glib-0.86-3.fc13.i686
Jul 27 09:02:46 Updated:
liberation-fonts-common-1.06.0.20100721-1.fc13.noarch
Jul 27 09:02:47 Updated: flex-static-2.5.35-11.fc13.x86_64
Jul 27 09:02:48 Updated: flex-2.5.35-11.fc13.x86_64
Jul 27 09:02:50 Updated:
liberation-serif-fonts-1.06.0.20100721-1.fc13.noarch
Jul 27 09:02:53 Updated:
liberation-mono-fonts-1.06.0.20100721-1.fc13.noarch
Jul 27 09:02:56 Updated:
liberation-sans-fonts-1.06.0.20100721-1.fc13.noarch
Jul 27 09:02:57 Updated: git-email-1.7.2-1.fc13.noarch
Jul 27 09:02:58 Updated: libXext-devel-1.1.2-2.fc13.x86_64
Jul 27 09:02:58 Updated: libuuid-devel-2.17.2-6.fc13.x86_64
Jul 27 09:03:08 Updated: google-chrome-stable-5.0.375.125-53311.x86_64
The Gnome top bar now appears to be too small showing underlines under
bar items :-
http://www.linnetsol.co.uk/images/Gnome-topbar.png
Kernel = 2.6.33.6-147.fc13.x86_64 #1 SMP
I use "radeon" graphic driver 1920 x 1200
--Andrew Gray
13 years, 9 months
fc13 preupgrade failure on swap
by Don Vogt
I have been using fedora since fedora 4 with great satisfaction. I tried to do an fc12 to fc13 preupgrade. All went fine until I was running anaconda ( I believe) with the install.img. I got a pop-up that said the swap device has not been created and that " The /etc/fstab on your upgrade partition does not reference a valid swap device" When I click OK the system reboots and the upgrade fails.
I have checked my swaps in the fc12 system and they seem OK, Top shows the swap partitions are there " I actually have three swap partition on two different drives. I checked the swaps in fstab on fc12 using findfs and they seem OK, UIIDs and /dev entries. I suspect that the upgrade partition it refers to is in the install.img.
I have another partition with fc13, on which I used preupgrade to upgrade
from fc12 It was a very smooth procedure. That kind of rules out hard drive problems. Unless something changed.
Does anyone have a suggestion on how to fix fstab, or what the problem might be?
Also, is there a way to undo the preupgrade attempt, so I can try again?
Any other suggestions will be welcome.
13 years, 9 months