Confirmed in Ubuntu 16.04 LTS. Package `python-paramiko` must still be
installed separately. If it's an optional plug-in then maybe having some
`duplicity-` dummy packages would be useful with better error
messages telling you what to install.
--
You received this bug notification because you
Hi Ryan,
Leonardo will provide the details regarding GPU pass-through here soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541902
Title:
Enable DDW on qemu aiming GPU passthrough performance on
Public bug reported:
Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
when pressed. This is confirmed when running the 'xev' utility and
pressing the 'home' key, xev does associate any events with the key.
tests ran: 65, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-36.55/ms10-34-mcdivittB0-kernel__4.4.0-36.55__2016-08-16_12-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/bugs/1
Junien - yes, that is the one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608854
Title:
[arm64] nova instances can't boot with 3.13.0-92
To manage notifications about this bug go to:
https://bu
Marking fix released according to #19
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
@jibel, thanks for the logs. The sequence of registration events that I
see is:
D/AT ( 2080): AT< +CREG: 1,"0C94","07EEF3DF",2,0,0
D/AT ( 2080): AT< +CREG: 3,"0D16","0540FD26",2,0,0
D/AT ( 2080): AT< +CREG: 1,"0D16","0540FD27",2,0,0
Apparently the phone tries to register to cell 05
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1591411
Title:
systemd-logind must be restarted every ~1000 SSH logins to prevent a
~25 second delay
To manage notifications abo
** Tags added: keyboard
** Description changed:
Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
when pressed. This is confirmed when running the 'xev' utility and
pressing the 'home' key, xev doe
Public bug reported:
ubuntu version - 16.04
uname -a: 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server 5.7.13-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Public bug reported:
curl in Ubuntu 14.0.4 suffers from a bug ("Problem (2) in the Chunked-
Encoded data") introduced in curl 7.35.0
(https://github.com/curl/curl/commit/345891edba32312686e18d8ff185f4476b74e417).
See the corresponding thread on the curl mailing list:
* https://curl.haxx.se/mail/l
The attachment "0005-tostring-2-tobytes.patch" seems to be a patch. If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
Thanks a lot for that work! No objections, commit away but don't upload
yet since we still struggle with the proposed migration...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612767
Title:
Drop a
*** This bug is a duplicate of bug 1568604 ***
https://bugs.launchpad.net/bugs/1568604
Installing xscreensaver and removing light-locker solved the issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
This change was made by a bot.
** Changed in: linux (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/1613696
Title:
Home key on Logitech keyboard not recognize
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Andrea Cimitan (cimi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595235
Title:
Preview widgets with state lose state when device rot
Investigating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594748
Title:
CRYPTO_set_mem_functions() is broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bu
** Changed in: media-hub (Ubuntu)
Assignee: Jim Hodapp (jhodapp) => Alfonso Sanchez-Beato
(alfonsosanchezbeato)
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
** Also affects: indicator-sound (Ubuntu)
Importance: Undecided
Status: New
--
Yo
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix th
Neither overlay working here. I think that the root problem is systemd-
nspawn never mounts the overlay. Please, can you can check it by
defining --overlay and -D to different dirs and then check mounts in
host? Is this behaviour correct?
--
You received this bug notification because you are a me
** Description changed:
Using the Logitech K800 wireless keyboard and on Ubuntu 16.04 with the
4.4.0-34 kernel, the 'home' key is not recognized, ie. nothing happens
when pressed. This is confirmed when running the 'xev' utility and
pressing the 'home' key, xev does associate any events wi
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Chad Miller (cmiller)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611037
Title:
Geolocation in firefox doesn't work anymore
To mana
Public bug reported:
Nautilus 3.20 is having some issues drawing the background image in
yakkety (see attached screenshot of two screens, one above the other):
* On my laptop, it draws a grey vertical partial line from the top of
the screen to approximately three launcher icons height down (in th
Public bug reported:
Enviroment:
current build number: 169
device name: frieza
channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
last update: 2016-08-16 10:23:29
version version: 169
version ubuntu: 20160816
version device: 20160809.0
version custom: 20160805--42-20-vivid
Product: BQ M10 FHD
Still affects Yakkety with GS 3.20 packages. Same workaround works.
** Tags added: yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559576
Title:
Ubuntu GNOME boots to black screen when using
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565772
Title:
[SRU] Allow plugins to decide which username to set on new accounts
To manage notifications about this
** Branch linked: lp:~unity-api-team/indicator-network/lp1598010
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598010
Title:
cellular data switch disabled until SIM selected in settings
To manage
Tested successfully xserver-xorg-video-intel
2:2.99.917+git20160325-1ubuntu1.1 on xubuntu 16.04.1
Made a restart and did several suspends. The mouse cursor reappeared
every time without problems.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug noti
** Description changed:
curl in Ubuntu 14.0.4 suffers from a bug ("Problem (2) in the Chunked-
Encoded data") introduced in curl 7.35.0
(https://github.com/curl/curl/commit/345891edba32312686e18d8ff185f4476b74e417).
See the corresponding thread on the curl mailing list:
* https://cur
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613696
Title:
Several keys on Logitech keyboard not recognized
To manage notifications about this bug go to:
** Changed in: debian
Status: New => 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/255299
Title:
[needs-packaging] Spark - Open Source VoIP and Video cross-platform IM
client
** 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.
https://bugs.launchpad.net/bugs/1613696
Title:
Several keys on Logitech keyboard not recognized
To manage notifica
Forgot to mention: in the kern.log attached above, there are some new
messages with the 4.8.0-rc2 kernel that weren't present with 4.4.0-31:
Aug 15 18:47:06 panzer kernel: [ 310.233191]
[drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] *ERROR*
[CRTC:26:pipe A] flip_done timed out
Thes
Thanks for the suggestion. Unfortunately, it's at least as bad with the
new kernel; maybe worse.
So first of all, "2nd login" doesn't reproduce the issue 100% reliably
after all. I tested one last time with kernel 4.4.0-31, and the same
exact problem occurred again, but on the 3rd, not 2nd login.
Public bug reported:
Juju 2.0 is not quite final, as per the risks and timeline outlined in
the FFe for Xenial, bug 1545913. As such, we intend to release SRU's
post-xenial release. This updates juju to the lastest 2.0 milestone
version.
[SRU Information]
juju-core has a stable release exception
Confirmed the bug exists in the 4.8-rc2 kernel. There are 4 keys not
working 'F5', 'F7', 'F9' and 'Home'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613696
Title:
Several keys on Logitech keyboa
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-68.76/onibi__3.19.0-68.76__2016-08-16_12-41-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/1612550
Title:
l
Public bug reported:
Display arrangement settings are reset after reboot.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity 7.4.0+16.04.20160715-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
NonfreeKernelModules: openafs zfs zunico
@mwhudson, a new version of juju-core-1, 1.25.6, is being uploaded into
yakkety. I agree with the package removal, but given the extended
timeline for juju 2.0, it's possible yakkety retains juju-core-1. Let's
revisit this before FF. I definitely agree with not including it in Z.
--
You received
** Branch linked: lp:~aacid/unity8/splash_spinner_vertical_tweak
** Changed in: unity8 (Ubuntu)
Status: New => In Progress
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Albert Astals Cid (aacid)
** Changed in: unity8 (Ubuntu)
Importance: Undecided => Low
--
You receiv
A patched version has been released upstream so we should backport it
in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581229
Title:
"Started" column not displayed for processes when column is ena
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-68.76~14.04.1/ms10-35-mcdivittB0-kernel__3.19.0-68.76~14.04.1__2016-08-16_12-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.la
Public bug reported:
When I select a wired profile manually and reboot, NetworkManager
instead connects to the profile that has the oldest timestamp. So it's
not connecting to the last used profile, which is troublesome.
On all of our machines (about 500), we define three wired network
profiles,
Hi, please fix this. I had the workaround but lost it after an upgrade
to my system. Now I have to add it again.
Please do something, **anything** to fix this. It is the #1 most
annoying bug in Inkscape, (of which there are many). I think I speak for
many when I say, basically, if there is somethi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: org-mode (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/1613236
Title:
p
right it's on our list but feel free to provide a debdiff if you want to
help with that update
** Changed in: gnome-system-monitor (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
You have been subscribed to a public bug:
Hi,
A new Onboard version has just been released. Here is the relevant part
of the debian/changelog from the debianisation I prepared for yakkety:
onboard (1.2.0+2177-0ppa1~yakkety) yakkety; urgency=medium
* Request for sponsorship for new upstream re
Tested successfully xserver-xorg-video-intel
2:2.99.917+git20160325-1ubuntu1.1 on xubuntu 16.04.1
Had to restart for it to take effect, then tested locking the screen and
suspending - the cursor returned as it should after each.
--
You received this bug notification because you are a member of U
** Changed in: canonical-devices-system-image
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548826
Title:
[devel-proposed] sshd doesn't start when service is enabled
I would have expected it to be removed when I purged all that I had
selected to install.
** Changed in: qemu-kvm (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
This happens when media-hub-server has crashed or become unresponsive in
some way, either because the current player session over dbus has hung
or because the system load is very high for some reason. Can you clear
out the crash files in /var/crash, then the next time you notice this do
the followi
Running "service --status-all | grep qemu" also revealed:
[ - ] qemu-kvm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613451
Title:
"qemu-kvm.service" should be removed upon uninstall
To m
Look, I just did:
sudo apt-get install qemu qemu-kvm virt-manager
To install it, then when I wanted to uninstall it I ran:
sudo apt-get purge qemu qemu-kvm virt-manager
sudo apt-get autoremove
And it seemed to work however after restarting my machine I found that
the qemu-kvm.servic
tests ran: 4, failed: 1;
http://kernel.ubuntu.com/testing/3.19.0-66.74~14.04.1/ms10-34-mcdivittB0-kernel__3.19.0-66.74~14.04.1__2016-08-16_13-57-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: nova (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/1608
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-68.76/dwalin__3.19.0-68.76__2016-08-16_13-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/1612550
Title:
** Branch linked: lp:~jonas-drange/ubuntu-system-settings/wifi-segfault
** Changed in: ubuntu-system-settings (Ubuntu)
Status: New => Fix Released
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: (unassigned) => Jonas G. Drange (jonas-drange)
--
You received this bug notific
** Project changed: onboard => onboard (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613063
Title:
Request for sponsorship for new upstream release (yakkety deb
provided)
To manage noti
http://www.northshoretreeservicesinc.com/retain.php
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/626594
Title:
HDMI Sound Cutting Out
To manage notifications about this bug go to:
https://bugs.lau
I confirm Timo's findings. vivid + upgrade (with udf) works, fresh
xenial doesn't boot. Here is the diff between writable parts of the 2
installation. Left is vivid+upgrade, right is xenial.
** Patch added: "vivid-xenial.diff"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604421/+atta
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 verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
Thanks, I'm sponsoring the update now, you should assign the bug against
the ubuntu package next time though and not the upstream project,
otherwise it not listed as needing sponsoring for ubuntu
** Changed in: onboard (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: onboard (Ubuntu)
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 verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from 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-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days from
** Changed in: unity8 (Ubuntu)
Assignee: Josh Arenson (josharenson) => Albert Astals Cid (aacid)
** Branch linked: lp:~aacid/unity8/pullToRefreshColorChangeWhenNeeded
** Changed in: unity8 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a me
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 verification is not done by 5 working days from t
That was with oxide 1.15.7-0ubuntu1.
With oxide 1.16.7-0ubuntu1 the pages don't even load, and a SIGILL is
received almost immediately:
http://paste.ubuntu.com/23061690/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Description changed:
Enviroment:
current build number: 169
device name: frieza
channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
last update: 2016-08-16 10:23:29
version version: 169
version ubuntu: 20160816
version device: 20160809.0
version custom: 20160805--42-20-vivid
Hi,
Thanks for reporting the issue.
Despite the logging and color of the message, it's usually harmless.
KVM does not provide access to all MSRs and in the case that the
application or OS running is attempting to read or write to MSRs that
KVM does not handle a warning is logged.
0x1c9 is a perf
unsure if that's a greeter or lightdm issue, also under Unity the lock
screen is part of "unity", lightdm/unity-greeter provides the screen
that lists the system users (that you get before first login or if you
switch user)
** Changed in: lightdm (Ubuntu)
Importance: Undecided => Wishlist
--
Tested successfully xserver-xorg-video-intel from xenial proposed.
Tested from suspend.
Tested from lock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568604
Title:
Mouse cursor lost when unlocki
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 verification is not done by 5 working days from 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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
I will see what I can do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581229
Title:
"Started" column not displayed for processes when column is enabled in
settings
To manage notifications abou
Public bug reported:
Quickbooks ╞╞ Tech Support phone number,Quickbooks ╞╞ Payroll
technical support phone number 1 1800 860 9230.Quickbooks ╞╞ Payroll
Tech Support Number Quickbooks ╞╞ Payroll Tech Quickbooks ╞╞ Payroll
tech support, )(1-800-860-9230) Quickbooks ╞╞ Payroll tech support
n
There's nothing allowing us to tell if a finger's already enrolled in
system settings, but maybe this could be added to biometryd?
** Changed in: ubuntu-system-settings (Ubuntu)
Status: New => Incomplete
** Also affects: biometryd (Ubuntu)
Importance: Undecided
Status: New
--
Y
They are supposed to be virtually the same button, and this discrepancy
does indeed sound like a bug. Could you maybe attach some logs to this
report?
.cache/upstart/indicator-network.log
.cache/upstart/application-legacy-ubuntu-system-settings-.log
Thanks!
** Also affects: ubuntu-system-s
*** This bug is a duplicate of bug 1589149 ***
https://bugs.launchpad.net/bugs/1589149
** This bug has been marked a duplicate of bug 1589149
the two Hotspots buttons seem to disagree
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
201 - 300 of 854 matches
Mail list logo
