4 May
2007
4 May
'07
1:52 p.m.
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.
Well it was going to be below. I ssh'd into Etch from FC2 so as to start
Phasex from FC2, and paste the output from the CLI before the segfault to
you.
Now this is really weird. I started Phasex from FC2, and the GUI opened in
FC2, and I'm waiting for it to segfault. A minute later, and it's still
running. So I play around with the file menu, load one of the patches, play a
bit, and I cannot get it to segfault.
Close it on FC2, and no problems showing on the CLI on FC2, as below.
djmons@debian:~$ phasex
Thank you for using PHASEX!
(C) 1999-2007 William Weston <weston(a)sysex.net>
Released under the GNU Public License, Ver. 2
djmons@debian:~$ exit
logout
Connection to 192.168.0.8 closed.
[djmons@localhost djmons]$
Why would it segfault when I run it from Debian Etch, but when I run it from
FC2, ssh'd into Etch, Phasex works perfectly? Anyway with a bit of file
creation, and ftp'ing the segfault errors from Etch to FC2, they *are* now
below.
I must say I love the arp's, and like this bit in your TODO.
"Create a programmable arpeggiator".
djmons@debian:~$ phasex
(<unknown>:10435): Gtk-CRITICAL **: gtk_style_finalize: assertion
d`style->attach_count == 0' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE
(style)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): Gtk-CRITICAL **: gtk_style_detach: assertion `GTK_IS_STYLE
(style)' failed
(<unknown>:10435): GLib-GObject-WARNING **: gsignal.c:2180: invalid unclassed
object pointer for value type `GtkStyle'
(<unknown>:10435): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
(<unknown>:10435): Gtk-CRITICAL **: _gtk_style_peek_property_value: assertion
`GTK_IS_STYLE (style)' failed
Segmentation fault
djmons@debian:~$
Nice work William. Phasex sounds really nice. I'll post again with any
problems with the build on FC5.
Nigel.
4 May
4 May
5:10 p.m.
New subject: ANNOUNCE: PHASEX v0.10.0
On Fri, May 04, 2007 at 05:52:16PM +0200, Nigel Henry wrote:
On Friday 04 May 2007 05:42, William Weston wrote:
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
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.
6:12 p.m.
New subject: ANNOUNCE: PHASEX v0.10.0
On Friday 04 May 2007 21:10, James Stone wrote:
On Fri, May 04, 2007 at 05:52:16PM +0200, Nigel Henry
wrote:
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.
On Friday 04 May 2007 05:42, William Weston
wrote:
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 On Thu, 3 May 2007, Nigel Henry wrote:
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. 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 _______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
6:49 p.m.
New subject: ANNOUNCE: PHASEX v0.10.0
On Fri, 4 May 2007, James Stone wrote:
I have a feeling that this is coming from gtkknob.c as well. That piece
of code has signs of pixbuf changes by several people, including myself.
I'll have to look into this one more...
--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 
8:48 p.m.
New subject: ANNOUNCE: PHASEX v0.10.0
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, May 04, 2007 at 08:10:12PM +0100, James Stone wrote:
On Fri, May 04, 2007 at 05:52:16PM +0200, Nigel Henry
wrote:
Also runs fine on mine too. Debian Etch. With GTK 2.8.20-3. On AMD64.
- -ken
On Friday 04 May 2007 05:42, William Weston
wrote:
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).
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGO7fPe8HF+6xeOIcRAiRtAKCSmcavk815oPwgOKRIBbc1wNOhPQCgiiMX
YPjNYsXQobFbm6ECGVdSnVg=
=+B70
-----END PGP SIGNATURE-----
9:15 p.m.
New subject: ANNOUNCE: PHASEX v0.10.0
On Saturday 05 May 2007 00:46, Ken Restivo wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, May 04, 2007 at 08:10:12PM +0100, James Stone wrote:
All a bit odd. As I mention above, my gtk version is 2.8.20-7. If I start
Phasex on the Etch machine it segfaults after some seconds. If I ssh into
Etch from FC2, and start Phasex from FC2, there are no problems, and can do
what I like with the synth.
I get exactly the same problem on the same machine that Etch is installed on,
with FC5. Phasex segfaults when running it on FC5, but if I ssh into FC5 from
FC2, and run Phasex from FC2 there are no problems.
Nigel.
On Fri, May 04, 2007 at 05:52:16PM +0200, Nigel
Henry wrote:
Also runs fine on mine too. Debian Etch. With GTK 2.8.20-3. On AMD64.
- -ken On Friday 04 May 2007 05:42, William Weston
wrote:
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). 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.
5 May
5 May
4:45 a.m.
New subject: ANNOUNCE: PHASEX v0.10.0
On Sat, May 05, 2007 at 01:15:28AM +0200, Nigel Henry wrote:
On Saturday 05 May 2007 00:46, Ken Restivo wrote:
Maybe a backtrace with gdb would give more info?
James
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, May 04, 2007 at 08:10:12PM +0100, James Stone wrote:
All a bit odd. As I mention above, my gtk version is 2.8.20-7. If I start
Phasex on the Etch machine it segfaults after some seconds. If I ssh into
Etch from FC2, and start Phasex from FC2, there are no problems, and can do
what I like with the synth.
I get exactly the same problem on the same machine that Etch is installed on,
with FC5. Phasex segfaults when running it on FC5, but if I ssh into FC5 from
FC2, and run Phasex from FC2 there are no problems.
Nigel. On Fri, May 04, 2007 at 05:52:16PM +0200, Nigel
Henry wrote:
Also runs fine on mine too. Debian Etch. With GTK 2.8.20-3. On AMD64.
- -ken 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).
6404
days inactive
6405
days old
linux-audio-user@lists.linuxaudio.org
6 comments
4 participants
participants (4)
-
James Stone -
Ken Restivo -
Nigel Henry -
William Weston