texmaker bug?

Dear list,

I run Texmaker under Wmaker /Debian / testing on my laptop since couple of months without any unsolvable problem. I updated the Texmaker version this morning (to 1.6), and there is no way for a user to start it anymore... An icon is docked, but nothing else happens. However, the root can make it run. I browsed through the mailing lists and forums, and then have to say this is NOT a segmentation fault (similar to the bug reported for the previous TexMaker version). Starting it from the console doesn't say something else than

QObject::connect: Connecting from COMPAT signal (QTabWidget::currentChanged(QWidget*))

The root gets the same message.
I actually miss a trick to monitor what's going on when I start the program. Any idea?


Best regards,
Fabien


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: texmaker bug?
    ... I run Texmaker under Wmaker /Debian / testing on my laptop since couple of months without any unsolvable problem. ... the root can make it run. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
    (Debian-User)
  • Re: FC7-64 and texmaker problem
    ... When I start texmaker as normal user, ... segfaults, when I start texmaker as root, no problem at all. ...
    (Fedora)
  • Re: texmaker bug?
    ... latex, but with texmaker you hardly need to. ... Kile is the same thing ... so texmaker starts in a fraction of the time. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: texmaker bug?
    ... I didn't even know what texmaker was until today. ... people are always complaining about learning ... latex, but with texmaker you hardly need to. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)