Zatacka recieves SIGSEGV on launch

Bug #1565485 reported by Nonny Moose
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
zatacka (Debian)
Fix Released
Unknown
zatacka (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When I try to launch Zatacka, I get:

  $ zatacka
  Segmentation fault (core dumped)

Instead of it running successfully.

In gdb I find this:

(gdb) run
Starting program: /usr/games/zatacka
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x76fad2d6 in TTF_SizeUNICODE ()
   from /usr/lib/arm-linux-gnueabihf/libSDL_ttf-2.0.so.0
(gdb) bt
#0 0x76fad2d6 in TTF_SizeUNICODE ()
   from /usr/lib/arm-linux-gnueabihf/libSDL_ttf-2.0.so.0
#1 0x76fae01c in TTF_RenderUNICODE_Blended ()
   from /usr/lib/arm-linux-gnueabihf/libSDL_ttf-2.0.so.0
#2 0x76fae344 in TTF_RenderText_Blended ()
   from /usr/lib/arm-linux-gnueabihf/libSDL_ttf-2.0.so.0
#3 0x00011874 in ?? ()
#4 0x00012142 in ?? ()
#5 0x000121dc in ?? ()
#6 0x00011330 in ?? ()
#7 0x76c88772 in __libc_start_main (main=0x112e1, argc=1, argv=0x7efff194,
    init=<optimized out>, fini=0x17ea1, rtld_fini=0x76fe2ab5 <_dl_fini>,
    stack_end=0x7efff194) at libc-start.c:289
#8 0x000113fc in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

I am using a Raspberry Pi 2 running Ubuntu Mate 15.10:
Description: Ubuntu 15.10
Release: 15.10

The version of Zatacka I am using is
zatacka:
  Installed: 0.1.8-5
  Candidate: 0.1.8-5
  Version table:
 *** 0.1.8-5 0
        500 http://ports.ubuntu.com/ wily/universe armhf Packages
        500 http://ports.ubuntu.com/ubuntu-ports/ wily/universe armhf Packages
        100 /var/lib/dpkg/status

Revision history for this message
Moritz Obermeier (moobsen) wrote :

The problem is that zatacka expects font.ttf somewhere. Unfortunately I could not find out where, so my solution was to compile from source and hard code a font path in fx.h, but if you can find out where it expects font.ttf you can just ln -s any font there and it should work.

Cheers

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in zatacka (Ubuntu):
status: New → Confirmed
Changed in zatacka (Debian):
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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