Upgrading from 3.2 gives Segmentation fault

[notme]

Basically you are asking for support for a distro that the producer no longer supports.  Unless you want to compile and install the dependencies you need at the newer versions you are SOL.

[rupy]

Well I could run the latest bitcoin client on windows XP from 2001, so I don't know what your on about?

[Red Emerald]

Well I could run the latest bitcoin client on windows XP from 2001, so I don't know what your on about?

Except with windows all of the dependencies are new and bundled with the client. You are trying to keep everything old except bitcoind...

[rupy]

So how come you can't bundle dependencies in linux like that?

[deepceleron]

So how come you can't bundle dependencies in linux like that?

You can. http://statifier.sourceforge.net/

For all the libraries it would take, it would make a huge binary for Bitcoin.

I got that openSUSE distro, and bitcoind runs just fine. The problem is the platform's old QT 4.5.3 even after full updates. Qt is forward-compatible, meaning applications will generally continue working on new platforms, but new apps might not work on old libraries or compile in old Qt.

If you absolutely must have bitcoin-qt running, I would suggest getting and compiling qt 4.8.4, and setting the path to the new built libraries. It would be less work than attempting to build Bitcoin. http://qt-project.org/doc/qt-4.8/install-x11.html

Even less work is to get virtualbox and put a new distro on it.

If you haven't linked up the Evergreen extended maintenance repository, your 11.2 SUSE is full of security holes big enough to drive a malware truck through. http://en.opensuse.org/openSUSE:Evergreen_11.2#List_of_updates_for_11.2_from_Evergreen

edit-FIX: I built and installed qt-4.8.4 on openSUSE 11.2.

Then in a terminal console:
export QTDIR="/usr/local/Trolltech/Qt-4.8.4/"
export PATH="${QTDIR}/bin:${PATH}"
export LD_LIBRARY_PATH="${QTDIR}/lib"
export CMAKE_PREFIX_PATH="${QTDIR}"
export PKG_CONFIG_PATH="${QTDIR}/lib/pkgconfig"
./bitcoin-qt

Bitcoin now launches just fine. Bitcoin "Help"->"About Qt" = "This program uses Qt version 4.8.4."

[notme]

So how come you can't bundle dependencies in linux like that?

You can. http://statifier.sourceforge.net/

For all the libraries it would take, it would make a huge binary for Bitcoin.

I got that openSUSE distro, and bitcoind runs just fine. The problem is the platform's old QT 4.5.3 even after full updates. Qt is forward-compatible, meaning applications will generally continue working on new platforms, but new apps might not work on old libraries or compile in old Qt.

If you absolutely must have bitcoin-qt running, I would suggest getting and compiling qt 4.8.4, and setting the path to the new built libraries. It would be less work than attempting to build Bitcoin. http://qt-project.org/doc/qt-4.8/install-x11.html

Even less work is to get virtualbox and put a new distro on it.

If you haven't linked up the Evergreen extended maintenance repository, your 11.2 SUSE is full of security holes big enough to drive a malware truck through. http://en.opensuse.org/openSUSE:Evergreen_11.2#List_of_updates_for_11.2_from_Evergreen

edit-FIX: I built and installed qt-4.8.4 on openSUSE 11.2.

Then in a terminal console:
export QTDIR="/usr/local/Trolltech/Qt-4.8.4/"
export PATH="${QTDIR}/bin:${PATH}"
export LD_LIBRARY_PATH="${QTDIR}/lib"
export CMAKE_PREFIX_PATH="${QTDIR}"
export PKG_CONFIG_PATH="${QTDIR}/lib/pkgconfig"
./bitcoin-qt

Bitcoin now launches just fine. Bitcoin "Help"->"About Qt" = "This program uses Qt version 4.8.4."

My point exactly, although I guess I can agree with giving him the tools he's asking for even if it's bad for him.  I lean libertarian.

[rupy]

Ok, will definetly check this out...

Can you guys give me a scenario how my 11.2 install could get compromised?

[Red Emerald]

Ok, will definetly check this out...

Can you guys give me a scenario how my 11.2 install could get compromised?

Read the CVEs linked from http://en.opensuse.org/openSUSE:Evergreen_11.2#List_of_updates_for_11.2_from_Evergreen

Do you run any of the programs listed?

[notme]

Ok, will definetly check this out...

Can you guys give me a scenario how my 11.2 install could get compromised?

Read the CVEs linked from http://en.opensuse.org/openSUSE:Evergreen_11.2#List_of_updates_for_11.2_from_Evergreen

Do you run any of the programs listed?

I'm pretty sure he wan't to use the vulnerable version of Qt on that list .

[Herodes]

So what do I have to delete in .bitcoin to get the latest release to work?

Not sure if this is mentioned, but if you need to preserve coins, could you not send them temporarily to another wallet, then delete everything from the old version, then download the new binaries ?

After blockchain is synched, move the coins back to the new wallet ?

[deepceleron]

So what do I have to delete in .bitcoin to get the latest release to work?

Not sure if this is mentioned, but if you need to preserve coins, could you not send them temporarily to another wallet, then delete everything from the old version, then download the new binaries ?

After blockchain is synched, move the coins back to the new wallet ?

You really didn't read anything in this thread, did you?

[K1773R]

So what do I have to delete in .bitcoin to get the latest release to work?

Not sure if this is mentioned, but if you need to preserve coins, could you not send them temporarily to another wallet, then delete everything from the old version, then download the new binaries ?

After blockchain is synched, move the coins back to the new wallet ?

You really didn't read anything in this thread, did you?

ignore function ftw

[rupy]

Ok, FYI rolling updates is the solution; or tumbleweed for SuSE... the linux community has fixed the problem!

Too bad its only for 11.4 and above though... works great on my laptop! Incredible!