10 Jul
2007
10 Jul
'07
1:49 p.m.
Hi everyone,
I am humbly proud to announce that yet another one of my linux-audio
`cutie-suite` application has bitten the Qt4 dust.
Yes, it's time for QjackCtl 0.3.0 (unstable-qt4) to be released, fresh
from the CVS oven (hmmm... this makes it the second oxymoron on one
post; gotta fix this :)
Although the ChageLog doesn't go into many details, there were many
subtle bugs fixed but plenty as more were blindly introduced, as always.
I count on your eyeballs to make them shallow ;)
So it was:
- Qt4 migration was complete. Care must be taken with this new
configuration file and location: this release starts a new one from
scratch and won't reuse any of the previous existing ones, although cut
and paste might help if you know what you're doing :)
- On a last-minute addition, the "firewire" audio backend driver option
has been also included, supporting the ffado.org project which is
evolving where "freebob" is leaving (thanks to Klaus Zimmermann for this
one).
The usual place where the new source tarball can be grabbed:
http://qjackctl.sourceforge.net/
http://sourceforge.net/projects/qjackctl
Cheers && Enjoy,
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
10 Jul
10 Jul
2:20 p.m.
On Di, 10.07.07 18:40 Rui Nuno Capela <rncbc(a)rncbc.org> wrote:
Hi everyone,
I am humbly proud to announce that yet another one of my linux-audio
`cutie-suite` application has bitten the Qt4 dust.
Yes, it's time for QjackCtl 0.3.0 (unstable-qt4) to be released, fresh
Coool stuff!
Unfortunately configure refuses to find Qt4 headers here.
They are in /usr/include/qt4 (/Qt/qglobal.h)
Version is 4.3.0, and QTDIR is unset (that would point to Qt3)
configure.ac has some mention of qt3 still.
Thanks!
from the CVS oven (hmmm... this makes it the
second oxymoron on one
post; gotta fix this :)
Although the ChageLog doesn't go into many details, there were many
subtle bugs fixed but plenty as more were blindly introduced, as
always. I count on your eyeballs to make them shallow ;)
So it was:
- Qt4 migration was complete. Care must be taken with this new
configuration file and location: this release starts a new one from
scratch and won't reuse any of the previous existing ones, although
cut and paste might help if you know what you're doing :)
- On a last-minute addition, the "firewire" audio backend driver
option has been also included, supporting the ffado.org project which
is evolving where "freebob" is leaving (thanks to Klaus Zimmermann
for this one).
The usual place where the new source tarball can be grabbed:
http://qjackctl.sourceforge.net/
http://sourceforge.net/projects/qjackctl
Cheers && Enjoy,
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
2:43 p.m.
Thomas Kuther wrote:
On Di, 10.07.07 18:40 Rui Nuno Capela
<rncbc(a)rncbc.org> wrote:
You're right. I will replace the release tarball ASAP, at least while
it's hot!
BRT
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Hi everyone,
I am humbly proud to announce that yet another one of my linux-audio
`cutie-suite` application has bitten the Qt4 dust.
Yes, it's time for QjackCtl 0.3.0 (unstable-qt4) to be released, fresh
Coool stuff!
Unfortunately configure refuses to find Qt4 headers here.
They are in /usr/include/qt4 (/Qt/qglobal.h)
Version is 4.3.0, and QTDIR is unset (that would point to Qt3)
configure.ac has some mention of qt3 still.
from the CVS oven (hmmm... this makes it the
second oxymoron on one
post; gotta fix this :)
Although the ChageLog doesn't go into many details, there were many
subtle bugs fixed but plenty as more were blindly introduced, as
always. I count on your eyeballs to make them shallow ;)
So it was:
- Qt4 migration was complete. Care must be taken with this new
configuration file and location: this release starts a new one from
scratch and won't reuse any of the previous existing ones, although
cut and paste might help if you know what you're doing :)
- On a last-minute addition, the "firewire" audio backend driver
option has been also included, supporting the ffado.org project which
is evolving where "freebob" is leaving (thanks to Klaus Zimmermann
for this one).
The usual place where the new source tarball can be grabbed:
http://qjackctl.sourceforge.net/
http://sourceforge.net/projects/qjackctl
Cheers && Enjoy,
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
2:59 p.m.
Rui Nuno Capela wrote:
Thomas Kuther wrote:
The new tarball has been replaced. However, SF mirrors might lag in the
propagation, so that you'll probably still get the older one for a while...
Just in case you want it now, the right one is also accessible from here:
http://www.rncbc.org/jack/qjackctl-0.3.0.tar.gz
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
On Di, 10.07.07 18:40 Rui Nuno Capela
<rncbc(a)rncbc.org> wrote:
You're right. I will replace the release tarball ASAP, at least while
it's hot!
BRT Hi everyone,
I am humbly proud to announce that yet another one of my linux-audio
`cutie-suite` application has bitten the Qt4 dust.
Yes, it's time for QjackCtl 0.3.0 (unstable-qt4) to be released, fresh
Coool stuff!
Unfortunately configure refuses to find Qt4 headers here.
They are in /usr/include/qt4 (/Qt/qglobal.h)
Version is 4.3.0, and QTDIR is unset (that would point to Qt3)
configure.ac has some mention of qt3 still.
from the CVS oven (hmmm... this makes it the
second oxymoron on one
post; gotta fix this :)
Although the ChageLog doesn't go into many details, there were many
subtle bugs fixed but plenty as more were blindly introduced, as
always. I count on your eyeballs to make them shallow ;)
So it was:
- Qt4 migration was complete. Care must be taken with this new
configuration file and location: this release starts a new one from
scratch and won't reuse any of the previous existing ones, although
cut and paste might help if you know what you're doing :)
- On a last-minute addition, the "firewire" audio backend driver
option has been also included, supporting the ffado.org project which
is evolving where "freebob" is leaving (thanks to Klaus Zimmermann
for this one).
The usual place where the new source tarball can be grabbed:
http://qjackctl.sourceforge.net/
http://sourceforge.net/projects/qjackctl
Cheers && Enjoy,
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org 
3:49 p.m.
On 7/10/07, Rui Nuno Capela <rncbc(a)rncbc.org> wrote:
The new tarball has been replaced. However, SF mirrors
might lag in the
propagation, so that you'll probably still get the older one for a while...
Just in case you want it now, the right one is also accessible from here:
http://www.rncbc.org/jack/qjackctl-0.3.0.tar.gz
Thanks, compiles fine on Ubuntu Feisty now.
However, this is what qjackctl looks like:
http://das.nasophon.de/stuff/qjackctl.png
What happened here? I have qt-4.2.3... do I need 4.3? Or could the
problem be something else?
Dominic
3:58 p.m.
On Di, 10.07.07 21:49 "Dominic Sacré" <dominic.sacre(a)gmx.de> wrote:
On 7/10/07, Rui Nuno Capela <rncbc(a)rncbc.org>
wrote:
Thanks, compiled here too now.
But same problem as Dominic, it looks somewhat strange :)
Qt 4.3.0 here, so that's not it.
http://gimpel.ath.cx/~tom/qjack.png
Cheers,
Tom
The new tarball has been replaced. However, SF
mirrors might lag in
the propagation, so that you'll probably still get the older one
for a while...
Just in case you want it now, the right one is also accessible from
here:
http://www.rncbc.org/jack/qjackctl-0.3.0.tar.gz
Thanks, compiles fine on Ubuntu Feisty now.
However, this is what qjackctl looks like:
http://das.nasophon.de/stuff/qjackctl.png
What happened here? I have qt-4.2.3... do I need 4.3? Or could the
problem be something else?
Dominic
4:33 p.m.
Thomas Kuther wrote:
On Di, 10.07.07 21:49 "Dominic Sacré"
<dominic.sacre(a)gmx.de> wrote:
Damn. Gnome's a real PITA :( KDE rules here, as windows are managed as
good as ever before.
Anyway, please, would you try whether things get better with the
attached patch (-p1).
HIH
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
On 7/10/07, Rui Nuno Capela
<rncbc(a)rncbc.org> wrote:
Thanks, compiled here too now.
But same problem as Dominic, it looks somewhat strange :)
Qt 4.3.0 here, so that's not it.
http://gimpel.ath.cx/~tom/qjack.png
The new tarball has been replaced. However, SF
mirrors might lag in
the propagation, so that you'll probably still get the older one
for a while...
Just in case you want it now, the right one is also accessible from
here:
http://www.rncbc.org/jack/qjackctl-0.3.0.tar.gz
Thanks, compiles fine on Ubuntu
Feisty now.
However, this is what qjackctl looks like:
http://das.nasophon.de/stuff/qjackctl.png
What happened here? I have qt-4.2.3... do I need 4.3? Or could the
problem be something else?
Dominic
5:20 p.m.
On 7/10/07, Rui Nuno Capela <rncbc(a)rncbc.org> wrote:
Damn. Gnome's a real PITA :( KDE rules here, as
windows are managed as
good as ever before.
Anyway, please, would you try whether things get better with the
attached patch (-p1).
Looks good now, thanks! Doesn't seem to be just a Gnome problem by the
way, running xfwm here...
Dominic
5:30 p.m.
Dominic Sacré wrote:
On 7/10/07, Rui Nuno Capela <rncbc(a)rncbc.org>
wrote:
Yeah, you're right again. I've just tested (for the first, ugh!) on
Gnome and was able to reproduce the ugliness. Sorry for being harsh, but
my relation with Gnome just isn't ;)
OTOH, it has been also reported (Carlos?) that the system tray icon does
not look well. Are you able to test this on xfwm? Guess it won't work at
all, but we never know until someone puts it at the stake :)
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Damn. Gnome's a real PITA :( KDE rules here,
as windows are managed as
good as ever before.
Anyway, please, would you try whether things get better with the
attached patch (-p1).
Looks good now, thanks! Doesn't seem to be just a Gnome problem by the
way, running xfwm here...
6:23 p.m.
Rui Nuno Capela escribió:
Dominic Sacré wrote:
Again me :-p Systray icon begins to looks fine when pushing Start
button after launch Qjackctl , and seems to work well after this .
I don't know what , but there must be something wrong at the debian
folder of the tar ball that brokes apt when build the debian package .
I did my own deb package using "dh_make" and "fakeroot debian/rules
binary" commands , and everything went fine now.
BTW , the systray issue isn't too annoying .
Tested in Debian Etch x86 (Gnome 2.14.3) and Debian testing amd64
(Xfce4.4.1) with same issues on both .
Good work !
Thank you very much .
Saludos.
-- Carlos .
On 7/10/07, Rui Nuno Capela
<rncbc(a)rncbc.org> wrote:
Yeah, you're right again. I've just tested (for the first, ugh!) on
Gnome and was able to reproduce the ugliness. Sorry for being harsh, but
my relation with Gnome just isn't ;)
OTOH, it has been also reported (Carlos?) that the system tray icon does
not look well. Are you able to test this on xfwm? Guess it won't work at
all, but we never know until someone puts it at the stake :)
Cheers.
Damn. Gnome's a real PITA :( KDE rules here,
as windows are managed as
good as ever before.
Anyway, please, would you try whether things get better with the
attached patch (-p1).
Looks good now, thanks! Doesn't seem to be just a Gnome problem by the
way, running xfwm here...
6:41 p.m.
Carlos Pino wrote:
Again me :-p Systray icon begins to looks fine
when pushing Start
button after launch Qjackctl , and seems to work well after this .
I don't know what , but there must be something wrong at the debian
folder of the tar ball that brokes apt when build the debian package .
I did my own deb package using "dh_make" and "fakeroot debian/rules
binary" commands , and everything went fine now.
Hmmm. The only issue that I've com around on my debian virtualbox is
that one must `chmod +x debian/rules` before building it up with just
`dpkg_buildpackage` as root. And that's all I can do about testing
building debs.
YMMV, of course, as I only test this thing very now and then... :)
BTW , the systray issue isn't too annoying .
Tested in Debian Etch x86 (Gnome 2.14.3) and Debian testing amd64
(Xfce4.4.1) with same issues on both .
So, is that right that only on the first run the systray icon looks bad?
Like garbled, random inverted pixels or what?
Thanks for the patience, Carlos. I would rather play some guitar, if I
knew how to play the hundredth as you ;)
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
7:08 p.m.
Geoff Beasley escribió:
On Wednesday 11 July 2007 08:32, Rui Nuno Capela
wrote:
Yeah! That will never happens ..... hehehe .
Thanks for the patience, Carlos. I would rather
play some guitar, if I
knew how to play the hundredth as you ;)
yeah, but he can't code like you can.... hehehe
g.
_______________________________________________
7:06 p.m.
Wow, almost real time chat.
Rui Nuno Capela escribió:
Well, each time I run qjackctl , the icon looks bad untill press
Start , then looks fine .
Carlos Pino wrote:
Now is solved as I explained in other message .
Again me :-p Systray icon begins to looks
fine when pushing Start
button after launch Qjackctl , and seems to work well after this .
I don't know what , but there must be something wrong at the debian
folder of the tar ball that brokes apt when build the debian package .
I did my own deb package using "dh_make" and "fakeroot debian/rules
binary" commands , and everything went fine now.
Hmmm. The only issue that I've com around on my debian virtualbox is
that one must `chmod +x debian/rules` before building it up with just
`dpkg_buildpackage` as root. And that's all I can do about testing
building debs.
YMMV, of course, as I only test this thing very now and then... :)
BTW , the systray issue isn't too annoying
.
Tested in Debian Etch x86 (Gnome 2.14.3) and Debian testing amd64
(Xfce4.4.1) with same issues on both .
So, is that right that only on the first run the systray icon looks bad?
Like garbled, random inverted pixels or what?
Garbled ( say my translator :-P )
Thanks for the patience, Carlos. I would rather play
some guitar, if I
knew how to play the hundredth as you ;)
Thanks a ton for your great work , Rui .
Cheers.
Saludos .
-- Carlos.
10:19 p.m.
On Di, 10.07.07 21:24 Rui Nuno Capela <rncbc(a)rncbc.org> wrote:
Thomas Kuther wrote:
[...]
Eeeew he said Gnome :D
No, it's Enlightenment DR 0.17 here.
Applied the patch, and now it looks good.
Also after first short connection tests etc, it also seems to work nice.
Good work! :)
Thanks!
Tom
Thanks, compiled here too now.
But same problem as Dominic, it looks somewhat strange :)
Qt 4.3.0 here, so that's not it.
http://gimpel.ath.cx/~tom/qjack.png
Damn. Gnome's a real PITA :( KDE rules here, as windows are managed as
good as ever before.
Anyway, please, would you try whether things get better with the
attached patch (-p1).
HIH
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org 
11 Jul
11 Jul
8:32 a.m.
Quite nice. I applied that patch, compiled just fine.
1. How did the poster get that 0.3.0.1 deb?
2. Window title seems too small.
3. First try, setting the "midi driver" did not work, so chose "none".
After
that, choosing "raw" or "seq" does work. However, nothing shows up in
the
"midi" connections pane. (Everything appears on the alsa connections pane as
defaulted.) Jack is most recent from Debian Sid.
4. I never needed to resize previous versions. Vertical size really should be
set by the resulting widget sizes (current minimum). It should default to
this in any event.
5. Current active/inactive icons have changed from the green triangle red box
to red arrow/none. Was this intended? Does not change color or shape with
"transport" actions.
noon
David Baron wrote:
Quite nice. I applied that patch, compiled just fine.
1. How did the poster get that 0.3.0.1 deb?
Dunno. Maybe he/she checked out from todays' CVS HEAD, where I've made
some changes to make qjackctl work with jackdmp on... surprise,
surprise,... windows(tm).
2. Window title seems too small.
Did you copy your old ~/.qt/qjackctlrc into the new one location,
~/.config/rncbc.org/QjackCtl.conf ? If thats so, that explains most of
all your problems below.
3. First try, setting the "midi driver" did
not work, so chose "none". After
that, choosing "raw" or "seq" does work. However, nothing shows up in
the
"midi" connections pane. (Everything appears on the alsa connections pane as
defaulted.) Jack is most recent from Debian Sid.
4. I never needed to resize previous versions. Vertical size really should be
set by the resulting widget sizes (current minimum). It should default to
this in any event.
5. Current active/inactive icons have changed from the green triangle red box
to red arrow/none. Was this intended? Does not change color or shape with
"transport" actions.
There's no read arrow icon. Systray icon states should be as follows, as
they ever was:
- red square: Stopped, jackd is not running or is stopped.
- ligh-green arrow: Starting, jackd is starting...
- green arrow: Started, jackd is running.
- light red square: Stopping, jackd is stopping.
- light yellow arrow: Activating, jackd is running (but was not started
in qjackctl) and client is in (de)activating...
- yellow arrow: Active, jackd is running (but was not started in
qjackctl) and client is activated.
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
12:06 p.m.
Rui Nuno Capela wrote:
David Baron wrote:
hi rui,
can you please tell me, where qjack0.3.0 will write his configuration
file per default?
as i understand it will not be in the same place ( ~/.qt/qjackctlrc), so
for testing we could have both versions installed.
cheers,
doc
Quite nice. I applied that patch, compiled just
fine.
1. How did the poster get that 0.3.0.1 deb?
Dunno. Maybe he/she checked out from todays' CVS HEAD, where I've made
some changes to make qjackctl work with jackdmp on... surprise,
surprise,... windows(tm).
2. Window title seems too small.
Did you copy your old ~/.qt/qjackctlrc into the new one location,
~/.config/rncbc.org/QjackCtl.conf ? If thats so, that explains most of
all your problems below.
3. First try, setting the "midi driver"
did not work, so chose "none". After
that, choosing "raw" or "seq" does work. However, nothing shows up in
the
"midi" connections pane. (Everything appears on the alsa connections pane as
defaulted.) Jack is most recent from Debian Sid.
4. I never needed to resize previous versions. Vertical size really should be
set by the resulting widget sizes (current minimum). It should default to
this in any event.
5. Current active/inactive icons have changed from the green triangle red box
to red arrow/none. Was this intended? Does not change color or shape with
"transport" actions.
There's no read arrow icon. Systray icon states should be as follows, as
they ever was:
- red square: Stopped, jackd is not running or is stopped.
- ligh-green arrow: Starting, jackd is starting...
- green arrow: Started, jackd is running.
- light red square: Stopping, jackd is stopping.
- light yellow arrow: Activating, jackd is running (but was not started
in qjackctl) and client is in (de)activating...
- yellow arrow: Active, jackd is running (but was not started in
qjackctl) and client is activated.
Cheers.
12:37 p.m.
Dragan Noveski wrote:
hi rui,
can you please tell me, where qjack0.3.0 will write his configuration
file per default?
as i understand it will not be in the same place ( ~/.qt/qjackctlrc), so
for testing we could have both versions installed.
~/.config/rncbc.org/QjackCtl.conf
Bye now,
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
12:50 p.m.
On Wednesday 11 July 2007, Rui Nuno Capela wrote:
More what I would expect. However, these are not
what I am seeing.
That red arrow is there, otherwize the circle is simply blank/white.
Maybe the icons were not installed correctly by sudo make install?
David Baron wrote:
No I didn't. Did not know these were there! I set all
the options based on
those on the at the time running 0.2.2. Then I closed that at re-ran the new
one. Maybe I should purge the old version and reinstall the new one?
Quite nice. I applied that patch, compiled just
fine.
1. How did the poster get that 0.3.0.1 deb?
Dunno. Maybe he/she checked out from todays' CVS HEAD, where I've made
some changes to make qjackctl work with jackdmp on... surprise,
surprise,... windows(tm).
2. Window title seems too small.
Did you copy your old ~/.qt/qjackctlrc into the new one location,
~/.config/rncbc.org/QjackCtl.conf ? If thats so, that explains most of
all your problems below. 3. First try, setting the "midi driver"
did not work, so chose "none".
After that, choosing "raw" or "seq" does work. However, nothing shows
up
in the "midi" connections pane. (Everything appears on the alsa
connections pane as defaulted.) Jack is most recent from Debian Sid.
4. I never needed to resize previous versions. Vertical size really
should be set by the resulting widget sizes (current minimum). It should
default to this in any event.
5. Current active/inactive icons have changed from the green triangle red
box to red arrow/none. Was this intended? Does not change color or shape
with "transport" actions.
There's no read arrow icon. Systray icon states should be as follows, as
they ever was:
- red square: Stopped, jackd is not running or is stopped.
- ligh-green arrow: Starting, jackd is starting...
- green arrow: Started, jackd is running.
- light red square: Stopping, jackd is stopping.
- light yellow arrow: Activating, jackd is running (but was not started
in qjackctl) and client is in (de)activating...
- yellow arrow: Active, jackd is running (but was not started in
qjackctl) and client is activated.
1:06 p.m.
More very minor things:
1. Jack is always started with qjackctl. I have that option not checked.
2. I have had the program crash out working the connections (all-alsa) pane.
Happens when I touch the midi-through item.
3:12 p.m.
David Baron wrote:
More very minor things:
1. Jack is always started with qjackctl. I have that option not checked.
Does the main top-left display says 'Started' or 'Active' (in bright
yellow over black) when you launch qjackctl?
2. I have had the program crash out working the
connections (all-alsa) pane.
Happens when I touch the midi-through item.
This deserves some debugging. Are willing to help?
1) rebuild with ./configure --enable-debug && make
2) ulimit -c unlimited
3) ./qjackctl
4) *make-it-crash* (core dumped)
5) gdb ./qjackctl core
Tell me what you find.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
3:43 p.m.
On Wednesday 11 July 2007, Rui Nuno Capela wrote:
May try tomorrow. See what happens.
David Baron wrote:
Yes.
More very minor things:
1. Jack is always started with qjackctl. I have that option not checked.
Does the main top-left display says 'Started' or 'Active' (in bright
yellow over black) when you launch qjackctl? 2. I have had the program crash out working the
connections (all-alsa)
pane. Happens when I touch the midi-through item.
This deserves some debugging. Are willing to help?
1) rebuild with ./configure --enable-debug && make
2) ulimit -c unlimited
3) ./qjackctl
4) *make-it-crash* (core dumped)
5) gdb ./qjackctl core
Tell me what you find.
4:05 p.m.
David Baron wrote:
On Wednesday 11 July 2007, Rui Nuno Capela wrote:
Correct. But it should be either one, not both.
Sorry for my self-taught english :)
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
David Baron wrote:
Yes. More very minor things:
1. Jack is always started with qjackctl. I have that option not checked.
Does the
main top-left display says 'Started' or 'Active' (in bright
yellow over black) when you launch qjackctl?
12 Jul
12 Jul
9:09 a.m.
On Wednesday 11 July 2007, David Baron wrote:
May try tomorrow. See what happens. Was able to crash it but no "core"
file was produced.
Ran from within the debugger. Was not able to crash it after many tries.
As per a reply to another poster, here is the coredump from 5) core.8983
Program terminated with signal 11, Segmentation fault.
#0 0xb780fba2 in QObject::parent (this=0x0)
at ../../include/QtCore/../../src/corelib/kernel/qobject.h:213
213 ../../include/QtCore/../../src/corelib/kernel/qobject.h: No such file
or directory.
in ../../include/QtCore/../../src/corelib/kernel/qobject.h
If this were really not available, then it would not have compiled. However,
this is what I got.
On Wednesday 11 July 2007, Rui Nuno Capela wrote:
"Active"
Now this touches the icons as well!
The first run I tried this, icons were what was exected. The server did not
come up by itself and I had the red box. Hit start, got "starting" which
takes time. After I got rid of the -X command by having no "MIDI driver"
succeded in getting to "started" with the green arrow!
Runs after that, regardless of the "MIDI driver" setting, come up active with
the errant icons!! Stop yields blank white circle. Start returns immediately
to "active" with red arrow icon!
If I close the app.
killall jackd
rerun the app.
Comes up "stopped", red box.
Start --> "starting" --> "started" green arrow
Stop --> blanks black displa pane, blank white circle.
Start --> "active", red arrow.
If I check the "execute script after shutdown" as killall jackd, then stopping
and starting works the way I would expect with the correct icons.
Then I am be asked whether to terminate jackd on quitting.
If I leave and restart, then I get "active" with red arrow.
Stop goes to blank white circle.
Start goes to "starting" --> "started" green arrow ...
This should be useful information.
(Thanks for not killing the app on upper-right [x]. This was not correct
behavior for a "tray" app.)
David Baron wrote:
Yes. More very minor things:
1. Jack is always started with qjackctl. I have that option not
checked.
Does the main top-left display says 'Started' or 'Active' (in bright
yellow over black) when you launch qjackctl? 2. I have had the program crash out working the
connections (all-alsa)
pane. Happens when I touch the midi-through item.
This deserves some debugging. Are willing to help?
1) rebuild with ./configure --enable-debug && make
2) ulimit -c unlimited
3) ./qjackctl
4) *make-it-crash* (core dumped)
5) gdb ./qjackctl core
Tell me what you find.
1:59 p.m.
On Wednesday 11 July 2007, David Baron wrote:
May try tomorrow. See what happens. Was able to crash it but no "core"
file was produced.
Ran from within the debugger. Was not able to crash it after many tries.
As per a reply to another poster, here is the coredump from 5) core.8983
Program terminated with signal 11, Segmentation fault.
#0 0xb780fba2 in QObject::parent (this=0x0)
at ../../include/QtCore/../../src/corelib/kernel/qobject.h:213
213 ../../include/QtCore/../../src/corelib/kernel/qobject.h: No such file
or directory.
in ../../include/QtCore/../../src/corelib/kernel/qobject.h
As per you post use "bt"
(gdb) bt
#0 0xb780fba2 in QObject::parent (this=0x0)
at ../../include/QtCore/../../src/corelib/kernel/qobject.h:213
#1 0xb781cc0d in QWidget::parentWidget (this=0x0)
at ../../include/QtGui/../../src/gui/kernel/qwidget.h:949
#2 0xb7859ff1 in QWidget::window (this=0x0) at kernel/qwidget.cpp:3340
#3 0xb7850b65 in QWidget::topLevelWidget (this=0x0)
at ../../include/QtGui/../../src/gui/kernel/qwidget.h:287
#4 0xb785066f in QToolTip::showText (pos=@0xbfb4cfe0, text=@0x81ab66c, w=0x0,
rect=@0xbfb4cd34) at kernel/qtooltip.cpp:370
#5 0xb78507ad in QToolTip::showText (pos=@0xbfb4cfe0, text=@0x81ab66c, w=0x0)
at kernel/qtooltip.cpp:397
#6 0x0805bc68 in qjackctlClientListView::eventFilter (this=0x81c94d0,
pObject=0x81bbb88, pEvent=0xbfb4cfcc) at src/qjackctlConnect.cpp:818
#7 0xb78133c0 in QApplicationPrivate::notify_helper (this=0x812f198,
receiver=0x81bbb88, e=0xbfb4cfcc) at kernel/qapplication.cpp:3530
#8 0xb7814d5c in QApplication::notify (this=0xbfb4db60, receiver=0x82f47d0,
e=0xbfb4d1d0) at kernel/qapplication.cpp:3381
#9 0xb765955a in QCoreApplication::notifyInternal (this=0xbfb4db60,
receiver=0x82f47d0, event=0xbfb4d1d0) at kernel/qcoreapplication.cpp:509
#10 0xb7810177 in QCoreApplication::sendEvent (receiver=0x82f47d0,
event=0xbfb4d1d0)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:186
#11 0xb78171ac in QApplication::event (this=0xbfb4db60, e=0xbfb4d664)
at kernel/qapplication.cpp:2071
#12 0xb7813445 in QApplicationPrivate::notify_helper (this=0x812f198,
receiver=0xbfb4db60, e=0xbfb4d664) at kernel/qapplication.cpp:3538
#13 0xb781375e in QApplication::notify (this=0xbfb4db60, receiver=0xbfb4db60,
e=0xbfb4d664) at kernel/qapplication.cpp:3097
#14 0xb765955a in QCoreApplication::notifyInternal (this=0xbfb4db60,
receiver=0xbfb4db60, event=0xbfb4d664) at kernel/qcoreapplication.cpp:509
#15 0xb765c923 in QCoreApplication::sendEvent (receiver=0xbfb4db60,
event=0xbfb4d664)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:186
#16 0xb76858c9 in QTimerInfoList::activateTimers (this=0x8136fcc)
at kernel/qeventdispatcher_unix.cpp:541
#17 0xb7682848 in timerSourceDispatch (source=0x8136f98)
at kernel/qeventdispatcher_glib.cpp:142
#18 0xb715aa01 in g_main_context_dispatch ()
from /opt/kdedir/lib/libglib-2.0.so.0
#19 0xb715da76 in g_main_context_iterate ()
from /opt/kdedir/lib/libglib-2.0.so.0
#20 0xb715dff7 in g_main_context_iteration ()
from /opt/kdedir/lib/libglib-2.0.so.0
#21 0xb7682210 in QEventDispatcherGlib::processEvents (this=0x8133e48,
flags=@0xbfb4d7d8) at kernel/qeventdispatcher_glib.cpp:327
#22 0xb78aa188 in QGuiEventDispatcherGlib::processEvents (this=0x8133e48,
flags=@0xbfb4d80c) at kernel/qguieventdispatcher_glib.cpp:178
#23 0xb76564e2 in QEventLoop::processEvents (this=0xbfb4d880,
flags=@0xbfb4d844)
at kernel/qeventloop.cpp:126
#24 0xb7656664 in QEventLoop::exec (this=0xbfb4d880, flags=@0xbfb4d888)
at kernel/qeventloop.cpp:168
#25 0xb7659ca7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:729
#26 0xb7812fc8 in QApplication::exec () at kernel/qapplication.cpp:3035
#27 0x08057c39 in main (arg from /opt/kdedir/lib/libglib-2.0.so.0
#21 0xb7682210 in QEventDispatcherGlib::processEvents (this=0x8133e48,
flags=@0xbfb4d7d8) at kernel/qeventdispatcher_glib.cpp:327
#22 0xb78aa188 in QGuiEventDispatcherGlib::processEvents (this=0x8133e48,
flags=@0xbfb4d80c) at kernel/qguieventdispatcher_glib.cpp:178
#23 0xb76564e2 in QEventLoop::processEvents (this=0xbfb4d880,
flags=@0xbfb4d844)
at kernel/qeventloop.cpp:126
#24 0xb7656664 in QEventLoop::exec (this=0xbfb4d880, flags=@0xbfb4d888)
at kernel/qeventloop.cpp:168
#25 0xb7659ca7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:729
#26 0xb7812fc8 in QApplication::exec () at kernel/qapplication.cpp:3035
#27 0x08057c39 in main (argc=Cannot access memory at address 0x0
) at src/main.cpp:89
On Wednesday 11 July 2007, Rui Nuno Capela wrote:
"Active"
Now this touches the icons as well!
The first run I tried this, icons were what was exected. The server did not
come up by itself and I had the red box. Hit start, got "starting" which
takes time. After I got rid of the -X command by having no "MIDI driver"
succeded in getting to "started" with the green arrow!
Runs after that, regardless of the "MIDI driver" setting, come up active with
the errant icons!! Stop yields blank white circle. Start returns immediately
to "active" with red arrow icon!
If I close the app.
killall jackd
rerun the app.
Comes up "stopped", red box.
Start --> "starting" --> "started" green arrow
Stop --> blanks black displa pane, blank white circle.
Start --> "active", red arrow.
If I check the "execute script after shutdown" as killall jackd, then stopping
and starting works the way I would expect with the correct icons.
Then I am be asked whether to terminate jackd on quitting.
If I leave and restart, then I get "active" with red arrow.
Stop goes to blank white circle.
Start goes to "starting" --> "started" green arrow ...
This should be useful information.
(Thanks for not killing the app on upper-right [x]. This was not correct
behavior for a "tray" app.)
David Baron wrote:
Yes. More very minor things:
1. Jack is always started with qjackctl. I have that option not
checked.
Does the main top-left display says 'Started' or 'Active' (in bright
yellow over black) when you launch qjackctl? 2. I have had the program crash out working the
connections (all-alsa)
pane. Happens when I touch the midi-through item.
This deserves some debugging. Are willing to help?
1) rebuild with ./configure --enable-debug && make
2) ulimit -c unlimited
3) ./qjackctl
4) *make-it-crash* (core dumped)
5) gdb ./qjackctl core
Tell me what you find. 
11 Jul
11 Jul
6:40 p.m.
2. I have had
the program crash out working the connections (all-alsa) pane.
Happens when I touch the midi-through item.
This deserves some debugging. Are willing to help?
1) rebuild with ./configure --enable-debug && make
2) ulimit -c unlimited
3) ./qjackctl
4) *make-it-crash* (core dumped)
5) gdb ./qjackctl core
Tell me what you find.
12 Jul
12 Jul
3:32 a.m.
On Wed, July 11, 2007 23:39, David Adler wrote:
>>> 2. I have had the program crash out working the connections
>>> (all-alsa) pane.
>>> Happens when I touch the midi-through item.
>> >> >
>> This deserves some debugging. Are willing to help?
>> 1) rebuild with ./configure --enable-debug && make
>> 2) ulimit -c unlimited
>> 3) ./qjackctl
>> 4) *make-it-crash* (core dumped)
>> 5) gdb ./qjackctl core
> >
>> Tell me what you find.
> >
> I get segfaults as well - they seem related to (dis-)connecting things
> in the alsa-tab, here not nessesarily with the midi-through ports
> involved.
> Following the above debugging-advice
gives:
> minos@digital:/usr/src/qjackctl-0.3.0$ ulimit -c unlimited
> minos@digital:/usr/src/qjackctl-0.3.0$ ./qjackctl
> Warning: no locale found: /usr/local/share/locale/qjackctl_en_US.qm
> Segmentation fault (core dumped)
> minos@digital:/usr/src/qjackctl-0.3.0$ gdb ./qjackctl core
> GNU gdb 6.4.90-debian
> Copyright (C) 2006 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are welcome to change it and/or distribute copies of it under certain
> conditions. Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for
> details. This GDB was configured as "i486-linux-gnu"...Using host
> libthread_db library "/lib/i686/cmov/libthread_db.so.1".
> /usr/src/qjackctl-0.3.0/core: No such file
or directory.
> (gdb)
> What about 'core'? Sorry if this is silly, its my first debugging.
> What to change/read for gdb to work? 'man gdb' did not help me.
Some systems have this "core" file suffixed with something else (e.g. pid)
or/and might be located on the current directory where qjackctl was set
when the segfault occurred.
Please, locate it under your home directory with:
find ~/ -name "core*" -ls
check the correct timestamp and then play it again with
gdb ./qjackctl /path/to/core.file
and send me the complete output. Ah, I forgot, that under the gdb prompt,
after it finds the correct point of segfault, you type "bt" (for
backtrace) and enter. Send me the additional trace.
I just can't reproduce this segfaults on any of my trials, no matter how
much I try. Please report whether the crashes are systematically
reproducible and in that case, which are the minimum set of steps to get
one.
> Something else: Alt+c doesn't connect
things here while Alt+d and Alt+a
> work properly.
Noted. Will check and fix. Thanks.
> by the way, the gui looks the way it is supposed to here on debian testing
> & evilwm
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
1:23 p.m.
Rui Nuno Capela wrote:
gdb ./qjackctl /path/to/core.file
and send me the complete output. Ah, I forgot, that under the gdb prompt,
after it finds the correct point of segfault, you type "bt" (for
backtrace) and enter. Send me the additional trace.
I just can't reproduce this segfaults on any of my trials, no matter how
much I try. Please report whether the crashes are systematically
reproducible and in that case, which are the minimum set of steps to get
one.
the minimum set of steps was starting the app, opening the 'connections'
child window and expanding the view of one of the midi-through-items. A
fiew seconds later the crash documented below appeard.
I did not (yet) get any crash without the alsa-tab involved, everything
ran stable for more than 2 h, but within the last hour i was not able to
reproduce any crash, no matter how i treated the whole app/alsa
connections. Seems all rather unsystematically
the output:
minos@digital:~/qjackctl-0.3.0$ ./qjackctl
Warning: no locale found: /usr/local/share/locale/qjackctl_en_US.qm
Segmentation fault (core dumped)
minos@digital:~/qjackctl-0.3.0$ gdb ./qjackctl core.8274
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db
library "/lib/i686/cmov/libthread_db.so.1".
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/libjack.so.0...done.
Loaded symbols for /usr/lib/libjack.so.0
Reading symbols from /usr/lib/libasound.so.2...done.
Loaded symbols for /usr/lib/libasound.so.2
Reading symbols from /lib/i686/cmov/libpthread.so.0...done.
Loaded symbols for /lib/i686/cmov/libpthread.so.0
Reading symbols from /usr/lib/libQtXml.so.4...done.
Loaded symbols for /usr/lib/libQtXml.so.4
Reading symbols from /usr/lib/libQtGui.so.4...done.
Loaded symbols for /usr/lib/libQtGui.so.4
Reading symbols from /usr/lib/libQtCore.so.4...done.
Loaded symbols for /usr/lib/libQtCore.so.4
Reading symbols from /usr/lib/libstdc++.so.6...done.
Loaded symbols for /usr/lib/libstdc++.so.6
Reading symbols from /lib/i686/cmov/libm.so.6...done.
Loaded symbols for /lib/i686/cmov/libm.so.6
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/i686/cmov/libc.so.6...done.
Loaded symbols for /lib/i686/cmov/libc.so.6
Reading symbols from /usr/lib/libX11.so.6...done.
Loaded symbols for /usr/lib/libX11.so.6
Reading symbols from /lib/i686/cmov/librt.so.1...done.
Loaded symbols for /lib/i686/cmov/librt.so.1
Reading symbols from /lib/i686/cmov/libdl.so.2...done.
Loaded symbols for /lib/i686/cmov/libdl.so.2
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/libfontconfig.so.1...done.
Loaded symbols for /usr/lib/libfontconfig.so.1
Reading symbols from /usr/lib/libz.so.1...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /usr/lib/libgthread-2.0.so.0...done.
Loaded symbols for /usr/lib/libgthread-2.0.so.0
Reading symbols from /usr/lib/libglib-2.0.so.0...done.
Loaded symbols for /usr/lib/libglib-2.0.so.0
Reading symbols from /usr/lib/libaudio.so.2...done.
Loaded symbols for /usr/lib/libaudio.so.2
Reading symbols from /usr/lib/libXt.so.6...done.
Loaded symbols for /usr/lib/libXt.so.6
Reading symbols from /usr/lib/libpng12.so.0...done.
Loaded symbols for /usr/lib/libpng12.so.0
Reading symbols from /usr/lib/libSM.so.6...done.
Loaded symbols for /usr/lib/libSM.so.6
Reading symbols from /usr/lib/libICE.so.6...done.
Loaded symbols for /usr/lib/libICE.so.6
Reading symbols from /usr/lib/libXi.so.6...done.
Loaded symbols for /usr/lib/libXi.so.6
Reading symbols from /usr/lib/libXrender.so.1...done.
Loaded symbols for /usr/lib/libXrender.so.1
Reading symbols from /usr/lib/libXrandr.so.2...done.
Loaded symbols for /usr/lib/libXrandr.so.2
Reading symbols from /usr/lib/libXfixes.so.3...done.
Loaded symbols for /usr/lib/libXfixes.so.3
Reading symbols from /usr/lib/libXcursor.so.1...done.
Loaded symbols for /usr/lib/libXcursor.so.1
Reading symbols from /usr/lib/libXinerama.so.1...done.
Loaded symbols for /usr/lib/libXinerama.so.1
Reading symbols from /usr/lib/libfreetype.so.6...done.
Loaded symbols for /usr/lib/libfreetype.so.6
Reading symbols from /usr/lib/libXext.so.6...done.
Loaded symbols for /usr/lib/libXext.so.6
Reading symbols from /usr/lib/libXau.so.6...done.
Loaded symbols for /usr/lib/libXau.so.6
Reading symbols from /usr/lib/libXdmcp.so.6...done.
Loaded symbols for /usr/lib/libXdmcp.so.6
Reading symbols from /usr/lib/libexpat.so.1...done.
Loaded symbols for /usr/lib/libexpat.so.1
Reading symbols from /usr/lib/gconv/UTF-16.so...done.
Loaded symbols for /usr/lib/gconv/UTF-16.so
Reading symbols from /usr/lib/qt4/plugins/imageformats/libqgif.so...done.
Loaded symbols for /usr/lib/qt4/plugins/imageformats/libqgif.so
Reading symbols from /usr/lib/qt4/plugins/imageformats/libqjpeg.so...done.
Loaded symbols for /usr/lib/qt4/plugins/imageformats/libqjpeg.so
Reading symbols from /usr/lib/libjpeg.so.62...done.
Loaded symbols for /usr/lib/libjpeg.so.62
Reading symbols from /usr/lib/qt4/plugins/imageformats/libqmng.so...done.
Loaded symbols for /usr/lib/qt4/plugins/imageformats/libqmng.so
Reading symbols from /usr/lib/libmng.so.1...done.
Loaded symbols for /usr/lib/libmng.so.1
Reading symbols from /usr/lib/liblcms.so.1...done.
Loaded symbols for /usr/lib/liblcms.so.1
Reading symbols from /usr/lib/qt4/plugins/imageformats/libqsvg.so...done.
Loaded symbols for /usr/lib/qt4/plugins/imageformats/libqsvg.so
Reading symbols from /usr/lib/libQtSvg.so.4...done.
Loaded symbols for /usr/lib/libQtSvg.so.4
Reading symbols from /usr/lib/qt4/plugins/imageformats/libqtiff.so...done.
Loaded symbols for /usr/lib/qt4/plugins/imageformats/libqtiff.so
Core was generated by `./qjackctl'.
Program terminated with signal 11, Segmentation fault.
#0 0xb7783ba2 in operator new () from /usr/lib/libQtGui.so.4
(gdb) bt
#0 0xb7783ba2 in operator new () from /usr/lib/libQtGui.so.4
#1 0xb7790c0d in QApplicationPrivate::QApplicationPrivate () from
/usr/lib/libQtGui.so.4
#2 0xb77cdff1 in QWidget::window () from /usr/lib/libQtGui.so.4
#3 0xb77c4b65 in QToolTip::showText () from /usr/lib/libQtGui.so.4
#4 0xb77c466f in QToolTip::showText () from /usr/lib/libQtGui.so.4
#5 0xb77c47ad in QToolTip::showText () from /usr/lib/libQtGui.so.4
#6 0x0805bc16 in qjackctlClientListView::eventFilter (this=0x81a1d68,
pObject=0x818e898, pEvent=0xbfc7ace0) at src/qjackctlConnect.cpp:808
#7 0xb77873c0 in QApplicationPrivate::notify_helper () from
/usr/lib/libQtGui.so.4
#8 0xb7788d5c in QApplication::notify () from /usr/lib/libQtGui.so.4
#9 0xb75cd55a in QCoreApplication::notifyInternal () from
/usr/lib/libQtCore.so.4
#10 0xb7784177 in operator new () from /usr/lib/libQtGui.so.4
#11 0xb778b1ac in QApplication::event () from /usr/lib/libQtGui.so.4
#12 0xb7787445 in QApplicationPrivate::notify_helper () from
/usr/lib/libQtGui.so.4
#13 0xb778775e in QApplication::notify () from /usr/lib/libQtGui.so.4
#14 0xb75cd55a in QCoreApplication::notifyInternal () from
/usr/lib/libQtCore.so.4
#15 0xb75d0923 in QCoreApplicationPrivate::appName () from
/usr/lib/libQtCore.so.4
#16 0xb75f98c9 in QEventDispatcherUNIX::registerTimer () from
/usr/lib/libQtCore.so.4
#17 0xb75f6848 in QEventDispatcherGlib::~QEventDispatcherGlib () from
/usr/lib/libQtCore.so.4
#18 0xb70cfa62 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb70d2a2f in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#20 0xb70d2f95 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb75f6210 in QEventDispatcherGlib::processEvents () from
/usr/lib/libQtCore.so.4
#22 0xb781e188 in QX11Info::copyX11Data () from /usr/lib/libQtGui.so.4
#23 0xb75ca4e2 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#24 0xb75ca664 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#25 0xb75cdca7 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#26 0xb7786fc8 in QApplication::exec () from /usr/lib/libQtGui.so.4
#27 0x08057c56 in main (argc=Cannot access memory at address 0x0
) at src/main.cpp:90
(gdb)
1:29 p.m.
David Adler wrote:
Rui Nuno Capela wrote:
but the v0.3.0.5 seems not to be crashing here anymore, at least i am
not able to reproduce!
cheers,
doc
gdb ./qjackctl /path/to/core.file
and send me the complete output. Ah, I forgot, that under the gdb
prompt,
after it finds the correct point of segfault, you type "bt" (for
backtrace) and enter. Send me the additional trace.
I just can't reproduce this segfaults on any of my trials, no matter how
much I try. Please report whether the crashes are systematically
reproducible and in that case, which are the minimum set of steps to get
one.
the minimum set of steps was starting the app, opening the
'connections' child window and expanding the view of one of the
midi-through-items. A fiew seconds later the crash documented below
appeard.
I did not (yet) get any crash without the alsa-tab involved,
everything ran stable for more than 2 h, but within the last hour i
was not able to reproduce any crash, no matter how i treated the whole
app/alsa connections. Seems all rather unsystematically
5:58 p.m.
David Adler wrote:
the minimum set of steps was starting the app, opening
the 'connections'
child window and expanding the view of one of the midi-through-items. A
fiew seconds later the crash documented below appeard.
I did not (yet) get any crash without the alsa-tab involved, everything
ran stable for more than 2 h, but within the last hour i was not able to
reproduce any crash, no matter how i treated the whole app/alsa
connections. Seems all rather unsystematically
the output:
<...>
(gdb) bt
#0 0xb7783ba2 in operator new () from /usr/lib/libQtGui.so.4
#1 0xb7790c0d in QApplicationPrivate::QApplicationPrivate () from
/usr/lib/libQtGui.so.4
#2 0xb77cdff1 in QWidget::window () from /usr/lib/libQtGui.so.4
#3 0xb77c4b65 in QToolTip::showText () from /usr/lib/libQtGui.so.4
#4 0xb77c466f in QToolTip::showText () from /usr/lib/libQtGui.so.4
#5 0xb77c47ad in QToolTip::showText () from /usr/lib/libQtGui.so.4
#6 0x0805bc16 in qjackctlClientListView::eventFilter (this=0x81a1d68,
pObject=0x818e898, pEvent=0xbfc7ace0) at src/qjackctlConnect.cpp:808
<...>
Ah. Tooltips again in the same place. We're getting somewhere...
Thanks David.
BBL
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
13 Jul
13 Jul
7:54 a.m.
Rui Nuno Capela wrote:
This deserves some debugging. Are willing to help?
1) rebuild with ./configure --enable-debug && make
2) ulimit -c unlimited
3) ./qjackctl
4) *make-it-crash* (core dumped)
5) gdb ./qjackctl core
Tell me what you find.
hi, the version 0.3.0.5 is crashing here regularly when the connection
window is open.
here is the backtrace:
nwhiskey@murija2:~$ gdb /usr/bin/qjackctl core.9761
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db
library "/lib/libthread_db.so.1".
warning: Can't read pathname for load map: Eingabe-/Ausgabefehler.
Reading symbols from /usr/lib/libjack.so.0...done.
Loaded symbols for /usr/share/qt4/lib/libjack.so.0
Reading symbols from /usr/lib/libasound.so.2...done.
Loaded symbols for /usr/share/qt4/lib/libasound.so.2
Reading symbols from /lib/libpthread.so.0...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /usr/lib/libQtXml.so.4...done.
Loaded symbols for /usr/share/qt4/lib/libQtXml.so.4
Reading symbols from /usr/lib/libQtGui.so.4...done.
Loaded symbols for /usr/share/qt4/lib/libQtGui.so.4
Reading symbols from /usr/lib/libQtCore.so.4...done.
Loaded symbols for /usr/share/qt4/lib/libQtCore.so.4
Reading symbols from /usr/lib/libstdc++.so.6...done.
Loaded symbols for /usr/share/qt4/lib/libstdc++.so.6
Reading symbols from /lib/libm.so.6...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /usr/lib/libX11.so.6...done.
Loaded symbols for /usr/share/qt4/lib/libX11.so.6
Reading symbols from /lib/librt.so.1...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/libfontconfig.so.1...done.
Loaded symbols for /usr/share/qt4/lib/libfontconfig.so.1
Reading symbols from /usr/lib/libz.so.1...done.
Loaded symbols for /usr/share/qt4/lib/libz.so.1
Reading symbols from /usr/lib/libgthread-2.0.so.0...done.
Loaded symbols for /usr/share/qt4/lib/libgthread-2.0.so.0
Reading symbols from /usr/lib/libglib-2.0.so.0...done.
Loaded symbols for /usr/share/qt4/lib/libglib-2.0.so.0
Reading symbols from /usr/lib/libaudio.so.2...done.
Loaded symbols for /usr/share/qt4/lib/libaudio.so.2
Reading symbols from /usr/lib/libXt.so.6...done.
Loaded symbols for /usr/share/qt4/lib/libXt.so.6
Reading symbols from /usr/lib/libpng12.so.0...done.
Loaded symbols for /usr/share/qt4/lib/libpng12.so.0
Reading symbols from /usr/lib/libSM.so.6...done.
Loaded symbols for /usr/share/qt4/lib/libSM.so.6
Reading symbols from /usr/lib/libICE.so.6...done.
Loaded symbols for /usr/share/qt4/lib/libICE.so.6
Reading symbols from /usr/lib/libXi.so.6...done.
Loaded symbols for /usr/share/qt4/lib/libXi.so.6
Reading symbols from /usr/lib/libXrender.so.1...done.
Loaded symbols for /usr/share/qt4/lib/libXrender.so.1
Reading symbols from /usr/lib/libXrandr.so.2...done.
Loaded symbols for /usr/share/qt4/lib/libXrandr.so.2
Reading symbols from /usr/lib/libXfixes.so.3...done.
Loaded symbols for /usr/share/qt4/lib/libXfixes.so.3
Reading symbols from /usr/lib/libXcursor.so.1...done.
Loaded symbols for /usr/share/qt4/lib/libXcursor.so.1
Reading symbols from /usr/lib/libXinerama.so.1...done.
Loaded symbols for /usr/share/qt4/lib/libXinerama.so.1
Reading symbols from /usr/lib/libfreetype.so.6...done.
Loaded symbols for /usr/share/qt4/lib/libfreetype.so.6
Reading symbols from /usr/lib/libXext.so.6...done.
Loaded symbols for /usr/share/qt4/lib/libXext.so.6
Reading symbols from /usr/lib/libXau.so.6...done.
Loaded symbols for /usr/share/qt4/lib/libXau.so.6
Reading symbols from /usr/lib/libXdmcp.so.6...done.
Loaded symbols for /usr/share/qt4/lib/libXdmcp.so.6
Reading symbols from /usr/lib/libexpat.so.1...done.
Loaded symbols for /usr/share/qt4/lib/libexpat.so.1
Reading symbols from /usr/lib/gconv/UTF-16.so...done.
Loaded symbols for /usr/lib/gconv/UTF-16.so
Reading symbols from /usr/lib/gconv/ISO8859-15.so...done.
Loaded symbols for /usr/lib/gconv/ISO8859-15.so
Reading symbols from /usr/lib/qt4/plugins/imageformats/libqgif.so...done.
Loaded symbols for /usr/lib/qt4/plugins/imageformats/libqgif.so
Reading symbols from /usr/lib/qt4/plugins/imageformats/libqjpeg.so...done.
Loaded symbols for /usr/lib/qt4/plugins/imageformats/libqjpeg.so
Reading symbols from /usr/lib/libjpeg.so.62...done.
Loaded symbols for /usr/share/qt4/lib/libjpeg.so.62
Reading symbols from /usr/lib/qt4/plugins/imageformats/libqmng.so...done.
Loaded symbols for /usr/lib/qt4/plugins/imageformats/libqmng.so
Reading symbols from /usr/lib/libmng.so.1...done.
Loaded symbols for /usr/share/qt4/lib/libmng.so.1
Reading symbols from /usr/lib/liblcms.so.1...done.
Loaded symbols for /usr/share/qt4/lib/liblcms.so.1
Reading symbols from /usr/lib/qt4/plugins/imageformats/libqsvg.so...done.
Loaded symbols for /usr/lib/qt4/plugins/imageformats/libqsvg.so
Reading symbols from /usr/lib/libQtSvg.so.4...done.
Loaded symbols for /usr/share/qt4/lib/libQtSvg.so.4
Reading symbols from /usr/lib/qt4/plugins/imageformats/libqtiff.so...done.
Loaded symbols for /usr/lib/qt4/plugins/imageformats/libqtiff.so
Failed to read a valid object file image from memory.
Core was generated by `/usr/bin/qjackctl'.
Program terminated with signal 11, Segmentation fault.
#0 0xb7778ba2 in operator new () from /usr/share/qt4/lib/libQtGui.so.4
(gdb) thread apply all bt
Thread 3 (process 9769):
#0 0xb7333897 in select () from /lib/libc.so.6
#1 0xb75a822e in QFSFileEngine::remove () from
#/usr/share/qt4/lib/libQtCore.so.4
#2 0xb750dd33 in QThread::idealThreadCount () from
#/usr/share/qt4/lib/libQtCore.so.4
#3 0xb7e31183 in start_thread () from /lib/libpthread.so.0
#4 0xb733aa7e in clone () from /lib/libc.so.6
Thread 2 (process 9787):
#0 0xb7330e29 in poll () from /lib/libc.so.6
#1 0xb7f0b4bb in jack_client_thread (arg=0x8237368) at client.c:1309
#2 0xb7f11a30 in jack_thread_proxy (varg=0x8163ab0) at thread.c:111
#3 0xb7e31183 in start_thread () from /lib/libpthread.so.0
#4 0xb733aa7e in clone () from /lib/libc.so.6
Thread 1 (process 9761):
#0 0xb7778ba2 in operator new () from /usr/share/qt4/lib/libQtGui.so.4
#1 0xb7785c0d in QApplicationPrivate::QApplicationPrivate () from
#/usr/share/qt4/lib/libQtGui.so.4
#2 0xb77c2ff1 in QWidget::window () from /usr/share/qt4/lib/libQtGui.so.4
#3 0xb77b9b65 in QToolTip::showText () from
#/usr/share/qt4/lib/libQtGui.so.4
#4 0xb77b966f in QToolTip::showText () from
#/usr/share/qt4/lib/libQtGui.so.4
#5 0xb77b97ad in QToolTip::showText () from
#/usr/share/qt4/lib/libQtGui.so.4
#6 0x0805be26 in qjackctlClientListView::eventFilter (this=0x8186160,
#pObject=0x8169cb8, pEvent=0xbf8bd720) at src/qjackctlConnect.cpp:825
#7 0xb777c3c0 in QApplicationPrivate::notify_helper () from
#/usr/share/qt4/lib/libQtGui.so.4
#8 0xb777dd5c in QApplication::notify () from
#/usr/share/qt4/lib/libQtGui.so.4
#9 0xb75c255a in QCoreApplication::notifyInternal () from
#/usr/share/qt4/lib/libQtCore.so.4
#10 0xb7779177 in operator new () from /usr/share/qt4/lib/libQtGui.so.4
#11 0xb77801ac in QApplication::event () from
#/usr/share/qt4/lib/libQtGui.so.4
#12 0xb777c445 in QApplicationPrivate::notify_helper () from
#/usr/share/qt4/lib/libQtGui.so.4
#13 0xb777c75e in QApplication::notify () from
#/usr/share/qt4/lib/libQtGui.so.4
#14 0xb75c255a in QCoreApplication::notifyInternal () from
#/usr/share/qt4/lib/libQtCore.so.4
#15 0xb75c5923 in QCoreApplicationPrivate::appName () from
#/usr/share/qt4/lib/libQtCore.so.4
#16 0xb75ee8c9 in QEventDispatcherUNIX::registerTimer () from
#/usr/share/qt4/lib/libQtCore.so.4
#17 0xb75eb848 in QEventDispatcherGlib::~QEventDispatcherGlib () from
#/usr/share/qt4/lib/libQtCore.so.4
#18 0xb70c4a62 in g_main_context_dispatch () from
#/usr/share/qt4/lib/libglib-2.0.so.0
#19 0xb70c7a2f in g_main_context_check () from
#/usr/share/qt4/lib/libglib-2.0.so.0
#20 0xb70c7f95 in g_main_context_iteration () from
#/usr/share/qt4/lib/libglib-2.0.so.0
#21 0xb75eb210 in QEventDispatcherGlib::processEvents () from
#/usr/share/qt4/lib/libQtCore.so.4
#22 0xb7813188 in QX11Info::copyX11Data () from
#/usr/share/qt4/lib/libQtGui.so.4
#23 0xb75bf4e2 in QEventLoop::processEvents () from
#/usr/share/qt4/lib/libQtCore.so.4
#24 0xb75bf664 in QEventLoop::exec () from /usr/share/qt4/lib/libQtCore.so.4
#25 0xb75c2ca7 in QCoreApplication::exec () from
#/usr/share/qt4/lib/libQtCore.so.4
#26 0xb777bfc8 in QApplication::exec () from
#/usr/share/qt4/lib/libQtGui.so.4
#27 0x08057e66 in main (argc=Cannot access memory at address 0x0
) at src/main.cpp:90
cheers,
doc
9:38 a.m.
On Fri, July 13, 2007 14:54, Dragan Noveski wrote:
Rui Nuno Capela wrote:
Thanks Dragan.
However I'm still failing to reproduce these crashes here. It sure is
related to the connections item tooltips, as at least one other user has
reported and posted a very identical trace.
Please, I need you to tell me some more: is it just a matter of hovering
the mouse pointer in the connections window panes? does it crash regularly
on all connections tabs, ie. Audio, MIDI and ALSA, or just one in
particular?
There is a certain workaround to fix this, though, about getting rid of
the client/port items tooltips altogether: just comment the whole body of
qjackctlConnect::eventFilter() function, leaving in only the last return
statement (qjackctlConnect.cpp, lines 815-840). Not a nice fix I may say
:(
All you fellows that are currently experiencing similar crashes should
raise your hands and tell what in the world you have in common to make
this happen like so. Please?
Thanx
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
This deserves some debugging. Are willing to help?
1) rebuild with ./configure --enable-debug && make
2) ulimit -c unlimited
3) ./qjackctl
4) *make-it-crash* (core dumped)
5) gdb ./qjackctl core
Tell me what you find.
hi, the version 0.3.0.5 is crashing here regularly when the connection
window is open.
11:47 a.m.
Rui Nuno Capela wrote:
Thanks Dragan.
However I'm still failing to reproduce these crashes here. It sure is
related to the connections item tooltips, as at least one other user has
reported and posted a very identical trace.
Please, I need you to tell me some more: is it just a matter of hovering
the mouse pointer in the connections window panes? does it crash regularly
on all connections tabs, ie. Audio, MIDI and ALSA, or just one in
particular?
There is a certain workaround to fix this, though, about getting rid of
the client/port items tooltips altogether: just comment the whole body of
qjackctlConnect::eventFilter() function, leaving in only the last return
statement (qjackctlConnect.cpp, lines 815-840). Not a nice fix I may say
:(
All you fellows that are currently experiencing similar crashes should
raise your hands and tell what in the world you have in common to make
this happen like so. Please?
Thanx
Crashes appear as soon as the mouse pointer is hovering above any item
in any of the connections panes for more than about one second (not in
the MIDI-pane here, but it is empty in my case).
When the pane-tooltip is already visible and i move the pointer above an
item the crash occurs immediately.
If i am fast i can mark or expand things without crash.
So I can just confirm its tooltip-related - crash instead of tooltip.
The pane-tooltips work, its just about the item ones. I checked possibly
all others, they all show up.
debian testing, evilwm, version of qt4 is 4.3.0-2+b1, jackd 0.103.0-6
I try to raise my hand but sadly do not (yet) know what we crashers have
in common.
Tell me if i can give other information that might be relevant.
good luck,
d
12:10 p.m.
David Adler wrote:
Rui Nuno Capela wrote:
Yes, its item tooltip related, that I'm sure. What I don't know is why ;)
Thanks Dragan.
However I'm still failing to reproduce these crashes here. It sure is
related to the connections item tooltips, as at least one other user has
reported and posted a very identical trace.
Please, I need you to tell me some more: is it just a matter of hovering
the mouse pointer in the connections window panes? does it crash
regularly
on all connections tabs, ie. Audio, MIDI and ALSA, or just one in
particular?
There is a certain workaround to fix this, though, about getting rid of
the client/port items tooltips altogether: just comment the whole body of
qjackctlConnect::eventFilter() function, leaving in only the last return
statement (qjackctlConnect.cpp, lines 815-840). Not a nice fix I may say
:(
All you fellows that are currently experiencing similar crashes should
raise your hands and tell what in the world you have in common to make
this happen like so. Please?
Thanx
Crashes appear as soon as the mouse pointer is hovering above any item
in any of the connections panes for more than about one second (not in
the MIDI-pane here, but it is empty in my case).
When the pane-tooltip is already visible and i move the pointer above an
item the crash occurs immediately.
If i am fast i can mark or expand things without crash.
So I can just confirm its tooltip-related - crash instead of tooltip.
The pane-tooltips work, its just about the item ones. I checked possibly
all others, they all show up.
debian testing, evilwm, version of qt4 is 4.3.0-2+b1, jackd 0.103.0-6
I try to raise my hand but sadly do not (yet) know what we crashers have
in common.
Tell me if i can give other information that might be relevant.
It seems that the one thing in common is about that debian testing, and
perhaps qt4.3.0 -- I still have qt4.2.1 but already testing with qt4.3
in windows tho (where it's ok too, btw).
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
2:31 p.m.
David Adler wrote:
Rui Nuno Capela wrote:
david is right, as i see now, the
crash appears always when mouse is not
moving but being placed over any of clients name.
no matter if i try this in audio, midi or alsa tab.
Thanks Dragan.
However I'm still failing to reproduce these crashes here. It sure is
related to the connections item tooltips, as at least one other user has
reported and posted a very identical trace.
Please, I need you to tell me some more: is it just a matter of hovering
the mouse pointer in the connections window panes? does it crash
regularly
on all connections tabs, ie. Audio, MIDI and ALSA, or just one in
particular?
There is a certain workaround to fix this, though, about getting rid of
the client/port items tooltips altogether: just comment the whole
body of
qjackctlConnect::eventFilter() function, leaving in only the last return
statement (qjackctlConnect.cpp, lines 815-840). Not a nice fix I may say
:(
All you fellows that are currently experiencing similar crashes should
raise your hands and tell what in the world you have in common to make
this happen like so. Please?
Thanx
Crashes appear as soon as the mouse pointer is hovering above any item
in any of the connections panes for more than about one second (not in
the MIDI-pane here, but it is empty in my case). When the pane-tooltip
what is the
'pane-tooltip'?
is already visible and i move the pointer above an
item the crash
occurs immediately.
If i am fast i can mark or expand things without crash.
So I can just confirm its tooltip-related - crash instead of tooltip.
The pane-tooltips work, its just about the item ones. I checked
possibly all others, they all show up.
debian testing, evilwm, version of qt4 is 4.3.0-2+b1, jackd 0.103.0-6
i am usind
debian testing too, fluxbox, the same qt4 and
jackd-0.103.0-selfcomiled binary.
cheers,
doc
I try to raise my hand but sadly do not (yet) know what we crashers
have in common.
Tell me if i can give other information that might be relevant.
good luck,
d
14 Jul
14 Jul
2:01 p.m.
Dragan Noveski wrote:
David Adler wrote:
It seems to me that this libqt4-gui_4.3.0-2+b1 from debian testing
(lenny) is the one common denominator in these reported tooltip crashes.
I've been testing on debian etch, where its libqt4-gui_4.2.1-2+etch1
have no issues re. these crashes and any other, fwiw :)
Would it be too troublesome if at least one of you could regress to Qt4
4.2.1 as in etch ? Unless you really need it for the latest
bleeding-edge KDE4, there's no real need to have Qt 4.3 atm. But you
tell me if it's OK in checking this out just for the peace of (my) mind.
Thanks.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
debian testing, evilwm, version of qt4 is 4.3.0-2+b1, jackd 0.103.0-6
i am usind
debian testing too, fluxbox, the same qt4 and
jackd-0.103.0-selfcomiled binary.
cheers,
doc
>
> I try to raise my hand but sadly do not (yet) know what we crashers
> have in common. Tell me if i can give other information that might be relevant.
>
3:02 p.m.
Rui Nuno Capela wrote:
Dragan Noveski wrote:
Forget this last question.
I have certified on my own, and beyond any reasonable doubt, that
_it_is_ libqt4-gui_4.3.0-2+b1 on debian testing that is the culprit.
Taking advantage of the snapshot feature of virtualbox, I've taken the
chance to upgrade from debian etch to testing (lenny) and the reported
crashes suddenly start pouring :(.
Back in debian etch, libqt4-gui_4.2.1-2+etch1 all goes well and sane, as
suspected.
Thanks anyway.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
David Adler wrote:
It seems to me that this libqt4-gui_4.3.0-2+b1 from debian testing
(lenny) is the one common denominator in these reported tooltip crashes.
I've been testing on debian etch, where its libqt4-gui_4.2.1-2+etch1
have no issues re. these crashes and any other, fwiw :)
Would it be too troublesome if at least one of you could regress to Qt4
4.2.1 as in etch ? Unless you really need it for the latest
bleeding-edge KDE4, there's no real need to have Qt 4.3 atm. But you
tell me if it's OK in checking this out just for the peace of (my) mind.
debian testing, evilwm, version of qt4 is
4.3.0-2+b1, jackd 0.103.0-6
i am usind debian testing too, fluxbox, the same qt4
and
jackd-0.103.0-selfcomiled binary.
cheers,
doc
> I try to raise my hand but sadly do not (yet) know what we crashers
> have in common. Tell me if i can give other information that might be relevant.
>
15 Jul
15 Jul
7:45 a.m.
Rui Nuno Capela wrote:
Bye now
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
I have certified on my own, and beyond any reasonable doubt, that
_it_is_ libqt4-gui_4.3.0-2+b1 on debian testing that is the culprit.
Taking advantage of the snapshot feature of virtualbox, I've taken the
chance to upgrade from debian etch to testing (lenny) and the reported
crashes suddenly start pouring :(.
Back in debian etch, libqt4-gui_4.2.1-2+etch1 all goes well and sane, as
suspected.
Thanks anyway.
For those interested, on qjackctl-devel Ken Ellinwood took the plunge
and confirmed what is now certain:
Ken, would it be too troublesome if you could
regress to Qt4 4.2.1 as
in etch ? Unless you really need it for the latest bleeding-edge
KDE4, there's no real need to have Qt 4.3 atm.
Not a problem...
rockfish:/home/ken# apt-get remove --purge libqt4-core
The following packages will be REMOVED:
libqt4-core* libqt4-dev* libqt4-gui* libqt4-qt3support* libqt4-sql*
qt4-dev-tools* qt4-qtconfig*
Do you want to continue [Y/n]? Y
[edited /etc/apt/sources.list, commented out references to 'testing',
did 'apt-get update']
rockfish:/home/ken# apt-get install libqt4-core libqt4-dev libqt4-gui
libqt4-qt3support libqt4-sql qt4-dev-tools qt4-qtconfig
[snip]
Do you want to continue [Y/n]? Y
ken@rockfish:~/qjackctl-0.3.0$ dpkg -l | grep libqt4
libqt4-core 4.2.1-2+etch1 Qt 4 core non-GUI functionality library
libqt4-dev 4.2.1-2+etch1 Qt 4 development files
libqt4-gui 4.2.1-2+etch1 Qt 4 core GUI functionality runtime
libqt4-qt3support 4.2.1-2+etch1 Qt 3 compatibility library for Qt 4
libqt4-sql 4.1-2+etch1 Qt 4 SQL database module
I then re-enabled the code I had previously commented out, did
./configure, make, and make install.
the About/Qt window reports version 4.2.1 and the port names appear
over the tooltips in the Connection window without causing a segfault.
Cheers.
Ken
9:21 a.m.
Rui Nuno Capela wrote:
Rui Nuno Capela wrote:
Bye now
i can confirm this, downgrading to qt4-4.2.1-2+b1 from debian stable
solved the problem, no crashes anymore here!
cheers,
doc
I have certified on my own, and beyond any
reasonable doubt, that
_it_is_ libqt4-gui_4.3.0-2+b1 on debian testing that is the culprit.
Taking advantage of the snapshot feature of virtualbox, I've taken the
chance to upgrade from debian etch to testing (lenny) and the reported
crashes suddenly start pouring :(.
Back in debian etch, libqt4-gui_4.2.1-2+etch1 all goes well and sane, as
suspected.
Thanks anyway.
For those interested, on qjackctl-devel Ken Ellinwood took the plunge
and confirmed what is now certain:
Ken,
would it be too troublesome if you could regress to Qt4 4.2.1 as
in etch ? Unless you really need it for the latest bleeding-edge
KDE4, there's no real need to have Qt 4.3 atm.
Not a problem...
rockfish:/home/ken# apt-get remove --purge libqt4-core
The following packages will be REMOVED:
libqt4-core* libqt4-dev* libqt4-gui* libqt4-qt3support* libqt4-sql*
qt4-dev-tools* qt4-qtconfig*
Do you want to continue [Y/n]? Y
[edited /etc/apt/sources.list, commented out references to 'testing',
did 'apt-get update']
rockfish:/home/ken# apt-get install libqt4-core libqt4-dev libqt4-gui
libqt4-qt3support libqt4-sql qt4-dev-tools qt4-qtconfig
[snip]
Do you want to continue [Y/n]? Y
ken@rockfish:~/qjackctl-0.3.0$ dpkg -l | grep libqt4
libqt4-core 4.2.1-2+etch1 Qt 4 core non-GUI functionality library
libqt4-dev 4.2.1-2+etch1 Qt 4 development files
libqt4-gui 4.2.1-2+etch1 Qt 4 core GUI functionality runtime
libqt4-qt3support 4.2.1-2+etch1 Qt 3 compatibility library for Qt 4
libqt4-sql 4.1-2+etch1 Qt 4 SQL database module
I then re-enabled the code I had previously commented out, did
./configure, make, and make install.
the About/Qt window reports version 4.2.1 and the port names appear
over the tooltips in the Connection window without causing a segfault.
Cheers.
Ken
13 Jul
13 Jul
2:51 p.m.
Rui Nuno Capela wrote:
On Fri, July 13, 2007 14:54, Dragan Noveski wrote:
doing this seems to solve the issue here.
i do not have the knowledge to know, why this is not nice, but it
obviously solves the problem.
cheers,
doc
Rui Nuno Capela wrote:
Thanks Dragan.
However I'm still failing to reproduce these crashes here. It sure is
related to the connections item tooltips, as at least one other user has
reported and posted a very identical trace.
Please, I need you to tell me some more: is it just a matter of hovering
the mouse pointer in the connections window panes? does it crash regularly
on all connections tabs, ie. Audio, MIDI and ALSA, or just one in
particular?
There is a certain workaround to fix this, though, about getting rid of
the client/port items tooltips altogether: just comment the whole body of
qjackctlConnect::eventFilter() function, leaving in only the last return
statement (qjackctlConnect.cpp, lines 815-840). Not a nice fix I may say
:(
This deserves some debugging. Are willing to
help?
1) rebuild with ./configure --enable-debug && make
2) ulimit -c unlimited
3) ./qjackctl
4) *make-it-crash* (core dumped)
5) gdb ./qjackctl core
Tell me what you find.
hi, the version 0.3.0.5 is crashing here regularly when the connection
window is open.
All you fellows that are currently experiencing
similar crashes should
raise your hands and tell what in the world you have in common to make
this happen like so. Please?
Thanx
3:57 p.m.
Dragan Noveski wrote:
Not nice because it's just code/feature amputation, not a real fix.
However I'm getting more and more suspicious concerning the precise qt4
version on debian testing. IIRC David Adler said it was something like
4.3.0-2+b1. What is this exactly? Does the b1 mean beta-one in debianese
? That might ring some bells :)
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
There is a certain workaround to fix this, though, about getting rid of
the client/port items tooltips altogether: just comment the whole body of
qjackctlConnect::eventFilter() function, leaving in only the last return
statement (qjackctlConnect.cpp, lines 815-840). Not a nice fix I may say
:(
doing this seems to solve the issue here.
i do not have the knowledge to know, why this is not nice, but it
obviously solves the problem.
10 Jul
10 Jul
4:28 p.m.
Dominic Sacré escribió:
On 7/10/07, Rui Nuno Capela <rncbc(a)rncbc.org>
wrote:
Same happens to me in Debian Etch , and also I've got an error
message at the installation procces:
dpkg -i qjackctl-0.3.0/qjackctl_0.3.0-1_i386.deb
(Leyendo la base de datos ...
151345 ficheros y directorios instalados actualmente.)
Preparando para reemplazar qjackctl 0.2.21-1 (usando
.../qjackctl_0.3.0-1_i386.deb) ...
Desempaquetando el reemplazo de qjackctl ...
dpkg: problemas de dependencias impiden la configuración de qjackctl:
qjackctl depende de libjack; sin embargo:
El paquete `libjack' no está instalado.
qjackctl depende de libasound; sin embargo:
El paquete `libasound' no está instalado.
dpkg: error al procesar qjackctl (--install):
problemas de dependencias - se deja sin configurar
Se encontraron errores al procesar:
qjackctl
It says that libjack and libasound aren't installed , something that
is false . Finally it is installed an launch ok , but looks bad .
Saludos.
-- Carlos.
The new tarball has been replaced. However, SF
mirrors might lag in the
propagation, so that you'll probably still get the older one for a
while...
Just in case you want it now, the right one is also accessible from
here:
http://www.rncbc.org/jack/qjackctl-0.3.0.tar.gz
Thanks, compiles fine on Ubuntu Feisty now.
However, this is what qjackctl looks like:
http://das.nasophon.de/stuff/qjackctl.png
What happened here? I have qt-4.2.3... do I need 4.3? Or could the
problem be something else?
Dominic 
10:22 p.m.
El Martes, 10 de Julio de 2007 17:29, Carlos Pino escribió:
| Dominic Sacré escribió:
| > On 7/10/07, Rui Nuno Capela <rncbc(a)rncbc.org> wrote:
| >> The new tarball has been replaced. However, SF mirrors might lag in the
| >> propagation, so that you'll probably still get the older one for a
| >> while...
| >>
| >> Just in case you want it now, the right one is also accessible from
| >> here:
| >>
| >> http://www.rncbc.org/jack/qjackctl-0.3.0.tar.gz
| >
| > Thanks, compiles fine on Ubuntu Feisty now.
| >
| > However, this is what qjackctl looks like:
| > http://das.nasophon.de/stuff/qjackctl.png
| >
| > What happened here? I have qt-4.2.3... do I need 4.3? Or could the
| > problem be something else?
| >
| >
| > Dominic
|
| Same happens to me in Debian Etch , and also I've got an error
| message at the installation procces:
|
| dpkg -i qjackctl-0.3.0/qjackctl_0.3.0-1_i386.deb
| (Leyendo la base de datos ...
| 151345 ficheros y directorios instalados actualmente.)
| Preparando para reemplazar qjackctl 0.2.21-1 (usando
| .../qjackctl_0.3.0-1_i386.deb) ...
| Desempaquetando el reemplazo de qjackctl ...
| dpkg: problemas de dependencias impiden la configuración de qjackctl:
| qjackctl depende de libjack; sin embargo:
| El paquete `libjack' no está instalado.
| qjackctl depende de libasound; sin embargo:
| El paquete `libasound' no está instalado.
| dpkg: error al procesar qjackctl (--install):
| problemas de dependencias - se deja sin configurar
| Se encontraron errores al procesar:
| qjackctl
By the way:
I dont know if you allready know it Carlos, but you can set your locales to
english if you want to.
export LANGUAGE=en
export LC_ALL=en_US
export LANG=en_US
marcos@musix1:/$ locale
LANG=en_US
LANGUAGE=en
LC_CTYPE="en_US"
LC_NUMERIC="en_US"
LC_TIME="en_US"
LC_COLLATE="en_US"
LC_MONETARY="en_US"
LC_MESSAGES="en_US"
LC_PAPER="en_US"
LC_NAME="en_US"
LC_ADDRESS="en_US"
LC_TELEPHONE="en_US"
LC_MEASUREMENT="en_US"
LC_IDENTIFICATION="en_US"
LC_ALL=en_US
marcos@musix1:/$ apt-get install ardour2
E: Could not open lock file /var/lib/dpkg/lock - open (13 Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
marcos@musix1:/$ sudo apt-get install ardour2
Reading package lists... Done
Building dependency tree... Done
ardour2 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 44 not upgraded.
marcos@musix1:/$ apt-cache policy ardour2
ardour2:
Installed: 2.0.3-1
Candidate: 2.0.3-1
Version table:
*** 2.0.3-1 0
500 ftp://musix.ourproject.org ./ Packages
100 /var/lib/dpkg/status
marcos@musix1:/$
My 2 cents ;)
| It says that libjack and libasound aren't installed , something that
| is false . Finally it is installed an launch ok , but looks bad .
|
| Saludos.
| -- Carlos.
|
| _______________________________________________
| Linux-audio-user mailing list
| Linux-audio-user(a)lists.linuxaudio.org
| http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user
--
`&'
# Marcos Guglielmetti, co-director de
# Musix GNU+Linux, 100% Software Libre para artistas
_#_ http://www.musix.org.ar
(#)
/ O \ + archivos: ftp://musix.ourproject.org/pub/musix
( === ) Ecología: http://autosus.wordpress.com
`---' Personal: http://marcospcmusica.wordpress.com
"Nuestras clases dominantes han procurado siempre que los trabajadores no
tengan historia, no tengan doctrina, no tengan héroes ni mártires. Cada lucha
debe empezar de nuevo, separada de las luchas anteriores: la experiencia
colectiva se pierde, las lecciones se olvidan. La historia aparece así como
propiedad privada, cuyos dueños son los dueños de todas las otras cosas"
(Rodolfo Walsh)
6136
days inactive
6141
days old
linux-audio-user@lists.linuxaudio.org
44 comments
9 participants
participants (9)
-
Carlos Pino -
David Adler -
David Baron -
Dominic Sacré -
Dragan Noveski -
Geoff Beasley -
Marcos Guglielmetti -
Rui Nuno Capela -
Thomas Kuther