Upgrade oddities

[mdlbear]

Solved a mysterious networking problem at work this morning by replacing a copy of Debian Etch that had been upgraded from Sarge, with a clean install. (Well, actually a copy, via tar, of a clean install.) Nothing I can really put my finger on, but it seems as though there are still some bugs in the Sarge-to-Etch upgrade. Not surprising; Etch hasn't been released yet. But it leads me to suspect even more strongly that my fileserver crash problems here at home may be the same kind of thing. Possibbly some kind of hardware-detection thing.

The new disk will give me the excuse; now I just need the time. There may be some time in the late afternoon Thursday and Friday depending on how long cleanup and setup for next week's shindig take; between work and Consonance, next week is totally shot.

Comments

[autographedcat.livejournal.com]

Digressing slightly, do you happen to know what might be causing the resource leak in Xorg in the current version of Ubuntu? I keep having to reset the computer because X performance gets sluggish, and top shows the only thing really consuming abnormal amounts of resources is Xorg itself.

[mdlbear]

Memory leaks in X are nothing new, but it's more likely that you have an application with a resource leak. Look for an application that sticks around and uses lots of X resources like fonts and offscreen pixmaps. My inclination would be to suspect a web browser, but there are plenty of likely culprits in Gnome.

If logging out and back in fixes it, you definitely have a resource leak -- X is supposed to release all resources when the last client quits. Otherwise try killing X with ctrl-alt-backspace. It shouldn't be necessary to reset the computer.

[autographedcat.livejournal.com]

Nod. I only just discovered the command xrestop, so next time it gets bogged down I'll try and use that to see what's going on. I was just curious if there was some known bug that everyone but me knew about. :)

[mdlbear]

Cool! My top resource hog is Firefox, which doesn't surprise me at all.

[autographedcat.livejournal.com]

Btw, Over the weekend my resource problem cropped up again, and I was able to catch it using xrestop:

https://launchpad.net/ubuntu/+source/vino/+bug/31037

A "killall vino-server" freed up the cpu and restored non-sluggish behaviour to my WM.