Re: Software request
by Rahul Sundaram
On 05/04/2009 08:56 PM, Beartooth Comcast wrote:
> On Mon, 4 May 2009, Rahul Sundaram wrote:
>
>> On 04/29/2009 07:39 PM, Beartooth wrote:
>>> Could some kind soul make an rpm and put it into a repository for
>>> gnome-format? It's at
>>>
>>> http://live.gnome.org/gnome-format -- and there are .debs there, but
>>> no .rpms.
>>
>> Here, you go
>>
>> http://koji.fedoraproject.org/koji/taskinfo?taskID=1335062
>>
>> I need to put this up for review but you can pick it up meanwhile. Let
>> me know if you find any issues.
>
> Many thanks -- and, alas!, I do have one. It's probably my
> incompetence (I never touch source code), but it looks a lot like the
> failures I've been getting with the packagekit updater :
>
> [root@Hbsk2 btth]# rpm -ivh gnome-format-0.1.1-1.fc10.i386.rpm
> rpmdb: Thread/process 22733/3086984896 failed: Thread died in Berkeley
> DB library
Run these commands:
rm -f /var/lib/rpm/__db*
rpm --rebuilddb
and try again.
Rahul
15 years
Re: nVidia vs. ATI graphics card for fedora
by Jack Howarth
Kevin,
Our experience here with x86_64 Fedora 10 linux and
the radeon drivers on a couple machines with Radeon X1650 Pro
cards has been very uneven. One of the boxes is very fragile
to spontaneous reboots when running the free drivers and
using UCSF Chimera to work with MD trajectories. The other
box still has a habit of blanking the screen for minutes
at time despite having the nomodeset flag passed to the
kernel. I am afraid things will only get worse under Fedora 11.
So far, testing on a MacBook Pro with X1600 graphics, I find
that pymol still renders outside of its windows. While I
appreciate the aims of these changes to X11 and the free
drivers, the problem is that Fedora has become destablized.
It is really exposing the limitations of a monolithic kernel
when the graphics drivers keep taking down the entire box.
Jack
ps We run a large amount of OpenGL software (free and
commercial) and have found the non-free drivers to be
more compatible in general. Hopefully this will improve
over time.
15 years
Re: Fedora 11 fail because of Anaconda :(
by Bruno Wolff III
On Mon, May 04, 2009 at 15:15:24 +0100,
Peter Robinson <pbrobinson(a)gmail.com> wrote:
>
> I agree the test days have helped but its concerning that I still
> can't do an install with custom partitions with the preview release.
> And there doesn't seem to be a lot of traction on the bug to fix it
> before release.
Have you tried using a boot.iso image to do a network install? There
were a lot of bugs addressed in anaconda-11.5.0.48-1 (-2 is now available)
since the preview image.
15 years
RE:Where is lsof?
by Alan Gagne
>
> Where is it in F9?
>
>
]# yum info lsof
Loaded plugins: refresh-packagekit
Installed Packages
Name : lsof
Arch : i386
Version : 4.80
Release : 2.fc10
Size : 867 k
Repo : installed
Summary : A utility which lists open files on a Linux/UNIX system
URL : ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof
License : zlib
Description: Lsof stands for LiSt Open Files, and it does just that: it
lists
: information about files that are open by the processes
running on a
: UNIX system.
15 years
Software request
by Beartooth
Could some kind soul make an rpm and put it into a repository for
gnome-format? It's at
http://live.gnome.org/gnome-format -- and there are .debs there, but
no .rpms.
It *might* (I'm told) be able to handle the trouble some of us
have been having wiping Conficker-prone M$-foulness (automount, I think)
off thumb drives.
--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Remember I know precious little of what I am talking about.
15 years
internal system error
by potat0
Lately I've been getting very frequently (let's say every quarter of an hour) a warning about an internal system error, specifically a Package Manager error. In detail:
Error Type:
Error Value: 'NoneType' object is unsubscriptable
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2316, in
main()
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2313, in main
backend.dispatcher(sys.argv[1:])
File : /usr/lib/python2.5/site-packages/packagekit/backend.py, line 600, in dispatcher
self.dispatch_command(args[0], args[1:])
File : /usr/lib/python2.5/site-packages/packagekit/backend.py, line 508, in dispatch_command
self.get_updates(filters)
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1769, in get_updates
self._check_init()
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1996, in _check_init
self.yumbase.repos.doSetup()
File : /usr/lib/python2.5/site-packages/yum/repos.py, line 71, in doSetup
self.ayum.plugins.run('postreposetup')
File : /usr/lib/python2.5/site-packages/yum/plugins.py, line 178, in run
func(conduitcls(self, self.base, conf, **kwargs))
File : /usr/lib/yum-plugins/rpm-warm-cache.py, line 32, in postreposetup_hook
cmd = commands[0]
Does anybody know what I should do to fix it?
Thanks in advance,
molly
--
This is an email sent via The Fedora Community Portal https://fcp.surfsite.org
https://fcp.surfsite.org/modules/newbb/viewtopic.php?post_id=342609&topic...
If you think, this is spam, please report this to webmaster(a)fcp.surfsite.org and/or blame psalviato(a)gmail.com.
15 years
Installation of F 11
by mike
Tried to install F 11 on a dual boot machine. Base is XP and the second
is currently F 10. The install failed with an error message that the
partition could not be installed. Then the machine would not reboot be
died at a grub shell.
I pulled out my F 10 DVD and reinstalled a base F 10 over the existing
Linux partition. This gave me back grub in a dual boot and a fresh F 10
not updated.
Y'all can keep F 11. Let me know when it maybe works!
15 years
Selinux disallows read-only loop mount of a file, but only at boot
by David
I'm exploring new territory: the first time I've ever tried to mount a
loop device (a ro file) at boot using fstab.
My fstab entry works fine from the command line, but it fails at boot
time due to a selinux avc error, I dont understand why but I suspect
it is because the file context is unsuitable.
The file and context are:
[david@kablamm ~]$ ls -lZ
/HUGE/get/iso/Fedora-09-i386-DVD/Fedora-09-i386-DVD.iso
-r--r----- root share unconfined_u:object_r:default_t:s0
/HUGE/get/iso/Fedora-09-i386-DVD/Fedora-09-i386-DVD.iso
The fstab line is:
/HUGE/get/iso/Fedora-09-i386-DVD/Fedora-09-i386-DVD.iso /mnt/Fedora-09-i386-DVD iso9660 loop,ro,gid=share
0 0
The command line that works is:
# mount /mnt/Fedora-09-i386-DVD
The boot-time error messages are:
Mounting local filesystems:
/HUGE/get/iso/Fedora-09-i386-DVD/Fedora-09-i386-DVD.iso: Permission
denied [FAILED]
Mounting other filesystems:
/HUGE/get/iso/Fedora-09-i386-DVD/Fedora-09-i386-DVD.iso: Permission
denied [FAILED]
and from dmesg:
type=1400 audit(1241411595.523:4): avc: denied { read } for
pid=1335 comm="mount" name="Fedora-09-i386-DVD.iso" dev=sdb2 ino=1922
scontext=system_u:system_r:mount_t:s0
tcontext=unconfined_u:object_r:default_t:s0 tclass=file
and my selinux status is:
[root@kablamm ~]# sestatus
SELinux status: enabled
SELinuxfs mount: /selinux
Current mode: enforcing
Mode from config file: enforcing
Policy version: 22
Policy from config file: targeted
QUESTIONS:
I'm guessing that the problem is the file's tcontext .. what should it
be? Is it just a matter of changing it to mount_t, the same as the
error message scontext?
The command
# sesearch --allow -s mount_t -c file -p read
gives 1292 results. How could I decide which one of these to use?
And if anyone can say why it does not matter after boot time, I'd
appreciate understanding that. Possibly something to do with context
transitions?
I've not attempted any trial and error solution, prefer to comprehend
security tools if possible.
Thanks.
15 years
Why Can't I run 2 X servers on the same machine?
by Derek Tattersall
I would like to set up 2 seats on my PC, with 2 mice, 2 keyboards and 2
monitors. It is running f9, and the nvidia driver version 180.51.
I spent a few hours messing around with it, and I got it almost working.
I have an nvidia graphics GeForce 8500 card, and it works just fine as a
dual-head card. I can also run 2 X servers on different VTs when the
card is configured with dual heads. The problem comes when I try to run
2 X servers, one on each of the 2 monitors.
So I modified the xorg.conf file to have 2 different server layouts, one
for each monitor. It works perfectly when I try to run each server
layout independently. It fails when I try to run tehm both at once. I
get this error in my Xorg.0.log file:
/var/log/Xorg.0.log:(EE) NVIDIA(0): EVO Push buffer channel allocation
failed
/var/log/Xorg.0.log:(EE) NVIDIA(0): *** Aborting ***
/var/log/Xorg.0.log:(EE) NVIDIA(0): Failed to allocate EVO DMA push buffer
/var/log/Xorg.0.log:(EE) NVIDIA(0): *** Aborting ***
Can anyone tell me what this error means?
Thanks.
Derek Tattersall
15 years
Re: Fedora 11 fail because of Anaconda
by Jayson Rowe
On 05/03/2009 11:01 PM, fedora-list-request(a)redhat.com wrote:
> Re: Fedora 11 fail because of Anaconda
I commented on the blog-post as well (saw that first).
I'm on real hardware, and I've installed on two machines without issue.
I don't use LVM, but I have 3 hard drives.
First drive: 150G 10kRPM gets /boot (ext2) / (ext4) /home (ext4) and SWAP
Second Drive: 320G gets /virtuals (ext4)
Third Drive: 1TB gets /data (ext4)
On my laptop, which has a single drive gets /boot (ext2) / (ext4) and
/home (ext4)
Install went great on both systems. Did a clean install because I'm a
new (well, returning I guess, but it's been since FC2/FC3T2) Fedora user
from the (horrid) land of Ubuntu :-)
I *did* however run into an issue trying to install the x86_64 LiveCD in
a KVM virtual machine - it (is the live installer still Anaconda?)
crashed even leaving the defaults alone. I need to try it again and make
note of the specific error, but I was in a rush when trying it, and just
planned to come back too it later after 2 failed attempts at the same
exact spot.
I wish I had another physical system here I could sacrifice for testing,
but I do hope this gets worked out soon if lots of people are seeing
this - we need all the users on F11 as we can get before it goes Gold!
-jayson
15 years