LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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-16-2010, 03:51 PM   #91
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 299

Rep: Reputation: 80

Quote:
Originally Posted by volkerdi View Post
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.
If i remember correctly i received a few warnings about checksums when i upgraded. I think i'll start over with 13.1 (ive broken a few things since) then try upgrading that way. Cheers.

EDIT: Scrap that, i just reinstalled aaa_elflibs again, rebooted and now everything works!
That's why i love slackware.

Last edited by coralfang; 11-16-2010 at 04:34 PM.
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 11-16-2010, 04:04 PM   #92
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 490
Blog Entries: 1

Rep: Reputation: 55
Well, according to all the entries in this thread, I must be in the minority here. I upgraded yesterday & have had no problems on either my desktop or laptop. I do keep to the shallow end of the pool, never use either slackpkg or KDE's desktop effects.
Regards,
Bill
 
Old 11-16-2010, 04:11 PM   #93
BobNutfield
Senior Member
 
Registered: Dec 2005
Location: United Kingdom
Distribution: Fedora , Ubuntu, Slackware-Current
Posts: 1,477

Rep: Reputation: 51
I don't seem to have any errors in /var/log/Xorg.0.log, but X will not start. I get the same SEGMENTATION FAULT Caught signal 11. server aborting as is mentioned in this thread. this line is just after /lib/lib.so.6.

Am I looking at a reinstall? I read alien Bob's blog, but nothing seems to address this. can anyone offer any ideas of what I can try?

Thanks for any replies

Bob
 
Old 11-16-2010, 05:03 PM   #94
devnull10
Member
 
Registered: Jan 2010
Location: Lancashire
Distribution: Slackware Stable
Posts: 547

Rep: Reputation: 115Reputation: 115
This upgrade also crashed X for me - complaining of NVidia drive error. I just changed nvidia to nv in xorg.conf though and whilst it has got me into X, I don't have 3d acceleration.

[edit]

After re-installing NVidia drivers I now have 3D acceleration.

Last edited by devnull10; 11-16-2010 at 05:12 PM.
 
Old 11-16-2010, 06:14 PM   #95
BroX
Member
 
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current
Posts: 752

Rep: Reputation: 64
Quote:
Originally Posted by LJSBrokken View Post
After update, on 64bit KDE throws me back to the KDM login screen when restoring a minimized app (and sometimes by other causes, seemingly at random).
...
Enabling KMS solved it
 
Old 11-16-2010, 06:53 PM   #96
slackass
Member
 
Registered: Apr 2006
Location: SE Texas
Distribution: Slack64-C ML
Posts: 886

Rep: Reputation: 78
The only thing that broke on mine was inkscape, but that was easy to fix.
Smooth upgrade
Thanks Pat, Robby, & the gang

Slack64-C
Multi-Lib
KDE 4.5.3
 
Old 11-16-2010, 08:17 PM   #97
akiku
Member
 
Registered: Jun 2009
Distribution: Slackware
Posts: 62

Rep: Reputation: 17
I did all the recommended fixes, disable/enable compositing, aaa_elflibs upgrade, and the mesa downgrade to 7.8.2. My X is still hosed, segfault on start-up.
My laptop has the Radeon IGMP340M chipset and all the -current upgrades (except the glibc stuff)
What else can I try?
 
Old 11-16-2010, 09:03 PM   #98
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 433

Rep: Reputation: 30
Great update! I did the update (Sun Nov 14 23:58:42 UTC 2010) and has not i did the update "Tue Nov 16 23:38:13 UTC 2010," I do this last tomorrow ...
For now all I use is working.

Thanks for Slackers Very Good ! :-)
 
Old 11-17-2010, 01:43 AM   #99
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,316

