trouble running solfege on Mac OS 10.6
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
trouble running solfege on Mac OS 10.6
by Allen McBride
::
Rate this Message:
Hi all,
Sorry I haven't been updating the MacPort of solfege in the past several months. I just installed Snow Leopard, so I thought now would be a good time to update it, but unfortunately I can't get solfege to run anymore. I've tried both 3.14.8, which I'd never used before, and 3.14.1, which is the current MacPorts version and which worked for me on OS 10.5. Both compiled fine, but when I start solfege, it gets to the point where it says, "Starting GNU Solfege 3.14.8 / http://www.solfege.org / creating MainWin". It takes longer than usual to get to this point, and when it does, nothing else happens. The Python process keeps churning away with most of my CPU. It doesn't seem hung, because Python quits nicely when I ask it to. When I sample the Python process using Activity Monitor, and refresh repeatedly, things look similar each time, though I don't really know what I'm looking at. Anyone else out there using Solfege on Mac OS 10.6? Tom Cato, any ideas about what could be going wrong at the "creating MainWin" step? Thanks! --Allen McBride ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Solfege-devel mailing list To UNSUBSCRIBE, email to solfege-devel-request@... with a subject of "unsubscribe", or visit https://lists.sourceforge.net/lists/listinfo/solfege-devel |
|
|
|
|
|
Re: Fwd: trouble running solfege on Mac OS 10.6
by Allen McBride
::
Rate this Message:
On Sep 30, 2009, at 4:00 PM, Tom Cato Amundsen wrote:
> > I don't know how Mac people gently ask a program to exit ;-) > but on linux, if I start solfege from a terminal window and press > Ctrl-C to stop the program I get a traceback. An example shown below. > Can you do that and send me the output? There I can see what the > program is doing. > > Tom Cato Interesting. I hit Ctrl-C, and thought nothing was happening. But after a minute, "Traceback (most recent call last):" appeared, and then nothing after that for a long time. Python kept churning, and I did not get a command prompt again at the terminal. But then finally, after maybe 20 minutes or so, the terminal showed: Traceback (most recent call last): File "/opt/local/share/solfege/src/htmlwidget.py", line 143, in rr def rr(widget): KeyboardInterrupt But the program kept going. I got a window asking if I wanted to make an automatic bug report. I clicked the yes button, but then things seemed to hang in that window. Behind that window, I finally got the actual Solfege main window. But I can't click any menus on it or anything else. As I write this, Python is still chugging away. I'm sending one other thing: it's the results of "sample process" on the Python process, while it was hung on the "creating MainWin" stage. Each sample I take in this state looks very similar. Thanks! --Allen Sampling process 33572 for 1 seconds with 1 millisecond of run time between samples Sampling completed, processing symbols... Analysis of sampling Python (pid 33572) every 1 millisecond Call graph: 703 Thread_174238 DispatchQueue_1: com.apple.main-thread (serial) 703 0x100000f14 703 Py_Main 703 PyRun_SimpleFileExFlags 703 PyRun_FileExFlags 703 PyEval_EvalCode 703 PyEval_EvalCodeEx 703 PyEval_EvalFrameEx 703 PyEval_EvalCodeEx 703 PyEval_EvalFrameEx 703 _wrap_gtk_widget_show 703 gtk_widget_show 703 g_signal_emit 703 g_signal_emit_valist 703 signal_emit_unlocked_R 703 g_closure_invoke 703 gtk_window_show 703 gtk_widget_size_allocate 703 g_signal_emit 703 g_signal_emit_valist 703 signal_emit_unlocked_R 703 g_closure_invoke 703 gtk_window_size_allocate 703 gtk_widget_size_allocate 703 g_signal_emit 703 g_signal_emit_valist 703 signal_emit_unlocked_R 703 g_closure_invoke 703 gtk_box_size_allocate 703 gtk_widget_size_allocate 703 g_signal_emit 703 g_signal_emit_valist 703 signal_emit_unlocked_R 703 g_closure_invoke 703 gtk_box_size_allocate 703 gtk_widget_size_allocate 703 g_signal_emit 703 g_signal_emit_valist 703 signal_emit_unlocked_R 703 g_closure_invoke 703 gtk_box_size_allocate 703 gtk_widget_size_allocate 703 g_signal_emit 703 g_signal_emit_valist 703 signal_emit_unlocked_R 703 g_closure_invoke 703 gtk_scrolled_window_size_allocate 703 gtk_widget_size_allocate 703 g_signal_emit 703 g_signal_emit_valist 703 signal_emit_unlocked_R 703 g_closure_invoke 703 gtk_text_view_size_allocate 703 g_signal_emit 703 g_signal_emit_valist 703 signal_emit_unlocked_R 703 g_closure_invoke 703 changed_handler 703 gtk_text_view_update_child_allocation 703 gtk_widget_size_allocate 703 g_signal_emit 703 g_signal_emit_valist 703 signal_emit_unlocked_R 703 g_closure_invoke 703 gtk_table_size_allocate 703 gtk_widget_size_allocate 703 g_signal_emit 703 g_signal_emit_valist 703 signal_emit_unlocked_R 703 g_closure_invoke 703 gtk_text_view_size_allocate 703 get_hadjustment 703 gtk_text_view_value_changed 703 gtk_text_view_validate_onscreen 703 gtk_text_layout_validate_yrange 703 _gtk_text_btree_validate_line 703 gtk_text_layout_real_wrap 703 gtk_text_layout_get_line_display 703 pango_layout_get_extents_internal 703 pango_layout_check_lines 703 process_item 703 shape_run 703 pango_shape 703 basic_engine_shape 703 _pango_ot_info_position 703 hb_ot_layout_position_lookup 395 hb_ot_layout_position_lookup 308 PosLookupSubTable::apply(_hb_ot_layout_context_t*, _hb_buffer_t*, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int) const Total number in stack (recursive counted multiple, when >=5): 10 g_closure_invoke 10 g_signal_emit 10 g_signal_emit_valist 10 signal_emit_unlocked_R 8 gtk_widget_size_allocate Sort by top of stack, same collapsed (when >= 5): hb_ot_layout_position_lookup 395 PosLookupSubTable::apply(_hb_ot_layout_context_t*, _hb_buffer_t*, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int) const 308 Sample analysis of process 33572 written to file /dev/stdout ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Solfege-devel mailing list To UNSUBSCRIBE, email to solfege-devel-request@... with a subject of "unsubscribe", or visit https://lists.sourceforge.net/lists/listinfo/solfege-devel |
|
|
Re: Fwd: trouble running solfege on Mac OS 10.6
by Tom Cato Amundsen
::
Rate this Message:
Comment out line 159 in src/htmlwidget.py. The line looks like this:
self.connect("realize", rr) Change it to: # self.connect("realize", rr) Does this make any difference? Tom Cato On Wed, Sep 30, 2009 at 11:02 PM, Allen McBride <allencmcbride@...> wrote: > On Sep 30, 2009, at 4:00 PM, Tom Cato Amundsen wrote: >> >> I don't know how Mac people gently ask a program to exit ;-) >> but on linux, if I start solfege from a terminal window and press >> Ctrl-C to stop the program I get a traceback. An example shown below. >> Can you do that and send me the output? There I can see what the >> program is doing. >> >> Tom Cato > > Interesting. I hit Ctrl-C, and thought nothing was happening. But after a > minute, "Traceback (most recent call last):" appeared, and then nothing > after that for a long time. Python kept churning, and I did not get a > command prompt again at the terminal. But then finally, after maybe 20 > minutes or so, the terminal showed: > > Traceback (most recent call last): > File "/opt/local/share/solfege/src/htmlwidget.py", line 143, in rr > def rr(widget): > KeyboardInterrupt > > But the program kept going. I got a window asking if I wanted to make an > automatic bug report. I clicked the yes button, but then things seemed to > hang in that window. Behind that window, I finally got the actual Solfege > main window. But I can't click any menus on it or anything else. As I > write this, Python is still chugging away. I'm sending one other thing: > it's the results of "sample process" on the Python process, while it was > hung on the "creating MainWin" stage. Each sample I take in this state > looks very similar. > > Thanks! > --Allen > > -- Tom Cato Amundsen <tca@...> http://www.solfege.org/ GNU Solfege - free ear training http://www.gnu.org/software/solfege/ ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Solfege-devel mailing list To UNSUBSCRIBE, email to solfege-devel-request@... with a subject of "unsubscribe", or visit https://lists.sourceforge.net/lists/listinfo/solfege-devel |
|
|
Re: Fwd: trouble running solfege on Mac OS 10.6
by Allen McBride
::
Rate this Message:
I assume you meant to change it in place, and not recompile, right?
It still stopped at the "creating MainWin", and it still took forever for the traceback to actually return something, but here's what it gave me: Traceback (most recent call last): File "/opt/local/bin/solfege", line 74, in <module> src.mainwin.start_app(os.path.join(prefix, "share", "solfege")) File "/opt/local/share/solfege/src/mainwin.py", line 887, in start_app w.show() KeyboardInterrupt And this time, it actually stopped the Python process and spit me back to the command prompt. --Allen On Sep 30, 2009, at 5:11 PM, Tom Cato Amundsen wrote: > Comment out line 159 in src/htmlwidget.py. The line looks like this: > self.connect("realize", rr) > > Change it to: > # self.connect("realize", rr) > > Does this make any difference? > > Tom Cato > > On Wed, Sep 30, 2009 at 11:02 PM, Allen McBride <allencmcbride@... > > wrote: >> On Sep 30, 2009, at 4:00 PM, Tom Cato Amundsen wrote: >>> >>> I don't know how Mac people gently ask a program to exit ;-) >>> but on linux, if I start solfege from a terminal window and press >>> Ctrl-C to stop the program I get a traceback. An example shown >>> below. >>> Can you do that and send me the output? There I can see what the >>> program is doing. >>> >>> Tom Cato >> >> Interesting. I hit Ctrl-C, and thought nothing was happening. But >> after a >> minute, "Traceback (most recent call last):" appeared, and then >> nothing >> after that for a long time. Python kept churning, and I did not >> get a >> command prompt again at the terminal. But then finally, after >> maybe 20 >> minutes or so, the terminal showed: >> >> Traceback (most recent call last): >> File "/opt/local/share/solfege/src/htmlwidget.py", line 143, in rr >> def rr(widget): >> KeyboardInterrupt >> >> But the program kept going. I got a window asking if I wanted to >> make an >> automatic bug report. I clicked the yes button, but then things >> seemed to >> hang in that window. Behind that window, I finally got the actual >> Solfege >> main window. But I can't click any menus on it or anything else. >> As I >> write this, Python is still chugging away. I'm sending one other >> thing: >> it's the results of "sample process" on the Python process, while >> it was >> hung on the "creating MainWin" stage. Each sample I take in this >> state >> looks very similar. >> >> Thanks! >> --Allen >> >> > > > > -- > Tom Cato Amundsen <tca@...> http:// > www.solfege.org/ > GNU Solfege - free ear training http://www.gnu.org/software/ > solfege/ ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Solfege-devel mailing list To UNSUBSCRIBE, email to solfege-devel-request@... with a subject of "unsubscribe", or visit https://lists.sourceforge.net/lists/listinfo/solfege-devel |
| Free embeddable forum powered by Nabble | Forum Help |
