Bling?
by Brian C. Huffman
Is there a project for the new accelerated compositing that's being
merged into Xorg and associated apps? I'd like to be able to follow the
status like I do here on the fedora distro.
Thanks,
Brian
18 years, 3 months
Re: Fedora Core 5 Status
by Horst H. von Brand
Philippe Rigault <prigault(a)oricom.ca> wrote:
> > Due to circumstances outside of our control, we're going to be unable to
> > keep to the scheduled date of March 15th for the release of FC5 and
> > instead are going to have to make the release date Monday, March 20th.
> > While unfortunate in some ways, this gives us the opportunity to pull in
> > the final GNOME 2.14 tarballs which should be available on Monday
> > assuming the changes are suitably minor.
> I have two problems with this:
> The first is that FC5 will be released essentially _untested_ after two
> of its main components were upgraded to a stable release after FC5test3:
> - gcc 4.1.0
> - glibc-2.4
And the kernel has been updated almost daily, but that doesn't count?
> It could be argued that FC5 will be _released_ with a stable release of its
> compiler and C library, but not that this had been tested.
Can't have it both ways (fix bugs timely + ultra-tested software only)...
> The second goes the same way, arguing that if test3 is the latest test
> release, any new major component should _not_ be upgraded to a new release,
> which is particularly true for a big beast like GNOME.
There we could perhaps agree... but presumably the changes between the
current one and the final release are minor, bugfixes only?
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
18 years, 3 months
Epson scanner problem - more information
by David Fletcher
I'm starting a fresh thread on this because I believe there is a bug in a USB
driver.
My scanner used to work with FC3 until there was an upgrade which killed it. I
managed to get it working again by removing some rpms and installing older
ones.
Now I have found that with another machine with an identical motherboard and
processor, but running FC5t3, the same scanner won't work with that machine
either.
But, using my old machine which I kept for the purpose of fiddling with things
without the worry of messing up my main machine, I can install FC5t3 on that,
and the same scanner works, so long as the scanner is connected and switched
on before user login. This machine looks pretty slow these days, having a
Celeron 633 and one of the early USB motherboards with two USB 1.1 sockets,
but it works with my scanner.
There are two bugzilla reports that seem relevant to this, 149027 and 183063.
My hardware which does not play nicely:-
Epson Perfection 2450 Photo scanner
Intel D865PERL motherboard
With the final FC5 due to be released soon, could we please have this sorted
out? I have been in contact with the maintainer of the Epson driver, and hope
to hear from him again over the weekend, but if the scanner works with one
machine I don't think it is likely to be Epson driver that's at fault. I
think it's more likely to be a USB system driver. Is that reasonable?
If there are any diagnostic tests I can run on my Intel boards to find out
exactly what chips they have on them, and help trace the cause of this
problem, please tell me what to run and I'll post the logs back to whoever
needs them.
Dave Fletcher
--
Registered Linux user number 393408
18 years, 3 months
Trivial package updater improvements
by Josh
Hello all,
I'm all excited for the final release and looks like things are coming along nicely ..
While updating my FC5T3 install using package updater, I noticed that the popup window width keeps varying whenever downloading/updating packages with long names .
Since the title ("Downloading and Uploading" is displayed in bold, only the package names can be displayed instead of displaying "Downloading or Uploading" again with the package name. This will probably keep the window width the same.
Josh
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
18 years, 3 months
Stellarium very flaky - slow and crashes or causes log outs.
by Dan Thurman
For fun,
I tried to run Stellarium in FC5-T3 and noticed:
- Very slow on my 900Mhz, 512MB system. Cursor is very slugglish
- When opened, opens FULL SCREEN, if there are any problems - hard to
get out of it
- Caused my system to log me out
- Hard-Crashed FC5-T3 and forced a reboot
I guess, this program is a good system stress tester and buster
for FC5-T3 :-) ?
Dan
18 years, 3 months
ipw2200 + dhclient: No go
by Horst H. von Brand
For some time now (perhaps 2 weeks?) in rawhide ipw2200 doesn't work with
dhclient. The interface associates fine, but dhclient doesn't get an
IP. Using ifconfig directly (with a free IP address on the wireless
network) doesn't work either.
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria +56 32 654239
Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
18 years, 3 months
Fedora Core 4 Test Update: perl-PDL-2.4.2-2.fc4
by Jason Vas Dias
---------------------------------------------------------------------
Fedora Test Update Notification
FEDORA-2006-143
2006-03-10
---------------------------------------------------------------------
Product : Fedora Core 4
Name : perl-PDL
Version : 2.4.2
Release : 2.fc4
Summary : PDL Perl module
Description :
PDL ("Perl Data Language") gives standard Perl the ability to
compactly store and speedily manipulate the large N-dimensional data
arrays which are the bread and butter of scientific computing. PDL
turns perl in to a free, array-oriented, numerical language similar to
such commercial packages as IDL and MatLab.
---------------------------------------------------------------------
* Fri Mar 10 2006 Jason Vas Dias <jvdias(a)redhat.com> - 2.4.2-2
- Further code cleanup & CFLAGS settings required to enable tests
to succeed on all platforms
* Thu Mar 9 2006 Jason Vas Dias <jvdias(a)redhat.com> - 2.4.2-2
- Enable tests to succeed on ia64 (remove casts from int to * !)
* Fri Feb 3 2006 Jason Vas Dias <jvdias(a)redhat.com> - 2.4.2-2
- rebuild for new perl-5.8.8
- enable build to succeed without perl-PDL being installed :-)
* Sun Sep 25 2005 Warren Togami <wtogami(a)redhat.com> - 2.4.2-2
- Ship pdldoc.db, tune build dependencies and file permissions (#163219 scop)
* Fri May 27 2005 Warren Togami <wtogami(a)redhat.com> - 2.4.2-1
- 2.4.2
- filter perl(Inline) from provides (#158733)
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/4/
a46a71bf5496d1b5146115d3b5c94df9b580b211 SRPMS/perl-PDL-2.4.2-2.fc4.src.rpm
4efa00b3645309374bf7ce86de575717801f9a43 ppc/perl-PDL-2.4.2-2.fc4.ppc.rpm
7802a273a3560f9593c5ede327bf8e6f8e2862f8 ppc/debug/perl-PDL-debuginfo-2.4.2-2.fc4.ppc.rpm
1a797f097d22e1a1b3e06a657fcaa875cdb9ee0f x86_64/perl-PDL-2.4.2-2.fc4.x86_64.rpm
7a54bda281144a2187e22c713ddbae4bb07e7329 x86_64/debug/perl-PDL-debuginfo-2.4.2-2.fc4.x86_64.rpm
2369f8a6a6dd8fe3c2aa099ab74b1ef27ace2e19 i386/perl-PDL-2.4.2-2.fc4.i386.rpm
1ff71d45fdb9f48b282f528969d70a96a19e9569 i386/debug/perl-PDL-debuginfo-2.4.2-2.fc4.i386.rpm
This update can be installed with the 'yum' update program. Use 'yum update
package-name' at the command line. For more information, refer to 'Managing
Software with yum,' available at http://fedora.redhat.com/docs/yum/.
---------------------------------------------------------------------
18 years, 3 months
Re: Fedora Core 5 Status
by Philippe Rigault
On Friday 10 March 2006 13:58, you wrote:
> On Fri, 2006-03-10 at 12:20 -0500, Philippe Rigault wrote:
> > I have two problems with this:
> >
> > The first is that FC5 will be released essentially _untested_ after two
> > of
>
> its
>
> > main components were upgraded to a stable release after FC5test3:
> > - gcc 4.1.0
> > - glibc-2.4
> >
> > It could be argued that FC5 will be _released_ with a stable release of
> > its compiler and C library, but not that this had been tested.
>
> The changes between what we shipped in test3 and what we're going to be
> shipping are extremely small.
Sure, only 2442 RPM packages have been rebuilt out of 2442.
> And we _always_ have to fix bugs in
> things between test3 and the final release, sometimes larger ones than
> the diff present there.
Understood, but there should be a rule that after the last release candidate,
there can not be _any_ major change (such as one that triggers recompilation
of all packages) and that only major regressions be fixed. And in case a
major change must occur (to fix showstoppers only), then at least one more
release candidate is warranted.
I find GCC to be an example to follow in the way they deal with releases, both
in terms of policies and in terms of enforcing them. Release candidates
(which test3 should be) are exactly that, an ideal release candidate is one
that is not modified at all before release. A (good) consequence of that is
that one never knows how many RC will be necessary, all they know is that
quality and process is what drives releases.
> > The second goes the same way, arguing that if test3 is the latest test
> > release, any new major component should _not_ be upgraded to a new
> > release, which is particularly true for a big beast like GNOME.
>
> Again, the changes going in at this point are all small targeted bug
> fixes as they wind down their release cycle.
>
> Trust me, we're looking at diffs of everything that's going in at this
> point and if some component of GNOME goes off and rewrites a huge chunk
> of how it works, we're not going to pull it in.
This point already has 100% of packages different from what I last tested in
core3.
I trust you and other Fedora developers for the quality of your work, but it
is entirely beside the point.
The point of testing is that you avoid surprises, and you always apply the
same simple rules consistently.
My machines trust neither you nor me.
Respecting arbitrary timelines for final releases (especially by a few weeks),
although desirable, is of importance close to zero to me compared to
quality.
Cheers,
Philippe.
18 years, 3 months
Strange power management behaviour
by Camilo Mesias
Hi,
I wonder if anyone has seen strange behaviour from the power management?
I'm not sure if I could pin down the details of the problems, but things
like:
* screensaver activating periodically, even if there has been input (I
saw this one time and it hasn't reproduced itself)
* strange behaviour at the moment when external power is applied or
removed to the laptop, eg. unplug from mains and the machine suspends
immediately (the battery is in fine condition at this point); also,
start suspend and unplug from the mains before the suspend has
completed, when the machine resumes it immediately suspends itself again.
The PM prefs are
[on AC]
display to sleep when inactive (=30 mins)
computer to sleep when inactive (=never)
lid closed: suspend
[battery]
display to sleep when inactive (=5 mins)
computer to sleep when inactive (=20 mins)
lid closed: suspend
battery critical: shutdown
[general]
sleep type when inactive: suspend
The behaviour isn't a show stopper but it is a bit annoying and unpolished.
-Cam
--
<--
camilo(a)mesias.co.uk
18 years, 3 months