TexStudio freezes on Workstation 30

TexStudio on the Workstation version of FC30 will not run. The application comes up then freezes.

1 Like

if an upgrade or a fresh install , works great here

execute in terminal:

texstudio

and post any error here

1 Like

When use a terminal, I get

texstudio
          Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.

The application comes up, but I try to select a tex file to work on, it freezes.

Could you please try this workaround:

sudo dnf remove texstudio
rm -rf /home/youruserhere/.config/texstudio
sudo dnf install texstudio

Regards.,

1 Like

Is this advice the equivalent of ‘try turning it off, then turning it back on.’?

I get the same results as before.

No, it’s merely a test to see if a config file could cause the issue.

I just did a fresh install of texstudio and it seems to work OK here too. Does the journal say anything about it by any chance? I have these packages installed (and quite a bit of texlive)

$ rpm -qa \*texstudio\* \*qt\*
qt-common-4.8.7-49.fc30.noarch
qt5-qtx11extras-5.12.1-1.fc30.x86_64
qt5-qtwebchannel-5.12.1-1.fc30.x86_64
qt-settings-30.0-1.fc30.noarch
qt5-qtbase-5.12.1-2.fc30.x86_64
qt5-qtenginio-1.6.2-22.fc30.x86_64
qt5-qtwebengine-freeworld-5.12.2-2.fc30.x86_64
sni-qt-0.2.7-0.2.20170217.fc30.x86_64
python-qt5-rpm-macros-5.11.3-6.fc30.noarch
qt5-qtlocation-5.12.1-1.fc30.x86_64
python3-qt5-base-5.11.3-6.fc30.x86_64
qtsingleapplication-qt5-2.6.1-35.fc30.x86_64
qt5-qtwayland-5.12.1-1.fc30.x86_64
qt5-qtdeclarative-5.12.1-1.fc30.x86_64
qt-4.8.7-49.fc30.x86_64
qt5-qtwebengine-5.12.2-2.fc30.x86_64
qt5-qtwebkit-5.212.0-0.34.alpha2.fc30.x86_64
qt5-qtserialport-5.12.1-1.fc30.x86_64
dbusmenu-qt-0.9.3-0.20.20160218.fc30.x86_64
qtlockedfile-qt5-2.4-28.20150629git5a07df5.fc30.x86_64
qt-x11-4.8.7-49.fc30.x86_64
qt5-qtwebsockets-5.12.1-1.fc30.x86_64
python3-pyqt5-sip-4.19.13-4.fc30.x86_64
texstudio-2.12.14-2.fc30.x86_64
qt5-qtbase-gui-5.12.1-2.fc30.x86_64
adwaita-qt4-1.0-6.fc30.x86_64
python3-qt5-webengine-5.11.3-6.fc30.x86_64
poppler-qt5-0.73.0-9.fc30.x86_64
gstreamer1-plugins-good-qt-1.16.0-1.fc30.x86_64
qt5-qttools-common-5.12.1-1.fc30.noarch
qt5-qtmultimedia-5.12.1-1.fc30.x86_64
qt5-qtsvg-5.12.1-1.fc30.x86_64
qt5-qtscript-5.12.1-1.fc30.x86_64
qt5-qttools-libs-designer-5.12.1-1.fc30.x86_64
qt5-qtxmlpatterns-5.12.1-2.fc30.x86_64
qt5-srpm-macros-5.12.1-1.fc30.noarch
adwaita-qt5-1.0-6.fc30.x86_64
qt5-qtbase-common-5.12.1-2.fc30.noarch
qt5-qtsensors-5.12.1-1.fc30.x86_64
qt5-qtconnectivity-5.12.1-1.fc30.x86_64
python3-qt5-5.11.3-6.fc30.x86_64
python3-qt5-webkit-5.11.3-6.fc30.x86_64
ibus-qt-1.3.3-21.fc30.x86_64
qt5-qttools-libs-help-5.12.1-1.fc30.x86_64
quazip-qt5-0.7.6-3.fc30.x86_64
1 Like

Here’s what I get

