texmaker crashes with segmentation fault

Bug #88891 reported by Peter Adam
48
Affects Status Importance Assigned to Milestone
texmaker (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: texmaker

Using PowerPC Architecture with Ubuntu 7.04, texmaker crashes directly after launch and produces following output:

~$ texmaker
Segmentation fault (core dumped)

Texmaker Version is 1.5

ProblemType: Crash
Architecture: powerpc
CrashCounter: 1
Date: Thu Mar 1 10:32:20 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/texmaker
Package: texmaker 1.5-1ubuntu1
ProcCmdline: texmaker
ProcCwd: /home/pedda
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: texmaker
StacktraceTop:
 QString::fromLocal8Bit () from /usr/lib/libQtCore.so.4
 QCoreApplication::arguments () from /usr/lib/libQtCore.so.4
 ?? () from /usr/lib/libQtGui.so.4
 ?? () from /usr/lib/libQtGui.so.4
 _SmcProcessMessage () from /usr/lib/libSM.so.6
Uname: Linux pedda-laptop 2.6.20-9-powerpc #3 Sun Feb 25 23:27:54 UTC 2007 ppc GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Peter Adam (pedda) wrote :
Revision history for this message
Alessio Caiazza (nolith) wrote :

Same problem for me.
PPC arch

Revision history for this message
Kurt Hallavej (kridhvidneger) wrote :

me too

amd64 arch

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

me too. amd64, daily build from march 16th.

Revision history for this message
Ian Jessen (07imj) wrote :

crashes for me on amd64. 1.5-1ubuntu1 (feisty)

William Grant (wgrant)
Changed in texmaker:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
gremi357 (gremi357) wrote :

me too ... amd64 feisty

Revision history for this message
Jonathan Gibert (jokot3) wrote :

the same here, amd64, pretty the same stacktrace

join gdb bt and strace outputs ...

Revision history for this message
Jonathan Gibert (jokot3) wrote :

strace output

Revision history for this message
Ernst (ernst-blaauw) wrote :

Here too... amd64 feisty

Revision history for this message
Cian Davis (davisc) wrote :

Crashes here on AMD64 Feisty, but not on my laptop with 32bit Feisty. 2 straces attached. From AMD64 machine (texmaker.strace) and from laptop (texmaker.strace.working)

Revision history for this message
Cian Davis (davisc) wrote :

Apologies. Thought attachments could be added 1 at a time.

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

still there on feisty final. the first time i start it, it survives a few seconds. from then on it crashes immediately: i can see the startup logo and for about half a second i see the main window before it crashes.

Revision history for this message
Richard Kleeman (kleeman) wrote :

Confirmed here on amd64. Some observations:
It works fine on i386
It crashes in gnome and kde (amd64) but not in enlightenment
It does not crash if run as
gksudo texmaker

Revision history for this message
Cian Davis (davisc) wrote :

Confirmed regarding it being OK if you run gksudo texmaker.

I've run strace on this. It outputs 74,254 lines. Files is attached.

Seems to be mainly 2 lines about "Resource not available". Counted these lines with sort texmaker-root.strace | uniq -c | sort -n

Output as follows (only lines counted more than 1,000 times)
   1755 read(16, "10497 (texmaker) S 10496 10497 1"..., 8191) = 249
   3092 read(16, "10497 (texmaker) S 10496 10497 1"..., 8191) = 246
   3210 read(16, "10497 (texmaker) S 10496 10497 1"..., 8191) = 245
   8645 nanosleep({0, 1000000}, NULL) = 0
   8645 read(15, 0x2b8af9bd8000, 1024) = -1 EAGAIN (Resource temporarily unavailable)
   8646 open("/proc/10497/stat", O_RDONLY) = 16
   8646 stat("/proc/10497", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
   8646 wait4(10497, 0x7fffb7c2d4dc, WNOHANG, NULL) = 0
   8649 close(16) = 0
  12495 read(15, 0x7fffb7c2d4e0, 1) = -1 EAGAIN (Resource temporarily unavailable)

Anyone have a clue what this means?

Revision history for this message
James Clemence (jvc26) wrote :

+1 here, 32bit Texmaker no issues, 64bit (AMD64 Ubuntu standard texmaker package from the repositories) same exit as above, segmentation fault.
Il

Revision history for this message
Bjorn Hansen (holomorph) wrote :

Also segfaulting on me running amd64, but works on my i386 machine.

Here's the strange bit: if I change the $HOME environment variable to point somewhere else it does not crash. For example

bjorn@berserker:/home/bjorn$ export HOME=/home/bjorn/tmp/
bjorn@berserker:/home/bjorn$ texmaker
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
bjorn@berserker:/home/bjorn$ export HOME=/home/bjorn/
bjorn@berserker:/home/bjorn$ texmaker
Segmentation fault (core dumped)
bjorn@berserker:/home/bjorn$

It runs fine, as far as I can tell in the first case, just producing the Autentication Rejected message, but with the standard home directory it crashes.

Revision history for this message
Joseph Smidt (jsmidt) wrote :

Can somebody test the new texmaker-1.6 in gutsy to see if this bug persists. Texmaker-1.6 fixes this bug in Debian Unstable.

Revision history for this message
Tessa (unit3) wrote :

I just backported this to my Fiesty system, and it does seem to fix this problem. Is it possible to get this into fiesty-backports, since the package in fiesty is broken? Or will this just have to wait until Gutsy?

Revision history for this message
Jørgen Kristoffersen (jorgekri) wrote :

Gutsy AMD64, texmaker-1.6.1ubuntu launches without segfault.

Revision history for this message
Tessa (unit3) wrote :

I confirm that this appears to be fixed in gutsy.

Changed in texmaker:
status: Confirmed → Fix Released
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.