Bug 1630163 - Game crashes on initial start
Summary: Game crashes on initial start
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lincity-ng
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-18 06:15 UTC by Matthias Runge
Modified: 2018-10-30 17:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 11:38:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
coredump (14.92 MB, application/x-gzip)
2018-09-18 06:15 UTC, Matthias Runge
no flags Details

Description Matthias Runge 2018-09-18 06:15:23 UTC
Created attachment 1484249 [details]
coredump

Description of problem:

on initial start, it was never started before.
> lincity-ng 
Starting lincity-ng (version 2.9.beta)...
Unexpected exception: Failed creating configuration directory '/home/mrunge/.lincity-ng': unsupported

(the game created a file, not a dir)

Fixing that, creating a dir.

Then the game crashes

 mrunge  ~  lincity-ng 
Starting lincity-ng (version 2.9.beta)...
[/home/mrunge/.lincity-ng] is in the search path.
[/usr/share/lincity-ng] is in the search path.
[/home/mrunge/.lincity-ng] is the write directory.
Language is "en_IE".
 fast = 10

OpenGL Mode 1024x768
File found: 'music/default/default.xml'. Loading song data...
Found song: 'Robert van Herk - City Blues'
Found song: 'Robert van Herk - Architectural Contemplations'
Found song: 'Pronobozo - Lincity'
world id: 122815719
carving river ...Floating point exception (core dumped)



Version-Release number of selected component (if applicable):
lincity-ng-2.9-0.14.20160605git7f266b1.fc28



coredumpctl dump lincity-ng --output core
           PID: 4713 (lincity-ng)
           UID: 1000 (mrunge)
           GID: 1000 (mrunge)
        Signal: 8 (FPE)
     Timestamp: Tue 2018-09-18 08:05:09 CEST (7min ago)
  Command Line: lincity-ng
    Executable: /usr/bin/lincity-ng
 Control Group: /user.slice/user-1000.slice/user/gnome-terminal-server.service
          Unit: user
     User Unit: gnome-terminal-server.service
         Slice: user-1000.slice
     Owner UID: 1000 (mrunge)
       Boot ID: bb5148c59b834a68a7e9a3b0fc307870
    Machine ID: 99b6051475924ec7a267fcef21f5cfd3
      Hostname: hilbert.berg.ol
       Storage: /var/lib/systemd/coredump/core.lincity-ng.1000.bb5148c59b834a68a7e9a3b0fc307870.4713.1537250709000000.lz4
       Message: Process 4713 (lincity-ng) of user 1000 dumped core.
                
                Stack trace of thread 4713:
                #0  0x000055cb0f1202d9 _Z15create_new_cityPiS_P13_CitySettingsii (lincity-ng)
                #1  0x000055cb0f0ce607 _ZN8MainMenu25newGameStartButtonClickedEP6Button (lincity-ng)
                #2  0x000055cb0f10b51d _ZN6Button5eventERK5Event (lincity-ng)
                #3  0x000055cb0f107ade _ZN9Component10eventChildER5ChildRK5Eventb (lincity-ng)
                #4  0x000055cb0f107bbe _ZN9Component5eventERK5Event (lincity-ng)
                #5  0x000055cb0f107ade _ZN9Component10eventChildER5ChildRK5Eventb (lincity-ng)
                #6  0x000055cb0f107bbe _ZN9Component5eventERK5Event (lincity-ng)
                #7  0x000055cb0f107ade _ZN9Component10eventChildER5ChildRK5Eventb (lincity-ng)
                #8  0x000055cb0f107bbe _ZN9Component5eventERK5Event (lincity-ng)
                #9  0x000055cb0f10259e _ZN7Desktop5eventERK5Event (lincity-ng)
                #10 0x000055cb0f0d2775 _ZN8MainMenu3runEv (lincity-ng)
                #11 0x000055cb0f0acf7d _Z8mainLoopv (lincity-ng)
                #12 0x000055cb0f09a351 main (lincity-ng)
                #13 0x00007fa28ad1711b __libc_start_main (libc.so.6)
                #14 0x000055cb0f0a4b9a _start (lincity-ng)

Comment 1 Tom "spot" Callaway 2018-10-05 19:10:53 UTC
The first part is a physfs bug, which I am applying the fix for now.

The second part... I can't reproduce. :/

Comment 2 Fedora Update System 2018-10-05 19:17:08 UTC
physfs-3.0.1-4.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-08cf700cc5

Comment 3 Fedora Update System 2018-10-05 19:17:14 UTC
physfs-3.0.1-4.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-77edb18d2f

Comment 4 Fedora Update System 2018-10-07 23:36:20 UTC
physfs-3.0.1-4.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-08cf700cc5

Comment 5 Fedora Update System 2018-10-08 00:08:56 UTC
physfs-3.0.1-4.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-77edb18d2f

Comment 6 Fedora Update System 2018-10-16 11:38:32 UTC
physfs-3.0.1-4.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2018-10-30 17:20:54 UTC
physfs-3.0.1-4.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.