$ rpm -qa \*texstudio\* \*qt\*
qt5-qtsvg-5.12.1-1.fc30.x86_64
qt5-qtxmlpatterns-5.12.1-2.fc30.x86_64
qt5-qttools-libs-help-5.12.1-1.fc30.i686
polkit-qt5-1-0.112.0-15.fc30.x86_64
qtlockedfile-qt5-2.4-28.20150629git5a07df5.fc30.x86_64
libyui-mga-qt-1.0.3-0.17.gitb508e88.20140119.fc30.x86_64
dbusmenu-qt5-0.9.3-0.20.20160218.fc30.x86_64
qt5-qtbase-common-5.12.1-2.fc30.noarch
qt5-qtwayland-5.12.1-1.fc30.x86_64
qscintilla-qt5-2.11.1-1.fc30.i686
quazip-qt5-0.7.6-3.fc30.x86_64
qscintilla-qt5-2.11.1-1.fc30.x86_64
ibus-qt-1.3.3-21.fc30.x86_64
qt5-qttools-common-5.12.1-1.fc30.noarch
libaccounts-qt5-1.15-7.fc30.x86_64
qt5-qtgraphicaleffects-5.12.1-1.fc30.x86_64
libyui-qt-2.47.1-14.fc30.x86_64
dbusmenu-qt-0.9.3-0.20.20160218.fc30.x86_64
qt5-qttools-libs-help-5.12.1-1.fc30.x86_64
qt5-qtdeclarative-5.12.1-1.fc30.x86_64
qca-qt5-2.2.0-0.10.20181017.fc30.x86_64
qt5-qtquickcontrols-5.12.1-1.fc30.x86_64
qt-settings-30.0-1.fc30.noarch
qt5-qtbase-gui-5.12.1-2.fc30.i686
adwaita-qt4-1.0-6.fc30.x86_64
qt-4.8.7-49.fc30.x86_64
phonon-qt5-4.10.2-3.fc30.x86_64
gstreamer1-plugins-good-qt-1.16.0-1.fc30.x86_64
qt5-qtx11extras-5.12.1-1.fc30.x86_64
libyui-qt-graph-2.44.6-4.fc30.x86_64
qtsingleapplication-qt5-2.6.1-35.fc30.x86_64
poppler-qt5-0.73.0-9.fc30.x86_64
qca-qt5-ossl-2.2.0-0.10.20181017.fc30.x86_64
qt-x11-4.8.7-49.fc30.x86_64
adwaita-qt5-1.0-6.fc30.x86_64
qt5-qtquickcontrols2-5.12.1-1.fc30.x86_64
sni-qt-0.2.7-0.2.20170217.fc30.x86_64
qt-common-4.8.7-49.fc30.noarch
qt5-srpm-macros-5.12.1-1.fc30.noarch
qt5-qtbase-gui-5.12.1-2.fc30.x86_64
qt5-qtspeech-5.12.1-1.fc30.x86_64
qt-devel-4.8.7-49.fc30.x86_64
qt5-qttools-libs-designer-5.12.1-1.fc30.x86_64
qt5-qtscript-5.12.1-1.fc30.x86_64
texstudio-2.12.14-2.fc30.x86_64
qt5-qtbase-5.12.1-2.fc30.x86_64
grantlee-qt5-5.1.0-11.fc30.x86_64
qt5-qtbase-5.12.1-2.fc30.i686
qt5-qtspeech-speechd-5.12.1-1.fc30.x86_64

Nothing obvious there—anything in the journal logs?

1 Like

How do I get to the logs?

1 Like

Have a look at this quick-doc: https://docs.fedoraproject.org/en-US/quick-docs/viewing-logs/

1 Like

I don’t seeanything that stands out, but I’m not used to reading logs.

1 Like

How about the output of:

journalctl -b | tail -n 50

right after you see this freeze? That gives us the last 50 lines of your logs which should contain messages from texstudio if any. There shouldn’t be any personal information there, but please do check and remove anything that you’re not OK with sharing here.

Also worth trying:

texstudio --no-session
1 Like

Try to delete only this file rm -r /home/youruserhere/.config/texstudio.ini

and start again

