texmaker stops responding to keyboard after saving

Bug #348028 reported by Rohan Agrawal
88
This bug affects 7 people
Affects Status Importance Assigned to Milestone
qt4-x11 (Ubuntu)
Invalid
Undecided
Unassigned
texmaker (Ubuntu)
Fix Released
Undecided
Scott Kitterman

Bug Description

Description: Ubuntu jaunty (development branch)
Release: 9.04

libqtcore4:
  Installed: 4.5.0-0ubuntu2
  Candidate: 4.5.0-0ubuntu2
  Version table:
 *** 4.5.0-0ubuntu2 0
        500 http://ubuntu.media.mit.edu jaunty/main Packages
        100 /var/lib/dpkg/status

libqtgui4:
  Installed: 4.5.0-0ubuntu2
  Candidate: 4.5.0-0ubuntu2
  Version table:
 *** 4.5.0-0ubuntu2 0
        500 http://ubuntu.media.mit.edu jaunty/main Packages
        100 /var/lib/dpkg/status

Create a document in texmaker, make a few changes, and then save it. After saving, you will no longer be able to edit the document as texmaker stops responding to keyboard input.

The bug is in the qt4 libraries, not in texmaker, since downgrading qt to the intrepid version solves the problem, but downgrading texmaker does not solve it.

Tags: jaunty

Related branches

Rohan Agrawal (agrawalr)
description: updated
Revision history for this message
TerpInHotLanta (ccampjr) wrote :

Since the upgrade to Jaunty, I too have seen the same problem and there seems to be a redraw problem-- some times when opening TexMaker, many of the headers (File, Edit, etc) do not appear until the cursor is dragged over there positions or the entire TexMaker window is moved.

Not sure if the redraw problem is related, but i thought I'd include it.

Revision history for this message
Rohan Agrawal (agrawalr) wrote :

I have marked this as confirmed since TerpInHotLanta has confirmed it and there are several duplicates.

Changed in qt4-x11:
status: New → Confirmed
Revision history for this message
scandido (scandido) wrote :

I can also confirm I have this problem.

Revision history for this message
mvavrek (mattvavrek) wrote :

Bug seems to be fixed with most recent updated packages in Jaunty as of April 1, 2009

Revision history for this message
TerpInHotLanta (ccampjr) wrote :

Works for me, but the program still is missing buttons, and isn't redrawn quickly... time to search for other bugs.

Revision history for this message
scandido (scandido) wrote :

Even with yesterday and today's updates, it still does not work for me. It does allow me to retain the cursor after saving the first time but after two or three changes and saves the cursor disappears again.

Revision history for this message
der_vegi (m-may) wrote :

I have the same problem on a fully updated Jaunty (amd64). After compiling a document a couple of times and editing in between, the editor does not accept keyboard input any more. Mouse still works.
Interesting: The keyboard shortcuts to access the menu Alt + something also work. And if I click in "structure" on "LABELS", the editor suddenly accepts input again. If I click on the editor window, then, the problem is there again. So this might have to do something with the focus?
The problem with headers not appearing, TerpInHotLanta mentioned, does not apply for me.

Revision history for this message
Rohan Agrawal (agrawalr) wrote :

My situation is identical to der_vegi's.

Revision history for this message
Martin Topinka (martin-topinka) wrote :

I can confirm that I still can't see the cursor either type in any text after saving in Jaunty Beta (last update 3rd April 09). So the bug is still present.

Revision history for this message
der_vegi (m-may) wrote :

Hm, maybe this bug is not related to qt4-x11 but rather to texmaker due to some incompatibility with newer qt versions?

der_vegi (m-may)
tags: added: jaunty
Revision history for this message
gotigersducksvols (moseley-daniel) wrote :

I too have this error. The bug is still present as of the 7th of April.

Revision history for this message
Fledi (realfledi) wrote :

Same problem here. I can edit and compile tex-files, as the output opens texmaker loses its focus (as it should). Closing the dvi/ps/pdf without doing anything to texmaker works, the courser is there again. I can even move it around with the keyboard. But as soon as I click in the editor the courser disappears and won't come back 'till I restart texmaker.

Revision history for this message
Tomáš Pikálek (tpikalek) wrote :

