Skip to main content

Topic: Otter crashes and burns in Ubuntu Linux (Read 173 times)

  • gracious1
  • [*]
Otter crashes and burns in Ubuntu Linux
I installed Otter Browser in Ubuntu 14.04. At first, it seemed to work fine, but then it started freezing and hanging, and then it lead to a segmentation fault and coredump.

Please help! Right now it seems my only choice is to purge Otter browser. I had to use another browser to even post this thread! Maybe the problem is the package I used, and some other form of installation would work.



Here is some information about the last crash:

otter-browser crashed with SISEGV in QWebHItTestResultPrivate::QWebHitTestResultPrivate()

Segfault happened at: 0x7fdb06521d42: mov (%rdi) %rax
reason: reading NULL VMA

source package: otter-browser
  Installed: 0.9.09.01-1~trusty~ppa1
  Candidate: 0.9.09.01-1~trusty~ppa1
  Version table:
 *** 0.9.09.01-1~trusty~ppa1 0
        500 http://ppa.launchpad.net/otter-browser/release/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

My system:
Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140722.2)
kernel is Linux 4.4.0-91-generic x86_84



  • gracious1
  • [*]
Re: Otter crashes and burns in Ubuntu Linux
Reply #1
Follow-up: I tried the AppImage, but it didn't work at all. I was able to download and execute the sample program, Subsurface. But I followed the same steps for the otter-browser AppImage, and double-clicking it just did nothing.

  • Emdek
  • [*][*][*][*][*]
  • Moderator
Re: Otter crashes and burns in Ubuntu Linux
Reply #2
@gracious1, try running AppImage from terminal and copy output, note that you usually need to mark it as executable first.
BTW, that version of Ubuntu is kind of outdated...
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.

  • gracious1
  • [*]
Re: Otter crashes and burns in Ubuntu Linux
Reply #3
"Kind of outdated"???? Ubuntu 14.04 is officially supported until 2019.     :irked:

And of course I marked the AppImage as executable before I tried to run it. As I stated in my post I followed all the steps for the otter AppImage as for the sample AppImage download. But even if I hadn't done the sample first, I would have known to chmod to executable. I have been using UNIX and UNIX-like operating systems since my undergraduate days.  :spock:

I re-installed from the PPA, and ran from the Terminal. The only output I get is:
Code: [Select]
$ otter-browser
Segmentation fault (core dumped)