1 Like
journalctl -b | tail -n 50
May 04 16:46:20 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 04 16:46:20 localhost.localdomain systemd[1]: packagekit.service: Main process exited, code=killed, status=15/TERM
May 04 16:46:20 localhost.localdomain systemd[1]: packagekit.service: Succeeded.
May 04 16:47:45 localhost.localdomain org.gnome.Shell.desktop[13185]: IPDL protocol Error: Received an invalid file descriptor
May 04 16:48:07 localhost.localdomain cupsd[1013]: REQUEST localhost - - "POST / HTTP/1.1" 200 183 Renew-Subscription successful-ok
May 04 16:50:52 localhost.localdomain NetworkManager[997]: <info>  [1557003052.6900] device (wlp2s0): set-hw-addr: set MAC address to 56:B5:3C:CC:47:D6 (scanning)
May 04 16:50:52 localhost.localdomain NetworkManager[997]: <info>  [1557003052.7011] device (wlp2s0): supplicant interface state: inactive -> disabled
May 04 16:50:52 localhost.localdomain wpa_supplicant[1118]: wlp2s0: Reject scan trigger since one is already pending
May 04 16:50:52 localhost.localdomain NetworkManager[997]: <info>  [1557003052.7012] device (p2p-dev-wlp2s0): supplicant management interface state: inactive -> disabled
May 04 16:50:52 localhost.localdomain NetworkManager[997]: <info>  [1557003052.7051] device (wlp2s0): supplicant interface state: disabled -> inactive
May 04 16:50:52 localhost.localdomain NetworkManager[997]: <info>  [1557003052.7052] device (p2p-dev-wlp2s0): supplicant management interface state: disabled -> inactive
May 04 16:53:02 localhost.localdomain org.gnome.Shell.desktop[13185]: libinput error: client bug: timer event6 debounce: offset negative (-189ms)
May 04 16:53:02 localhost.localdomain org.gnome.Shell.desktop[13185]: libinput error: client bug: timer event6 debounce short: offset negative (-222ms)
May 04 16:53:11 localhost.localdomain thunar[15003]: Name 'org.freedesktop.FileManager1' lost on the message dbus.
May 04 16:53:11 localhost.localdomain Thunar.desktop[13185]: ThunarThumbnailer: Failed to retrieve supported types: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
May 04 16:56:07 localhost.localdomain NetworkManager[997]: <info>  [1557003367.6946] device (wlp2s0): set-hw-addr: set MAC address to E6:9D:68:71:1A:2A (scanning)
May 04 16:56:07 localhost.localdomain NetworkManager[997]: <info>  [1557003367.7054] device (wlp2s0): supplicant interface state: inactive -> disabled
May 04 16:56:07 localhost.localdomain wpa_supplicant[1118]: wlp2s0: Reject scan trigger since one is already pending
May 04 16:56:07 localhost.localdomain NetworkManager[997]: <info>  [1557003367.7054] device (p2p-dev-wlp2s0): supplicant management interface state: inactive -> disabled
May 04 16:56:07 localhost.localdomain NetworkManager[997]: <info>  [1557003367.7055] device (wlp2s0): supplicant interface state: disabled -> inactive
May 04 16:56:07 localhost.localdomain NetworkManager[997]: <info>  [1557003367.7056] device (p2p-dev-wlp2s0): supplicant management interface state: disabled -> inactive
May 04 16:58:47 localhost.localdomain org.gnome.Shell.desktop[13185]: libinput error: client bug: timer event6 debounce: offset negative (-1ms)
May 04 16:58:47 localhost.localdomain org.gnome.Shell.desktop[13185]: libinput error: client bug: timer event6 debounce short: offset negative (-14ms)
May 04 16:59:13 localhost.localdomain org.gnome.Shell.desktop[13185]: IPDL protocol Error: Received an invalid file descriptor
May 04 17:01:01 localhost.localdomain CROND[15463]: (root) CMD (run-parts /etc/cron.hourly)
May 04 17:01:01 localhost.localdomain run-parts[15466]: (/etc/cron.hourly) starting 0anacron
May 04 17:01:01 localhost.localdomain run-parts[15472]: (/etc/cron.hourly) finished 0anacron
May 04 17:01:22 localhost.localdomain NetworkManager[997]: <info>  [1557003682.6931] device (wlp2s0): set-hw-addr: set MAC address to 86:EE:8F:0E:D6:CA (scanning)
May 04 17:01:22 localhost.localdomain NetworkManager[997]: <info>  [1557003682.7066] device (wlp2s0): supplicant interface state: inactive -> disabled
May 04 17:01:22 localhost.localdomain wpa_supplicant[1118]: wlp2s0: Reject scan trigger since one is already pending
May 04 17:01:22 localhost.localdomain NetworkManager[997]: <info>  [1557003682.7066] device (p2p-dev-wlp2s0): supplicant management interface state: inactive -> disabled
May 04 17:01:22 localhost.localdomain NetworkManager[997]: <info>  [1557003682.7067] device (wlp2s0): supplicant interface state: disabled -> inactive
May 04 17:01:22 localhost.localdomain NetworkManager[997]: <info>  [1557003682.7068] device (p2p-dev-wlp2s0): supplicant management interface state: disabled -> inactive
May 04 17:04:02 localhost.localdomain su[22601]: pam_unix(su:session): session closed for user root
May 04 17:04:02 localhost.localdomain audit[22601]: USER_END pid=22601 uid=1000 auid=1000 ses=8 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask acct="root" exe="/usr/bin/su" hostname=localhost.localdomain addr=? terminal=pts/0 res=success'
May 04 17:04:02 localhost.localdomain audit[22601]: CRED_DISP pid=22601 uid=1000 auid=1000 ses=8 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/su" hostname=localhost.localdomain addr=? terminal=pts/0 res=success'
May 04 17:05:56 localhost.localdomain wpa_supplicant[1118]: wlp0s20u9: WPA: Group rekeying completed with 5c:e2:8c:48:45:d2 [GTK=TKIP]
May 04 17:06:37 localhost.localdomain NetworkManager[997]: <info>  [1557003997.6933] device (wlp2s0): set-hw-addr: set MAC address to 82:8F:42:03:88:B9 (scanning)
May 04 17:06:37 localhost.localdomain NetworkManager[997]: <info>  [1557003997.7044] device (wlp2s0): supplicant interface state: inactive -> disabled
May 04 17:06:37 localhost.localdomain wpa_supplicant[1118]: wlp2s0: Reject scan trigger since one is already pending
May 04 17:06:37 localhost.localdomain NetworkManager[997]: <info>  [1557003997.7044] device (p2p-dev-wlp2s0): supplicant management interface state: inactive -> disabled
May 04 17:06:37 localhost.localdomain NetworkManager[997]: <info>  [1557003997.7194] device (wlp2s0): supplicant interface state: disabled -> inactive
May 04 17:06:37 localhost.localdomain NetworkManager[997]: <info>  [1557003997.7195] device (p2p-dev-wlp2s0): supplicant management interface state: disabled -> inactive
May 04 17:10:24 localhost.localdomain texstudio.desktop[13185]: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
May 04 17:10:25 localhost.localdomain org.gnome.Shell.desktop[13185]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1c00008 specified for 0x1c00006.
May 04 17:10:40 localhost.localdomain systemd[1]: Starting Hostname Service...
May 04 17:10:40 localhost.localdomain systemd[1]: Started Hostname Service.
May 04 17:10:40 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 04 17:11:10 localhost.localdomain systemd[1]: systemd-hostnamed.service: Succeeded.
May 04 17:11:10 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

