Adventures with Monday's Rawhide 64
by Chuck Forsberg WA7KGX
Intel DG33BU Core Duo - ethernet problem prevents NFS install
Asus A8N-E - successful NFS install. Gateway and
nameserver not set. The new software add app
still doesn't actually install anything.
--
Chuck Forsberg caf(a)omen.com www.omen.com 503-614-0430
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 FAX 629-0665
16 years
Re: moving a fedora 7 to rawhide
by Antonio Olivares
----- Original Message ----
From: Andrew Farris <lordmorgul(a)gmail.com>
To: For testers of Fedora Core development releases <fedora-test-list(a)redhat.com>
Sent: Friday, April 4, 2008 8:24:13 PM
Subject: Re: moving a fedora 7 to rawhide
Antonio Olivares wrote:
> --- Andrew Farris <lordmorgul(a)gmail.com> wrote:
>
>> John Summerfield wrote:
>>> Antonio Olivares wrote:
>>>> only since the machine only boots two kernels I
>> have
>>>> to resort to booting it. A few conflicts here
>> and
>>>> there, Is there a cleanup script that checks for
>> fc7
>>>> rpms and deletes them and finds corresponding fc9
>>>> rpms?
>>> I wouldn't expect one; if Anaconda and yum don't
>> do it, you're pretty
>>> much Pat Malone.
>>> This will give some clues as to what's obsolete:
>>>
>>> rpm -qa --last | less
>> Any package containing .fc7 should be obselete. The
>> Beta release notes [1] also
>> contain clues.
>>
>> You should: rpm -e --nodeps sysvinit; yum install
>> upstart
>>
>> /usr/lib/python2.5/site-packages/libusermodule.so
>> from
>> install of libuser-python-0.56.8-1.i386 conflicts
>> with
>> file from package libuser-0.56.2-1.i386
>> ^^ is a problem with mismatched versions, use
>> --exclude=libuser-python
>>
>> [1] http://fedoraproject.org/en/f9-beta-relnotes
>>
>> --
>> Andrew Farris <lordmorgul(a)gmail.com>
>> www.lordmorgul.net
>> gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC
>> 7DEB 5BD5 5F89 8E1B 8300 BF29
>> revoked key 0xC99B1DF3 no longer used
>> No one now has, and no one will ever again get, the
>> big picture. - Daniel Geer
>> ----
>> ----
>>
>> --
>> fedora-test-list mailing list
>> fedora-test-list(a)redhat.com
>> To unsubscribe:
>>
> https://www.redhat.com/mailman/listinfo/fedora-test-list
>
> Andrew,
>
> as I have mentioned in the other mail,
>
> what was done is here:
> http://www.geocities.com/olivares14031/fc72rawhide.htm
>
> I got by these errors. Several observations
> [olivares@localhost ~]$ su -
> bash: su: command not found
You're missing 'coreutils' I think. That would cause some serious weirdness.
> [root@localhost ~]# The program 'gkrellm' received an
> X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadName (named color or font does not
> exist)'.
> (Details: serial 7003 error_code 15 request_code 45
> minor_code 0)
After you get coreutils..
Since you're getting this BadName error on more than one app I think you may
need to try running a new user and see what happens (i.e. a clean /home). That
would give you some clues, maybe reset to default F9 themes, fonts, etc.
> [root@localhost ~]#
>
> Looking at it from the bright side, I can login as
> root and type this message.
Hehe, thats getting there.
--
Andrew Farris <lordmorgul(a)gmail.com> www.lordmorgul.net
gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC 7DEB 5BD5 5F89 8E1B 8300 BF29
revoked key 0xC99B1DF3 no longer used
No one now has, and no one will ever again get, the big picture. - Daniel Geer
---- ----
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
end of Original message
you wrote:
Since you're getting this BadName error on more than one app I think you may
need to try running a new user and see what happens (i.e. a clean /home). That
would give you some clues, maybe reset to default F9 themes, fonts, etc.
I have created a new user and the result is the same and I still have the same problem that I cannot
su -
with coreutils installed.
Thanks,
Antonio
____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com
16 years
cannot start x as regular user, coreutils is installed cannot su -
by Antonio Olivares
Again, I will attach logs of what I did
Script started on Mon 07 Apr 2008 07:39:25 PM CDT
[olivares@localhost ~]$ startx
xauth: creating new authority file /home/olivares/.serverauth.2424
Fatal server error:
Cannot open log file "/var/log/Xorg.0.log"
^Cgiving up.
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): unexpected signal 2.
Couldnt get a file descriptor referring to the console
[olivares@localhost ~]$ su -
bash: su: command not found
[olivares@localhost ~]$ rpm -qa corecutils
[olivares@localhost ~]$ rpm -qa corecutils [C [C^[cutils [cutils 3cutils ~cutils [1Pcutils [1Pcutils [1Pcutils [2Pcutils [1Pcutils ecutils [1Putils [C [C [C [C [C
coreutils-6.10-17.fc9.i386
[olivares@localhost ~]$ cat /b [Kvar/ [K [K [K [K [K [K [K [K [Kls -l /varlo [K [K/log/Xorg.0.log
[00mls: cannot access /var/log/Xorg.0.log: Permission denied
[m[olivares@localhost ~]$ s [Kexit
exit
Script done on Mon 07 Apr 2008 07:40:38 PM CDT
I removed Xorg.X.log from /var/log/ directory but situation is still the same. I was logged into KDE, and it has crashed several applications. Here's what I got
I saved part of the text to kwrite, but it also crashed as well, however I managed to save the file.
I also tried to reconfigure X, using both
Xorg -configure
and
system-config-display
but both failed, just like su -
when coreutils is installed.
BTW, I had gnome installed previously under fedora 7, but since I have upgraded to rawhide, I lost it and i yummed it in
It gave me a warning about running as priviledged user and KDE did not,
I get a bunch of warnings about something not found. I am tempted to remove X windows and reinstalling, but I wait for further direction from the list
[root@localhost ~]# startx
xauth: creating new authority file /root/.serverauth.3959
X.Org X Server 1.4.99.901 (1.5.0 RC 1)
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-53.1.6.el5 i686
Current Operating System: Linux localhost.localdomain 2.6.25-0.201.rc8.git4.fc9.i686 #1 SMP Sun Apr 6 21:55:27 EDT 2008 i686
Build Date: 04 April 2008 11:10:55AM
Build ID: xorg-x11-server 1.4.99.901-17.20080401.fc9
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 7 19:56:30 2008
(EE) Unable to locate/open config file
New driver is "sis"
(==) Using default built-in configuration (30 lines)
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:0:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:1:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:1) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:5) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:7) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:0) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:1) found
(WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:3) found
(EE) open /dev/fb0: No such file or directory
Failed to find device matching 0@128:0:0
Failed to find device matching 0@128:1:0
Failed to find device matching 0@128:2:0
Failed to find device matching 0@128:3:0
Failed to find device matching 0@128:4:0
Failed to find device matching 0@128:5:0
Failed to find device matching 0@128:6:0
Failed to find device matching 0@128:7:0
Failed to find device matching 0@128:8:0
Failed to find device matching 0@128:9:0
Failed to find device matching 0@128:10:0
Failed to find device matching 0@128:11:0
Failed to find device matching 0@128:12:0
Failed to find device matching 0@128:13:0
Failed to find device matching 0@128:14:0
Failed to find device matching 0@128:15:0
Failed to find device matching 0@128:16:0
Failed to find device matching 0@128:17:0
Failed to find device matching 0@128:18:0
Failed to find device matching 0@128:19:0
Failed to find device matching 0@128:20:0
Failed to find device matching 0@128:21:0
Failed to find device matching 0@128:22:0
Failed to find device matching 0@128:23:0
Failed to find device matching 0@128:24:0
Failed to find device matching 0@128:25:0
Failed to find device matching 0@128:26:0
Failed to find device matching 0@128:27:0
Failed to find device matching 0@128:28:0
Failed to find device matching 0@128:29:0
Failed to find device matching 0@128:30:0
Failed to find device matching 0@128:31:0
Failed to find device matching 1@128:0:0
Failed to find device matching 1@128:1:0
Failed to find device matching 1@128:2:0
Failed to find device matching 1@128:3:0
Failed to find device matching 1@128:4:0
Failed to find device matching 1@128:5:0
Failed to find device matching 1@128:6:0
Failed to find device matching 1@128:7:0
Failed to find device matching 1@128:8:0
Failed to find device matching 1@128:9:0
Failed to find device matching 1@128:10:0
Failed to find device matching 1@128:11:0
Failed to find device matching 1@128:12:0
Failed to find device matching 1@128:13:0
Failed to find device matching 1@128:14:0
Failed to find device matching 1@128:15:0
Failed to find device matching 1@128:16:0
Failed to find device matching 1@128:17:0
Failed to find device matching 1@128:18:0
Failed to find device matching 1@128:19:0
Failed to find device matching 1@128:20:0
Failed to find device matching 1@128:21:0
Failed to find device matching 1@128:22:0
Failed to find device matching 1@128:23:0
Failed to find device matching 1@128:24:0
Failed to find device matching 1@128:25:0
Failed to find device matching 1@128:26:0
Failed to find device matching 1@128:27:0
Failed to find device matching 1@128:28:0
Failed to find device matching 1@128:29:0
Failed to find device matching 1@128:30:0
Failed to find device matching 1@128:31:0
Failed to find device matching 2@128:0:0
Failed to find device matching 2@128:1:0
Failed to find device matching 2@128:2:0
Failed to find device matching 2@128:3:0
Failed to find device matching 2@128:4:0
Failed to find device matching 2@128:5:0
Failed to find device matching 2@128:6:0
Failed to find device matching 2@128:7:0
Failed to find device matching 2@128:8:0
Failed to find device matching 2@128:9:0
Failed to find device matching 2@128:10:0
Failed to find device matching 2@128:11:0
Failed to find device matching 2@128:12:0
Failed to find device matching 2@128:13:0
Failed to find device matching 2@128:14:0
Failed to find device matching 2@128:15:0
Failed to find device matching 2@128:16:0
Failed to find device matching 2@128:17:0
Failed to find device matching 2@128:18:0
Failed to find device matching 2@128:19:0
Failed to find device matching 2@128:20:0
Failed to find device matching 2@128:21:0
Failed to find device matching 2@128:22:0
Failed to find device matching 2@128:23:0
Failed to find device matching 2@128:24:0
Failed to find device matching 2@128:25:0
Failed to find device matching 2@128:26:0
Failed to find device matching 2@128:27:0
Failed to find device matching 2@128:28:0
Failed to find device matching 2@128:29:0
Failed to find device matching 2@128:30:0
Failed to find device matching 2@128:31:0
Failed to find device matching 3@128:0:0
Failed to find device matching 3@128:1:0
Failed to find device matching 3@128:2:0
Failed to find device matching 3@128:3:0
Failed to find device matching 3@128:4:0
Failed to find device matching 3@128:5:0
Failed to find device matching 3@128:6:0
Failed to find device matching 3@128:7:0
Failed to find device matching 3@128:8:0
Failed to find device matching 3@128:9:0
Failed to find device matching 3@128:10:0
Failed to find device matching 3@128:11:0
Failed to find device matching 3@128:12:0
Failed to find device matching 3@128:13:0
Failed to find device matching 3@128:14:0
Failed to find device matching 3@128:15:0
Failed to find device matching 3@128:16:0
Failed to find device matching 3@128:17:0
Failed to find device matching 3@128:18:0
Failed to find device matching 3@128:19:0
Failed to find device matching 3@128:20:0
Failed to find device matching 3@128:21:0
Failed to find device matching 3@128:22:0
Failed to find device matching 3@128:23:0
Failed to find device matching 3@128:24:0
Failed to find device matching 3@128:25:0
Failed to find device matching 3@128:26:0
Failed to find device matching 3@128:27:0
Failed to find device matching 3@128:28:0
Failed to find device matching 3@128:29:0
Failed to find device matching 3@128:30:0
Failed to find device matching 3@128:31:0
Failed to find device matching 4@128:0:0
Failed to find device matching 4@128:1:0
Failed to find device matching 4@128:2:0
Failed to find device matching 4@128:3:0
Failed to find device matching 4@128:4:0
Failed to find device matching 4@128:5:0
Failed to find device matching 4@128:6:0
Failed to find device matching 4@128:7:0
Failed to find device matching 4@128:8:0
Failed to find device matching 4@128:9:0
Failed to find device matching 4@128:10:0
Failed to find device matching 4@128:11:0
Failed to find device matching 4@128:12:0
Failed to find device matching 4@128:13:0
Failed to find device matching 4@128:14:0
Failed to find device matching 4@128:15:0
Failed to find device matching 4@128:16:0
Failed to find device matching 4@128:17:0
Failed to find device matching 4@128:18:0
Failed to find device matching 4@128:19:0
Failed to find device matching 4@128:20:0
Failed to find device matching 4@128:21:0
Failed to find device matching 4@128:22:0
Failed to find device matching 4@128:23:0
Failed to find device matching 4@128:24:0
Failed to find device matching 4@128:25:0
Failed to find device matching 4@128:26:0
Failed to find device matching 4@128:27:0
Failed to find device matching 4@128:28:0
Failed to find device matching 4@128:29:0
Failed to find device matching 4@128:30:0
Failed to find device matching 4@128:31:0
Failed to find device matching 5@128:0:0
Failed to find device matching 5@128:1:0
Failed to find device matching 5@128:2:0
Failed to find device matching 5@128:3:0
Failed to find device matching 5@128:4:0
Failed to find device matching 5@128:5:0
Failed to find device matching 5@128:6:0
Failed to find device matching 5@128:7:0
Failed to find device matching 5@128:8:0
Failed to find device matching 5@128:9:0
Failed to find device matching 5@128:10:0
Failed to find device matching 5@128:11:0
Failed to find device matching 5@128:12:0
Failed to find device matching 5@128:13:0
Failed to find device matching 5@128:14:0
Failed to find device matching 5@128:15:0
Failed to find device matching 5@128:16:0
Failed to find device matching 5@128:17:0
Failed to find device matching 5@128:18:0
Failed to find device matching 5@128:19:0
Failed to find device matching 5@128:20:0
Failed to find device matching 5@128:21:0
Failed to find device matching 5@128:22:0
Failed to find device matching 5@128:23:0
Failed to find device matching 5@128:24:0
Failed to find device matching 5@128:25:0
Failed to find device matching 5@128:26:0
Failed to find device matching 5@128:27:0
Failed to find device matching 5@128:28:0
Failed to find device matching 5@128:29:0
Failed to find device matching 5@128:30:0
Failed to find device matching 5@128:31:0
Failed to find device matching 0@128:0:0
Failed to find device matching 0@128:1:0
Failed to find device matching 0@128:2:0
Failed to find device matching 0@128:3:0
Failed to find device matching 0@128:4:0
Failed to find device matching 0@128:5:0
Failed to find device matching 0@128:6:0
Failed to find device matching 0@128:7:0
Failed to find device matching 0@128:8:0
Failed to find device matching 0@128:9:0
Failed to find device matching 0@128:10:0
Failed to find device matching 0@128:11:0
Failed to find device matching 0@128:12:0
Failed to find device matching 0@128:13:0
Failed to find device matching 0@128:14:0
Failed to find device matching 0@128:15:0
Failed to find device matching 0@128:16:0
Failed to find device matching 0@128:17:0
Failed to find device matching 0@128:18:0
Failed to find device matching 0@128:19:0
Failed to find device matching 0@128:20:0
Failed to find device matching 0@128:21:0
Failed to find device matching 0@128:22:0
Failed to find device matching 0@128:23:0
Failed to find device matching 0@128:24:0
Failed to find device matching 0@128:25:0
Failed to find device matching 0@128:26:0
Failed to find device matching 0@128:27:0
Failed to find device matching 0@128:28:0
Failed to find device matching 0@128:29:0
Failed to find device matching 0@128:30:0
Failed to find device matching 0@128:31:0
Failed to find device matching 1@128:0:0
Failed to find device matching 1@128:1:0
Failed to find device matching 1@128:2:0
Failed to find device matching 1@128:3:0
Failed to find device matching 1@128:4:0
Failed to find device matching 1@128:5:0
Failed to find device matching 1@128:6:0
Failed to find device matching 1@128:7:0
Failed to find device matching 1@128:8:0
Failed to find device matching 1@128:9:0
Failed to find device matching 1@128:10:0
Failed to find device matching 1@128:11:0
Failed to find device matching 1@128:12:0
Failed to find device matching 1@128:13:0
Failed to find device matching 1@128:14:0
Failed to find device matching 1@128:15:0
Failed to find device matching 1@128:16:0
Failed to find device matching 1@128:17:0
Failed to find device matching 1@128:18:0
Failed to find device matching 1@128:19:0
Failed to find device matching 1@128:20:0
Failed to find device matching 1@128:21:0
Failed to find device matching 1@128:22:0
Failed to find device matching 1@128:23:0
Failed to find device matching 1@128:24:0
Failed to find device matching 1@128:25:0
Failed to find device matching 1@128:26:0
Failed to find device matching 1@128:27:0
Failed to find device matching 1@128:28:0
Failed to find device matching 1@128:29:0
Failed to find device matching 1@128:30:0
Failed to find device matching 1@128:31:0
Failed to find device matching 2@128:0:0
Failed to find device matching 2@128:1:0
Failed to find device matching 2@128:2:0
Failed to find device matching 2@128:3:0
Failed to find device matching 2@128:4:0
Failed to find device matching 2@128:5:0
Failed to find device matching 2@128:6:0
Failed to find device matching 2@128:7:0
Failed to find device matching 2@128:8:0
Failed to find device matching 2@128:9:0
Failed to find device matching 2@128:10:0
Failed to find device matching 2@128:11:0
Failed to find device matching 2@128:12:0
Failed to find device matching 2@128:13:0
Failed to find device matching 2@128:14:0
Failed to find device matching 2@128:15:0
Failed to find device matching 2@128:16:0
Failed to find device matching 2@128:17:0
Failed to find device matching 2@128:18:0
Failed to find device matching 2@128:19:0
Failed to find device matching 2@128:20:0
Failed to find device matching 2@128:21:0
Failed to find device matching 2@128:22:0
Failed to find device matching 2@128:23:0
Failed to find device matching 2@128:24:0
Failed to find device matching 2@128:25:0
Failed to find device matching 2@128:26:0
Failed to find device matching 2@128:27:0
Failed to find device matching 2@128:28:0
Failed to find device matching 2@128:29:0
Failed to find device matching 2@128:30:0
Failed to find device matching 2@128:31:0
Failed to find device matching 3@128:0:0
Failed to find device matching 3@128:1:0
Failed to find device matching 3@128:2:0
Failed to find device matching 3@128:3:0
Failed to find device matching 3@128:4:0
Failed to find device matching 3@128:5:0
Failed to find device matching 3@128:6:0
Failed to find device matching 3@128:7:0
Failed to find device matching 3@128:8:0
Failed to find device matching 3@128:9:0
Failed to find device matching 3@128:10:0
Failed to find device matching 3@128:11:0
Failed to find device matching 3@128:12:0
Failed to find device matching 3@128:13:0
Failed to find device matching 3@128:14:0
Failed to find device matching 3@128:15:0
Failed to find device matching 3@128:16:0
Failed to find device matching 3@128:17:0
Failed to find device matching 3@128:18:0
Failed to find device matching 3@128:19:0
Failed to find device matching 3@128:20:0
Failed to find device matching 3@128:21:0
Failed to find device matching 3@128:22:0
Failed to find device matching 3@128:23:0
Failed to find device matching 3@128:24:0
Failed to find device matching 3@128:25:0
Failed to find device matching 3@128:26:0
Failed to find device matching 3@128:27:0
Failed to find device matching 3@128:28:0
Failed to find device matching 3@128:29:0
Failed to find device matching 3@128:30:0
Failed to find device matching 3@128:31:0
Failed to find device matching 4@128:0:0
Failed to find device matching 4@128:1:0
Failed to find device matching 4@128:2:0
Failed to find device matching 4@128:3:0
Failed to find device matching 4@128:4:0
Failed to find device matching 4@128:5:0
Failed to find device matching 4@128:6:0
Failed to find device matching 4@128:7:0
Failed to find device matching 4@128:8:0
Failed to find device matching 4@128:9:0
Failed to find device matching 4@128:10:0
Failed to find device matching 4@128:11:0
Failed to find device matching 4@128:12:0
Failed to find device matching 4@128:13:0
Failed to find device matching 4@128:14:0
Failed to find device matching 4@128:15:0
Failed to find device matching 4@128:16:0
Failed to find device matching 4@128:17:0
Failed to find device matching 4@128:18:0
Failed to find device matching 4@128:19:0
Failed to find device matching 4@128:20:0
Failed to find device matching 4@128:21:0
Failed to find device matching 4@128:22:0
Failed to find device matching 4@128:23:0
Failed to find device matching 4@128:24:0
Failed to find device matching 4@128:25:0
Failed to find device matching 4@128:26:0
Failed to find device matching 4@128:27:0
Failed to find device matching 4@128:28:0
Failed to find device matching 4@128:29:0
Failed to find device matching 4@128:30:0
Failed to find device matching 4@128:31:0
Failed to find device matching 5@128:0:0
Failed to find device matching 5@128:1:0
Failed to find device matching 5@128:2:0
Failed to find device matching 5@128:3:0
Failed to find device matching 5@128:4:0
Failed to find device matching 5@128:5:0
Failed to find device matching 5@128:6:0
Failed to find device matching 5@128:7:0
Failed to find device matching 5@128:8:0
Failed to find device matching 5@128:9:0
Failed to find device matching 5@128:10:0
Failed to find device matching 5@128:11:0
Failed to find device matching 5@128:12:0
Failed to find device matching 5@128:13:0
Failed to find device matching 5@128:14:0
Failed to find device matching 5@128:15:0
Failed to find device matching 5@128:16:0
Failed to find device matching 5@128:17:0
Failed to find device matching 5@128:18:0
Failed to find device matching 5@128:19:0
Failed to find device matching 5@128:20:0
Failed to find device matching 5@128:21:0
Failed to find device matching 5@128:22:0
Failed to find device matching 5@128:23:0
Failed to find device matching 5@128:24:0
Failed to find device matching 5@128:25:0
Failed to find device matching 5@128:26:0
Failed to find device matching 5@128:27:0
Failed to find device matching 5@128:28:0
Failed to find device matching 5@128:29:0
Failed to find device matching 5@128:30:0
Failed to find device matching 5@128:31:0
Failed to find device matching 0@128:0:0
Failed to find device matching 0@128:1:0
Failed to find device matching 0@128:2:0
Failed to find device matching 0@128:3:0
Failed to find device matching 0@128:4:0
Failed to find device matching 0@128:5:0
Failed to find device matching 0@128:6:0
Failed to find device matching 0@128:7:0
Failed to find device matching 0@128:8:0
Failed to find device matching 0@128:9:0
Failed to find device matching 0@128:10:0
Failed to find device matching 0@128:11:0
Failed to find device matching 0@128:12:0
Failed to find device matching 0@128:13:0
Failed to find device matching 0@128:14:0
Failed to find device matching 0@128:15:0
Failed to find device matching 0@128:16:0
Failed to find device matching 0@128:17:0
Failed to find device matching 0@128:18:0
Failed to find device matching 0@128:19:0
Failed to find device matching 0@128:20:0
Failed to find device matching 0@128:21:0
Failed to find device matching 0@128:22:0
Failed to find device matching 0@128:23:0
Failed to find device matching 0@128:24:0
Failed to find device matching 0@128:25:0
Failed to find device matching 0@128:26:0
Failed to find device matching 0@128:27:0
Failed to find device matching 0@128:28:0
Failed to find device matching 0@128:29:0
Failed to find device matching 0@128:30:0
Failed to find device matching 0@128:31:0
Failed to find device matching 1@128:0:0
Failed to find device matching 1@128:1:0
Failed to find device matching 1@128:2:0
Failed to find device matching 1@128:3:0
Failed to find device matching 1@128:4:0
Failed to find device matching 1@128:5:0
Failed to find device matching 1@128:6:0
Failed to find device matching 1@128:7:0
Failed to find device matching 1@128:8:0
Failed to find device matching 1@128:9:0
Failed to find device matching 1@128:10:0
Failed to find device matching 1@128:11:0
Failed to find device matching 1@128:12:0
Failed to find device matching 1@128:13:0
Failed to find device matching 1@128:14:0
Failed to find device matching 1@128:15:0
Failed to find device matching 1@128:16:0
Failed to find device matching 1@128:17:0
Failed to find device matching 1@128:18:0
Failed to find device matching 1@128:19:0
Failed to find device matching 1@128:20:0
Failed to find device matching 1@128:21:0
Failed to find device matching 1@128:22:0
Failed to find device matching 1@128:23:0
Failed to find device matching 1@128:24:0
Failed to find device matching 1@128:25:0
Failed to find device matching 1@128:26:0
Failed to find device matching 1@128:27:0
Failed to find device matching 1@128:28:0
Failed to find device matching 1@128:29:0
Failed to find device matching 1@128:30:0
Failed to find device matching 1@128:31:0
Failed to find device matching 2@128:0:0
Failed to find device matching 2@128:1:0
Failed to find device matching 2@128:2:0
Failed to find device matching 2@128:3:0
Failed to find device matching 2@128:4:0
Failed to find device matching 2@128:5:0
Failed to find device matching 2@128:6:0
Failed to find device matching 2@128:7:0
Failed to find device matching 2@128:8:0
Failed to find device matching 2@128:9:0
Failed to find device matching 2@128:10:0
Failed to find device matching 2@128:11:0
Failed to find device matching 2@128:12:0
Failed to find device matching 2@128:13:0
Failed to find device matching 2@128:14:0
Failed to find device matching 2@128:15:0
Failed to find device matching 2@128:16:0
Failed to find device matching 2@128:17:0
Failed to find device matching 2@128:18:0
Failed to find device matching 2@128:19:0
Failed to find device matching 2@128:20:0
Failed to find device matching 2@128:21:0
Failed to find device matching 2@128:22:0
Failed to find device matching 2@128:23:0
Failed to find device matching 2@128:24:0
Failed to find device matching 2@128:25:0
Failed to find device matching 2@128:26:0
Failed to find device matching 2@128:27:0
Failed to find device matching 2@128:28:0
Failed to find device matching 2@128:29:0
Failed to find device matching 2@128:30:0
Failed to find device matching 2@128:31:0
Failed to find device matching 3@128:0:0
Failed to find device matching 3@128:1:0
Failed to find device matching 3@128:2:0
Failed to find device matching 3@128:3:0
Failed to find device matching 3@128:4:0
Failed to find device matching 3@128:5:0
Failed to find device matching 3@128:6:0
Failed to find device matching 3@128:7:0
Failed to find device matching 3@128:8:0
Failed to find device matching 3@128:9:0
Failed to find device matching 3@128:10:0
Failed to find device matching 3@128:11:0
Failed to find device matching 3@128:12:0
Failed to find device matching 3@128:13:0
Failed to find device matching 3@128:14:0
Failed to find device matching 3@128:15:0
Failed to find device matching 3@128:16:0
Failed to find device matching 3@128:17:0
Failed to find device matching 3@128:18:0
Failed to find device matching 3@128:19:0
Failed to find device matching 3@128:20:0
Failed to find device matching 3@128:21:0
Failed to find device matching 3@128:22:0
Failed to find device matching 3@128:23:0
Failed to find device matching 3@128:24:0
Failed to find device matching 3@128:25:0
Failed to find device matching 3@128:26:0
Failed to find device matching 3@128:27:0
Failed to find device matching 3@128:28:0
Failed to find device matching 3@128:29:0
Failed to find device matching 3@128:30:0
Failed to find device matching 3@128:31:0
Failed to find device matching 4@128:0:0
Failed to find device matching 4@128:1:0
Failed to find device matching 4@128:2:0
Failed to find device matching 4@128:3:0
Failed to find device matching 4@128:4:0
Failed to find device matching 4@128:5:0
Failed to find device matching 4@128:6:0
Failed to find device matching 4@128:7:0
Failed to find device matching 4@128:8:0
Failed to find device matching 4@128:9:0
Failed to find device matching 4@128:10:0
Failed to find device matching 4@128:11:0
Failed to find device matching 4@128:12:0
Failed to find device matching 4@128:13:0
Failed to find device matching 4@128:14:0
Failed to find device matching 4@128:15:0
Failed to find device matching 4@128:16:0
Failed to fi
...
TIA
Antonio
____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com
16 years
rpm __db issues, PK/yum transactions fail to complete
by Andrew Farris
In the last few days I've had a few issues with yum, and PackageKit transactions
failing to finish, and the processes needing to be killed. When I notice this,
I usually cannot run any other transaction either because they will all hang.
It appears something is damaging my rpm __db.xxx files... nothing rpm tries to
do after that works. Running 'rm /var/lib/__db*; rpm --rebuilddb' gets things
moving again, but it does not seem to last long before I get the same situation
occurring. So far, it seems like both yum and packagekit end up doing this, as
I alternate between them while testing. I haven't decided if yum was what
triggered the problem yet or if only PK is what causes it.
Has anyone else been running into this? I've removed those files about 10 times
so far and it should not be something I have to keep doing.
https://bugzilla.redhat.com/show_bug.cgi?id=441420
--
Andrew Farris <lordmorgul(a)gmail.com> www.lordmorgul.net
gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC 7DEB 5BD5 5F89 8E1B 8300 BF29
16 years
Upgrade to ext4, how?
by Martin Sourada
Hi,
I'd like test ext4 on my rawhide install, but do not want to do a new
install. Is there a way to upgrade my system partition
(/dev/VolGroup00/LogVol00) to ext4 without breaking things? I tried
editing /etc/fstab to use ext4dev (ext4 at first) but computer stopped
booting with newer kernels (those that had initrd generated after the
fstab change...).
If not, then I'd perhaps be willing to do a new installation, but only
via Live Desktop Spin. Is that supported?
Thanks,
Martin
16 years
rawhide report: 20080406 changes
by Fedora compose checker
New package dotconf
Libraries to parse configuration files
New package mediawiki-StubManager
An extension meant to address 'rare events' handling
New package perl-Algorithm-FastPermute
Rapid generation of permutations
New package php-pear-File-Find
Class which facilitates the search of filesystems
New package pyPdf
PDF toolkit
New package stringtemplate
A Java template engine
Updated Packages:
BackupPC-3.1.0-2.fc9
--------------------
* Sat Apr 05 2008 Johan Cwiklinski <johan AT x-tnd DOT be> 3.1.0-2
- correcting nologin path
ConsoleKit-0.2.10-3.fc9
-----------------------
* Sat Apr 05 2008 Matthias Clasen <mclasen(a)redhat.com> - 0.2.10-3
- Return PolicyKit results
* Fri Mar 14 2008 Matthias Clasen <mclasen(a)redhat.com> - 0.2.10-2
- Fix trivial dir ownership issue
Django-0.96.1-2.fc9
-------------------
* Sat Apr 05 2008 Michel Salim <salimma(a)fedoraproject.org> - 0.96.1-2
- Package .egg-info file on Fedora >= 9
PackageKit-0.1.11-1.fc9
-----------------------
* Sat Apr 05 2008 Matthias Clasen <mclasen(a)redhat.com> - 0.1.11-1
- Update to 0.1.11
anjuta-1:2.2.3-6.fc9
--------------------
* Sun Apr 06 2008 Debarshi Ray <rishi(a)fedoraproject.org> - 1:2.2.3-6
- Added 'Requires: autogen'. Closes Red Hat Bugzilla bug #441036.
ballz-1.0-3.fc9
---------------
* Sat Apr 05 2008 Hans de Goede <j.w.r.degoede(a)hhs.nl> 1.0-3
- Rebuild for new guichan
bless-0.5.2-6.fc9
-----------------
* Sat Apr 05 2008 Adel Gadllah <adel.gadllah(a)gmail.com> 0.5.2-5
- Fix build with mono-1.9+ RH #440761
bouml-4.2-2.fc9
---------------
* Sun Apr 06 2008 Debarshi Ray <rishi(a)fedoraproject.org> - 4.2-2
- Replaced 'BuildRequires: qt-devel' with 'Buildrequires: qt3-devel' on all
distributions starting from Fedora 9. Closes Red Hat Bugzilla bug #440750.
* Fri Feb 22 2008 Debarshi Ray <rishi(a)fedoraproject.org> - 4.2-1
- Version bump to 4.2. Closes Red Hat Bugzilla bug #434284.
- Introduced PHP support.
- Previous releases can not read a project saved with this version, but
projects made by previous releases can be read.
* Tue Feb 19 2008 Release Engineering <rel-eng(a)fedoraproject.org> - 3.5-2
- Autorebuild for gcc-4.3.
bzr-1.3.1-0.1.rc1.fc9
---------------------
* Fri Apr 04 2008 Toshio Kuratomi <toshio(a)fedoraproject.org> - 1.3.1-0.1.rc1
- Update to 1.3.1rc1 to fix a bug when you have a pack based remote repo and
knit based local branch.
control-center-1:2.22.0-4.fc9
-----------------------------
* Sat Apr 05 2008 Soren Sandmann <sandmann(a)redhat.com> - 2.22.0-4
- Better clone mode support. Remove debug text.
emelfm2-0.4.0-1.fc9
-------------------
* Wed Apr 02 2008 Christoph Wickert <fedora christoph-wickert de> - 0.4.0-1
- Update 0.4.0
- Enable HAL support, but dont install hal by default
- Add emelfm2-0.4-hal_flags.patch (Thanks to Uwe Helm)
- Require bzip2 for the unpack-plugin
eric-4.1.2-2.fc9
----------------
* Sat Apr 05 2008 Johan Cwiklinski <johan AT x-tnd DOT be> 4.1.2-2
- using qt4-designer and qt4-doc
* Sat Apr 05 2008 Johan Cwiklinski <johan AT x-tnd DOT be> 4.1.2-1
- 4.1.2
* Mon Mar 24 2008 Johan Cwiklinski <johan AT x-tnd DOT be> 4.1.1-2
- Qt4 package was renamed from qt4 to qt
evolution-rss-0.0.8-7.fc9
-------------------------
* Sat Apr 05 2008 Lucian Langa <cooly(a)gnome.eu.org> - 0.0.8-7
- Modify dependencies for proper F8->F9 upgrade
fuse-s3fs-0.4-9.fc9
-------------------
* Sat Apr 05 2008 Neil Horman <nhorman(a)tuxdriver.com> 0.4-9
- Fix ftruncate to set proper length
gdl-0.9-0.rc1.1.fc9
-------------------
* Sat Apr 05 2008 - Orion Poplawski <orion(a)cora.nwra.com> - 0.9-0.rc1.1
- Update to 0.9rc1
* Mon Mar 17 2008 - Orion Poplawski <orion(a)cora.nwra.com> - 0.9-0.pre6.2
- Update cvs patch to latest cvs
gdm-1:2.21.10-0.2008.04.04.2.fc9
--------------------------------
* Sat Apr 05 2008 Matthias Clasen <mclasen(a)redhat.com> - 1:2.21.10-0.2008.04.04.2
- Improve handling of CK error messages
* Sat Apr 05 2008 Ray Strode <rstrode(a)redhat.com> - 1:2.21.10-0.2008.04.04.1
- Fix jump in animation for autologin
- Fix crash if LANG="somethingbogus"
* Sat Apr 05 2008 Ray Strode <rstrode(a)redhat.com> - 1:2.21.10-0.2008.04.03.3
- Fix crash when canceling autologin
getmail-4.8.1-1.fc9
-------------------
* Sat Apr 05 2008 Rob Loos <knolderpoor(a)gmail.com> - 4.8.1-1
- Updated to release 4.8.1
- remove setup.py patch (fixed upstream)
git-1.5.4.5-3.fc9
-----------------
* Fri Apr 04 2008 James Bowes <jbowes(a)redhat.com> 1.5.4.5-3
- Remove the last two requires on git-core.
gnome-desktop-2.22.0-6.fc9
--------------------------
* Sat Apr 05 2008 Soren Sandmann <sandmann(a)redhat.com> - 2.22.0-6
- Update randr code
gnome-packagekit-0.1.11-1.fc9
-----------------------------
* Sat Apr 05 2008 Matthias Clasen <mclasen(a)redhat.com> - 0.1.11-1
- Update to 0.1.11
gnome-panel-2.22.0-11.fc9
-------------------------
* Sat Apr 05 2008 Matthias Clasen <mclasen(a)redhat.com> - 2.22.0-11
- Handle PolicyKit errors returned from ConsoleKit
gnome-session-2.22.0-2.fc9
--------------------------
* Sun Apr 06 2008 Matthias Clasen <mclasen(a)redhat.com> - 2.22.0-2
- Drop gnome-volume-manager from the default session
gnome-settings-daemon-2.22.1-0.2008.03.26.5.fc9
-----------------------------------------------
* Sat Apr 05 2008 - Soren Sandmann <sandmann(a)redhat.com> - 2.22.1-2008.03.26.5
- Update randr plugin
gtk-qt-engine-1:1.1-1.fc9
-------------------------
* Fri Apr 04 2008 Rex Dieter <rdieter(a)fedoraproject.org> 1:1.1-1
- gtk-qt-engine-1.1 for kde4 support (#441038)
hatari-1.0.1-1.fc9
------------------
* Sat Apr 05 2008 Andrea Musuruane <musuruan(a)gmail.com> 1.0.1-1
- updated to upstream 1.0.1
homebank-3.8-1.fc9
------------------
* Sat Apr 05 2008 Johan Cwiklinski <johan AT x-tnd DOT be> 3.8-1
- 3.8
inkscape-0.46-2.fc9
-------------------
* Sat Apr 05 2008 Lubomir Kundrak <lkundrak(a)redhat.com> - 0.46-2
- Fix LaTeX rendering, #441017
jhead-2.82-1.fc9
----------------
* Sat Apr 05 2008 Adrian Reber <adrian(a)lisas.de> - 2.82-1
- updated to 2.82
kdebase-runtime-4.0.3-4.fc9
---------------------------
* Sat Apr 05 2008 Kevin Kofler <Kevin(a)tigcc.ticalc.org> 4.0.3-4
- don't crash if we don't have deinterlacing support in xine-lib (#440299)
kernel-2.6.25-0.200.rc8.git3.fc9
--------------------------------
* Fri Apr 04 2008 Chuck Ebbert <cebbert(a)redhat.com>
- Remove VIA VT6212 sleep time fix, already in mainline.
* Fri Apr 04 2008 Dave Jones <davej(a)redhat.com>
- USB: VIA VT6212 10us EHCI sleep time select. (#438599)
* Fri Apr 04 2008 Jarod Wilson <jwilson(a)redhat.com>
- firewire: add logging of register access failures to debug spew
- firewire: don't append AT packets to halted contexts (because certain
crappy controllers lock up if you do).
libflashsupport-000-0.4.svn20070904
-----------------------------------
* Sat Apr 05 2008 Warren Togami <wtogami(a)redhat.com> 000-0.4.svn20070904
- x86_64 requires i386 of itself and nspluginwrapper.i386 through file dependencies.
This really sucks but we currently have no other way of doing cross-arch dependencies.
libtorrent-0.11.8-4.fc9
-----------------------
* Sat Apr 05 2008 Christopher Aillon <caillon(a)redhat.com> - 0.11.8-4
- Add missing #includes so this compiles against GCC 4.3
* Mon Feb 18 2008 Fedora Release Engineering <rel-eng(a)fedoraproject.org> - 0.11.8-3
- Autorebuild for GCC 4.3
lua-5.1.3-4.fc9
---------------
* Sat Apr 05 2008 Hans de Goede <j.w.r.degoede(a)hhs.nl> 5.1.3-4
- Not only own $libdir/lua/5.1 and $datadir/lua/5.1 but also $libdir/lua
and $datadir/lua for proper removal of these dirs upon lua removal
ntfs-config-1.0-0.6.rc5.fc9
---------------------------
* Sat Apr 05 2008 Xavier Lamien <lxtnow(a)gmail.com> - 1.0-0.6.rc5
- Moved to python_sitearch path.
perl-Proc-ProcessTable-0.42-1.fc9
---------------------------------
* Sat Apr 05 2008 Tom "spot" Callaway <tcallawa(a)redhat.com> 0.42-1
- update to 0.42
- patch to define ARG_MAX (since for some unknown reason, it isn't defined anymore)
python-cerealizer-0.6-3.fc9
---------------------------
* Sat Apr 05 2008 Tom "spot" Callaway <tcallawa(a)redhat.com> 0.6-3
- Add egg-info files (fix FTBFS bz 440814)
python-elixir-0.5.2-1.fc9
-------------------------
* Sat Apr 05 2008 James Bowes <jbowes(a)redhat.com> 0.5.2-1
- Update to 0.5.2
python-gammu-0.24-3.fc9
-----------------------
* Sat Apr 05 2008 Xavier Lamien <lxtnow(a)gmail.com> - 0.24-3
- Added missing file on Rawhide.
* Tue Feb 19 2008 Fedora Release Engineering <rel-eng(a)fedoraproject.org> - 0.24-2
- Autorebuild for GCC 4.3
pyxdg-0.15-6.fc9
----------------
* Sat Apr 05 2008 Tom "spot" Callaway <tcallawa(a)redhat.com> - 0.15-6
- add egg-info (fixes FTBFS bz 440813)
qucs-0.0.13-3.fc9
-----------------
* Sat Apr 05 2008 Eric Tanguy <eric.tanguy(a)univ-nantes.fr> - 0.0.13-3
- Modify BR from qt-devel to qt3-devel
revisor-2.1.0-1rc7.fc9
----------------------
* Sat Apr 05 2008 Jeroen van Meeuwen <kanarip a fedoraunity.org> 2.1.0-1rc7
- Latest rebuild
* Wed Jan 30 2008 Jeroen van Meeuwen <kanarip a fedoraunity.org> 2.1.0-1rc5
- Add Rescue Image capabilities
- Add modserver into package
- Remove conflicts
- Updates
- Let's not build revisor-cobbler on ppc/ppc64
* Thu Dec 20 2007 Jeroen van Meeuwen <kanarip a fedoraunity.org> 2.1.0-1rc2
- Updates to many components related to plugins and kickstart
rrdtool-1.3-0.10.beta4.fc9
--------------------------
* Sat Apr 05 2008 Jarod Wilson <jwilson(a)redhat.com> 1.3.0-0.10.beta4
- Fix use of rrd_update in php bindings (#437558)
rtorrent-0.7.8-3.fc9
--------------------
* Sat Apr 05 2008 Christopher Aillon <caillon(a)redhat.com> - 0.7.8-3
- Fix build against newer sigc++
- Fix build against GCC 4.3
* Mon Feb 18 2008 Fedora Release Engineering <rel-eng(a)fedoraproject.org> - 0.7.8-2
- Autorebuild for GCC 4.3
scons-0.98.0-1.fc9
------------------
* Sat Apr 05 2008 Gerard Milmeister <gemi(a)bluewin.ch> - 0.98-1
- new release 0.98
sear-0.6.3-10.fc9
-----------------
* Sat Apr 05 2008 Wart <wart at kobold.org> 0.6.3-10
- Add patch for newer libsigc++ (BZ #440772)
selinux-policy-3.3.1-28.fc9
---------------------------
* Fri Apr 04 2008 Dan Walsh <dwalsh(a)redhat.com> 3.3.1-28
- Allow radvd to use fifo_file
- dontaudit setfiles reading links
- allow semanage sys_resource
- add allow_httpd_mod_auth_ntlm_winbind boolean
- Allow privhome apps including dovecot read on nfs and cifs home
dirs if the boolean is set
* Tue Apr 01 2008 Dan Walsh <dwalsh(a)redhat.com> 3.3.1-27
- Allow nsplugin to read /etc/mozpluggerrc, user_fonts
- Allow syslog to manage innd logs.
- Allow procmail to ioctl spamd_exec_t
shadow-utils-2:4.1.1-1.fc9
--------------------------
* Mon Apr 07 2008 Peter Vrabec <pvrabec(a)redhat.com> 2:4.1.1-1
- upgrade
shorewall-4.0.10-1.fc9
----------------------
* Sun Apr 06 2008 Jonathan G. Underwood <jonathan.underwood(a)gmail.com> - 4.0.10-1
- Update to version 4.0.10
- Remove 4.0.9 patches
specto-0.2.2-1.fc9
------------------
* Thu Aug 02 2007 Xavier Lamien <lxtnow[at]gmail.com> - 0.2.2-1
- Updated Release.
sunbird-0.8-1.fc9
-----------------
* Fri Apr 04 2008 Lubomir Kundrak <lkundrak(a)redhat.com> 0.8-1
- 0.8 GA
system-config-keyboard-1.2.14-2.fc9
-----------------------------------
* Sat Apr 05 2008 Bill Nottingham <notting(a)redhat.com> 1.2.14-2
- Do not show in KDE and Gnome menus
- Rework specfile
udev-120-2.fc9
--------------
* Sat Apr 05 2008 Harald Hoyer <harald(a)redhat.com> 120-2
- removed warning about deprecated /lib/udev/devices (rhbz#440961)
- replaced /usr/bin/find with shell find function (rhbz#440961)
vpnc-0.5.1-5.fc9
----------------
* Sat Apr 05 2008 Michal Schmidt <mschmidt(a)redhat.com> - 0.5.1-5
- vpnc-script: fix 'ip link ...' syntax.
wings-0.99.02-1.fc9
-------------------
* Thu Mar 27 2008 Gerard Milmeister <gemi(a)bluewin.ch> - 0.99.02-1
- new releae 0.99.02
* Sun Apr 08 2007 Gerard Milmeister <gemi(a)bluewin.ch> - 0.98.36-1
- new version 0.98.36
* Thu Feb 15 2007 Gerard Milmeister <gemi(a)bluewin.ch> - 0.98.32b-11
- add optflags (bugzilla 228925)
xfce4-battery-plugin-0.5.0-4.fc9
--------------------------------
* Sat Apr 05 2008 Christoph Wickert <fedora christoph-wickert de> - 0.5.0-4
- Fix for kernel 2.6.24 (bugzilla.xfce.org #3938)
- Lower acpi polling. (bugzilla.xfce.org #2948)
- Rebuild with gcc 4.3.0
* Tue Aug 28 2007 Christoph Wickert <fedora christoph-wickert de> - 0.5.0-3
- Fix for x86_64 kernels >= 2.6.21. (bugzilla.xfce.org #3190)
- Update license tag
xorg-x11-drv-radeonhd-1.1.0-0.7.20080404git.fc9
-----------------------------------------------
* Fri Apr 04 2008 Hans Ulrich Niedermann <hun(a)n-dimensional.de> - 1.1.0-0.7.20080404git
- Do not create fedora snapshot git branch unless necessary
- New snapshot (upstream commit db2c3948d5a398047b3a881f6f88541dc963d22e):
- db2c3948: Fix LVTMA code to also handle single link DVI correctly.
- 55e3b21e: HDMI Type A is single link DVI while B is dual link.
- d53f2201: Add source select to DDIA block.
- be9055f0: Fixed argument order to rhdAtomGetTableRevisionAndSize().
- 1623f86f: Added missing rhd_ddia.c/rhd_ddia.o to Imakefile.
- 186c345c: Print output name for sensed type.
- d7d63b25: Print sensed type also for RandR.
- 6d628f56: Make debugging output of HPD verbose about the result.
- 811b0cd6: Added quirk table entry for a different Sapphire X1300
- 89cfb738: Add support for RS690 DDIA digital block.
- b6418a97: Add debugging aids.
- c8ad2599: Reset CRTC horizontal counter replication.
- bd11d76a: Handle AtomBIOS TMDS PLL parameters correctly.
- 806d9536: HDMI Type B connector is dual link capable.
- ae3171b9: Add TMDS PLL macro control values for M54 (0x7145).
- 19a6eb46: Chipset name review.
- 96f36339: Fixed imake build.
- 3d62e9a1: Cosmetics: Move RV620/635 to a more sensible position in our devices list.
- 9de85904: RHDPLLsInit: PLL2: Add missing " else " in "if () {}{}"... Duh.
- 00f182d6: Use correct option name for (yet unused) TVMode option.
- 98d328b0: Fix endless loop.
- 427d9553: If available read panel dithering parameters from AtomBIOS.
- c336508e: Remove DVI_DUAL as a type which can be detected by load detection.
- bf8bda88: Make variable and enum names more consistent.
- db0d6058: Fix a memory leak.
- 098cf71d: Make test for DIG2 more consistent.
- 46a40c82: Add #ifdef wrappers around AtomBIOS related code.
- 54f491f9: Add AtomBIOS based UNIPHY support for RV620/635.
- 2d81ffc7: Fix a wrong type in ATOM_ANALOG_TV_INFO in upstream version of atombios.h.
- cab03118: DxCRTC: Fix disabling check.
- 52f04a7f: TMDSA: Fix sensing with respect to duallink.
- 42d3201b: PLL: further fall-out of removal of validation callback for our hw.
- 8f499c38: DVI is on TMDSB not LVDS.
- 56a264f8: Set Connector element already in rhdRROutputDetect().
- 478bda79: Fix issues with DDC on RV620/635.
- e5dddbc2: Fix issues with DAC load detection on RV620/635.
- 5596d06d: Fix issues with DAC load detection and erronous DDC detection on RV620/635.
- c9ccc4c4: Resolve unknown registers.
- aa7037a7: Remove stale structure elements.
- dfe36048: Changed heuristics for encoder link enabling.
- 153331e8: Properly restore Encoder and Transmitter.
- 6742f79e: RV620: Add Pixelclock support.
- 807e525a: Implement the hardware level scaling code.
- fd6a7abf: Restructure FMT block handling.
- 2e1f55b0: Consolidate handling of dual link TMDS displays.
- f0256f38: List explicite arguments for FMT block programming.
- 59de4071: Fix identification of end-of-code table data tables and GoldenSettings search.
- b3df388f: Add RV620/RV635 devices.
- c13650e6: Add KLDSKP_LVTMA and UNIPHYs to connector handling.
- 0dee42c5: Add support for new DIG blocks on RV620/635.
- 8dabb69a: Fix structure names in rhd_output.c.
- 80fb6b3f: Fix copy-over artefacts from rhd_conntest.
- 252491e4: Adding KLDSKP_LVTMA and UNIPYA/B as output types.
- 6dab67a8: Add RHD_CONNECTOR_DVI_SINGLE to be able to mark a single link connector.
- abb188fe: Separate query for temporal and spatial dithering.
- 4ec30282: Add more verbose output on GoldenSettings matching.
- a0c11368: Add support enumerated object IDs to the connector table parser.
- b280b417: Support for TMDSA dual link load detection (untested!).
- dec87ba6: Add support for dual link DVI panels (untested!).
- cf8eea25: Add support for two new ObjectIDs required for RV620/635.
- 55ce4f82: Added own version of AtomBIOS getConditionalGoldenValues().
- 283c2d2e: Fix GPIO routing for DDC in RV620/635.
- d499a616: Fix GPIO routing for DDC for RV620/635 in rhd_conntest.c.
- 8de4cd9a: Locate data tables embedded in AtomBIOS command tables.
- e29024d9: Consolidate load detection for R5xx/r6xx in rhd_conntest.
- f021c0cf: Add support for DAC load detection and I2C for RV620/RV635 to rhd_conntest.
- 481df402: Add stubs for the PLL subsystem.
- 3ba1c093: Add support for the DAC output subsystem for RV620/RV635.
- b08e64ec: Add I2C subsystem support for RV620/RV635.
- 089801d4: Add RV620/RV635 PCI IDs.
- 47298a34: Add support for sensing and programming different analog outputs.
- 2d42e5b7: Add monitor support for TVs.
- 8f06626d: Add an option to pass the TV standard to override boot default.
- 3fe49f2a: Fix spelling of 'Supp(p)orted' to match the fixed spelling in atombios.h.
- 2bcabe12: Add parsing of TV releated data tables to the AtomBIOS support.
- 726f6da1: Add TV detection do DAC load detection.
- e1605dfb: Be more verbose about fb parameters.
- 5163b9fb: Get and store verbosity level.
- 00e1b025: Restore original order of CRTCRestore and VGARestore.
yakuake-2.9.1-1.fc9
-------------------
* Sat Apr 05 2008 2008 Johan Cwiklinski <johan AT x-tnd DOT be> - 2.9.1-1
- 2.9.1
- use of %{cmake_kde4} macro
- remove no longer needeed chrpath
zeroinstall-injector-0.32-1.fc9
-------------------------------
* Sat Apr 05 2008 Michel Salim <salimma(a)fedoraproject.org> - 0.32-1
- Update to 0.32
- Package .egg-info file on Fedora >= 9
Broken deps for i386
----------------------------------------------------------
boo-0.8.1.2865-2.fc9.i386 requires mono(NAnt.Core) = 0:0.85.2478.0
boo-0.8.1.2865-2.fc9.i386 requires mono(NAnt.DotNetTasks) = 0:0.85.2478.0
evolution-brutus-1.1.28.7-2.fc8.i386 requires libcamel-1.2.so.10
flumotion-0.4.2-3.fc9.i386 requires pycrypto
kazehakase-0.5.0-1.fc9.2.i386 requires gecko-libs = 0:1.8.1.10
mediawiki-openid-0.7.0-5.noarch requires php-pear-Auth-OpenID
mediawiki-openid-0.7.0-5.noarch requires php-pear-Services-Yadis
perl-clearsilver-0.10.4-5.fc8.i386 requires perl(:MODULE_COMPAT_5.8.8)
thunderbird-lightning-0.8-1.fc9.i386 requires libxpcom_core.so
util-vserver-build-0.30.214-2.fc8.i386 requires libbeecrypt.so.6
vtk-examples-5.0.3-22.fc9.i386 requires vtkdata = 0:5.0.3
vtk-testing-5.0.3-22.fc9.i386 requires vtkdata = 0:5.0.3
Broken deps for x86_64
----------------------------------------------------------
boo-0.8.1.2865-2.fc9.x86_64 requires mono(NAnt.Core) = 0:0.85.2478.0
boo-0.8.1.2865-2.fc9.x86_64 requires mono(NAnt.DotNetTasks) = 0:0.85.2478.0
evolution-brutus-1.1.28.7-2.fc8.i386 requires libcamel-1.2.so.10
evolution-brutus-1.1.28.7-2.fc8.x86_64 requires libcamel-1.2.so.10()(64bit)
flumotion-0.4.2-3.fc9.x86_64 requires pycrypto
kazehakase-0.5.0-1.fc9.2.x86_64 requires gecko-libs = 0:1.8.1.10
mediawiki-openid-0.7.0-5.noarch requires php-pear-Auth-OpenID
mediawiki-openid-0.7.0-5.noarch requires php-pear-Services-Yadis
perl-clearsilver-0.10.4-5.fc8.x86_64 requires perl(:MODULE_COMPAT_5.8.8)
thunderbird-lightning-0.8-1.fc9.x86_64 requires libxpcom_core.so()(64bit)
util-vserver-build-0.30.214-2.fc8.x86_64 requires libbeecrypt.so.6()(64bit)
vtk-examples-5.0.3-22.fc9.x86_64 requires vtkdata = 0:5.0.3
vtk-testing-5.0.3-22.fc9.x86_64 requires vtkdata = 0:5.0.3
Broken deps for ppc
----------------------------------------------------------
evolution-brutus-1.1.28.7-2.fc8.ppc requires libcamel-1.2.so.10
evolution-brutus-1.1.28.7-2.fc8.ppc64 requires libcamel-1.2.so.10()(64bit)
flumotion-0.4.2-3.fc9.ppc requires pycrypto
kazehakase-0.5.0-1.fc9.2.ppc requires gecko-libs = 0:1.8.1.10
mediawiki-openid-0.7.0-5.noarch requires php-pear-Auth-OpenID
mediawiki-openid-0.7.0-5.noarch requires php-pear-Services-Yadis
perl-clearsilver-0.10.4-5.fc8.ppc requires perl(:MODULE_COMPAT_5.8.8)
thunderbird-lightning-0.8-1.fc9.ppc requires libxpcom_core.so
util-vserver-build-0.30.214-2.fc8.ppc requires libbeecrypt.so.6
vtk-examples-5.0.3-22.fc9.ppc requires vtkdata = 0:5.0.3
vtk-testing-5.0.3-22.fc9.ppc requires vtkdata = 0:5.0.3
Broken deps for ppc64
----------------------------------------------------------
evolution-brutus-1.1.28.7-2.fc8.ppc64 requires libcamel-1.2.so.10()(64bit)
flumotion-0.4.2-3.fc9.ppc64 requires pycrypto
kazehakase-0.5.0-1.fc9.2.ppc64 requires gecko-libs = 0:1.8.1.10
mediawiki-StubManager-1.2.0-1.fc9.noarch requires mediawiki >= 0:1.10
mediawiki-openid-0.7.0-5.noarch requires php-pear-Auth-OpenID
mediawiki-openid-0.7.0-5.noarch requires php-pear-Services-Yadis
mediawiki-openid-0.7.0-5.noarch requires mediawiki
perl-Test-AutoBuild-darcs-1.2.2-3.fc9.noarch requires darcs >= 0:1.0.0
perl-clearsilver-0.10.4-5.fc8.ppc64 requires perl(:MODULE_COMPAT_5.8.8)
thunderbird-lightning-0.8-1.fc9.ppc64 requires libxpcom_core.so()(64bit)
util-vserver-build-0.30.214-2.fc8.ppc64 requires libbeecrypt.so.6()(64bit)
vtk-examples-5.0.3-22.fc9.ppc64 requires vtkdata = 0:5.0.3
vtk-testing-5.0.3-22.fc9.ppc64 requires vtkdata = 0:5.0.3
16 years
Graphic install Fedora Last build
by Enrique Garcia
I tried to install Fedora Beta 9 32 and 64 bits and 32 from bittorrent
and ALL can not be installed because the anaconda graphic don't works
with a NDivia 8500GT and Samsung LCD TV Monitor all i can see it's
lines in the windows, All fedora installs works fine but you have to
change something in Fedora 9
regards
16 years
Re: coreutils is installed, cannot su -, and cannot add user still running as root
by Antonio Olivares
> ----- Original Message ----
> From: Antonio Olivares <olivares14031(a)yahoo.com>
> To: fedora-test-list(a)redhat.com
> Sent: Monday, April 7, 2008 7:46:05 AM
> Subject: coreutils is installed, cannot su -, and cannot add user still running as root
>
> Dear all,
>
> I have run the updates on this machine, the fedora 7
> machine updated to rawhide. I cannot add users and
> still cannot add users to troubleshoot errors.
>
> [root@localhost ~]# system-config-users
> The program 'system-config-users.py' received an X
> Window System error.
> This probably reflects a bug in the program.
> The error was 'BadName (named color or font does not
> exist)'.
> (Details: serial 91 error_code 15 request_code 45
> minor_code 0)
> (Note to programmers: normally, X errors are
> reported asynchronously;
> that is, you will receive the error a while after
> causing it.
> To debug your program, run it with the --sync
> command line
> option to change this behavior. You can then get a
> meaningful
> backtrace from your debugger if you break on the
> gdk_x_error() function.)
> [root@localhost ~]# system-config-users --sync
> The program 'system-config-users.py' received an X
> Window System error.
> This probably reflects a bug in the program.
> The error was 'BadName (named color or font does not
> exist)'.
> (Details: serial 91 error_code 15 request_code 45
> minor_code 0)
(Note to programmers: normally, X errors are
reported asynchronously;
that is, you will receive the error a while after
causing it.
To debug your program, run it with the --sync
command line
option to change this behavior. You can then get a
meaningful
backtrace from your debugger if you break on the
gdk_x_error() function.)
[root@localhost ~]# rpm -qa coreutils
coreutils-6.10-17.fc9.i386
[root@localhost ~]#
I updated to today's rawhide report, and I get the
following error message
*** removed to save space ****
(94/94): upstart-0.3.9-15 100%
|=========================| 243 kB 00:00
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Check Error:
file /usr/sbin/vipw from install of
shadow-utils-4.1.1-1.fc9.i386 conflicts with file from
package util-linux-2.13-0.54.1.fc7.i386
file /usr/share/man/man8/vipw.8.gz from install of
shadow-utils-4.1.1-1.fc9.i386 conflicts with file from
package util-linux-2.13-0.54.1.fc7.i386
Error Summary
-------------
So I ran it with
[root@localhost ~]# ./nodep
and got most of the updates.
How can I fix this issue?
Thanks,
Antonio
____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
I can fix this one by doing an
# rpm -e util-linux-2.13-0.54.1.fc7.i386
But the others, should I remove X and reinstall it?
____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com
16 years
F9 and selinux
by Anne Wilson
I gave up on the beta install as I couldn't get anything working at all. My
network settings wouldn't stick, and despite the fact that
system-config-keyboard showed that I was on a UK keyboard, I was still
getting US configuration. Every attempt to change it resulted in an AVC.
Every attempt to run the required selinux restorcon commands resulted in a
failure, saying that the file or directory did not exist.
I installed the kde live CD, only to find that I have the same problems. I
can't remember the command to relabel everything, but it seems to me that
that's the best bet. Can someone please prompt me?
Anne
16 years
Gah! Moving panel icons no KDE4/rawhide?
by Gilboa Davara
Hello all,
I've tried to remove the kick-off application launcher and replace it
with the traditional application launcher.
By itself, it worked, but it shifted all the panel widgets to the left
and there's no visible means to return them to their original position.
(Google didn't help either)
Far worse, I cannot seem to find a method of adding application
launchers (Firefox, evolution, konq, etc) to the panel, either. (Now
that kickoff menu is removed).
Welp?
- Gilboa
16 years