Forums » Linux
VO doesn't start on SolydK (Debian Testing)
Hello,
My distro just updated a few days ago and I have this odd problem.
The game Doesn't start OR it starts after many MANY clicks (some times).
The weirdest thing is that it does not show anything, not even when I run it from console, it just does nothing, it shows no error, no exception, nothing.
I would be very grateful to anyone who might give me a helpful tip, thank you :-)
(I am using the non-free drivers from the repositories of Debian, but it didn't work with the proprietary ones from the site of AMD/ATI either)
CPU:
AMD Phenom(tm) II X4 965 Processor
GPU:
Advanced Micro Devices [AMD] nee ATI Barts PRO [Radeon HD 6800 Series]
Audio:
ALSA Timer Device
Audio:
Webcam C170 (OSS Device)
Audio:
HD-Audio Generic (OSS Device)
Audio:
HD-Audio Generic(HDA Intel ALSA hardware specific Device)
Audio:
HDA ATI SB
Audio:
HDA ATI SB (ALC892 Digital)
Audio:
HDA ATI SB (ALC892 Analog)
Audio:
ALSA Sequencer Device
Audio:
Webcam C170 (USB Audio)
Audio:
HD-Audio Generic
Audio:
Barts HDMI Audio [Radeon HD 6800 Series]
Audio:
HDA ATI SB(HDA Intel ALSA hardware specific Device)
Audio:
Webcam C170
Audio:
HD-Audio Generic (HDMI 0)
Network:
Loopback device Interface
Network:
RTL8111/8168B PCI Express Gigabit Ethernet controller
My distro just updated a few days ago and I have this odd problem.
The game Doesn't start OR it starts after many MANY clicks (some times).
The weirdest thing is that it does not show anything, not even when I run it from console, it just does nothing, it shows no error, no exception, nothing.
I would be very grateful to anyone who might give me a helpful tip, thank you :-)
(I am using the non-free drivers from the repositories of Debian, but it didn't work with the proprietary ones from the site of AMD/ATI either)
CPU:
AMD Phenom(tm) II X4 965 Processor
GPU:
Advanced Micro Devices [AMD] nee ATI Barts PRO [Radeon HD 6800 Series]
Audio:
ALSA Timer Device
Audio:
Webcam C170 (OSS Device)
Audio:
HD-Audio Generic (OSS Device)
Audio:
HD-Audio Generic(HDA Intel ALSA hardware specific Device)
Audio:
HDA ATI SB
Audio:
HDA ATI SB (ALC892 Digital)
Audio:
HDA ATI SB (ALC892 Analog)
Audio:
ALSA Sequencer Device
Audio:
Webcam C170 (USB Audio)
Audio:
HD-Audio Generic
Audio:
Barts HDMI Audio [Radeon HD 6800 Series]
Audio:
HDA ATI SB(HDA Intel ALSA hardware specific Device)
Audio:
Webcam C170
Audio:
HD-Audio Generic (HDMI 0)
Network:
Loopback device Interface
Network:
RTL8111/8168B PCI Express Gigabit Ethernet controller
It's called "testing" for a reason ya know.
Yes, because it has packages that are more recent than the stable, therefor it's "testing", so?
Many packages are still a bit old though!
And there are distros (even popular) that have nothing extra in their name and have even more recent packages, what does that make them?
Many packages are still a bit old though!
And there are distros (even popular) that have nothing extra in their name and have even more recent packages, what does that make them?
Because I used to run debian testing and it would break shit on occasion at random. It's just part of the chance you take when running it.
Try starting the game from a terminal and see what happens. It doesn't matter how many times you click it if you never see the error message. :)
Also check ~/.vendetta/errors.log for any relevant info.
Also check ~/.vendetta/errors.log for any relevant info.
I 've tried to run it from a terminal and as I said it does noting, it looks like it stucks reading something but it doesn't show what it processes (there is the no-error message I said).
Anyway, thank you both for your consideration.. :-)
vskye: are you using the stable now (I was thinking of using a more stable one, like Debian stable, but there are some packages I want to have their later releases)?
Anyway, thank you both for your consideration.. :-)
vskye: are you using the stable now (I was thinking of using a more stable one, like Debian stable, but there are some packages I want to have their later releases)?
I was running 7.0 stable for about 2 weeks, but I hated it, since it wasn't so stable with VO. So back to Mint 15 for the moment. (64-bit version).
Just a question, but you did install VO via your user account vs root yes?
http://www.vendetta-online.com/x/download?platform=linux&accept=y
"To install Vendetta, type "sh ./vendetta-linux-x-installer.sh". You do not need to be root; install it under your usual account."
Just a question, but you did install VO via your user account vs root yes?
http://www.vendetta-online.com/x/download?platform=linux&accept=y
"To install Vendetta, type "sh ./vendetta-linux-x-installer.sh". You do not need to be root; install it under your usual account."
Linux Mint 15 is based on Ubuntu, so the packages are more recent than stable or even testing, right??
Also, yes, I use my user account, I know, that .sh are not installed as root, but thanks for you suggestion anyway
abortretryfail: I cannot find the errors.log
And it is still driving me crazy the no-error message even via console :-@
Anyway, thank you guys I suppose that the new testing (after the new stable release) needs some more testing first, maybe in a few releases :-o
Also, yes, I use my user account, I know, that .sh are not installed as root, but thanks for you suggestion anyway
abortretryfail: I cannot find the errors.log
And it is still driving me crazy the no-error message even via console :-@
Anyway, thank you guys I suppose that the new testing (after the new stable release) needs some more testing first, maybe in a few releases :-o
~/.vendetta/ is a hidden directory, due to the dot before the vendetta. How you get to it depends on your file manager. I don't use mainstream file managers so I can't help you there, but there should be some kind of "show hidden files" or "show all" toolbar button or right-click option or menu option or something.
Alternately, you could just use the commandline: less ~/.vendetta/errors.log
Note that it isn't only about how new a package is. It's also about how a selection of packages interacts with eachother, how they were compiled, and how the overall system is configured. You can have two distros using the exact same package versions, but one is broken and the other works.
Alternately, you could just use the commandline: less ~/.vendetta/errors.log
Note that it isn't only about how new a package is. It's also about how a selection of packages interacts with eachother, how they were compiled, and how the overall system is configured. You can have two distros using the exact same package versions, but one is broken and the other works.
I meant that there is no error.log inside the .vendetta folder
I thought it is due to a newer version of a package because I had no problem with the older version of my distro.
thank you all for you help and for all the explanations (even if it was unnecessary sometimes :-) )
I thought it is due to a newer version of a package because I had no problem with the older version of my distro.
thank you all for you help and for all the explanations (even if it was unnecessary sometimes :-) )
No errors.log? Note the 's'
It could be due to a newer package, but I (and a few other users) run the game on ArchLinux which ships the latest and greatest when it comes out, so it's more likely due to a broken package than one that's too new.
Try running the game in gdb or another debugger and see if it'll give you some more info.
It could be due to a newer package, but I (and a few other users) run the game on ArchLinux which ships the latest and greatest when it comes out, so it's more likely due to a broken package than one that's too new.
Try running the game in gdb or another debugger and see if it'll give you some more info.
Just a shot in the dark here, but are you using PulseAudio?
I think that yes, I use PulseAudio..
I tried it with gdb and that is what shows up at the console:
(gdb) exec-file /winLinData/Games/MMO/Space/Vendetta/lin/Vendetta-Online/vendetta
(gdb) run /winLinData/Games/MMO/Space/Vendetta/lin/Vendetta-Online/vendetta
Starting program: /winLinData/Games/MMO/Space/Vendetta/lin/Vendetta-Online/vendetta /winLinData/Games/MMO/Space/Vendetta/lin/Vendetta-Online/vendetta
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
process 6404 is executing new program: /home/orestes/.vendetta/update.rlb
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff113a700 (LWP 6408)]
^C
Program received signal SIGINT, Interrupt.
0x00007ffff6a071bd in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)
I 'll try again and try mto find my way with the libraries, thank you very much, at least now I can see some errors :-)
I tried it with gdb and that is what shows up at the console:
(gdb) exec-file /winLinData/Games/MMO/Space/Vendetta/lin/Vendetta-Online/vendetta
(gdb) run /winLinData/Games/MMO/Space/Vendetta/lin/Vendetta-Online/vendetta
Starting program: /winLinData/Games/MMO/Space/Vendetta/lin/Vendetta-Online/vendetta /winLinData/Games/MMO/Space/Vendetta/lin/Vendetta-Online/vendetta
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
process 6404 is executing new program: /home/orestes/.vendetta/update.rlb
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff113a700 (LWP 6408)]
^C
Program received signal SIGINT, Interrupt.
0x00007ffff6a071bd in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)
I 'll try again and try mto find my way with the libraries, thank you very much, at least now I can see some errors :-)