** Description changed:
[Impact]
- TBD
+ dnsmasq will fail to respond on network devices that weren't up when its
+ service started, thus not binding as expected.
[Test Case]
TBD
[Regression Potential]
The fix is just configuring the order of service startup, so is unlikely to
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
The version of xfce4-settings in the proposed pocket of Cosmic that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of
The version of xfce4-settings in the proposed pocket of Cosmic that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of
Hello all,
apologies if am commenting incorrectly, my first post here
could anyone confirm if the fix mentioned in #1 will be backported to systemd
in bionic ?
also any time frame on the completion of the activity ?
Thank you for your time
--
You received this bug notification because you are
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
The version of xfce4-settings in the proposed pocket of Cosmic that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Tags removed: verification-needed-cosmic
** Changed in:
The version of python-tornado in the proposed pocket of Cosmic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification
** Changed in: linux (Ubuntu Bionic)
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/1836715
Title:
selftests: Remove broken Power9 paste tests and fix
The version of lldpd in the proposed pocket of Cosmic that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
** Tags removed: verification-needed-cosmic
--
You received this bug
The version of python-tornado in the proposed pocket of Cosmic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
** Tags removed: verification-needed-cosmic
The version of lldpd in the proposed pocket of Cosmic that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Changing the cosmic entry to Invalid since it reached it's EOL on July, 18th
2019 (last week).
With that change the entire ticket is now Fix Released.
** Changed in: linux (Ubuntu Cosmic)
Status: Fix Committed => Invalid
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix
The version of python-tornado in the proposed pocket of Cosmic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
** Tags removed: verification-needed
--
Same issue.
After these two command.
sudo apt update
sudo apt -f install
Errors were encountered while processing:
pgadmin4-apache2
E: Sub-process /usr/bin/dpkg returned an error code (1)
** Attachment added: "Screenshot from 2019-07-23 11-03-32.png"
The version of lldpd in the proposed pocket of Cosmic that was purported
to fix this bug report has been removed because the bugs that were to be
fixed by the upload were not verified in a timely (105 days) fashion.
** Changed in: lldpd (Ubuntu Cosmic)
Status: Fix Committed => Won't Fix
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
** Changed in: linux (Ubuntu Disco)
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/1836806
Title:
Two crashes on raid0 error path (during a member device
** Changed in: linux (Ubuntu Bionic)
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/1836816
Title:
Fix nf_conntrack races when dealing with same origin
Thomas, if it's PSR related, please test the kernel here:
https://bugzilla.freedesktop.org/show_bug.cgi?id=110511#c25
** Bug watch added: freedesktop.org Bugzilla #110511
https://bugs.freedesktop.org/show_bug.cgi?id=110511
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu Bionic)
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/1836971
Title:
sched: Prevent CPU lockups when task groups take longer
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
Examining the information you have given us, this does not appear to be
a bug report so we are closing it and converting it to a question in the
support tracker. We understand the difficulties you are facing,
** Tags added: s390x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837073
Title:
linux 5.2.0-8.9 disabled backlight on s390x.
To manage notifications about this bug go to:
** Description changed:
- The ROM state is represented by the 24 LSB bits in the ROM status
- register, so the mask should be 0xff instead of 0xf.
+
+ [Impact]
+ Intel notified me that they found a critical issue, and this is the
+ fix for this issue.
+
+ [Fix]
+ correct the status register
[Expired for console-setup (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: console-setup (Ubuntu)
Status: Incomplete => Expired
--
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: tracker-miners (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/1750698
[Expired for mysql-5.7 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-5.7 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830029
[Expired for cloud-init (Ubuntu) because there has been no activity for
60 days.]
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: ubuntu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830283
Title:
Xorg
Public bug reported:
When I tried upgrading my Ubuntu from 18.10 to 19.04 I encountered this
issue...Can you please help me out???
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-release-upgrader-core 1:18.10.11.9
ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
Public bug reported:
The ROM state is represented by the 24 LSB bits in the ROM status
register, so the mask should be 0xff instead of 0xf.
** Affects: linux-oem-osp1 (Ubuntu)
Importance: Undecided
Assignee: Hui Wang (hui.wang)
Status: New
--
You received this bug
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
great post. thanks to you.
http://www.winmilliongame.com
http://www.gtagame100.com
http://www.subway-game.com
http://www.zumagame100.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274167
Title:
This is blocking the ubuntu_zfs test as well.
** Tags added: ubuntu-ltp-syscalls ubuntu-zfs-fstest
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821275
Title:
Unable to configure the
This is blocking the ubuntu_zfs_fstest as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821275
Title:
Unable to configure the nfs-kernel-server (1:1.2.8-9ubuntu12.1) on
Xenial KVM
To
Hello Timo, or anyone else affected,
Accepted mesa into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.8-0ubuntu0~19.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
It sounds like your PrtScn button might be stuck down. This can happen
without it looking stuck down. Please try tapping PrtScn several times
to try and unstick it.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug
Reopened per bug 1837467.
** Tags removed: cosmic
** Tags added: disco
** Changed in: bluez (Ubuntu)
Status: Won't Fix => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836809
Title:
*** This bug is a duplicate of bug 1836809 ***
https://bugs.launchpad.net/bugs/1836809
Reopened bug 1836809. Please use that instead.
** This bug has been marked a duplicate of bug 1836809
segfault when CCD are present in two different HOG services
--
You received this bug notification
Please:
sudo apt install openssh-server
so that you can log into the machine before/while the lid is closed.
Then while the lid is closed and the machine overheating, please run:
top
and tell us what process is using the most CPU? Or just take a
screenshot.
** Package changed: xorg
There is nothing wrong with Simple Scan nor kernel 4.15.0-55. Scanning is now
fine. The fault was with my scanner and has been resolved.
I apologise for being too quick to press the panic button.
Cheers,
Andre
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
Installing plymouth-theme-spinner results in an unwanted purple screen
during start-up:
- 1. Black screen with Lenovo logo, no spinner.
+ 1. Black screen with BIOS logo, no spinner.
2. Purple screen with no logos or spinners. <
- 3. Black screen with
** Summary changed:
- Ubuntu 18.10 doesn't like fullscreen mode for sauerbraten(game)
+ Ubuntu doesn't like fullscreen mode for sauerbraten(game)
** Tags removed: cosmic
** Tags added: disco
** Changed in: gnome-shell (Ubuntu)
Status: Won't Fix => Confirmed
** Changed in: mutter
I think if you need to build any older kernels then the simplest answer
is the workaround in comment #8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830961
Title:
Kernels & kernel drivers fail
1 - 100 of 793 matches
Mail list logo
