Fastfetch makes one tiny error (additional line) in print when not run in terminal start about fastfetch HOT 24 CLOSED

Please post the output of fastfetch --show-errors --multithreading false

from fastfetch.

from fastfetch.

Does fastfetch --structure Title:Separator:OS:Host:Kernel:Uptime:Packages:Resolution:DE:WM:WMTheme:Theme:Icons:Font:Cursor:Terminal:TerminalFont:CPU:GPU:Memory:Disk:Battery:Locale:Break:Colors have the same issue?

from fastfetch.

yes it does

from fastfetch.

Well it is fine when I erase "resolution" item. So it's caused because of this module I think

from fastfetch.

Thanks, that makes debugging easier.

from fastfetch.

Of course, not a problem.

from fastfetch.

Let me sum it up so i can be sure:

• It does work in a newly created terminal as expected
• If a command was executed before, it has the line
• It doesn't matter what command was executed before
• The line always appears after the Shell output, even when multi threading is disabled
• Removing the shell output doesn't remove the issue
• Removing the resolution output does tho
• Same behavior in bash and fish
• Same behavior in different terminal emulators

If all of that is true, tbh i have no idea what even could be the problem.

from fastfetch.

Does the following command have the issue?

fastfetch --multithreading false --structure Title:Separator:OS:Host:Kernel:Uptime:Packages:Resolution:DE:WM:WMTheme:Theme:Icons:Font:Cursor:CPU:GPU:Memory:Disk:Battery:Locale:Break:Colors

from fastfetch.

Yes, all of that is true. Also it does that on my second device (stable PC) with same OS setup.

Does the following command have the issue?

Yes it does

Maybe I could some day try some debugging myself. I know C a little. But not sure what I can do.

from fastfetch.

The best thing you can try is to go to src/common/detectTerminalShell.c. In line 190 you find static void getShellVersionGeneric(FFstrbuf* exe, const char* exeName, FFstrbuf* version). See if it gets executed. This is the only method that could potentially add a newline to an output. If it does, something is wrong with static void getShellVersion(FFstrbuf* exe, const char* exeName, FFstrbuf* version).

from fastfetch.

Ok I will look at that later. I will comment here once I try figure out something

from fastfetch.

I just fixed a bug in shell code, i don't believe this fixes your problem, but who knows.

from fastfetch.

Nope. Still same.

But found out another interesting fact. If I run fastfetch via run.sh it works properly, but if I run directly fastfetch it does not.

PS: I'm still planning to look at that code (especialy the func you recomended to me), but I haven't much time lately...

from fastfetch.

This is kinda expected, since calling a shell script spawns a new instance of sh, so running fastfetch through run.sh is always as if fastfetch is the first command to be entert in a terminal.

from fastfetch.

If you have latest version, can you please post the output of fastfetch --load-config devinfo-verbose?

from fastfetch.

from fastfetch.

Output of fastfetch --shell-format "Before {7} After"?

from fastfetch.

from fastfetch.

I have problem to debug the program.
With CLion nor with gdb I'm unable to reproduce the bug in debugging enviroment. As you said earlier:

This is kinda expected, since calling a shell script spawns a new instance of sh, so running fastfetch through run.sh is always as if fastfetch is the first command to be entert in a terminal.

debugger also creates new env, where the program runs perfectly.
If you have any advice, please tell me, but currently I don't know how to debug the program.

Also I have found solution. Kind of... By accident I discovered, that clear; sleep 0.1; fastfetch works perfectly fine. I don't now how's that possible, but it is what it is. It is not clean solution, so if you have any ideas?...

from fastfetch.

This sounds more like a problem with clear in your terminal emulator than with fastfetch. Is it possible that bug happens with other programs too that output very fast, like clear; cat /proc/cpuinfo?

from fastfetch.

well no, because it does it even without clear. Cmd fastfetch will produce bug but sleep 0.1; fastfetch won't. Even without the clear cmd

from fastfetch.

Closing this for now, maybe it gets fixed in future by luck.

from fastfetch.

Actually it was already fixed by luck, but I forget to report it there. Thanks for the effort.

from fastfetch.