Imprudence 1.2 x86_64 build (Linux)

Post here with your bug reports or any troubles running the viewer, crashes, etc. Be sure to use the Search to look for similar issues, since someone might have a solution for your problem already!

Imprudence 1.2 x86_64 build (Linux)

Postby Armin on Wed Dec 23, 2009 9:15 am

Hi,

here comes the second test-build of Imprudence 1.2 for x86_64-Linux.
"The second? Did I miss the first ?" You may ask ... er ... well ... no, you didn't miss much, unless you wanted to see a client crash before even the login screen opened.

"Test-build - whats that?" The lack of a better word, of course ...
It comes with all libraries needed, like the 32bit client versions, and that's the part that needs testing. Almost all of the libs are recompiled, since the ones that LL(tm) provides for 64bit Linux are pretty old, some broken, or not even existent.

Some of these libs tend to get depending to the system they are build on instead to what they are told to depend on. That was the trouble with the first test build - it depended on a mixture of Debian versions (Lenny and Squeeze).

The second build was tested on Debian Lenny, Gentoo 10.1, and OpenSuse 11.0 (thank you, Adamas !). So it's time to go into the wild ...

old :
http://imprudenceviewer.org/download/bu ... 64.tar.bz2 ]
new, 1.22 based:
http://imprudenceviewer.org/download/bu ... .3.tar.bz2
NEW, 1.23 based:
http://imprudenceviewer.org/download/bu ... 64.tar.bz2

:)
Armin


Known issues:
===========
* no voice. You can work around this if you have 32bit compatibility in place - afaik all fairly recent popular distros have that out of the box.
Now keep a backup of your imprudence/lib/ folder. Get the voice parts from an 1.22 LL(tm) client and copy them in place. Make sure you have openal and libuuid installed on your system (using your package manager). Get 32bit versions of: libalut.so libopenal.so.1 libortp.so libuuid.so.1 (they e.g. can be found in 1.22 ) and libidn.so.11 - and copy them in your imprudence/lib/ folder. Ok overwriting libopenal.so.1 and libuuid.so.1 (since you made sure you installed them system wide and keep a backup this is safe).

*no sound in videos. Binaries of the aac decoder ( libgstfaad.so) are patented and can't be redistributed. Many Gstreamer plugins just can be plugged in the imprudence/lib/gstreamer-plugins/ folder - i didn't have this special one to try.
Last edited by Armin on Mon Jan 04, 2010 3:45 pm, edited 2 times in total.
User avatar
Armin
 
Posts: 189
Joined: Sun Nov 23, 2008 9:34 am

Re: Imprudence 1.2 x86_64 build (Linux)

Postby Nedrae Messmer on Sun Dec 27, 2009 1:09 pm

So far everything's fine, except that GTK dialogs don't grab my theme (they look like unskinned GTK1 dialogs), and the following error shows up in the terminal a bunch of times:

(<unknown>:24385): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/local/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory

This is on Ubuntu 9.10 64-bit.
Nedrae Messmer
 
Posts: 6
Joined: Sun Dec 27, 2009 8:00 am

Re: Imprudence 1.2 x86_64 build (Linux)

Postby Armin on Sun Dec 27, 2009 3:50 pm

Yay feedback :)

Nedrae Messmer wrote:So far everything's fine, except that GTK dialogs don't grab my theme (they look like unskinned GTK1 dialogs), and the following error shows up in the terminal a bunch of times:(<unknown>:24385): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/local/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory


Ok, I look in this.

Issues already worked on:
* Pango wrong elfclass ELF32 issues on Opensuse (inverse of the Debian/Ubuntu Pango wrong elfclass ELF64 issue on the 32bit viewer)
* Snapshot not working

known issues not yet worked on:
* hi-res snapshot not working


Thanks for finding the bugs !
:) Armin
User avatar
Armin
 
Posts: 189
Joined: Sun Nov 23, 2008 9:34 am

Re: Imprudence 1.2 x86_64 build (Linux)

Postby Armin on Tue Dec 29, 2009 11:58 am

Nedrae Messmer wrote:So far everything's fine, except that GTK dialogs don't grab my theme (they look like unskinned GTK1 dialogs), and the following error shows up in the terminal a bunch of times:

(<unknown>:24385): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/local/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory

This is on Ubuntu 9.10 64-bit.



Renaming of libgdk_pixbuf-2.0.so.0 to libgdk_pixbuf-2.0.so.0.foo in the Imprudence/lib/ folder let Imprudence use your systems gdk-pixbuf.loaders - also here no disadvantage doing so. If that works well for you you can of course delete the unneeded file.

;)
Armin
User avatar
Armin
 
Posts: 189
Joined: Sun Nov 23, 2008 9:34 am

Re: Imprudence 1.2 x86_64 build (Linux)

Postby Nedrae Messmer on Tue Dec 29, 2009 2:11 pm

Didn't work, and now in the terminal I get this:

(<unknown>:14956): GLib-GObject-WARNING **: Two different plugins tried to register 'BasicEngineFc'.

(<unknown>:14956): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed

but repeated 69 times.
Nedrae Messmer
 
Posts: 6
Joined: Sun Dec 27, 2009 8:00 am

Re: Imprudence 1.2 x86_64 build (Linux)

Postby Roberta Messerchmitt on Sat Jan 02, 2010 8:18 am

It does not seem to run on 64 bit Ubuntu 8.04 LTS at all. The imprudence.log stops at "INFO: ll_try_gtk_init: Starting GTK Initialization." :(
User avatar
Roberta Messerchmitt
 
Posts: 36
Joined: Tue Dec 23, 2008 8:48 am

Re: Imprudence 1.2 x86_64 build (Linux)

Postby Armin on Sat Jan 02, 2010 1:27 pm

New build, tested on Debian Lenny, OpenSuse 11.1, Gentoo 10.1, and Ubuntu 9.10:
http://imprudenceviewer.org/download/bu ... .3.tar.bz2

:)
Armin
User avatar
Armin
 
Posts: 189
Joined: Sun Nov 23, 2008 9:34 am

Re: Imprudence 1.2 x86_64 build (Linux)

Postby Armin on Sat Jan 02, 2010 1:56 pm

Roberta Messerchmitt wrote:It does not seem to run on 64 bit Ubuntu 8.04 LTS at all. The imprudence.log stops at "INFO: ll_try_gtk_init: Starting GTK Initialization." :(

Yeah, also the 32bit Imprudence1.2 isn't working on a 32bit Ubuntu 8.04 without updating a few libraries to Jaunty. Even though I did that myself for my 32bit 8.04 and it worked well I'm not sure if that is something I should recommend - if something goes wrong it is not easy to fix.

Armin
User avatar
Armin
 
Posts: 189
Joined: Sun Nov 23, 2008 9:34 am


Return to Bug Reports & Troubleshooting

Who is online

Users browsing this forum: Google [Bot], Silverdrake and 3 guests

cron