Hi Cliff,

Based on the Stacktrace the crash itself seems to be in Pipelight code,
but its not immediately clear if this is a problem with libwebkitgtk /
Osmo or Pipelight itself. It would probably be helpful to take a look at
some more detailed debug output.

Can you probably compile Pipelight yourself with --debug enabled and attach a 
new log from the terminal output?
I assume that you already have some experience with compiling software, if not 
we can also provide some more detailed instructions.

I would suggest to checkout Pipelight from git:
https://bitbucket.org/mmueller2012/pipelight/overview

Afterwards you have to modify debian/rules and add " --debug" at the end of 
line 7 and 9:
https://bitbucket.org/mmueller2012/pipelight/src/5d5e122ee51d11e1d1ccf9a37c50fdc0e7b94704/debian/rules?at=master#cl-7

The required build dependencies are:

Build-Depends: debhelper (>= 8), libc6-dev(>= 2.11.1), libx11-dev (>= 2:1.3),
        mingw-w64, g++-mingw-w64, make (>= 3.81), g++ (>= 4:4.4), sed (>= 
4.2.1), po-debconf

Then just build the package (for example with "debuild -uc -us -b") and
install it.

Please try to reproduce the problem, and then attach a new log
containing all stderr & stdout output, for example with:

osmo &> pipelight.log

It should contain a lot more detailed output including all function
calls which are relayed by Pipelight. Please attach the log to this bug
report.

Regards,
Sebastian

** Also affects: pipelight
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297872

Title:
  osmo crashed with SIGSEGV in std::basic_string<char,
  std::char_traits<char>, std::allocator<char> >::~basic_string()

To manage notifications about this bug go to:
https://bugs.launchpad.net/pipelight/+bug/1297872/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to