Bug 1369909

here is the upstream bug that was rejected as it seems to be fedora only.

https://sourceforge.net/p/texstudio/bugs/1833/

strange enough, on a machine updated from fedora 21 up to fedora 24 texstudio is running just fine with the exception that i can not chose the adwaita style (compared to running it as root on the fresh installed system) so there are more differences.

maybe some leftover configurations of qt avoid the problem that texstudio is not starting?

I don't really understand the last comment. Which Desktop Environment are you using and which style is selected in the copied over .ini file. Does this copied file have the same permissions?

gnome 3 standard fedora workstation installation. 
the selected style in the ini file was gtk+. yes it had the same permissions.

the last comment was:
I have 2 computer in my office. one has a new installation of fedora 24 and texstudio is unable to start as described above.
The other one was continuously upgraded over time from fedora ~20 to 24 and on this one i can use texstudio without a problem.

one difference though is, that i can not select the adwaita style on the latter machine. it is not even in the list (and i have no idea why. but maybe this is connected with this problem)

i was now able to start texstudio as describd in another post of the askfedora thread.
I downloaded the appimage of texstudio, deleted the .config folder of texstudio and started the appimage. afterwards I was able to start texstudio that was installed by the package manager.

There is no possibility to select any special Gtk+ theme for a Qt application. So it's not an error, that there's no Adwaita in the list of texstudio. Great that it's working now, although I've no idea what's causing the issue.

Could you please check if the following package is installed:
https://apps.fedoraproject.org/packages/qt5-qtstyleplugins
It would be even better if you could check if it's installed in the working and not installed in the failing installation.
Thanks a lot.

i made a screenshot to show you where i can select the adwaita style in the texstudio installation that won't start. this entry is not available on the other machine (where texstudio is starting fine) and the appimage.
It is the first dropdown under general settings.

qt5-qtsyleplugins is not installed on any of the machines.
at least that is what rpm -q qt5-qtsyleplugins says.

Created attachment 1193986 [details]
screenshot of the adwaita style on the crashing installation

this entry is only visible on the new installation of fedora 24 where texstudio fails to start.
also, if i select this style, texstudio freezes and won't start again.
deleting ~/.config/texstudio, starting the appimage that creates a new config folder makes it start again.

Ok, well any theme, which is related to Gtk+ won't start, so both adwaita and gtk+ will not be an option as theme for texstudio. 
Could you please check if the following command will start texstudio, regardless of the initial setup:
QT_STYLE_OVERRIDE=gtk2 texstudio

with a deleted config folder i get:

(texstudio:2077): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplayManager'

(texstudio:2077): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(texstudio:2077): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

(texstudio:2077): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(texstudio:2077): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(texstudio:2077): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(texstudio:2077): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(texstudio:2077): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplay'

(texstudio:2077): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(texstudio:2077): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed

(texstudio:2077): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(texstudio:2077): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed


and then it hangs until killed.

Thanks again for your patience. Would it be possible for you to provide us with a full backtrace with gdb. That would be really helpful. 

Please see https://fedoraproject.org/wiki/StackTraces#Obtaining_a_stack_trace_using_just_GDB

Created attachment 1194042 [details]
gdb backtrace

i followed the instructions given by the link.
the output is attached. Notice, that i had to interrupt (ctrl + c) the "execution" after the error messages mentioned earlier as the program did not terminate on its own.

Working with a fresh install of Fedora 24 so had no existing working install to copy.

Initially tried to run as root and copy the .config/texstudio to my own .config/ directory, then change the owner and group. That didn't work.

I then ran it as root, changed the window manager to (default - i think, or something other than gtk+) then went though the same process. This seems to have worked, however, I did fiddle with other things in between (on of which might have worked). Could someone test this as a work around?

(In reply to Glenn L. Jenkins from comment #13)
> Working with a fresh install of Fedora 24 so had no existing working install
> to copy.
> 
> Initially tried to run as root and copy the .config/texstudio to my own
> .config/ directory, then change the owner and group. That didn't work.
> 
> I then ran it as root, changed the window manager to (default - i think, or
> something other than gtk+) then went though the same process. This seems to
> have worked, however, I did fiddle with other things in between (on of which
> might have worked). Could someone test this as a work around?

I had the same problem with texstudio on my fresh Fedora 24 installation.
I followed the steps mentioned by G. L. Jenkins and it worked well.
The only thing to mention is:
After you copied the /root/.config/texstudio directory to your own .config directory and before you start texstudio with your user account (not root), you have to kill all other texstudio processes that are running in the background, otherwise it wont start even with this workaround.

I can confirm that this workaround cited by G. L. Jenkins and Jonas Kantic works as they describe.

It seems it works as root because thebroot user uses a different GTK+ theme. It also looks like this was ok in Fedora 24 betas and only this bug only surfaced in the final release. Maybe investigating what changed GTK-wise between the two would reveal more of the reason why it happens. Changing the theme to default in the config files also work.

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.