The menu can also be re-enabled from the context menu in the chat view, i.e.
right clicking the chat background.
This bug report is of course still valid, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I was asked to fix a machine affected by this after upgrading from
trusty to xenial (LTS releases).
On this machine systemctl start sddm started sddm successfully, but
enable did nothing.
Reinstalling the sddm package added the previously missing
/etc/systems/system/display-manager.service symlin
Quassel should really save any signal handler that is in place before
installing a new one. After handling the signal, the original one should
be restored and the signal be re-raised. I thought we were already doing
that, but looking at
https://github.com/quassel/quassel/blob/17311326016f3654fd33a6
Sounds like the first Quassel instance isn't stopped when switching to
plasma5. Then when switching back another Quassel instance is started.
This second instance tries to use the nick name that's blocked by the
first instance, so the IRC network assigns a random string as nick name.
--
You recei
https://github.com/quassel/quassel/commit/3939820389d995f56a073fc1d54ab245c6558312
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299872
Title:
Quassel Client won't start with recent updates (3/30/2
The proposed fix was committed upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299872
Title:
Quassel Client won't start with recent updates (3/30/2014)
To manage notifications about this b
** Bug watch added: ATi Linux Platform Bugs #1026
http://ati.cchtml.com/show_bug.cgi?id=1026
** Also affects: fglrx via
http://ati.cchtml.com/show_bug.cgi?id=1026
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Bug watch added: Debian Bug tracker #678567
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678567
** Also affects: linux (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678567
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
You'd need to file a bug against xdg-utils then, please.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/884752
Title:
quassel ignores default web browser
To manage notifications about this bug go to
Quassel relies on Qt to handle links, which under Linux means that the
URL is passed on to `xdg-open`.
** Changed in: quassel (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to quassel in Ubuntu.
https://b
Working fine for me, not seeing any regressions.
** Attachment added: "install.log"
https://bugs.launchpad.net/ubuntu/+source/choqok/+bug/654236/+attachment/1694045/+files/install.log
--
SRU : Please release choqok 0.9.85 for lucid
https://bugs.launchpad.net/bugs/654236
You received this bug
** Bug watch added: KDE Bug Tracking System #174117
http://bugs.kde.org/show_bug.cgi?id=174117
** Also affects: kdeartwork via
http://bugs.kde.org/show_bug.cgi?id=174117
Importance: Unknown
Status: Unknown
--
screen not locked on suspend or hibernate (screen saver not activated)
I'm experiencing the same behaviour in lucid as described in this bug
report. This is however different from what is described in kde-bug
#224517, since a comment states, that the screen does get locked after
waiting for I/O heavy resume tasks to finish.
--
screen not locked on suspend or hiberna
Fix committed upstream:
http://git.quassel-irc.org/?p=quassel.git;a=commit;h=bb94bb24a70ee1b0784afe6a7b2b875ec68053d1
status fixcommitted
assignee kitterman
** Changed in: quassel (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: quassel (Ubuntu)
Assignee: (unassigned
This seems to be a problem with the Danish translation.
status confirmed
** Changed in: quassel (Ubuntu)
Status: New => Confirmed
--
Messages does only contain "1"
https://bugs.launchpad.net/bugs/533094
You received this bug notification because you are a member of Ubuntu
Bugs, which
Quoted from http://bugs.quassel-irc.org/projects/quassel-irc/wiki/FAQ
#How-do-I-ignore-CTCP-requests:
Versions 0.5.2 and newer offer a "CTCP" type in the ignorelist settingspage.
If selected, the rule is parsed as follows:
hostmask [CTCPCMD CTCPCMD]
For example "* VERSION PING" would ignore VERSIO
It has probably just been sent as white text? You can disable text
coloring via Settings > Interface > Chat View > [_] Allow colored text
--
some caracter can't be see without select all
https://bugs.launchpad.net/bugs/504690
You received this bug notification because you are a member of Ubuntu
Err, I meant to refer to alsaconf, not asoundconf.
--
alsa-utils missing asoundconf
https://bugs.launchpad.net/bugs/376024
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
Shipping asoundconf wouldn't do any harm, would it? I don't understand
why you would remove a well established, working application only
because there's an alternative. After all, Open Source *is about* having
options to choose from.
--
alsa-utils missing asoundconf
https://bugs.launchpad.net/bug
Can anyone of you maybe provide a stacktrace?
Once the error occurs, run: gdb `which quassel` `pgrep quassel`
Then in gdb execute "bt" followed by "c" and then ctrl+c a few times.
--
Quassel freeze and can't be used when resize or change option
https://bugs.launchpad.net/bugs/435107
You received
The patch doesn't provide "savedefault fallback" functionality yet, does
it?
--
savedefault not default in update-grub
https://bugs.launchpad.net/bugs/216178
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
With a fresh install of Hardy, updates added I was able to unlock for
administration tasks. After adding another
admin user, neither I nor the admin user can unlock. Popup says
Could not authenticate
An unexpected error has occurred.
A side effect is that navigating from System --> Adminstrati
22 matches
Mail list logo
