FAQ
Page translations: PPFF (Castellano) FAQ (日本語) НПП SEG (Euskara)
1. I have been told to look for a file in my profile directory. So where are all my profile data stored?
2. I have bookmarked a page, the star icon is shining, but I cannot see the bookmark in the Menu or in the bookmark panel.
3. I cannot save any bookmark and my history is empty. What should I do?
4. QupZilla is using a lot % of my CPU. What can I do to cool it down?
5. I have heard that QupZilla supports importing bookmarks from other browsers, but I can't find this feature anywhere.
6. Site xyz offers less features in QupZilla than in other browser, is it possible to change the User Agent?
7. I have started QupZilla, but it looks very very different from the screenshots (very ugly!).
8. How can I get command line output in Windows?
9. How do I debug QupZilla in case of a crash?
10. I have successfully compiled QupZilla on FreeBSD, but when I try to run it, only a blank window appears.
11. QupZilla's blog says, that nested bookmark folders are supported. I do not find this in QupZilla yet.
12. Does QupZilla support the blink web rendering engine used in Chromium?
13. Does QupZilla support Firefox and/ or Chrome extensions?
14. I have problems with the facebook web-page. How can I fix it?
15. QupZilla does not play HTML5-videos on youtube. What can I do?
16. There is no Web Inspector in QupZilla 2.0?
1. I have been told to look for a file in my profile directory. So where are all my profile data stored?
Please select the menu entry Help -> Configuration Information and then scroll to the Paths section.
2. I have bookmarked a page, the star icon is shining, but I cannot see the bookmark in the Menu or in the bookmark panel.
When you add a bookmark from the star icon, it is automatically added to unsorted bookmarks folder.
You will find unsorted bookmarks only in the library (Ctrl+Shift+O).
You can move the bookmark to other folder with the star icon or in the library.
At first, please check that you have installed the Qt SQLite plugin. On Debian this package is called libqt4-sql-sqlite and libqt5sql5 respectively on qt5.
If you have it installed and you are still experiencing this issue, please run QupZilla from a terminal window and have a look at the output.
If it contains something like
QSqlQuery::value: not positioned on a valid record
QSqlQuery::value: not positioned on a valid record
it seems that your profile database is broken. You can check it with some SQLite database viewer like (for example) DB Browser for SQLite. If the database is empty, then you can recover it by creating a new profile.
If this does not help, please open an issue.
Well, the problem with using excessive amount of processor time is very likely caused by some flash content running in the browser (most likely bad coded advertisement). You have 3 options to solve this:
- Completely disable flash support by unchecking Preferences -> Browsing -> Web Configuration -> Allow Netscape Plugins (Flash plugin) (Allow Pepper Plugins (Flash plugin) in QupZilla 2.0)
- Use the Click2Flash plugin by checking Preferences -> Extensions -> folder "WebKit Plugins" -> Allow Click to Flash. You will now have to start every flash content on a specific site manually. (Not available in QupZilla 2.0)
- Use AdBlock to filter adverts Menu Tools -> AdBlock -> Enable AdBlock. If your filters list is empty, press Options to add filter subscriptions or to create your own rules.
5. I have heard that QupZilla supports importing bookmarks from other browsers, but I can't find this feature anywhere.
This feature has been added in version 1.0.0-rc1.
You will find the Import Bookmarks option in Menu File -> Bookmarks -> Organize Bookmarks:
The importing wizard will then guide you through the importing process. As you can see you will be able to export your bookmarks as well.
6. Site xyz offers less features in QupZilla than in other browser, is it possible to change the User Agent?
It might help, if you change the user agent in QupZilla. Starting with QupZilla version 1.1.8 you will be able to do this in the preferences:
It is even possible to define a User Agent per site.
You have probably downloaded a tarball for another Linux distribution and executed QupZilla from it.
You need to move files from /usr/share/qupzilla directory in the tarball to (probably) /usr/share/qupzilla directory in your system.
The exact path can be found directly from QupZilla: Menu Help -> Informations about application -> Paths -> Data
After a restart of QupZilla, it should work.
If you are not using a tarball for another Linux distribution, please verify, that you did not forget to run make install.
You have to, obviously, run qupzilla.exe from command line. You will be able do it by following these steps:
- Open Start -> Run -> type
cmd.exe-> Enter - Then you have to cd into directory where qupzilla.exe is. For example:
cd C:\\Program Files\QupZilla - To get output, you have to run
qupzilla.exe 1> output.txt 2>&1and output will be then written into output.txt file
I assume you are using Linux and have gdb installed:
At first, you will have to build QupZilla with debugging symbols. For this, please add CONFIG += debug into the src/defines.pri file.
Then start a debugging session:
gdb ./path/to/your/compiled/qupzilla
You will get into gdb prompt. Type:
start
QupZilla should be running now. Make the steps to reproduce the crash and gdb will inform you about that. Now type:
backtrace
and you have a backtrace of the crash that you can paste into your issue.
Starting with version 1.3.0 QupZilla is able to generate a backtrace and to save it into a file when QupZilla crashes. You will find this file in
$HOME/username/.config/qupzilla/crashlog
However, this will provide less info than debugging with gdb. So using gdb is preferred method to get backtrace.
Note: Please remove # characters from your backtrace when you are pasting it into issue. Otherwise, you would reference issues with number following after # character.
The best way to send backtraces would be to upload them at gist
10. I have successfully compiled QupZilla on FreeBSD, but when I try to run it, only a blank window appears.
There is problem with raster graphics system on FreeBSD with (probably) NVIDIA drivers.
You can workaround it by running QupZilla with the native graphics system:
qupzilla -graphicssystem native
Please note, that running QupZilla with the native graphics system may be slower.
To fix this issue, you have to set 3 sysctls:
kern.ipc.shmmax=67108864
kern.ipc.shmall=32768
kern.ipc.shm_allow_removed=1
You can do it by
- putting them in /etc/sysctl.conf and running
/etc/rc.d/sysctl restart - set them manually with:
sysctl kern.ipc.shmmax=67108864
sysctl kern.ipc.shmall=32768
sysctl kern.ipc.shm_allow_removed=1
11. QupZilla's blog says, that nested bookmark folders are supported. I do not find this in QupZilla yet.
Starting with version 1.8.0 nested or multi-level bookmarks are fully supported.
Please check, if this version is available for your distribution and install it.
QtWebEngine is a new web engine based on Chromium, adopted for use within Qt, which has been introduced in the Qt-5.4 series. Given the fact that Chromium uses multi-process architecture, a lot of the API is now asynchronous (instead of synchronous as in QtWebKit). As a consequence a lot of advanced features in QupZilla had to be adapted due to this change. As of QupZilla 2.0.0 it uses QtWebEngine only.
Since January 27, 2015 QupZilla with QtWebEngine is in the master-branch of the git-repository. You might want to clone it with:
linux:~>git clone https://github.com/QupZilla/qupzilla.git
Hint: QupZilla with the QtWebkit engine can be found in the v1.8-branch, which can be cloned with:
linux:~>git clone -b v1.8 https://github.com/QupZilla/qupzilla.git
To build QupZilla you will have to install libqt >= 5.6.0 and of course libqt5-qtwebengine. The package names might be different depending on your distribution. Then you can start compiling QupZilla by invoking
linux:~>qmake DEFINES+=NO_SYSTEM_DATAPATH
It is recommended to build QupZilla with NO_SYSTEM_DATAPATH, so it can be run directly from the \bin directory instead of installing it system-wide.
To answer this questions we would like to give you some background information about APIs and dependencies at a high technical level.
Firefox Extensions
Generally speaking it is possible to support firefox extensions via XUL (XML User Interface Language), which is Mozilla's XML-based language for building user interfaces of applications like firefox. These
extensions are also known as traditional or classic. Due to the fact, that XUL is a completely different framework than Qt, there is no reasonable factor and benefit to mix two or more UI frameworks.
The other type of firefox extensions, which are known as restartless or bootstrapped, may be supported, but it takes to much effort to implement them.
Chrome Extensions
From a technical point of view Chrome extensions are the same as the restartless or bootstrapped firefox extensions. In addition, because of the multi-process architecture, they support asynchronous messaging
between extension and browser and between other extensions. Although it may be possible to somehow support these extensions, it is just too much effort again.
It has to be mentioned, that there will probably be a huge impact on the performance of QupZilla, as all extensions will run in one single process in QtWebkit - which is not the case with Chrome.
Conclusion: Firefox and Chrome extension are currently not supported in QupZilla. Generally, it is not the goal of the project. It never was and never will be.
Please consider, that even without Firefox or Chrome extensions QupZilla is a full-featured web browser! Thus, it comes with many features, that provide the almost same functionality with a high integration into your browsing experience:
AdBlock
AdBlock was designed to subscribe to 3rd party filter lists and/ or to create own filter lists. By selecting suitable filter subscriptions it will be possible to achieve a functionality, that comes close to ghostery or noscript.
FlashBlock
Blocks unwanted flash content. User-defined whitelist entries are supported.
Mouse Gestures
Provides support for navigating in webpages by mouse gestures
GreaseMonkey
Provides support for userscripts (www.userscripts.org)
Access Keys Navigation
Provides support for navigating in webpages by keyboard shortcuts
Personal Information Manager
Adds the ability for QupZilla to store some personal data for filling out formulars in the web
Speed-Dial
The name says it all
RSS
Basic RSS reader implementation
Autoscroll
Provides support for autoscroll with middle mouse button
Videoner
Opens video links from video sharing services in an external program
MailHandle
Makes QupZilla handle mailto links in online services
StatusBar-Icons
Adds additional icons (like for example AdBlock, GreaseMonkey, Images, Javascript, network status) and a zoom widget to statusbar
TabManager
A TabManager-Plugin for QupZilla
FlashCookieManager
A plugin to manage flash cookies
If you have problems to access facebook.com, then please try to do the following steps:
1 - Change the user agent to Mozilla/5.0 (Windows 7; rv:24.0) Gecko/20131101 Firefox/24.1.0
2 - Disable javascript
3 - Use the mobile version of Facebook
Unfortunately this issue is caused by QtWebkit, which will have to be fixed upstream. Please have a look at this issue as well.
To allow QupZilla to play HTML5-videos you will have to install the gstreamer-framework. You will find more detailed information here.
There isn't currently an API to use classic web inspector in QtWebEngine as it was in QtWebKit. The only way how to show a web inspector is to enable remote debugging and connect to it. This also posses a possible security issue, so it is disabled by default. To enable remote debugging (and web inspector + inspect element actions), you need to set the remote debugging port in environment variable:
export QTWEBENGINE_REMOTE_DEBUGGING=12345
and then restart QupZilla.