This happens for me quite often on 20.10:
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 32)
I can barely stay attached to wifi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
```
~/.config/fish/functions/fish_prompt.fish (line 281): Expected a string, but
ins
tead found a '&'
if which rvm-prompt >/dev/null ^&1
```
https://github.com/fish-shell/fish-
https://lists.xenproject.org/archives/html/xen-
users/2019-05/txtiEUldDuKY9.txt
This is the stacktrace/log that was originally captured by the filer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829
Also does not boot for linux-image-4.15.0-51-generic
>From the xl console output trying to boot that kernel. Previous kernels
have no problem.
libxl: error: libxl_xshelp.c:201:libxl__xs_read_mandatory: xenstore read
failed: `/libxl/45/type': No such file or directory
libxl: warning: libxl_dom.c:
This does not occur with the version of grub-xen on 18.04
root@nosgoth:/etc/xen/auto# apt show grub-xen
Package: grub-xen
Version: 2.02-2ubuntu8
I was using a self-built version of it mounted in, and that version
matched 16.04's version. After updating, I forgot to stop doing that. An
upgrade to
Public bug reported:
https://github.com/clementine-player/Clementine/pull/6087
Clementine, when interacting with it, not during automatic song
transition, will always reset the default device, switching away from my
bluetooth headset, and back to the non-default Speaker. This is super
annoying. F
> I guess it's pretty similar to LP: #1697556. Try blacklisting nouveau.
Good guess, it is indeed. Blacklisting nouveau and things suspend just
fine.
of note, I'm using the intel graphics adaptor exclusively, and don't
even have the nvidia drivers installed at the moment.
But this gets me to an
Still present in -26
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698616
Title:
4.10.0-22 No longer suspends on Dell XPS 9560
To manage notifications about this bug go to:
https://bugs.launchpad.
~ > uname -a
Linux XPS 4.12.0-041200rc5-lowlatency #201706112031 SMP PREEMPT Mon Jun 12
00:38:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Suspends just fine, so i'll tag it with "kernel-fixed-upstream"
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete
Public bug reported:
I have to roll back to -21 to be able to suspend.
Linux XPS 4.10.0-21-lowlatency #23~16.04.1-Ubuntu SMP PREEMPT Tue May 2
14:25:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
With -22, it doesn't suspend, and has lots of trouble with it.
I expect to be able to suspend when I cl
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698508
mentions the same symptoms, but it also talks about failures during
install. I don't have these failures, only the suspend problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Indeed, quite frustrating that this is still so old, and unfixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512027
Title:
open of device pixma:MX7600_... failed: invalid argument
To manage not
Oh, sorry, that symlink should be:
ln -s /usr/lib/i386-linux-gnu/sasl2 /usr/lib/sasl2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088822
Title:
SASL-Plugins not found, path mismatch
To manage n
There is something remarkably like this happening in 16.04.1
I had to create a symlink:
ln -s /usr/lib/i386-linux-gnu/sasl2/ sasl2
If I didn't do this the directory server didn't pick up any of the
GSSAPI modules. Made installing freeipa very difficult
--
You received this bug notification beca
Sorry for the noise on this bug! It turns out I'm simply not waiting
long enough for it to come up. It is being started on boot, and
everything is working like I expect, just isn't showing up.
I do still have the question about when it'll make it into a Xenial-updates
repo, though.
Thanks, and
Also, I've grabbed and installed the 5.15-1 .dpkg. systemctl reports
that it's enabled, but it never starts on boot. Checking right after
boot yields this:
```
root@hylden:~# systemctl status watchdog
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service; ena
Forgive my ignorance, but is this going to make it into a standard
xenial updates repo?
It's very broke as it stands right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
watchdog
17 matches
Mail list logo
