I'm running a dual boot Windows/Fedora system on my Thinkpad T43.
Whenever I run Windows, I find my time is 1 hour out
when I return to Linux.
Is this my punishment for consorting with the devil,
or is there a simple solution?
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
I see fedoraproject.org has a AAAA record now (how new is that?) but the
IP is not responding today. Access to fedoraproject was working up until
today so I'm not sure if the AAAA record is brand new today or if it's
$ ping6 fedoraproject.org
PING fedoraproject.org(2610:28:200:1::fed0:1) 56 data bytes
--- fedoraproject.org ping statistics ---
11 packets transmitted, 0 received, 100% packet loss, time 10721ms
I cannot use yum in this situation. I can access http://ipv6.google.com
I did not use gdm for some time and now I'm not happy how it looks in Fedora
First of all - the list of local users is unacceptable from security
reasons. Even if it supports such "an " option - how it can be the default
Second problem I have is shutdown button (and possibly restart as well) -
when you click on shutdown button by mistake, system will shut - there is no
I also tried to find some ways how to customize gdm in Fedora 11 but I did
not find any usable guide.
Can anybody please advise me how can I have prompt asking for username only
(showing last logged user at maximum) and not displaying the list of all
Also can I somehow add confirmation or remove shutdown restart buttons from
Or can you please advise any alternative to gdm?
Thank you very much,
Suddenly, most of the icons in thunderbird and *some* images in ff are
pretty messed up. They appear to be indexed to just 3 colours.
Sometimes, it's predominantly neon green, other times purple or black.
In TB, it's the ones that are highlighted, except for folders, which
look fine. Any icon that's greyed out also appears normal. Also, the
icons in the "write" window i'm typing now in are ok.
In FF, there doesn't appear to be any rhyme or reason, save for the fact
they're all PNGs. I thought that it was background images only, but that
doesn't appear to be the case. Nor are all PNGs screwed up.
I recently installed an LCD display and so modified my xorg.conf. But
this problem only just appeared so i doubt it's related. Is anyone else
seeing something similar (it's *really* hard to miss).
Otherwise, can anyone think of what I can check?
Here's the latest from yum.log:
Aug 19 16:40:07 Updated: gvfs-1.2.3-11.fc11.i586
Aug 19 16:40:07 Updated: pciutils-libs-3.1.3-1.fc11.i586
Aug 19 16:40:08 Updated: nss-softokn-freebl-18.104.22.168.3-2.11.4.fc11.i586
Aug 19 16:40:09 Updated: nss-22.214.171.124.3-2.11.4.fc11.i586
Aug 19 16:40:09 Updated: pciutils-3.1.3-1.fc11.i586
Aug 19 16:40:10 Updated: libmtp-0.3.7-2.fc11.i586
Aug 19 16:40:12 Updated: nss-tools-126.96.36.199.3-2.11.4.fc11.i586
Aug 19 16:40:12 Updated: gvfs-smb-1.2.3-11.fc11.i586
Aug 19 16:40:12 Updated: gvfs-obexftp-1.2.3-11.fc11.i586
Aug 19 16:40:13 Updated: gvfs-archive-1.2.3-11.fc11.i586
Aug 19 16:40:13 Updated: gvfs-gphoto2-1.2.3-11.fc11.i586
Aug 19 16:40:13 Updated: gvfs-fuse-1.2.3-11.fc11.i586
Aug 19 16:40:17 Updated: gdb-188.8.131.5290302-37.fc11.i586
Aug 19 16:40:53 Updated: gnome-settings-daemon-2.26.1-8.fc11.i586
Aug 19 16:41:06 Updated: 7:squid-3.0.STABLE18-1.fc11.i586
Aug 19 16:41:06 Updated: m17n-db-1.5.5-1.fc11.noarch
Aug 19 16:41:07 Updated: kernel-firmware-184.108.40.206-217.2.8.fc11.noarch
Aug 19 16:41:08 Updated: pciutils-devel-3.1.3-1.fc11.i586
Aug 19 16:41:10 Updated: nss-devel-220.127.116.11.3-2.11.4.fc11.i586
Aug 19 16:41:15 Updated: setroubleshoot-plugins-2.0.18-5.fc11.noarch
Aug 19 16:41:19 Updated: kernel-headers-18.104.22.168-217.2.8.fc11.i586
Aug 19 16:41:47 Installed: kernel-22.214.171.124-217.2.8.fc11.i586
Aug 19 16:41:47 Updated: systemtap-runtime-0.9.9-3.fc11.i586
Aug 19 16:41:52 Updated: systemtap-0.9.9-3.fc11.i586
Aug 19 16:41:53 Updated: m17n-lib-1.5.5-1.fc11.i586
For the past couple of weeks, my desktop machine has been shutting down
on its own. I thought it might be a hardware problem until I noticed
that, each time, /var/log/pm-suspend.log was being written to:
Initial commandline parameters:
Mon Aug 31 12:53:31 EDT 2009: Running hooks for suspend.
/usr/lib/pm-utils/sleep.d/00auto-quirk suspend suspend: Adding quirks
from HAL: --quirk-dpms-on --quirk-dpms-suspend --quirk-vbe-post
--quirk-vbemode-restore --quirk-vbestate-restore --quirk-vga-mode-3
So, what the heck is driving this? Can anyone tell me what is calling
/usr/lib/pm-utils/sleep.d/*? This box is quickly becoming unusable.
Just a quick note to call people's attention to
http://marc-abramowitz.com/archives/2007/02/17/getting-good-performance-o.... This is a couple of years old but it worked like a charm for me.
Briefly, there's a kernel parameter
called /sys/block/sd[a,b,...]/device/max_sectors (for USB drives sda,
sdb etc.). This specifies the maximum size of a disk I/O operation for
USB storage devices in units of 512 bytes, the default value being 240,
i.e. 120KB (see http://www.linux-usb.org/FAQ.html#i5). The max_sectors
value can be changed doing "echo N > ..." as root, and can have a
dramatic effect on write performance for USB devices such as pendrives.
I tested this by writing over 2GB to a fresh VFAT filesystem on a 4GB
Kingston Data Traveller pendrive plugged into a USB2 port with the EHCI
driver (as indicated by dmesg). With the default setting, this took
nearly 90 minutes including a final sync to flush the buffers. Using a
max_sectors value of 1024 -- the highest the system would accept -- the
time was reduced to under 16 minutes, a better than 5 times speedup.
YMMV of course, as different brands of pendrive can have very different
Note that the value resets to the default when you unplug the drive, so
you need to set it manually each time. I don't know if there's a way to
do this automatically, or change the default value permanently.
Sorry of everyone already knew this, but I found it so useful I just had
to share it :-)
The last time I had a system lock-out was several
weeks ago, and just today, I experienced another.
I tried to access the system locally via the keyboard,
no response. Mouse, same. Remotely, not responding,
all remote connections, ports, etc. Not there.
Darn! hard reboot.
So, I looked at the system messages logs:
Aug 29 01:08:11 gold pulseaudio: alsa-sink.c: Increasing wakeup
watermark to 125.99 ms
Aug 29 10:14:32 gold kernel: imklog 3.22.1, log source = /proc/kmsg started.
Yep, there is a 9 hour gap of no activity. It looks
like the system went to sleep just like I did when
it was time for bed. I got up this morning, but my
system never woke up. Lazy basta... oh, sorry.
Well, what else can I do, there seems to be no way
to figure out what is going on, if there is no record
Configuring the kernel I came across a choice between generic-x86_64
processors, and the Opteron/Athlon/Hammer/K8 processors. My system has
a 4-core Phenom processor. Questions:
1. Is the Phenom compatible with the Opteron/etc? I.e. if I
configure for the Opteron, will my kernel be reliable? (This is
not as easy to find out as I thought.)
2. How much of a performance advantage is there to configuring for
the Opteron as against the generic?
Thanks - jon
I'm running Fedora 11 with the gnome desktop on a small LAN. I'd like to
run an audio player (say xmms) on box2 and hear it on box1, which is
directly connected to my stereo.
In the past I would connect to box1 from box2 via ssh and then run xmms
from the command line. Now when I try doing this I get this message:
Couldn't open audio. Please check that
Your soundcard is configured properly
You have the correct output plugin selected
No other program is blocking the soundcard.
I can play audio with problems from box1, so the soundcard must be OK.
I have pulseaudio selected as the output plugin in xmms. (The same
problem occurs with alsa and the other plugins.)
It seems likely, then, that the problem is some other program is running
on box1 that is blocking use of the soundcard.
Two related questions:
(1) Does anyone know what other program this might be (gnome?) and how I
might get around the block?
(2) Isn't this the sort of simple application pulseaudio was designed
for? Shouldn't I be able to run xmms on box2 and use pulseaudio to play
the output on box1? Has anyone been able to do anything like this with
pulseaudio and, if so, what settings did you use and where did you set
Thanks for the help!
One one machine, I keep getting half a dozen popups that all
Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation
X server version data:
The X.Org Foundation
If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
It doesn't say *where* to send a bug report. So I ran those
commands, and got :
[btth@Hbsk ~]$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "evdev", "evdev", "us", "",
_XKB_RULES_NAMES(STRING) = "evdev", "pc105+inet", "us", "",
[btth@Hbsk ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = 
options = 
[btth@Hbsk ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = 
options = 
None of that means anything to me.
I tried yum remove xkb, meaning to follow it with yum install
xkb, but yum didn't find it.
I tried googling, and I tried yum whatprovides. That got me to /
usr/share/X11/xkb -- but everything in the readmes is Geek to me.
When I was working, all of us in my section had lots of what we
then called macros such as type Ctrl-b, and the machine would put
"Includes bibliographical references" into the proper field. What little
I can follow seems to say that such tricks are what XKB does; but I don't
use them now, and haven't since I retired.
Should I just remove XKB? If so, how? If not that, what?
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.