Re: Kyum: /var/log/yum.log, could not be opened for reading.
by ron
On Sun, 2006-07-02 at 15:24 -0400
ron wrote:
>>>> Hello,
>>>> Kyum says "/var/log/yum.log could not be opened for reading.".
>>>> I can view the yum.log outside of kyum.
>>>> Can anyone help?
>>>> -ron-
ON Mon, 03 Jul 2006 08:56:32 +0100
Paul wrote:
>>> If you have SELinux in enforcing mode, what's the output of:
>>> # ls -lZ /var/log/yum.log $(which kyum)
>>> Paul.
On Mon, 03 Jul 2006 09:54:17 -0400
ron wrote:
>> Paul,
>> SELinux is in enforcing mode.
>> The output of:
>> # ls -lZ /var/log/yum.log $(which kyum)
>> IS:
>> [root corefive ~]# ls -lZ /var/log/yum.log $(which kyum)
>> -rwxr-xr-x root root system_u:object_r:bin_t /usr/bin/kyum
>> -rw------- root root system_u:object_r:rpm_log_t
/var/log/yum.log
>> [root corefive ~]#
On Mon, 03 Jul 2006 15:10:58 +0100
Paul wrote:
> Hmm, it appears that kyum is just a GUI front-end for yum (i.e. it
invokes yum itself to do the work), compared with say
> yumex, which uses yum APIs but not the yum executable itself. So kyum
doesn't need the same SELinux context as yum,
> unlike yumex. Apart, that is, from the need to read rpm/yum log files.
> So give this a try:
> # chcon -t rpm_exec_t /usr/bin/kyum
> Then try kyum again, and make sure it still works OK for
installing/removing packages (try it on something you don't care
> much about), as well as being able to read the yum log.
> Paul.
Paul,
I tried:
# chcon -t rpm_exec_t /usr/bin/kyum
But I still get:
"/var/log/yum.log could not be opened for reading."
I removed kyum, erased all remaining files, reinstalled kyum, and set
SELinux to permissive.
But still no luck.
-ron-
17 years, 10 months
GNOME won't boot
by jery_wang
I have a major problem. I can't seem to logon to GNOME. After I type in my password and hit enter, a message pops up saying:
"There was an error starting the GNOME Setting Daemon. Some thing, such as themes, sounds, or background settings may not work correctly. The setting Daemon restarted too many times. The last error message was: Child process did not give an error massage, unknown failure occured. GNOME will still try to restart the Settings Daemon next tiime you log in"
Then it gives me the option to "close" the popup box. So I then hit close. After that it starts loading for about 12 minutes and then everything goes blank. When I say "loading" I mean that the "fedora core" sign comes up and then a picture of icons appear. Sound fimiliar?
As soon as it loads for about 12 minutes or so, it stops and everything goes away(including the fedora core sign) and the only thing that is in front of me is a mouse pointer, nothing else.
After that I just waited for about another 15 minutes or so to see if it would take me to my desktop but it didn't.
The last thing that I did to the computer was uninstalling "Glade Interface Designer" I'm positive that I didn't uninstall anything that was related to GNOME. Anyway, after uninstalling Glade Interface Designer, I tried to go into terminal but it failed. So that's when I restarted the computer. Then that's when I received the above error message when trying to log in, as you can see.
As of now, I have no idea what to do to fix this. I will take any suggestions. Am I toast?
--
This is an email sent via the webforum on http://fcp.homelinux.org
http://fcp.homelinux.org/modules/newbb/viewtopic.php?post_id=96826&topic_...
17 years, 10 months
Problem with tvtime and Xorg updates -- I think??
by Bill Case
Hi;
I seem to have lost some clarity in my reception after recent upgrades.
I was unsuccessful in getting help on the #tvtime IRC. Below is a copy
of my conversation. I am hoping someone here can help.
"<bill__> Hi; I have just upgraded a bunch of Xorg files (and other
programs including the latest kernel) on Fedora Core 5. The clarity of
my TV reception now seems all screwed up.
I am using, kernel 2.6.17-2139-FC5, ATI Wonder VE, tvtime 1.0.1.
<voosuz> what do you mean by clarity?
<bill__> hi voosuz; I was trying to avoid starting with long verbal
descriptions. It seems that the contrast has been increased, but when I
decrease the contrast value the whole picture just fades a bit.
<voosuz> did the same happen for mplayer/xine movies after your upgrade?
<bill__> Didn't try. I have never watched movies on my console. For
example, I keep news broadcasts on in the background.
CNN usually gives me my best reception. Now it seems facial detail is
lost, colours appear in blobs rather than gradients.
The loss in clarity is not huge, but noticeable.
(In the last couple of World Cup games, close up shots are watchable
even if not as sharp as they used to be, but, long shots are overwhelmed
by the greenish/yellow of the soccer field.)
Don't have/own any movie disks.
If it helps -- I am in Ottawa Canada, using Rogers Cable. They have
been moving to digital high definition lately. My pictures have been
slowly appearing clearer and clearer over the last few months -- almost
becoming spectacular. This problem is more than a step backwards.
<voosuz> hmm sorry, i'm only a user myself
<bill__> Thanks for trying voosuz; maybe someone who has some
suggestions can read this exchange and respond with some ideas.
<voosuz> if it really bothers you (i know it would bother me) you should
try and locate which package upgrade exactly caused it.
<bill__> Yea voosuz; I agree. I was trying to avoid an afternoon
playing around and tweaking, but I guess there is nothing but to get
started."
I really don't want to climb this long learning curve if I can avoid it.
Has anybody else run into this problem? Can anyone add suggestions on
how to solve it? Is it a bug?
--
Regards Bill
17 years, 10 months
Re: Kyum: /var/log/yum.log, could not be opened for reading.
by ron
On Sun, 2006-07-02 at 15:24 -0400
ron wrote:
>>>> Hello,
>>>> Kyum says "/var/log/yum.log could not be opened for reading.".
>>>> I can view the yum.log outside of kyum.
>>>> Can anyone help?
>>>> -ron-
ON Mon, 03 Jul 2006 08:56:32 +0100
Paul wrote:
>>> If you have SELinux in enforcing mode, what's the output of:
>>> # ls -lZ /var/log/yum.log $(which kyum)
>>> Paul.
On Mon, 03 Jul 2006 09:54:17 -0400
ron wrote:
>> Paul,
>> SELinux is in enforcing mode.
>> The output of:
>> # ls -lZ /var/log/yum.log $(which kyum)
>> IS:
>> [root corefive ~]# ls -lZ /var/log/yum.log $(which kyum)
>> -rwxr-xr-x root root system_u:object_r:bin_t /usr/bin/kyum
>> -rw------- root root system_u:object_r:rpm_log_t
/var/log/yum.log
>> [root corefive ~]#
On Mon, 03 Jul 2006 15:10:58 +0100
Paul wrote:
> Hmm, it appears that kyum is just a GUI front-end for yum (i.e. it
invokes yum itself to do the work), compared with say
> yumex, which uses yum APIs but not the yum executable itself. So kyum
doesn't need the same SELinux context as yum,
> unlike yumex. Apart, that is, from the need to read rpm/yum log files.
> So give this a try:
> # chcon -t rpm_exec_t /usr/bin/kyum
> Then try kyum again, and make sure it still works OK for
installing/removing packages (try it on something you don't care
> much about), as well as being able to read the yum log.
> Paul.
Paul,
I tried:
# chcon -t rpm_exec_t /usr/bin/kyum
But I still get:
"/var/log/yum.log could not be opened for reading."
So I removed kyum, erased all remaining files, reinstalled kyum, and set
SELinux to permissive.
But still no luck.
-ron-
17 years, 10 months
Removing old FC kernals
by Andrew Wood
Hi,
I need to free-up some space on my computer to install FC5. I have about
14 images of the kernals in the boot directory - from FC3 onwards.
Can I simply delete these files from the boot directory - except for the
most recent of course! Or is there some tool I'm supposed to use to do
this cleanly? Actually, which files can I delete that correspond with
each image - just to be thorough.
Thanks for you help,
Andrew
17 years, 10 months
kmod-fglrx
by Mark Curry
Hi,
I have installed a xen0 kernel and am trying to build a module fglrx-kmod from the livna srpm to load, but it ain't working can you help?
If I do:
rpmbuild -ba SPEC/fglrx-kmod.spec --target $(uname -rm) --without userland
I get a message saying (xen0) unsupported architecture.
In the spec file the line %define xenvar xen0 had been commented, but removing the comment makes no difference:
%define upvar ""
%ifarch i686 ppc
%define smpvar smp
%endif
%ifarch i686 x86_64
#disabled for now:
define xenvar xen0
%define kdumpvar kdump
%endif
%{!?kvariants: %define kvariants %{?upvar} %{?smpvar} %{?xenvar} %{?kdumpvar}}
Please help...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mark Curry
mcc28_x(a)yahoo.co.uk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
17 years, 10 months
hostname and dhcp question
by Deepak
Hi,
I have fedora core 5 installed in one of my computer in LAN. One of the
windows machine acts as the web server (internal) for the LAN but I can't
figure out how to get the web page served by that machine in my fedora. Just
typing the hostname (http://hostname) doesn't work, I have to put the IP
address to see the page. What's wrong with DHCP setting? and how to fix
this?
By the way all computers in my LAN have dynamic address which is handled by
DSL modem router. Other windows machine is behaving correctly, only fedora
installation is not. What do I need to do? I also checked the network
settings and found nothing to do with that as it has all automatic option
checked.
Thanks!
17 years, 10 months
Re: problem with httpd-2.2.0-5.1.2 after the latest FC5 httpd update
by Scott R. Godin
On Mon, 2006-07-03 at 06:56 -0400, fedora-list-request(a)redhat.com wrote:
> Re: problem with httpd-2.2.0-5.1.2 after the latest FC5 httpd
> update
have you tried a
vim -d /etc/httpd/conf/httpd.conf /etc/httpd/conf/httpd.conf.rpmnew
(or gvim for a better colorscheme, if you have vim-x11 installed)
to show differences, if the .rpmnew file exists ? (possible after any
updates)
17 years, 10 months
FC4: problems with kernel-2.6.17-1.2139_FC4
by Alberto Ferrante
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear all,
I have recently updated the kernel of one of our servers. The new kernel
(2.6.17-1.2139_FC4) appears not to recognize the host controller. Thus,
some devices, such as the USB controller, do not work. When the new
kernel is used, lspci does not even show the host bridge and the USB
controller; here is the result of lspci when the new kernel is used:
00:02.0 RAID bus controller: Silicon Image, Inc. SiI 0649 Ultra ATA/100
PCI to ATA Host Controller (rev 02)
00:03.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X
Gigabit Ethernet (rev 02)
00:04.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:05.0 System peripheral: Compaq Computer Corporation Advanced System
Management Controller
To make things work I needed to roll back to the old kernel release
(2.6.16-1.2115_FC4). Here is the result of a lspci when the old kernel
is used:
00:00.0 Host bridge: Broadcom GCNB-LE Host Bridge (rev 32)
00:00.1 Host bridge: Broadcom GCNB-LE Host Bridge
00:02.0 RAID bus controller: Silicon Image, Inc. SiI 0649 Ultra ATA/100
PCI to ATA Host Controller (rev 02)
00:03.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X
Gigabit Ethernet (rev 02)
00:04.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:05.0 System peripheral: Compaq Computer Corporation Advanced System
Management Controller
00:0f.0 ISA bridge: Broadcom CSB6 South Bridge (rev a0)
00:0f.1 IDE interface: Broadcom CSB6 RAID/IDE Controller (rev a0)
00:0f.2 USB Controller: Broadcom CSB6 OHCI USB Controller (rev 05)
00:0f.3 Host bridge: Broadcom GCLE-2 Host Bridge
Has anybody experienced anything similar? Is there any new module I need
to load for the 2.6.17 kernel to work?
I thank you in advance for your help.
Best regards,
Alberto Ferrante
- --
Home page: http://www.alari.ch/people/alberto
Public key: http://www.alari.ch/people/alberto/pubkey.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
iQIVAwUBRKkzImwAj6ArCn4kAQj1Hg//Unl3W8QOUBAQHSqH38YW5Ppjaq9Ql4D3
ciucaHpbOCUPcacVLWwTnkPzbcUZENTeHzoUr/42Dp65fJEWuGUG+ZwIakdBPkvT
I4/p7neth5LM1wNeuo+SHWL+TYgJziYzK3qrBN6+QDZ/UcNur15h7Y+YoAjrMJVZ
NQcshzRhTmn391UJkhiWtWPmYUDRS3AkAcwkv+rrO76STQsVajONuqQUwydPAoZl
RCbpW34KOcwLVJPIUUv/C7IGJ39M5ukQSh30/vK8uZx9x8o5TNEaGCWV7dNrJDac
YkseINjPwLry/ht3HSzV/LUvTdGKtjkTtRM00Em8PEd+tXGrWbIpEdeIJh3MrsQK
rNtj//QTIM52CoTSoCnmjG6Qk/eEkQj012Yqcwj6azrnATfgmSnlK8Kan3lTLrMf
yILXlOqnXc077tWQmw+8X9eq/wedFEjS1m6IGg/0wOy2+CtKOPInrE15MfZIWQBG
HF3+x3uA4vR9Bn2Be3JjS7qcCvSPwcXxjHdG13kLfzdrQ8gtxruFtVi3VGlxtsyh
f3ln0GqNbwU3wgvwH5V/KeGY9nDmjL5YhZkcMul9BqYT/XWzJniWrxhcLh9foSOu
6xyzPeVpqmQ3+DW1bsz/ugmdDSBdAWp+daYUcKZZZu1RHGZxmFgS+1h5J54GieS9
P1yMtN8nRdM=
=tA9D
-----END PGP SIGNATURE-----
17 years, 10 months