after the upgrade to Ubuntu 16.04. I have a problem with my Texstudio. I used to compile with the shortcut F6, but after the upgrade it doesn't work anymore (shortcuts in other programs are doing fine).
Thanks in advance, Luca
This seems to be a known (and unfortunately, by now, rather long-standing) issue involving Qt5 (version 5 of Qt, the graphical toolkit used to create TeXStudio’s user interface). It has come up several times in TeXStudio’s bug tracker and other places; for example:
The solution is to install a version of TeXStudio that is built against the previous version, Qt4. Unfortunately, such a version is not available in Ubuntu’s default repositories. Instead, you can go to TeXStudio’s official download page and choose a link that says “QT 4”.
I found this solution here, it works fine for TeXStudio: Edit the file
and change the line
Exec=env UBUNTU_MENUPROXY= texstudio %F
NOTE: Remember to edit the file again after upgrade to version 2.12.2, released Jan 24, 2017.
NOTE (Jul 25, 2017): TeXStudio released yesterday: TeXstudio 2.12.6 (hg 6631:16db084dae24). Using Qt Version 5.5.1, compiled with Qt 5.5.1 R, works fine without any edit of file
/usr/share/applications/texstudio.desktop. The nightmare is over!!!
This is bug in Qt-5 package. Remove the "appmenu-qt5" package to get the shortcuts working again.
sudo apt remove appmenu-qt5
This seems to induce some changes in the appearance of menu buttons in TexStudio, but the shortcuts are enabled.
A different solution to what @Socob suggested might be (for Ubuntu 16.04) to navigate to the applications folder (/usr/share/applications) as sudo, right-click on 'texstudio' and select 'Properties'. Change the 'texstudio %F' to 'env UBUNTU_MENUPROXY= texstudio %F'. At least, that did it for me. I am not aware of any downsides to this.
EDIT: As pointed out by @Orion in the comment, the HUD stops working when using this solution. This has never been an inconvenience to me, since I never use the HUD, but as always, it's good to be aware of the possible downsides.
One workaround (worked for me) is to add the menu command to the toolbar (from Configure/Toolbars), then the assigned keyboard shortcut could work.