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
Reply to: