Re: [Bino-list] Subtitles - Thank-You!!

[Jack Metal]

Thanks!  Running in a terminal with the debug option gave the following when I press play in bino and bino crashes (also the same error in .xsession.errors when running via desktop):

bino: [err] Caught signal 11 (SIGSEGV). Aborting.
bino: [err] Report bugs to <address@hidden>.

I tested a few different videos (with and without subtitles) and also tested the pre-built binary from the repository, but get the same issue and error.  

The laptops are loaded pretty much the same as the desktops that work (Ubuntu, apps, etc.).  The one difference that I've found so far is the video cards, the desktops are using nVidia and the laptops are using Intel (driver = i915).

I also decided to give it a test in a Windows Virtual Machine to see if it might be something OS related, but it crashed there also (it actually crashed and closed the entire virtual machine and not just bino).  So it must be something to do with the video card or something else it definitely doesn't like on these laptops.  LOL 

One of the laptops is an HP w/Ubuntu and the other is an Acer w/Ubuntu, but both have Intel video.

On Mon, Apr 11, 2011 at 3:17 PM, Martin Lambers <address@hidden> wrote:

> Martin,  quick question on logging in bino (Ubuntu): Where should I be
> looking for any logs that bino uses?

When starting Bino from the Desktop environment, its log messages are
typically redirected to .xsession-errors in your home directory, along
with the messages from all other Desktop programs.

You can start Bino from a terminal to see its log messages directly. You
can also set the amount of messages you want to see with the -l option, e.g.
$ bino -l debug

Martin