http://forum.xfce.org/viewtopic.php?id=5089
Sat, 11 Jul 2009 01:05:17 +0000FluxBBhttp://forum.xfce.org/viewtopic.php?pid=18241#p18241
I haven't had any luck duplicating the problem, so I suppose the WM simply failed coincidentally at the same time that I made the changes to /etc/network/interfaces, and then the session got saved that way when I logged out. I've seen occasional weird stuff like this (user interface related) on that system. It's the only one of these systems that has an nVidia graphics card (Quadro). Desktop compositing (with the Open Source driver) is pretty bad on that system, so I have to leave it switched off. Compositing on the other systems, which have ATI or Intel video subsystems, works extremely well and quickly.

I wonder if the nVidia graphics is the problem. I may never know. The problems with graphical user interfaces on this system have happened in GNOME, IceWM, LXDE, Fluxbox, and Xfce. They are always inconsistent in nature, being hard to reproduce (except for poor compositing behavior). It's almost certainly not bad software, per se, since the motherboard and video subsystem have been replaced, once and twice, respectively, with no apparent change in the behaviors.

I'm going to consider this issue "solved".

]]>Sat, 11 Jul 2009 01:05:17 +0000http://forum.xfce.org/viewtopic.php?pid=18241#p18241http://forum.xfce.org/viewtopic.php?pid=18077#p18077
Avinash.Rao, please start a new thread ]]>Mon, 06 Jul 2009 04:33:50 +0000http://forum.xfce.org/viewtopic.php?pid=18077#p18077http://forum.xfce.org/viewtopic.php?pid=18076#p18076
Another thing i have notice in my Xubuntu running on my laptop is that, when i log in, few applications that i have used last time open automatically. And I am sure that I have closed these applications when i used them last time.

Probably just died and your Session was saved, for whatever reason. Probably not even related, don't see any reason network configuration would play with it (especially xfwm).

I guess I just had too many other things (project at work) buzzing around in my head when the failure occurred. I keep forgetting about sessions being saved. There's no excuse for my forgetting that because I've been bitten by this feature before -- and figured it out on my own that time. (I had the panel fail and was surprised to not see it come after I logged out and logged on. Typical Windows user response.) But now that you mention it, this makes sense. All I would have had to do was restart the window manager (as suggested before) and log out, thus saving the session with the wm configured to run.

Come to think of it, maybe it would just make sense for me to turn off automatic session saving once I've got things configured the way I want them. Can you think of any real disadvantage to doing so?

Ask away, the ppl here and on irc (irc.freenode.net in #xfce) are knowledgeable

Yes they are. But before I post 500 questions about "how stuff works" I'm going to be doing some man page and wiki reading.

]]>Sun, 05 Jul 2009 12:35:13 +0000http://forum.xfce.org/viewtopic.php?pid=18068#p18068http://forum.xfce.org/viewtopic.php?pid=18066#p18066
Probably just died and your Session was saved, for whatever reason. Probably not even related, don't see any reason network configuration would play with it (especially xfwm).

