Mouse Wheel gone
by Christian Menzel
Since the latest xorg-X11 upgrade I receive the already mentioned XKB
error and the mouse wheel is not working anymore.
Has anybody seen this behavior?
Regards
Chris
3 years, 3 months
Re: NFS failure
by Fulko.Hew＠sita.aero
Damian Menscher <menscher(a)uiuc.edu>@redhat.com on 04/07/2004 04:57:13 PM
wrote:
> On Wed, 7 Apr 2004, Jeff Elkins wrote:
>
> > I'm getting failure messages on my nfs mounts i.e. :
> >
> > mount to NFS server 'music.elkins' failed: server is down.
> >
> > nsfd appears to be running and I didn't see anything suspicious in the
logs.
> > The servers are up and running and have other clients connected.
>
> You didn't mention what steps you took to debug it:
>
> Can you ping the server?
> What is the output of rpcinfo -p servername?
> Does the server have access restrictions (firewall, TCP Wrappers, etc)?
I have the same symptoms...
rpcinfo says that nfs et.al. are running.
Something has changed in test 2, since the same PC running RH9
accesses that host just fine.
3 years, 3 months
Some things to focus testing on for F9Beta
by Will Woods
Fedora 9 will have a lot of new and exciting things. Naturally, we want
those things to be stable and well-polished for the final release.
With that in mind, here's a list of things that deserve especially close
attention.
1) PackageKit
This *replaces* pup and pirut, by default, on all new installs. If
you're following rawhide, *please* disable or remove pup and pirut and
test this. It's very important that you file bugs about *any* problems
with PackageKit.
Use the "gnome-packagekit" component in bugzilla for bugs about
confusing (or missing) UI pieces, and "PackageKit" for bugs about
backend errors, missing capabilities, or other (non-UI) problems.
2) NetworkManager
At long last, NetworkManager is installed and enabled by default for all
new installs. It is *supposed* to play nice with the system
configuration set up by Anaconda and the old system-config-network tool.
I'd recommend that all testers install and enable NetworkManager if
possible. File bugs about network configuration problems (not honoring
static IP configurations, for instance) against "NetworkManager".
3) Upstart
Upstart has replaced sysvinit. Everything should be working as it did in
F8, but if you have problems with serial consoles, boot-time arguments,
changing runlevels (using telinit or similar), or the like, make sure
bugs get filed.
The runlevels are now controlled by the Upstart event scripts
in /etc/event.d. If you have problems changing runlevels file bugs
against "event-compat-sysv". Other upstart bugs should probably be filed
under "upstart".
4) evdev
Xorg is now using the new "evdev" generic input driver. This driver is
intended to automatically handle all input devices recognized by the
kernel - keyboards, mice, joysticks, whatever.
Unfortunately its handling of keyboards is still a bit messy and
probably won't be ready for F9. Therefore, ajax modified it to let the
old, working driver claim your keyboard.
So as of F9Beta, keyboards *should* work just like they did in F8. If
you have *new* problems with your keyboard layout (and you're not having
lingering evdev problems from older rawhide[1]), check Xorg.0.log to see
if evdev has claimed your keyboard. If so, file a bug against
"xorg-x11-drv-evdev". Otherwise, use "xorg-x11-drv-keyboard".
If there's any other things that people think need closer attention..
now would be a good time to mention them.
Happy testing!
-w
[1]
https://redhat.com/archives/fedora-test-list/2008-March/msg00710.html
10 years, 8 months
"too many timeout resolving $DOMAIN, disabling EDNS"?
by David Hagood
Over the past couple of weeks I've been getting lots of messages like
this in my logs:
unexpected RCODE (SERVFAIL) resolving 'example.com/A/IN': 64.71.97.21#53
Aug 5 17:54:49 Deathwish named[1870]: too many timeouts resolving
'www.example.com/A' (in 'example.com'?): disabling EDNS
(where I have replaced the actual domain with "example.com")
This happens on MANY domains, not just a few, and on domains that I
would think would NOT be likely to have stupid problems (like Google and
Slashdot).
Has something changed in BIND that could cause this?
10 years, 10 months
nemiver i386 not listed in repo
by Andrew Farris
Has anyone else seen a problem with nemiver i386 package not being available?
There is an update in x86_64, and the matching version is actually present on
the mirror for i386, but its not being shown as available through yum. This was
causing updates to fail even with skip-broken, so I had to --exclude it.
Both packages are there:
http://limestone.uoregon.edu/ftp/fedora/development/x86_64/os/Packages/ne...
http://limestone.uoregon.edu/ftp/fedora/development/i386/os/Packages/nemi...
But only x86_64 tries to update.
10:05:03 |lordmorgul.durthangnix:0| |17 files:11M@~| |0 jobs|
- yum list nemiver.x86_64 nemiver.i386
Loaded plugins: basearchonly, fastestmirror, fedorakmod, priorities, security,
: versionlock
Loading mirror speeds from cached hostfile
* livna-development: mirrors.tummy.com
* livna-development-debuginfo: mirrors.tummy.com
* rawhide: limestone.uoregon.edu
* upstart-debuginfo: notting.fedorapeople.org
* upstart: notting.fedorapeople.org
Reading version lock configuration
Installed Packages
nemiver.x86_64 0.4.0-3.fc9 installed
nemiver.i386 0.4.0-3.fc9 installed
Available Packages
nemiver.x86_64 0.5.1-1.fc9 rawhide
10:05:22 |lordmorgul.durthangnix:0| |17 files:11M@~| |0 jobs|
- yum list updates
Loaded plugins: basearchonly, fastestmirror, fedorakmod, priorities, security,
: versionlock
Loading mirror speeds from cached hostfile
* livna-development: mirrors.tummy.com
* livna-development-debuginfo: mirrors.tummy.com
* rawhide: limestone.uoregon.edu
* upstart-debuginfo: notting.fedorapeople.org
* upstart: notting.fedorapeople.org
Skipping security plugin, no data
Reading version lock configuration
Updated Packages
evince.x86_64 2.22.0-3.fc9 rawhide
inkscape.x86_64 0.46-0.3.pre3.fc9 rawhide
kpathsea.x86_64 2007-28.fc9 rawhide
nemiver.x86_64 0.5.1-1.fc9 rawhide
poppler.x86_64 0.7.3-1.fc9 rawhide
poppler-glib.x86_64 0.7.3-1.fc9 rawhide
poppler-qt.x86_64 0.7.3-1.fc9 rawhide
poppler-qt4.x86_64 0.7.3-1.fc9 rawhide
texlive.x86_64 2007-28.fc9 rawhide
texlive-dvips.x86_64 2007-28.fc9 rawhide
texlive-latex.x86_64 2007-28.fc9 rawhide
texlive-utils.x86_64 2007-28.fc9 rawhide
10:07:39 |lordmorgul.durthangnix:0| |17 files:11M@~| |0 jobs|
- rpm -q nemiver.x86_64 nemiver.i386
nemiver-0.4.0-3.fc9.x86_64
nemiver-0.4.0-3.fc9.i386
--
Andrew Farris <lordmorgul(a)gmail.com> www.lordmorgul.net
gpg 0xC99B1DF3 fingerprint CDEC 6FAD BA27 40DF 707E A2E0 F0F6 E622 C99B 1DF3
No one now has, and no one will ever again get, the big picture. - Daniel Geer
---- ----
10 years, 10 months
Fedora 9 beta no fonts on intel x3100 laptop
by Klaasjan Brand
Hi,
I've downloaded the Fedora 9 beta and created a bootable usb stick to test
it out on some systems.
It works fine on my desktop with radeon graphics so I assume the usb stick
is ok.
However, on a laptop with Intel x3100 graphics, X doesn't display fonts and
icons (it draws rough outlines of where the windows are supposed to be and I
can log in by clicking the right places). This is the same in rhgb, gdm and
on the desktop. Fedora 8 works fine on this laptop.
Is anyone able to confirm if this is an issue with all x3100 systems?
Klaasjan
10 years, 10 months
Successful test of encrypted usb drive
by Bruno Wolff III
While I think this feature has been available for a while, it might be worth
mentioning with the encrypted install feature.
I tried it out as follows (as root):
Plug in the usb drive and not the device name (/dev/sdc1 in my case)
Erase it with random data (which can take a while and isn't really needed
if no senstive data was previously on the device and you don't care about
leaking which blocks on the drive have been written)
dd if=/dev/urandom of=/dev/sdc1
Create the encrypted area
cryptsetup luksFormat /dev/sdc1
Enter the passphrase twice
Make the encrypted area a usable device
The name at the end is arbitrary, but don't use one already in use
cryptsetup luksOpen /dev/sdc1 luks-usb
Create the file system using the name from above as the device
mkfs -t ext3 /dev/mapper/luks-usb
Close the encrypted device
cryptsetup luksClose /dev/mapper/luks-usb
Unplug the device
Now when you plug in the device (while logged in at the console using a GUI)
you will get asked for the passphrase and after prodiving the correct one
the device will work like a normal removable device.
Note that doing this limits you to using it with systems that support luks
and ext3, which isn't going to work for everyone.
10 years, 10 months
hwbrowser not showing DASD
by Clyde E. Kunkel
Hi, I just noticed that my drives are no longer showing up in hwbrowser
when I select hard drives.
Anyone else seeing this? I didn't see a bz and will enter one if others
seeing the same thing. This is on current rawhide x86 system, SATA and
IDE drives, no selinux.
--
__________________________
Regards,
Old Fart
10 years, 10 months
