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
5 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.
5 years, 3 months
Dependencies for MonoDevelop
by Benjamín Valero Espinosa
Today I have installed MonoDevelop in FC10 (recently installed and
updated) and cannot see or navigate any source file when I try to open
it. For the second problem I have installed "ctags". For the first, I
have tried to install "gtksourceview2-sharp". I think both should be
dependencies of the "monodevelop" package.
When I try:
# pkcon install gtksourceview2-sharp
I get that:
Error: package-already-installed : The packages failed to be installed
But if I search that package, I get that:
available gtksourceview2-sharp-1.0-2.svn89788.2.fc10 A C sharp
binder for gtksourceview2
available gtksourceview2-sharp-devel-1.0-2.svn89788.2.fc10 Development
files for gtksourceview-sharp
so is not really installed. What can it be? Thanks for your work.
12 years
F10 and nVidia ==> Big Problems
by Christopher A Williams
This was also a problem on F9, but it is now worse on F10 beta. Video
simply fails to load on my system using the F10 live CD. This happens on
both 32-bit and 64-bit versions. I've reproduced this on other similar
computers as well.
Video attempts to load at bootup but eventually fails and drops to a
text mode login prompt. My system is a self-built machine. Here's the
specific video oriented info:
EVGA e-7100/630i Motherboard
- Onboard nVidia GeForce 7100 GPU
- nVidia nForce 630i chip set
I have 4GB RAM and a Intel Quad-Core processor.
When I loaded F9, I worked around the problem by:
1) Waiting for the live system to fail back to text mode
2) Logging in as root at the text prompt
3) Run system-config-display and accepting the detected defaults
4) Run startx to start the gui
5) Run the installer as normal
Post-install, the OpenSource nv driver would load and provide a
reasonable display resolution until I could install the Livna nVidia
drivers.
On F10, system-config-display is no longer there! So instead I have to:
1) Wait for the live system to fail back to text mode
2) Log in as root at the text prompt
3) Install system-config-display (yum -y install system-config-display)
4) Run system-config-display and accept the detected defaults (nothing
else works)
5) Run startx to start the gui
6) Run the installer as normal
However, on F10, startx only provides 800x600 resolution, despite that
my display is capable of 1920x1200.
Can we get this fixed in F10 please? I'm happy to Bugzilla this if it
isn't there already.
Cheers,
Chris
--
=========================================
"In theory there is no difference between theory and practice.
In practice there is."
--Yogi Berra
12 years, 1 month
java redisplay problem on intel driver
by Per Bothner
Could people try the attached Java test program?
There is a bad redisplay problem for large (greater than around 1000
lines) text windows using a TextArea (or a Swing JTextPane).
I have the feeling it is specific to the Intel driver.
To test it, you need to have openjdk "java" installed and
in your path:
$ java -version
java version "1.6.0_0"
IcedTea6 1.4 (fedora-7.b12.fc10-i386) Runtime Environment (build
1.6.0_0-b12)
OpenJDK Server VM (build 10.0-b19, mixed mode)
Java is provided by java-1.6.0-openjdk-1.6.0.0-7.b12.fc10.i386.
However, the same problem occurs with jdk1.6.0 update 11
downloaded directly from Sun, as well as jdk 1.5.0_05.
To test it, put TextTest.java in a temporary directory,
cd to that directory, compile it, and run it:
$ javac TextTest.java
$ java TextTest
Now try scrolling back and forth a bit. What happens for me is that
the text lines will be over-written multiple times on top of each other.
The interesting thing is that only the first 700 lines
or so are garbled - the remaining lines are fine.
My guess is that there is some weird interaction between Java,
the Gtk peers, and the intel driver, since otherwise more people
would have reported this problem. Also, I have tried it on an
NVidia-based laptop, and well as with the vesa driver (iirc).
It would be helpful to get some data-points before I decide
whether to complain to Sun or to Intel or to Gnome!
--
--Per Bothner
per(a)bothner.com http://per.bothner.com/
12 years, 1 month
selinux adventures/troubles
by Michal Jaegermann
I wonder if this is my unique experience or this is widely observed.
So far, AFAICT, when installing a machine "from scratch", and while
keeping a layout as plain as possible, then selinux is rather
expected to work; at least decently enough. The picture becomes
entirely diferent when you are trying to upgrade a distro. What
results of such exercise will be I am unable to predict.
I have now such example recently moved from F8 to F10. It was
configured "targeted" and in the past it was behaving ok. Burned on
other occasions I set selinux to "permissive" before upgrading
distros with an intentions to restore "enforcing" later on. In
anaconda it is hard not to notice that an installation of
selinux-policy-targeted package takes a really long time. One would
think that this is because some checks are run or some relabeling
takes place or whatever. Only the end result was that after a
reboot a machine was mostly busy spitting all kind of complaints and
warnings. If not that "permissive" setting it most likely would
not boot at all. 'touch /.autorelabel' followed by a reboot and
relabelling took care of most of that stuff. But without the
machine really going into a service at least two "mysteries" remain
(and I fully expect more to show up later).
There is a requirement that a root needs to be able to login via
ssh on this machine using an authorized key (a remote root login
with a password is blocked). This works but I am getting every
time "Unable to get valid context for root" and in /var/log/secure:
"pam_selinux(sshd:session): Security context
system_u:system_r:logrotate_t:s0-s0:c0.c1023 is not allowed for
system_u:system_r:logrotate_t:s0-s0:c0.c1023".
Eh? What this is supposed to mean? There are no corresponding
'sealert' message I can find nor 'allow2why' comes with any reasons.
Another problem which hits immediately is that 'root' has
.procmailrc file and it is necessary there. Every mail to root
results in selinux complaints. Initially these were in a form:
SELinux is preventing the procmail from using potentially mislabeled
files (./_ZoC.lwQVJB.xxxxxx.yyyy.zzz).
and propositions to relabel these. A very good advice. :-)
This time 'allow2rules' had the following things to propose:
allow procmail_t admin_home_t:dir { write remove_name add_name };
allow procmail_t admin_home_t:file { write create unlink link };
I generated a corresponding module, and added it to a fray, and
that only changed a nature of complaints to:
SELinux is preventing the procmail from using potentially mislabeled
files (./.procmailrc).
The catch is that /root/.procmailrc has for a label
system_u:object_r:admin_home_t:s0 and 'restorecon -v' on it does not
change anything at all.
Of course I have no idea if there are policy problems, or troubles
are somewhere else, or everything really works as expected. A big
mystery.
To makes things even more interesting I have another machine, also
upgraded from F8 to F10 and configured, it would appear, in a
similar way, and none of symptoms described above shows there.
Only on that other box /root/.procmailrc is labeled with
system_u:object_r:user_home_t (do not ask me why!) and
system_u:object_r:user_home_dir_t shows on /root and running
there 'restorecon -vR /root' also does not change anything at all.
So apparently both are correct only one does not work and how and
why they aquired different labels is another of those puzzles.
Does selinux policies are applied at random?
Michal
12 years, 1 month
Fedora 10 on an HP EVO D510
by John Summerfield
Some of the issues here probably won't be addressed in F10, so this is
probably a reasonable list for discussion.
Yesterday, I downloaded F10 and installed it on an HP/Compaq EVO D510.
The only non-standard feature on the system is a prism54-based network
card. It works with the prism54 driver first incorporated into the
kernel, but needs a firmware blob.
The system has a CD drive, not DVD, and since I wanted to install to the
system where it will live (needs wireless), I downloaded CD images and
installed using those burned to CD. I was downloading and installing at
the same time, downloading running a little faster (thank goodness I
finally escaped the modem).
Without giving much thought, I chose a text install. On reflection, I
think that a good choice.
About disk three there was an error reading the zsh rpm. There were
fewer options than I would like, but "eject" is an improvement on last
time I had this problem, about RHL 8.0 or a beta of it I think, where I
could only retry.
I would like also the options to
1. Skip. I understand it's not always prudent to skip a package, but not
all are equally essential and I'd probably do fairly well without zsh.
2. Install from another source.
In this case, ejecting and reloading the CD was effective.
Since I installed in text mode, F10 defaulted to runlevel 3. This
highlights the prudence of my choice in doing a text install (besides
which, text should be faster in 512 Mbytes RAM).
On first boot, I tried to configure the network - I had copied fhe
firmware into place before rebooting after the install), but the
text-mode network install doesn't understand wireless.
Note, I've not seen any documentation of how to do this for Fedora, I
had some experience with the first release of Ubuntu and this particular
wireless card, so I had some ideas of what to do. If there is some
documentation on the 'net, it would be especially hard to browse for it
as I didn't yet have a working network. For purposes of discussion,
we're ignoring the other umpteen computers here, okay?
Once I had the driver in the rignt place and a symlink with the right
name, the wireless came up easily enough.
I was quite surprised though to find it's eth0 in F10 (at least some of
the time), it used to be eth1 (and is, in the kubuntu 6.10 system I
booted off my LAN more recently). The EVO has an on-board NIC, so I
fully expected that to be eth0.
I was dismayed to find I had to apply over 600 Mbytes of updates Those,
it seemed to me, took longer than the original installation. However,
it's done.
I then switched to runlevel 5 and tried to login as root.
The screen displayed some junk, but I did get a login screen of sorts. I
tried to login, the login failed but there was no comprehensible
message, the fonts were badly distorted. After that, nothing
comprehensible displayed and I could not crash X or switch to a text
console.
The only way to regain control was the power button (no reset switch on
these systems). Remember, no network yet. I need graphics to configure
the wireless.
I don't like gdm anyway, never have, so "rpm --erase gdm" and then the
bits that require it.
After this, the login screen was less useful, so I tried runlevel 3 and
"startx" as root. That got a grey screen with an X cursor and nothing
else. I'm pretty sure I had to cycle power again here.
I thought to try tweaking xorg.conf if only to ensure
control-alt-backspace and control-alt-F1 etc work, but there is none:
(EE) Unable to locate/open config file
The full log is at http://fedora.js.id.au/var/log/Xorg.0.log and its
content suggests it's going to take more than five minutes to fix. These
don't look good to me:
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x812bc5b]
1: /usr/bin/X(mieqEnqueue+0x289) [0x810b379]
2: /usr/bin/X(xf86PostMotionEventP+0xc2) [0x80d4262]
3: /usr/bin/X(xf86PostMotionEvent+0x68) [0x80d43c8]
4: /usr/lib/xorg/modules/input//evdev_drv.so [0xa6fa8d]
5: /usr/bin/X [0x80bcdb7]
6: /usr/bin/X [0x80ac91e]
7: [0x130400]
8: [0x130416]
9: /lib/libc.so.6(ioctl+0x19) [0x4f3979]
10: /usr/lib/libdrm.so.2 [0x6f56cf]
11: /usr/lib/libdrm.so.2(drmCommandWrite+0x34) [0x6f5984]
12: /usr/lib/xorg/modules/drivers//intel_drv.so(I830Sync+0x135) [0x711ca5]
13: /usr/lib/xorg/modules/drivers//intel_drv.so [0x73b97a]
14: /usr/lib/xorg/modules//libexa.so(exaWaitSync+0x65) [0x7d4095]
15: /usr/lib/xorg/modules//libexa.so(ExaDoPrepareAccess+0x7e) [0x7d53ae]
16: /usr/lib/xorg/modules//libexa.so [0x7da3b2]
17: /usr/lib/xorg/modules//libexa.so [0x7da905]
18: /usr/lib/xorg/modules//libexa.so(exaDoMigration+0x652) [0x7db0c2]
19: /usr/lib/xorg/modules//libexa.so(exaCopyNtoN+0x3f1) [0x7d7fd1]
20: /usr/lib/xorg/modules//libexa.so(exaComposite+0x90e) [0x7dd4de]
21: /usr/bin/X [0x816f6fa]
22: /usr/bin/X(CompositePicture+0x19a) [0x815818a]
23: /usr/lib/xorg/modules//libexa.so [0x7d8c1d]
24: /usr/lib/xorg/modules//libexa.so(exaGlyphs+0x4e2) [0x7d9672]
25: /usr/bin/X [0x816f9c5]
26: /usr/bin/X(CompositeGlyphs+0xa2) [0x8154612]
27: /usr/bin/X [0x816197e]
28: /usr/bin/X [0x815ad75]
29: /usr/bin/X(Dispatch+0x34f) [0x8085e9f]
30: /usr/bin/X(main+0x47d) [0x806b71d]
31: /lib/libc.so.6(__libc_start_main+0xe5) [0x42e6e5]
[mi] mieqEnequeue: out-of-order valuator event; dropping.
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
Here is a similar report:
http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg37058.html
In view of this, I tried booting with 'vga=6' but the result is a login
screen with a garbage background but visible entry boxes and
intelligible text. However, mouseclicks and the keyboard are ignored.
With the earlier kernel, I got no garbage (but that might have been
luck), but the other symptoms are the same.
I connected over the LAN (It's been relocated). "chvt 1" is ineffective.
"telinit 3" has no visible effect. Nothing less than "kill -KILL" got
rid of X and that left the display in a parlous state: random junk,
frozen X mouse cursor.
This is similar:
https://fcp.surfsite.org/modules/newbb/viewtopic.php?viewmode=flat&order=...
I have to have this system running, Mrs S requires it. I know this
system runs opensuse 11.0, but I plan on trying CentOS5 first. It's not
available for testing.
fwiw I have a Kubuntu 6.10 sytem I can boot off the LAN. It boots fine
on this system (to a framebuffer console, I don't have X on it), and
even loads the firmware for the wireless card (which certainly was not
present in the original system I did the install on).
--
Cheers
John
-- spambait
1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
12 years, 1 month
usb storage device not being detected
by Neal Becker
This always used to work. Plugging in this sansa device would open the plasma, showing the device. Now, nothing happens. Log says:
Dec 31 17:34:38 nbecker1 kernel: usb 5-2: USB disconnect, address 4
Dec 31 17:34:45 nbecker1 kernel: usb 2-2: new high speed USB device using ehci_hcd and address 6
Dec 31 17:34:45 nbecker1 kernel: ehci_hcd 0000:00:1d.7: port 2 reset error -110
Dec 31 17:34:45 nbecker1 kernel: hub 2-0:1.0: hub_port_status failed (err = -32)
Dec 31 17:34:45 nbecker1 kernel: hub 2-0:1.0: unable to enumerate USB device on port 2
Dec 31 17:34:46 nbecker1 kernel: usb 5-2: new full speed USB device using uhci_hcd and address 5
Dec 31 17:34:46 nbecker1 kernel: usb 5-2: not running at top speed; connect to a high speed hub
Dec 31 17:34:46 nbecker1 kernel: usb 5-2: configuration #1 chosen from 1 choice
Dec 31 17:34:46 nbecker1 kernel: scsi7 : SCSI emulation for USB Mass Storage devices
Dec 31 17:34:46 nbecker1 kernel: usb 5-2: New USB device found, idVendor=0781, idProduct=7432
Dec 31 17:34:46 nbecker1 kernel: usb 5-2: New USB device strings: Mfr=6, Product=7, SerialNumber=8
Dec 31 17:34:46 nbecker1 kernel: usb 5-2: Product: SanDisk Sansa Clip
Dec 31 17:34:46 nbecker1 kernel: usb 5-2: Manufacturer: SanDisk
Dec 31 17:34:46 nbecker1 kernel: usb 5-2: SerialNumber: F4FEF9132030B5910000000000000000
12 years, 2 months