Ask away, the ppl here and on irc (irc.freenode.net in #xfce) are knowledgeable

It sounds like xfwm4 died, open a terminal and check (ps ax | grep xfwm4), if so manually run "xfwm4 --replace" (Alt+F2 should bring up the Xfce Run window)

Yep, I really need to actually learn something about Xfce instead of just using and enjoying it. The error message I was seeing mentioned an "unknown window manager". It was really dumb of me not to realize that the message might have meant simply that the window manager wasn't running.

I haven't had time yet to do any testing to try to duplicate the problem, and it may not happen at all this weekend. Kids and grandkids want to do stuff. But when I get around to testing I'm going to remember your suggestion. If I am able to duplicate the problem I'm still going to be very interested in learning why fussing around with the network settings would cause the window manager to become disabled. I have changed the way the network settings are managed on the system by using network-config, so I suppose it's possible that the problem stems from that.

And, at some point, I've got to just do some reading about Xfce so that I actually know the names of the modules. I use Alt+F2 for starting most software, but just haven't got around to learning much about Xfce -- other than the fact that I really like it. A lot.

I do not quite see how a change in networking can have such an effect (unless your home would be on a share which you access via networking). Just one other suggestion should this happen again: the problem appeared to be user related, i.e. other users did not have the problem. A faster work-around probably would have been to delete your own userID, rename /home/username to something else, create a new user with same name, UID and GID and then copy over the userdata from /home/username to your new name

Yes, that was exactly what I was thinking. How on earth could the DE be affected in this way by a change in network settings? No, my home directories aren't on a network location.

Yes, the problem was definitely affecting only the primary standard user profile. I started to just re-create the profile -- but I had a nice, shiny, newly-burned Debian Lenny 5.02 netinst disc (just released a couple of days ago). Since I'm new to Linux and am trying to learn about it I would normally have tried to find the exact location of the configuration issue so I could fix it. Replacing the user profile would have been my second choice, and doing a full re-install would have been my last choice (normally).

I intend to attempt to duplicate the problem on a different system later this weekend. If I learn what was going on, I'll post it here in this thread.

I have no idea how this could affect your desktop environment.After you changed your interfaces file, did you check your network configuration, i mean did it get an IP? To figure this out, Why don't you make the same change you made using the ifconfig command instead of editing the /etc/interfaces file directly and check if your desktop is ok.

This reminds me of a problem i had with Windows many years back. If the network was not configured properly, for instance, if it was configured for DHCP or if it was looking for a domain, and when I logged in, the OS would be searching the network for IP or the domain and wouldn't show the desktop until it gets an IP or whatever. After many tweaks, i removed the network cable and the machine would login without any problem.

This may not be the same in your case, just thought i will share it. Guess you can report this in Launchpad.net

Regards,Avinash

The system was initially configured with a manually set IP during the installation process using a netinst image and wired network connection. I have not installed the proprietary wireless firmware, so the system uses only the wired eth0 connection. As I said, restoring the original interfaces file (or using one with a different manually set IP address / broadcast / gateway / nameservers did nothing to restore proper desktop behavior. I realized that the network interface wasn't going to get all of the data it needed when I tried the experiment. I was just trying to find out just what network-config provided. Apparently, it just uses ifconfig. Anyway, I lost interest in the network settings research when my desktop started having problems. The desktop was still usable, but not conveniently so.

Thanks for your interest. I will probably experiment with this on a more "disposable" system later this weekend to see if I can duplicate the problem and correct it.

]]>Sat, 04 Jul 2009 12:05:28 +0000http://forum.xfce.org/viewtopic.php?pid=18059#p18059http://forum.xfce.org/viewtopic.php?pid=18057#p18057
I do not quite see how a change in networking can have such an effect (unless your home would be on a share which you access via networking). Just one other suggestion should this happen again: the problem appeared to be user related, i.e. other users did not have the problem. A faster work-around probably would have been to delete your own userID, rename /home/username to something else, create a new user with same name, UID and GID and then copy over the userdata from /home/username to your new name]]>Sat, 04 Jul 2009 05:54:06 +0000http://forum.xfce.org/viewtopic.php?pid=18057#p18057http://forum.xfce.org/viewtopic.php?pid=18056#p18056
Hi,

I have no idea how this could affect your desktop environment.After you changed your interfaces file, did you check your network configuration, i mean did it get an IP? To figure this out, Why don't you make the same change you made using the ifconfig command instead of editing the /etc/interfaces file directly and check if your desktop is ok.

This reminds me of a problem i had with Windows many years back. If the network was not configured properly, for instance, if it was configured for DHCP or if it was looking for a domain, and when I logged in, the OS would be searching the network for IP or the domain and wouldn't show the desktop until it gets an IP or whatever. After many tweaks, i removed the network cable and the machine would login without any problem.

This may not be the same in your case, just thought i will share it. Guess you can report this in Launchpad.net

Regards,Avinash

]]>Sat, 04 Jul 2009 02:13:17 +0000http://forum.xfce.org/viewtopic.php?pid=18056#p18056http://forum.xfce.org/viewtopic.php?pid=18050#p18050
I just changed this

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback

I wasn't trying to accomplish anything except to see what would this change would do to the network-config package's ability to control the network configuration of the laptop. I expected (or at least allowed for) adverse effects on network configuration. But putting the original interfaces file back in place did not restore the desktop environment's proper behavior.