Red Hat Bugzilla – Bug 803042
[abrt] texmaker-3.2.2-1.fc16: Process /usr/bin/texmaker was killed by signal 11 (SIGSEGV)
Last modified: 2012-09-25 12:36:59 EDT
libreport version: 2.0.8
reason: Process /usr/bin/texmaker was killed by signal 11 (SIGSEGV)
time: Wed 14 Mar 2012 06:54:36 EST
backtrace: Text file, 41859 bytes
build_ids: Text file, 5535 bytes
dso_list: Text file, 12419 bytes
environ: Text file, 4587 bytes
maps: Text file, 34657 bytes
:Mar 13 21:30:50 politemadness kernel: [928942.024597] texmaker: segfault at 0 ip 4569b109 sp bf814ee0 error 4 in libQtGui.so.4.8.0[452a3000+abd000]
:Mar 13 21:32:37 politemadness abrt: Saved core dump of pid 22183 (/usr/bin/texmaker) to /var/spool/abrt/ccpp-2012-03-13-21:30:51-22183 (255938560 bytes)
:Mar 14 06:54:36 politemadness kernel: [942342.187676] texmaker: segfault at 730065 ip 00730065 sp bfde64ec error 14 in texmaker[802b000+41f000]
:Mar 14 06:54:54 politemadness abrt: Saved core dump of pid 4444 (/usr/bin/texmaker) to /var/spool/abrt/ccpp-2012-03-14-06:54:36-4444 (80019456 bytes)
Created attachment 569777 [details]
Created attachment 569778 [details]
Created attachment 569779 [details]
Created attachment 569780 [details]
Created attachment 569781 [details]
*** Bug 799697 has been marked as a duplicate of this bug. ***
I was compiling a beamer file then Texmaker crashed
OS Release: Fedora release 16 (Verne)
Created attachment 576126 [details]
texmaker-3.5-1.fc17 has been submitted as an update for Fedora 17.
texmaker-3.5-1.fc16 has been submitted as an update for Fedora 16.
texmaker-3.5-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing texmaker-3.5-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
texmaker-3.5-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.