SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I don't necessarily agree with everyone, every time; nor necessarily with the way one may come across, from time to time, but that's what makes this board, and especially this slack forum *real*.
It's all about discovering and discussing problems and solutions. No one is being forced to do either or any, but there's really no need to diss anyone. If one has the time to post a disparaging comment, then perhaps that time might be used in a helpful fashion, or not at all....
Yep. Public forums will always have the few that spew on others hateful and hurtful comments. Just ignore them and/or hit the report button on their posts. Half the time they often are drowned out and blend back into the background unnoticed or just vanish.
You may also want to run:
...at some point if you use a lot of additional packages not normally distributed with Slackware like slackbuilds, to see if those packages are in need of removals or check their version numbers against updates either from Slackware or SlackBuilds.
Installed the latest WINE and, again, it wouldn't run any of the ms-windows based applications that were installed and run with WINE 1.2.1, so I attempted to launch from a prompt and this is the error message:
bash-4.2$ env WINEPREFIX="/home/~/.wine" wine "C:\AHDW\AHD3.EXE"
wine: '/home/~/.wine' is a 64-bit installation, it cannot be used with a 32-bit wineserver.
Rather interesting since I'm using Slackware64-current with the "True Multilib" files installed.
Thunderbird (from "current"):
Since the recent updates to "current" Thunderbird has ceased to function properly. I've deleted ~/.thunderbird and ran "upgradepkg --reinstall --install-new" on the latest Thunderbird package three times and each time is the same.
It will launch, let you set up an account, retrieve mail and then crash and disappear.
If started from a prompt the error message is,
pure virtual method called
terminate called without an active exception
I seem to have hit this too, but only on slackware-current (32bit), seems related to this bug (that points to this other one), really dunno why for others things work, maybe it's a fault on our side.
As the provided patches in the bug report seem not to apply cleanly here, the thing seems fixed in the latest version and seamonkey-2.10, firefox-13 and thunderbird-13 are out for grabs, I tried to build the new versions...
...but I met another bug: as also the patches linked in this other bug don't apply (I'm definitely missing something on how to apply that stuff from mercurial), I've prepared some patches myself (based on the ones submitted) that should let them build.
Seamonkey and firefox compilation has completed, and the new thunderbird seems to build with no hassles with the seamonkey patch (still going on, everything using the slackbuilds from -current).
I'll confirm later on (I'm out for dinner) if things has gone well.
P.S. no, same behaviour for thunderbird: now I'm trying adding the (recreated) suggested patch. Will report back in some hours (after sleep).