Rep: Reputation: Disabled
Quote:
Originally Posted by akiku View Post
all the -current upgrades (except the glibc stuff
You need to upgrade fully, including glibc.
If you are running a multilib Slackware64 then the version of your multilib glibc packages must match that of the slackware64-current packages.

Eric
 
Old 11-17-2010, 07:54 AM   #100
akiku
Member
 
Registered: Jun 2009
Distribution: Slackware
Posts: 62

Rep: Reputation: 17
Quote:
Originally Posted by Alien Bob View Post
You need to upgrade fully, including glibc.
If you are running a multilib Slackware64 then the version of your multilib glibc packages must match that of the slackware64-current packages.

Eric
When the glibc updates came out, I did let slapt-get do the upgrade, but it left the machine unusable. So I downgraded it using Robbie W.'s instructions.
Do I need to upgrade manually in a particular order?

I am not using slackware64, btw.
 
Old 11-17-2010, 10:31 AM   #101
foodown
Member
 
Registered: Jun 2009
Location: Texas
Distribution: Slackware
Posts: 609

Rep: Reputation: 218Reputation: 218Reputation: 218
Quote:
Originally Posted by cgorac View Post
... 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.
<SARCASM>

Geez, I know . . . The nerve of Pat to not pace the progression of the unstable branch of his distro more to your tastes. I can't believe that guy. Doesn't he know that his stable releases aren't good enough for you and that you have to run -current?

</SARCASM>
 
1 members found this post helpful.
Old 11-17-2010, 11:20 AM   #102
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,238

Original Poster
Rep: Reputation: 176Reputation: 176
I installed the 16 November upgrades and additions this morning, but it changed nothing.
KDE still crashes shortly after launching.
Xfce still runs fine.
 
Old 11-17-2010, 11:33 AM   #103
Erik_FL
Member
 
Registered: Sep 2005
Location: Boynton Beach, FL
Distribution: Slackware
Posts: 799

Rep: Reputation: 247Reputation: 247Reputation: 247
Quote:
Originally Posted by cwizardone View Post
I installed the 16 November upgrades and additions this morning, but it changed nothing.
KDE still crashes shortly after launching.
Xfce still runs fine.
I noticed that you mentioned KDE 4.5.3. The version that I am using, installed from "current" is KDE 4.5.1. Did you update from the KDE site, or has "current" moved up to KDE 4.5.3?

If you want to investigate your KDE crashes further, I have two suggestions that might shed some light on the problem. Create a new, virgin account and then try to start up KDE from that. KDE sometimes has problems with files created by older versions of KDE. Test with a non-proprietary graphics driver that is part of the distro. For example, use the VESA driver. If that stops KDE from crashing then the problem may actually be the graphics driver.

I use XFCE 4 quite a lot and one can even run the KDE programs from XFCE 4. The only thing that I have trouble with in XFCE 4 is accessing network folders. That's probably because I don't know how rather than an actual limitation of THUNAR (sp?).
 
Old 11-17-2010, 12:23 PM   #104
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,238

Original Poster
Rep: Reputation: 176Reputation: 176
[QUOTE=Erik_FL;4162067]I noticed that you mentioned KDE 4.5.3. The version that I am using, installed from "current" is KDE 4.5.1. Did you update from the KDE site, or has "current" moved up to KDE 4.5.3?/QUOTE]

4.5.3 is available courtesy of Alien Bob at,

http://alien.slackbook.org/blog/i-po...-5-3-packages/

Quote:
Originally Posted by Erik_FL View Post
If you want to investigate your KDE crashes further, I have two suggestions that might shed some light on the problem....
Thanks for the suggestions, but the KDE programs I like and use run just
fine in Xfce so there is little to no need to run KDE itself and all the
bloat that comes with it.
 
Old 11-17-2010, 01:06 PM   #105
merciful
LQ Newbie
 
Registered: Jun 2006
Distribution: Slackware 13.1 / GSB / Compiz | Slackware 12.1 KDE
Posts: 15

Rep: Reputation: 0
Quote:
Originally Posted by cwizardone View Post
Thanks for the suggestions, but the KDE programs I like and use run just
fine in Xfce so there is little to no need to run KDE itself and all the
bloat that comes with it.
That is the only reason I have KDE installed. Some apps I use will run with other desktops.

Today I tried to sync my Slackware-current. Well...that did not go as it should. My installation was until today a Slackware-current with Gsb-current. A very nice system to work with.

The upgrade done with slapt-get went all okay. Of cource the aaa_elflibs were not installed, so a view of my (kde) apps stopped working. And...the screen fonts were changed :-( . I didn't like this, but sometimes things are as they are.

Upgrading the aaa_elflib like Alien Bob mentioned had as result that the Xserver got broken. Hmmm, I did not upgrade the gtk+2 and glibc packages. Upgrading these would solve the broken Xserver, but will most likely break my gsb setup.

So I downgraded to 13.1 and got every thing working (again). my conclusion: Slackware-current & Gsb-current can not be installed together. I really regret this, because I really like to run current.

NB: I upgraded from kde 3.5 to kde4, but really don't like it so I switched to gsb.
 
  


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 10:14 AM
Latest current ? brodo Slackware 34 03-13-2009 03:15 PM
Latest nmap (4.50) in current and its gui jazzor Slackware 30 05-16-2008 12:22 PM
Race condition in /etc/rc.d/ with latest -current ? Yalla-One Slackware 1 08-06-2006 02:23 PM
warning about latest current aaa_elflibs-10.1.0 xushi Slackware 2 01-25-2005 07:57 AM


All times are GMT -5. The time now is 02:28 PM.

Main Menu
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