Public bug reported:
On my machine, after booting I always have to type in my password,
allthough I set "settings -> users -> auto login".
The same happens after resume from suspend, allthough I set "privacy ->
auto screen lock" to "disabled". In both cases the screen attached
appears.
My system
Public bug reported:
On my machine, after booting I always have to type in my password,
allthough I set "settings -> users -> auto login".
The same happens after resume from suspend, allthough I set "privacy ->
auto screen lock" to "disabled". In both cases the screen attached
appears.
My system
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-78.99-lowlatency/archytas__4.4.0-78.99__2017-05-03_05-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/1686645
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/hainzel__4.8.0-52.55__2017-05-03_06-04-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/1686976
Ti
Can you try again with http://people.canonical.com/~khfeng/lp1686592-2/?
If the issue persists, please attach dmesg here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686592
Title:
APST quirk nee
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/pepe__4.8.0-52.55__2017-05-03_06-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.net/bugs/1686976
Title
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.10.0-21.23-generic/kernel03__4.10.0-21.23__2017-05-03_06-43-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/1686414
This bug was fixed in the package duplicity - 0.7.11-1ubuntu1
---
duplicity (0.7.11-1ubuntu1) artful; urgency=low
* Merge from Debian unstable (LP: #1669616). Remaining changes:
- Enable tests during build and add a simple dep8 test
- Drop Recommends for various backends to
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-78.99~14.04.2-generic/ms10-34-mcdivittB0-kernel__4.4.0-78.99~14.04.2__2017-05-03_06-56-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
After building vanilla kernel 4.10.13 with the patch #5 jumbo frames is
possible on ovs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685742
Title:
MTU 9000 not possible on openvswitch bridge
To
*** This bug is a duplicate of bug 1672157 ***
https://bugs.launchpad.net/bugs/1672157
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1672157, so is being marked as such.
*** This bug is a duplicate of bug 1672157 ***
https://bugs.launchpad.net/bugs/1672157
Public bug reported:
running on Lubuntu
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: mouseemu 0.16-0ubuntu9
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-gene
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55~16.04.1-generic/fozzie__4.8.0-52.55~16.04.1__2017-05-03_06-58-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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mouseemu (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/1672157
Title:
p
** 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/1672157
Title:
package mouseemu 0.16-0ubuntu9 failed to install/upgrade: subprocess
installed post-installation script returned e
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55~16.04.1-generic/amaura__4.8.0-52.55~16.04.1__2017-05-03_07-00-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: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/gonzo__4.8.0-52.55__2017-05-03_06-30-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/1686976
Titl
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/pepe__4.8.0-52.55__2017-05-03_07-17-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/1686976
Title
Public bug reported:
My W540 can not detect my external screen when I arrive at work after my
laptop have been used at home with no external screen and suspended on
the way to work. Sometimes it does detect it. Sometimes I can un-dock
and dock again and it works. Sometimes it never works when I am
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.10.0-21.23-generic/rizzo__4.10.0-21.23__2017-05-03_06-31-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/1686414
Ti
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-78.99~14.04.2-generic/ms10-34-mcdivittB0-kernel__4.4.0-78.99~14.04.2__2017-05-03_07-23-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I am running Ubuntu Zesty 17.04 and have this flickering issue. The
above fix of changing the theme does nothing to correct the issue. I was
using 16.10 prior and did not have this problem. Only after the upgrade
did this start to happen. Is there any update on a possible fix for
this?
--
You rec
Public bug reported:
dpkg-query: atención: falta el fichero de lista de ficheros del paquete
`libimage-magick-perl', se supondrá que el paquete no tiene ningún fichero
actualmente instalado
dpkg-maintscript-helper: error: directory '/usr/share/doc/libimage-magick-perl'
contains files not owned
*** This bug is a duplicate of bug 1574278 ***
https://bugs.launchpad.net/bugs/1574278
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: abiword (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubun
same error with Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300533
Title:
Support for cores revisions 0x17 and 0x18 disabled by module param
allhwsupport=0. Try b43.allhwsupport=1
** Also affects: inkscape
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/1687817
Title:
Inkscape 0.92.1-1 always reverts display units to px
To manage not
My current situation is matching Johns comment, since the Host is Xenial
in my case all "would" run just fine - and it does seem to work, except
of the fact that while loading fine due to the postinst loading them on
reboot they are skipped.
On a not representative scan on my system in /var/lib/dp
tests ran: 6, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-78.99-lowlatency/archytas__4.4.0-78.99__2017-05-03_07-11-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/1686645
I have a fully updated Ubuntu 17.04 and when I connect to VPN
/var/run/NetworkManager/resolv.conf does not get updated with DNS. Any
fix soon?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Tit
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/gonzo__4.8.0-52.55__2017-05-03_07-37-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/1686976
Titl
Additionally (due to personal experience) it might be worth checking whether
linux-image-extra-4.4.0-77* got installed. Not sure how that could happen but
it seems update-manager offered to install linux-image and linux-image-signed
without any of the other packages which should be installed at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (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/1687742
Tit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openssl (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/1623638
Title:
pa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: debconf (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/1623638
Title:
pa
I did some testing, it affects PPTP, but does not seem to affect
OpenVPN.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
name resolution (dnsmasq) fails to send queries out after
sus
tests ran: 34, failed: 3;
http://kernel.ubuntu.com/testing/4.8.0-52.55~16.04.1-generic/amaura__4.8.0-52.55~16.04.1__2017-05-03_07-16-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: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55~16.04.1-generic/secchi__4.8.0-52.55~16.04.1__2017-05-03_06-34-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
@exander77 this bug is specifically about a failure after
suspend/resume. If your issue does not relate to suspend/resume it is a
different bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639776
T
Thanks.
I can still reproduce the issue with Linux kernel 4.10.0-20-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681904
Title:
WLan not working after Kernel update (HWE)
To manage notif
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/rumford__4.8.0-52.55__2017-05-03_07-00-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/1686976
Ti
@colin-law That's bullshit, #1671606 was closed as duplicated of this:
DNS server from vpn connection is not being used after network-manager upgrade
to 1.2.6-0ubuntu0.16.04.1
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606
--
You received this bug notification because you
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/hainzel__4.8.0-52.55__2017-05-03_07-12-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/1686976
Ti
I have the same issue, no Ethernet, connection and low display
resolution which I was unable to change (1024 × 768 I think). Rebooting
on .75 kernel resolved the issues. Attached report as suggested in reply
#4 (this is done after rebooting to the .75 kernel, if it makes a
difference I can reboot t
G'day Brian! Yes, the theme workaround began not working for me with
17.04. Yes, the problem can come and go with any changes to the
hardware, kernel, X server, or libraries. There is a fix that makes the
situation a lot better, see my post last week on the upstream bug
https://bugzilla.abisourc
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55~16.04.1-generic/amaura__4.8.0-52.55~16.04.1__2017-05-03_07-55-00/results-index.html
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
You received this bug notification because
I have similar issues with 4.4.0-77-generic, except that after the
update no hardware is recognized at all. Ubuntu doesn't see my monitors,
wired network card, etc. While booting with 4.4.0-75-generic has no such
problems.
--
You received this bug notification because you are a member of Ubuntu
B
@mbrennwa that seems likely (display issue) There was a similar bug a
while ago that was a rendering issue:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-
accounts/+bug/1309247
Also, there have been recent updates to Gnome's Javascript engine iirc
--
You received this bug notification b
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-78.99-lowlatency/michael__4.4.0-78.99__2017-05-03_07-01-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/1686645
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-78.99-lowlatency/archytas__4.4.0-78.99__2017-05-03_07-58-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/1686645
tests ran: 19, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55~16.04.1-generic/fozzie__4.8.0-52.55~16.04.1__2017-05-03_07-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.net/b
Same happened to me. For whatever reason both Intel Microcode and nvidia
proprietary drivers were not used after upgrade from 16.10.
The installation of the nvidia proprietary drivers (alone) didn't solve
the problem. But now, after additionally installing microcodes it seems
to work.
I will Info
Philip, the 'not working' one or the 'way too fast' one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657553
Title:
Laptop stick and touchpad problems after linux 4.4 update
To manage notificatio
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/hainzel__4.8.0-52.55__2017-05-03_08-11-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/1686976
Ti
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pasystray (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/1676069
Title:
I guess it's better not to load pinctrl_amd until AMD & Gigabyte solve
the issue.
What's the name of the board do you guys have?
You can get the name via `cat /sys/class/dmi/id/board_name`.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/pepe__4.8.0-52.55__2017-05-03_08-04-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/1686976
Title
tests ran: 6, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55~16.04.1-generic/secchi__4.8.0-52.55~16.04.1__2017-05-03_08-03-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
@Thomas, Jacob,
and "dpkg -l|grep 4.4.0-77", does that show and linux-image-extra or
not? If not, try the manual update I described in comment #12 from the
-75 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sgt-launcher (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/1670610
Title:
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55~16.04.1-generic/amaura__4.8.0-52.55~16.04.1__2017-05-03_08-14-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
Karl,
Please retest with a newer (supported) version of Ubuntu:
https://wiki.ubuntu.com/Releases
** Changed in: bluez (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Public bug reported:
The problem happens when changing the ring size of a mlx5_core interface that
is part of a LACP bond.
[268312.721076] mlx5_core :42:00.1 enp66s0f1: mlx5e_update_carrier:143:
Link up
[268312.721940] mlx5_core :42:00.1 enp66s0f1: speed changed to 0 for port
enp66s0f
I think I found a workaround. I noticed the traceback I saw in syslog
happened a lot before I tried to log back in and I deduced it happened
when notification were displayed on my locked screen.
Since I disabled notifications on my lock screen (Notifications >
Notifications on lock screen) I haven
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.10.0-21.23-generic/rizzo__4.10.0-21.23__2017-05-03_07-51-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/1686414
Ti
~$ uname -a
Linux blabla 4.10.0-21-generic #23~lp1653456+asus SMP Tue May 2 17:52:56 CST
2017 x86_64 x86_64 x86_64 GNU/Linux
Unfortunately it doesn't work. I tried both with and without USB mouse
connected, I tried few times to disable/enable the touchpad within System
settings - but nothing ch
@exander77 there is no need for personal abuse here. In that case the
description of this bug should have been updated to include that.
However I see there is debate on that bug about whether it is fixed by
the version of dnsmasq which fixes this bug. If not then it is
definitely a different bug. I
> It is not a setting, it's where the designers chose to place them.
Then you should consider replacing your designers with someone who
understands the term "user experience". A bit harsh, I know, but so is
your statement "This will not change".
I have used 16.04LTS with unity now for some weeks
Thank you for reporting this bug to Ubuntu. Ubuntu 9.10 (karmic) reached EOL on
April 30, 2011.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confirmed =
Thank you for reporting this bug to Ubuntu. Ubuntu 9.10 (karmic) reached EOL on
April 30, 2011.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confirmed =
@Stefan thanks, that did indeed solve the problem for me. I thought I
checked that it was installed before I reported the issue but I must've
misread.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-78.99~14.04.2-generic/amaura__4.4.0-78.99~14.04.2__2017-05-03_08-42-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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: 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/1687653
Title:
QEMU-KVM / d
cat /sys/class/dmi/id/board_name
gives me:
AB350M-HD3-CF
Yes, it is an Gigabyte AB350m HD3 that I own.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360
Title:
System doesn't boot properly on Gi
Perttu,
Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached
EOL on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confir
Jeff,
Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached
EOL on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confirme
Yotam,
Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached
EOL on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confirm
Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached EOL on
May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Confirmed => I
co0lingFir3,
Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached
EOL on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: gnome-bluetooth (Ubuntu)
vava,
Thank you for reporting this bug to Ubuntu. Ubuntu 10.10 (maverick)
reached EOL on April 10, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Co
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/rumford__4.8.0-52.55__2017-05-03_08-13-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/1686976
Ti
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1687877
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a commen
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55~16.04.1-generic/secchi__4.8.0-52.55~16.04.1__2017-05-03_08-48-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
Vojtěch,
Thank you for reporting this bug to Ubuntu. Ubuntu 11.04 (natty) reached
end-of-life on October 28, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
The fix mentioned in vorlon's branch does not appear in the current
bluez source yet. Do we need it or was another solution found?
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/gonzo__4.8.0-52.55__2017-05-03_08-29-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/1686976
Titl
tests ran: 64, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/hainzel__4.8.0-52.55__2017-05-03_08-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/1686976
Ti
Probably because of this:
[4.370218] i2c-ELAN1203:00 supply vcc not found, using dummy regulator
Do you see anything under /sys/class/regulator?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16534
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-78.99-lowlatency/daedalus__4.4.0-78.99__2017-05-03_09-05-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/1686645
tests ran: 141, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-78.99-lowlatency/archytas__4.4.0-78.99__2017-05-03_08-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/bugs/1686645
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.4.0-78.99~14.04.2-generic/ms10-34-mcdivittB0-kernel__4.4.0-78.99~14.04.2__2017-05-03_07-52-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
tests ran: 34, failed: 3;
http://kernel.ubuntu.com/testing/4.4.0-78.99-lowlatency/michael__4.4.0-78.99__2017-05-03_08-24-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/1686645
I realized we carry this as Delta and there was no Debian report yet, I
opened one and linked it up here.
** Bug watch added: Debian Bug tracker #861727
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861727
** Also affects: ntp (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Co
Lunarts,
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Ivan,
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Sta
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
Status: Co
Thank you for reporting this bug to Ubuntu. Ubuntu 12.10 (quantal)
reached end-of-life on May 16, 2014. And Ubuntu 11.04 (natty) reached
end-of-life on October 28, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest versi
Varga,
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
St
Damian,
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise)
reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to the latest version and re-test.
** Changed in: bluez (Ubuntu)
S
tests ran: 33, failed: 3;
http://kernel.ubuntu.com/testing/4.4.0-78.99~14.04.2-generic/amaura__4.4.0-78.99~14.04.2__2017-05-03_08-55-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
1 - 100 of 932 matches
Mail list logo