This is know bug’s and happen only in fedora maybe a regression from upgrade:

1.- Could you try to start textstudio as root:

sudo textstudio

if this works the problem is in your user side…

2.- Try to look for a workaround in your user:

Could you perhaps try to change the texstudio style? It seems is failing and perhaps it’s working when using another one “default”. I think it should be possible by editing:

cat ~/.config/texstudio/texstudio.ini | grep X11

~/.config/texstudio/texstudio.ini Please look for the line X11\Style=[wharever] and change it to X11\Style=default , Hope this helps

3.- If this doesn’t work try this, copy root configuration file to your user:

.- Comment 13 Glenn L. Jenkins 2016-09-06 21:45:46 UTC

REFERENCE

.- 1369909, also how to debug.
.- 1414849

CONCLUSION

I suggest to you open a new one, because is a regression, you can login with your FAS -> https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/ and provide all this information…

2 Likes

Please in the future suggest something less destructive, like:

mv /home/**youruserhere**/.config/texstudio{,.bak}
1 Like

Thx, for your suggestion but in this case doesn’t matter because the configuration is created everytime the program is started or reinstall the package

Regards.,

1 Like

I just reloaded my old texstudio.ini and everything works fine now.

1 Like

Yes, the program will run with or without the configuration data, but that’s not my point. My point is that it’s destructive to a user who has done any sort of configuration.