Glitchy display: nvidia driver, KDE, or hardware problem ?
by Reuben D. Budiardja
Hello,
I am using F10 with KDE 4.1, using nvidia-173xx driver (the older nvidia
driver, I think). My graphic card is GE Force FX 5500 AGP (rather old). I use
some 3D effect in KDE. I use both the DVI and VGA output from the card with
Twinview option.
The problem is :
1. rather frequently the desktop would lock up for few seconds. Sometime when
this happens, I can move around my mouse pointer but not do anything else. The
mouse pointer becomes a block of glitchy display that moves around. On other
instances, it would just lock up and not accepting any input.
2. Once in a while the whole screen would blink with a blank screen, then
comes back to normal.
When these things happen, I don't usually do anything fancy (i.e. not
switching / moving Windows with 3D effect or anything like that), just simply
typing on terminal or document. When (1) happen, the OS itself is still
running. I can workaround the lock up by switching to TTY (CTRL-ALT-F2), then
switch back to X again. That almost always clears the lock up, although
sometime it takes a second or two before CTRL-ALT-F2 gave me TTY.
So, my question is, is there a known problem with either the Nvidia driver, or
KDE, or the combination of both ? Or, am I simply having a bad graphic card ?
Any suggestions to find out ?
Thanks.
RDB
15 years, 2 months
Fedora 10, login screen
by Margaret Doll
How can I change the login screen? I either want to remove the
partial list of users on the systems or extend the list to all the
users.
15 years, 2 months
F10: boot hangs after yesterday's yum updates
by Colin Brace
Hi all,
Last night I ran yum and installed forty or so updates. Just now I rebooted
the machine. Alas it is hanging during the boot process. The horizontal bar
appears at the bottom of the screen, the system appears to be loading, and
then it stops when the bar has turned white.
If I press c-a-d I see a flurry of error messages before the system shuts
down -- something about alsa... -- but they flash by too quickly to be
helpful.
Is there any way of disabling this progress bar so I can actually see what
is or what is not happening?
I hoped that sshd was loaded, but no remote login possible at this point.
I tried booting an earlier kernel. Same problem.
Anyone have any other suggestions?
TIA
-----
Colin Brace
Amsterdam
http://lim.nl
--
View this message in context: http://www.nabble.com/F10%3A-boot-hangs-after-yesterday%27s-yum-updates-t...
Sent from the Fedora List mailing list archive at Nabble.com.
15 years, 2 months
vsftp and chroot problem
by Dan Track
Hi Guys,
I'm hoping you pro's can help me on this. I've setup vsftp to chroot
users to their home directory after logging in via ftp, however I need
one of those users to chroot to a different directory /opt/ftp/upload,
can someone please let me know how I can achieve this?
Thanks
Dan
15 years, 2 months
Re: F10, NetworkManager, and intermittent dns -- Update
by McGuffey, David C.
On Date: Tue, 3 Feb 2009 15:59:25 -0500, McGuffey, David C. wrote:
>
> Problem persists. Have had several batches of patches pushed through
> yum auto update, but nothing concerning NM to fix this problem.
>
> I set PEERDNS=no with no affect.
>
> I set /etc/resolv.conf to a workable solution and then removed the
write
> bits and set it immutable. I get errors in /var/log/messages about
it,
> but the behavior is still the same. After a reboot, all is OK. After
a
> while, dns dies. Restarting NM brings it back to life...then it dies
a
> few minutes later. As long as someone is actively accessing the net,
> dns seems to stay up. But give it a few minutes of idle time and
> something causes it to stop. Here is a snapshot of /var/log/messages
> before, during, and after a NM restart. Can anyone figure out what is
> going wrong with dns?
>
> Feb 2 21:23:45 desk NetworkManager: <WARN> nm_signal_handler():
> Caught signal 15, shutting down normally.
> Feb 2 21:23:45 desk NetworkManager: <info> (eth0): now unmanaged Feb
> 2 21:23:45 desk NetworkManager: <info> (eth0): device state
> change: 8 -> 1
> Feb 2 21:23:45 desk NetworkManager: <info> (eth0): deactivating
device
> (reason: 36).
> Feb 2 21:23:45 desk NetworkManager: <info> eth0: canceled DHCP
> transaction, dhcp client pid 2034 Feb 2 21:23:45 desk NetworkManager:
> <WARN>
> nm_named_manager_remove_ip4_config(): Could not commit DNS changes.
> Error: 'Could not replace /etc/resolv.conf: Operation not
permitted#012'
> Feb 2 21:23:45 desk NetworkManager: <WARN> check_one_route(): (eth0)
> error -34 returned from rtnl_route_del(): Sucess#012 Feb 2 21:23:45
> desk avahi-daemon[2071]: Withdrawing address record for
> 192.168.1.2 on eth0.
> Feb 2 21:23:45 desk avahi-daemon[2071]: Leaving mDNS multicast group
on
> interface eth0.IPv4 with address 192.168.1.2.
> Feb 2 21:23:45 desk avahi-daemon[2071]: Interface eth0.IPv4 no longer
> relevant for mDNS.
> Feb 2 21:23:45 desk NetworkManager: <info> (eth0): cleaning up...
> Feb 2 21:23:45 desk NetworkManager: <info> (eth0): taking down
device.
> Feb 2 21:23:45 desk avahi-daemon[2071]: Withdrawing address record
for
> fe80::207:e9ff:fef2:b64d on eth0.
> Feb 2 21:23:45 desk NetworkManager: <info> disconnected by the
system
> bus.
> Feb 2 21:23:45 desk nm-dispatcher.action: Error in get_property: The
> name org.freedesktop.NetworkManager was not provided by any .service
> files Feb 2 21:23:46 desk NetworkManager: <info> starting...
> Feb 2 21:23:46 desk NetworkManager: <WARN>
> nm_generic_enable_loopback(): error -17 returned from
> rtnl_addr_add():#012Sucess#012
> Feb 2 21:23:46 desk NetworkManager: <info> eth0: driver is 'e100'.
> Feb 2 21:23:46 desk NetworkManager: <info> Found new Ethernet device
> 'eth0'.
> Feb 2 21:23:46 desk NetworkManager: <info> (eth0): exported as
> /org/freedesktop/Hal/devices/net_00_07_e9_f2_b6_4d
> Feb 2 21:23:50 desk NetworkManager: <info> (eth0): device state
> change: 1 -> 2
> Feb 2 21:23:50 desk NetworkManager: <info> (eth0): bringing up
device.
> Feb 2 21:23:50 desk kernel: e100: eth0: e100_watchdog: link up,
> 100Mbps, full-duplex Feb 2 21:23:50 desk kernel: ADDRCONF(NETDEV_UP):
> eth0: link is not ready Feb 2 21:23:50 desk kernel:
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Feb 2 21:23:50 desk
> NetworkManager: <info> (eth0): preparing device.
> Feb 2 21:23:50 desk NetworkManager: <info> (eth0): deactivating
device
> (reason: 2).
> Feb 2 21:23:50 desk NetworkManager: <info> (eth0): carrier now ON
> (device state 2) Feb 2 21:23:50 desk NetworkManager: <info> (eth0):
> device state
> change: 2 -> 3
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0)
starting
> connection 'System eth0'
> Feb 2 21:23:50 desk NetworkManager: <info> (eth0): device state
> change: 3 -> 4
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 1
> of 5 (Device Prepare) scheduled...
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 1
> of 5 (Device Prepare) started...
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 2
> of 5 (Device Configure) scheduled...
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 1
> of 5 (Device Prepare) complete.
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 2
> of 5 (Device Configure) starting...
> Feb 2 21:23:50 desk NetworkManager: <info> (eth0): device state
> change: 4 -> 5
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 2
> of 5 (Device Configure) successful.
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 3
> of 5 (IP Configure Start) scheduled.
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 2
> of 5 (Device Configure) complete.
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 3
> of 5 (IP Configure Start) started...
> Feb 2 21:23:50 desk NetworkManager: <info> (eth0): device state
> change: 5 -> 7
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0)
Beginning
> DHCP transaction.
> Feb 2 21:23:50 desk dhclient: Internet Systems Consortium DHCP Client
> 4.0.0 Feb 2 21:23:50 desk dhclient: Copyright 2004-2007 Internet
> Systems Consortium.
> Feb 2 21:23:50 desk dhclient: All rights reserved.
> Feb 2 21:23:50 desk dhclient: For info, please visit
> http://www.isc.org/sw/dhcp/ Feb 2 21:23:50 desk dhclient:
> Feb 2 21:23:50 desk NetworkManager: <info> dhclient started with pid
> 4747
> Feb 2 21:23:50 desk dhclient: Listening on LPF/eth0/00:07:e9:f2:b6:4d
> Feb 2 21:23:50 desk dhclient: Sending on LPF/eth0/00:07:e9:f2:b6:4d
> Feb 2 21:23:50 desk dhclient: Sending on Socket/fallback
> Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 3
> of 5 (IP Configure Start) complete.
> Feb 2 21:23:50 desk NetworkManager: <info> DHCP: device eth0 state
> changed (null) -> preinit Feb 2 21:23:52 desk dhclient: DHCPDISCOVER
on
> eth0 to 255.255.255.255 port 67 interval 4 Feb 2 21:23:52 desk
> avahi-daemon[2071]: Registering new address record for
> fe80::207:e9ff:fef2:b64d on eth0.*.
> Feb 2 21:23:53 desk dhclient: DHCPOFFER from 192.168.1.1 Feb 2
> 21:23:53 desk dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
> Feb 2 21:23:53 desk dhclient: DHCPACK from 192.168.1.1 Feb 2
21:23:53
> desk NetworkManager: <info> DHCP: device eth0 state changed preinit
->
> bound Feb 2 21:23:53 desk NetworkManager: <info> Activation (eth0)
> Stage 4 of 5 (IP Configure Get) scheduled...
> Feb 2 21:23:53 desk NetworkManager: <info> Activation (eth0) Stage 4
> of 5 (IP Configure Get) started...
> Feb 2 21:23:53 desk NetworkManager: <info> address 192.168.1.2
> Feb 2 21:23:53 desk NetworkManager: <info> prefix 24
(255.255.255.0)
> Feb 2 21:23:53 desk NetworkManager: <info> gateway 192.168.1.1
> Feb 2 21:23:53 desk NetworkManager: <info> hostname 'desk'
> Feb 2 21:23:53 desk NetworkManager: <info> nameserver
'192.168.1.1'
> Feb 2 21:23:53 desk NetworkManager: <info> domain name
> 'seclab.net'
> Feb 2 21:23:53 desk NetworkManager: <info> Activation (eth0) Stage 5
> of 5 (IP Configure Commit) scheduled...
> Feb 2 21:23:53 desk NetworkManager: <info> Activation (eth0) Stage 4
> of 5 (IP Configure Get) complete.
> Feb 2 21:23:53 desk NetworkManager: <info> Activation (eth0) Stage 5
> of 5 (IP Configure Commit) started...
> Feb 2 21:23:53 desk avahi-daemon[2071]: Joining mDNS multicast group
on
> interface eth0.IPv4 with address 192.168.1.2.
> Feb 2 21:23:53 desk avahi-daemon[2071]: New relevant interface
> eth0.IPv4 for mDNS.
> Feb 2 21:23:53 desk avahi-daemon[2071]: Registering new address
record
> for 192.168.1.2 on eth0.IPv4.
> Feb 2 21:23:53 desk dhclient: bound to 192.168.1.2 -- renewal in
80417
> seconds.
> Feb 2 21:23:54 desk NetworkManager: <WARN>
> nm_named_manager_add_ip4_config(): Could not commit DNS changes.
Error:
> 'Could not replace /etc/resolv.conf: Operation not permitted#012'
> Feb 2 21:23:54 desk NetworkManager: <info> (eth0): device state
> change: 7 -> 8
> Feb 2 21:23:54 desk NetworkManager: <WARN>
> nm_named_manager_add_ip4_config(): Could not commit DNS changes.
Error:
> 'Could not replace /etc/resolv.conf: Operation not permitted#012'
> Feb 2 21:23:54 desk NetworkManager: <info> Policy set 'System eth0'
> (eth0) as default for routing and DNS.
> Feb 2 21:23:54 desk NetworkManager: <info> Activation (eth0)
> successful, device activated.
> Feb 2 21:23:54 desk NetworkManager: <info> Activation (eth0) Stage 5
> of 5 (IP Configure Commit) complete.
> Feb 2 22:56:55 desk NetworkManager: <WARN> nm_signal_handler():
Caught
> signal 15, shutting down normally.
> Feb 2 22:56:55 desk NetworkManager: <info> (eth0): now unmanaged Feb
> 2 22:56:55 desk NetworkManager: <info> (eth0): device state
> change: 8 -> 1
> Feb 2 22:56:55 desk NetworkManager: <info> (eth0): deactivating
device
> (reason: 36).
> Feb 2 22:56:55 desk NetworkManager: <info> eth0: canceled DHCP
> transaction, dhcp client pid 4747 Feb 2 22:56:55 desk NetworkManager:
> <WARN>
> nm_named_manager_remove_ip4_config(): Could not commit DNS changes.
> Error: 'Could not replace /etc/resolv.conf: Operation not
permitted#012'
> Feb 2 22:56:55 desk NetworkManager: <WARN> check_one_route(): (eth0)
> error -34 returned from rtnl_route_del(): Sucess#012 Feb 2 22:56:55
> desk avahi-daemon[2071]: Withdrawing address record for
> 192.168.1.2 on eth0.
> Feb 2 22:56:55 desk avahi-daemon[2071]: Leaving mDNS multicast group
on
> interface eth0.IPv4 with address 192.168.1.2.
> Feb 2 22:56:55 desk avahi-daemon[2071]: Interface eth0.IPv4 no longer
> relevant for mDNS.
> Feb 2 22:56:55 desk NetworkManager: <info> (eth0): cleaning up...
> Feb 2 22:56:55 desk NetworkManager: <info> (eth0): taking down
device.
> Feb 2 22:56:55 desk avahi-daemon[2071]: Withdrawing address record
for
> fe80::207:e9ff:fef2:b64d on eth0.
> Feb 2 22:56:55 desk NetworkManager: <info> disconnected by the
system
> bus.
> Feb 2 22:56:56 desk NetworkManager: <info> starting...
> Feb 2 22:56:56 desk NetworkManager: <WARN>
> nm_generic_enable_loopback(): error -17 returned from
> rtnl_addr_add():#012Sucess#012
> Feb 2 22:56:56 desk NetworkManager: <info> eth0: driver is 'e100'.
> Feb 2 22:56:56 desk NetworkManager: <info> Found new Ethernet device
> 'eth0'.
> Feb 2 22:56:56 desk NetworkManager: <info> (eth0): exported as
> /org/freedesktop/Hal/devices/net_00_07_e9_f2_b6_4d
> Feb 2 22:57:00 desk NetworkManager: <info> (eth0): device state
> change: 1 -> 2
> Feb 2 22:57:00 desk NetworkManager: <info> (eth0): bringing up
device.
> Feb 2 22:57:00 desk kernel: e100: eth0: e100_watchdog: link up,
> 100Mbps, full-duplex Feb 2 22:57:00 desk kernel: ADDRCONF(NETDEV_UP):
> eth0: link is not ready Feb 2 22:57:00 desk kernel:
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Feb 2 22:57:00 desk
> NetworkManager: <info> (eth0): preparing device.
> Feb 2 22:57:00 desk NetworkManager: <info> (eth0): deactivating
device
> (reason: 2).
> Feb 2 22:57:00 desk NetworkManager: <info> (eth0): carrier now ON
> (device state 2) Feb 2 22:57:00 desk NetworkManager: <info> (eth0):
> device state
> change: 2 -> 3
> Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0)
starting
> connection 'System eth0'
> Feb 2 22:57:00 desk NetworkManager: <info> (eth0): device state
> change: 3 -> 4
> Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 1
> of 5 (Device Prepare) scheduled...
> Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 1
> of 5 (Device Prepare) started...
> Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 2
> of 5 (Device Configure) scheduled...
> Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 1
> of 5 (Device Prepare) complete.
> Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 2
> of 5 (Device Configure) starting...
> Feb 2 22:57:00 desk NetworkManager: <info> (eth0): device state
> change: 4 -> 5
> Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 2
> of 5 (Device Configure) successful.
> Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 3
> of 5 (IP Configure Start) scheduled.
> Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 2
> of 5 (Device Configure) complete.
> Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 3
> of 5 (IP Configure Start) started...
> Feb 2 22:57:00 desk NetworkManager: <info> (eth0): device state
> change: 5 -> 7
> Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0)
Beginning
> DHCP transaction.
> Feb 2 22:57:00 desk dhclient: Internet Systems Consortium DHCP Client
> 4.0.0 Feb 2 22:57:00 desk dhclient: Copyright 2004-2007 Internet
> Systems Consortium.
> Feb 2 22:57:00 desk dhclient: All rights reserved.
> Feb 2 22:57:00 desk dhclient: For info, please visit
> http://www.isc.org/sw/dhcp/ Feb 2 22:57:00 desk dhclient:
> Feb 2 22:57:00 desk NetworkManager: <info> dhclient started with pid
> 13377
> Feb 2 22:57:00 desk dhclient: Listening on LPF/eth0/00:07:e9:f2:b6:4d
> Feb 2 22:57:00 desk dhclient: Sending on LPF/eth0/00:07:e9:f2:b6:4d
> Feb 2 22:57:00 desk dhclient: Sending on Socket/fallback
> Feb 2 22:57:00 desk dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
> port 67 interval 6 Feb 2 22:57:00 desk NetworkManager: <info>
> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
> Feb 2 22:57:00 desk NetworkManager: <info> DHCP: device eth0 state
> changed (null) -> preinit Feb 2 22:57:01 desk avahi-daemon[2071]:
> Registering new address record for fe80::207:e9ff:fef2:b64d on eth0.*.
> Feb 2 22:57:02 desk dhclient: DHCPOFFER from 192.168.1.1 Feb 2
> 22:57:02 desk dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
> Feb 2 22:57:02 desk dhclient: DHCPACK from 192.168.1.1 Feb 2
22:57:02
> desk NetworkManager: <info> DHCP: device eth0 state changed preinit
->
> bound Feb 2 22:57:02 desk NetworkManager: <info> Activation (eth0)
> Stage 4 of 5 (IP Configure Get) scheduled...
> Feb 2 22:57:02 desk NetworkManager: <info> Activation (eth0) Stage 4
> of 5 (IP Configure Get) started...
> Feb 2 22:57:02 desk NetworkManager: <info> address 192.168.1.2
> Feb 2 22:57:02 desk NetworkManager: <info> prefix 24
(255.255.255.0)
> Feb 2 22:57:02 desk NetworkManager: <info> gateway 192.168.1.1
> Feb 2 22:57:02 desk NetworkManager: <info> hostname 'desk'
> Feb 2 22:57:02 desk NetworkManager: <info> nameserver
'192.168.1.1'
> Feb 2 22:57:02 desk NetworkManager: <info> domain name
> 'seclab.net'
> Feb 2 22:57:02 desk NetworkManager: <info> Activation (eth0) Stage 5
> of 5 (IP Configure Commit) scheduled...
> Feb 2 22:57:02 desk NetworkManager: <info> Activation (eth0) Stage 4
> of 5 (IP Configure Get) complete.
> Feb 2 22:57:02 desk NetworkManager: <info> Activation (eth0) Stage 5
> of 5 (IP Configure Commit) started...
> Feb 2 22:57:02 desk avahi-daemon[2071]: Joining mDNS multicast group
on
> interface eth0.IPv4 with address 192.168.1.2.
> Feb 2 22:57:02 desk avahi-daemon[2071]: New relevant interface
> eth0.IPv4 for mDNS.
> Feb 2 22:57:02 desk avahi-daemon[2071]: Registering new address
record
> for 192.168.1.2 on eth0.IPv4.
> Feb 2 22:57:02 desk dhclient: bound to 192.168.1.2 -- renewal in
84449
> seconds.
> Feb 2 22:57:03 desk NetworkManager: <WARN>
> nm_named_manager_add_ip4_config(): Could not commit DNS changes.
Error:
> 'Could not replace /etc/resolv.conf: Operation not permitted#012'
> Feb 2 22:57:03 desk NetworkManager: <info> (eth0): device state
> change: 7 -> 8
> Feb 2 22:57:03 desk NetworkManager: <WARN>
> nm_named_manager_add_ip4_config(): Could not commit DNS changes.
Error:
> 'Could not replace /etc/resolv.conf: Operation not permitted#012'
> Feb 2 22:57:03 desk NetworkManager: <info> Policy set 'System eth0'
> (eth0) as default for routing and DNS.
> Feb 2 22:57:03 desk NetworkManager: <info> Activation (eth0)
> successful, device activated.
> Feb 2 22:57:03 desk NetworkManager: <info> Activation (eth0) Stage 5
> of 5 (IP Configure Commit) complete.
> [root@desk ~]#
>
> The error message concerning /etc/resolv.conf is due to the removal of
> write bit and setting it immutable. NM does create a file called
> /etc/resolv.conf.tmp which appears to be a copy of my immutable
> resolv.conf.
>
Found another set of errors. Could this be the root cause of my dns
problem? I hear that NM relies on the keyring...at least for wireless.
I'm not running wireless on this box, and not running NFS. This is a
plain install of an F10 development load.
Feb 4 07:14:59 desk gdm-session-worker[7681]: gnome-keyring-daemon:
couldn't lookup keyring component setting: Failed to contact
configuration server; some possible causes are that you need to enable
TCP/IP networking for ORBit, or you have stale NFS locks due to a system
crash. See http://www.gnome.org/projects/gconf/ for information.
(Details - 1: Not running within active session)gnome-keyring-daemon:
couldn't lookup ssh component setting: Failed to contact configuration
server; some possible causes are that you need to enable TCP/IP
networking for ORBit, or you have stale NFS locks due to a system crash.
See http://www.gnome.org/projects/gconf/ for information. (Details - 1:
Not running within active session)gnome-keyring-daemon: couldn't lookup
pkcs11 component setting: Failed to contact configuration server; some
possible causes are that you need to enable TCP/IP networking for ORBit,
or you have stale NFS locks due to a system crash. See
http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not
running within active session)
Dave McGuffey
Principal Information System Security Engineer // NSA-IEM, NSA-IAM
Save a Tree...Unless necessary don't print this e-mail
15 years, 2 months
OT?: Thunderbird/Firefox - http links changed to file: links??
by G.Wolfe Woodbury
Recently Ive had a problem with thunderbird and firefox wherein an
http::// link gets changed to a file:/// link somewhere between
clicking the link in thunderbird and the link opening in Firefox.
I've prowled through the advanced config controls of both apps and see
no obvious transformations. I've disabled all extensions in Firefox
(especially NoScript) but the problem persists. I've even uninstalled
and re-installed Firefox to see if that helps.
The next step would be to remove my personal .mozilla tree, but this
would mean loosing all my settings and I've worked a lot customizing my
preferences that I'd rather not lose.
I've done some superficial google searches for the problem, as well as
the Mozilla bugzilla with no relevant returns, bu I admit my google-fu
may be inadequate.
So, has anyone seen anything like this? Were you able to cure it?
Thanks for any help offered.
Fedora relevance: it happens on my F10 installation, not F9 nor the
EvilEmpire installations.
15 years, 2 months
Easiest Way to Configure Wireless Settings Manually?
by Robert L Cochran
What is the easiest way to manually configure an ifcfg-xxxx module and
all the other wireless things I need for a laptop Intel Pro Wifi Link
5300 a/g/n card, without the help of Network Manager? Do I need an
ifcfg-wlan0 module or a module of some other name (as in ifcfg-[something]?)
I'm currently in Boston assisting a relative who needs medical testing,
and I'd love to get wireless going on my laptop (a Dell Latitude E6400)
while doing those long hospital waiting room stays, but when I installed
Fedora 10 on this baby I forgot to turn on the wireless card hardware
switch. So Network Manager didn't configure anything. Just at the moment
I'm using a wireless bridge device and my wired port.
Thanks a lot for the help!
Bob Cochran
15 years, 2 months
Upgrading old RH server
by Ashley M. Kirchner
We have an old RH7.3 server that holds all of our user accounts.
I'm in the process of upgrading everything to FC10 and looking at
/etc/shadow I'm noticing some differences in the way the passwords are
encrypted/stored.
RH7.3's string looks like this:
$1$9cgDnjV/$SLqsoxfwr6tr3o7QkdQ3j1
Whereas FC10 looks like:
$6$KS2xrBPJ$jXiz1pE9Lpcb8sSSU0ZHifeN9wBwc.k7GdWO4KIJ3F2JqEw/1mD7bPO6b4jvRXiyXrQn0noWPfs.0h6/tjKbe0
I tried simply copying the old shadow file to a new FC10 server and
it seems to work just fine, however I wonder if I'm not breaking
something else by doing that. So, what's the proper way to do this? I
really don't want to have to reset everyone's password (at least not
till they reach their forced expiration.)
Thanks.
-- A
15 years, 2 months
rpmbuild and getting Missing Dependency
by Gregory Machin
Hi all.
I'm trying to build an rpm for lightsquid . I have got the rpm to build without any issues but now when I try and install it, it dies with missing dependencies the files are in the install list.
[root@gregory-workstation ~]# rpm -i /home/builder/rpm/RPMS/noarch/lightsquid-1.7-1.noarch.rpm
error: Failed dependencies:
perl(common.pl) is needed by lightsquid-1.7-1.noarch
perl(lightsquid.cfg) is needed by lightsquid-1.7-1.noarch
[root@gregory-workstation ~]#
I have also used mc to browse the contents on the rpm and the files are in it.. so why do I get this error ?
Thanks
Regards
Gregory Machin
Email: gmachin(a)techconcepts.co.za
Cell: +27 (0) 72 524 5098
gtalk: gmachin.techconcepts(a)gmail.com
Support
helpdesk(a)techconcepts.co.za
Tell: +27 (0) 11 803 2169
Fax: +27 (0) 11 803 2189
After Hours
Cell: +27 (0) 82 790 0796
15 years, 2 months