LinuxQuestions.org - [SOLVED] Slackware 13 + Gnome gsb2.2. freezes on the screen

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - Slackware 13 + Gnome gsb2.2. freezes on the screen (https://www.linuxquestions.org/questions/linux-general-1/slackware-13-gnome-gsb2-2-freezes-on-the-screen-813387/)

Slackware 13 + Gnome gsb2.2. freezes on the screen

Hello,
Some program's like Adobe Reader, Open Office and some other, when opening them, the screen is not readable (see an attachment )

My hardware is:

Code:



00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

It did not happen on the same hardware with OpenSuse or rhel5 installed

Slackware gives you all the bits, but the rest is up to you. Freezes on startup usually mean libs missing. You often see error messages on stdout (ctrl_alt_f1) Check for missing libs with
ldd /path/to/executable |grep found
ldd shows the shared libs that an executable relies on. the |grep found removes the ones that are there, and just shows the ones that are not.

The font problem may well be not enough fonts installed, something up with fontconfig, or a 32/64 bit issue seeing as you mention Acroread. If you have a 64 bit lib that's no use to a 32 bit program, and vice versa. And the box is rarely obliging enough to tell you, although file will.

business_kid, thanks for reply..

Actually, the problem was started on clean installed of Slackware 13 on my PC with Xfce window manager enabled by default

It's less happened,and visible with GnomeSlackwareBuild installed on it, but the problem is still exist

Quote:

Check for missing libs with
ldd /path/to/executable |grep found

Code:

[test@test.com] # ldd /usr/bin/adobereader 

        not a dynamic executable



[test@test.com] # ldd /opt/openoffice.org3/program/swriter 

        not a dynamic executable

Quote:

Freezes on startup usually mean libs missing. You often see error messages on stdout (ctrl_alt_f1) Check for missing libs with
ldd /path/to/executable |grep found

The program's like adobe, could start with no problem once, but next time you run it again the problem came back, so my guess it's not libs missing issue, furthermore, it could happen sometimes when I drag icons from place to place on my desktop and I can't see them clear and clean... after refresh button (F5)rarely or max/minimize some window it came back clean Not sure this is the problem of

Quote:

The font problem may well be not enough fonts installed, something up with fontconfig, or a 32/64 bit issue seeing as you mention Acroread. If you have a 64 bit lib that's no use to a 32 bit program, and vice versa. And the box is rarely obliging enough to tell you, although file will.

It does't happen with the same hardware (on the same laptop ) with Suse11 of centos 5 installed

I started looking for screen refresh ratio issue, maybe this is the problem..

I have slack and have installed slack-13. The stuff in gnome I would expect to be libs, and they are mentioned on stdout. If you set runlevel 3, the terminal where you start x from is stdout. OO and acroread are nearly certainly a fonts problem.

After upgrade to slackware 13.1, the problem was solved