Project

General

Profile

FAQ » History » Version 29

genius3000, 12/24/2020 10:05 PM
Add a piece about the core setup wizard when the core is already configured.

1 1 dalbers
h1. FAQ
2 1 dalbers
3 6 seezer
{{toc}}
4 6 seezer
5 6 seezer
h2. How do I add accounts to my Quassel Core?
6 6 seezer
7 11 seezer
Check out the article on [[Manage_Core_Users|how to manage core users]]
8 6 seezer
9 6 seezer
h2. Where can I configure the autojoin list?
10 6 seezer
11 6 seezer
There is no list as such. Quassel will automatically rejoin the channels you were in at the time you shut Quassel down.
12 6 seezer
13 26 romibi
h2. Where is the config or script directory?
14 26 romibi
15 26 romibi
See [[Config Directories]] or [[Script Directories]]
16 26 romibi
17 6 seezer
h2. Why isn't Quassel using "Launchpad"?
18 6 seezer
19 19 johu
At the time being "Launchpad":https://www.launchpad.net doesn't support "git":http://gitorious.org/quassel.
20 9 shikamaru
21 9 shikamaru
h2. I lost my menu, how can I make it reappear?
22 9 shikamaru
23 28 public
Do you still have the toolbar with "connect", "disconnect" and other buttons? If you have it, and right click it, 'show menubar' is the last item.
24 1 dalbers
25 28 public
In old versions, you could press @Ctrl + M@ and the menu bar should reappear. This was removed as the default shortcut due to accidental use. You can click Settings>Shortcuts, and specify any custom shortcut for "Show menubar".
26 28 public
27 28 public
For other toolbars, you can display them from the submenu entitled "View".
28 12 seezer
29 21 romibi
h2. Quassel-Client (or Monolithic) won't start anymore (no visible window)
30 21 romibi
31 23 digitalcircuit
Check in @%appdata%\quassel-irc.org\quasselclient.ini@ or @~/.conf/quassel-irc.org/quasselclient.conf@ if there's a line with @MainWinHidden=true@. If so, change that to @MainWinHidden=false@
32 21 romibi
33 20 romibi
h2. How do I hide Join/Part/Quit messages?
34 20 romibi
35 20 romibi
Right-click inside the chat and choose Joins/Parts/Quits in the "Hide Events" menu.
36 20 romibi
37 22 digitalcircuit
h2. How do I start Quassel minimized?
38 20 romibi
39 23 digitalcircuit
Start Quassel with the command-line option @--hidewindow@
40 20 romibi
41 20 romibi
h2. Is there a list of command-line options?
42 20 romibi
43 23 digitalcircuit
For an up to date list of command line options start Quassel with the option @--help@
44 20 romibi
45 24 digitalcircuit
h2. How do I ignore specific highlights?
46 24 digitalcircuit
47 24 digitalcircuit
Version 0.13.0 and newer offer "Highlight Ignore Rules" to disable highlights in the same way you can add highlights.
48 24 digitalcircuit
49 24 digitalcircuit
For example, to ignore all pings from a bot with the nickname @qAnnounce@, add a new highlight ignore rule with empty rule text and a "Sender" of "qAnnounce!*".
50 24 digitalcircuit
51 24 digitalcircuit
Or, to keep a nickname variant from highlighting you, e.g. @yournick[m]@, add a highlight ignore rule with a "Rule" of "yournick[m]".
52 24 digitalcircuit
53 24 digitalcircuit
h2. How do I include special characters in Highlight/Ignore rules?
54 24 digitalcircuit
55 24 digitalcircuit
Version 0.13.0 and newer allow escaping special characters such as "*", "?", ";", "!", and "\" by prefixing them with an additional "\".
56 24 digitalcircuit
57 24 digitalcircuit
For example, "A question\?" would match "A question?" literally.
58 24 digitalcircuit
59 24 digitalcircuit
Sender/channel/scope are similar, with "\;" turning into a literal ";", and "\!test" matching the literal channel "!test" instead of inverting the rule.  "!" only needs escaped at the beginning of scope rules.
60 24 digitalcircuit
61 25 digitalcircuit
Take a look at the "full Pattern matching documentation page":https://bugs.quassel-irc.org/projects/quassel-irc/wiki/Pattern_matching for additional help.
62 25 digitalcircuit
63 12 seezer
h2. How do I ignore CTCP requests?
64 12 seezer
65 12 seezer
Versions 0.5.2 and newer offer a "CTCP" type in the ignorelist settingspage.
66 12 seezer
If selected, the rule is parsed as follows:
67 12 seezer
68 23 digitalcircuit
@hostmask [CTCPCMD [CTCPCMD ...]]@
69 12 seezer
70 12 seezer
For example "* VERSION PING" would ignore VERSION and PING requests for any hostmask.
71 12 seezer
If no CTCPCMD is given, all requests are ignored.
72 12 seezer
73 12 seezer
Only global- and per network scope are supported.
74 12 seezer
Since CTCP is ignored on the coreside, "Strictness" is always permanent.
75 13 kitterma
76 17 remi
CTCP ignore is patched into quassel 0.5.0-0ubuntu1.1 for Ubuntu Karmic users.
77 18 EgS
78 18 EgS
h2. Why does clicking on the systray icon take me to some strange buffer called something like "bartol.freenode.net"?
79 18 EgS
80 18 EgS
This is a known bug that needs to be fixed. But there is a workaround (Requires Quassel 0.6.0+).
81 18 EgS
82 18 EgS
First some background:
83 18 EgS
Quassel allows to show notices sent from a specific IRC server in separate buffers. This behavior is controlled by the setting "Message Redirection -> Server Notices". The default setting is here to show them in the "Status Window". Until recently quasselcore would still create a buffer called "bartol.freenode.net" and store the messages in that buffer. When the client receives such a message it redirects them to the Status Window and the buffer "bartol.freenode.net" would be hidden from all "Chat Lists". The highlighting / notification processing still triggers the activity for the original "bartol.freenode.net" though.
84 18 EgS
85 18 EgS
The Solution:
86 18 EgS
Enable "Message Redirection -> Server Notices -> default target". This will make those "ghost buffers" visible and you can delete them. After that disable the setting again, so that Server Notices are only displayed in the "Status Window". Since Quassel 0.6.0 Quassel will not recreate the buffer unless you have "Message Redirection -> Server Notices -> default target" enabled.
87 29 genius3000
88 29 genius3000
h2. Why is the client showing the Core Setup Wizard when I've already set up my core?
89 29 genius3000
90 29 genius3000
This can happen if the core loses the configuration for its backend (database). This is more likely to happen with [[PostgreSQL]] and system updates than with [[SQLite]].
91 29 genius3000
92 29 genius3000
To fix this, close the core setup wizard and disconnect the client from the core. Then from the system hosting the core, ran the setup of the backend configuration again:
93 29 genius3000
<pre>
94 29 genius3000
sudo -u quasselcore quasselcore --configdir=/var/lib/quassel --select-backend=PostgreSQL
95 29 genius3000
</pre>
96 29 genius3000
This will ask for the username, password, hostname, port, and database to be used with PostgreSQL. The default values are likely okay and the password would have been set when initally setting up the backend, you will need it.
97 29 genius3000
98 29 genius3000
Depending on your operating system and method of install, you may have to modify the above command to match with the correct user or config directory; you may not even need to `sudo -u <user>` if you are logged in as the same user that quasselcore runs as. A mention from a user on Gentoo was to use this command:
99 29 genius3000
<pre>
100 29 genius3000
sudo -i -u quassel -- quasselcore --configdir /var/lib/quassel --select-backend PostgreSQL
101 29 genius3000
</pre>
102 29 genius3000
103 29 genius3000
Further details to each backend type can be found on the respective Wiki pages linked in the second sentence.