** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699037
Title:
linux-raspi2: 4.8.0-1041.45 -proposed
Just installed new kernel 4.12-rc7, my ELAN touchpad is still completely
dead (please find attached the dmesg output file):
[5.320298] i2c_hid i2c-ELAN1203:00: i2c-ELAN1203:00 supply vdd not found,
using dummy regulator
[5.581767] hid-multitouch 0018:04F3:3043.0007: Ignoring the extra
** Changed in: lxd (Ubuntu)
Status: New => Triaged
** Changed in: lxd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694855
Title:
LXD cannot
Hi Locas,
I see in your log some retries always breaking at:
12:26:28 AptDaemon.Worker [CRITICAL]: amavisd-new: subprocess installed
post-installation script returned error exit status 1
The reason is also in your log:
jún 24 09:00:25 usergep amavis[9336]: The value of variable $myhostname
lxc 20170523193141.848 ERRORlxc_conf - conf.c:instantiate_veth:2727
- failed to set mtu '9000' for veth pair (veth39WF6S and vethX3QWS9):
Invalid argument
So the issue (rather well hidden by Juju) is that the container is
configured to use an MTU of 9000 but the bridge it's connecting to
Marking this bug as invalid for LXD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692985
Title:
Juju openstack lvd returns always "Container is already running a
start operation"
To manage
Unable to reproduce in a normal unprivileged container:
```
stgraber@castiana:~$ lxc launch ubuntu:16.04 unpriv
Creating unpriv
Starting unpriv
stgraber@castiana:~$ lxc exec unpriv bash
root@unpriv:~# ls -lh /sys/kernel/
total 0
drwxr-xr-x 2 nobody nogroup0 Jun 26 06:32 boot_params
Public bug reported:
I'm new to Ubuntu, could someone explain me to this step by step?
Thanks!
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: url-dispatcher 0.1+16.10.20160816.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => 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/1699028
Title:
linux: 4.10.0-25.29 -proposed tracker
*** This bug is a duplicate of bug 1670629 ***
https://bugs.launchpad.net/bugs/1670629
Hi,
this appears to me as a known issue being worked on already - I dupped your
report onto the main discussion so you can participate there.
** This bug has been marked a duplicate of bug 1670629
Public bug reported:
Need help with this annoying bug
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: ubuntu-app-launch 0.9+16.10.20160928-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
AptOrdering:
Public bug reported:
Dell optiplex 520 2GB ram. HDD 120MB, presenta error durante el
funcionamiento de inicio.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.8.0-56-generic 4.8.0-56.61~16.04.1
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname:
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-zesty
** Tags removed: block-proposed
--
You received this bug notification because you
Public bug reported:
I'm new to ubuntu, I am sorry.
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: click-apparmor 0.3.17
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
AptOrdering:
ubuntu-app-launch:amd64:
** Changed in: lxd (Ubuntu)
Status: New => Triaged
** Changed in: lxd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698712
Title:
stale dnsmasq
btw, it is 2.10.95-0ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700232
Title:
aa-logprof ignores dbus access
To manage notifications about this bug go to:
With current version of libgdata Google Contacts is unusable. See this
bug: https://bugzilla.gnome.org/show_bug.cgi?id=780067
** Bug watch added: GNOME Bug Tracker #780067
https://bugzilla.gnome.org/show_bug.cgi?id=780067
--
You received this bug notification because you are a member of
Updated the description with more details, re-assigned to the lshw
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699161
Title:
lshw crashes with SEGV in privileged containers
To manage
** Changed in: lxd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637230
Title:
[2.0] Error calling 'lxd forkstart
To manage notifications about this
An updated lxcfs was pushed to artful and will be included in the next
stable release for LXCFS too.
** Changed in: lxd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: lxd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667444
Title:
Failed to start lxd container because it is already running a start
Hi Meaje,
I see in your log that you installed, removed and reinstalled bacula.
Likely for the issues that you have seen and reported here.
If you purge all old pieces and then reinstall - do you still get no service
running?:
apt remove --purge bacula*
apt install bacula-console-qt bacula
I
** Patch removed: "rsyslog-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900262/+files/rsyslog-trusty.debdiff
** Patch removed: "rsyslog-xenial.debdiff"
this is the PPA that I used to test backported packages:
https://launchpad.net/~alextu/+archive/ubuntu/test
* libmbim - 1.12.2-2ubuntu1oem1:
https://launchpad.net/~alextu/+archive/ubuntu/test/+sourcepub/7925248/+listing-archive-extra
* libqmi - 1.12.6-1ubuntu1oem2:
Hi,
this could as well be a re-occurance of bug 1679435 or similar.
Might I ask via what tool you did the install/upgrade - I only see the
aptdaemon in the log, but it would be interesting which tool was the UI
triggering it?
Also - if that is your issue - you might be able to simply resolve it
** Changed in: oem-priority
Status: Incomplete => Triaged
** Changed in: oem-priority
Importance: Low => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567796
Title:
It is sometimes
** Tags added: virt-fixed-by-2.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1699968
Title:
[FFE] Qemu 2.10 in Artful
To manage notifications about this bug go to:
** Tags added: lp1558946
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567796
Title:
It is sometimes unable to find DELL WWAN module.
To manage notifications about this bug go to:
Thanks Mauricio for the answer.
Thanks for clarifying that it was meant as external documentation!
I don't think one wants to backport the newer concurrent code to Trusty, the
change would be too unstable for an SRU I'd assume. So for now I'll consider
the bug "opinion", that way it can serve as
I'm not sure what upgrade log you are referrin to, this is the matching
output from /var/log/apt/term.log:
Log started: 2017-06-23 13:57:41
(Reading database ... ^M(Reading database ... 5%^M(Reading database ...
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database
...
I agree on this key needing to be available in the/an official Ubuntu
keyring package.
For now, because the original key file is not even accessible via HTTPS,
I am attaching a copy of it here. The file is dated 2016-07-04 16:10,
and has the following SHA{256,512} hashes:
601 - 632 of 632 matches
Mail list logo
