Skip to main content ↑ ↓

Show Posts

This section allows you to view all Show Posts made by this member. Note that you can only see Show Posts made in areas you currently have access to.

Messages - rhubarbpieguy

1
Otter Browser Forum / Otter: Unknown option 'no-sandbox'
I've compiled otter-browser-1.0.81-dev333 and receive Otter: Unknown option 'no-sandbox.'  However, when starting Otter I receive 'Running as root without --no-sandbox is not supported.'  That implies to me 'otter-browser --no-sandbox' should work.

Yes, I realize running as root is discouraged by most.

3
Otter Browser Forum / Re: SSL support is not available or incomplete. 0.9.91-rc1v2-x86_64.AppImage
Quote from: Emdek on
uhm, perhaps it ended in some directory where Qt is not looking for it, I think that these are the paths used to locate it:

After viewing your link it seems openssl should be found.  Executing 'find' shows the following:

/etc/ssl/openssl.cnf
/etc/ssl/openssl.cnf.dist
/usr/bin/openssl
/usr/include/openssl
/usr/include/openssl/opensslconf.h
/usr/include/openssl/opensslv.h
/usr/include/openssl-1.0
/usr/include/openssl-1.0/openssl
/usr/include/openssl-1.0/openssl/opensslconf.h
/usr/include/openssl-1.0/openssl/opensslv.h
/usr/lib/libevent_openssl-2.1.so.6
/usr/lib/libevent_openssl-2.1.so.6.0.2
/usr/lib/libevent_openssl.la
/usr/lib/libevent_openssl.so
/usr/lib/openssl-1.0
/usr/lib/openssl-1.0/pkgconfig/openssl.pc
/usr/lib/pkgconfig/libevent_openssl.pc
/usr/lib/pkgconfig/openssl.pc

As I mentioned, I don't remember this problem with previous AppImages.  But with that said, I can't exclude a problem on my end.
7
Otter Browser Forum / Re: Key action questions.
Quote from: Emdek on
@rhubarbpieguy, I simply forgot about that issue, I'm not using that workflow myself...
About Alt shortcuts for menu bar, I'll discuss that with Chocimier, perhaps we will manage to add at least some basic solution.

Alt shortcuts would be very welcome but I don't understand why only basic functions would be added.

I admire and support the project.   And I do not want to come across as being snarky or overly critical.  But I view Alt shortcuts as very basic and the lack of such sticks out like a sort thumb.  The same thing applies to the F2 problem.  But I may well be an aberration as I prefer navigating by keystrokes.

I do realize development is harder than responding my saying "please do this."  But, if the F2 problem and lack of Alt shortcuts are remedied I would probably switch from occasional tester to regular user of Otter.  Just my take.
8
Otter Browser Forum / Re: Key action questions.
Quote from: Frenzie on
It'll disappear after hovering over it (or of course a quick F11 double press) but one could certainly argue it's odd that it doesn't disappear automatically. However, the way Otter and QupZilla allow you to use the addressbar through the keyboard with F8 and F6, without actually showing it, is certainly worse. It should be shown (temporarily?) or redirected to the "Go to Page or Search" (F2) dialog.

Yes, I'm aware the Firefox location bar disappears with user action.  And I do feel it should automatically disappear as does Otter's.  It appears we agree on that.

I don't understand your other point (did you mean Otter and Qupzilla?) as it seems Otter works perfectly logically (aside from requiring a double "Enter" of course).  When I hit F11 the screen goes full screen.  No toolbars or other distractions I don't want.  F2 brings up the location bar and as soon as I process an address it disappears and I go back to full screen.  Otter works perfectly as regards F2 in my book.

Assuming Alt access keys are fixed, something like the menu bar might be a different issue.  For while it's obvious "Enter" means the location bar's function is done, it seems the same can't be said of the menu bar.

I loaded Vivaldi 1.9 and couldn't bring up the location bar in full screen.  F6 brings it up in normal mode but does nothing in full screen.  If I'm right, that makes Vivaldi quite unattractive.  And of course, there's the chrome thing.

9
Otter Browser Forum / Re: Key action questions.
Quote from: Frenzie on
How do you mean exactly?

Firefox → works exactly as expected.
Qupzilla → doesn't show addressbar but allows you to type in it.

Opera → opening a new tab in full screen doesn't allow you to do much of anything other than use the speeddial, but it doesn't leave it.
Vivaldi → same issue as Opera… something Chromium-related?

I'm currently using Firefox which gives me the address bar after I access a new site.  That's no longer full screen.  For instance, if I read this post in full screen, hit F6, type ibm.com and "Enter" I have the IBM site with an address bar.  If memory serves, Qupzilla does something similar.

Otter doesn't do that to my memory.  If I access another site by F2 when in full screen the new site remains in full screen as it should.  Otter does it better.  That's a big plus for me.

I believe Midori also does full screen correctly, but it has no bookmark keywords so I don't take it seriously.  Opera and Vivaldi aren't on my radar. 
10
Otter Browser Forum / Re: Key action questions.
Quote from: Emdek on
Indeed, it's a regression, most likely introduced by address completion.

