Bug 1671727 - Trackballs game crashed since Kernel 4.20.4
Summary: Trackballs game crashed since Kernel 4.20.4
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: trackballs
Version: 32
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-01 13:16 UTC by yousifjkadom@yahoo.com
Modified: 2020-07-02 19:52 UTC (History)
2 users (show)

Fixed In Version: trackballs-1.3.1-1.fc31 trackballs-1.3.1-1.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-01 01:35:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description yousifjkadom@yahoo.com 2019-02-01 13:16:21 UTC
Description of problem:
Trackballs constantly crashed at any trail to launch it since I receive kernel 4.20.4
Before kernel 4.20.4 it was worked - see additional information bellow.
Few hrs ago I received new kernel 4.20.5 & error is still existing !

Version-Release number of selected component (if applicable):
1.1.4

How reproducible:
Try to launch the game

Steps to Reproduce:
1.
2.
3.

Actual results:
Game crashed & never launched correctly !

Expected results:
Game should launched okay.

Additional info:
1) terminal trail to launch it give following output:

$ trackballs
setLocale:  -> en_US.utf8
Welcome to Trackballs. 
Using /usr/share/trackballs as gamedata directory.
Warning: Failed to load texture /usr/share/trackballs/images/Cell height
Attempting to open mixer...successfull
Segmentation fault (core dumped)

2) Sine I was on Fedora 24 till now on Fedora 28 X64 bit Cinnamon edition, this game when I was on kernel BEFORE version 4.20.4 , this game only possible to work at lowest resolution of the game from within it's setting ! Any trail to increased it resolution owen setting of game was leading to it's crash !

Comment 1 yousifjkadom@yahoo.com 2019-02-14 12:57:53 UTC
Hi. I'm now on kernel 4.20.7 & issue is still existing !

Comment 2 Ben Cotton 2019-05-02 19:54:25 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-05-28 23:40:19 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 yousifjkadom@yahoo.com 2019-06-01 20:03:39 UTC
Hi. I upgraded successfully, using CLI via tty terminal, from Fedora 28 to 30, but this bug is still existing ! I'm now on kernel 5.1.5-300

I'm suspecting that this bug hardware specific because no one confirm this bug or added a comment since I open it.

Please how can I help you to investigate this issue ?

Comment 5 Paul Dufresne 2020-03-23 23:23:23 UTC
I am affected by this bug on latest daily Fedora Games live 32 (in live mode).

I don't understand why ABRT does not kick in.

If I launch with "gdb trackballs"
run
then an intro image appears and "hang" there.

My system use Intel GPU:
00:02.0 VGA compatible controller: Intel Corporation 8th Gen Core Processor Gaussian Mixture Model

Comment 6 Paul Dufresne 2020-03-24 04:38:26 UTC
bug 1816471 have a nice backtrace info generated by Abrt

Comment 7 Ben Cotton 2020-04-30 20:19:10 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2020-05-26 18:29:46 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 9 yousifjkadom@yahoo.com 2020-05-30 10:11:55 UTC
Issue is still existing after upgrading from Fedora 30 to 32 !

Comment 10 Hans de Goede 2020-06-20 09:41:28 UTC
Thank you for your bug report and sorry for being very slow with responding to it. I'm currently preparing an update to trackballs 1.3.1, which is a much newer version with many bugfixes.

Hopefully that version will also fix this crash. If you are still seeing a crash with the new version, please file a new bug against the new version.

Comment 11 Fedora Update System 2020-06-20 10:55:57 UTC
FEDORA-2020-16ea6e44cc has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-16ea6e44cc

Comment 12 Fedora Update System 2020-06-23 01:03:36 UTC
FEDORA-2020-e8a6da8bb4 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e8a6da8bb4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e8a6da8bb4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2020-06-23 01:53:37 UTC
FEDORA-2020-16ea6e44cc has been pushed to the Fedora 31 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-16ea6e44cc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-16ea6e44cc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2020-07-01 01:35:23 UTC
FEDORA-2020-16ea6e44cc has been pushed to the Fedora 31 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2020-07-01 01:48:51 UTC
FEDORA-2020-e8a6da8bb4 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 yousifjkadom@yahoo.com 2020-07-01 21:52:36 UTC
@Hans de Goede

Hi dear.
Just few minutes I received new version.

It is working okay BUT ONLY FROM TERMINAL !

I investigated the issue & saw in menu editor that the launcher has the command "trackballs-wrapper". So, I tried it in the terminal & gave me that "no such command"! Then I tried just "trackballs" & the game launched okay !

Dear do you forgot to change menu command in new version ? I decided to post this here not in new issue because I'm not sure if it is a bug or not, because I'm already edited the command to switch ON my dedicated video card (I have switch-able video cards system). The command in launcher is:
"env DRI_PRIME=1 trackballs-wrapper"

Is adding "env DRI_PRIME=1" by me interfere with inclusion with new command that set by packager ?

Thank you.

Comment 17 Hans de Goede 2020-07-02 19:52:44 UTC
(In reply to yousifjkadom from comment #16)
> @Hans de Goede
> 
> Hi dear.
> Just few minutes I received new version.
> 
> It is working okay BUT ONLY FROM TERMINAL !
> 
> I investigated the issue & saw in menu editor that the launcher has the
> command "trackballs-wrapper". So, I tried it in the terminal & gave me that
> "no such command"! Then I tried just "trackballs" & the game launched okay !
> 
> Dear do you forgot to change menu command in new version ? I decided to post
> this here not in new issue because I'm not sure if it is a bug or not,
> because I'm already edited the command to switch ON my dedicated video card
> (I have switch-able video cards system). The command in launcher is:
> "env DRI_PRIME=1 trackballs-wrapper"
> 
> Is adding "env DRI_PRIME=1" by me interfere with inclusion with new command
> that set by packager ?

Yes I believe that you using your own modified launcher is the problem here, the .desktop file in the new version of trackballs looks like this:

[hans@x1 ~]$ cat /usr/share/applications/trackballs.desktop 
[Desktop Entry]
Name=Trackballs
GenericName=Marble Madnees type game
Comment=Guide a marble through a maze and avoid obstacles
Comment[de]=Führe eine Murmel durch ein Labyrinth und weiche Hindernissen aus
Exec=trackballs
Icon=trackballs
Type=Application
Categories=Game;ArcadeGame;
Keywords=marble;maze;obstacle;


As you can see "Exec" is set to just "trackballs". If you changed your modified launcher / .desktop file to be just "env DRI_PRIME=1 trackballs" then your problem should be fixed.


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