** 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
I am setting this bug invalid. Nice that you pointed a reason in your
last comment.
** Changed in: aisleriot (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will
I suggest to enable CONFIG_EARLY_PRINTK_USB_XDBC and USB_XHCI_DBGCAP in
Bionic HWE kernels as this will allow to debug via serial console with a
simple USB 3 crossover-cable (aka "USB 3.0 super-speed A-to-A debugging
cable") without the need of a physical RS-232 interface.
--
You received this
*** This bug is a duplicate of bug 1821393 ***
https://bugs.launchpad.net/bugs/1821393
** This bug has been marked a duplicate of bug 1821393
vmware_backdoors will fail on kvm_unit_tests on aws i3.metal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug was fixed in the package virtualbox - 4.3.40-dfsg-
0ubuntu14.04.1
---
virtualbox (4.3.40-dfsg-0ubuntu14.04.1) trusty; urgency=medium
* New upstream release (LP: #1812671)
-- Gianfranco Costamagna Mon, 21 Jan 2019
14:33:14 +0100
--
You received this bug notification
This bug was fixed in the package nautilus - 1:3.26.4-0~ubuntu18.04.4
---
nautilus (1:3.26.4-0~ubuntu18.04.4) bionic; urgency=medium
* d/p/0015-tracker-search-engine-don-t-start-it-if-not-availabl.patch:
- update the patch to fix a logic error in the code which made tracker
The verification of the Stable Release Update for qemu 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
This bug was fixed in the package virtualbox-guest-additions-iso -
4.3.40-0ubuntu1.14.04.1
---
virtualbox-guest-additions-iso (4.3.40-0ubuntu1.14.04.1) trusty; urgency=medium
* New upstream release
(LP: #1812671)
-- Gianfranco Costamagna Mon, 21 Jan 2019
14:33:17 +0100
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws (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/1821393
Title:
Thanks, this should be enough in that case. Releasing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818880
Title:
Deadlock when detaching network interface
To manage notifications about this bug
The verification of the Stable Release Update for virtualbox 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
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.35
---
qemu (1:2.5+dfsg-5ubuntu10.35) xenial; urgency=medium
* Fix deadlock when detaching network interface (LP: #1818880)
Fixed by upstream patch:
- d/p/lp-1818880-rcu-disable-atfork.patch: rcu: completely
This bug was fixed in the package virtualbox-lts-xenial - 4.3.40-dfsg-
0ubuntu1.14.04.1~14.04.1
---
virtualbox-lts-xenial (4.3.40-dfsg-0ubuntu1.14.04.1~14.04.1) trusty;
urgency=medium
* Use lts-xenial stack. Build only guest additions (LP: #1424769).
-- Gianfranco Costamagna
--- Comment From heinz-werner_se...@de.ibm.com 2019-03-25 04:49 EDT---
Description will be reversed mirrored from LP
** Tags added: architecture-s39064 bugnameltc-176335 severity-high
targetmilestone-inin1904
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: python
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348275
Title:
gdb message "Got object file from memory but can't read symbols: File
truncated."
The verification of the Stable Release Update for lldpd 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
Thank you for testing the package, I have promoted it to bionic-updates.
The cosmic counterpart still needs verification though. Could someone
test the 18.10 package so we could get it released as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The verification of the Stable Release Update for nautilus 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
Thank you for the verification! I have released this to bionic-updates
just now. Could you or someone else perform the same validation on a
18.10 system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package indicator-application -
12.10.1+18.04.20190308.1-0ubuntu1
---
indicator-application (12.10.1+18.04.20190308.1-0ubuntu1) bionic; urgency=medium
[ Iain Lane ]
* data/indicator-application.desktop.in: Don't run in ubuntu sessions
(LP: #1819103)
This bug was fixed in the package lldpd - 0.9.9-1ubuntu0.1
---
lldpd (0.9.9-1ubuntu0.1) bionic; urgency=medium
* debian/patches/0002-remove-specific-handling-for-bond.patch: Remove
specific handling for bonds. Thanks to Vincent Bernat
. Closes LP: #1816650.
-- Nishanth
The verification of the Stable Release Update for indicator-application
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
This bug was fixed in the package shadow - 1:4.5-1.1ubuntu2
---
shadow (1:4.5-1.1ubuntu2) disco; urgency=medium
* debian/patches/1013_extrausers_deluser.patch
- add --extrausers option to "userdel" (LP: #1659534)
-- Michael Vogt Fri, 22 Mar 2019 19:32:50
+0100
** Changed
This bug was fixed in the package indicator-application -
12.10.1+18.10.20190308.1-0ubuntu1
---
indicator-application (12.10.1+18.10.20190308.1-0ubuntu1) cosmic; urgency=medium
[ Iain Lane ]
* data/indicator-application.desktop.in: Don't run in ubuntu sessions
(LP: #1819103)
Hi Nicolas,
yeah that isn't easy to fix and at least I didn't find the time to develop
something completely new to cover this yet.
I challenge the statement "Even the default storage pool
/var/lib/libvirt/images is not working", it does and it does well.
And for things that are under the
Please test this kernel:
https://people.canonical.com/~khfeng/lp1821434/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821434
Title:
Panic on suspend/resume Kernel panic - not syncing:
Yeah Michael,
Making just the commit [1] an SRU where needed would have been my thought as
well. But since it is assigned to Mario I wanted to know if he is still (or
again) working on this to avoid doing the work twice - also they might as well
have ended up with discussions somewhere
Just the same issue with my Galaxy C5 PRO, when i'm trying to get
access to Сamera folder inside DCIM folder on the micro-sd card. Both
with Ubuntu 16.04 and Ubuntu 18.04 (default nau managers)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I checked the test instructions and mentioned there that timing is
important as that was inhibiting me at first.
Furthermore I checked through releases and marked the tasks accordingly
(fixed in Disco already, B/C affected).
** Description changed:
[Impact]
When an operator of Juju
Add the following to the same list (for Cosmic)
http://autopkgtest.ubuntu.com/packages/l/linux/cosmic/ppc64el
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711478
Title:
[FTBFS] arm does not
Add the following to the same list (for Cosmic)
http://autopkgtest.ubuntu.com/packages/l/linux/cosmic/ppc64el
--
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:
"numastat" doesn't display
I had a try on kernel 4.15.0-46 in Bionic with efi-pstore module loaded
as pstore backend, but I cannot reproduce that kernel panic. It really
takes more information before one can investigation more into this
issue, so apport runs, even before the panic taking place, is really
mandatory. Please
Looking at the autopkgtest failures and especially the history of them
indicates that the remaining few (most worked well) can be ignored.
Here references to the remaining issues and their history:
http://autopkgtest.ubuntu.com/packages/l/linux/bionic/i386
Looking at the autopkgtest failures and especially the history of them
indicates that the remaining few (most worked well) can be ignored.
Here references to the remaining issues and their history:
http://autopkgtest.ubuntu.com/packages/l/linux/bionic/i386
src:linux-firmware is only accepted into cosmic-proposed but still waiting in
Bionic-unapproved.
AFAIK the current status of "Fix committed" will make it not to be seen by the
SRU Team (at least for similar cases I had in the past).
Therefore to increase the chance to get also the Bionic portion
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => In Progress
** 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
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/1808389
Title:
iwlwifi
After adding the line "/usr/bin/xinit" to gdm3.service I get this in
every boot:
ProblemType: Crash
Architecture: amd64
Date: Mon Mar 25 19:17:11 2019
DistroRelease: Ubuntu 18.04
ExecutablePath: /usr/lib/xorg/Xorg
ExecutableTimestamp: 1543339632
ProcCmdline: /usr/lib/xorg/Xorg :0
...
Did you
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** 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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: Ubuntu Cosmic
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/1808389
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: Ubuntu Bionic
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/1808389
Title:
*** This bug is a duplicate of bug 1808389 ***
https://bugs.launchpad.net/bugs/1808389
Yep, the changes accepted to B/C-unapproved as part of an SRU should be what we
need.
Marking as a Duplicate so that we can test that SRU as well to hopefully
resolve it for all of us.
** This bug has
Its look like the issue is on usage the connect/pair command.
When use a bluetoothctl 'connect' command, the connection is
established, with info:
[CHG] Device ServicesResolved: yes
[CHG] Device Paired: yes
Connection successful
but the [LinkKey] section is not stored in 'info' file.
When
@Paul - you were so active before - thanks for checking the PPAs and all that.
But I still have no NFS server uncoorperative enough to trigger this; Could you
for the (final) SRU verification as asked on the comments #18 and #19 confirm
that this works in your setup with the changes that are in
** Changed in: ubuntu-z-systems
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/1788432
Title:
4.15 s390x kernel BUG at /build/linux-
** Attachment removed: "syslog from installer"
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1821351/+attachment/5248519/+files/mok-syslog
** Attachment added: "syslog from installer"
The error in your log is:
Configurazione di grub-efi-amd64-signed (1.66.20+2.02~beta2-36ubuntu3.20)...
grub-install: errore: /usr/lib/grub/i386-pc/modinfo.sh doesn't exist. Please
specify --target or --directory.
dpkg: errore nell'elaborare il pacchetto grub-efi-amd64-signed (--configure):
il
STACK OVERFLOW: https://stackoverflow.com/questions/55291787/vagrant-no-
guest-ip-was-given-to-the-vagrant-core-nfs-helper
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821083
Title:
Kernel driver
Seems as if this was partially fixed in disco, but when searching for a
name with "firstname lastname", entering the space doesn't allow me to
continue to search, but jumps into the first folder when "firstname"
matches.
Desired result should be that entering a space allows me to continue to
Public bug reported:
Ubuntu 18.04.
Let's create error entry in /etc/crontab:
00 09 * * 4 1 root /usr/local/bin/geoiprenew.sh
restart cron
systemctl restart cron
мар 25 10:29:02 ovpn1 cron[12403]: Error: bad username; while reading
/etc/crontab
мар 25 10:29:02 ovpn1 cron[12403]: (*system*)
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564
Title:
b44 Ethernet driver
Based on a lead from an Arch Linux blog post, I tried adding the i915
module to the initramfs. This could possibly lead to earlier
initialization of the graphics device and it also seems consistent with
the DragonFlyBSD "probe early" patch I linked to in my initial bug
report which may have fixed
Ubuntu-Studio 19.04 QA-Test (live)
I didn't note any strange behavior (I'd left the room briefly and came
back to this)
I was just using xfce4-settings-manager just prior to leaving the room,
and had just changed my window dressing (button layout change then style
to another choice [moheli]).
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xfce4-settings (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/1785143
Public bug reported:
This problem started after upgrading to Ubuntu 19.04. It was not present
with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic
kernel. Ever time during boot there is a null pointer dereference in the
b44 driver for the on-board Ethernet on this Dell Inspiron
Thanks.
Confirm, the tlp not installed.
Mouse: Acer MT1BF
One more thing, the use of bluetoothctl is not resolving issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779289
Title:
[regression]
** Package changed: xorg (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821508
Title:
there is a lagging while i am accessing the software or browing
To manage notifications
ran another QA-test of same ISO on dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati
radeon rv516/x1300/x1550)
i suspended system twice; it resumed as expected. I could not re-create it
(using 'radeon' driver which fits @Theo's notation too)
--
You received this bug notification because you are a
Since support for SDL 1.2 has been removed from QEMU now, can you still
reproduce this issue with the latest version of QEMU and SDL2 ?
** Changed in: qemu
Status: Triaged => Incomplete
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged => Incomplete
** Bug watch removed:
401 - 461 of 461 matches
Mail list logo
