LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Anyone else having to go back to 14.0? (http://www.linuxquestions.org/questions/slackware-14/anyone-else-having-to-go-back-to-14-0-a-4175486497/)

enine 12-01-2013 08:41 PM

Anyone else having to go back to 14.0?
 
Sorry to sound ranty but I keep running into problem after problem with 14.1.

First issue was .jpg's will start displaying as just a black box. If I quit X and startx again I can then view jpg's fine for a few days.

Second was loosing half the features of my printer so I had to remove the hlip package and go back to the one from 14.0

Now sane can't use my scanner even though its there so I need to roll it back to the 14.0 version.

Granted there are not Slackware's fault but why does software have to loose features going to new versions.

hitest 12-01-2013 09:07 PM

Sorry to hear about your issues. Slackware 14.1 is running well on 3 boxes and slackware-current on another box. All is well here.

frankbell 12-01-2013 09:15 PM

I'm on Current and I have encountered no issues, and I've frequently edited and viewed image files of various formats and used my HP all-in-one to scan documents with xsane.

tux_dude 12-01-2013 09:18 PM

What features did you loose? Did you install all the required packages? How are you viewing jpegs? Did you download the required plugins for hplip? If you also have a HP scanner, sane will require the correct plugins to function. Other than local time being screwed up by the upstream kernel group, 14.1 is humming along fine.

irgunII 12-01-2013 09:30 PM

I just had a need to use the scanner of my all-in-one printer tonight. The printer 'prints' just fine, but skanlite and xsane both segfault on me every time I try to scan. It gets started just fine, but about the middle of the scan the apps fail and I have no sanned image.

This along with a few other problems I have posted about are making me go back to 14.0 tonight also. I hate to do it, but 14.1 just doesn't seem to be doing as well *for me* as 14.0 did.

smoooth103 12-01-2013 09:30 PM

I'm on current as well, no issues here. Not a single one.

angryfirelord 12-01-2013 09:47 PM

Remember that Slackware is essentially just upstream packaged up for you, so if you're encountering a problem with a package, it might be worth to see if the program has any outstanding bug reports for that version.

STDOUBT 12-01-2013 11:13 PM

Still on 14.0 here because of lazy, but I'm curious if you guys who are "not having problems"
are able to use the same programs as enine?

enine, you really should better describe your setup; which DE/WM are you using, what application
do you use to view jpegs, did you do a Full Install, etc...
I had a lot of hair-pulling moments going from 13.37 to 14.0, but it turned out all of the problems
were easily solveable. That may be the case for you if you just investigate further.

narz 12-01-2013 11:37 PM

I'm good with 14.1 so far but it seems like one of the more conservative releases since I last remember. Doesn't seem like much was really changed, added or removed (even by Slackware standards). Everything is just a tad newer.

Drakeo 12-02-2013 02:18 AM

Quote:

First issue was .jpg's will start displaying as just a black box. If I quit X and startx again I can then view jpg's fine for a few days.
had this issue with 13.37 fix was broken links in xorg when installing nvidia driver . reinstalled my ap, l,x,xap blacklisted nouveau. then reinstalled nvidia. when not using kwin 3d desk top would cause this. but that fixed the problem.

as for the sane it seems to work fine but your scanner side is not functional. Since your not new to here you should know to give us model and make That would be helpful to other members so we can work on the said issue. I have and older HP c4200 printer+flatbed scanner it works. I will say in 14.0 that wasn't till I rebuilt HP program to a newer version
did I get hp to work at all.

bartgymnast 12-02-2013 03:27 AM

People, I think some of you started to experience the know issue of (latest OS on oldest PC problem)

for example, Boost newest libraries wont work on i386 anymore
newest kernel does not support pre 2000 power options (non ACPI), think its called PMI

If you have an old system, stick with an OS that works, and only update packages with bug fixes
slack 14.0 has a kernel 3.2 which has a pretty long life.
things that come in newer kernel is 99% of the time, things you wont need anyway.

flyingv2 12-02-2013 08:28 AM

Cannot install catalyst 13.1 legacy driver on 14.1 -> Rdesktop is painfully slow with opensource radeon driver.

arubin 12-02-2013 09:25 AM

It took me all day yesterday to get wine working with SilkyPix on 14.1 and was on the point of rolling back in frustration.

Much of the problem was of my own making. I could have sworn I had multiib fully installed but didn't. And on the umpteenth try SilkyPix ran. I still don't know what I did that made the difference.

But the combination of wine and SilkyPix is unsupported and I suppose I should count myself lucky that it does work.

dive 12-02-2013 11:20 AM

Quote:

Originally Posted by arubin (Post 5073929)
But the combination of wine and SilkyPix is unsupported and I suppose I should count myself lucky that it does work.

You might want to look at darktable. Requires no wine. I've been using it for a couple of weeks now and love it.

http://slackbuilds.org/repository/14...ics/darktable/

Woodsman 12-02-2013 01:08 PM

Quote:

People, I think some of you started to experience the know issue of (latest OS on oldest PC problem)
There has been a long standing claim that Linux based systems are good for reviving old hardware. I have a PI and a PII. I updated those systems regularly when I updated my primary systems. Both now run Slackware 14.0 and both are horribly sluggish. Through the years I noticed both systems getting slower with each update.

This is not a rap against Slackware, which I have used for 10 years. Only a rebuttable against the claim.

Those two computers seem to have run best around the Slackware 12.1 and 12.2 era. That seems to be the turning point at which the claim turned into a fallacy. I'm half tempted to return those old systems to 12.2 (which I always thought was one of the best Slackware releases ever :)). 12.1/12.2 are reaching EOL, but I use the two computers only for hobbyist reasons anyway.


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