Public bug reported:
recently upgraded to Ubuntu 24.04.1 LTS
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-44-generic 6.8.0-44.44
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architec
Same issue, fingerprint reader not recognized. ASUS VivoBook K-513 Linux
Mint 20.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641290
Title:
[04f3:0903] Elan Microelectronics Corp fingerprint rea
Hi,
After the latest Ubuntu updates I am no longer experiencing this issue
(possibly nvidia related?)
Thanks for your support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949909
Title:
Computer
Hi, apologies if bluez is not the appropriate package. I have followed
the above instructions in an case.
1. No crash files present.
2. The following problems were reported on errors.ubuntu.com
https://errors.ubuntu.com/oops/feac943a-8847-11eb-9538-fa163ee63de6
https://errors.ubuntu.com/oops/7f3
Public bug reported:
Crash on resume from suspend. The following messages appear and the
computer stops responding:
```
[ 26.227264] Bluetooth: hci0: Reading supported features failed (-16)
[ 26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask
failed (-95)
```
ProblemTy
More, this is on a Lenovo laptop, LCD only (no external monitors, no USB
graphics cards on anything like that). Also:
=
$ openscad --info
QObject::startTimer: Timers can only be used with threads started with QThread
OpenSCAD Version: 2021.01
System information: Linux 5.11.0-18-ge
Public bug reported:
After upgrade from 20.10 to 21.04, I am unable to run OpenSCAD
successfully.
The program launches ok, but after clicking New or loading a file, the
preview/render window is blank with no axes shown. When opening an
existing .scad file, the Console window shows that the design
Public bug reported:
If I add --help to the end of an enable command, I get a stack trace:
```
ubuntu@pro1604:~$ sudo ua enable fips --help
ERROR:root:Unhandled exception, please file a bug
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 937, in wr
I suspect it might be an issue with snapd not being ready to execute
snaps, this might help confirm.
Is this a persistent issue or does it eventually resolve with retries?
Did this happen early in the machine uptime, perhaps in cloud-init?
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1883089 ***
https://bugs.launchpad.net/bugs/1883089
As the fix this was a duplicate of has been abandoned, can this still be
addressed somehow? Is there anything I can do to move this forward?
--
You received this bug notification because you are a member
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461009/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461008/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461007/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Title:
No
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461006/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Title:
No
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461005/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Titl
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461004/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461003/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/191
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461002/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461001/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461000/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460999/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Title:
No
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460998/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460997/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460996/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Title:
No s
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460995/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460994/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Title:
No s
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460993/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460992/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460991/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914881
Title:
No sou
apport information
** Tags added: apport-collected
** Description changed:
There is no sound output from the laptop internal speakers when running
Ubuntu 20.10.
This is a dual-boot system;
- Booting Windows first and then rebooting to Ubuntu -> sound works fine
- Booting Ubuntu fi
Following instructions at:
https://wiki.ubuntu.com/DebuggingSoundProblems
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
** Tags added: kernel-sound
** Description changed:
There is no sound output from the laptop internal speakers when running
Ubuntu 20.10.
This is a dual-
Adding the alsainfo_good attachment
** Attachment added: "alsainfo_good.txt"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1914881/+attachment/5460962/+files/alsainfo_good.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Have collected alsa-info output from non-working and working situations
as per the notes at
https://bugzilla.kernel.org/show_bug.cgi?id=195457#c11
echo 1 | sudo tee /sys/module/snd_hda_codec/parameters/dump_coef
sudo alsa-info --no-upload --output /home/derek/alsainfo_bad.txt
** Bug watch added
Public bug reported:
There is no sound output from the laptop internal speakers when running
Ubuntu 20.10.
This is a dual-boot system;
- Booting windows first and then rebooting to Ubuntu = sound works fine
- Booting Ubuntu first and then rebooting to Windows - Windows identifies
sound as not
though it may be at a lower level (I wanted to enter kde-plasma-desktop
here which I do have installed from Ubuntu)
** Package changed: ubuntu => meta-kde (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Public bug reported:
Since my upgrade to 20.10 I am sometimes seeing the keyboard becoming
unresponsive (or very slowly responding) in some applications. At the moment
emacs is in this state - menu events in emacs are fine. I've also seen this
behaviour in konsole and firefox. I think the loss
Public bug reported:
I've noticed first boot times are significantly slower on Ubuntu Focal
than other distros. The following benchmark was taken on the same host
with in-sync images (so image downloads aren't a factor).
https://paste.ubuntu.com/p/ZdscB88vWY/
I'm opening this bug because I care
*** This bug is a duplicate of bug 1886994 ***
https://bugs.launchpad.net/bugs/1886994
** This bug is no longer a duplicate of bug 1655458
Livepatch gives "Invalid Machine Token" and "check-failed" resulting in no
payload
** This bug has been marked a duplicate of bug 1886994
Bionic/Foc
Why does desktop depend on libsnmp35 though?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860620
Title:
ubuntu-desktop-minimal should not depend on mysql libs
To manage notifications about this b
Since `ua auto-attach` runs on boot, it needs to be improved to detect
changes in instance-id. If the instance-id changes, all prior tokens
should be deleted prior (or as part of) `ua auto-attach`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
After latest focal updates, gnome-shell crashes and I lose my entire
session when I lock the screen.
c@slate:~$ dpkg -l | grep gnome-shell
ii gnome-shell3.35.91-1ubuntu2
amd64graphical shell for the
I'm the upstream maintainer of Hockeypuck. If someone wanted to maintain
the package in Ubuntu or Debian, I'd be supportive, but this is not work
I'm willing to take on. Hockeypuck is primarily distributed as a snap
and docker image.
--
You received this bug notification because you are a member
Public bug reported:
Ive tried different usb sticks and continue to have system installer
crash while partitioning the hard drive
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.4
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
Nonfre
Public bug reported:
After upgrading to 20.04 I decided to remove packages that I don't need
or use.
I was surprised to find that mysql client, server and common packages
were installed, as I could not remember having installed mysql -- I
don't use it or develop for it...
When I removed them, ub
*** This bug is a duplicate of bug 1841318 ***
https://bugs.launchpad.net/bugs/1841318
I fumbled around and got it fixed.
On Tue, Aug 27, 2019 at 8:45 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> *** This bug is a duplicate of bug 1841318 ***
> https://bugs.launchpad.net/
*** This bug is a duplicate of bug 1841318 ***
https://bugs.launchpad.net/bugs/1841318
How can it be repaired?
On Tue, Aug 27, 2019 at 8:45 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> *** This bug is a duplicate of bug 1841318 ***
> https://bugs.launchpad.net/bugs/184131
Public bug reported:
I apologize that I cannot explain clearly what happened to end up with
this problem. The machine works when I get into firefox, but I really
don't have much. My orig. sys. did not have a "dash"? but I had top and
bottom options. I just do not know what occurred, but I would li
Public bug reported:
I have a dual boot system that somehow got corrupted on the ubuntu side.
What causes it I do not have a clue. There are two very shaky, blurred
screens. Pressing the firefox icon open up browser fine and all seems to
work. The display is different from what I gotten use to, bu
This is still an issue on Ubuntu 18.04.2 LTS. I can reliably get it to happen.
Need to run killall to get it to stop trying with large transfers. The [x] to
stop file operations will not work all the time once it hangs.
The terminal and windows dualboot work fine for transferring the same files.
Public bug reported:
The livepatch widget will show an error[0] if patches cannot be applied.
They cannot be applied on a Secure Boot system unless the livepatch
signing key is imported. Unfortunately this requires a reboot and some
confirmation in the UEFI settings, so it can't be automated.
`ca
Same problem on an old HP NX7010 Laptop with i386 and forcepae install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789035
Title:
cannot login due to seeing only white screen
To manage notificat
What is this? Can u stop?
On Jan 25, 2019 12:36 AM, "Seth Arnold" <1772...@bugs.launchpad.net> wrote:
> ** Information type changed from Public Security to Public
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1776110).
> https://bugs.launchpad.
hu? should i be worried?
On Thu, Jan 17, 2019 at 5:00 PM Brian Murray wrote:
> ** Changed in: ubiquity (Ubuntu Bionic)
> Milestone: None => ubuntu-18.04.2
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1776110).
> https://bugs.launchpad.ne
sorry who is this?
On Thu, Jan 3, 2019 at 7:25 AM Drew Walton
wrote:
> This needs to be merged back to bionic ASAP because it entirely prevents
> installing on UEFI systems.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1776110).
> https://bu
Upgrading bluez to 5.50 as mentioned in link below fixed the problem
with bluetooth headphones not connecting after resume on Ubuntu 18.04.
https://askubuntu.com/questions/1036195/bluetooth-doesnt-work-after-
resuming-from-sleep-ubuntu-18-04-lts
--
You received this bug notification because you
Public bug reported:
Dont know. tried to do update and got this automatically
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-software-common 3.28.1-0ubuntu4.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.2
Public bug reported:
nothing
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Uname: Linux 4.4.0-75-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: marshall 2187 F pulseaudio
/dev/snd/controlC2: marshall 2187 F pulseaudio
/dev/snd/controlC0: marshall 2187 F
I am experiencing the issue where my console becomes completely
unresponsive when the unity screensaver is activated.
I have tested some potential work arounds for console lockup when the unity
screensaver activates under 16.04 (choose one) :
Upgrade to 16.10
Upgrade to 16.04.2
In
Public bug reported:
We currently have a maas 1.9.5 setup on trusty that has 4 subnets
defined in it under 10.x.0.0, one /24, 2 /23s and a /21. With the
latest version of maas installed it appears that it is writing out two
zones configs for x.10.in-addr.arpa in the named.conf.maas file, which
is
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668123
Title:
lxc fails to start with cgroup error
To manage notifications about thi
I've had this occur on another system, and this time I could debug it a
little more freely. This is an interesting output:
# dpkg --purge --simulate systemd
dpkg: dependency problems prevent removal of systemd:
snapd depends on systemd (>= 204-5ubuntu20.20); however:
Package systemd is to be r
Got it fixed, thanks. Now I'm having other issues but I don't think they
are related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571416
Title:
System freezes shortly after reaching the desktop (
I put quotes around both, that must be what broke it. Then I tried to
fix it using live CD to re-edit but I couldn't make it stick as the live
CD couldn't update the bin. Mint always warns me of syntax errors so if
this did as well I missed it.
I'll try it again. I might just switch back to Tiger
I tried that and got a syntax error on reboot that I couldn't recover
from. I'll look at it again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571416
Title:
System freezes shortly after reaching
How do I add the boot options and have them stick? I tried modifying the
yaboot but I ended up breaking my install.
I can get it installed with the live radeon.agpmode=-1
then I was able to boot it by typing at the first boot Linux radeon.agpmode=-1
that's where it breaks down, I don't know how t
> Sidenote) the 18GB of /var/lib/juju/db (with backups, of backups, of backups)
> was not helpful, I'll need to talk to sosreport people about that. This is
> what made the report so huge.
I did notice that, but I figured getting you all of the data was better than
fiddling around trying to not in
It's uploading slowly to https://private-
fileshare.canonical.com/~bradm/lp1668123/, once you see the .md5 file in
place and the sosreport is 7.7G, it'll be done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I've generated a sosreport, but its 7.7G. How would you like me to get
this to you?
The interesting part is that all this was deployed via juju, so I don't
know how we got into this state. It also appears to be the only node in
this state, so its a bit confusing as to how it got to be this way.
Public bug reported:
After rebooting a KVM instance hosting LXCs, we get the following error:
$ sudo lxc-ls --fancy
lxc: cgmanager.c: lxc_cgmanager_escape: 331 call to
cgmanager_move_pid_abs_sync(name=dsystemd) failed: invalid request
and the LXCs won't start up. In the error logs it showe
For any poor soul who wanders here, here is the best known workaround
for this issue I've seen to date:
22-09-2016 15:23:18 < stgraber!~stgraber@ubuntu/member/stgraber: cmars:
if you mask (systemctl mask) the systemd units related to binfmt
(systemctl -a | grep binfmt) and reboot, then the problem
Public bug reported:
think I had an update failure trying to get 16.04
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: wine-gecko2.21:amd64 2.21-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: wl
ApportVersio
I apt purge'ed binfmt-support from my system and I'm still able to
comment here :) We'll see if this fixes the issue.
If it does, why was it even installed on my system by default to begin
with?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Still seeing this on xenial enough that I've written a script to perform
the umounting when LXD gets stuck. Do I even need binfmt_misc on my
system? Can I just remove it or would that break something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Public bug reported:
nova-compute process across 2 Openstack deployments died around the same
time as the recent libc-bin upgrade:
2016-07-12 00:59:26 status half-configured libc-bin:amd64 2.19-0ubuntu6.9
2016-07-12 00:59:26 status installed libc-bin:amd64 2.19-0ubuntu6.9
Digging into the lo
Public bug reported:
We ran into a situation over the past couple of days where we had 2
different ceph-osd nodes crash in such a way that they caused ps listing
to hang when enumerating the process. Both had a call trace associated
with them:
Node 1:
Jul 4 07:46:15 provider-cs-03 kernel: [4188
I've just tried upgrading a system to the haproxy from your PPA, and it
now only logs to /var/log/syslog. The rsyslog.d file has disappeared
completely, and its no longer logging to /var/log/haproxy.log. Is that
the intended outcome from this? Or should it be logging to just
/var/log/haproxy.log
This just occured on another cloud, this time with nova-consoleauth
1:2015.1.4-0ubuntu2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572320
Title:
nova-consoleauth (2:12.0.2-0ubuntu1~cloud0) upgr
I've upgraded systemd across my cluster to 229-4ubuntu6, removed all my
custom tweaks to systemd settings, reloaded the daemon and both rabbitmq
and mysql appear to be working fine on my openstack cluster. I'll be
throwing a bit more load at it, but usually by this point mysql has
fallen over, so
Public bug reported:
I'm trying to install a PPC64EL node with Xenial via MAAS 1.9.2 using
Juju 1.25.5 and it seems to be failing due to a possible multipath
issue. The node is setup in maas with a default single partition. The
boot logs show:
Begin: Running /scripts/init-premount ... done.
FWIW I'm also seeing limits hit in other areas, rabbitmq-server seems to
be a common one. I'm also randomly seeing:
Failed to allocate directory watch: Too many open files
on the command line. I suspect its related to the percona and rabbitmq
services hitting limits, but I'm not exactly sure.
When is this going to be fixed upstream? I'm having to remount on the
host and restart containers quite often. I can't imagine this will be a
good user experience for new LXD users on xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Public bug reported:
apt-get update && apt-get dist-upgrade and this happened
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-path (not installed)
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zcommo
Public bug reported:
Did an apt-get update && apt-get dist-upgrade. My /boot partition did
fill up at some point but I was able to recover with autoremove.
apport opened this bug so I'll send it anyway in case something in it is
helpful. FWIW I've stopped evaluating zfs for the time being because
Public bug reported:
I've been setting up a Mitaka Openstack using the cloud archive running
on Trusty, and am having problems working with EFI enabled instances on
ARM64.
I've done some work with wgrant and gotten things to a stage where I can
boot instances, using the aavmf images.
However, wh
I'm not seeing the symbolic links error, but I am seeing this when
trying to start a trusty container on xenial:
https://github.com/lxc/lxd/issues/1836
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/155
I can work around this with my custom build of pcscd with udev disabled,
but it seems that this issue will still affect Debian and Ubuntu users
who install the package.
Can we mark this bug as Confirmed, since my symptoms are so similar to
the descriptions in the Debian bug[1] you've linked above?
Note these are freshly bootstrapped clouds, as per an irc conversation
with alexisb and anastasiamac_.
I took a working juju environment deploying to canonistack, just changed the
default series, did a juju bootstrap and then a juju
deploy local:xenial/ubuntu --to lxc:0, and got an error as abov
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557345
Title:
xenial juju 1.25.3 unable to deploy to lxc containers
To manage notifications about this bug go to:
h
Public bug reported:
There appears to be some issue with deploying to lxc containers using
juju 1.25.3 on Xenial.
When deploying with xenial to canonistack-lcy02:
bradm@serenity:~/src/juju$ juju deploy local:xenial/ubuntu --to lxc:0
Added charm "local:xenial/ubuntu-2" to the environment.
ERROR a
Public bug reported:
While debugging something, I ran the kvm-ok script on a VM running on
openstack, and got an interesting error:
ubuntu@juju-bradm-lcy02-machine-0:~$ sudo kvm-ok
INFO: /dev/kvm does not exist
HINT: sudo modprobe kvm_intel
INFO: Your CPU supports KVM extensions
/usr/sbin/kvm-o
Thanks for the fix. I didn't notice anything in particular that seemed
to cause the issue. I do remember having the issue right after boot &
desktop environment -- in some cases the first thing I did was start
containers in a gnome terminal. Other things I did at various points
last week:
- Usual
Haven't seen it in a few days. I'll reboot and see if I can reproduce
it. It usually happens after rebooting the host, when launching new
containers or existing ones would autostart.
Info you requested. I think the /usr/share/lxc/... might have been a red
herring. I'm exclusively using LXD on this
Recompiling with --disable-libudev gets rid of the 100% CPU problem and
I can still use my smartcard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive CPU utilization
To manag
@stforshee I'll uncomment the debugfs mount in my
/usr/share/lxc/config/ubuntu.common.conf (putting it back the way it
was), reboot, and see if I can reproduce it again.
My juju-lxd profile shows:
name: juju-lxd
config:
boot.autostart: "true"
security.nesting: "true"
description: ""
devices:
Interesting. I removed the /sys/kernel/debug mount and containers seem
to start up just fine:
c@mawhrin-skel:~$ grep kernel/debug /usr/share/lxc/config/ubuntu.common.conf
# lxc.mount.entry = /sys/kernel/debug sys/kernel/debug none bind,optional 0 0
c@mawhrin-skel:~$ lxc launch ubuntu-trusty t2
Cr
** Attachment added: "pcscd binary and core dump"
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4588521/+files/pcscd-core-bin.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Here's a core dump with the corresponding pcscd binary I built from
source, which was taken in the above-mentioned gdb session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551897
Title:
Excessive
Oh, here's /var/log/syslog from unplugging and replugging in my camera.
I Ctrl-C killed pcscd after it went to 100% each time.
pcscd segfaulted.
Mar 4 12:04:11 mawhrin-skel pcscd: debuglog.c:289:DebugLogSetLevel() debug
level=debug
Mar 4 12:04:13 mawhrin-skel kernel: [14604.513268] usb 3-1: US
Ran it with gdb, reproduced, and then interrupted when it started
consuming 100% CPU:
Thread 1 "pcscd" received signal SIGINT, Interrupt.
0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x000
1 - 100 of 525 matches
Mail list logo
