F7 to F8 upgrade - Anaconda nightmare
by Timothy Murphy
I tried upgrading a ThinkPad T43 from Fedora 7 to 8
and met the familiar hanging syndrome.
I followed the recipe
at <http://fedoraproject.org/wiki/Bugs/F8Common>,
downloading
<http://katzj.fedorapeople.org/updates-f8-yumloop.img>
and appending "updates" to the kernel command.
The latter seemed to work, since /tmp/updates
contained the updates*.img file
(and all other files in the same directory).
However, I saw no evidence that the updates*.img file
was actually invoked.
In any case, the hanging was not cured.
I wondered how anaconda knows which file to use to update?
Does it use all *.img files?
Is one meant to change the name of the downloaded file?
As far as I can tell, Anaconda upgrade has not worked
for most people - it worked for me on one computer,
but not on a second.
This is not good;
if the developers cannot get anaconda to upgrade reasonably well
they should remove the option.
As a practical matter, I did not see any way
of determining what exactly anaconda was doing
during the eternal "Checking dependencies ...".
If one knew it was stuck checking dependencies on one file
it would be easy to tell that the process had failed.
As it is, there seems to be no way of knowing
except to wait for several hours.
Anaconda: 1 out of 10.
16 years, 4 months
yum install sane-backends-libs fails
by Chris G
I want to install sane-backends-libs but it fails because of conflicts
between the 32-bit and 64-bit versions, I want both versions, how can
I force the install?
I suspect the errors are irrelevant:-
Transaction Check Error:
file /usr/share/locale/de/LC_MESSAGES/libexif-12.mo from install of
libexif-0.6.15-2.fc7 conflicts with file from package libexif-0.6.13-3.fc7
file /usr/share/locale/es/LC_MESSAGES/libexif-12.mo from install of
libexif-0.6.15-2.fc7 conflicts with file from package libexif-0.6.13-3.fc7
file /usr/share/locale/fr/LC_MESSAGES/libexif-12.mo from install of
libexif-0.6.15-2.fc7 conflicts with file from package libexif-0.6.13-3.fc7
file /usr/share/locale/pl/LC_MESSAGES/libexif-12.mo from install of
libexif-0.6.15-2.fc7 conflicts with file from package libexif-0.6.13-3.fc7
--
Chris Green
16 years, 4 months
pptpconfig, where from?
by Paul Smith
Dear All,
I have asked in the pptp client list for updating the repository of
pptpconfig for F8, but no reply until now. Is there some other
repository with pptpconfig for F8?
Thanks in advance,
Paul
16 years, 4 months
Re: F8 Sound problems
by Steve Blackwell
---- Abhijit Shylanath <abhijit.shylanath(a)gmail.com> wrote:
> > I have tried enabling everything but the only option that gave my any noticable difference in sound was when I enabled "analog Mix". I could discern a slightly louder background noise.
>
> Hm. I'm not really the expert here, but my guess is that it's just a
> problem with the mixer using digital output when you have an analog
> card. Try toggling "Analog/digital output' in alsamixer.
How do you do that?
> You may have
> to use 'alsamixer -c 1' if you have an onboard card. Press F5 to
> enable all channels, and then look for that channel. Press m to
> toggle. While you're there, you may also want to blindly turn
> everything up (so that it's at around and below 75).
>
I tried alsamixer -c 1 which gets the built-in Intel sound chip and I tried alsamixer -c 0 which gets my Audigy card. Everything was enabled and the volumes looked good.
> Also, I realize now that the Audigy has a different driver from the
> Live!, so your outputs will be labelled differently.
16 years, 4 months
Can't set valid fonts in NEdit (Fedora 8)
by wwp
Hello all,
I've just installed Fedora 8 from scratch on a D810 laptop, then
migrated my personal files and config elements from my previous FC5
system.
Running NEdit shows unexpected fonts (and thus, size of window is way
too wide). If I try to edit NEdit's font settings, apparently there are
some fonts in the list, but they are invisible. Those invisible font
items in list seem sensitive, and if I click any one, I get an error:
"Invalid Font Specification".
Note: I'm running GNOME and apart from the "Look and Feel/Appearance"
font settings, I did not changed anything related to font settings
anywhere.
Am I missing some fonts packages or whatever?
Regards,
--
wwp
16 years, 4 months
Removing locales
by Matthieu Pupat
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
How can I remove the locales in /usr/share/locales. This uses 300++ M of
my disk and I do not need it.
I tried to go in Add/Remove software and removed some but the apply
button will remove grayed.
Thanks,
Matthieu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHUbJ3xNNzQwmqmn0RAkZRAKCNVNzHHy8z9p39ucW5L65YzntFkQCgqBwv
k4J+aqXcJCmyDP5V6gZG/No=
=vr33
-----END PGP SIGNATURE-----
16 years, 4 months
How to specify specific version etc. in yum
by Chris G
The yum man page doesn't seem to say how to specify specific versions
of a package, it just says:-
yum [options] [command] [package ...]
and expands on the options and command but not on the package. How
does one specify a 32-bit or 64-bit package and how does one specify a
particular version (for example for removing an older version of a
package)?
--
Chris Green
16 years, 4 months
What does this (error) message mean?
by clemens＠dwf.com
What does this error message mean?
crond[13121]: pam_loginuid(crond:session): set_loginuid failed opening
loginuid: 1 Time(s)
Who is issueing it?
Should I be worried about this?
Does it (just) mean something is missing (what?)?
I seem to see it about 40times in a given Logwatch output?
Any and all thoughts appreciated.
This is Fedora6 with a 2.6.23.1 kernel.
--
Reg.Clemens
reg(a)dwf.com
16 years, 4 months
broken yum after latest yum update
by Konstantin Svist
After updating my F8 install with "yum update" I can't run yum anymore.
Here's the error I get:
"""
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:
/usr/lib/python2.5/lib-dynload/cPickle.so: undefined symbol:
PyUnicodeUCS4_DecodeRawUnicodeEscape
Please install a package which provides this module, or
verify that the module is installed correctly.
It's possible that the above module doesn't match the
current version of Python, which is:
2.5 (trunk, Nov 28 2007, 11:58:41)
[GCC 4.1.2 20070925 (Red Hat 4.1.2-33)]
If you cannot solve this problem yourself, please go to
the yum faq at:
http://wiki.linux.duke.edu/YumFaq
"""
It doesn't look like anyone else has this problem (or I would've seen
other reports..)
Running python in command line and importing cPickle doesn't work
(same/similar error).
I've tried reinstalling python from fedora rpm (same version) - to no avail.
SELinux is running in permissive mode (meaning it should not have
blocked anything while I was performing the yum update). There *was*
some error/warning message in yum - something to do with some selinux
flag no longer being used, but that's all.
Another clue: I've installed a self-compiled python in /usr/local.
However, I was careful to not make it conflict with the built-in
version: I used the configure option to give the executable a suffix (so
the executable has to be called as "python.foobar" instead of just
"python"). I've verified that running the different python installs used
different lib directories (so that should not have been a problem.)
I've also tried running my custom python and importing cPickle - that
works without a problem.
Any ideas?
I guess I could just replace cPickle.so with the custom-built one, but
I'm not sure that's the best course of action...
Will it even be compatible? I probably used compile flags different from
default.
16 years, 4 months
