LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 11-15-2010, 07:42 PM   #61
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 826

Rep: Reputation: 107Reputation: 107

Quote:
Originally Posted by GazL View Post
Reverting isn't the ideal solution. Reconfiguring to get a good result is a better way forward. I've just symlinked "10-no-sub-pixel.conf" into /etc/fonts/conf.d and things already look a little bit more like they used to and closer to my tastes, but it still doesn't look quite as clear as it did before (unless I'm imagining it - hard to say without a side by side comparison).

Not knowing exactly what's changed doesn't help, but I daresay I'll get to something I can live with after some experimentation.
Well, it wasn't a security patch per say, so it is still safe to run. I'm sure that "workarounds" will come out as time goes by on how to get fonts to look the way they used to.

Where did you symlinked 10-no-sub-pixel.conf from? I need to give that a try.
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 11-15-2010, 07:55 PM   #62
GazL
Senior Member
 
Registered: May 2008
Posts: 3,503

Rep: Reputation: 1025Reputation: 1025Reputation: 1025Reputation: 1025Reputation: 1025Reputation: 1025Reputation: 1025Reputation: 1025
It's in the same directory as all the others (/etc/fonts/conf.avail). Do a ls -l /etc/fonts/conf.d and you'll see how they work.
 
Old 11-15-2010, 08:06 PM   #63
zhoun
Member
 
Registered: Oct 2007
Location: anywhere
Distribution: slackware64 current & win7 64 on thinkpad X61
Posts: 104

Rep: Reputation: 18
thanks rworkman,

0. upgrade aaa_elflibs fix it
1. mkdir /lib/udev/devices/shm fix it
2. convert gtk2+ and gdk-pixbuf2 to compat32 package and then upgrade fix it

Quote:
Originally Posted by rworkman View Post
This is broken - that's not the solution. Upgrade aaa_elflibs.



This *is* a bug, and I have no idea how it happened - the build script says it didn't happen, but the package says it did.
In the meantime, do this:
Code:
mkdir /lib/udev/devices/shm
and all will be fine.

You seem to have missed upgrading something - that's not reproducible on a properly upgraded system.



Without more information, I can't say much about this one. I'm obviously skeptical though, given the diagnosis implied by #2.

Last edited by zhoun; 11-15-2010 at 08:30 PM.
 
Old 11-15-2010, 08:07 PM   #64
bg4
LQ Newbie
 
Registered: Jan 2007
Distribution: Slackware -current
Posts: 27

Rep: Reputation: 4
Missing.....

After upgrading -current I have found the desktop effects have been "temporarily disabled". Looking under the "all effects" tab of "configure desktop effects" shows an empty box. It appears the effects are not installed. They were working before the upgrade and this has occurred on two machines - a laptop and a desktop. Otherwise all went well.

Any thoughts?

Thanks, bg4.
 
Old 11-15-2010, 09:10 PM   #65
tpreitzel
Member
 
Registered: Aug 2007
Posts: 253

Rep: Reputation: 28
Upgrade proceeded flawlessly here. Of course, mutt still doesn't work properly which is probably due to changes in configuration options during compilation. I know. Mutt wasn't upgraded in this last upgrade, but the problem still needs fixing. Otherwise, great work! TIA
 
Old 11-15-2010, 10:10 PM   #66
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,520

Rep: Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873
@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.
 
Old 11-15-2010, 10:13 PM   #67
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,272

Original Poster
Rep: Reputation: 186Reputation: 186
Well, it turns out Mesa-7.9 was the source of my problems.
Everything else works just fine with Mesa-7.8.1.

Is it OK to run with this older version?

Many Thanks.
 
Old 11-15-2010, 10:18 PM   #68
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,520

Rep: Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873
Quote:
Well, it turns out Mesa-7.9 was the source of my problems.
Everything else works just fine with Mesa-7.8.1.

Is it OK to run with this older version?
Have a look at post #38 in this thread.
 
Old 11-15-2010, 10:59 PM   #69
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,272

Original Poster
Rep: Reputation: 186Reputation: 186
Quote:
Originally Posted by allend View Post
Have a look at post #38 in this thread.
Yes, I saw that and Alien Bob said,
Quote:
Try without xorg.conf first. Slackware's X.Org does not need one.

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/
For some Ati and Nvidia cards (using the opensource drivers) the slightly older version mesa package may just work.

If that package works for you, please report it here!

Eric
It would seem, but maybe I'm wrong, that he was talking about the 7.8.2 version, not 7.8.1.
Regardless, consider it "reported" that the 7.8.1 version of Mesa works fine.
 
Old 11-15-2010, 11:52 PM   #70
Erik_FL
Member
 
Registered: Sep 2005
Location: Boynton Beach, FL
Distribution: Slackware
Posts: 801

Rep: Reputation: 247Reputation: 247Reputation: 247
I usually don't install "current" but KDE has been a problem for me. I could have installed KDE 3.5.1 on top of Slackware 13.1 but I'd rather take my chances with "current". I have a lot more confidence in the Slackware maintainers than KDE or myself. I also ran into the problem with "liblzma" but I consider it a minor problem. I will say that Slackware is looking very good. Considering the rate that KDE changes that speaks of a lot of care and effort.