I occassionally test Otter to check progress and I'm confused.  Is this intended as permament?  It seems if I don't access the drop-down menu one "Enter" should take me to the entered address.  That's how other browsers work and is better.  And yes, I know it's been mentioned, but still no Alt access keys?

On the plus side, I really appreciate how Otter treats full-screen browsing.  If I'm using full screen and open a new site it stays full screen.  Why other browsers leave full screen makes zero sense to me.

I am also impressed by the app.  I compile almost everything and don't mind the effort.  However, to compile packages as large as QT and qtWebKit for one application is a bit extreme.  So, thumbs up for the app.
13
Otter Browser Forum / This tab has crashed. Otter-0.9.12/qt-5.7
It's been some some since I tried Otter but I decided to test it again as there are now bookmark keywords.  I don't remember keywords in earlier versions; perhaps I missed them.

Unfortunately, I receive "This tab has crashed." for several sites.  I don't remember this problem with previous versions.  What should I check?
15
Otter Browser Forum / Re: Key action questions.
No, I started Otter with "otter-browser --profile /tmp" and Enter again had no effect.  It's a minor annoyance and I understand that if it occurs on only my box makes it a low priority.

I assumed an incorrect setting as regards my drop-down menu access keys.  That, considering the time since I first questioned them.  IMHO, access keys are 101 and far from a low priority.

I feared/fear Bookmarks access keys will not happen.  I hope they're still on the docket.  If they happen, let me suggest again, don't waste letters on "Bookmark Page..." and "Manage Bookmarks..."
18
Otter Browser Forum / Key action questions.
Alt keys don't seem to work.  For instance, [Alt f] doesn't bring up the File menu.  In fact, File appears only as File.  None of the menu options display an underlined access letter.  I assume the problem is on my box but I see no appropriate setting.

"Enter" doesn't seem to work with F2 "Go to Page."  F2 works as it brings up "Go to Page."  However, after typing an address, "Enter" has no effect.  Shouldn't "Enter" take me to the address?

Is it still planned to add alpha access keys to the Bookmarks menu?  I really like the feature in Opera.  Unfortunately, recent releases don't seem to have it.
19
Otter Browser Forum / Key action questions.
Alt keys don't seem to work.  For instance, [Alt f] doesn't bring up the File menu.  In fact, File appears only as File.  None of the menu options display an underlined access letter.  I assume the problem is on my box but I see no appropriate setting.

"Enter" doesn't seem to work with F2 "Go to Page."  F2 works as it brings up "Go to Page."  However, after typing an address, "Enter" has no effect.  Shouldn't "Enter" take me to the address?

Is it still planned to add alpha access keys to the Bookmarks menu?  I really like the feature in Opera.  Unfortunately, recent releases don't seem to have it.
21
Otter Browser Forum / QT configuration options.
Compiling QT is a significant and time-consuming process.  Otter is the only reason I compile QT.  ./configure --help lists numerous options.  The following can be omitted.  Which are unnecessary for Otter?

    -no-c++11 .......... Do not compile Qt with C++11 support enabled.
    -no-largefile ...... Disables large file support.
    -no-accessibility .. Do not compile Accessibility support.
    -no-sql-<driver> ... Disable SQL <driver> entirely.
    -no-qml-debug ...... Do not build the in-process QML debugging support.
    -no-sse2 ........... Do not compile with use of SSE2 instructions.
    -no-sse3 ........... Do not compile with use of SSE3 instructions.
    -no-ssse3 .......... Do not compile with use of SSSE3 instructions.
    -no-sse4.1 ......... Do not compile with use of SSE4.1 instructions.
    -no-sse4.2 ......... Do not compile with use of SSE4.2 instructions.
    -no-avx ............ Do not compile with use of AVX instructions.
    -no-avx2 ........... Do not compile with use of AVX2 instructions.
    -no-mips_dsp ....... Do not compile with use of MIPS DSP instructions.
    -no-mips_dspr2 ..... Do not compile with use of MIPS DSP rev2 instructions.
    -no-pkg-config ..... Disable use of pkg-config.
    -no-mtdev ........... Do not compile mtdev support.
+  -no-journald ........ Do not send logging output to journald.
    -no-gif ............. Do not compile GIF reading support.
    -no-libpng .......... Do not compile PNG support.
    -no-libjpeg ......... Do not compile JPEG support.
    -no-freetype ........ Do not compile in Freetype2 support.
    -no-harfbuzz ........ Do not compile HarfBuzz-NG support.
    -no-openssl ......... Do not compile support for OpenSSL.
    -no-libproxy ....... Do not compile support for libproxy
    -no-xkbcommon-evdev . Do not use X-less xkbcommon when compiling libinput support.
    -no-xinput2 ......... Do not compile XInput2 support.
    -no-xcb-xlib......... Do not compile Xcb-Xlib support.
    -no-glib ............ Do not compile Glib support.
    -no-pulseaudio ...... Do not compile PulseAudio support.
    -no-alsa ............ Do not compile ALSA support.
    -no-gtkstyle ........ Do not compile GTK theme support.
    -nomake <part> ..... Exclude part from the list of parts to be built.
    -no-compile-examples ... Install only the sources of examples.
    -no-gui ............ Don't build the Qt GUI module and dependencies.
    -no-widgets ........ Don't build the Qt Widgets module and dependencies.
    -no-rpath .......... Do not use the library install path as a runtime