Here is a patch that should fix it (but I didn't try it):
http://bugs.gentoo.org/262151

Revision history for this message
Tomáš Pikálek (tpikalek) wrote :

I applied the patch and it seems to fix the problem. So please, include it in Ubuntu package. Thanks.

Revision history for this message
Rohan Agrawal (agrawalr) wrote :

Here is a debdiff for the patch from gentoo.

Changed in qt4-x11 (Ubuntu):
status: Confirmed → Invalid
Changed in texmaker (Ubuntu):
status: New → Confirmed
Rohan Agrawal (agrawalr)
Changed in texmaker (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Rohan Agrawal (agrawalr) wrote :

Now that there is patch, it would be good if a MOTU could take a look at it.

Revision history for this message
tropicflite (tropicflite) wrote :

I have the same issue, but I'm not sure how to apply the patch. Can someone please give the method?

Revision history for this message
Rohan Agrawal (agrawalr) wrote :
Revision history for this message
Papadakos Panagiotis (papadako) wrote :

Yep, it would be nice to have this fixed!

Revision history for this message
Daniel Holbach (dholbach) wrote :

It seems texmaker is using quilt. Could you make use of it too?

https://wiki.ubuntu.com/PackagingGuide/Howtos/Quilt
https://wiki.ubuntu.com/UbuntuDevelopment/PatchTaggingGuidelines

Could you also forward the patch to the upstream author please? :-)

Revision history for this message
Chris Jones (jones-home) wrote :

I would like to add my vote to this. I am still struggling with an unusable TexMaker on 14 Apr in Jaunty (AMD64). I am using Gnome WM.

Revision history for this message
Scott Kitterman (kitterman) wrote :

I suspect that some of you with redraw issues have Intel video. If you do, I'd recommend reviewing the Intel video section of the RC release notes for options that may help.

I'll try and review the patch later tonight.

Changed in texmaker (Ubuntu):
assignee: nobody → kitterman
Revision history for this message
tropicflite (tropicflite) wrote :

I made this .deb using Tomáš patch, and it seems to fix the problem on my system (Jaunty 32 release candidate). I removed the old version using synaptic 'mark for complete removal' and installed this version doing

sudo dpkg -i texmaker_1.8-1ubuntu1_i386.deb

I also rebooted, probably unnecessary.

Appears to be stable, but install at your own risk.

Also, if posting this file here violates any rules I apologise in advance.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package texmaker - 1.8-1ubuntu1

---------------
texmaker (1.8-1ubuntu1) jaunty; urgency=low

  [ Rohan Agrawal ]
  * Fix a focus bug with newer versions of qt (lp: #348028)

  [ Scott Kitterman ]
  * Package fix as a patch and upload

 -- Scott Kitterman <email address hidden> Thu, 16 Apr 2009 23:04:04 -0400

Changed in texmaker (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Papadakos Panagiotis (papadako) wrote :

Even with this fix, sometimes I loose the focus again. This happens when I open the find console for example!

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 348028] Re: texmaker stops responding to keyboard after saving

I'd suggest file a new bug for that.

Revision history for this message
biomathman (bes-shapon) wrote :

I still have this bug using texmaker in the Jaunty official 9.04 AMD-64 release (not the beta) which I installed from scratch on 9/25/09, with the latest version of texmaker, which I presume is the "fixed" texmaker-1.8-1ubuntu1.

Texmaker will work fine for a while but randomly stops accepting keyboard input. Sometimes this follows a file save (but not always); sometimes it follows a pdf-tek (but not always); sometimes it follows an attempt to copy something from a different file (in another open tab, but not always); sometimes it happens after doing a search and replace (but not always); and sometimes I don't know why it happens. The only workaround I've found is to quite texmaker and reload the file.

Core-i7 920/asus P6T/12GB

Revision history for this message
kaphi (csae3318) wrote :

I got a similar bug with texmaker 1.8 and Jaunty: when I click into the log messages I can't set the focus/cursor back to the editor area anymore nor write anything. The log keeps highlighted until choosing a section from "Structure"

Revision history for this message
Razi Alavizadeh (srazi) wrote :

I work on a patch for texmaker that adds support for bidirectional editing and right to left languages, and I see this bug,
I report it to Qt developer

http://www.qtsoftware.com/developer/task-tracker/index_html?method=entry&id=250064

In that page they say that they fixed the bug for Qt4.5.1 ,
I attached the patch file for this bug.

If you interesting to bidirectional patch you can find download links and screenshots in my weblog:

download links for bidi patch: http://srazi.blogfa.com/page/biditexmaker.aspx
bidi screenshots: http://srazi.blogfa.com/page/bidi-screenshots.aspx

patch for losing focus is attached.

Revision history for this message
MrPok (wiebenik) wrote :

I also frequently have this bug on 2009-06-09, having run all updates using "Update Manager" (probably not any of them was related to this problem).
My typical usage of Texmaker involves clicking the "Quick build" button a lot ..

On the TexMaker website an overview of the new version 1.9 (May 21 2009)says:
" Qt >= 4.5.1 is now required "

Side-note: kind of a dramatic bug in a text editor :-P

Revision history for this message
everflux (tklaunchpad) wrote :

Problem still occurs here, too. (Completely updated jaunty amd64)
Especially after searching for text, the focus can not be established to the text document. This makes the program completely useless.

Revision history for this message
mercutio22 (macabro22) wrote :

Yes, this is really annoying

Revision history for this message
Alaak (alaak-gmx) wrote :

I also have this bug. It happens for example when I click on "Next Latex Error".

A workaround without restarting texmaker is to choose some of the latex templates from the "Latex" Menu and insert them into your file. Then you get your cursor back. Of course you have to delete the inserted code afterwards.

Revision history for this message
gianluca (antonelli) wrote :

I also have this problem for

Texmaker Version: 1.8-1ubuntu1

on

uname -a
Linux trinity 2.6.28-16-generic #55-Ubuntu SMP Tue Oct 20 19:48:24 UTC 2009 i686 GNU/Linux

Revision history for this message
Sebastian (guttenb) wrote :

I have the same problem with lyx 1.6.4 in Hardy instead of texmaker. So perhaps it's not only a texmaker-problem?
There is a bug-report at lyx: http://www.lyx.org/trac/ticket/5917

Revision history for this message
Sebastian (guttenb) wrote :

Sorry, I did not mean Hardy but Karmic. That's different than what is mentioned in the above link, but I've observed it myself with Karmic with Qt version 4.5.3really4.5.2.

Revision history for this message
Martin Topinka (martin-topinka) wrote : Invitation to connect on LinkedIn

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Martin

Martin Topinka
Post-doc at University College Dublin
Ireland

Confirm that you know Martin Topinka:
https://www.linkedin.com/e/hp0l6p-hstolx8s-11/isd/5850783741894479872/lyRK-5Zh/?hs=false&tok=10Rhj2SFwtM681

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/hp0l6p-hstolx8s-11/I6odceHdr9aOX0TIwS2qgUkdDNAuOououuRsHnp/goo/348028%40bugs%2Elaunchpad%2Enet/20061/I6691658784_1/?hs=false&tok=1TPgNYYvYtM681

(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.