texstudio segfaults after recent update

ExecutorElassus

This is all I see in dmesg (I tried starting texstudio several times):

Hu · Administrator Joined: 06 Mar 2007 Posts: 22810

Segmentation faults are always either a hardware fault or a software bug. What did you update since it was last working? What backtrace do you get when it crashes?

Although removing a virtual should not matter here, I will reiterate the oft-posted advice that you should use emerge --depclean, not emerge --unmerge, to remove packages. Forced-unmerge relies on the administrator not making a bad decision about what to remove. A poor choice can easily break the system.

ExecutorElassus · Posted: Wed Dec 11, 2024 12:55 pm Post subject:

genlop says:

dmpogo · Advocate Joined: 02 Sep 2004 Posts: 3449 Location: Canada

Recent update switched texstudio from Qt5 to Qt6. So you are probably guessing right that it is Qt related

ExecutorElassus · Posted: Thu Dec 12, 2024 5:04 am Post subject:

I've had it working with the Qt6 version, though. Like I said, it worked up until the `emerge world` I did on the 10th. So while it might have been Qt-related, it's not simply from switching to using Qt6.

ExecutorElassus · Posted: Thu Dec 12, 2024 8:15 am Post subject:

This is the end of the stacktrace:

wjb · Posted: Thu Dec 12, 2024 11:25 am Post subject:

Try removing (or renaming) the config and see if anything changes

i.e. ~/.config/texstudio/

(because it shows up in the stack trace and old settings may be upsetting the new thing)

sam_ · Developer Joined: 14 Aug 2020 Posts: 2020

ExecutorElassus · Posted: Thu Dec 12, 2024 1:39 pm Post subject:

OK, I've built texstudio so that gdb can run it.

Hu · Administrator Joined: 06 Mar 2007 Posts: 22810

No, that does not help. run ran until a breakpoint. You set a breakpoint on main, so the program stopped before doing anything of consequence. Run it without a breakpoint. You want output like:

ExecutorElassus · Posted: Thu Dec 12, 2024 2:30 pm Post subject:

Hi Hu,

I'll post outputs below. However, I also renamed ~/.config/texstudio/ to ~/.config/texstudio.old/, and now it starts. And from there I tried replacing the newly generated texstudio.ini with the old one, and it segfaulted.

When I run gdb without a breakpoint, I get this:

ExecutorElassus · Posted: Thu Dec 12, 2024 4:05 pm Post subject:

arrgh, I have another question.

So, after starting texstudio with an empty config, it runs, but now it can't compile documents because it can't find 'luatexja-fontspec.sty'. This file is located at '~/path/tex-local/texlive/texmf-dist/tex/luatex/luatexja/addons/luatexja-fontspec.sty'.

How do I make it so my newly running texstudio can find this?

UPDATE: I moved the above questions to a separate thread, here, since it's something of a different topic.
UPDATE2: nevermind that post at all; I deleted it. Turns out TexStudio was *lying* about not being able to find awesome-cv.cls (it found it just fine), and I fixed my paths so it could find the fontspec.sty file. So now, I THINK (??) everything's solved?

Also, now the "Open File" dialogue is this hideous bright color scheme. How do I fix that so it follows the WM's dark color scheme?

Cheers,

EE