Re: [LAU] ANNOUNCE: PHASEX v0.10.0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday 04 May 2007 21:10, James Stone wrote:
> On Fri, May 04, 2007 at 05:52:16PM +0200, Nigel Henry wrote:
> > On Friday 04 May 2007 05:42, William Weston wrote:
> > > On Thu, 3 May 2007, Nigel Henry wrote:
> > > > Well it looks superb. I've still to hear it, as I'm attempting to
> > > > initially build it on FC2, but am getting a problem with "make".
> > > >
> > > > What are the build requirements for Phasex? I don't want to waste a
> > > > lot of time trying to get it to build on FC2, if it's not possible.
> > >
> > > I wouldn't expect it to be possible on FC2.  Not until I take the time
> > > to make the GTK code compile on older versions of GTK-2.x.
> > >
> > >
> > > Could you let me know how that FC5 and Debian builds go?
> > >
> > > Thanks,
> > > --ww
> >
> > It builds ok on Debian Etch, using v0.10.1, but segfaults after a few
> > seconds, even without touching anything on the GUI. If I try to load a
> > patch, or open the file menu, it segfaults immediately. GTK version on
> > Etch is libgtk2.0-0 installed 2.8.20-7.  Output from starting Phasex on
> > the CLI below.
>
> Strangely, it builds and plays fine on my Debian system... I have
> been running SID, but have not updated everything for quite some
> time, so some of my stuff will be newer than Etch, some older.
>
> My version of GTK is libgtk2.0-0 (that's the rather confusing
> Debian name for it, because actually it is 2.10.11-2).
>
> By the way, I think most of the output is probably a red herring,
> because I also get lots of error messages, but it does not affect
> the functioning of the program...
>
> (<unknown>:14918): Gdk-CRITICAL **: gdk_draw_pixbuf: assertion
> `GDK_IS_PIXBUF (pixbuf)' failed
>
> (<unknown>:14918): Gdk-CRITICAL **: gdk_draw_pixbuf: assertion
> `GDK_IS_PIXBUF (pixbuf)' failed
>
> (<unknown>:14918): Gdk-CRITICAL **: gdk_draw_pixbuf: assertion
> `GDK_IS_PIXBUF (pixbuf)' failed
>
> ... and so on...
>
> James

Your probably correct on the output on the CLI being a red herring. For 
example, on some distros when running Gedit from the CLI, I get stuff like 
this, and this from FC2.

[root@localhost djmons]# gedit

(gedit:21025): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 
(gdk_pixbuf_new_from_file): assertion `filename != NULL' failed

(gedit:21025): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 
(gdk_pixbuf_new_from_file): assertion `filename != NULL' failed

(gedit:21025): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 
(gdk_pixbuf_new_from_file): assertion `filename != NULL' failed

(gedit:21025): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 
(gdk_pixbuf_new_from_file): assertion `filename != NULL' failed

(gedit:21025): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 
(gdk_pixbuf_new_from_file): assertion `filename != NULL' failed

(gedit:21025): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 
(gdk_pixbuf_new_from_file): assertion `filename != NULL' failed

(gedit:21025): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 
(gdk_pixbuf_new_from_file): assertion `filename != NULL' failed

(gedit:21025): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 
(gdk_pixbuf_new_from_file): assertion `filename != NULL' failed

(gedit:21025): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 
(gdk_pixbuf_new_from_file): assertion `filename != NULL' failed

(gedit:21025): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 
(gdk_pixbuf_new_from_file): assertion `filename != NULL' failed

(gedit:21025): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 
(gdk_pixbuf_new_from_file): assertion `filename != NULL' failed
[root@localhost djmons]#

It creates no problems for Gedit, and the editor works fine.

It doesn't explain though why, if I start Phasex in Etch, it segfaults, but if 
I ssh from FC2 into Etch, and start it from FC2, it runs ok.

Btw. My current Debian installs were originally installed from Woody 3.0r2 
cdroms, and sources were set to testing. That is when Sarge was still on 
testing. When Sarge went stable I kept one of the 3 installs on testing, and 
it updated to Etch. With Etch about to go stable I upgraded one of my 2 Sarge 
installs to Etch, and it went like clockwork. virtually no problems, even 
with the transition from xfree86 to xorg. So currently I have 1 Sarge 
install, and 2 Etch installs. I think this evening I will put the Etch 
install, that was on testing back on testing, and see how Lenny goes. I had 
changed the sources for Etch from testing to Etch, as Etch was approaching 
stable.

Hopefully I should end up with 3 Debian versions. Sarge, Etch, and Lenny.

This Lenny. Is he the same one that works at Burn's power plant in 
Springfield, and is a workmate of Homer?

Nigel.

> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
> http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user

[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux