Menu
▾
▴
jazzplusplus-devel — Discussion Forum for Jazz Developers
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
(189) |
Apr
(40) |
May
(8) |
Jun
(6) |
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
(13) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(4) |
Feb
(1) |
Mar
(3) |
Apr
|
May
(7) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(8) |
Oct
(19) |
Nov
(19) |
Dec
(7) |
| 2007 |
Jan
(6) |
Feb
(6) |
Mar
(3) |
Apr
(6) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(1) |
| 2008 |
Jan
(19) |
Feb
(1) |
Mar
(40) |
Apr
(31) |
May
(174) |
Jun
(24) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(64) |
Dec
(17) |
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(5) |
Mar
(1) |
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(11) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Kevin C. <ke...@co...> - 2008-04-18 06:02:31
|
On 10 April 2008 at 6:51, Pete Stieber <pst...@ve...> wrote: > Would you be willing to post the offensive MIDI file to the > list or send it directly to me? Gosh, I forgot to send you the file! My inbox filled up recently (90 messages) and I'm getting ready for 3 gigs this weekend, hand drums in one, drumkit in another, and sound tech in another -- yes, 3 bands. I'm attaching the file. It's a demo song from the old Jazz++ 4.1.3 release from years back. You might want to try to play a few of those. I have all the old demos, if you want some. Actually, I have hundreds of MIDI files. > I could run it using a debugger on a different OS (the Windows > version works too) and see what is causing the problem. No > application should cause the machine to lockup. Core dump for > sure, but not lockup the kernel. Agreed. > I could also try playing the file using gdb on Fedora 8. I've > never had Jazz++ (or any other application) lockup Fedora. The only time I've had an application on Linux lock up a system is when it turned out that I was using the wrong RAM for my vintage of motherboard. Was that EVER hard to figure out; it took me over a year. > I'll be heading off to work soon, but if you can send me the > file, I'll look at it tonight. > > Thanks again for the testing, Sorry again to be so delinquent..... -- Kevin |
|
From: Pete S. <pst...@ve...> - 2008-04-10 13:50:21
|
KC = Kevin Cosgrove KC> I'm attaching what there is of a log file from KC> my attempt at playing a .mid file before my KC> machine locked up. I don't see anything odd, KC> so maybe the offensive thing didn't get captured? KC> KC> Sorry.... Kevin, Would you be willing to post the offensive MIDI file to the list or send it directly to me? I could run it using a debugger on a different OS (the Windows version works too) and see what is causing the problem. No application should cause the machine to lockup. Core dump for sure, but not lockup the kernel. I could also try playing the file using gdb on Fedora 8. I've never had Jazz++ (or any other application) lockup Fedora. I'll be heading off to work soon, but if you can send me the file, I'll look at it tonight. Thanks again for the testing, Pete |
|
From: Kevin C. <ke...@co...> - 2008-04-10 05:53:47
|
On 9 April 2008 at 15:54, Pete Stieber <pst...@ve...> wrote: > KC> I opened the Harmony Browser, and it looks like > KC> what I remember so fondly. One thing that seems > KC> busted with it is that the "close" choice under its > KC> "File" menu doesn't close the window. > > Thanks for the bug report. I just committed a fix for that. You can... > > 1. Update your source directory using svn. > 2. Change directory to your Build directory and type "make". > 3. Copy the resulting Jazz++ binary (called "jazz" in the src directory) > over the one in your existing TestInstall/bin directory. > > And you should be ready to test the "File | Close" fix. The bug is nicely squashed. Thanks! -- Kevin |
|
From: Kevin C. <ke...@co...> - 2008-04-10 05:50:19
|
Pete, I'm attaching what there is of a log file from my attempt at playing a .mid file before my machine locked up. I don't see anything odd, so maybe the offensive thing didn't get captured? Sorry.... -- Kevin |
|
From: Kevin C. <ke...@co...> - 2008-04-10 04:02:47
|
On 9 April 2008 at 15:54, Pete Stieber <pst...@ve...> wrote: > Don't expect too much functionality as we are "early in the > development process" ;-) You should be able to play a loaded > MIDI file. Well, I just tried that using a demo MIDI file from the old Jazz 4.1.3 from eons ago. Somehow I locked up the machine. It's rebooting now after a hard power-off. It should have the disks fsck'd in a couple hours (too much disk space). > If you were to run "make install" from the Build directory, > it would overwrite your jazz.cfg file and you would have to > re-setup the app. I changed where jazz.cfg goes so as not to be in the install directory for jazz. > Also, the code might work on your Madriva 2007 desktop. I just grabbed fresh SVN for both wxWindows and Jazz++ on my Mandriva 2007.0 music machine, rebuilt the whole thing, and ran it. It was looking good until the above mentioned machine lock-up. I'm not sure whether or not the stdout/stderr logfile I was creating will be preserved after the crash. We'll see. > Thank you for all of the testing. Without it I would feel like > I'm working in a void. Likewise, thanks! -- Kevin |
|
From: Kevin C. <ke...@co...> - 2008-04-10 03:58:24
|
On 9 April 2008 at 20:29, Pete Stieber <pst...@ve...> wrote: > Well Kevin, the last time I tried to use the machine with Mandriva, I > couldn't even get it to recognize my USB keyboard. I tried multiple > reboots... > > Tonight, everything worked. Even the ALSA restart. I even hooked up > the M-AUDIO Uno cable I recommended in the other thread to my Roland > TD-20 drum kit module, and Jazz++ worked using that setup. > > I did install TIMidity++ and it played the file too. Glad it's working for ya. > Thanks for the help, Not that I actually DID anything, but you're welcome... -- Kevin |
|
From: Pete S. <pst...@ve...> - 2008-04-10 03:28:28
|
PS = Pete Stieber wrote on 4 April 2008 at 14:03 PS>>> I'm starting to think there is a problem that is PS>>> independent of Jazz++. I tried restarting ALSA PS>>> from a cold boot and it also has problems... PS>>> PS>>> # service alsa restart PS>>> Doing alsactrl to store mixer settings... [ OK ] PS>>> Shutting down ALSA sound driver (version 1.0.14): no. PS>>> sound is being used by pid 6272)) [FAILED] PS>>> ALSA driver (version 1.0.14) is already running. PS>>> PS>>> Process 6272 is the sound mixer applet PS>>> (/usr/lib/mixer_applet2). PS>>> PS>>> Is this normal. I thought root should be able PS>>> to restart this service. KC = Kevin Cosgrove KC>> That doesn't look normal. Here's what I get: KC>> KC>> [root@laptop2-INCOMING #31] service alsa restart KC>> Doing alsactl to store mixer settings... [ OK ] KC>> Shutting down ALSA sound driver (version 1.0.14): [ OK ] KC>> Starting ALSA version 1.0.14: snd_ali5451. [ OK ] KC>> [root@laptop2-INCOMING #32] PS>> When I check to see what ALSA version I have installed... PS>> PS>> $ rpm -qa | grep alsa PS>> libalsa2-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa-data-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa-oss0-1.0.14-2mdv2008.0 PS>> alsa-utils-1.0.15-0.rc1.1mdv2008.0 PS>> alsa-plugins-1.0.14-7mdv2008.0 KC> Here's what I have that grep finds: KC> KC> alsamixergui-0.9.0-0.12rc1_3mdv2008.0 KC> alsaplayer-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-input-sndfile-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-input-vorbis-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-output-jack-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-ui-gtk-0.99.80-0.rc2.1mdv2008.0 KC> alsa-plugins-1.0.14-7mdv2008.0 KC> alsa-utils-1.0.15-0.rc1.1mdv2008.0 KC> java-1.6.0-sun-alsa-1.6.0.05-1mdv2008.0 KC> libalsa2-1.0.15-0.rc1.4mdv2008.0 KC> libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 KC> libalsa-data-1.0.15-0.rc1.4mdv2008.0 KC> libalsa-oss0-1.0.14-2mdv2008.0 PS>> Should 1.0.14 be mixed with 1.0.15? KC> Mine apparently is too. PS>>> I don't want to get too caught up in Mandriva PS>>> specific problems. KC>> I don't blame you for wanting to stay out of KC>> distribution specific traps, whatever the KC>> distribution or trap. PS>>> Maybe I botched the install? KC>> Did it seem to go smoothly? PS> Yes. I didn't have any problems. PS>>> Any ideas Kevin? KC>> See if anything else can access ALSA? Does KC>> TiMidity play things? How about [x]playmidi? PS> I'll give it a try when I get home. I hear PS> sound when I login and logout so I assumed PS> sound was properly configured. Well Kevin, the last time I tried to use the machine with Mandriva, I couldn't even get it to recognize my USB keyboard. I tried multiple reboots... Tonight, everything worked. Even the ALSA restart. I even hooked up the M-AUDIO Uno cable I recommended in the other thread to my Roland TD-20 drum kit module, and Jazz++ worked using that setup. I did install TIMidity++ and it played the file too. Thanks for the help, Pete |
|
From: Pete S. <pst...@ve...> - 2008-04-09 22:53:11
|
KC = Kevin Cosgrove KC> I used the latest build instructions from the website, KC> and after 'svn up ...', I rebuilt jazz. My earlier KC> exception is gone. Good. KC> I got the main window of jazz to open after selecting KC> my jazz.cfg file (no seg fault this time!). Even better. KC> This is all on a Mandriva 2008.0 laptop. I'm not KC> logged in properly on it, rather just SSH'd in, so KC> I didn't get ownership of /dev/snd/seq (which happens KC> when logged in locally). I fixed that as root by KC> making my user ID part of the "audio" group, KC> which has permissions on that device. I can't tell KC> how much works, but it seems to function at least a KC> little. Don't expect too much functionality as we are "early in the development process" ;-) You should be able to play a loaded MIDI file. KC> I opened the Harmony Browser, and it looks like KC> what I remember so fondly. One thing that seems KC> busted with it is that the "close" choice under its KC> "File" menu doesn't close the window. Thanks for the bug report. I just committed a fix for that. You can... 1. Update your source directory using svn. 2. Change directory to your Build directory and type "make". 3. Copy the resulting Jazz++ binary (called "jazz" in the src directory) over the one in your existing TestInstall/bin directory. And you should be ready to test the "File | Close" fix. If you were to run "make install" from the Build directory, it would overwrite your jazz.cfg file and you would have to re-setup the app. KC> I'll try more after I can be local on the laptop. KC> I guess I'll have to set up an ALSA MIDI sound KC> source, like TiMidity, as I don't have any way to KC> connect MIDI hardware to the laptop -- such things KC> exist, but I don't have anything. I purchased an M-AUDIO Uno cable (http://www.m-audio.com/products/en_us/Uno-main.html) for about $35 and have been very happy with it. Also, the code might work on your Madriva 2007 desktop. KC> Thanks! Thank you for all of the testing. Without it I would feel like I'm working in a void. Pete |
|
From: Pete S. <pst...@ve...> - 2008-04-09 22:51:24
|
PS = Pete Stieber wrote on 4 April 2008 at 14:03 PS>> I'm starting to think there is a problem that is PS>> independent of Jazz++. I tried restarting ALSA PS>> from a cold boot and it also has problems... PS>> PS>> # service alsa restart PS>> Doing alsactrl to store mixer settings... [ OK ] PS>> Shutting down ALSA sound driver (version 1.0.14): no. PS>> sound is being used by pid 6272)) [FAILED] PS>> ALSA driver (version 1.0.14) is already running. PS>> PS>> Process 6272 is the sound mixer applet PS>> (/usr/lib/mixer_applet2). PS>> PS>> Is this normal. I thought root should be able PS>> to restart this service. KC = Kevin Cosgrove KC> That doesn't look normal. Here's what I get: KC> KC> [root@laptop2-INCOMING #31] service alsa restart KC> Doing alsactl to store mixer settings... [ OK ] KC> Shutting down ALSA sound driver (version 1.0.14): [ OK ] KC> Starting ALSA version 1.0.14: snd_ali5451. [ OK ] KC> [root@laptop2-INCOMING #32] PS>> When I check to see what ALSA version I have installed... PS>> PS>> $ rpm -qa | grep alsa PS>> libalsa2-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa-data-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa-oss0-1.0.14-2mdv2008.0 PS>> alsa-utils-1.0.15-0.rc1.1mdv2008.0 PS>> alsa-plugins-1.0.14-7mdv2008.0 KC> Here's what I have that grep finds: KC> KC> alsamixergui-0.9.0-0.12rc1_3mdv2008.0 KC> alsaplayer-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-input-sndfile-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-input-vorbis-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-output-jack-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-ui-gtk-0.99.80-0.rc2.1mdv2008.0 KC> alsa-plugins-1.0.14-7mdv2008.0 KC> alsa-utils-1.0.15-0.rc1.1mdv2008.0 KC> java-1.6.0-sun-alsa-1.6.0.05-1mdv2008.0 KC> libalsa2-1.0.15-0.rc1.4mdv2008.0 KC> libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 KC> libalsa-data-1.0.15-0.rc1.4mdv2008.0 KC> libalsa-oss0-1.0.14-2mdv2008.0 PS>> Should 1.0.14 be mixed with 1.0.15? KC> Mine apparently is too. PS>> I don't want to get too caught up in Mandriva PS>> specific problems. KC> I don't blame you for wanting to stay out of KC> distribution specific traps, whatever the KC> distribution or trap. PS>> Maybe I botched the install? KC> Did it seem to go smoothly? Yes. I didn't have any problems. PS>> Any ideas Kevin? KC> See if anything else can access ALSA? Does KC> TiMidity play things? How about [x]playmidi? I'll give it a try when I get home. I hear sound when I login and logout so I assumed sound was properly configured. Thanks for the help, Pete |
|
From: Kevin C. <ke...@co...> - 2008-04-09 17:11:08
|
Hiya, I used the latest build instructions from the website, and after 'svn up ...', I rebuilt jazz. My earlier exception is gone. I got the main window of jazz to open after selecting my jazz.cfg file (no seg fault this time!). This is all on a Mandriva 2008.0 laptop. I'm not logged in properly on it, rather just SSH'd in, so I didn't get ownership of /dev/snd/seq (which happens when logged in locally). I fixed that as root by making my user ID part of the "audio" group, which has permissions on that device. I can't tell how much works, but it seems to function at least a little. I opened the Harmony Browser, and it looks like what I remember so fondly. One thing that seems busted with it is that the "close" choice under its "File" menu doesn't close the window. I'll try more after I can be local on the laptop. I guess I'll have to set up an ALSA MIDI sound source, like TiMidity, as I don't have any way to connect MIDI hardware to the laptop -- such things exist, but I don't have anything. Thanks! -- Kevin |
|
From: Kevin C. <ke...@co...> - 2008-04-09 17:02:54
|
On 4 April 2008 at 14:03, Pete Stieber <pst...@ve...> wrote: > Thanks for suggesting this Kevin. I'm a long time Red Hat/Fedora user > and though the "service" command was specific to Red Hat. > > I'm starting to think there is a problem that is independent of Jazz++. > I tried restarting ALSA from a cold boot and it also has problems... > > # service alsa restart > Doing alsactrl to store mixer settings... [ OK ] > Shutting down ALSA sound driver (version 1.0.14): no. (sound is being > used by pid 6272)) [FAILED] > ALSA driver (version 1.0.14) is already running. > > Process 6272 is the sound mixer applet (/usr/lib/mixer_applet2). > > Is this normal. I thought roo should be able to restart this service. That doesn't look normal. Here's what I get: [root@laptop2-INCOMING #31] service alsa restart Doing alsactl to store mixer settings... [ OK ] Shutting down ALSA sound driver (version 1.0.14): [ OK ] Starting ALSA version 1.0.14: snd_ali5451. [ OK ] [root@laptop2-INCOMING #32] > When I check to see what ALSA version I have installed... > > $ rpm -qa | grep alsa > libalsa2-1.0.15-0.rc1.4mdv2008.0 > libalsa-data-1.0.15-0.rc1.4mdv2008.0 > libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 > libalsa-oss0-1.0.14-2mdv2008.0 > alsa-utils-1.0.15-0.rc1.1mdv2008.0 > alsa-plugins-1.0.14-7mdv2008.0 Here's what I have that grep finds: alsamixergui-0.9.0-0.12rc1_3mdv2008.0 alsaplayer-0.99.80-0.rc2.1mdv2008.0 alsaplayer-plugin-input-sndfile-0.99.80-0.rc2.1mdv2008.0 alsaplayer-plugin-input-vorbis-0.99.80-0.rc2.1mdv2008.0 alsaplayer-plugin-output-jack-0.99.80-0.rc2.1mdv2008.0 alsaplayer-plugin-ui-gtk-0.99.80-0.rc2.1mdv2008.0 alsa-plugins-1.0.14-7mdv2008.0 alsa-utils-1.0.15-0.rc1.1mdv2008.0 java-1.6.0-sun-alsa-1.6.0.05-1mdv2008.0 libalsa2-1.0.15-0.rc1.4mdv2008.0 libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 libalsa-data-1.0.15-0.rc1.4mdv2008.0 libalsa-oss0-1.0.14-2mdv2008.0 > Should 1.0.14 be mixed with 1.0.15? Mine apparently is too. > I don't want to get too caught up in Mandriva specific problems. I don't blame you for wanting to stay out of distribution specific traps, whatever the distribution or trap. > Maybe I botched the install? Did it seem to go smoothly? > Any ideas Kevin? See if anything else can access ALSA? Does TiMidity play things? How about [x]playmidi? Good luck.... -- Kevin |
|
From: Kevin C. <ke...@co...> - 2008-04-07 18:09:27
|
On 7 April 2008 at 10:51, Pete Stieber <pst...@ve...> wrote: > I've done some preliminary work on the harmony browser. Use "Tools... | > Harmony Browser..." to give it a whirl. > > Let me know if it is acting properly. IIRC you were interested in this. I was/am quite interested in the harmony browser. It'll be the first feature I test out, other than basic operation. Thanks..... -- Kevin |
|
From: Pete S. <pst...@ve...> - 2008-04-07 17:50:43
|
PS = Pete Stieber PS>>> I'm trying to understand the Jazz++ PS>>> zombie process that lives on when I exit Jazz++... PS>> After putting in cout statements and rebooting PS>> several time, I think I commented out the PS>> offending code. PS>> PS>> Kevin, PS>> Make sure you update and rebuild Jazz++ before PS>> attempting to run it. KC = Kevin Cosgrove KC> OK, will do. I've got wxWidgets to compile fine KC> on the laptop. I didn't do anything with Jazz++ KC> yet. So, your timing is great. Kevin and anyone else who may be listening ;-) I've done some preliminary work on the harmony browser. Use "Tools... | Harmony Browser..." to give it a whirl. Let me know if it is acting properly. IIRC you were interested in this. Pete |
|
From: Kevin C. <ke...@co...> - 2008-04-05 08:42:01
|
On 4 April 2008 at 22:32, Pete Stieber <pst...@ve...> wrote: > PS = Pete Stieber > PS> I'm trying to understand the Jazz++ > PS> zombie process that lives on when I exit Jazz++... > > After putting in cout statements and rebooting several time, I think I > commented out the offending code. > > Kevin, > Make sure you update and rebuild Jazz++ before attempting to run it. OK, will do. I've got wxWidgets to compile fine on the laptop. I didn't do anything with Jazz++ yet. So, your timing is great. Thanks... -- Kevin |
|
From: Pete S. <pst...@ve...> - 2008-04-05 05:31:30
|
PS = Pete Stieber PS> I'm trying to understand the Jazz++ PS> zombie process that lives on when I exit Jazz++... After putting in cout statements and rebooting several time, I think I commented out the offending code. Kevin, Make sure you update and rebuild Jazz++ before attempting to run it. Robert, If you are out there, you may want to update, rebuild and see how it goes. Thanks for all of the help, Pete |
|
From: Pete S. <pst...@ve...> - 2008-04-05 04:00:14
|
PS = Pete Stieber PS>>> Thanks Kevin. I'm trying to understand the Jazz++ PS>>> zombie process that lives on when I exit Jazz++. PS>>> It looks like it has to do with the ALSA connection. PS>>> When I reboot, the ALSA close message even fails. PS>>> This doesn't happen on the Fedora 8 box I test on. KC = Kevin Cosgrove KC>> Rather than rebooting, is there an alsa service in KC>> /etc/init.d/... which could be restarted with the KC>> 'service' command? PS> Thanks for suggesting this Kevin. I'm a long time PS> Red Hat/Fedora user and though the "service" PS> command was specific to Red Hat. PS> PS> I'm starting to think there is a problem that is PS> independent of Jazz++. I tried restarting PS> ALSA from a cold boot and it also has problems... PS> PS> # service alsa restart PS> Doing alsactrl to store mixer settings... [ OK ] PS> Shutting down ALSA sound driver (version 1.0.14): no. (sound is being PS> used by pid 6272)) [FAILED] PS> ALSA driver (version 1.0.14) is already running. PS> PS> Process 6272 is the sound mixer applet PS> (/usr/lib/mixer_applet2). PS> PS> Is this normal. I thought root should be able to PS> restart this service. PS> PS> When I check to see what ALSA version I PS> have installed... PS> $ rpm -qa | grep alsa PS> libalsa2-1.0.15-0.rc1.4mdv2008.0 PS> libalsa-data-1.0.15-0.rc1.4mdv2008.0 PS> libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 PS> libalsa-oss0-1.0.14-2mdv2008.0 PS> alsa-utils-1.0.15-0.rc1.1mdv2008.0 PS> alsa-plugins-1.0.14-7mdv2008.0 PS> PS> Should 1.0.14 be mixed with 1.0.15? PS> PS> I don't want to get too caught up in Mandriva PS> specific problems. Maybe I botched the install? PS> PS> Any ideas Kevin? I can't even stop the process with # service alsa force-stop This command tries to stop all processes attached to alsa, but gets stuck trying to kill the Jazz++ process with a SIGKILL. I'm not sure what to do next. Pete |
|
From: Pete S. <pst...@ve...> - 2008-04-04 21:02:45
|
PS = Pete Stieber PS>> Thanks Kevin. I'm trying to understand the Jazz++ PS>> zombie process that lives on when I exit Jazz++. PS>> It looks like it has to do with the ALSA connection. PS>> When I reboot, the ALSA close message even fails. PS>> This doesn't happen on the Fedora 8 box I test on. KC = Kevin Cosgrove KC> Rather than rebooting, is there an alsa service in KC> /etc/init.d/... which could be restarted with the KC> 'service' command? Thanks for suggesting this Kevin. I'm a long time Red Hat/Fedora user and though the "service" command was specific to Red Hat. I'm starting to think there is a problem that is independent of Jazz++. I tried restarting ALSA from a cold boot and it also has problems... # service alsa restart Doing alsactrl to store mixer settings... [ OK ] Shutting down ALSA sound driver (version 1.0.14): no. (sound is being used by pid 6272)) [FAILED] ALSA driver (version 1.0.14) is already running. Process 6272 is the sound mixer applet (/usr/lib/mixer_applet2). Is this normal. I thought roo should be able to restart this service. When I check to see what ALSA version I have installed... $ rpm -qa | grep alsa libalsa2-1.0.15-0.rc1.4mdv2008.0 libalsa-data-1.0.15-0.rc1.4mdv2008.0 libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 libalsa-oss0-1.0.14-2mdv2008.0 alsa-utils-1.0.15-0.rc1.1mdv2008.0 alsa-plugins-1.0.14-7mdv2008.0 Should 1.0.14 be mixed with 1.0.15? I don't want to get too caught up in Mandriva specific problems. Maybe I botched the install? Any ideas Kevin? Pete |
|
From: Kevin C. <ke...@co...> - 2008-04-04 15:05:49
|
On 4 April 2008 at 7:40, Pete Stieber <pst...@ve...> wrote: > Thanks Kevin. I'm trying to understand the Jazz++ zombie process that > lives on when I exit Jazz++. It looks like it has to do with the ALSA > connection. When I reboot, the ALSA close message even fails. This > doesn't happen on the Fedora 8 box I test on. Rather than rebooting, is there an alsa service in /etc/init.d/... which could be restarted with the 'service' command? Alternatively, could 'alsactl' be used to shutdown alsa, rather than needing to reboot? > Keep us posted, and thanks for all of the testing, Will do, and you're welcome! -- Kevin |
|
From: Pete S. <pst...@ve...> - 2008-04-04 14:40:18
|
PS = Pete Stieber PS>> I've separated the build instructions into wxWidgets PS>> and Jazz++ pages... PS>> PS>> http://jazzplusplus.sourceforge.net/buildingwx/ PS>> PS>> http://jazzplusplus.sourceforge.net/buildingjazz/ PS>> PS>> Let me know if anything isn't clear or you find PS>> typos or errors. KC = Kevin Cosgrove KC> It seems to be working. I'm building wxWidgets on KC> my Mandriva 2008.0 laptop. It took a while to load KC> all the development stuff on it. Sorry about that. KC> I normally just use it as a remote terminal to SSH KC> into one of the other machines at the house, or KC> I'll use it as a portable video player to watch KC> watch streaming video, but no development until now. KC> I'll let you know how the jazz build goes, which I'm KC> certain won't start tonight. Thanks Kevin. I'm trying to understand the Jazz++ zombie process that lives on when I exit Jazz++. It looks like it has to do with the ALSA connection. When I reboot, the ALSA close message even fails. This doesn't happen on the Fedora 8 box I test on. I'll have more time to look at it this weekend. Keep us posted, and thanks for all of the testing, Pete |
|
From: Kevin C. <ke...@co...> - 2008-04-04 06:39:43
|
On 3 April 2008 at 7:13, Pete Stieber <pst...@ve...> wrote: > I've separated the build instructions into wxWidgets and Jazz++ pages... > > http://jazzplusplus.sourceforge.net/buildingwx/ > > http://jazzplusplus.sourceforge.net/buildingjazz/ > > Let me know if anything isn't clear or you find typos or errors. It seems to be working. I'm building wxWidgets on my Mandriva 2008.0 laptop. It took a while to load all the development stuff on it. I normally just use it as a remote terminal to SSH into one of the other machines at the house, or I'll use it as a portable video player to watch streaming video, but no development until now. I'll let you know how the jazz build goes, which I'm certain won't start tonight. Thanks! -- Kevin |
|
From: Pete S. <pst...@ve...> - 2008-04-03 14:12:21
|
I've separated the build instructions into wxWidgets and Jazz++ pages... http://jazzplusplus.sourceforge.net/buildingwx/ http://jazzplusplus.sourceforge.net/buildingjazz/ Let me know if anything isn't clear or you find typos or errors. Thanks, Pete |
|
From: Pete S. <pst...@ve...> - 2008-04-03 03:31:59
|
PS = Pete Stieber PS>> That file name should have been .Jazz *not* .jazz. PS>> Sorry about that. Do you have a $HOME/.Jazz file? KC = Kevin Cosgrove KC> Nope. It wouldn't be written if the jazz.cfg file was found when Jazz++ was initially started. I have one on the Mandriva box I made last night. I started the code from $HOME/Jazz++/TestInstall/bin, it didn't find jazz.cfg, and the file was written when I selected it using the open dialog box. Go figure. Pete |
|
From: Kevin C. <ke...@co...> - 2008-04-03 00:03:43
|
On 2 April 2008 at 16:05, Pete Stieber <pst...@ve...> wrote: > That file name should have been .Jazz *not* .jazz. Sorry about that. > Do you have a $HOME/.Jazz file? Nope. -- Kevin |
|
From: Pete S. <pst...@ve...> - 2008-04-02 23:05:23
|
KC> How does this relate to: KC> KC> [kevinc@joseph-temp #886] printenv | grep jazz KC> WXHELPFILES=/usr/local/jazz KC> JAZZ=/usr/local/jazz KC> KC> I'm guessing that I should unset those KC> environment variables, right? I grepped through the source code, and WXHELPFILES isn't used anywhere. I don't have help building yet. JAZZ is used, but go ahead and unset it. PS>> Make sure you erase $HOME/.jazz before you run the PS>> code after your rebuild. KC> I don't have a ~/.jazz file nor directory. Maybe KC> I've been using what's pointed to by my environment KC> variables sometime in the past. That file name should have been .Jazz *not* .jazz. Sorry about that. Do you have a $HOME/.Jazz file? Pete |
|
From: Kevin C. <ke...@co...> - 2008-04-02 22:37:47
|
On 2 April 2008 at 15:03, Pete Stieber <pst...@ve...> wrote: > There is a preliminary version of the updated instructions in > place. I separated the wxWidgets build page from the Jazz++ > build page. Good deal. > The wxWidgets build instructions are modified, and the Jazz++ > build page is new and incomplete (Windows instructions are not > included). There should be enough there to get you started. Cool. I'll try it. > I just wanted to make sure... > > 1. That the wxWidgets install does not conflict with any OS installed > version. How does this relate to: [kevinc@joseph-temp #886] printenv | grep jazz WXHELPFILES=/usr/local/jazz JAZZ=/usr/local/jazz I'm guessing that I should unset those environment variables, right? > 2. That you don't use the jazz.cfg file under the checked out code. I'll try not to. > Make sure you erase $HOME/.jazz before you run the code after your rebuild. I don't have a ~/.jazz file nor directory. Maybe I've been using what's pointed to by my environment variables sometime in the past. > I'm sure there are errors in the instructions I just slapped together. > If you could post the error reports here, that would be great. I certainly will report errors, successes and failures. > Sorry I didn't install Mandriva 2007. No worries. I should upgrade. It's just a pain, so I do so sparingly. One machine is used by my wife too, so I need to test all the applications, etc. I imagine you've been through that, regardless of whether you're sharing a computer. > Thanks for the help! Likewise.... -- Kevin |
86 messages has been excluded from this view by a project administrator.
