libedataserver dependency problem
by Michael Hannon
Greetings. I hope this doesn't distract anyone from the discussion of top
posting, but I'm getting a dependency problem when doing a yum update on a
freshly-installed, f13, x86_64 system.
Basically, it appears that some of the gnome applications require a version of
libedataserver that is older than the one that is currently installed. Please
see the appended for details.
I haven't done much tweaking of this system and none at all that would affect
the gnome applications.
Any suggestions?
Thanks.
-- Mike
# yum update
Loaded plugins: presto, refresh-packagekit
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package empathy.x86_64 0:2.30.1.1-1.fc13 set to be updated
---> Package evolution.x86_64 0:2.30.2-1.fc13 set to be updated
--> Processing Dependency: libedataserver-1.2.so.11()(64bit) for package:
gnome-panel-2.30.0-1.fc13.x86_64
--> Processing Dependency: libedataserver-1.2.so.11()(64bit) for package:
empathy-2.30.1.1-1.fc13.x86_64
--> Processing Dependency: libedataserver-1.2.so.11()(64bit) for package:
nautilus-sendto-2.28.4-1.fc13.x86_64
---> Package evolution-data-server.x86_64 0:2.30.2-2.fc13 set to be updated
---> Package evolution-data-server-devel.x86_64 0:2.30.2-2.fc13 set to be
updated
---> Package evolution-help.noarch 0:2.30.2-1.fc13 set to be updated
--> Finished Dependency Resolution
Error: Package: gnome-panel-2.30.0-1.fc13.x86_64
(@anaconda-InstallationRepo-201005130101.x86_64)
Requires: libedataserver-1.2.so.11()(64bit)
Removing: evolution-data-server-2.30.1-2.fc13.x86_64
(@anaconda-InstallationRepo-201005130101.x86_64)
Error: Package: empathy-2.30.1.1-1.fc13.x86_64 (updates)
Requires: libedataserver-1.2.so.11()(64bit)
Removing: evolution-data-server-2.30.1-2.fc13.x86_64
(@anaconda-InstallationRepo-201005130101.x86_64)
Error: Package: nautilus-sendto-2.28.4-1.fc13.x86_64
(@anaconda-InstallationRepo-201005130101.x86_64)
Requires: libedataserver-1.2.so.11()(64bit)
Removing: evolution-data-server-2.30.1-2.fc13.x86_64
(@anaconda-InstallationRepo-201005130101.x86_64)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
13 years, 11 months
Unexplained temporary freezes in Thunderbird Fedora 13
by Jerry Feldman
In the past, Thunderbird would freeze temporarily while waiting to
obtain a GPG key or to load some graphics. However in Thunderbird 3.04
on Fedora 13 (x86_64) I'm seeing some issues where the screen goes dark,
even while I am composing. After a short while, it cathes up. My system
is an x86_64 system with 6GB RAM and an AMD quad core processor. I have
2 sources I get email from, (1) gmail via IMAP, (2) my ISP via POP.
AFAIK, Thunderbird downloads new email in the background, and has not
affected the performance. What is annoying is that this freeze occurs
while composing email, so that the other things, like waiting for a GPG
key to be downloaded or waiting for a very large email body to display
is not in play. I'm looking to see if anyone else is experiencing
similar issues for corroboration purposes. For instance, I encountered
it this morning before leaving for work. My system was relatively idle
with firefox and Gnome-terminal running. I think I had about 3
relatively non-dynamic websites on firefox at the time.
--
Jerry Feldman <gaf(a)blu.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
13 years, 11 months
Error Messages when openning Firefox.
by Jim
FC12/KDE
When starting Firefox I get this Error message below, The same error
message in /home/user or /root desktops when starting Firefox.
I deleted /.mozilla folder in /home/user and put Bookmarks back in
/.mozilla and still got the same Error message below.
Where and how do I fix this problem ??
Error Message;
security features.Could not initialize the application's security component. The most likely cause is problems with files in
your application's profile directory. Please check that this directory has no read/write restrictions and
your hard disk is not full or close to full. It is recommended that you exit the application and fix
the problem. If you continue to use this session, you might see incorrect application behaviour when accessing
I checked hard drive and it is not full, it has 75% free space in / and /home
13 years, 11 months
Firefox got better...
by Tom Horsley
A while back I noticed that all flash content flickered
something horrible when I scrolled the firefox window contents.
I wondered if the problem was flash, or firefox, or
ATI driver, but had no way to tell for sure. (This started
happening on Fedora 13 - it wasn't a problem on Fedora 12).
Today I just noticed that since the updates I got on
June 24th, the horrible flicker has disappeared. Flash
content scrolls smoothly just like all other content.
Since that update didn't include a new ATI driver or
flash update, I guess it really was a firefox problem
which has now been fixed.
So, if anyone else has noticed flash flashing them,
get the firefox update :-).
13 years, 11 months
F13 udev rule boot warning messages
by linux guy
I'm getting this in my otherwise clean boot log. What, if anything, do
I need to do about them ?
Thanks
Starting udev: udevd[491]: BUS= will be removed in a future udev
version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS=
to match a parent device, in /etc/udev/rules.d/85-pcscd_egate.rules:3
udevd[491]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /etc/udev/rules.d/85-pcscd_egate.rules:3
udevd[491]: BUS= will be removed in a future udev version, please use
SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent
device, in /etc/udev/rules.d/85-pcscd_egate.rules:5
udevd[491]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /etc/udev/rules.d/kino.rules:11
udevd[491]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /etc/udev/rules.d/kino.rules:13
udevd[491]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /etc/udev/rules.d/kino.rules:15
udevd[491]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /etc/udev/rules.d/kino.rules:17
udevd[491]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /etc/udev/rules.d/kino.rules:19
udevd[491]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /etc/udev/rules.d/kino.rules:21
udevd[491]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /etc/udev/rules.d/kino.rules:23
udevd[491]: SYSFS{}= will be removed in a future udev version, please
use ATTR{}= to match the event device, or ATTRS{}= to match a parent
device, in /etc/udev/rules.d/kino.rules:25
13 years, 11 months
32-bit upgrade fails on Thinkpad
by Robert G. (Doc) Savage
I'm hoping this is a known problem with an easy work-around. It looks
like an RPM versioning problem of some sort, but I'm not 100% sure.
I have a rusty trusty old IBM Thinkpad A22p with a 32-bit PIII/M
processor and 512MB. I've tried F12->F13 upgrades from ISO images on
local hard drive (/dev/sdb1), an nfs mount, and on a local DVD that
tests OK. The only change I've made to a bone stock installation is to
append "vesa" to the Install/Upgrade command line to deal with an
uncooperative ATI video.
All of these upgrade attempts fail when I click on Next at the boot
loader dialog screen:
[X] Install boot loader on /dev/sda. [Change device]
[ ] Use a boot loader password
Boot loader operating system list
Default Label Device
(*) Fedora /dev/sda2
The error is:
"An unhandled exception has occurred. This is
most likely a bug. Please save a copy of the
detailed exception and file a bug report."
The saved Details file is quite large (5731 lines, 400K). Its first 23
lines are:
anaconda 13.42 exception report
Traceback (most recent call first):
File "/usr/lib/python2.6/site-packages/yum/config.py", line 944, in _getsysver
idx = ts.dbMatch('provides', distroverpkg)
File "/usr/lib/python2.6/site-packages/yum/config.py", line 834, in readStartupConfig
startupconf.releasever = _getsysver(startupconf.installroot, startupconf.distroverpkg)
File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 255, in _getConfig
startupconf = config.readStartupConfig(fn, root)
File "/usr/lib/anaconda/yuminstall.py", line 664, in doConfigSetup
YumSorter._getConfig(self)
File "/usr/lib/anaconda/yuminstall.py", line 361, in setup
self.doConfigSetup(root=self.anaconda.rootPath)
File "/usr/lib/anaconda/yuminstall.py", line 1155, in doBackendSetup
self.ayum.setup()
File "/usr/lib/anaconda/backend.py", line 282, in doBackendSetup
if anaconda.backend.doBackendSetup(anaconda) == DISPATCH_BACK:
File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
self.moveStep()
File "/usr/lib/anaconda/gui.py", line 1313, in nextClicked
self.anaconda.dispatch.gotoNext()
error: rpmdb open failed
I'm re-using the existing hard drive layouts:
Data Storage Devices Install Target Devices
Model Capacity Boot Model Capacity
ATA IC25N080ATMR04-0 76319 MB -> ( ) ATA IC25N080ATMR04-0 76319 MB
ATA ST9120821A 114473 MB (*) ATA ST9120821A 114473 MB
Please Select A Device
Size Mount Point/
Device (MB) RAID/Volume Type Format
Hard Drives
sda
sda1 300 /boot ext4
sda2 113146 / ext4
sda3 1024 swap
sdb
sdb1 76316 /pub ext3
After saving the Details to a file on /mnt/sysimage/pub
(actually /dev/sdb1) and exit the installer, I see the following text:
Running anaconda 13.42, the Fedora system installer - please wait
02:31:42 Starting graphical installation
rpmdb: Program version 4.8 doesn't match environment version 4.7
error: db3 error(-30971) from dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch
error: cannot open Packages index using db3 - (-30971)
error: cannot open Packages database in /mnt/sysimage/var/lib/rpm
install exited abnormally [1/1]
The system will be rebooted when you presss Ctrl-C or Ctrl-Alt-Delete
I've tried deleting and rebuilding the RPM database, but the error keeps
coming back.
--Doc Savage
Fairview Heights, IL
13 years, 11 months
uuid -> /dev/sdx partition resize
by Robert Arkiletian
I have 1 drive /dev/sda (which is actually a hardware raid 10 array
but Fedora doesn't know that)
I want to resize my partitions bigger.
Going to use Clonezilla to make an image of each partition and save it
on another box.
Then re-partition and format new bigger partitions.
Then restore images with Clonezilla.
But I know UUID's will be wrong and I don't feel like creating new
ones. I just want to use /dev/sdx
Am I correct in assuming I only need to edit /etc/fstab and /etc/grub.conf
or is there anything else I need to edit?
--
Robert Arkiletian
Eric Hamber Secondary, Vancouver, Canada
13 years, 11 months
OT: NIS to LDAP/AD advise
by Jamie Bohr
Hello All,
Sorry this is off-topic but I would like some advise from this list and
possibly get an understanding of what other large organizations are doing
for UNIX/Linux authentication management.
I am a Senior Administrator for 3000 UNIX/Linux based devices ranging from
HP-UX 10.20-11.31, Solaris 8-10 and RHEL 3-5 at 40 different sites. Most
are using NIS for authentication (separate NIS domains) and the AMD
(am-utils) automounter. I would like to move authentication to LDAP (AD
would be better) but before I invest a lot of time and effort I would like
advise from this list on what direction I should go.
Because some of the devices are NOT capable of using LDAP (or AD) for
authentication I will need to keep NIS around until they can be removed from
the environment. If I move to LDAP I would like as much put into LDAP as
possible including Netgroup, automounter maps and sudo permissions.
A few questions:
1. Do you manage a multi-site, multi-geography environment using LDAP?
1. If so, what LDAP version do you use?
2. Do you keep automounter maps in LDAP?
3. Do you keep netgroups in LDAP?
4. Do you have SUDO information in LDAP?
5. Do you support OSes other than Linux with LDAP?
1. If so, what OSes and version, i.e.: HP-UX 11.23, ...
2. Would Fedora Directory server, FreeIPA or something else be the way
to go?
3. Any advice on resolving over lapping UIDs/GIDs?
4. Have anyone used Likewise (or something like it) to authenticate of an
AD domain?
--
Jamie Bohr
13 years, 11 months
Yum update
by Mike Guilmot
Getting errors when trying to update F13
Can't seem to find out which one is giving the problem. Anybody has an idea ?
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package ekiga.i686 0:3.2.7-2.fc13 set to be updated
---> Package empathy.i686 0:2.30.2-2.fc13 set to be updated
--> Processing Dependency: libedataserver-1.2.so.11 for package:
ekiga-3.2.7-2.fc13.i686
--> Processing Dependency: libedataserver-1.2.so.11 for package:
gnome-panel-2.30.0-2.fc13.i686
--> Processing Dependency: libedataserver-1.2.so.11 for package:
nautilus-sendto-2.28.4-1.fc13.i686
--> Processing Dependency: libedataserver-1.2.so.11 for package:
empathy-2.30.2-2.fc13.i686
---> Package evolution-data-server.i686 0:2.30.2-2.fc13 set to be updated
---> Package gnome-panel.i686 0:2.30.0-2.fc13 set to be updated
---> Package gnome-panel-devel.i686 0:2.30.0-2.fc13 set to be updated
---> Package gnome-panel-libs.i686 0:2.30.0-2.fc13 set to be updated
--> Finished Dependency Resolution
Error: Package: nautilus-sendto-2.28.4-1.fc13.i686
(@anaconda-InstallationRepo-201005130056.i386)
Requires: libedataserver-1.2.so.11
Removing: evolution-data-server-2.30.1-3.fc13.i686 (@updates-testing)
Available: evolution-data-server-2.30.1-2.fc13.i686 (fedora)
Error: Package: ekiga-3.2.7-2.fc13.i686 (updates-testing)
Requires: libedataserver-1.2.so.11
Removing: evolution-data-server-2.30.1-3.fc13.i686 (@updates-testing)
Available: evolution-data-server-2.30.1-2.fc13.i686 (fedora)
Error: Package: empathy-2.30.2-2.fc13.i686 (updates-testing)
Requires: libedataserver-1.2.so.11
Removing: evolution-data-server-2.30.1-3.fc13.i686 (@updates-testing)
Available: evolution-data-server-2.30.1-2.fc13.i686 (fedora)
Error: Package: gnome-panel-2.30.0-2.fc13.i686 (updates-testing)
Requires: libedataserver-1.2.so.11
Removing: evolution-data-server-2.30.1-3.fc13.i686 (@updates-testing)
Available: evolution-data-server-2.30.1-2.fc13.i686 (fedora)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
locate libedataserver-1.2.so.11 gives:
/usr/lib/libedataserver-1.2.so.11
/usr/lib/libedataserver-1.2.so.11.0.1
TIA.
--
KR,
Mike
13 years, 11 months