Public bug reported:
Platform/version:
Ubuntu 14.04
ii gccgo 4:4.9-1ubuntu6
ppc64el Go compiler, based on the GCC backend
ii gccgo-4.9 4.9-20140406-0ubuntu1
ppc64el GNU Go compiler
ii gccgo-go
** Changed in: hockeypuck
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1108416
Title:
word-based key lookup should be case insensitive
To manage
** Also affects: hockeypuck (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1108416
Title:
word-based key lookup should be case insensitive
To
** Changed in: hockeypuck
Milestone: 0.9 = 0.8.2
** Changed in: hockeypuck (Ubuntu)
Assignee: (unassigned) = Casey Marshall (cmars)
** Changed in: hockeypuck
Status: Confirmed = Won't Fix
** Changed in: hockeypuck
Status: Won't Fix = In Progress
--
You received this bug
** Changed in: hockeypuck
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1108416
Title:
word-based key lookup should be case insensitive
To manage
I have verified this fix on a vanilla lucid. After installing from
proposed, haveged installs successfully and starts up.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I ran into this issue working with a private apt repository at
Canonical, in the context of adding a configured repository from a Juju
charm install hook, but it seems like a general issue which may affect
users of apt-add-repository.
I added a custom repo with:
Oh, and these are the package versions I upgraded to tested:
ii xfce4-power-manager 1.2.0-2ubuntu1.1
amd64power manager for Xfce desktop
ii xfce4-power-manager-data1.2.0-2ubuntu1.1
all power
I'm running 13.10 and familiar with the issue, though I've mostly
ignored it. This package from proposed fixed it for me today. I've got
suspend-on-close for battery power, lock-screen-on-close for AC. Nice
work!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug is not fixed oneiric. I am running Xubuntu 11.10 and still
experiencing these random freezes on my T420. Subjectively seems like
certain graphics-heavy applications/plugins make it happen more often.
Also subjectively seems like some of the kernel options and phoronix
drivers make it
Seeing the same thing on 12.04 precise, on a busy SKS server.
** Changed in: sks (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937931
Title:
unable to
I built SKS 1.1.3 from source (not from apt-get source, downloaded
direct from code.google.com) with BDB 5.3 (downloaded from oracle.com
and compiled) and I got the same error with seven concurrent clients
doing /pks/add and queries in a continuous loop.
I built SKS 1.1.3 against BDB 4.7 from
Public bug reported:
Packages were up to date at time of writing (apt-get update apt-get
dist-upgrade after xubuntu 14.04 install). Then I installed byobu, which
pulled in python3-newt as a dependency, and I got this package install
error:
Setting up python3-newt (0.52.15-2ubuntu4) ...
This fix resolved the issue for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295774
Title:
ERROR processing policydb rules for profile lxc-container-default,
failed to load
To
Public bug reported:
I have several user-space LXC 1.0 containers which recently stopped
working (apt-get dist-upgrade 2-3 days ago, maybe?). I've been unable to
start them up, I'm getting:
user@trusty:~$ lxc-start -n sandbox -d
lxc_container: command get_cgroup failed to receive response
Log
I'm getting the same Enocoding of mount rule failed when I restart
apparmor. I'm running Xubuntu 14.04 on my laptop, doing a dist-upgrade
at least daily. I was using LXC user-space containers to isolate non-
free apps, and it was working quite well until a few days ago. Is there
anything I can try
This stopped the runaway load cycles as a workaround:
sudo hdparm -B 254 /dev/sda
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm also seeing a ridiculous load cycle count increase on my thinkpad
x230 running xubuntu 14.04. I got suspicious when I could hear the faint
click in a quiet room, and it reminded me of the issue from several
years back.
193 Load_Cycle_Count0x0012 094 094 000Old_age Always
-
** Changed in: linux (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316284
Title:
[HP Probook 4540s] Load/Unload Cycle Count
To manage notifications
I am reopening this because:
1. My harddrive has already been cooked by this bug and I'll probably
have to buy a new one. I set up an upstart script to run the hdparm
command, but it seems to need it run more often than at just startup.
Check it out:
193 Load_Cycle_Count0x0012 090
Public bug reported:
When running my Thinkpad x230 on battery, the Load_Cycle_Count increases
at a high rate: about 10-15 load cycles per minute. I discovered this
issue in a quiet room, where I could hear the clicks (or death rattle,
as I've come to think of them).
The following commands will
Installed the BIOS update:
root@cloudsong:~# dmidecode -s bios-version sudo dmidecode -s
bios-release-date
G2ETA1WW (2.61 )
04/22/2014
Still burning load cycles on battery power:
root@cloudsong:~# while true;
do
date
smartctl -a /dev/sda | grep Load_Cycle
sleep 60
done
Fri Aug 1
The rate certainly seems slower than before with latest 3.16 kernel
(Linux cloudsong 3.16.0-031600-generic #201408031935 SMP Sun Aug 3
23:36:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux).
Is this looking more like a normal cycle pattern, or still more load
cycles than there should be?
Nope, still burnin. A fresh boot it doesn't seem too bad, but this just
happened, coming off of standby (that seems to worsen it):
Wed Aug 6 18:28:53 CEST 2014
193 Load_Cycle_Count0x0012 089 089 000Old_age Always
- 113151
Wed Aug 6 18:29:54 CEST 2014
193
Public bug reported:
Just did an apt-get update apt-get dist-upgrade on my trusty
laptop. It's been stuck in the libpam-systemd postinst for 15-20
minutes:
Recent output from dist-upgrade:
Unpacking xpra (0.12.3+dfsg-1ubuntu1) over (0.12.2+dfsg-1ubuntu1) ...
Processing triggers for man-db
I am getting the above error when I try to run tests on amd64 with gccgo
4.9.
http://paste.ubuntu.com/8827836/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381671
Title:
reboot tests fail to
^^ in juju master @ a7e1ea03bb98064a5173e2200335d641fde511a5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381671
Title:
reboot tests fail to build on gccgo
To manage notifications about this bug
Public bug reported:
Platform/version:
Ubuntu 14.04
ii gccgo 4:4.9-1ubuntu6
ppc64el Go compiler, based on the GCC backend
ii gccgo-4.9 4.9-20140406-0ubuntu1
ppc64el GNU Go compiler
ii gccgo-go
Here's another one:
panic: runtime error: invalid memory address or nil pointer dereference
[0/1099]│···
[signal 0xb code=0x1 addr=0x60]
This is still broken on trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1156704
Title:
Virtualenv breaks if python-configparser is installed
To manage notifications about this bug go to:
Public bug reported:
In xenial, pcscd CPU utilization occasionally goes haywire:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
This is what I've got installed ^^
c@mawhrin-skel:~/omnibus-layers$ dpkg -l | grep pcscd
ii pcscd 1.8.14-1ubuntu1
amd64Middleware to access a smart card using PC/SC
(daemon side)
--
You received this bug notification
FWIW I've observed the bug outside of Juju. Launching a trusty
container, sshd did not start until I remounted debug on the host. The
main reason it's been observed with juju is, Juju tries to SSH into the
instance right after cloud-init, but upstart in the container isn't
starting sshd so
This is the config from the container that had the issue this morning:
c@mawhrin-skel:~/omnibus-layers$ lxc config show
juju-145a3177-d1c0-4974-89f6-feaebb3ca87d-machine-0
name: juju-145a3177-d1c0-4974-89f6-feaebb3ca87d-machine-0
profiles:
- default
- juju-lxd
config:
user.juju-model-uuid:
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
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
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
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
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
It starts consuming 100% CPU after this:
02341452 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
0217 hotplug_libudev.c:619:HPEstablishUSBNotifications()
0068 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed
0149
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:
@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:
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
I ran pcscd as you suggested, capturing output. Made sure the smart card
was working by using my SSH key. I was then able to reproduce the 100%
cpu condition by plugging in my Logitech USB webcam.
Attached the output, but I redacted the hex dumps before posting here
because I'm not sure if they
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
** 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.
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:
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
Public bug reported:
I'm using lxd with zfs block storage on xenial, and having issues with
trusty containers. I've witnessed this problem when trying to bootstrap
as well as after rebooting the host and a container failed to start.
In the latter case, the container that failed to start was the
I also confirmed that the mountall error message was duplicated every
time I restarted the machine-0 container -- until remounting on the
host.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551854
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.
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
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
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
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
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.
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:
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,
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
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
*** 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
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
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
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
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
65 matches
Mail list logo
