SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,096
Original Poster
Rep:
Quote:
Originally Posted by mrclisdue
Indeed, I don't understand all the *hate*.
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:
Code:
slackpkg clean-system
...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.
Glad to report that my -current install is all sorted out, my Sbo repo is set to the -current git repo, and I finally got Inkscape installed. Time to put this box to work!
Thanks for all the help...that's really the best part of the Slackware experience. We wouldn't be using Slack if we didn't are about it, right?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,096
Original Poster
Rep:
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:
Quote:
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.
bash-4.2$
Rather interesting since I'm using Slackware64-current with the "True Multilib" files installed.
Maybe you have compiled Wine as a 64bit version before or you used the official 64bit wine package from winehq.org - it creates a 64bit prefix, which cannot run 32bit applications.
Delete your $HOME/.wine folder and create a new 32bit prefix with the following command:
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,
Code:
bash-4.2$ thunderbird
null:profile-after-change
added
added
[object ChromeWindow]:mail-startup-done
pure virtual method called
terminate called without an active exception
Aborted
bash-4.2$
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).
no, the mozglue/jemalloc thingie seems completely unrelated, I'm more and more oriented to think that me and you simply messed up something on our installs
I'll try to investigate, my girlfriend notebook is affected too and she takes care of motivating me on the matter (lol).
P.S. not everything has gone negative in this thing: with the cache dir patches, now I'm running the new mozillas stuff also on x86_64
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