*  -no-optimized-qmake ... Do not build qmake optimized.
    -no-nis ............ Do not compile NIS support.
    -no-cups ........... Do not compile CUPS support.
    -no-iconv .......... Do not compile support for iconv(3).
    -no-evdev .......... Do not compile support for evdev.
    -no-tslib .......... Do not compile support for tslib.
    -no-icu ............ Do not compile support for ICU libraries.
    -no-fontconfig ..... Do not compile FontConfig support.
    -no-strip .......... Do not strip binaries and libraries of unneeded symbols.
*  -no-pch ............ Do not use precompiled header support.
    -no-dbus ........... Do not compile the Qt D-Bus module.
    -no-use-gold-linker ..... Do not link using the GNU gold linker.
*  -no-separate-debug-info . Do not store debug information in a separate file.
    -no-xcb ............ Do not compile Xcb (X protocol C-language Binding) support.
    -no-eglfs .......... Do not compile EGLFS (EGL Full Screen/Single Surface) support.
    -no-directfb ....... Do not compile DirectFB support.
    -no-linuxfb ........ Do not compile Linux Framebuffer support.
    -no-kms ............ Do not compile KMS support.
    -no-gcc-sysroot ..... When using -sysroot, it disables the passing of --sysroot to the compiler
    -no-feature-<feature> Do not compile in <feature>.
    -no-opengl .......... Do not support OpenGL.
    -no-libinput ........ Do not support libinput.
    -no-gstreamer ....... Do not support GStreamer.
*  -no-system-proxies .. Do not use system network proxies by default.
    -no-warnings-are-errors Make warnings be treated normally
    -no-slog2 .......... Do not compile with slog2 support.
    -no-pps ............ Do not compile with pps support.
    -no-imf ............ Do not compile with imf support.
    -no-lgmon .......... Do not compile with lgmon support.
    -no-framework ...... Do not build Qt as a series of frameworks.
    -secure-transport .. Use SecureTransport instead of OpenSSL (requires -no-openssl)
    -no-android-style-assets ....... Do not compile in the code which automatically extracts
22
Otter Browser Forum / Re: Issues with single key shortcuts
My single key shortcuts work.  However, I do notice a noticeably slower transition between pages than with Opera.  Same box, same connection, same time, but slower with Otter.

I don't consider it a significant problem.  Just feedback.
23
Otter Browser Forum / Re: Site problem with Opera and Otter.
Quote from: Emdek on

@rhubarbpieguy, have you tried changing UA and private tab (it does a bit more than just disabling cookies ;-))?
You said that it was blank page and not an error page, could you please check source if it is empty (Ctrl+U or action in context menu and View menu)?
I've heard that sometimes QtWebKit fails to render a page.


Sorry, I missed the private tab earlier.  I'll try private tab and check source next time things act up.  All sites are coming up now without problems.
24
Otter Browser Forum / Re: Site problem with Opera and Otter.
Quote from: Emdek on

@rhubarbpieguy, we can start debugging with something simple, for example checking if changing UA helps, or disabling cookies (you can disable them for that specific site using Website Preferences) and then checking if it works when opened in private tab.


This is perhaps oppertune as linuxfromscratch.org won't load with Opera as I compose this, but does with Firefox AND Otter.  This the first time I remember that a problem site doesn't work with Opera but does with Otter.

I disable JavaScript globally and enable it on a per site basis only when necessary.  I mark "Accept cookies only from the site I visit" and "Delete new cookies when exiting Opera."  I changed my cookie settings to "Accept cookies" and "Never accept cookies"; reloading each time with no success.  Although a stretch, I also enabled JavaScript for the site without success.

It may still simply be my ISP.  But I contacted them when I had a non-responsive site with Opera but had that site up with Firefox.  They supposedly checked my connection and gave a thumbs up.  When I asked if they were possibly throttling down my speed based on browser they basically said "are not, are not."

I was pleasant in asking the question but was not surprised by their answer.  I'm really at a loss on this one and do appreciate your help.  However, if this isn't Opera/Otter related and you can suggest a more appropriate forum I'll move the question there.
25
Otter Browser Forum / Re: Site problem with Opera and Otter.
That makes sense to me, which is why I mentioned I'd contacted my ISP.

However, it doesn't make sense in that with each instance I immediately check the problem site with Firefox and test-qtwebkit.  The problems occur only with Opera/Otter.

My ISP is treating my connection differently based on my browser?  The problem would be easier if it were consistent, but that's probably what makes it a problem.