FC3test2 heads-up, and easier development schedule tracking

[Elliot Lee]

Fedora Core 3 test 2 is devel-freezing on Wednesday, September 1. If there 
are bugs that need fixing by then, please make sure that they get 
needed love & attention. Install testing of the devel tree is especially 
valuable.

If you'd like an easier way to keep track of what's happening with
development, http://fedora.redhat.com/participate/schedule/ now has a link
to subscribe to the schedule in your favorite calendaring solution
(evolution, mozilla, etc.).

Thanks
-- Elliot
The daring is in the doing

http://people.redhat.com/sopwith/

[Steve G]

> Fedora Core 3 test 2 is devel-freezing on Wednesday, September 1. If
> there 
> are bugs that need fixing by then, please make sure that they get 
> needed love & attention. 
Can somebody please update the dialog package? BZ #129239. All you need to do is
download the latest tarball and change the Source line in the spec file. dialog
as it is today is unusable for me. The ccs configurations tools I've written are
also broken because of the same bug in dialog.

Also, the current glibc-kernheaders breaks compilation of dosfstools. BZ #127526.
This needs attention since it breaks the build.

Thanks,
-Steve Grubb


		
_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush

[Jef Spaleta]

On Thu, 26 Aug 2004 15:06:27 -0400 (EDT), Elliot Lee <sopwith(a)redhat.com&gt; wrote:
>  Fedora Core 3 test 2 is devel-freezing on Wednesday, September 1. If
> there
>  are bugs that need fixing by then, please make sure that they get
>  needed love & attention. Install testing of the devel tree is especially
>  valuable. 
You asked for it....... i just did a fresh install of the development tree:
Workstation install... no custom packages
/home and /usr/local  partitions unformated
/  /boot /var /usr  all formatted clean

1)firstboot in graphical mode traced back on my in the Activation module.
I'm going to have to go back and run firstboot again and take a
digital image so i can transcribe the traceback text before I can file
this.
1a)firstboot in text mode mostly worked... the soundcard detection
didnt, and the tui interface for the printer setup left some ascii art
artifects when switching "screens"... things like text dialog buttons
lingering into the next text screen when choosing the printer location
and driver.  test page printing worked in text mode firstboot

2)no cdrom or floppy mount points were created.
/dev/fd0 device is created.. but fstab doesnt have an entry for it.
/dev/hdb is my cdrom drive and it mounts correctly using mount on the
commandline
but no /dev/cdrom link is created and no fstab entry.

I'm really starting to think my idea for a command called
"give-me-my-floppy-back-now-damn-it" would be a good idea

3)plugging in usb devices and i dont get an fstab entry on hotplug.
udev is creating the sdX and sgY devices. I've commented on this
before and the problem is still there. I have to forcible restart
haldaemon to see updated fstab entries for usbdrives.. I was hoping
what i was seeing before was an artifact of something i did on my
fc3t1 based install. But I'm still seeing this with a fresh install
directly from the development tree.

4)opening the Computer icon on my desktop is making nautilus peg a cpu
at 99% until i forcible kill nautilus.  Haven't seen this before.
Anyone else seeing this?

5)usb scanner still seems to work, shockingly.

6)looking for a way as a user to set a default printer.... I'm not
seeing anything obvious... anyone got any pointers to the right menu
item or whatever im suppose to use to do that now?

7)gnome-theme-manager is crashing on me again... damn! I had a bug
open on this and I thought it was no longer occuring i was sooooo
ready to go back and close it.
running  strace g-t-m  in a terminal makes the crashing stop...i'm
still grotesquely fascinated by that.

I think thats about it on initial findings.

-jef"<kingston trio>where have all my floppy drives gone.. long time
passing... when will they return... when will they return</kingston
trio>"spaleta

[Tim Waugh]

On Fri, Aug 27, 2004 at 01:55:29AM -0400, Jeff Spaleta wrote:

>  4)opening the Computer icon on my desktop is making nautilus peg a
> cpu
>  at 99% until i forcible kill nautilus.  Haven't seen this before.
>  Anyone else seeing this? 
This sounds like a gamin bug that was fixed in 0.0.8-1.

>  6)looking for a way as a user to set a default printer.... I'm
> not
>  seeing anything obvious... anyone got any pointers to the right menu
>  item or whatever im suppose to use to do that now? 
The 'lpoptions' command can do it; really we need the user print
dialog to have a method of doing that.

Tim.
*/

[seth vidal]

On Fri, 2004-08-27 at 09:36 +0100, Tim Waugh wrote:
>  On Fri, Aug 27, 2004 at 01:55:29AM -0400, Jeff Spaleta wrote:
>  
>  > 4)opening the Computer icon on my desktop is making nautilus peg a cpu
>  > at 99% until i forcible kill nautilus.  Haven't seen this before.
>  > Anyone else seeing this?
>  
>  This sounds like a gamin bug that was fixed in 0.0.8-1.
>  
>  > 6)looking for a way as a user to set a default printer.... I'm not
>  > seeing anything obvious... anyone got any pointers to the right menu
>  > item or whatever im suppose to use to do that now?
>  
>  The 'lpoptions' command can do it; really we need the user print
>  dialog to have a method of doing that. 
qtcups can set the default. :)

