F12 gdm greeter user List missing and other issues

[oneklema]

I have F12 running as guest in Virtualbox. The F12 install had been working well for some time.

I am now having an issue with the following characteristics:
1. Upon bootup when I come to the gdm greeter list it does not have a user list, only the option for "Other"
2. If I do log on, and then attempt to reboot the system through the System->Shutdown menu, I often get only the options to Hibernate or Cancel. This seems to happen randomly and other times I get the normal options to Hibernate, Reboot, Shutdown, or Cancel.
3. Also, randomly, I am unable to mount a USB drive, receiving a lack of permissions error.
4. Also, randomly, if I issue the 'shutdown now' command as root, the system locks up and must be reset.

Issues 2-4 always happen (or don't happen) together. Either I have all of the problems 2-4 or it acts normally. Issue #1 always occurs.

I have found that if I disable networking, through Network Manager applet, and reboot, everything works fine (obviously with no networking) including getting the expected Greeter user list. If I have networking enabled, the networking itself seem to work fine, but I get issues 1-4 as above.

Any help would be appreciated. If any particular log/command output would be helpful, please indicate and I will submit it.

[oneklema]

Just to close out my own post. The problem was solved. It was cased by an incorrectly configured local network. I was using a subnet of 192.168.0.* along side of a subnet of 192.168.1.* and they seemed to conflict (incorrect subnet masks??). I know use 192.168.1.* only. Also, I had configured F12 to use a static IP, and then configured it to use a dynamic IP as assigned by DHCP. I had to return the configuration back to using a static IP for the problem(s) to go away.

I run multiple Fedora machines using VirtualBox and I saw inconsistent behavior regarding these issues, though more than one machine had the problems and were fixed by making the two changes above.

[desertrat]

Off the top of my head, I do believe your subnet should be 255.255.255.0

[forkbomb]

Originally Posted by desertrat

Off the top of my head, I do believe your subnet should be 255.255.255.0

Define "should." If the router is acting as the DHCP server, then 10 to 1 the subnet mask for a 192.168 network is set to 255.255.255.0 (default mask for class C), but there's nothing that says you can't use a nonstandard subnet mask.

[desertrat]

I have found that the non-standard subnet masks don't always work, so I stick with the standard default one. Cause it is a real PITA to find the problem when the non-standard subnet mask decides to go south for the summer.

[forkbomb]

Originally Posted by desertrat

I have found that the non-standard subnet masks don't always work, so I stick with the standard default one. Cause it is a real PITA to find the problem when the non-standard subnet mask decides to go south for the summer.

TCP/IP implementations that are compliant with the relevant RFCs shouldn't present a problem as long as you're still using a valid subnet mask.

The only device I've run into that hasn't handled a nonstandard (classless) subnet mask properly is the Xbox360, which has a crippled TCP/IP stack to begin with.