This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
** Description changed:
+ Test Case
+ -
+ 1) install apt-xapian-index on a yakkety system
+ 2) observe python3-xapian1.3 is installed too
+ 3) edit /etc/apt/sources.list to zesty
+ 4) run apt-get update
+ 5) run apt-get install apt-xapian-index
+ 6) observe python3-xapian1.3 is still insta
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/archytas__4.8.0-48.51__2017-04-13_16-10-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682034
T
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
@Andre,
I believe what happens here is filed at LP: #1678184.
Kernel parameter 'nvme_core.default_ps_max_latency_us=0' can workaround the
issue as a temporary fix.
Please also try other value I suggested in comment #6 in LP: #1678184.
--
You received this bug notification because you are a memb
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verifi
Public bug reported:
Using the standard Ubuntu 16.10 installation, and installing GNOME in
parallel, there is a confusing problem for users continuing to use
Unity.
In Unity, searching for *setting* – or for Germans *Eins* –, and hitting
enter, or selecting the first match, *gnome-control-center*
Public bug reported:
because pitti says so
cherrypick from debian
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-35-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_16-20-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-34-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_16-20-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
tests ran: 37, failed: 4;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/rumford__4.8.0-48.51__2017-04-13_15-50-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682034
Ti
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/gonzo__4.8.0-48.51__2017-04-13_15-38-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682034
Titl
Hello dino99, or anyone else affected,
Accepted apt-xapian-index into zesty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/apt-xapian-
index/0.47ubuntu13 in a few hours, and then in the -proposed repository.
Please help us by testing this new package
I think comment #9 was caused by either an error in some script or
incorrect reference.
** Tags removed: verification-needed-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678009
Title:
Fix C
I've been using the script from #57 in 16.04 & 16.10, but in 17.04 I
switched to GNOME and now the script fails since it cannot find an a2dp
sink. After some research, it seems that the problem is with GDM
starting its own pulseaudio process
(https://bbs.archlinux.org/viewtopic.php?pid=1526658#p152
Public bug reported:
This is my first time installing this system, however i have not had the best
of luck.
I was installing it on a WD 750GB HDD, however it failed to install grub with
the message
saying something along the lines of " Unable to install grub bootloader, the
system will not boot
** Also affects: ubuntu-gnome
Importance: Undecided
Status: New
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-control-center (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-gnome
Importance: Undecided => Medium
**
I installed dkms from zesty-proposed and then upgraded from Y to Z.
bdmurray@clean-yakkety-amd64:~$ do-release-upgrade -d
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [836 B]
Get:2 Upgrade tool [1,268 kB]
Fetched 1,269 kB in 0s (0 B/s)
authenticate 'zesty.tar.gz' against 'zesty.t
Also, after using the dkms from proposed, after update I see:
ubuntu@yakkety2:~$ grep "Building for" /var/log/dist-upgrade/apt-term.log
Building for 4.8.0-45-generic 4.10.0-19-generic
Building for 4.8.0-45-generic 4.10.0-19-generic
Building for architecture x86_64
** Tags removed: verification-n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-sound (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/1663906
Tit
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Zesty)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
Update Ubuntu MATE
ProblemType: Package
DistroRelease: Debian 9
Package: libjpeg8 8c-2ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Thu Apr 13 18:47:15 2017
Depen
The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
This bug was fixed in the package dkms - 2.3-3ubuntu1
---
dkms (2.3-3ubuntu1) zesty; urgency=medium
* 0013-postinst-Fix-newest-kernel-detection.patch: dkms_common.postinst: We
were passing a list of kernels to get_newest_kernel(), when it expected a
single kernel as its fir
tested on xenial with the -proposed 4.4.0-74-generic kernel, ran 16
xattr stressors for 5 minutes, no failure, passed.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Hi,
kernel works fine with the patch on IPv6.
Thanks
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605494
Title:
SOLUTION for me was:
edit:
/etc/pulse/daemon.conf
find change or add the following line
resample-method =
change to:
resample-method = src-sinc-best-quality
**remember to remove the hash or colon from the begining of the line to
enable that line**
reboot for changes to take effect
--
You rec
Could you try the 4.10 mainline build and see if the bug exists there?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/
If that one fails for you we have a straight-forward path for bisecting
to find out what fixed the issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomple
For reference this is the daily build which is reported to resolve the
issues:
git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack
cod/tip/daily/2017-04-13 (b9b3322f13f350587f17f0a76f008830e3a420d3)
--
You received this bug notification because you are a member
Shouldn't we also fix yakkety and company?
Are we sure upgrade will use the new dkms?
(probably yes, because all postinst are done after all package upgrade,
right?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
tested on Yakkety with the -proposed 4.8.0-48-geneirc kernel, ran 16
xattr stressors for 5 minutes, no failure, passed.
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Ok, I'm testing one by one and as soon as I get results I'm posting it here.
Thank you!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682331
Title:
Cannot get lowest brightness with kernel 4.4.0-5
Hello, I tested the patch using a testing kernel from Joseph Salisbury
and it completely fixed the bug. Later, I was unable to boot to 4.8.0-42
which came with updates. I do not know why. I have never before
experienced such a problem.
What can I do to try it again better?
--
You received this b
Sweet, thanks adconrad!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681566
Title:
nvidia-375 DKMS module not recompiled on upgrade to 17.04
To manage notifications about this bug go to:
https://
Adding some miscellaneous data points.
I'm still unable to reproduce this outside of a lgw01 compute node that
Laney set up for me, running xenial with qemu 1:2.5+dfsg-5ubuntu10.10
and linux 4.4.0-72. It doesn't happen on every host. I'm still
experimenting to see if I can reproduce this on some h
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633905
Title:
xenial to yakkety upgrade : "Activated service 'ca.desrt.dconf'
failed"
To manage notifications about this bug go
If you have a system currently running yakkety or that upgraded to you
yakkety you could look to see how many kernels the modules were built
for e.g. here's a yakkety system of mine:
[ 9:05AM 10517 ] [ bdmurray@impulse:/tmp ]
$ grep "Building for" /var/log/dist-upgrade/apt-term.log
Building for
Public bug reported:
this error comes up after I rebooted on initial setup
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libaprutil1:amd64 1.5.4-1build1
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
NonfreeKernelModules: nvidia_uv
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51~16.04.1-generic/fozzie__4.8.0-48.51~16.04.1__2017-04-13_16-28-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/hainzel__4.8.0-48.51__2017-04-13_16-26-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682034
Ti
tests ran: 14, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-35-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_16-50-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
tests ran: 14, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/ms10-34-mcdivittB0-kernel__4.8.0-48.51__2017-04-13_16-50-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Some more debug info:
$ sudo dmidecode -t 21
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Handle 0x0035, DMI type 21, 7 bytes
Built-in Pointing Device
Type: Track Point
Interface: PS/2
Buttons: 3
Handle 0x0036, DMI type 21, 7 bytes
Built-in Point
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
mate-applets. This problem was most recently seen with package version
1.18.1-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/a20181a3412b7fb1765cfe5409b88c3a1326e516
contains mo
** Changed in: chromium-browser (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/1676368
Title:
Corrupted package, impossible to install
To manage notific
tests ran: 19, failed: 1;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/archytas__4.8.0-48.51__2017-04-13_16-38-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682034
T
Public bug reported:
1) click on activities
2) type 'b' for blender (or anything really)
3) click on blender -> add to favorites
4) "Blender has been added to favorites"
nothing happens.
I can go back to look at the favorites pane and...nothing has changed.
Similarly
click on firefox in my
I've installed the v4.10 mainline.
painter@merlin:~$ uname -a
Linux merlin 4.10.0-041000-generic #201702191831 SMP Sun Feb 19 23:33:19 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
Will monitor and see if there are any more system crashes. I will update
in a few hours.
Thanks!
--
You received this
Public bug reported:
1.
> xkill
expected result:
a) output: "Select the window whose client you wish to kill with button 1..."
b) pointer turns to an X
c) you can click on a window
d) that window's process gets killed
what actually happens
a) output: "Select the window whose client you wish to
Public bug reported:
This issue will effectively be a regression in desktop usage once Ubuntu
switches from Unity to Gnome Shell. Gnome Shell does not work well with
multiple monitors unlike every other desktop environment except Budgie,
which is switching away from GTK/Gnome to Qt with Budgie 11
Public bug reported:
--EOF--
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: sudo 1.8.16-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Wed Apr 12 21:26:08 2017
ErrorMessage
This looks like it would be a "duplicate" of bug 1682499; we should
disable DNSSEC by default.
Can you please verify if setting DNSSEC=off fixes your issue?
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of U
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/gonzo__4.8.0-48.51__2017-04-13_16-50-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682034
Titl
The patch works around the issue in apt, but isn't the underlying cause
the fact that /etc/apt/apt.conf.d/50unattended-upgrades was a confffile
in ~0.82.1ubuntu2.3, and is no longer a conffile in ~0.90ubuntu0.3, yet
the typical pattern for obsoleting a conffile wasn't performed? So even
an unchange
Public bug reported:
>From the Gnome Help >> Tips & Tricks >> Determine which version of GNOME
is running
You can determine the version of GNOME that is running on your system by going
to the Details panel in Settings.
Open the Activities overview and start typing Details.
Click on Details to op
dmesg also tells us that psmouse failed to retrieve extended button
data:
[...]
[ 5276.513617] psmouse serio7: trackpoint: failed to get extended button data
[ 5280.377455] psmouse serio7: trackpoint: IBM TrackPoint firmware: 0x0e,
buttons: 0/0
[...]
--
You received this bug notification becaus
I don't know, but it certainly is right to ignore the file in apt.
** Changed in: apt (Ubuntu)
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/1639558
Title
So, if old prerm is failing on a bad unit, then new prerm is attempted.
New prerm should be written in a way that it skips/ignores the failure.
** Changed in: cups (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: cups (Ubuntu)
Status: Fix Released => Confir
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682035
Title:
package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade:
package li
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682237
Title:
package humanity-icon-theme 0.6.10 [modified:
usr/share/icons/Humanity/embl
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678310
Title:
package nginx-core 1.10.3-0ubuntu0.16.10.1 failed to install/upgrade:
subpr
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681479
Title:
package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade:
tent
Builds of ubuntu-server-live look good using -proposed for both amd64
and i386; the initrd and kernel artifacts are now built.
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/zesty/ubuntu-
server-live/+build/94572
Verification-done.
** Tags removed: verification-needed
** Tags added: verifi
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681038
Title:
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
installed
tested on Trusty with the -proposed 3.13.0-117-generic and
4.4.0-74-generic #95~14.04.1 HWE kernel, ran 16 xattr stressors for 5
minutes, no failure, passed.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are
To verify this... I verified there were no obvious regressions by
(lxc-proposed-snapshot is
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot
It publishes an image to lxd with proposed enabled and cloud-init upgraded.)
$ release=xenial
$ ref=$release-pro
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681679
Title:
package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is
in a
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681494
Title:
package linux-headers-4.8.0-46 4.8.0-46.49~16.04.1 failed to
install/upgrad
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mrtg-rrd (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/1618800
Title:
D
Patch worked 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/1618800
Title:
Does not work on Ubuntu 16.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (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/1682499
Title:
di
I disabled /org/gnome/desktop/peripherals/touchpad/tap-to-click before
reporting here. I can confirm that it has no effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682171
Title:
No way to dis
*** This bug is a duplicate of bug 1682499 ***
https://bugs.launchpad.net/bugs/1682499
Yes, I put 'DNSSEC=off' in /etc/systemd/resolved.conf yesterday evening,
and it is working.
** This bug has been marked a duplicate of bug 1682499
disable dnssec
--
You received this bug notification b
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/hainzel__4.8.0-48.51__2017-04-13_17-36-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682034
Ti
To verify this... I verified there were no obvious regressions by the
following.
(lxc-proposed-snapshot is
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot
It publishes an image to lxd with proposed enabled and cloud-init upgraded.)
$ for r in xenial yak
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/rumford__4.8.0-48.51__2017-04-13_17-27-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682034
Ti
The apt-xapian-index change is insufficient as python3-xapian1.3 wasn't
removed first.
Selecting previously unselected package python3-xapian.
Preparing to unpack .../python3-xapian_1.4.3-1_amd64.deb ...
Unpacking python3-xapian (1.4.3-1) ...
dpkg: error processing archive
/var/cache/apt/archives
Public bug reported:
I was running Ubuntu 16.04 and I used xbacklight frequently. Upon
upgrading to 17.04 release candidate as of 13th of April, xbacklight
stopped to work.
$ xbacklight -set 10
No outputs have backlight property
# lshw
foobar
description: Laptop
product: Latitude 3330 (
Public bug reported:
I get this error whenever I start or reboot the pc
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date:
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
1 - 100 of 847 matches
Mail list logo
