Gentoo AMD 64 Steamcontroller Crashes Steam #4244
Comments
|
OUTPUT BELOW: ./steam (steam:25887): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:25887): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:25887): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:25887): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:25887): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:25887): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:25887): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:25887): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:25887): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:25887): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:25887): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", |
|
DMESG OUTPUT(relevant) [250141.181451] CPU3 is up |
|
about PC in question: uname -a |
|
|
|
OK, are there any actions required from me? I mean, Steam runtime is enabled, so its not system's problem? Steam needs to update the library? |
|
Sure, some options are deleting the offending library from the steam runtime (comes back every time a steam update changes the runtime) or preload the system version of the library. |
|
I removed offending file still getting this: ** (steam:28358): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files (steam:28358): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:28358): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:28358): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:28358): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:28358): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:28358): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:28358): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:28358): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:28358): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:28358): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", (steam:28358): Gtk-WARNING **: Unable to locate theme engine in module_path: "xfce", |
|
I'm running into this same bug, can't do LD_PRELOAD
also removed the file (and I have crashlogs uploaded in my dev space http://dev.gentoo.org/~prometheanfire/crash-logs/steam-controller-bp/
log snipet from the badness, reinstalled steam to get it 'vanilla'. I kinda wonder if it has to do with zfs and the o_direct stuff from #2515 @drjoms are you using zfs by chance (btrfs might have this issue too, not sure) |
|
@drjoms also, are you using the steam beta client? @gdrewb-valve I've tested and I think the fix for #2515 might have introduced this bug, I installed on a test ext4 partition (same workaround I used before #2515 was fixed) and the controller setup work in big picture mode without crashing steam. It is also possible that the firmware got updated before I switched to the beta though. |
|
I suspect that's what happened, (update before the switch to the beta client). I just switched back to my normal install and the controller setup. I moved it back from the pc I was testing on to another one that didn't ever change to the normal client and it's working there as well. so, maybe switching back to the normal client is a workaround for now? |
|
The fix for #2515 was extremely simple (basically don't use O_DIRECT) so it's hard to see how it would have directly caused any problems. I would guess this is more a Steam runtime compat thing, but that's for the Steam team to figure out. |
|
ya, first hunch was off I think. maybe when this is fixed the steam controller will actually work in games (have the udev stuff working and works in big picture just fine...). |
|
@prometheanfire |
|
@gdrewb-valve the reason I say the o_direct thing is because it might not have been fixed in all places. @drjoms what fs do you use? |
|
ext4 on separate(/home/) non encrypted non raid partition.(as simple as it gets) |
|
There was only one use of O_DIRECT in Valve code. It's possible there's something lurking somewhere else but again that's for the Steam team to discover. |
|
ah, kk |
|
hello, any news anybody? new beta doesn't help. |
|
user fault... |
|
I'm still seeing this problem, where when I connect my steam controller in Big Picture Mode it prompts me to migrate the settings profile (I hadn't used my controller in some time) then steam crashes while migrating. Otherwise steam and the games I've tried playing through it work fine. I'm on a 64-bit Gentoo with STEAM_RUNTIME disabled and ZFS filesystems (steam is running off an SSD with that ZFS filesystem having a 16K recordsize and lz4 compression enabled, no encryption though). The relevant bit of output from steam, from when I turned on the controller until it crashed: I suspect the assertion about chunk size not aligning to disk sector size is checking for the wrong thing or in some other way is not valid, and is the source of the problem with the controller crashing steam under Linux for some folks. |
|
I just filed issues #4458 since while prometheanfire saw the same assertion I did, the output in the original bug report from drjoms doesn't have the assertion about the default chunk size. |
Steam Controller moment connected over USB or moment wireless part of controller is connected to USB - crashes Steam.
Will add as new message additional info.
The text was updated successfully, but these errors were encountered: