Anyone using Debian?

jordi13 · 2014-12-11 10:42:35

Hello, I know it's a long shot but after the last update I can't launch the game anymore!
I am using Linux 3.2.0-4-amd64 (debian)
KDE 4.8.4
I have tried everything, any help would be so appreciated!
Thanks

AMWhy · 2014-12-11 17:41:18

The best person to ask would be Jason himself. Send him an email and see what he can do.

jordi13 · 2014-12-12 01:30:41

Well, I didn't want to bother him when I have no idea of why it isn't working, as far as I know I haven't done anything but update!
At least now I have an error message:
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
I'm gonna get it running in a virtual machine for now, hope the issue resolves itself with the next update!
I can guess I have $0 and a dead wife by now lol

AMWhy · 2014-12-12 05:16:14

That could be a while. Jason has moved onto his next game and I don't foresee any updates with TCD for a long time, if at all! He's responsive to emails though, so if you can't get it to work...

voxel · 2014-12-13 18:33:36

I doubt very much that that warning message has anything to do with the problem. I get it for other programs. TCD isn't even a Qt application.

Is that the only thing printed to the console when you try to run it? Last update of what, TCD or your system? Either way, a shared library problem sounds far more likely to me. What does "ldd CastleDoctorineApp" print?

Last edited by voxel (2014-12-13 18:35:16)

jordi13 · 2014-12-14 00:09:45

Thanks for trying to help! The last update of debian wheezy Ishould have said.
ldd CastleDoctrineApp prints this:

linux-gate.so.1 => (0xf778a000)
libGL.so.1 => /usr/lib/i386-linux-gnu/libGL.so.1 (0xf7651000)
libGLU.so.1 => /usr/lib/i386-linux-gnu/libGLU.so.1 (0xf75dc000)
libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf74a3000)
libSDL-1.2.so.0 => /usr/lib/i386-linux-gnu/libSDL-1.2.so.0 (0xf7405000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf73ec000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf7300000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf72da000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf72bc000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf716c000)
libnvidia-tls.so.340.46 => /usr/lib/i386-linux-gnu/tls/libnvidia-tls.so.340.46 (0xf7167000)
libnvidia-glcore.so.340.46 => /usr/lib/i386-linux-gnu/libnvidia-glcore.so.340.46 (0xf4bd5000)
libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xf4bc3000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf4bbe000)
libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf4b9b000)
libasound.so.2 => /usr/lib/i386-linux-gnu/libasound.so.2 (0xf4aa3000)
libpulse-simple.so.0 => /usr/lib/i386-linux-gnu/libpulse-simple.so.0 (0xf4a9e000)
libpulse.so.0 => /usr/lib/i386-linux-gnu/libpulse.so.0 (0xf4a4e000)
libdirectfb-1.2.so.9 => /usr/lib/i386-linux-gnu/libdirectfb-1.2.so.9 (0xf49c7000)
libfusion-1.2.so.9 => /usr/lib/i386-linux-gnu/libfusion-1.2.so.9 (0xf49bd000)
libdirect-1.2.so.9 => /usr/lib/i386-linux-gnu/libdirect-1.2.so.9 (0xf49a6000)
libcaca.so.0 => /usr/lib/i386-linux-gnu/libcaca.so.0 (0xf48d9000)
libts-0.0.so.0 => /usr/lib/i386-linux-gnu/libts-0.0.so.0 (0xf48d6000)
/lib/ld-linux.so.2 (0xf778b000)
libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf48d2000)
libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf48cc000)
librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf48c3000)
libpulsecommon-2.0.so => /usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-2.0.so (0xf485b000)
libcap.so.2 => /lib/i386-linux-gnu/libcap.so.2 (0xf4856000)
libjson.so.0 => /lib/i386-linux-gnu/libjson.so.0 (0xf484b000)
libdbus-1.so.3 => /lib/i386-linux-gnu/libdbus-1.so.3 (0xf47ff000)
libslang.so.2 => /lib/i386-linux-gnu/libslang.so.2 (0xf46cc000)
libncursesw.so.5 => /lib/i386-linux-gnu/libncursesw.so.5 (0xf4699000)
libtinfo.so.5 => /lib/i386-linux-gnu/libtinfo.so.5 (0xf4679000)
libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf465f000)
libX11-xcb.so.1 => /usr/lib/i386-linux-gnu/libX11-xcb.so.1 (0xf465d000)
libICE.so.6 => /usr/lib/i386-linux-gnu/libICE.so.6 (0xf4644000)
libSM.so.6 => /usr/lib/i386-linux-gnu/libSM.so.6 (0xf463c000)
libXtst.so.6 => /usr/lib/i386-linux-gnu/libXtst.so.6 (0xf4636000)
libwrap.so.0 => /lib/i386-linux-gnu/libwrap.so.0 (0xf462b000)
libsndfile.so.1 => /usr/lib/i386-linux-gnu/libsndfile.so.1 (0xf45b7000)
libasyncns.so.0 => /usr/lib/i386-linux-gnu/libasyncns.so.0 (0xf45b1000)
libattr.so.1 => /lib/i386-linux-gnu/libattr.so.1 (0xf45ab000)
libuuid.so.1 => /lib/i386-linux-gnu/libuuid.so.1 (0xf45a5000)
libXi.so.6 => /usr/lib/i386-linux-gnu/libXi.so.6 (0xf4595000)
libnsl.so.1 => /lib/i386-linux-gnu/libnsl.so.1 (0xf457e000)
libFLAC.so.8 => /usr/lib/i386-linux-gnu/libFLAC.so.8 (0xf452b000)
libvorbisenc.so.2 => /usr/lib/i386-linux-gnu/libvorbisenc.so.2 (0xf43b3000)
libvorbis.so.0 => /usr/lib/i386-linux-gnu/libvorbis.so.0 (0xf4387000)
libogg.so.0 => /usr/lib/i386-linux-gnu/libogg.so.0 (0xf437f000)
libresolv.so.2 => /lib/i386-linux-gnu/libresolv.so.2 (0xf436a000)