(BTW, where are the preference/profile files for otter located? Haven't successfully purged those.)

  • Frenzie
  • [*][*][*][*][*]
  • Administrator
Re: Otter crashes and burns in Ubuntu Linux
Reply #4
(BTW, where are the preference/profile files for otter located? Haven't successfully purged those.)
Normally under ~/.config/otter/

  • gracious1
  • [*]
Re: Otter crashes and burns in Ubuntu Linux
Reply #5

To help you debug, here is the output of running the command otter-browser with GNU's debugger:

Code: [Select]
~$ gdb otter-browser
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from otter-browser...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/otter-browser
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe38fa700 (LWP 32207)]
[New Thread 0x7fffdab67700 (LWP 32208)]
[New Thread 0x7fffda366700 (LWP 32209)]
[New Thread 0x7fffd10de700 (LWP 32211)]
[New Thread 0x7fffd08dd700 (LWP 32212)]
[New Thread 0x7fffc7fff700 (LWP 32213)]
[New Thread 0x7fffc77fe700 (LWP 32214)]
[Thread 0x7fffd08dd700 (LWP 32212) exited]
[New Thread 0x7fffd08dd700 (LWP 32215)]
[New Thread 0x7fff6c33d700 (LWP 32216)]
[New Thread 0x7fff6b2bb700 (LWP 32217)]
[New Thread 0x7fff6a6ba700 (LWP 32218)]
[New Thread 0x7fff69e39700 (LWP 32220)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff4fc2d42 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
(gdb) backtrace
#0  0x00007ffff4fc2d42 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#1  0x00007ffff40dc072 in QWebHitTestResultPrivate::QWebHitTestResultPrivate(WebCore::HitTestResult const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x00007ffff40dc550 in QWebFrameAdapter::hitTestContent(QPoint const&) const
    () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x00007ffff3a3af50 in QWebFrame::hitTestContent(QPoint const&) const ()
   from /usr/lib/x86_64-linux-gnu/libQt5WebKitWidgets.so.5
#4  0x00007ffff3a3ee08 in QWebPage::frameAt(QPoint const&) const ()
   from /usr/lib/x86_64-linux-gnu/libQt5WebKitWidgets.so.5
#5  0x0000000000725ba3 in Otter::QtWebKitWebWidget::getHitTestResult(QPoint const&) ()
#6  0x0000000000684802 in Otter::WebWidget::handleToolTipEvent(QHelpEvent*, QWidget*) ()
#7  0x000000000072a2ff in Otter::QtWebKitWebWidget::eventFilter(QObject*, QEvent*) ()
#8  0x00007ffff771ce53 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007ffff332bc6c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007ffff3332770 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007ffff771cc2d in QCoreApplication::notifyInternal(QObject*, QEvent*)
---Type <return> to continue, or q <return> to quit---
    () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007ffff332ebef in QApplication::event(QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007ffff332bc8c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007ffff3330e56 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007ffff771cc2d in QCoreApplication::notifyInternal(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007ffff77691ad in QTimerInfoList::activateTimers() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007ffff7769661 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007ffff0d52e04 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff0d53048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007ffff0d530ec in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007ffff77699ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007ffff771b96b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007ffff77220e1 in QCoreApplication::exec() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
---Type <return> to continue, or q <return> to quit---
#24 0x0000000000542b03 in main ()
(gdb)

If there is a better place to send a bug report, please let me know. Thanks.

  • Emdek
  • [*][*][*][*][*]
  • Moderator
Re: Otter crashes and burns in Ubuntu Linux
Reply #6
@gracious1, Windows XP was still supported until recently. ;-)
So you are getting crash after using both that outdated package (14.04 uses very outdated Qt version...) and fresh AppImage?
Please check if you are still getting crash with AppImage after renaming configuration file.

BTW, which OpenSSL versions do you have installed?
AppImage uses official Qt bianries which expect 1.0.x as libssl.so (or with some suffix), OpenSSL 1.1 is not backwards compatible.
It also requires GStreamer 1.0.

About backtrace, AFAIR that Ubuntu version uses the most bogus QtWebKit package imaginable, using some snapshot from Qt 5.1 together with Qt 5.2 (due to issues with their failed phone attempt, AFAIR it was mentioned in changelog of that package or elsewhere).
Anyway, any QtWebKit version older than 5.4.x is pretty unstable and all versions older than 5.212 are outdated.

You should focus on AppImage.
You can try to extract it and try gdb again (run otter-browser.sh first).
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.

  • gracious1
  • [*]
Re: Otter crashes and burns in Ubuntu Linux
Reply #7
Hello. Sorry for the delay in getting back to you.

I have today re-installed otter-browser from the repository (using apt-get). So far, it seems to be going well, despite the apparent antiquity of my system  :monkey: , but I notice a few oddities.

For example, in the Preferences, the settings relating to passwords are grayed out, like so:
https://s6.postimg.org/4gburjlbl/Passwords-grayed-out-_Otter_01.png

Likewise, remembering search and form history are grayed out.

I also notice something else. The otter inside the O is appearing everywhere in my system, not just in Otter application windows. Here, for example, is SeaMonkey:
https://s6.postimg.org/521a70xbl/otter_issue_2.png

All my windows in every application look like this, with the otter-in-the-O in the upper left-had corner!

  • Emdek
  • [*][*][*][*][*]
  • Moderator
Re: Otter crashes and burns in Ubuntu Linux
Reply #8
@gracious1, it's an old version and Passwords Manager wasn't available yet.
Likewise, remembering search and form history are grayed out.
That is normal even for current master.
All my windows in every application look like this, with the otter-in-the-O in the upper left-had corner!
That might be displaced tray icon, try disabling Browser/EnableTrayIcon in about:config.

You can try newest AppImage too (weekly 191), there were some changes that might allow it to run for you.
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.

  • gracious1
  • [*]
Re: Otter crashes and burns in Ubuntu Linux
Reply #9
@gracious1, it's an old version and Passwords Manager wasn't available yet.

What is an old version? The version of Otter that I am using?

Code: [Select]
$ apt-cache policy otter-browser
otter-browser:
  Installed: 0.9.09.01-1~trusty~ppa1
  Candidate: 0.9.09.01-1~trusty~ppa1
  Version table:
*** 0.9.09.01-1~trusty~ppa1 0
        500 http://ppa.launchpad.net/otter-browser/release/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

So the candidate in the PPA is not up-to-date?

You can try newest AppImage too (weekly 191), there were some changes that might allow it to run for you.

Nope. Doesn't work.

  • gracious1
  • [*]
Re: Otter crashes and burns in Ubuntu Linux
Reply #10
Arrrgggh! Otter crashed again while I was editing my last post.  :no:   :bomb:

It crashed with signal 11. Here is what I got in the crash report:

Quote
This problem report is damaged and cannot be processed.

OSError('invaldi core dump: BFD: Warning /tmp/apport_core_c5uyjk28 is truncated; expected core file size >=188798320, found: 924090586.',)

Not very helpful, I know. :rolleyes:

And the AppImage just will not run.   :awww:   The sample program (Subsurface-4.6.2-x86_64) still runs just fine, so I am inclined to think there is something wrong with the AppImage not with my system.

  • gracious1
  • [*]
Re: Otter crashes and burns in Ubuntu Linux
Reply #11
Output of latest attempt to run AppImage:

Code: [Select]
$ ./otter-browser*191*.AppImage 
Loading /usr/lib64/libssl.so.1.0.0
Loading /usr/lib64/libssl.so.1.0.1
Loading /usr/lib64/libssl.so.1.0.2
Loading /usr/lib64/libssl.so.1.0
Loading /usr/lib64/libssl.so.1
Loading /usr/lib64/libssl.so.10
Loading /usr/lib64/libssl.so
Loading /lib64/libssl.so.1.0.0
Loading /lib64/libssl.so.1.0.1
Loading /lib64/libssl.so.1.0.2
Loading /lib64/libssl.so.1.0
Loading /lib64/libssl.so.1
Loading /lib64/libssl.so.10
Loading /lib64/libssl.so
Loading /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
Loading /usr/lib/x86_64-linux-gnu/libssl.so.1.0.1
Loading /usr/lib/x86_64-linux-gnu/libssl.so.1.0.2
Loading /usr/lib/x86_64-linux-gnu/libssl.so.1.0
Loading /usr/lib/x86_64-linux-gnu/libssl.so.1
Loading /usr/lib/x86_64-linux-gnu/libssl.so.10
Loading /usr/lib/x86_64-linux-gnu/libssl.so
./otter-browser: /tmp/tmp.mKe5ocfufL/libssl.so.10: version `libssl.so.10' not found (required by ./lib/libQt5Network.so.5)
./otter-browser: /tmp/tmp.mKe5ocfufL/libcrypto.so.10: version `OPENSSL_1.0.1_EC' not found (required by ./lib/libQt5Network.so.5)
./otter-browser: /tmp/tmp.mKe5ocfufL/libcrypto.so.10: version `libcrypto.so.10' not found (required by ./lib/libQt5Network.so.5)
$

It looks as though I am missing certain dependencies. Would it be possible to update the deb packages in the repository to include the libraries that not every LTS disto has access to? I seem to have better luck installing that way.

I really want to make this browser work, and I would appreciate any help. Thanks.

  • Frenzie
  • [*][*][*][*][*]
  • Administrator
Re: Otter crashes and burns in Ubuntu Linux
Reply #12
For me the latest weekly AppImage (191) won't start either due to some libssl nonsense (see here). OpenSSL is pretty frustrating. :(

(I guess you could always build Otter yourself. :P)

  • Emdek
  • [*][*][*][*][*]
  • Moderator
Re: Otter crashes and burns in Ubuntu Linux
Reply #13
I guess you could always build Otter yourself.  :P
I think that this would be the best option for such old version of Ubuntu, it uses Qt 5.2 so even that alternative approach for AppImage wouldn't help, it's too old Qt version.
Nadszedł już czas, najwyższy czas, nienawiść zniszczyć w sobie.
The time has come, the high time, to destroy hatred in oneself.