Re: 'Applications -> Preferences -> Font' not working.

[Adam Bogacki]

See below.

Tux:~# gnome-font-properties
gnome-font-properties: error while loading shared libraries: libmetacity-private.so.0: cannot open shared object file: No such file or directory
Tux:~# gnome-sound-properties
gnome-sound-properties: error while loading shared libraries: libmetacity-private.so.0: cannot open shared object file: No such file or directory
Tux:~# gnome-theme-properties
bash: gnome-theme-properties: command not found
Tux:~# find -name gnome-theme-manager -print
Tux:~# cd /
Tux:/# find -name gnome-theme-manager -print
./usr/bin/gnome-theme-manager
find: ./proc/3746/task: No such file or directory
find: ./proc/4633/task: No such file or directory
Tux:/#

Also, in trying mplayer (working yesterday) I now get

alsa-init: requested format: 16000 Hz, 2 channels, Signed 16-bit (Little-Endian)alsa-init: no soundcards found: Success
AO: [arts] loading the aRts backend "/usr/lib/libartscbackend.la" failed
AO: [esd] esd_open_sound failed: No such file or directory

... possibly unrelated.

I might try 'apt-get remove metacity' and switch to testing
(I usually find it a bit boring ...)

Adam Bogacki,
[EMAIL PROTECTED]

Michael Banck wrote:

On Wed, May 19, 2004 at 08:10:25PM +1200, Adam Bogacki wrote:
  

When I click 'Applications->Desktop Preferences->Font' on the top left 
of the top panel a small square appears on the bottom left of the
bottom panel saying

'Aa Starting Font'

... sits there for a while ... then disappears. Previously a font config 
panel would open up in the center of the screen allowing me to adjust
font size and/or select another font.
    

Try running gnome-font-properties in a GNOME terminal and see whether
you get some error messages you can relate to us.
 
  

The same occurs for 'Applications->Desktop Preferences->Themes' and
'Applications->Desktop Preferences-> Sound'. The last is not so
important since the ALSA sound modules in 2.6.5 kicked in.
    

That would be gnome-theme-manager and gnome-sound-properties.
 
  

I recently did a number of 'apt-get dist-upgrade --fix-missing" [...]
        

Were any packages inadvertently removed by the "apt-get dist-upgrade"?

      

Not that I am aware of.

    

Was there a reason you were performing the dist-upgrade?

      

I had upgraded to kernel 2.6.5 but on second dist-upgrade I could not
get past a 'Kernel Panic'. I got past this via mkinitrd and tried to fix
any problems via 'apt-get dist-upgrade --fix-missing'.
    

You should not run dist-upgrade in general, that can lead to bad
effects. Run apt-get upgrade all the time and if packages are being kept
back, run apt-get dist-upgrade afterwards and have a close look at what
APT wants to do.

What Debian distribution are you running anyway? testing?


Michael