Steam for Linux > Limited Beta > Detalles del tema
mblackwell 3 de Dic, 2012 a las 13:49
Issue Report: TF2 Segfault from Symlink
I actually picked up on this from other threads (and had the same issue myself), however I noticed there was no actual report thread.

I can confirm that using a symlinked SteamApps folder causes TF2 to crash during the intro video. Moving files back to ~/Steam allowed the game to run normally.

Processor Information:
Vendor: GenuineIntel
Speed: 3085 Mhz
4 logical processors
4 physical processors
HyperThreading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Unsupported

Network Information:
Network Speed:

Operating System Version:
Ubuntu 12.10 (64 bit)
Kernel Name: Linux
Kernel Version: 3.5.0-19-generic
X Server vendor: The X.Org Foundation
X Server release: 11300000

Video Card:
Driver: NVIDIA Corporation GeForce GTX 560 Ti/PCIe/SSE2

Driver Version: 4.3.0 NVIDIA 310.14
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x10de
DeviceID: 0x1200
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1200
Desktop Resolution: 1920 x 1200
Primary Display Size: 20.39" x 12.76" (24.02" diag)
51.8cm x 32.4cm (61.0cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 1023 MB
Supported MSAA Modes: 2x 4x 8x 16x

Sound card:
Audio device: Nvidia GPU 16 HDMI/DP

Memory:
RAM: 3953 Mb

Miscellaneous:
UI Language: English
LANG: C
Microphone: Not set
Total Hard Disk Space Available: 709765 Mb
Largest Free Hard Disk Block: 85422 Mb

Installed software:

Recent Failure Reports:
Mon Dec 3 20:04:38 2012 GMT: file ''/tmp/dumps/crash_20121203140436_1.dmp'', upload yes: ''CrashID=bp-4bb90689-6e85-4aa5-a048-c3f2d2121203
''
Mon Dec 3 20:07:20 2012 GMT: file ''/tmp/dumps/crash_20121203140718_1.dmp'', upload yes: ''CrashID=bp-1bd5c43a-9c63-4566-97bd-e11b42121203
''
Mon Dec 3 20:17:50 2012 GMT: file ''/tmp/dumps/crash_20121203141748_1.dmp'', upload yes: ''CrashID=bp-b0a97f24-027f-46f9-aea5-744612121203
''
Mon Dec 3 20:19:56 2012 GMT: file ''/tmp/dumps/crash_20121203141955_1.dmp'', upload yes: ''CrashID=bp-234b0841-1ecf-43b1-aa51-b341a2121203
''

A separate issue is that the above information is incorrect. My system is actually using my SB Live audio card, not the HDMI audio. Just noting that for those who read the sysinfo.
Última edición por mblackwell; 3 de Dic, 2012 a las 13:50
Mostrando 1-7 de 7 comentarios
< >
Frank 4 de Dic, 2012 a las 14:09 
Thanks, we've added this to the bug database.
mikesart 17 de Dic, 2012 a las 18:05 
Can you give me more information on how you set this up? You moved your SteamApps folder, and then symlinked from there to wherever you moved it? If this still happens, do you have a CrashID as well? Thanks.
mblackwell 17 de Dic, 2012 a las 18:12 
Correct. Moved SteamApps and then Symlinked back. The CrashIDs are in the info from the first post. If there was progress on this I can retest it at a later date.
mikesart 19 de Dic, 2012 a las 13:22 
I've fixed the crash in the next release. It's failing to find some resources for the video playback. It should now display an error dialog and not crash. I've added a bug entry about running from symlinked directories - that's going to be harder to get working though. Thanks for the help.
mblackwell 19 de Dic, 2012 a las 16:12 
It probably depends largely on how the application steps back and forth through the directories. I've run into situations where a new terminal or certain commands will cause you to end up with the actual path rather than the Symlinked path, and I've seen this cause issues with SVN. Both are valid as far as the overall system is concerned however.
mikesart 19 de Dic, 2012 a las 16:22 
I think the problem is we are getting a path with ".../SteamApps.symlink/..." and Steam thinks we started in ".../SteamApps/...". So when we then ask Steam for a file with ".../SteamApps.symlink/..." it's failing. Steam will have an official way to do this at some point, so I'm not sure it makes sense for me to spend a bunch of time trying to fix this...
mblackwell 19 de Dic, 2012 a las 20:27 
Perhaps, but it is fairly common in the Linux world to have files all over the place (for various reasons) and linked back in different ways so it might be worth fixing just to account for the odd arrangement of people's /home filesystem and avoid user frustration (or surprise).
Mostrando 1-7 de 7 comentarios
< >
Por página: 15 30 50