-sv

[Tim Waugh]

On Fri, Aug 27, 2004 at 09:06:32AM -0400, seth vidal wrote:

>  qtcups can set the default. :) 
That's no longer shipped.

Um, should we still be shipping printman?

Tim.
*/

[Konstantin Ryabitsev]

On Fri, 2004-08-27 at 14:32 +0100, Tim Waugh wrote:
>  On Fri, Aug 27, 2004 at 09:06:32AM -0400, seth vidal wrote:
>  
>  > qtcups can set the default. :)
>  
>  That's no longer shipped. 
And it's actually quite a bummer -- there is no decent print dialog tool
like qtcups in FC2 that could be used with Gnome. There is kprinter,
which is *excellent* but it takes forever to start up each time if you
aren't already running the KDE-environment apps.

Gnome is in dire need of something simple and functional like qtcups
that wouldn't rely on KDE.

Regards,
-- 
Konstantin ("Icon") Riabitsev
Duke University Physics Sysadmin

[Michael Knepher]

On Fri, 2004-08-27 at 09:36 -0400, Konstantin Ryabitsev wrote:
>  On Fri, 2004-08-27 at 14:32 +0100, Tim Waugh wrote:
>  > On Fri, Aug 27, 2004 at 09:06:32AM -0400, seth vidal wrote: 
>  Gnome is in dire need of something simple and functional like qtcups
>  that wouldn't rely on KDE. 
Like this: http://www.bluethingy.com/linux/Print_Dialog.png ?

[Brent Fox]

On Fri, 2004-08-27 at 01:55, Jeff Spaleta wrote:
>  On Thu, 26 Aug 2004 15:06:27 -0400 (EDT), Elliot Lee
> <sopwith(a)redhat.com&gt; wrote:
>  > Fedora Core 3 test 2 is devel-freezing on Wednesday, September 1. If there
>  > are bugs that need fixing by then, please make sure that they get
>  > needed love & attention. Install testing of the devel tree is especially
>  > valuable.
>  
>  You asked for it....... i just did a fresh install of the development tree:
>  Workstation install... no custom packages
>  /home and /usr/local  partitions unformated
>  /  /boot /var /usr  all formatted clean
>  
>  1)firstboot in graphical mode traced back on my in the Activation module.
>  I'm going to have to go back and run firstboot again and take a
>  digital image so i can transcribe the traceback text before I can file
>  this. 
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130567

For what it's worth, firstboot should dump a debug output into /root if
it has a crash.  No need to photograph the traceback on the screen.  :)


Cheers,
   Brent

>  1a)firstboot in text mode mostly worked... the soundcard detection
>  didnt, and the tui interface for the printer setup left some ascii art
>  artifects when switching "screens"... things like text dialog buttons
>  lingering into the next text screen when choosing the printer location
>  and driver.  test page printing worked in text mode firstboot
>  
>  2)no cdrom or floppy mount points were created.
>  /dev/fd0 device is created.. but fstab doesnt have an entry for it.
>  /dev/hdb is my cdrom drive and it mounts correctly using mount on the
>  commandline
>  but no /dev/cdrom link is created and no fstab entry.
>  
>  I'm really starting to think my idea for a command called
>  "give-me-my-floppy-back-now-damn-it" would be a good idea
>  
>  3)plugging in usb devices and i dont get an fstab entry on hotplug.
>  udev is creating the sdX and sgY devices. I've commented on this
>  before and the problem is still there. I have to forcible restart
>  haldaemon to see updated fstab entries for usbdrives.. I was hoping
>  what i was seeing before was an artifact of something i did on my
>  fc3t1 based install. But I'm still seeing this with a fresh install
>  directly from the development tree.
>  
>  4)opening the Computer icon on my desktop is making nautilus peg a cpu
>  at 99% until i forcible kill nautilus.  Haven't seen this before.
>  Anyone else seeing this?
>  
>  5)usb scanner still seems to work, shockingly.
>  
>  6)looking for a way as a user to set a default printer.... I'm not
>  seeing anything obvious... anyone got any pointers to the right menu
>  item or whatever im suppose to use to do that now?
>  
>  7)gnome-theme-manager is crashing on me again... damn! I had a bug
>  open on this and I thought it was no longer occuring i was sooooo
>  ready to go back and close it.
>  running  strace g-t-m  in a terminal makes the crashing stop...i'm
>  still grotesquely fascinated by that.
>  
>  I think thats about it on initial findings.
>  
>  -jef"<kingston trio>where have all my floppy drives gone.. long time
>  passing... when will they return... when will they return</kingston
>  trio>"spaleta
>