Have a good day!

voxel · 2014-12-17 04:47:20

I was hoping that ldd would show that something was wrong, but no such deal.

Does it just cleanly exit when you run it? What if you run it under gdb? Run "gdb CastleDoctorineApp" and then enter "r" at the prompt to start it and see what happens.

jordi13 · 2014-12-17 09:51:47

OK thanks for helping! This is what happens:

Starting program: /media/docs/Downloads/CastleDoctrine_v35/CastleDoctrineApp
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0xf0957b70 (LWP 6486)]
[Thread 0xf0957b70 (LWP 6486) exited]
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 137 (NV-GLX)
Minor opcode of failed request: 4 ()
Resource id in failed request: 0x420000f
Serial number of failed request: 35
Current serial number in output stream: 35
[Inferior 1 (process 6431) exited with code 01]
(gdb)

Still using a virtual machine with crunchbang for now but I'd love to get to the bottom of this as it also seems to affect Steam and Chromium
Have a good day :-)

PS: When I try to run it nothing happens at all...

Last edited by jordi13 (2014-12-17 10:25:37)

jordi13 · 2014-12-17 10:13:48

OK maybe it is because after the kernel upgrade the proprietary nvidia driver is not working properly?
Sorry I am still a novice with Linux, I am gonna try running smxi or switching to the free one, I don't even know if it would be better :-(

jordi13 · 2014-12-17 10:16:31

Yes! It works! Thank you! You are a genius!
I did a short course about Linux but it was mostly based on Ubuntu, and it covered just the basics, what is the best way to learn more?
I find some of the man pages a bit confusing, I keep meaning to learn more, but now it works, thanks again, I am happy.
Of course $0 and a dead family... start again :-)

eppfel · 2014-12-17 17:10:44

jordi13 wrote:

Yes! It works!

Would you mind, posting your solution? I had troubles starting on Ubuntu.

Last edited by eppfel (2014-12-17 17:11:05)

jordi13 · 2014-12-17 21:35:27

All I did was re-install the driver for my nvidia graphics card, on Ubuntu I think you should be able to do it easily like this:

If you are using an older version of Ubuntu, or if you aren't notified about additional drivers, you can launch the installation yourself.

Go to System -> Administration -> Additional Drivers
Once the drivers are downloaded and installed, reboot your computer.

Note: In older version of Ubuntu, Additional Drivers are called Hardware Drivers.

Note: In older version of Ubuntu, newer graphic adapters may not be supported with the repositories provided driver.

Note: In newer version of Ubuntu, older graphic adapters may not be supported with the repositories provided driver.

The gdb command should work I think as it is GNU so maybe that will help you find out. Make sure the CastleDoctrineApp file is executable, you can check doing right click, properties, permissions, and then tick the "is executable" box.
Good luck!

voxel · 2014-12-17 23:53:03

Ah, great.

I don't know what would be a good way to learn basics. I just read about topics as I need to. Generally the trick to solving any problem to first obtain an error message, and then google that. Despite years of dealing with them, I still know nothing about 90% of the problems I encounter. A lot of programs will print error messages if run from a terminal which are completely invisible otherwise, so that's always the first thing to try. Also, sometimes when an application crashes it won't actually print a message like "Segmentation Fault" but will appear to simply exit, and you'd need to run under gdb to discover that it's crashing. It's often possible to do some more advanced poking around with gdb to get clues about why something is crashing (eg, somewhere in a function that looks like it's doing window initialisation). There are also system message logs but those will generally only contain messages useful for debugging hardware, filesystems, etc, not normal applications. (In this case though there probably would have been messages about your graphics driver)

Last edited by voxel (2014-12-17 23:55:06)

The Castle Doctrine Forums

#1 2014-12-11 10:42:35

Anyone using Debian?

#2 2014-12-11 17:41:18

Re: Anyone using Debian?

#3 2014-12-12 01:30:41

Re: Anyone using Debian?

#4 2014-12-12 05:16:14

Re: Anyone using Debian?

#5 2014-12-13 18:33:36

Re: Anyone using Debian?

#6 2014-12-14 00:09:45

Re: Anyone using Debian?

#7 2014-12-17 04:47:20

Re: Anyone using Debian?

#8 2014-12-17 09:51:47

Re: Anyone using Debian?

#9 2014-12-17 10:13:48

Re: Anyone using Debian?

#10 2014-12-17 10:16:31

Re: Anyone using Debian?

#11 2014-12-17 17:10:44

Re: Anyone using Debian?

#12 2014-12-17 21:35:27

Re: Anyone using Debian?

#13 2014-12-17 23:53:03

Re: Anyone using Debian?

Board footer