Installed The Latest Changes to Current and......

Daedra · 11-16-2010, 03:12 AM

For one thing this might have a hand in the font rendering... from freetype.org

Since May 2010, all patents related to bytecode hinting have expired worldwide. It it thus no longer necessary to disable the bytecode interpreter, and starting with FreeType version 2.4, it is enabled by default.

Have you seen this thread
http://www.linuxquestions.org/questi...68/page12.html

Check the last few post, there are tweaks to make your fonts look very nice.

hiptobecubic · 11-16-2010, 03:37 AM

Quote:

Originally Posted by stormtracknole

FYI, if for whatever reason you don't like the new fonts or how they are being rendered, reverting freetype to the previous installed version (2.3.12) will restore them to their previous state.

I knew it had to do with the font rendering and not the fonts themselves. It didn't make sense. I'm worried now though. Why have they changed the fonts we all know and love? Who knows what's next!?

edit: Didn't see previous post. I suppose this is a "good" thing then? I guess I'll have to recompile with this 'feature' off.

Daedra · 11-16-2010, 04:10 AM

Can you post a screenshot of your desktop, I'm curious to see what your fonts look like? And you shouldn't have to recompile you can tell fontconfig to just use the autohinter.

kiroff · 11-16-2010, 04:13 AM

Quote:

Originally Posted by gbschenkel

Eric, it work, i have downgrade the mesa from 7.9 to 7.8.2 and my X.Org start work again. Thanks very much.

And about my last post, i know the Slackware's X.Org don't use anymore xorg.conf, i think since was integrated hal on it. Like i said previous in the other post(in page 2), i just try put it work again to check if i try force use vesa, it work again! But i think you know, it don't work.

Well like i said before, thank you very much, and thank you Patrick to upload the mesa-7.8.2 package, maybe it can be put on /pasture on the next update

Did the trick for me as well (unfortunately by disabling the compositing), thanks for the tips.

4Strings · 11-16-2010, 06:04 AM

Quote:

Originally Posted by Alien Bob

...
What you should also try is to replace the mesa-7.9 package from slackware-current with the mesa-7.8.2 package which was uploaded here today by Pat Volkerding: http://slackware.osuosl.org/unsupported/mesa-7.8.2/...

Hi! me too!

After the upgrade, I've had to downgrade to "mesa-7.8.2" in order to successfully launch the X session again!
Before the downgrade I've experienced the segmentation fault issue on launching the X server (...and disabling "Compositing" had no effect!).

My video card is an "Ati X1400" on a "Dell Inspiron 6400" - driver "radeon" opensource.

4Strings · 11-16-2010, 06:17 AM

Quote:

Originally Posted by LJSBrokken

After upgrade to current I lost the scroll function of my synaptics touchpad (Thinkpad T41). To fix it:

Code:

cp /usr/share/X11/xorg.conf.d/50-synaptics.conf /etc/X11/xorg.conf.d/

and edit /etc/X11/xorg.conf.d/50-synaptics.conf to suit your wishes. I added

Code:

        Option "VertEdgeScroll" "on"
        Option "HorizEdgeScroll" "on"

and all is well again

...

Before the upgrade I used the two "hal" configuration files ("10-keymap.fdi" and "x11-synaptics.fdi" in "/etc/hal/fdi/policy/") in order to setup the Synaptic touchpad and the keybord map.
But, after the upgrade, these two configuration files seems to have no more effect!

So, according to LJSBrokken (thanks!

), I had to copy the two files "50-synaptics.conf" and "90-keyboard-layout.conf" from the directory "/usr/share/X11/xorg.conf.d/" to the "/etc/X11/xorg.conf.d/, and edit them properly!

the_penguinator · 11-16-2010, 06:19 AM

Quote:

Originally Posted by rworkman

You did it wrong. Upgrade the aaa_elflibs package properly *after* you "unfix" what you just broke by renaming.

thanks Robby...funny...breaking it made it work, but yeah after commenting aaa_elflibs in /etc/slackpkg/blacklist, I upgraded and all is "as it should be"

this is enjoyable
BTW, this box -and I would recommend it to anyone- looking for a cheap -current testing machine is an IBM R51 laptop model 1836-XXU, this has been running current for two years now with only two minor hiccups related to X that needed sorting out. And I use it as my daily work/home machine.
Cheers

cwizardone · 11-16-2010, 10:06 AM

A correction to my earlier post regarding mesa.

I should have said everything runs fine in Xfce with mesa 7.8.1. However, KDE 4.5.3 will not run. KDE fires up,
but immediately reports a knotify error and crashes back to the command line.
After upgrading to mesa 7.8.2, KDE still crashed, but Xfce continued to run fine.

Also, VirtualBox has ceased to run regardless of which version of mesa is installed.

2handband · 11-16-2010, 10:13 AM

I still don't have X. KDE seems to start and then crashes with the following error:

Code:

Caught signal 11 (segmentation fault). Server aborting.

tomtomjkw · 11-16-2010, 10:29 AM

cwizardone ->

I had similar error during fresh current install about two weeks ago. KDE splash screen loaded its icons and then reverted to kdm login. Not sure, but it might have been something sql related.
Had also the issue with Virtualbox - it only started as root. Downloading new installer (3.2.10.66896) solved the problem.

cwizardone · 11-16-2010, 12:04 PM

Quote:

Originally Posted by tomtomjkw

cwizardone ->

I had similar error during fresh current install about two weeks ago. KDE splash screen loaded its icons and then reverted to kdm login. Not sure, but it might have been something sql related.
Had also the issue with Virtualbox - it only started as root. Downloading new installer (3.2.10.66896) solved the problem.

I un-installed VB, downloaded the latest version, installed it and all is well with VB and Xfce.

KDE 4.5.3, still won't run with the latest current files. Well, as I said earlier, it starts and then crashes back to the command line. No great loss.

Erik_FL · 11-16-2010, 12:54 PM

Thanks for the VirtualBox solution. I downloaded the Linux files just after the 3.2.10 release and I didn't know that there was a newer 3.2.10 for Linux.

I am occasionally seeing KDE return to the logon dialog after I log in. If I log in again then it brings me to the desktop. It's a minor issue and the things that I really want are working great.

bg4 · 11-16-2010, 02:35 PM

Quote:

Originally Posted by allend

@bg4 - I have found that KDE 4.5.1 has an entry "OpenGLIsUnsafe=false" (in ~/.kde/share/config/kwinrc under [Compositing] ). If this is set to "true" then the Desktop effects tab under System Settings -> Display is empty of entries.
By design, KDE checks for support for compositing and after two attempts it will give up and mark the lack of support.

allend, thank you for the feedback. I suppose my next question is why now after the upgrade does KDE think OpenGLIsUnsafe should set to true when prior to the upgrade it wasn't and all worked fine. I haven't had time to chase that yet but hope to over the weekend. It is interesting that it happened on two different machines with different hardware.

Also, I must say thank you to all on this forum. Many questions have been answered just by a bit of reading. Cheers, bg4.

coralfang · 11-16-2010, 02:49 PM

Commented aaa_elflibs in /etc/slackpkg/blacklist followed by:

Code:

slackpkg upgrade-all

which upgraded the one new package

Now i have another problem with anything gtk2 related:

Code:

/usr/lib64/firefox-3.6.12/firefox-bin: symbol lookup error: /usr/lib64/libgio-2.0.so.0: undefined symbol: g_variant_unref

Whats happened now o.o

volkerdi · 11-16-2010, 03:00 PM

I had issues testing the upgrade here with slackpkg, where a couple of packages (pango, for example) were skipped because the checksums on the mirror I chose did not match. I ran upgradepkg --install-new on all the -current packages and it fixed it right up. I would run the usual sequence given in the slackpkg man page again and watch to see if it says that any packages are being skipped. If so, upgradepkg --install-new those manually.