In the following messages I'll try to include log-files for
4.4.0-142-generic kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818148
Title:
virtualbox-guest-x11 does not work with 4.4.0-143-g
We could probably also group this with bug 1817979 (and bug 1788816 and
bug 1816416). Because the function at the top is only an indication of
which generation CPU you are using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Tracking in:
https://errors.ubuntu.com/problem/1bdc3e539949aa164d276979f62ca0282a54fcbd
https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034
** Description changed:
+ https://errors.ubuntu.com/problem/1bdc3e539949aa164d276979f62ca0282a54fcbd
+ https://errors.ubuntu.com/probl
** Summary changed:
- linux-azure-edge: -proposed tracker
+ linux-azure-edge: 4.18.0-1013.13~18.04.1 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818200
Title:
linux-azure-edge
Hello Steve, or anyone else affected,
Accepted resolvconf into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.79ubuntu10.18.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. Se
*** This bug is a duplicate of bug 1818199 ***
https://bugs.launchpad.net/bugs/1818199
** This bug is no longer a duplicate of private bug 1788816
** This bug has been marked a duplicate of private bug 1817979
** This bug is no longer a duplicate of private bug 1817979
** This bug has been ma
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Invalid
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the
Public bug reported:
I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac
Wireless Network Adapter (rev 31).
The menu shows that wireless is off. Turning on the wireless from the
menu does not do anything.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2
*** This bug is a duplicate of bug 1818199 ***
https://bugs.launchpad.net/bugs/1818199
** This bug has been marked a duplicate of bug 1818199
packagekitd crashed with SIGSEGV in __memmove_sse2_unaligned_erms() from
std::char_traits::copy() from std::__cxx11::basic_string, std::allocator >:
*** This bug is a duplicate of bug 1818200 ***
https://bugs.launchpad.net/bugs/1818200
** Tags removed: kernel-sru-backport-of-1814749
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanatio
*** This bug is a duplicate of bug 1818199 ***
https://bugs.launchpad.net/bugs/1818199
** This bug has been marked a duplicate of bug 1818199
packagekitd crashed with SIGSEGV in __memmove_sse2_unaligned_erms() from
std::char_traits::copy() from std::__cxx11::basic_string, std::allocator >:
** Description changed:
- This bug is for tracking the upload package. This
- bug will contain status and testing results related to that upload.
+ This bug will contain status and test results related to a kernel source
+ (or snap) as stated in the title.
- For an explanation of the tasks and
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: packagekit (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/1818199
Title:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
- https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ https://wiki.ubuntu.com/Kernel/ker
** Summary changed:
- packagekitd crashed with SIGSEGV in std::__cxx11::basic_string, std::allocator >::_M_replace()
+ packagekitd crashed with SIGSEGV in __memmove_sse2_unaligned_erms() from
std::char_traits::copy() from std::__cxx11::basic_string, std::allocator >::_S_copy() from
std::__cxx11:
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot
** Information type changed from Private 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/1818059
Title:
packagekitd crashed with SIGSEGV in __strncasecmp_l_avx()
To manage notifications abo
Public bug reported:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 181
*** This bug is a duplicate of bug 1818199 ***
https://bugs.launchpad.net/bugs/1818199
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
packagekit. This problem was most recently seen with package version
1.1.12-1ubuntu1, the problem page a
** Information type changed from Private 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/1818199
Title:
packagekitd crashed with SIGSEGV in __memmove_sse2_unaligned_erms()
from std::char_t
Your configuration looks as if you bridges the guests to an external connected
bridge (br0)
I assume your guests get DHCP from something else on 172.18.232.11/25 and not
from the hosts DNSMASQ is that right?
If that is true please provide logs from the actual dnsserver.
--
You received this bu
Would you have the full journal from the time you started the guest (we
should see it getting a lease from dnsmasq) until the guest complains
about it being lost?
Please attach those from Guest AND Host as I'd like to check if dnsmasq
in the host and/or systemd-networkd in the guest had any.
Best
Ah BTW - to keep things clean please just start one guest until the
issue occurs and then a second as discussed.
Do not start/stop other guests at the time
Do not have other guests up before you start
Do not restart services for all of the time you track this
That also should help to keep the log
Finally if your dhcp server might just be flaky/unresponsive then this is the
correct behavior.
Please fix it on the dhcp server setup then OR follow the discussion at bug
1776013 which leads to
https://www.freedesktop.org/software/systemd/man/systemd.network.html#CriticalConnection=
But really
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818126
Title:
linux-azure: 4.18.0-1013.13~18.04.1 -p
** Description changed:
[Impact]
These are not driven from a direct user experience, but are related to other
developments:
(1) unattended-upgrades could use the never pinning to disable
repositories rather than switching candidates. That would simplify code
quite a bit.
(2) Pac
Uploaded to -unapproved to be as ready as possible and so that other
uploaders see/know there is something in case they modify numactl.
@SRU Team - please wait with acceptance until we see a confirmation by IBM on
the PPA here.
Once that is done I'll set the status accordingly and this is meant t
apport information
** Tags added: apport-collected
** Description changed:
Steps to reproduce:
1. Have 16.04 LTS installed
2. Enable xenial-proposed repository
3. Install `virtualbox-guest-x11` package
Expected results:
* virtualbox-guest-x11 is working as before
Actual resul
Thank you so much, setting verified then
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Oi Edson
I don’t know what you mean by “efficiency test”. But to answer your
question, these are the use cases we were designing for:
- Someone was using Livepatch in 18.04 LTS, then they upgraded to 19.04,
and they skipped past (or forgot) the warning that Livepatch wouldn’t be
available after t
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1818148/+attachment/5242528/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818148
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1818148/+attachment/5242527/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818148
Title:
virt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1818148/+attachment/5242525/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818148
Title:
virtua
@IBM - to unblock this is all on you now, please test the PPA at
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3671
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817258
Title:
"numa
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1818148/+attachment/5242529/+files/ProcCpuinfoMinimal.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: virtualbox (Ubuntu)
Status: New => Confirmed
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1818148/+attachment/5242526/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818148
Thanks for pointing the error. My cups is now printing fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818089
Title:
Cups can not print with "filter failed" error just after ghostcript
update
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818128
Title:
linux-azure: 4.18.0-1013.13 -proposed
Finally got there. Although ran out of time to think about a general
redesign that could be upstreamed. Instead I've just proposed a fix
specific to disco:
https://code.launchpad.net/~vanvugt/ubuntu/+source/gnome-shell/+git
/gnome-shell/+merge/363831
--
You received this bug notification because
** Also affects: apt (Ubuntu Trusty)
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/1815760
Title:
Additional hooks for update
To manage notifications abo
** Description changed:
[Impact]
These are not driven from a direct user experience, but are related to other
developments:
(1) unattended-upgrades could use the never pinning to disable
repositories rather than switching candidates. That would simplify code
quite a bit.
(2) Pac
** Description changed:
[Impact]
- json hooks ending with EPIPE on first read fail, but should simply do
nothing.This causes spurious failures of uninstalled hooks.
+ json hooks ending with EPIPE on first read fail, but should simply do
nothing. This causes spurious failures of uninstalled hoo
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
First I tried cosmic amd64 on Thinkpad T480s, upgraded libvirt0 to
4.6.0-2ubuntu3.3. It could run virt-manager successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811198
Title:
virt-manager
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/363831
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813119
Title:
In Ubuntu 19.
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Cosmic)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
There is (always) hope :-)
Please try the build at PPA [1] if it resolves your apparmor issues.
If it is good I'll submit upstream, if not we will polish the rules as needed.
Furthermore the removal of the assert might in fact be just what you need.
As I expect the remaining error you hit might a
** Description changed:
[Impact]
json hooks ending with EPIPE on first read fail, but should simply do
nothing.This causes spurious failures of uninstalled hooks.
[Test case]
- TODO
+ Cannot generate one. This was discovered by snapd ci, but I did not find a
reproducer yet.
+
+ FWIW, t
** Description changed:
[Impact]
Dpkg::Post-Invoke is run only when dpkg had to be run. We'd like to be able
to show some extra output even if no changes had been made. Imagine "the user
disabled the security repo, and does not get any updates shown scenario" - we'd
like to be able to tell
** Changed in: linux (Ubuntu)
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/1788730
Title:
TP-LINK TG-3468 network card not recognized correctly
To manage n
Looks like this has been fixed.
/tmp$ for i in {1..10}; do curl -s -I
http://security.ubuntu.com/ubuntu/pool/main/libg/libgd2/libgd3_2.1.1-4ubuntu0.16.04.11_amd64.deb
| grep HTTP; done
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
HTTP/1.1 200 OK
Do you know when a fix for linux-xenial will be available? Looks like
that's the only one remaining.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802021
Title:
[Hyper-V] srcu: Lock srcu_data struc
Just removing the assert (somewhat unsurprisingly) isn't enough to make
it work.
(Additional apparmor rules)
/proc/modules r,
/proc/driver/nvidia/params r,
/etc/glvnd/egl_vendor.d/{,*} r,
/usr/share/egl/egl_external_platform.d/ r,
/usr/share/egl/egl_external_platform.d/** r,
/sys/devic
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
Public bug reported:
安装别的库总是出现这个错误
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: redis-server 2:3.0.6-1ubuntu0.3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Fri Mar 1 16:10:27
** Tags added: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813119
Title:
In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly
during the login animation
To man
401 - 457 of 457 matches
Mail list logo
