unstable system after using slackpkg current
 

I did a fresh install of slackware 14.2 and decided to try the current branch, i have been experiencing some issues that i can not fix on my own, some of the issues are
1. The day before yesterday i ran a virus scan in the morning it took 45 min, yesterday i ran the same scan but it hadnt finish after 5hrs so i had to cancel it
2. I received a message that irq19 had been disabled or shutdown, i found out that irq is tied to my network card, all i did was change from network manager to dchp and it seems tofix the issue
3. Yesterday when i was trying to shutdown my conputer thru xfce it took maybe 2 mintues to display the different logout options and then got an error message, see picture
4. Have more than once been unable to iniciate xfce
5. When ever i run under root netconfig, mkinit generator, etc the windows appera like my picture

I pretty sure all of this issues have occured after using the current branch updates, unless my computer has been compromised which in either case i really dont know were to start, i have looked at the syslog but honestly dont know what to mAke of it. I'm not to sure if it my ssd, its not even a year old, any help would be appreciated. I was wondering if maybe by any chance someone locally could help me

How did you perform upgrade on your machine?
Did you install the new packages and merge all new configs?

Note that current is now set to use UTF-8

if you are planning to use -current, probably it's better to use -current ISO generated by AlienBOB
see here: http://bear.alienbase.nl/mirrors/sla...4-current-iso/

Also, did you update 14.2 before moving to --Current?

I downloaded 14.2 from the slackware website and that is what i used for the installation. After i had completed the installtion I logged in as root, changed the etc/slackpkg/mirrors and uncommented one current mirror that was closest to my location, i use slackpkg as my upgrade manager, i was given a handful of updates but i only did the kernel updates first, then I ran lilo with the appropriate lines, rebooted my machine and completed the rest of the remaing updates. As for the utf-8 i dont remember what i set it to do i find that setting maybe in lilo?
One quick question i have is in previous installs what i have done before checking for updates is create a non-root use then use SU to run all the commands but this time i logged in as root is that an issue?


To answer frankbell question: i would say no based on my respond to willsyr

No, it doesn't make any difference in terms of creating users for performing updates.
It does make difference if you are running normal users on daily activities

Did you run these 2 commands on your upgrade procedure?
UTF-8 is set in /etc/profile.d/lang.sh

I remember runing the first one for sure, the second one i think i did but i cant remember can i still run it?

yes, you still do it now
basically it just removed packages no longer included in the -current, although i don't think it has any effect on your stability.

From the utf-8 profile i only have the following lines omitted
Export LANG=en_US.UTF-8
Export LC_COLLATE=C

For the install-new command it installed
- gcc.brig-7-1.0......
- lame-3.99.5.......
- urw-core35-fonts.....

For the clean-system command it removed maybe 80 applications

If you don't think the clean-system command might fix the stability is there something else i should try?

I would go with a fresh -current ISO generated by AlienBOB i mentioned on my first reply

Fair enough but can explain in more detaill why em i experiencing this weird behaviour? Or why you think using AlienBOB might fix all my issues? Before i reload slackware is there anything else we can try?

I used the same procedure on a VM, but i didn't get the same behaviour as you did, so i can't give a detailed answer about that.

I also followed current on my desktop, laptop and workstation and everything works well too.

Starting from a fresh installation is just one solution. You can also try to reinstall all slackware packages by running
and see if it fixed your problem

I recently upgraded an up to date install of Slackware64 14.2 to Slackware64-current. Here are the commands I ran after uncommenting one mirror for slackware64-current.

# slackpkg update gpg

# slackpkg update

# slackpkg install-new

# slackpkg upgrade-all

# slackpkg clean-system

Thanks for trying on a VM, well ill try the command first, after I run that command to i need to redo the slackpkg update?
I do have another question and i hope u can answer or someone else, my question is:
In terms of exploits is running current updates far more secure than running stable updates? I read all the time "keep ur system up to date" so does that mean use current as default? For example stable Firefox is usually a couple revs behind current, so is othet libraries like openssl an other ones i saw

Thanks hitest if my memory serves me well, i believe i did the smae steps but not in that order i did
Slackpkg update gpg
Slackpkg update
Slackpkg upgrade-all
Slackpkg install-new
And maybe the clean-system
But know that i know the proper sequence ill write them down

probably best to run install-new first then upgrade-all. That way, if an important package is replaced, you will not end up with a broken system.

-stable is designed to maintain backward compatibility, so not all new version gets backported to -stable. Only security fixes or an important patches that goes into -stable. As for Firefox case, -stable received ESR version, which is maintained for a long time instead of following latest version that might *surprise* people with their new features.