I apologize if some of these have been mention previously but here are some issue I ran into with the F9 preview.
1) Shortly after using gnome nautilus crashed X after opening a browser window ( I had switched off spatial nautilus). ctrl+alt_backspace was needed to exit. 2) GDM does not honor any settings changes in /etc/profile (is there another location?) 3) When using KDM, the first login works but if I logout KDM no longer accepts keyboard input. Restarting the X server resolves this. 4) Networkmanager and bridged networking. I am trying to setup a Xen style bridge setup. Network manager overrides this configuration, however disabling networkmanager at startup left me with no network. A manual network restart resolves this.
I don't know if this is related but I am using the Beta Nvidia drivers with experimental xorg 1.4 support (does anyone know how to control the GPU fan without using the binary drivers?).
Mark Bidewell
Mark Bidewell <mark.bidewell <at> alumni.clemson.edu> writes:
3) When using KDM, the first login works but if I logout KDM no longer accepts keyboard input. Restarting the X server resolves this.
In my case if I logout then I can log back in but the touchpad no longer accepts tap input and I have to use the left button adjacent to the touchpad instead. As you say restarting X returns the system to normal touchpad behaviour.
Mike C wrote:
Mark Bidewell <mark.bidewell <at> alumni.clemson.edu> writes:
- When using KDM, the first login works but if I logout KDM no longer
accepts keyboard input. Restarting the X server resolves this.
In my case if I logout then I can log back in but the touchpad no longer accepts tap input and I have to use the left button adjacent to the touchpad instead. As you say restarting X returns the system to normal touchpad behaviour.
fyi, related bz report: https://bugzilla.redhat.com/show_bug.cgi?id=443320
-- Rex
Mike C <mike.cloaked <at> gmail.com> writes:
In my case if I logout then I can log back in but the touchpad no longer accepts tap input and I have to use the left button adjacent to the touchpad instead. As you say restarting X returns the system to normal touchpad behaviour.
I was not up to date enough - I just updated and now have the same behaviour as above - i.e. after logout no keyboard input.
By the way great to see administrator mode working now - excellent!
On Mon, 2008-04-21 at 08:42 -0400, Mark Bidewell wrote:
I apologize if some of these have been mention previously but here are some issue I ran into with the F9 preview.
- Shortly after using gnome nautilus crashed X after opening a
browser window ( I had switched off spatial nautilus). ctrl +alt_backspace was needed to exit. 2) GDM does not honor any settings changes in /etc/profile (is there another location?) 3) When using KDM, the first login works but if I logout KDM no longer accepts keyboard input. Restarting the X server resolves this. 4) Networkmanager and bridged networking. I am trying to setup a Xen style bridge setup. Network manager overrides this configuration, however disabling networkmanager at startup left me with no network. A manual network restart resolves this.
Mark any devices that you do not want to control with NetworkManager with NM_CONTROLLED=no in the ifcfg file for that device. Of course that makes the device unmanaged by NM, and therefore it will never be your default route, but it might work for you if you want to keep using NM.
Dan
I don't know if this is related but I am using the Beta Nvidia drivers with experimental xorg 1.4 support (does anyone know how to control the GPU fan without using the binary drivers?).
Mark Bidewell
fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
On Mon, Apr 21, 2008 at 12:45:02PM -0400, Dan Williams wrote:
Mark any devices that you do not want to control with NetworkManager with NM_CONTROLLED=no in the ifcfg file for that device. Of course that makes the device unmanaged by NM, and therefore it will never be your default route, but it might work for you if you want to keep using NM.
How does NM choose the device to use for the default route? I had a problem with NM choosing the device that has NO default route over the one that has a default route.
On Mon, 2008-04-21 at 13:16 -0400, Chuck Anderson wrote:
On Mon, Apr 21, 2008 at 12:45:02PM -0400, Dan Williams wrote:
Mark any devices that you do not want to control with NetworkManager with NM_CONTROLLED=no in the ifcfg file for that device. Of course that makes the device unmanaged by NM, and therefore it will never be your default route, but it might work for you if you want to keep using NM.
How does NM choose the device to use for the default route? I had a problem with NM choosing the device that has NO default route over the one that has a default route.
Latest activated wired device, then wireless, then GSM/CDMA. AutoIPv4 devices never get the default route. Do you by chance have a device that's not really connected to anything?
Dan
On Mon, Apr 21, 2008 at 01:25:09PM -0400, Dan Williams wrote:
On Mon, 2008-04-21 at 13:16 -0400, Chuck Anderson wrote:
On Mon, Apr 21, 2008 at 12:45:02PM -0400, Dan Williams wrote:
Mark any devices that you do not want to control with NetworkManager with NM_CONTROLLED=no in the ifcfg file for that device. Of course that makes the device unmanaged by NM, and therefore it will never be your default route, but it might work for you if you want to keep using NM.
How does NM choose the device to use for the default route? I had a problem with NM choosing the device that has NO default route over the one that has a default route.
Latest activated wired device, then wireless, then GSM/CDMA. AutoIPv4 devices never get the default route. Do you by chance have a device that's not really connected to anything?
I have a device that's connected to a network with DHCP but that doesn't connect to the world. Is that so strange? It happens to use RFC1918 addressing, and no default "routers" options is sent by the DHCP server.
Le Lun 21 avril 2008 19:25, Dan Williams a écrit :
On Mon, 2008-04-21 at 13:16 -0400, Chuck Anderson wrote:
On Mon, Apr 21, 2008 at 12:45:02PM -0400, Dan Williams wrote:
Mark any devices that you do not want to control with
NetworkManager
with NM_CONTROLLED=no in the ifcfg file for that device. Of
course that
makes the device unmanaged by NM, and therefore it will never be
your
default route, but it might work for you if you want to keep using
NM.
How does NM choose the device to use for the default route? I had a problem with NM choosing the device that has NO default route over the one that has a default route.
Latest activated wired device, then wireless, then GSM/CDMA. AutoIPv4 devices never get the default route. Do you by chance have a device that's not really connected to anything?
That's pretty common in home networks where the trusty linux desktop bridges/NATs the brittle home lan to the wild internet. The wired connection to the LAN is therefore a dead end.
Dnia 21-04-2008, pon o godzinie 13:25 -0400, Dan Williams pisze:
On Mon, 2008-04-21 at 13:16 -0400, Chuck Anderson wrote:
On Mon, Apr 21, 2008 at 12:45:02PM -0400, Dan Williams wrote:
Mark any devices that you do not want to control with NetworkManager with NM_CONTROLLED=no in the ifcfg file for that device. Of course that makes the device unmanaged by NM, and therefore it will never be your default route, but it might work for you if you want to keep using NM.
How does NM choose the device to use for the default route? I had a problem with NM choosing the device that has NO default route over the one that has a default route.
Latest activated wired device, then wireless, then GSM/CDMA. AutoIPv4 devices never get the default route. Do you by chance have a device that's not really connected to anything?
I have eth0 connected to real network without DHCP. IP for eth0 was configured statically in installer. Default gateway is reachable by eth0. I also have eth1 which is directly connected to other computer. No default route, no DHCP. After first boot I had no network connectivity. Or network dissappeared when I logged in, I don't remeber correctly. NM cleared /etc/resolv.conf and default route. First I tried to configure eth0 as static IP in NM. But I got lost in dialog. Clicked Add, got some settings for "Wired connection 1" but couldn't find how to select which eth* I'm configuring (BTW, this computer has 4 ethernet cards). I gave up. So I stuck NETWORKMANAGER=no, NM_CONTROLLED=no and GATEWAY=x.x.x.x in ifcfg-eth0, but I still don't have network (default route/nameservers) after reboot.
On the other way, mobile broadband works perfectly, requiring plugin my Huawei E220 and two (2!) clicks.
On Tue, Apr 22, 2008 at 01:24:05PM +0200, Tomasz Torcz wrote:
Dnia 21-04-2008, pon o godzinie 13:25 -0400, Dan Williams pisze:
Latest activated wired device, then wireless, then GSM/CDMA. AutoIPv4 devices never get the default route. Do you by chance have a device that's not really connected to anything?
I have eth0 connected to real network without DHCP. IP for eth0 was configured statically in installer. Default gateway is reachable by eth0. I also have eth1 which is directly connected to other computer. No default route, no DHCP. After first boot I had no network connectivity. Or network dissappeared when I logged in, I don't remeber correctly. NM cleared /etc/resolv.conf and default route.
https://bugzilla.redhat.com/show_bug.cgi?id=437338
I attached a patch there that fixes the issue for me.
On Tue, 2008-04-22 at 08:16 -0400, Chuck Anderson wrote:
On Tue, Apr 22, 2008 at 01:24:05PM +0200, Tomasz Torcz wrote:
Dnia 21-04-2008, pon o godzinie 13:25 -0400, Dan Williams pisze:
Latest activated wired device, then wireless, then GSM/CDMA. AutoIPv4 devices never get the default route. Do you by chance have a device that's not really connected to anything?
I have eth0 connected to real network without DHCP. IP for eth0 was configured statically in installer. Default gateway is reachable by eth0. I also have eth1 which is directly connected to other computer. No default route, no DHCP. After first boot I had no network connectivity. Or network dissappeared when I logged in, I don't remeber correctly. NM cleared /etc/resolv.conf and default route.
https://bugzilla.redhat.com/show_bug.cgi?id=437338
I attached a patch there that fixes the issue for me.
And pushed upstream, thanks! Will be in the next F9 and rawhide snapshots.
Dan
The way I solved these issues was to reenable the network service
chkconfig network on service network restart
I didn't realize the network service was not being used.
Also, further investigation shows that GDM sources /etc/profile for GNOME but not KDE. Is there a reason for this?
Mark Bidewell
On Tue, Apr 22, 2008 at 10:34 AM, Dan Williams dcbw@redhat.com wrote:
On Tue, 2008-04-22 at 08:16 -0400, Chuck Anderson wrote:
On Tue, Apr 22, 2008 at 01:24:05PM +0200, Tomasz Torcz wrote:
Dnia 21-04-2008, pon o godzinie 13:25 -0400, Dan Williams pisze:
Latest activated wired device, then wireless, then GSM/CDMA.
AutoIPv4
devices never get the default route. Do you by chance have a device that's not really connected to anything?
I have eth0 connected to real network without DHCP. IP for eth0 was configured statically in installer. Default gateway is reachable by eth0. I also have eth1 which is directly connected to other computer. No default route, no DHCP. After first boot I had no network connectivity. Or network
dissappeared
when I logged in, I don't remeber correctly. NM cleared
/etc/resolv.conf
and default route.
https://bugzilla.redhat.com/show_bug.cgi?id=437338
I attached a patch there that fixes the issue for me.
And pushed upstream, thanks! Will be in the next F9 and rawhide snapshots.
Dan
-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list