[pythonian4000]

Hey everyone! In what little spare time I can find at present, I am making progress on the build system. And I now have a semi-working nightly builder. Semi-working in that it builds a nightly fine, but it doesn't build it nightly - only when I force a build.

In the interest of giving everyone something to play with, you can find the builds here:

http://ngale.jackgrigg.com/builds/

I must stress that these are NOT OFFICIAL BUILDS yet, as the build system is still in flux. These aren't even alpha builds - they are entirely dependent on what I am doing with the build system, and more than likely they will get deleted at some point as I refine and rebuild bits. In addition, there are still Songbird-related icons etc. that need replacing, and I'm guessing that the license needs reworking, and these things prevent any current builds being official.

However, they are still builds of the Nightingale source as it currently stands, and I have been able to run them fine (well, it opened and would play a song - that's all the testing I'm doing at present ^_^ ). Oh - don't try to use the Nightingale feather at present - there are bits missing, like the main player form, and so you end up with one giant Mozilla-esque "File Not Found" page and have to kill the program and delete your .nightingale2 folder =D

So, in short - non-official builds are available, and take whichever one is in the highest numbered folder. If numbers disappear, it just means I rebuilt the buildbot (again =P ).

[haeckle]

hi,
i tried the latest build (Nightingale_1.8.1-1863_linux-i686.tar.gz version 9) in a vm running ubuntu 10.10. but all i got were these outputs:

haeckle@maverickvirtual:/opt/Nightingale_build-1863$ ./nightingale

(nightingale-bin:1702): Gdk-WARNING **: gdk_window_set_icon_list: icons too large
haeckle@maverickvirtual:/opt/Nightingale_build-1863$ ./nightingale-bin
./nightingale-bin: error while loading shared libraries: libjemalloc.so: cannot open shared object file: No such file or directory

[pythonian4000]

(03-03-2011, 09:11 PM)haeckle Wrote: hi,
i tried the latest build (Nightingale_1.8.1-1863_linux-i686.tar.gz version 9) in a vm running ubuntu 10.10. but all i got were these outputs:

haeckle@maverickvirtual:/opt/Nightingale_build-1863$ ./nightingale

(nightingale-bin:1702): Gdk-WARNING **: gdk_window_set_icon_list: icons too large
haeckle@maverickvirtual:/opt/Nightingale_build-1863$ ./nightingale-bin
./nightingale-bin: error while loading shared libraries: libjemalloc.so: cannot open shared object file: No such file or directory

I have just tested that build on my local machine (Xubuntu 10.10) and it runs fine. The command you should be running is the first one, not the second - hence the second error about loading libraries. As for the first one, did yours die straight after that? The Gdk-WARNINGs come up many times when I run it, and it does take about 15 seconds for a window to pop up (FWIR that would normally have the splash screen in it but due to licensing we had to remove it), but it still runs so for now treat those warnings as expected behaviour ^_^

[haeckle]

hi,
yes, it died straight after that. i tried it with 'sudo -H ./nightingale', some more Gdk-WARNINGs came, but then it started fine and i was also able to play an ogg-file (but no mp3. it's because i haven't install the corresponding gstreamer packages, isn't it?).
is this information useful? can i provide some more information to help?

[pythonian4000]

(03-04-2011, 08:37 AM)haeckle Wrote: hi,
yes, it died straight after that. i tried it with 'sudo -H ./nightingale', some more Gdk-WARNINGs came, but then it started fine and i was also able to play an ogg-file (but no mp3. it's because i haven't install the corresponding gstreamer packages, isn't it?).
is this information useful? can i provide some more information to help?

I think I get it - I noticed that when you first run Nightingale some files are created in the base directory of the install, and since you have extracted it in /opt you don't have permission. Using 'sudo -H' will have run it as root, giving you the needed permissions, but the preferences would then be in /root/.nightingale2/

My recommendation is to instead extract the package in your home bin directory (/home/user/bin/) and run it from there. You can even symlink the /home/user/bin/Nightingale_blah/nightingale script to /home/user/bin/nightingale (symlink MUST have the same name) and then just run it from the command line like any program.

EDIT: And yes, you can't play .mp3 because the system packages are missing - Nightingale as it stands relies on system Gstreamer, not built-in ^_^

[haeckle]

(03-04-2011, 10:58 AM)pythonian4000 Wrote:

(03-04-2011, 08:37 AM)haeckle Wrote: hi,
yes, it died straight after that. i tried it with 'sudo -H ./nightingale', some more Gdk-WARNINGs came, but then it started fine and i was also able to play an ogg-file (but no mp3. it's because i haven't install the corresponding gstreamer packages, isn't it?).
is this information useful? can i provide some more information to help?

I think I get it - I noticed that when you first run Nightingale some files are created in the base directory of the install, and since you have extracted it in /opt you don't have permission. Using 'sudo -H' will have run it as root, giving you the needed permissions, but the preferences would then be in /root/.nightingale2/

My recommendation is to instead extract the package in your home bin directory (/home/user/bin/) and run it from there. You can even symlink the /home/user/bin/Nightingale_blah/nightingale script to /home/user/bin/nightingale (symlink MUST have the same name) and then just run it from the command line like any program.

EDIT: And yes, you can't play .mp3 because the system packages are missing - Nightingale as it stands relies on system Gstreamer, not built-in ^_^

you are right. it's because of the permissions. i extract it in my home folder and everything goes fine.
is there anything in the moment i can help with?

[pythonian4000]

I think the best thing right now would be to start getting some bug reports. So use it, abuse it and find out where it fails ^_^

As for where to submit the bug reports, we have three trackers running at present - a self-hosted Bugzilla instance and the Sourceforge and Trac ones on Sourceforge. stevo in his last blog post indicated that he would rather use a Sourceforge-hosted tracker, so post your bugs to http://sourceforge.net/apps/trac/ngale/ (I refuse to use the inbuilt Sourceforge tracker - that thing is awful in terms of customization and any sort of data extraction).

[pythonian4000]

(03-08-2011, 02:52 AM)pyrignis Wrote: Hello all,

I'm eagerly waiting for nightingale to be usable!
I have no coding skills but I'd love to do some bug tracking. Is there a x64 build ready or in plan?
Other ways to help?

Nightingale can be built for x64, but at present the only server I have to run a buildslave on is a 32-bit system. I think I will focus on 32-bit for now and get the build infrastructure running properly on that, and then it should be completely trivial to drop in another buildslave and start generating 64-bit builds.

So for now just run the 32-bit version on (I assume) your 64-bit OS, which in fact will be a good test case, and note down any bugs or problems. As mentioned in another thread we have three possible bug trackers at present, so probably best to keep the reports locally until the decision is made.

[freaktechnik]

I just wanted to mention, that it works fine (I didn't test playing yet...) on my Ubuntu 10.10. (Yes, there are three gdk warnings, but hey, who cares?)

[nighthawk]

Just thought you would like to know that I currently have it working on Fedora 14 very nicely.

Thank you.