Project

General

Profile

Actions

Emulator Issues #8398

closed

4.0-5908 beyond does not work in Linux Mint

Added by wifomstaff about 9 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

[READ THIS: https://forums.dolphin-emu.org/showthread.php?pid=276132 <<<
Your answers are there!]
[Leave the questions as they are and answer them in the next line]
[Remove lines written inside brackets [], but nothing else]

Game Name? All

Game ID? N/A

What's the problem? Describe what went wrong in few words.
Starting with 4.0-5908 Dolphin is aborted on start for Linux Mint 17.1

What did you expect to happen instead?
Dolphin to start

What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]
1.Be on Linux Mint
2.Start DOlphin 4.0-5908

Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?

4.0-5908

Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?

4.0-5906

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)

Linux Mint 17.1

i5 760

Nvidia GTX 560 Ti

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
[Upload big files to a hosting service and post links here!]

[Do not attach files to this issue. Upload them to another site and
link here. Use imgur.com for images and pastie.org for logs. Monitor the
email address that was used to create this issue.]


Related issues 1 (0 open1 closed)

Is duplicate of Emulator - Emulator Issues #8402: 4.0-5908 beyond does not work in ubuntuFixed

Actions
Actions #1

Updated by yxmline about 9 years ago

GDB debugging with whether error

Actions #2

Updated by skidau about 9 years ago

Which input plugin(s) are you using for the controller? e.g. xinput, xinput2, sdl etc.

Try clearing (making a backup of) the Dolphin Config folder. If that works, please provide a link to a zip file of the non-working Config folder so that I can inspect it.

Is there a backtrace I can view?

Actions #3

Updated by skidau about 9 years ago

Does 4.0-5930 fix this problem?

Actions #4

Updated by yxmline about 9 years ago

not fix
gdb log
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from dolphin-emu...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/games/dolphin-emu
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe1489700 (LWP 5493)]
[New Thread 0x7fffe0c88700 (LWP 5494)]
[New Thread 0x7fffdbfff700 (LWP 5495)]
[Thread 0x7fffdbfff700 (LWP 5495) exited]
[New Thread 0x7fffdbfff700 (LWP 5498)]
[New Thread 0x7fffdb186700 (LWP 5500)]
[New Thread 0x7fffda50a700 (LWP 5505)]

Program received signal SIGSEGV, Segmentation fault.
__strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:209
209 ../sysdeps/x86_64/multiarch/../strcmp.S: No such file or directory

Actions #5

Updated by yxmline about 9 years ago

ps
The problem is the same as
Segmentation fault

Actions #6

Updated by dinextinctus about 9 years ago

looking at 5908 from PR #2230

I wonder why you init and deinit everything in exactly the same order. Wouldn't it be better/safer to deinit everything in reverse order to avoid problems?
(Before the patch, Init would simply return and not deinitialize and reinitialize everything)

Actions #7

Updated by skidau about 9 years ago

dinextenctus, yes, it would be safer to deinit everything in reverse order. The code has been like that in Dolphin for a long time (executed when the Refresh button is pressed in a controller config) and would be unlikely to cause this particular issue.

From the sounds of issue 8402, this crash is caused by a bug in old versions of SDL.

Actions #8

Updated by skidau about 9 years ago

  • Status changed from New to Duplicate
Actions

Also available in: Atom PDF