rpmdb error help needed
by Parag Nemade
Hi,
Yesterday i installed FC6 from rawhide repository. I did not played
with any rpm command or with rpm database but today when I then tried
to install rpmlint package i got
yum install rpmlint
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
extras-development 100% |=========================| 1.1 kB 00:00
pnq-rawhide 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Downloading header for rpmlint to pack into transaction set.
rpmlint-0.78-1.fc6.noarch 100% |=========================| 19 kB 00:00
---> Package rpmlint.noarch 0:0.78-1.fc6 set to be updated
--> Running transaction check
Dependencies Resolved
=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
rpmlint noarch 0.78-1.fc6 extras-development 167 k
Transaction Summary
=============================================================================
Install 1 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 167 k
Is this ok [y/N]: y
Downloading Packages:
(1/1): rpmlint-0.78-1.fc6 100% |=========================| 167 kB 00:01
Running Transaction Test
/etc/selinux/targeted/contexts/files/file_contexts: Multiple same
specifications for /media/\.hal-.*.
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
/etc/selinux/targeted/contexts/files/file_contexts: Multiple same
specifications for /media/\.hal-.*.
Installing: rpmlint ######################### [1/1]
rpmdb: PANIC: Invalid argument
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_put: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) storing record Config.pyo into Basenames
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "ConfigCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "ConfigCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "ConfigCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "DistributionCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "DistributionCheck.pyc" records from
Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "DistributionCheck.pyo" records from
Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "DocFilesCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "DocFilesCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "DocFilesCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "FHSCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "FHSCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "FHSCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "FilesCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "FilesCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "FilesCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "Filter.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "Filter.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "Filter.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "I18NCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "I18NCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "I18NCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "InitScriptCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "InitScriptCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "InitScriptCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "LSBCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "LSBCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "LSBCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "MenuCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "MenuCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "MenuCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "MenuXDGCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "MenuXDGCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "MenuXDGCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "NamingPolicyCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "NamingPolicyCheck.pyc" records from
Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "NamingPolicyCheck.pyo" records from
Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "PamCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "PamCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "PamCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "Pkg.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "Pkg.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "Pkg.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "PostCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "PostCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "PostCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "RpmFileCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "RpmFileCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "RpmFileCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "SignatureCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "SignatureCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "SignatureCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "SourceCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "SourceCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "SourceCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "SpecCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "SpecCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "SpecCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "TagsCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "TagsCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "TagsCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "Testing.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "Testing.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "Testing.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "ZipCheck.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "ZipCheck.pyc" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "ZipCheck.pyo" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "config" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
error: error(-30977) getting "rpmlint.py" records from Basenames index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
error: cannot open Group index using db3 - (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
error: cannot open Requirename index using db3 - (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
error: cannot open Providename index using db3 - (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
error: cannot open Dirnames index using db3 - (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
error: cannot open Requireversion index using db3 - (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
error: cannot open Provideversion index using db3 - (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
error: cannot open Installtid index using db3 - (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
error: cannot open Sigmd5 index using db3 - (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
error: cannot open Sha1header index using db3 - (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
error: cannot open Filemd5s index using db3 - (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error,
run database recovery
Installed: rpmlint.noarch 0:0.78-1.fc6
Complete!
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal
error, run database recovery
I even removed all /var/lib/rpm/__* files and tried to install any rpm
but same errors i got when i executed following command
rpm -ivh kernel-xen-devel-2.6.18-1.2747.fc6.i686.rpm
whats that mean? how to recover rpm database?
regards,
Parag.
17 years, 6 months
Using a custom DSDT with Fedora
by Richard Hughes
I've just spend a couple of hours fixing my BIOS :
http://hughsient.livejournal.com/5884.html
To do this, I needed to re-write the _BIF and _BST ACPI methods to
actually interface with the hardware in a sane way.
Using Ubuntu or SUSE, using a new dsdt would be as easy as adding it to
the initrd. BUT on Fedora you have to build a custom kernel (not
trivial), patch it to add the custom dsdt functionality, add the dsdt to
the initrd and then boot this new custom kernel.
I do understand the policy of not including random patches to the kernel
source, but given:
* There are lots (hundreds?) of existing out-of-tree patches to the
default fedora kernel.
* Most of the the other big distros allow a user to load custom dsdt's
* The feature is already used by thousands of users.
* Installing a random dsdt into the initrd isn't the sort of thing you
can you trivially or accidentally.
So, is there any good reason this feature isn't available on the Fedora
kernel? Thanks.
Richard.
17 years, 6 months
Xorg backtrace when logging in for the first time after bootup
by Matthias Saou
Hi,
I've been having this particular issue on a recent workstation ever
since I first installed Rawhide on it (a couple of weeks ago) :
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208619
After the computer boots, I log into gdm, then my desktop starts
appearing, but only a few icons from the desktop manage to show up,
then *boom* : X dies then back to gdm after a short wait. I log in for
the second time and all works fine...
This is 100% reproducible. Backtrace below. Please note that this is
without using the proprietary Nvidia driver. When using the proprietary
Nvidia driver, login works on the first attempt :-/
Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x71) [0x495ff1]
1: /lib64/libc.so.6 [0x38ac230210]
2: /usr/lib64/xorg/modules/libfb.so(fbCopyAreammx+0x200)
[0x2aaaadf20ea0] 3: /usr/lib64/xorg/modules/libfb.so(fbComposite+0x5db)
[0x2aaaadf1176b]
4: /usr/lib64/xorg/modules/libxaa.so(XAAComposite+0x2ac)
[0x2aaaae1629ec] 5: /usr/bin/Xorg [0x512e5d] 6: /usr/bin/Xorg [0x50f268]
7: /usr/bin/Xorg [0x502d2f]
8: /usr/bin/Xorg(Dispatch+0x1ca) [0x449c9a]
9: /usr/bin/Xorg(main+0x455) [0x4325d5]
10: /lib64/libc.so.6(__libc_start_main+0xf4) [0x38ac21da44]
11: /usr/bin/Xorg(FontFileCompleteXLFD+0x231) [0x4318c9]
Fatal server error:
Caught signal 11. Server aborting
Is anyone else seeing this?
Matthias
--
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora Core release 5.92 (FC6 Test3) - Linux kernel 2.6.18-1.2759.fc6
Load : 0.00 0.02 0.02
17 years, 6 months
NVIDIA dkms srpms
by Richard Hughes
My home media server uses a NVIDIA geforce 4 video card. Usually, using
the 2D driver is good enough, but sometimes I need to do something
graphical and 3D - and so require the NVIDIA closed source driver. I've
got pretty sick installing the NVIDIA-Linux-x86-1.0-xxxx-pkg1.run file
every time I upgrade my kernel, and watching it copy "stuff" all over my
filesystem and muck up my rpmdb.
I *know* closed source drivers are bad, and illegal if they link to the
kernel. That's not in debate. I understand why Fedora doesn't ship them,
and I can also understand why the people who run the repo beginning with
l have stopped updating the kmod's. I can really understand the kernel
guys flatly refusing to debug any tainted kernel. But then I need my 3D
openGL application to run at more than 2 fps.
So, I began to think. And then I read the LICENCE file for the NVIDIA
linux drivers a couple of times. Now, IANAL, but I think it boils down
to:
* We can't legally ship compiled nvidia code (so no kmods)
* We can't legally ship a broken apart xxxx-pkgx.run file
* We probably shouldn't be shipping the .run file as part of an SRPM
So, my brain got thinking. I've used DKMS in the past, and it's been
very stable and well thought out. So, I've had a play and created a
7.4kb SRPM that does the following:
* displays a warning that closed source drivers are bad and makes the
user acknowledge.
* downloads the correct .run file from ftp.nvidia.com
* displays the nvidia LICENCE and makes user acknowledge
* installs the x11 bits and bobs in standard places (I've taken most of
this from the l.org package) so that it does not conflict with mesa etc.
* installs the useful nvidia helper tools
* installs the kernel stuff (manually) as a dkms package so that the
kernel part gets rebuilt every time you change your kernel.
And the best bit: you don't muck up your rpmdb *and* you can install the
resulting build rpm's on all your *home* PC's automatically (without
prompts). Single time pain.
Now, I'm aware I've broken two big packaging rules, that SRPMs shouldn't
download files, and that SRPMs shouldn't be interactive. I seem to
remember jpackage doing something similar with java a few years ago,
where there was only a SRPM available and you had to download a large
tar.gz file.
So, advice required from you guys: is this legal (assuming the binary
rpm's are never distributed, only the SRPM) and is this sane? I can
upload the SRPM to my private webspace (as long as I'm not doing
anything illegal in doing so) if people want.
Richard.
p.s. I am an engineer, not a lawyer.
17 years, 6 months
Fedora core Chinese font support
by Leo
Hi all,
Four years ago, I hated tweaking Chinese font support. It was such a
waste of time. So with FC5, I have been using English for about 8
months now. FC5's Chinese support is as bad as Redhat Linux 8. Lately
I did a lot of work in Chinese. It wasn't a pleasant experience with
Fedora core 5. I'm studying in UK and I don't need to use Chinese on
daily bases. If I feel awful, how would my fellow Chinese feel. I'm
posting here so that fedora developers could pay more attention to
this aspect in future releases.
Here is a comparison between SuSE 9.3 (released 2005/04/15) and FC5
(released 2006/03/20):
SuSE:
Fedora:
As you can see, the Chinese characters in SuSE 9.3 are much clearer
and easier on the eyes.
Now there is a GPL'ed CJK font¹ that has actually been in Debian for a
while. Hope it could make it into FC and be standardized as the
default CJK font.
Footnotes:
¹ http://wqy.sourceforge.net/cgi-bin/enindex.cgi
--
Leo
17 years, 6 months
rawhide report: 20061011 changes
by Build System
Updated Packages:
acpid-1.0.4-5
-------------
* Tue Oct 10 2006 Phil Knirsch <pknirsch(a)redhat.com> - 1.0.4-5
- Made acpid a PIE binary (#210016)
anaconda-11.1.1.0-1
-------------------
* Tue Oct 10 2006 Jeremy Katz <katzj(a)redhat.com> - 11.1.1.0-1
- Allow setting the language to something not in lang-table (clumens, #176538)
- Fix split media (pnasrat)
- Fix going back from advanced bootloader (clumens, #210190)
- Bump early swap to be higher
coolkey-1.0.1-9
---------------
* Mon Oct 16 2006 Bob Relyea <rrelyea(a)redhat.com> - 1.0.1-9
- use pk11install which does not require loading the module to install it.
* Mon Oct 16 2006 Bob Relyea <rrelyea(a)redhat.com> - 1.0.1-8
- pcscd must be running in order to add coolkey.
device-mapper-1.02.07-3
-----------------------
* Tue Oct 10 2006 Jeremy Katz <katzj(a)redhat.com> - 1.02.07-3
- bump version to fix upgrade path
* Thu Aug 03 2006 Milan Broz <mbroz(a)redhat.com> - 1.02.07-1.2
- rpmlint cleaning, summary, permissions
filesystem-2.4.0-1
------------------
* Tue Oct 10 2006 Bill Nottingham <notting(a)redhat.com> - 2.4.0-1
- create and own /usr/share/locale/*/LC_MESSAGES (#196669)
* Tue Oct 10 2006 Phil Knirsch <pknirsch(a)redhat.com> - 2.3.8-1
- Added the manXx directories to the ownership of filesystem (#208121)
java-1.4.2-gcj-compat-0:1.4.2.0-40jpp.110
-----------------------------------------
* Tue Oct 10 2006 Thomas Fitzsimmons <fitzsim(a)redhat.com> - 0:1.4.2.0-40jpp.110
- Require gij binary explicitly. (208913)
kernel-2.6.18-1.2759.fc6
------------------------
* Tue Oct 10 2006 Dave Jones <davej(a)redhat.com>
- OOM Killer improvements.
- Fix bug in set_page_dirty_buffers
- Fix hibernate on macmini. (Peter Jones).
* Tue Oct 10 2006 Jon Masters <jcm(a)redhat.com>
- Move symsets into /usr/src/kernels.
* Tue Oct 10 2006 Dave Jones <davej(a)redhat.com>
- Remove unneeded seccomp patch.
- XFS fix for umount oops (209062)
openoffice.org-1:2.0.4-5.3
--------------------------
* Fri Oct 06 2006 Caolan McNamara <caolanm(a)redhat.com> - 1:2.0.4-5.3
- add openoffice.org-2.0.4.ooo69992.vcl.im_yield.patch for rh#208537#
- add workspace.cmcfixes28.patch for rh#208966#
- add openoffice.org-2.0.4.ooo70064.sc.crashonalignment.patch for rh#208888#
pirut-1.2.4-1
-------------
* Tue Oct 10 2006 Jeremy Katz <katzj(a)redhat.com> - 1.2.4-1
- More updated translations
- Raise error on error in repo setup (jbowes, #208845)
- puplet: Show menu on left click (#209990)
pygtk2-2.10.1-4.fc6
-------------------
* Mon Oct 02 2006 Jeremy Katz <katzj(a)redhat.com> - 2.10.1-4
- go back to raising an exception when importing gtk fails (#208608)
setup-2.5.54-1
--------------
* Tue Oct 10 2006 Phil Knirsch <pknirsch(a)redhat.com> 2.5.54-1
- Update /etc/protocols to latest officiall IANA version (#209191)
tzdata-2006m-2.fc6
------------------
* Tue Oct 10 2006 Petr Machata <pmachata(a)redhat.com> - 2006m-2
- Proposed upstream patch (#210058)
- Jordan will switch to winter time on October 27, not September 29
- Brazil's DST this year is the first Sunday in November to the last
Sunday in February. (Thanks to Frederico A. C. Neves.)
- ISO 3166 codes for Serbia and Montenegro, zone Europe/Podgorica
- Commentary and past timestamps changes
* Tue Oct 03 2006 Petr Machata <pmachata(a)redhat.com> - 2006m-1
- Upstream 2006m:
- Adjustments for Egypt, Palestine, Uruguay
- Better description of `until' field in zic (8) manpage
* Thu Sep 21 2006 Petr Machata <pmachata(a)redhat.com> - 2006l-1
- Upstream 2006k, 2006l:
- Adjustments for Egypt, Palestine, Cuba, Honduras
- Documentation changes
yum-3.0-4
---------
* Tue Oct 10 2006 Jeremy Katz <katzj(a)redhat.com> - 3.0-4
- fix traceback on package download error (#210135, #210181, #210115)
Broken deps for s390
----------------------------------------------------------
systemtap - 0.5.9-1.fc6.s390 requires kernel >= 0:2.6.9-11
17 years, 6 months
No more amarok-x86_64?
by Neal Becker
Looks like amarok x86_64 package was removed from fc5? Is this intentional?
What is the reason?
17 years, 6 months
Re: Error inserting acpi_cpufreq
by Jason Dravet
Antonio Olivares wrote:
>
>When I start the machine, I get to see the message that there was an error
>inserting
>acpi_cpufreq in
>/lib/modules/2.6.18-1.2747.fc6/kernel/arch/i386/kernel/cpu/cpufreq
>It says that there is no acpi-cpufreq.ko, and I looked for it and it is
>there
Sorry I replied to the wrong list.
Jason
17 years, 6 months
Re: Error inserting acpi_cpufreq
by Jason Dravet
Antonio Olivares wrote:
>
>When I start the machine, I get to see the message that there was an error
>inserting
>acpi_cpufreq in
>/lib/modules/2.6.18-1.2747.fc6/kernel/arch/i386/kernel/cpu/cpufreq
>It says that there is no acpi-cpufreq.ko, and I looked for it and it is
>there
Ever since FC3 this error has popped up at one point or another during
development. During the FC6 development the bug is:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201832
It looks like it has popped up again.
Jason
17 years, 6 months
thunderbird-1.5.0.7-3
by Christopher Aillon
very low risk, makes firefox use '•' (U+2022) instead of '*' for its
"password" characters.
17 years, 6 months