| Summary: | ufed dies with "fatal error: the dialog couldn't be opened" | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mark E. Drummond <mark> |
| Component: | Current packages | Assignee: | Fred Van Andel (RETIRED) <fava> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gentoo-bugs |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
strace output
strace -f ufed Test program that will save dialog parameters to a file. ufed.pl output test script # 1 for ufed Test script #2 for ufed strace -f output against dialog |
||
|
Description
Mark E. Drummond
2003-09-03 18:34:01 UTC
Created attachment 17027 [details]
strace output
Here's the output of a `strace ufed`.
Mark
you didnt run with -f so your strace didnt capture stuff post the fork() do you have dialog installed ? is your terminal big enough ? You're right, I forgot the -f. I'll rerun it when I get home. I assume I have dialog installed (ufed has always worked until recently) but I'll double check that too. Not sure what you mean by "is your terminal big enough ?". I am trying to run this from a VC, not an X terminal app. Mark When ufed gives that error is usually means something is wrong with the parameters being passed to dialog. I am attaching a slightly modified version of ufed called ufed2 to this bug. Please run it. It will create a file in the current directory called ufed-output.txt. Please attach that file to this bugreport. Created attachment 17102 [details]
strace -f ufed
Created attachment 17103 [details]
Test program that will save dialog parameters to a file.
Please run and attach ufed-output.txt to this bug report
Dialog is installed too:
tess root # qpkg -I -i dialog
dev-util/dialog-0.9_beta20030308-r1 *
A Tool to display Dialog boxes from Shell [
http://www.advancedresearch.org/dialog/ ]
Created attachment 17104 [details]
ufed.pl output
I think I know what the problem is, now to figure out why. I am attaching 2 scripts to this bug, please run them and tell me the results. One should work and the other should fail. I want to know the error message that ensues. Please maximuse your terminal before running the scripts. Can you please tell me what terminal software are you using and does it occur when using different terminal software. Can you please also try to run ufed from a textmode terminal as well. Created attachment 17127 [details]
test script # 1 for ufed
Created attachment 17128 [details]
Test script #2 for ufed
There's something wrong with the scripts, I think. When I open them up they are both just single continuous lines (no life feeds). Can you upload them again if they are not supposed to be like that? And are these shell scripts? If not, how do I run them. Mark errr, s/life/line/ Yes they are shell scripts. Yes they are supposed to be one very long line. run: sh test1.sh sh test2.sh to execute them. I have tried running ufed both from a VC and in KDE's Konsole, both fail the same way. I ran both scripts and they both seem to do the same thing ... output a whole pile of text. They both end with: ... Adds support for Zope Enterprise Objects" off "Adds support for Zope Enterprise Objects" zlib " (+ ) Adds support for zlib (de)compression" on "Adds support for zlib (de)compression" Mark The long output string is just repeating the command line for dialog. Lets try a simpler example, in a console run the followong command (as one line). dialog --checklist "Pick One" 12 20 3 one " 1 " off two " 2 " off three " 3" on tess root # dialog --checklist "Pick One" 12 20 3 one " 1 " off two " 2 " off three " 3" Illegal instruction tess root # er, maybe I should just re-emerge dialog? Mark I would say that is probably the problem. Please mark the bug as fixed if it works. Created attachment 17207 [details]
strace -f output against dialog
Re-emerged ufed, no joy:
mark@tess mark $ dialog --checklist "Pick One" 12 20 3 one "1" off two "2" off
three "3" on
Illegal instruction
mark@tess mark $
strace -f attached.
You need to re-emerge dialog, not ufed. Sorry, that's what I meant. I re-emerged dialog, not ufed. Brain burp ... Mark Fixed by re-emerging ncurses. Fixed by re-emerging ncurses. I'm having the same problem as Mark. Had ufed installed and working for some time but have not used it at least since upgrading to Portage 2.50 more than a month ago. A couple of emerge system/worlds later and its broken. I tried re-emerging dialog & ncurses with to no avail. I tried the tests listed in the comments above but I got the same errors as Mark. |
