In kde of FC2 (as well as Red Hat 7.1) when you click
the logout menu in the kmenu it will lead to two
options- logout and cancel. I wish instead that you
have the options- restart, logout and shut down just
like what you see in gnome. does fc3 have this in its
kde? in other kde-centric distribution this has been
the case for a lot that I have seen- Mandrake and
Bayanihan Linux for instance. Without this, the way to
restart or shutdown your computer is by typing in the
command line which is a little burdensome for a desktop.
Do you Yahoo!?
Jazz up your holiday email with celebrity designs. Learn more.
After reading to much forums, i can se "everyone" is complaing about
"the default font in (put your favorite web browser here) is so ugly, it
is hardly readable!"
Then the reply is "use Bitstream vera (sans) instead" and then "oh! that
was better! it was really readable! nice!"
Why is it so? Why is those fonts, which it seem like "everyone" thinks
are really ugly are used, when better fonts are shipped?
I would guess there are more people than me who has opinions on this.
Disclaimer: i am forwarding a "general feeling" from parts of the
comunity, as not everyone are on this list. But after changing my
default fonts in firefox, i must say i agree. This was *much* better!
Kyrre Ness Sjøbæk
I have an old computer that wont boot off of the cd rom. It will boot
off of the floppy drive and the hard drive. I want to install fedora 3
but it doesn't have a boot diskette. am I right? what can I do?
After two weeks I have solved my problem with udev and DVB. I feel that
the following information should be on the release notes page for FC3:
To use DVB with Fedora Core 3 and udev you _MUST_ use the modules in
The DVB modules supplied with stock FC3 kernels do not work with udev.
The DVB people were not having my problem because they were using hand
rolled kernels and latest modules from CVS. The end user of a FC3
desktop machine may have a DVB card but this does not mean that she is
familiar with checking modules out of CVS to make it work...
Now if anybody has lirc working I am all ears =:-D
Has anyone had any experience with the generic 2.6.9 kernel?
Netraverse no longer provides pre-compiled kernel after FC2. The only
way to run Win4Lin is to get a generic kernel, then apply Netraverse patch.
Thanks a lot to all of you who helped me to get FC 2 on my PC. Now my PC is
working fine except with two problems which I mention below:
1. How to get my motherboard drivers installed on to my PC?
2. I have a PCI modem on my PC. I could not get a driver on web for it (SM56
from Motorola). I wanted to write my own driver for it but problem is that
both KDevelop and gcc do not pick up the header files in /usr/include/pci
directory. both of them are picking up files in only /usr/include/linux. How
do I get them to include the directories above the linux directory
(/usr/include/linux)? If I put the full path of pci.h (.i.e
/usr/include/pci/pci.h) it cannot find files included within pci.h.
3. Another thing is that the pci.h within /usr/include/linux does not
contain anything that is required for building PCI drivers for desktops. why
has everything been moved from this file to /usr/include/pci/pci.h. If the
intended move is correct why do KDevelop and gcc do not lookup the correct
4. printk does not support KERN_ALERT. It is simply not defined?
Thanks in advance for any help!
When I used redhat 8.0 I used to double click a .rpm (while in konqueror)
file and it used to get installed thru gui,
But in FC3, I am not able to do the same, Can anybody help,
Thanks & Regards,
I wanted to do this for a long time but only now I had the time and
a destop beefy enough to try this. Basically I replaced /usr/bin/gnome-session
by a shell script :
/usr/bin/valgrind --trace-children=yes --log-file=/tmp/valgrind /usr/bin/gnome-session.orig $*
Then logged on in gdm , and checked what happened from an ssh connection
top the box.
The good news:
- logging went through, but it took a few minutes
- everything looked functional though extremely slow
- there wasn't many logs reported by valgrind
The bad news:
- I had to stop the session shortly after the login fully complete
the VM was full (1G of Ram + 500M of swap)
- reports from the logs are a pain to try to analyze.
- one python (rhn applet I suspect) generated a huge log, python-2.3
doesn't seems valgrindable.
I them eliminated all the empty /tmp/valgrind.pid* files, I was left with
reports from oly 25 processes.
First a word of warning, I used the normal optimized code as shipped as
part of Fedora devel (fully up-to-date box for todays version), some
of the optimizations sometimes defeat valgrind so there may be false positive.
I have tried to sort all the reports to gather together what was frequently
reported because all apps went through the same code path, for example
there is an error reported when opening gdk display which is reported like
30 times by various apps. So what I saw most:
- gdk_display_open leading to write(buf) contains uninitialised or
unaddressable byte in __write_nocancel though _X11TransWrite
hard to tell without a debugging lib if the error is a false positive
a lack of initialization gdk_display_open() or within X. Strange thing
is that valgrind report the block as being alloc'ed with calloc()
offending address is 128 bytes inside a block of size 16384
- giop_send_buffer_write in libORBit-2 leading to
Syscall param writev(vector[...]) contains uninitialised or unaddressable byte(s)
that time the uninitialized data is 10 bytes inside a block of size 2048
allocated within orbit itself.
- pango read_line raises a strange pthread mutex error:
pthread_mutex_lock/trylock: mutex has invalid owner
in pthread_mutex_lock called by pango_read_line from pango_find_map
Apparently the GStreamer code detects it's running under valgrind and
manage to shut it up :-)
Except those 3 repeated all other the place and consisting of the bulk of
the reports, I have seen errors in:
- /usr/bin/gnome-session: invalid file descriptors,
pango_attr_list_get_iterator uninitialized value.
- /usr/bin/pam-panel-icon: 2 invalid file descriptor, seems the same
as for gnome-session with value 828 too.
- /usr/lib/libwnck: uninitialized values in _wnck_read_icons
- /usr/libexec/gconfd-2: repeated g_strdup of initialized values
from gconf_set_daemon_ior, gconf_get_lock, gconf_object_to_string,
gconf_quote_string, and an fprintf
- /usr/libexec/bonobo-activation-server: uninitialized values in
- gam_server : I got one too :-)
- metacity: uninitialized values in gdk_window_new, gdk_window_resize,
gdk_region_rectangle, gdk_region_subtract, a couple of strange
g_int_equal bugs, meta_display_begin_grab_op, meta_display_end_grab_op
- gnome-terminal: terminal_profile_update and _vte_pty_open
The best way to double check is to do the same trick as I did for
gnome-session, move the original somewhere else, replace it by a script
calling valgrind but without recursion to child on a local copy of the
program in debugging mode.
Enclosed are the data as sorted and recouped for more informations.
Daniel Veillard | Red Hat Desktop team http://redhat.com/
veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
I am having some printing issues with FC3 that I have not seen before.
I have a CUPS server with 6 printers. When I initially built my machine
I used printer "A." Recently I attempted to set printer "B" to my
default. Some applications(namely firefox and xpdf) simply do not
recognize the change even though the printer config util shows that
printer "B" is my default. The applications continue to print to "A"
Anyone seen this?