I took the plunge and ran the script on Slacko 5.3.3 even though it looks like I'm missing everything it's expecting to find I just wanted to test the buttons and anything else that might be going on in there.

Before we go any further can you add this line:

Code:

echo GTKDIALOG EXITED

at line 609 so that the code in that part of the file looks like this:

Now, if you run Frisbee in the terminal, do you see " GTKDIALOG EXITED" after you've pressed Frisbee's exit button? What exactly are you seeing in the terminal? If you press Enter in there, what happens? Have you got a prompt? Can you run commands in there like ls?

Also, what is the full path of the Frisbee source that you are editing in Geany?

There is something wierd there, in the original unmodified Frisbee source at lines 280 and 418:

They are part of progressbars that are being used to auto-refresh widgets and run programs except that they remain running in the background and the more you use Frisbee the more of them remain running (you can see them accumulating in htop).

You could try simply deleting the lines, try Frisbee, then put the lines back.

I took the plunge and ran the script on Slacko 5.3.3 even though it looks like I'm missing everything it's expecting to find I just wanted to test the buttons and anything else that might be going on in there.

Before we go any further can you add this line:

Code:

echo GTKDIALOG EXITED

at line 609 so that the code in that part of the file looks like this:

Now, if you run Frisbee in the terminal, do you see " GTKDIALOG EXITED" after you've pressed Frisbee's exit button? What exactly are you seeing in the terminal? If you press Enter in there, what happens? Have you got a prompt? Can you run commands in there like ls?

Also, what is the full path of the Frisbee source that you are editing in Geany?

There is something wierd there, in the original unmodified Frisbee source at lines 280 and 418:

They are part of progressbars that are being used to auto-refresh widgets and run programs except that they remain running in the background and the more you use Frisbee the more of them remain running (you can see them accumulating in htop).

You could try simply deleting the lines, try Frisbee, then put the lines back.

Regards,
Thunor

Hi Thunor

Tried deleting the strange lines - that stopped wifi signals being detected - tried altering the parameters instead - it worked fine with the count set down to 100 and the delay set to 5.

Those lines are in the current working V2 Frisbee BTW.

the full path is /usr/local/bin/Frisbee - as given by which Frisbee

the echo you have suggested is the same as the debug echo put in by rerwin - the echo does not appear in the /tmp file - nothing appears from your terminal echo either.

In the terminal I see nothing except a red underline cursor until I press cntrl-c when the prompt reappears....anything I type is echoed but no commands are recognised until I get the # prompt back with cntrl-c.

Tried deleting the strange lines - that stopped wifi signals being detected - tried altering the parameters instead - it worked fine with the count set down to 100 and the delay set to 5.

Yeah, but I only wanted to know if deleting the lines stops gtkdialog3 from not exiting because these lines are processes being started by gtkdialog in another thread and they're being left running because there's no exit condition in the code.

1. Delete the lines in Geany
2. Open a terminal and type Frisbee
3. Click the "Configure Network Interfaces" tab
4. Click the Exit button
5. Type ls in the terminal and press Enter
6. Do you get a directory listing or does the cursor simply go to the next line?

the echo you have suggested is the same as the debug echo put in by rerwin - the echo does not appear in the /tmp file - nothing appears from your terminal echo either.

No it's not the same. rerwin's messages go to /tmp/udevtrace-modem.log, mine goes to stdout i.e. the same terminal window that you are running frisbee in.

peebee wrote:

In the terminal I see nothing except a red underline cursor until I press cntrl-c when the prompt reappears....anything I type is echoed but no commands are recognised until I get the # prompt back with cntrl-c.

Ok, great, so can you try the first item in this post and let me know what happens please.

1. Delete the lines in Geany
2. Open a terminal and type Frisbee
3. Click the "Configure Network Interfaces" tab
4. Click the Exit button
5. Type ls in the terminal and press Enter
6. Do you get a directory listing or does the cursor simply go to the next line?

Ok, great, so can you try the first item in this post and let me know what happens please.
Regards,
Thunor

6 = directory listing - pressing exit after configure network interfaces exits Frisbee and takes you back to the # prompt in the terminal.

I downloaded the Frisbee.gz package posted by rerwin and that is Frisbee, one file, with "Frisbee" in the window title bar and two tabs, "Configure Wireless Networks" and "Configure Network Interfaces".

So we've established that Frisbee/gtkdialog3 is not exiting from the exit button on the first tabbed page and that the Frisbee developer needs to quit those progressbar inputs.

That's it. To be honest it's bizarre and I don't really want to spend another day communicating my debugging methodology through a forum. You need somebody with programming skills that can quickly narrow down and isolate the cause on your computer in your house.

What else can I say. Try replacing gtkdialog3 within the code with gtkdialog4 or just gtkdialog. The exit button on the first tabbed page is at line 414: try placing <action>echo EXITING</action> above it and look for it in the terminal. Try placing <action signal=\"hide\">echo HIDING</action> above the </window> tag at line 604. Those progressbar inputs should have an exit condition.

Thunor
A quest about r473 - export="false"
This is of course a very handy option. I see clearly how I can include it into pMusic which handles large amount of data in some widgets...
... But, does this has an effect only if <variable> is defined, or does gtkdialog export the content even if no variable is set?

Thunor
A quest about r473 - export="false"
This is of course a very handy option. I see clearly how I can include it into pMusic which handles large amount of data in some widgets...
... But, does this has an effect only if <variable> is defined, or does gtkdialog export the content even if no variable is set?

Thank you
Sigmund

It only has an effect if <variable> is defined. gtkdialog does not export the contents of a widget if you haven't given it a name.

There's a gtkdialog function called variables_export_all() which puts the contents of all widgets into the environment if you have given them a name. This function is called when you run a shell command i.e. in an <action> directive, when you refresh a widget and when you launch a new dialog so I think you can imagine how desirable it would be to stop putting unneccessary data into the environment.

From a terminal, run Frisbee and then press the exit button on the first tabbed page. Does gtkdialog exit or hang? I can't see why it would not exit at this stage because it's a similar exit button to the other one on the second tabbed page.

Let's say it exits cleanly. You know the route that you take through Frisbee to duplicate this problem, so do the next thing whatever that is (ckick a button, select something?) and then click the same exit button. Did it exit cleanly? It did, so do two things and then click the exit button. At some point you are going to find the exact place where the exit button becomes problematic and then we have something to work with. It's important that you only do one more additional thing each time.

Let me know what you find. I can't do anything at the moment except give you advice on how to effectively problem solve.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum