Just a few days ago, I switched from my old, reliable LG Flatron L1960TR-BF (4:3, 1280x1024) monitor to an Asus VH242 (16:9). Both are LCD types with flourescent tube, not LED, backlight. With everything shutdown, I hooked up the Asus using the LG's DVI-DVI cable. The boot went fine. New monitor got recognized and properly configured to 1920x1080. Nouveau driver. The desktop, however, had two panel anomalies.
In the top panel, a couple of the application launchers got switched even though they had been locked. They still worked and were still shown "locked", but their place on the panel had been transposed. No problem. Switched them back, relocked, and it took even when rebooting. However, the bottom panel was the curious one. It was now at the top of the screen beneath the "top" panel, and would not reset to the bottom through Properties, nor would it go to the left or right. It changed to vertical and held the setting, but stayed centered at the top of the screen.
After several failed attempts to alter its position, I just created a new, duplicate panel, set to the bottom which it went to, and deleted the original bottom panel. Problem solved or so I thought. When I rebooted the system the next day (I shut my system down when I go to bed), the new bottom panel was at the top just like the old one, and would not reset to the bottom. You could set "bottom", but the setting would immediately change back to "top" without the panel moving.
I should mention that the top panel had "Extended" set, a solid color (white) background and transparency very transparent. The bottom panel was set the same, except Extended was turned off.
I was able to "fix" the problem by setting the Extended option on the bottom panel, then it would move to the bottom and stay there after a boot. If not set to extended, it would not.
Now, here's the real curious thing: I didn't have this problem with the LG monitor.
Any clue as to the cause? A flaw in nouveau? I checked ps -ef and it lists two nouveau processes running. Don't remember having two with the LG.
root 180 2 0 0 0 0 11:28 ? 00:00:00 [nouveau/0]
root 181 2 0 0 0 1 11:28 ? 00:00:00 [nouveau/1]
I'm running Fedora 12 64-bit. Fully updated. Basically a "stock" install. No 3D artsy-fartsy stuff, etc. GNOME desktop only. No others installed or ever used. Not even other window managers.
And, before you say it, no(!), I'm not upgrading to 14. ;-)
I have a Fedora 14 64 bit installation running on a machine with a
dual core AMD 64 bit at 3,00 GHz cpu ,
2 GB of RAM and a lot of hard disk space ( the Fedora installation
resides on a 1,5 TB hard disk drive ) .
I have succesfully installed and run a virtual machine running Windows
XP Professional under QEMU but
now i wanted to do it with Xen . I have google for it and it seems that
the first thing am missing is a Xen
kernel . Since am quite new on this thing i was wondering if there is
somewhere a step by step guide with
instructions on how to install and run a virtual machine under Xen
instead of QEMU .
Kind Regards ,
I have an applet that will not work with IcedTea. This applet is a remote
console applet spawned by the HP iLO web interface and is critical for my
With F13, I was able to successfully install the Oracle jre and soft link
the correct plugin.
Recently, I upgraded to F14. Of course, the Open jre with IcedTea came with
F14, so I "yum erase" the jre and "rpm -ivh" the Oracle jre, just as I did
in F13, an soft linked to the correct plugin thus:
# ln -sf /usr/java/latest/lib/i386/libnpjp2.so /usr/lib/mozilla/plugins
... which is what I did in F13.
However, I have actually removed everything from /usr/lib/mozilla/plugins
and from my /home/user/.mozilla/plugins directories, and I am still seeing
plugins in FireFox, most annoyingly, this one.
The IcedTea NPR Web Browser Plugin (using IcedTea6 1.8 (fedora-41.b18.fc13-i386)) executes Java applets.
Appreciate any and all help ...
Can somebody explain why pure numbers are allowed for username in the
sudo useradd 123456789
is not rejected!
As is known, this leads to big problems if referring to such a user and
the username differs from the userid: should such a username be
interpreted as username or userid?
Thanks for each comment.
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
Dear fellow fedora users,
I have several machines running Fedora 14 and I get the message:
Starting capi4linux: udev-work[46X]: kernel-provided name 'capi' and NAME= 'api20' disagree, please use SYMLINK+= or change the kernel to provide the proper name
Does this "service" do anything special or important on the computer that is is "really needed"?
I am deliberating whether to
# service capi4linux stop
# chkconfig capi4linux off
and not see it again?
I see machine freezing randomly too, Don't know what to blame, nouveau, capi4linux, or other thing? Machine froze several times since Fedora 10, but then had not froze, but now it does and screen just changes color. Is there something I can do,
NO I won't check the memory, been there and done that. Memory tests report fine :)
Thanks for advice/suggestions/ and other answers are greatly appreciated.
P.S. will give smoltProfile if needed to determine if that could be what is wrong?