Of course everyone would like another release of Slackware soon. I prefer to encourage rather than complain. I wish I had more to contribute besides my encouragement and helping an occasional Slackware user with a question that I can answer.

I think that Slackware 13.1 was a good release that suffered from being done at a time when many packages were still undergoing some growing pains. That makes it even more important for 13.2 to be released when it is ready, and not before. I will be perfectly happy if 13.2 uses KDE 4.5 instead of 4.6. I use Slackware because I want stability, not bleeding edge software.

It's nice that Slackware "current" is available and from what I've seen people get plenty of help with problems even if they have "current". Expecting "current" to always install and run with no effort is unreasonable. The obvious solution to difficult problems is to wait a while and then update again with the current "current". Someone who needs an always working system is probably better off to stick to official releases, fix whatever problems are there and then leave it alone. That's what I have done in the past and will probably do most of the time in the future.
 
3 members found this post helpful.
Old 11-16-2010, 12:56 AM   #71
grissiom
Member
 
Registered: Apr 2008
Location: China, Beijing
Distribution: Slackware
Posts: 423

Rep: Reputation: 45
Quote:
Originally Posted by rworkman View Post
Maybe I'm misunderstanding what you wrote, but aaa_elflibs should *always* be upgraded when one goes from e.g. Slackware 13.0 to 13.1. The "never upgrade or reinstall this package" is intended for those tracking a stable release (e.g. 13.1) in /patches -- it should never be reinstalled in those circumstances.

When 13.2 (assuming it is 13.2) is released, everyone should certainly upgrade the aaa_elflibs package along with the rest, because if they don't, they will be missing libtalloc.so (for example) if they try to run without installing the samba package.
Yes, I'm agree with RW. Now I have a better understanding of aaa_elflibs pkg. Maybe we should state that clearly in slack-desc and CHANGES_AND_HINTS.TXT?

Because you expect -current trackers to "fix bugs by their own", I think it's up to ourself to un-blacklist aaa_elflibs in slackpkg
 
Old 11-16-2010, 01:57 AM   #72
trxdraxon
Member
 
Registered: Jan 2006
Location: Command Line
Distribution: Slackware
Posts: 68
Blog Entries: 1

Rep: Reputation: 7
Thanks to everyone in this thread and the information provided. Made my my upgrade today pretty painless
 
Old 11-16-2010, 03:26 AM   #73
smoooth103
Member
 
Registered: Aug 2009
Location: NC, USA
Distribution: Slackware (64 bit)
Posts: 238

Rep: Reputation: 60
I upgraded to -current (32-bit) today and everything went smoothly with the tips from this thread. Had to download and rebuild a new version of the nvidia drivers and finally create a new symbolic link for liblzma.so.0 and everything works great now. I've noticed some subtle performance improvements in the new version of X already. Thanks everyone.

Last edited by smoooth103; 11-16-2010 at 03:28 AM.
 
Old 11-16-2010, 03:53 AM   #74
cgorac
Member
 
Registered: Oct 2009
Posts: 48

Rep: Reputation: 4
Quote:
Originally Posted by rworkman View Post
You seem to have missed upgrading something - that's not reproducible on a properly upgraded system.
That was about libgdk_pixbuf error - I had the same error reported on properly upgraded system, and the solution here was just to run ld-config.
 
Old 11-16-2010, 04:07 AM   #75
cgorac
Member
 
Registered: Oct 2009
Posts: 48

Rep: Reputation: 4
Quote:
Originally Posted by volkerdi View Post
Wait, you're upset that we didn't "release early and release often", but you're also whining about the remaining bugs? Please, make up your mind.
I'm not whining about the bugs. Most of the stuff mentioned above, and obviously all of the stuff mentioned in my post, are issues with upstream: BlueZ is known to be crap, breaking things with each new release, and also I really cannot understand how it could be possible, after so many years, to have FreeType to completely change text rendering all of a sudden. But unfortunately we don't have an alternative Bluetooth stack or an alternative FreeType rendering library, so we'll have to live with this... However that doesn't change my complaints about Slackware update policy in recent times: for example, Slackware 13.1 came with FreeType 2.3.12, and there were 2.4.0, 2.4.1 and 2.4.2 releases in the meantime, and you just decided to come up now with 2.4.3 updated, buried in this huge pile of other updates. And now there are suggestions to go back to 2.3.12 for those who don't like new rendering of fonts, implying that nothing in -current actually depends on FreeType 2.4.x. So I really can't understand why it was not possible then for example to release updated FreeType in some small batch of updates previously - this way, I would be probably able to find what caused the issue much quicker, as I'd have to check change logs of dozen of packages, instead of thousands in this case.
 
0 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Latest current problems brodo Slackware 17 03-03-2010 11:14 AM
Latest current ? brodo Slackware 34 03-13-2009 04:15 PM
Latest nmap (4.50) in current and its gui jazzor Slackware 30 05-16-2008 01:22 PM
Race condition in /etc/rc.d/ with latest -current ? Yalla-One Slackware 1 08-06-2006 03:23 PM
warning about latest current aaa_elflibs-10.1.0 xushi Slackware 2 01-25-2005 08:57 AM


All times are GMT -5. The time now is 11:43 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration