Re: Sawfish screwed up after upgrade
Have you installed the sawfish-gnome package? Andrew Sione Taumoefolau [EMAIL PROTECTED] http://users.pipeline.com.au/tonga/ - Original Message - From: Larry Elmore [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Tuesday, April 17, 2001 2:39 PM Subject: Sawfish screwed up after upgrade After upgrading to 'Unstable', Sawfish reverted to default settings and any attempt to use the Gnome Control Center to change those settings results in the Gnome Control Center being locked up. Has anyone else had a problem like this? I've tried purging all packages that might be related to this problem, then deleting all directories and files still left behind by those packages, then reinstalling the packages. No luck. Any ideas? Larry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sawfish screwed up after upgrade
On Mon, Apr 16, 2001 at 11:39:48PM -0500, Larry Elmore wrote: After upgrading to 'Unstable', Sawfish reverted to default settings and any attempt to use the Gnome Control Center to change those settings results in the Gnome Control Center being locked up. Has anyone else had a problem like this? I've tried purging all packages that might be related to this problem, then deleting all directories and files still left behind by those packages, then reinstalling the packages. No luck. Any ideas? I experienced these symptoms when I upgraded from potato+ximian to unstable. librep was the problem IIRC. I solved the problem by getting rid of all the ximian stuff. No problems since then. -- Nathan Norman - Staff Engineer | A good plan today is better Micromuse Ltd. | than a perfect plan tomorrow. mailto:[EMAIL PROTECTED] | -- Patton pgpjVnSV6Mf7l.pgp Description: PGP signature
Sawfish screwed up after upgrade
After upgrading to 'Unstable', Sawfish reverted to default settings and any attempt to use the Gnome Control Center to change those settings results in the Gnome Control Center being locked up. Has anyone else had a problem like this? I've tried purging all packages that might be related to this problem, then deleting all directories and files still left behind by those packages, then reinstalling the packages. No luck. Any ideas? Larry
