ManjaroThis forum is for the discussion of Manjaro Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) checking available disk space [######################] 100%
:: Processing package changes...
(1/1) installing eterm [######################] 100%
Etbg_update_list: Generating pixmap list file from images in tile/ and scale/...
Old pixmap list will be saved in pixmaps.list.old
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[bwave@manjaroieo ~]$ Eterm
Eterm: Error: Unable to load font "-adobe-helvetica-medium-r-normal--10-100-75-75-p-56-iso8859-1". Falling back on "fixed"
when It opens up the promt does not show up like normal, it has its color but looks like it is caught in a loop?
I'm not too sure how well one can see it I had to use
import -display :0 -window root screenshot filename.jpg
to get a shot of the screen.
I do not know what is causing the prompt to hang like it is. I even tried removing my home .bashrc to have it default to the systems and no change.
I'm not sure again.... /etc/profile sets some defaults (on PS1). Also you can set it in ~/.bashrc, but I can't find any location, where it is actually cleared. But probably you have set something.
Also you can set it directly in Eterm - to check at least if that works.
What do you mean by hanging? If it eats up some resources you can see it with htop or pstree. Does bash started at all (inside)?
I'm not sure again.... /etc/profile sets some defaults (on PS1). Also you can set it in ~/.bashrc, but I can't find any location, where it is actually cleared. But probably you have set something.
Also you can set it directly in Eterm - to check at least if that works.
What do you mean by hanging? If it eats up some resources you can see it with htop or pstree. Does bash started at all (inside)?
it looks like as if you start an app within a terminal, then the promt sits as it is, that is how it is when first started off a menu, or within a different term. I removed my .bashrc from home and it didn't help, so I put it back.
there is no output when starting it from a terminal so I have no errors or warning about that. Let me go bounce into manjaro and check /etc/profile,and my bashrc PS1, I'm in slack right now setting up e16 in it.
I will copy over .bashrc from slack to see if that helps as Eterm in slack is working without issues.
Does bash started at all (inside)?
What if you set PS1 manually (inside)?
Oh yes, and why did you try to modify bashrc and other files which seems ok in every other terminal?
1. Does bash started at all (inside)? color me ignorant, I have no idea what that means, or how to do that, inside what,
Eterm config file, that'd I'd have to research?
2. What if you set PS1 manually (inside)? read ans. 1
3. Oh yes, and why did you try to modify bashrc and other files which seems ok in every other terminal?
I removed it, by mv .bashrc bashrc to get it out of the way just in case Eterm was being finicky to
where my .bashrc might be messing it up, because no prompt, .bashrc controls the prompt, so remove
.bashrc and let it use the systems default prompt. then see what happens, kind of like what you're
telling me to try about a prompt, that I (color me ignorant) have no idea how to do.
There is probably rather something wrong with the config file of eterm. I would copy the working one from Slackware,
eterm has --debug, it seems, but i don't know if it might help.
that's an idea, I did how ever use an already compiled working binary from slack and copied it over onto manjaro and got that same issue.
MOD:
Code:
[bwave@manjaroieo ~]$ Eterm --debug
Eterm: Error: long option --debug requires an integer value
Eterm: Error: Attempting to continue, but strange things may happen.
Eterm: Error: Can't open display ebug. Set $DISPLAY or use --display
[bwave@manjaroieo ~]$ Eterm --debug --display 0
Eterm: Warning: Unable to resolve "bottom_right" as a color name. Falling back on "#000000".
still nothing, and still hanging. must be something with this distro.
that's an idea, I did how ever use an already compiled working binary from slack and copied it over onto manjaro and got that same issue.
MOD:
Code:
[bwave@manjaroieo ~]$ Eterm --debug
Eterm: Error: long option --debug requires an integer value
Eterm: Error: Attempting to continue, but strange things may happen.
Eterm: Error: Can't open display ebug. Set $DISPLAY or use --display
[bwave@manjaroieo ~]$ Eterm --debug --display 0
Eterm: Warning: Unable to resolve "bottom_right" as a color name. Falling back on "#000000".
still nothing, and still hanging. must be something with this distro.
No, this is not the distro, it looks like the eterm config[file] is corrupted.
Quote:
Originally Posted by BW-userx
QUOTE=pan64
1. Does bash started at all (inside)? color me ignorant, I have no idea what that means
Ok, so usually a terminal emulator is a graphical program which can draw nice frame, menu, buttons, can be resized and also it will draw the fonts for you. But that's all. The emulator always start a program which will run "inside" (the frames), and will use that area. Usually it is the shell itself, but can be anything. bash will see nothing but a virtual terminal, which has rows and columns, stdin/stdout/stderr and probably some other features.
So the question was if eterm could start bash (or whatever) or not. You can easily check it with pstree for example (which will show you if there was a child app).
Quote:
Originally Posted by BW-userx
Eterm config file, that'd I'd have to research?
Yes, probably there is a config file somewhere which can rule the behaviour of eterm, but not the program running inside. You can use lsof, strace for example to find it, if you have no better idea.
Quote:
Originally Posted by BW-userx
2. What if you set PS1 manually (inside)? read ans. 1
If bash was really started and responsive (so accepts input and can execute commands) you can set PS1='$ ' (for example) and check if that was really the issue.
Quote:
Originally Posted by BW-userx
3. Oh yes, and why did you try to modify bashrc and other files which seems ok in every other terminal?
I removed it, by mv .bashrc bashrc to get it out of the way just in case Eterm was being finicky to
where my .bashrc might be messing it up, because no prompt, .bashrc controls the prompt, so remove
.bashrc and let it use the systems default prompt. then see what happens, kind of like what you're
telling me to try about a prompt, that I (color me ignorant) have no idea how to do.
You may destroy your system by modifying system wide config files (or just user specific configs) and I'm not really sure this is the right way to catch this issue.
As far i know:
The config files shipped with the package of the distro are either
a) systemwide, /etc location or
b) sometimes come only as an example, /usr/share ... (doc sounds right)
the admin has to copy over to /etc (though that seems to be used too)
c) the config files in the users home either get copied by the user itself or get created automatically, when the user starts the program and it doesn't find a users config file. Most of the time either ~/.progname or ~/.config/progname.
If there is no users config file, the systemwide will be applied.
To make a long story short: you sure will want to either find a known working example for the user or find out where eterm has it's systemwide config file.
eterm's manpage doesn't say it. I would try "locate eterm" and "locate Eterm"; grep for usr or etc too;
perhaps "whereis eterm" (again also with uppercase).
diff with slackwares config file, make a backup of it, copy slackwares config file.
Or: eterm in manjaro is simply broken ?
---
Well: the brutal truth, i for one would probably simply use a different terminal-emulator. But as it is a bit different, i assume you really want it, so that solution is out.
In slack where it is not having issues, looking into configs it seems that each theme has its own config, by some magical programming means with in e16 if that theme gets changes then Eterm changes its theme to match it, if there is one.
under themes, and configuration, on the bottom there.
so config are out, but not all of the way out. I still think it is something else, what i do not know, straight from the same source code Slack uses and Manjaro no go, slack it's a go.
If I remove all of my themes from /usr/share/Eterm/themes it still has to have a default setting written within the code itself, or it should anyways.
who ever submitted this I wonder if they even checked to make sure it worked on manjaro, if yes why, and why is it not still working?
As far i know:
The config files shipped with the package of the distro are either
a) systemwide, /etc location or
b) sometimes come only as an example, /usr/share ... (doc sounds right)
the admin has to copy over to /etc (though that seems to be used too)
c) the config files in the users home either get copied by the user itself or get created automatically, when the user starts the program and it doesn't find a users config file. Most of the time either ~/.progname or ~/.config/progname.
If there is no users config file, the systemwide will be applied.
To make a long story short: you sure will want to either find a known working example for the user or find out where eterm has it's systemwide config file.
eterm's manpage doesn't say it. I would try "locate eterm" and "locate Eterm"; grep for usr or etc too;
perhaps "whereis eterm" (again also with uppercase).
diff with slackwares config file, make a backup of it, copy slackwares config file.
Or: eterm in manjaro is simply broken ?
---
Well: the brutal truth, i for one would probably simply use a different terminal-emulator. But as it is a bit different, i assume you really want it, so that solution is out.
it is the system itself that is broken for Eterm
command.c
Code:
void
main_loop(void)
{
printf("Im main loop\n");
/* int ch; */
register int ch;
D_CMD(("PID %d\n", getpid()));
printf(("PID %d\n", getpid()));
printf(("Command buffer base == %8p, length %lu, end at %8p\n", cmdbuf_base, CMD_BUF_SIZE, cmdbuf_base + CMD_BUF_SIZE - 1));
D_CMD(("Command buffer base == %8p, length %lu, end at %8p\n", cmdbuf_base, CMD_BUF_SIZE, cmdbuf_base + CMD_BUF_SIZE - 1));
output
Code:
[userx@manjaroieo Eterm]$ src/Eterm
Im main loop
Eterm: Error: Received terminal signal SIGSEGV (11)
Eterm: Error: Attempting to dump a stack trace....
Eterm: Error: Your system does not support any of the methods Eterm uses. Exiting.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
