I have just run into this same problem on both 18.04 Server and 19.04
Server Beta. After finding this bug report, I unplugged the drive array
full of ZFS disks and the local write cache disk only to still run into
the issue due to my nvme used for read cache.
--
You received this bug notification
** 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
backports: bug 1822817 (xenial/li
Public bug reported:
keeps asking to report
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libitm1:amd64 5.4.0-6ubuntu1~16.04.11
ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
** Package changed: ubuntu => simple-scan (Ubuntu)
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823339
Title:
Ubuntu 19.04: Simple scan found network scanner but could not co
Hi,
For now, the version from dpkg is the best way. Netplan does have plans
for querying feature-flags/--version.
https://trello.com/c/ls9KUQuV/42-feature-availability-documentation-
introspection-feature-flags
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
This actually caused downtime for me today because of the apache update.
The process stops apache, tries to stop u-u then exits, leaving apache
down.
When can we expect the fix to be released for xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820259
Title:
[FFe] Add a indicator to show the status of Livepatch
To manage notifications about this bug go to:
https
Public bug reported:
In Bionic the livepatch notification does not have a "Settings..."
button.
** Affects: update-notifier (Ubuntu)
Importance: Undecided
Status: Fix Released
** Tags: rls-bb-incoming
** Changed in: update-notifier (Ubuntu)
Status: New => Fix Released
**
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823350
Title:
package libitm1:amd64 5.4.0-6ubuntu1~16.04.11 failed to
install/upgrade: package is in a very bad
** 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
backports: bug 1822832 (trusty/li
** 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
backports: bug 1822817 (xenial/li
** 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
**
oh well, it seems to me that kernel versioning is pretty much messed
up. The (test) kernel I had installed, as of #77 reports version
4.15.0-46 ( linux-unsigned, modules, modoles-extra). Software Updater
reports the very same version numbers for those modules to be updated,
independent from wh
closing mesa as fixed according to upstream years ago
** Changed in: mesa (Ubuntu)
Status: Triaged => Fix Released
** Changed in: mesa (Ubuntu Precise)
Status: Triaged => Fix Released
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed => Fix Released
**
Public bug reported:
Description:Ubuntu 18.04.2 LTS
Release:18.04
After card reader device is used with write-protected SD card, write-
protection incorrectly persists to future SD cards, even non-protected
ones.
To reproduce:
1) Insert non-protected SD card in card reader (confirm s
Upstream report was closed "RESOLVED FIXED" on 2015-03-29
Unable to reproduce with Thunderbird 60.6 in Ubuntu 18.04
No comments here or upstream for 4 years so closing as fixed
** Changed in: thunderbird (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification beca
I'm deleting this SRU from bionic-proposed to unbreak image builds. It
can always be copied back in over itself if we decide to go ahead with
it after the MIR is completed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Hi Bounces,
We're very sorry about it and it is a known issue. We'll be fixing it after
some of our patches are backported.
--
Software Engineer, MLSE
AMD, Advanced Micro Devices
Phone: +86-13761283909
Adam Yang
From: boun...@canonical.com on behalf of
mazahaka
Verification successful with bionic-proposed.
Tested in login screen and auto-login session;
repeated 5 times with consistent results.
bionic-updates
--
$ dpkg -s plymouth | grep ^Version:
Version: 0.9.3-1ubuntu7.18.04.1
$ grep -wo splash /proc/cmdline
splash
$ dmesg | grep console
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823336
Title:
Sc
pretty sure this got fixed at some point
** Changed in: idm-console-framework (Ubuntu)
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/1049774
Title:
idm-console-fr
We still see random fails on Azure instances, it does not appear to be
isolated to a particular instance
03:19:44 DEBUG| Running
'/home/azure/autotest/client/tmp/monotonic_time/src/time_test --duration 300
tsc_lfence'
03:24:44 INFO | Time test command exit status: 1
03:24:44 ERROR| Exception esc
I'd like to also confirm this bug, which we've been experiencing for the
past few months since we first setup an 18.04 image for our deployment
portal.
Initially I thought the cause MAY have been from us using ifupdown (we
have to as our vCenter instance hasn't been upgraded to 6.5.x or 6.7
where
cosmic and up has 1.2.0, so marking it fixed for other than bionic
** Also affects: idm-console-framework (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: idm-console-framework (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because yo
** Changed in: salt
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823332
Title:
salt --versions-report broken in bionic/cosmic with openssl 1.1.1
To manage notificati
On 2019-04-05 11:08, Timo Aaltonen wrote:
> shouldn't this be fixed in cosmic too?
Well, I skipped it since there are only three months left. If it is a
requirement, I'll do it. Please let me know.
I installed im-config 0.34-1ubuntu1.3 from bionic-proposed and verified
the test case.
** Tags rem
..to 1.1.17
** Summary changed:
- 389-Console says 389-admin is stopped ater it connect to it
+ 389-Console says 389-admin is stopped after connection
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
Public bug reported:
Upon trying to scan to network scanner, simple scan found the scanner
but could not connect to scan. Tried multiple times with a reboot in b/t
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member o
I can't repro this specific issue, I believe it may be a H/W issue as
reported in this bug. Other reasons for the reboot tests failing are
marked in comment #3. Marking this as won't fix.
** Changed in: linux-aws (Ubuntu)
Status: In Progress => Won't Fix
--
You received this bug notifica
Successfully verified on cosmic:
ubuntu@hwe0002:~/stress-ng$ apt-cache policy linux-generic
linux-generic:
Installed: 4.18.0.18.19
Candidate: 4.18.0.18.19
Version table:
*** 4.18.0.18.19 500
500 http://us.ports.ubuntu.com/ubuntu-ports cosmic-proposed/main s390x
Packages
100
Cosmic verfication:
root@concise-fly:~# virtualenv --no-download venv
Running virtualenv with interpreter /usr/bin/python2
New python executable in /root/venv/bin/python2
Also creating executable in /root/venv/bin/python
Installing setuptools, pkg_resources, pip, wheel...done.
root@concise-fly:~#
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => 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 se
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822793
Title:
linux-gcp: 4.18.0-1009.10 -proposed tracker
To manage notifications about this bug go to:
https
Hi,
I try to remember the release notes, but my feeling here was they are too long
for a bug description.
For testing I have formerly only talked with the Debian maintainer and
it seemed good.
But to be sure on buildability and no major issues I have built it in a
PPA [1] and installed as well a
** 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
backports: bug 1822832 (trusty/li
** 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
backports: bug 1822817 (xenial/li
Thank @xnox, I just made the test and I have the same issue with rebuilt
python3.6.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04 LTS
To manage notificat
** Bug watch added: github.com/saltstack/salt/issues #49661
https://github.com/saltstack/salt/issues/49661
** Also affects: salt via
https://github.com/saltstack/salt/issues/49661
Importance: Unknown
Status: Unknown
** Changed in: salt (Ubuntu Disco)
Status: New => Fix Rele
Public bug reported:
= Steps to reproduce =
1. Open the control center
2. Open the sound panel
3. Position the mouse in the middle of the panel and scroll up and down with
the wheel
4. If a slider box moves to be under the mouse then the slider is moved instead
of scrolling the window
A video
Public bug reported:
Ubuntu 19.04 Disco Dingo.
I can save recorded video as webm or mp4 but not as gif. The peek app
from flatpak works fine so I suppose this is a problem in ubuntu
package. This is the output when run in terminal:
Using screen recorder backend gnome-shell
Recording to file /hom
It's the last thing seen on the console when it happens. The machine in
question has been updated to disco and I haven't seen the behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815509
Title:
Public bug reported:
sudden freeze. Power off required. complaint about a bcmwl update but
updated not switched on.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
Uname: Li
** 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
backports: bug 1822817 (xenial/li
** 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
backports: bug 1822832 (trusty/li
Thx again - entire verification is done - changing tags.
** Tags removed: 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.net/
@eole-team
hm, that shouldn't happen. python3.6, rebuilt against openssl1.1.1, has
not been accepted yet into bionic-proposed. And even, when I upgrade to
python3.6 from the staging ppa, salt still fails.
To get the pending python3.6, you can use the below PPA:
$ sudo add-apt-repository ppa:ci-tr
Public bug reported:
# sudo apt install salt-master
# sudo salt --versions-report
Traceback (most recent call last):
File "/usr/bin/salt", line 10, in
salt_main()
File "/usr/lib/python3/dist-packages/salt/scripts.py", line 476, in salt_main
client.run()
File "/usr/lib/python3/dist-p
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/182
Title:
bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module
failed to build
To manage n
Upstream bug showing "RESOLVED FIXED" on 2015-10-29
Checked working version 3.28 in Ubuntu 18.04
So closing as fixed.
** Changed in: gnome-mines (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
--- Comment From cborn...@de.ibm.com 2019-04-05 08:52 EDT---
verified successfully on cosmic-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818854
Title:
[Ubuntu] vfio-ap: add subs
Can you please tell me if:
1) it works with latest vbox6 version
2) it is reproducible with the upstream deb file
** Changed in: virtualbox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Changed in: update-manager (Ubuntu Disco)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807900
Title:
update-manager suggests to use Livepatch, which is n
Thank you - adjusting tag.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818854
Title:
[Ubuntu] vfio-ap: add sub
** 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
@root (mysky),
Qualys is slow to fix their detection algorithm. You just need to provide them
with False Positive report citing the vendor documentation
(https://usn.ubuntu.com/3809-1/).
Faking software version is the last thing someone should do to be PCI DSS
compliant.
--
You received this
--- Comment From cborn...@de.ibm.com 2019-04-05 08:34 EDT---
verified successfully on bionic-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818854
Title:
[Ubuntu] vfio-ap: add subs
** Tags added: id-5ca6214756f1b84f8df62a00
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821677
Title:
dl_open segment fault in ubuntu18.10 glibc2.28
To manage notifications about this bug go to:
# journalctl -u apache2
-- Logs begin at Fri 2019-03-29 14:29:08 UTC, end at Fri 2019-04-05 12:34:50
UTC. --
[...]
Apr 04 06:25:04 0616675e8cc176244 systemd[1]: Reloading LSB: Apache2 web server.
Apr 04 06:25:04 0616675e8cc176244 apache2[15672]: * Reloading Apache httpd web
server apache2
Apr 04
** 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
**
** 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
backports: bug 1822817 (xenial/li
** 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
backports: bug 1822832 (trusty/li
update Console Framework from 1.1.14 1.1.14 solved the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823328
Title:
389-Console says 389-admin is stopped ater it connect to it
To manage no
Sorry, wrong machine; here is the correct file:
# grep -i apache /var/log/syslog
Apr 5 06:33:34 0616675e8cc176244 systemd[1]: Stopping LSB: Apache2 web
server...
Apr 5 06:33:34 0616675e8cc176244 apache2[20777]: * Stopping Apache httpd web
server apache2
Apr 5 06:33:35 0616675e8cc176244 apache
Nothing found in /var/crash, enabled code dump but nothing happens:
[Fri Apr 05 14:25:24.740627 2019] [core:error] [pid 2264] AH00546: no record of
generation 0 of exiting child 27311
[Fri Apr 05 14:25:24.740630 2019] [core:notice] [pid 2264] AH00052: child pid
27312 exit signal Segmentation fau
org.mozilla.jss.ssl.SSLSocketException: SSL_VersionRangeSetDefault() for
variant=0 with min=768 max=770 out of range (769:772): 0: (0) Unknown error
at org.mozilla.jss.ssl.SSLSocket.setSSLVersionRangeDefault(Native
Method)
at
org.mozilla.jss.ssl.SSLSocket.setSSLVersionRangeDefaul
Ok. I'm no expert but I will try and do it.
.
Will let you know what happens next if I do not screw it all... lol
.
Cordially,
.
Scoobbs
===//===
Em sex, 5 de abr de 2019 09:01, Timo Aaltonen
escreveu:
> forcibly uninstall nvidia-340, then run updates and reinstall nvidia-340
> and make sur
Public bug reported:
Description:Ubuntu 18.04.2 LTS
Release:18.04
Client
389-console/bionic,bionic,now 1.1.18-2 all
** Affects: idm-console-framework (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bu
** 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
**
@edward, Yes thanks for pointing that out. That will delay this fix from
landing. Looks like your new fix for 1818614 is on track to land so
that's good. https://review.openstack.org/#/c/649991
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Upstream report closed "RESOLVED WORKSFORME" on 2019-04-04
Reporter says issue resolved, see comment #8
** Changed in: firefox (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Description changed:
[Impact]
Bionic released with version 2 of the Shibboleth Service Provider (and
its accompanying dependencies) and with OpenSSL 1.1. However, the SPv2
isn't compatible with OpenSSL 1.1, only 1.0 (and earlier), and was
therefore shipped compiled against 1.0. Thi
** 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
backports: bug 1822817 (xenial/li
** 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
backports: bug 1822832 (trusty/li
Public bug reported:
Please sync opensaml 3.0.1-1 (universe) from Debian unstable (main)
Changelog entries since current disco version 3.0.0-2:
opensaml (3.0.1-1) unstable; urgency=medium
* [d1daef5] Revert "Temporarily ignore build test failures"
* [792ec83] New upstream release: 3.0.1
*
** Summary changed:
- Changing Heading 1 to Heading 2 and then updating table of contents deletes
the whole Heading 2 section
+ Changing Heading 1 to Heading 2 and then updating table of contents cuts of
the whole Heading 2 section
** Description changed:
I've got a 20,129 word (122.5 kB) OD
Here is the result :
# grep apache /var/log/syslog
# grep -i apache /var/log/syslog.1
Apr 5 06:25:03 0d47a8f6bd573173d systemd[1]: Reloading LSB: Apache2 web server.
Apr 5 06:25:03 0d47a8f6bd573173d apache2[26744]: * Reloading Apache httpd web
server apache2
Apr 5 06:25:03 0d47a8f6bd573173d
Seyeong,
Can you take a look at this and see if you may have missed a package on
the install? When you say you were upgrading, were you upgrading from
queens? In that scenario you want to upgrade your queens py2 packages to
rocky py2 packages and then upgrade rocky py2 to rocky py3 packages.
Than
forcibly uninstall nvidia-340, then run updates and reinstall nvidia-340
and make sure it's the new one.. or just force install the new nvidia..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823270
T
Thank you for your report.
This looks like a local configuration problem, rather than a bug in Ubuntu.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration pr
Tested with -proposed stress-ng 0.09.25-1ubuntu2 on amd64 with 192 cpus,
300 af-alg stressors and it works fine, so verification passed.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification
Hi, well Firmware is a broad term - let me split it up into two cases:
1) boot from CD or FTP server (e.g. 'Load from Removeable Media and
Server' task),
then install to disk and reboot from that disk - possible in classic HMC
mode and DPM
2) boot from network server (PXE-like), then install
I've been merrily switching between OS's without this kind of issue for more
than 10 years ..
the behaviour changed recently in the last 30 days ..
it was fine prior to that ..
This is a regression bug and will annoy anyone working with multiple instances
of disco xubuntu for testing..
yes it
Will try, but can take some days/weeks because other priorities for the
moment
Brgds,
Raf
Op vr 5 apr. 2019 13:30 schreef Kai-Heng Feng
:
> Please try the kernels between 4.18.0-10 and 4.18.0-17 and find out the
> last good and first bad kernel.
>
> --
> You received this bug notification becau
** Tags added: server-triage-discuss
** Changed in: run-one (Ubuntu)
Status: New => Triaged
** Changed in: run-one (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Attachment added: "Heading 1 update bug"
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1823322/+attachment/5253052/+files/Screencast%20from%2005-04-19%2012%3A40%3A22.webm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** 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
backports: bug 1822811 (xenial/li
Public bug reported:
I've got a 20,129 word (122.5 kB) ODT with a number of headings and a
table of contents. I've got a heading (the last heading in the document)
which was Heading 1 (style), I think, but is now Heading 2. The table of
contents indicates that it is Heading 1 (hence I think it was
I don't really understand your question so I recorded the steps to
reproduce the bug. Please note that no matter the event is 'personal' or
sync with gmail, this bug still happens.
** Attachment added: "Steps to reproduce"
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1822402/+
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => 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 s
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.xfce.org/show_bug.cgi?id=13724.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.la
** 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
backports: bug 1822817 (xenial/li
Previous comment should have been:
Verified on Cosmic amd64, stress-ng 0.09.42-1ubuntu2
Also:
Verified on Bionic amd64, stress-ng 0.09.25-1ubuntu2
** Tags removed: verifica verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-d
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-
** 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
backports: bug 1822832 (trusty/li
Started seeing something similar on Precision 5520 with TB16 dock after
a recent kernel update. The original 4.18 worked fine, but 4.18.0-16 and
4.18.0-17 are definitely affected, possibly some earlier ones too.
After a while, e.g. 2 hours of work, connecting a new device to the dock
causes the xh
** Also affects: adcli (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: adcli (Ubuntu Bionic)
Status: New => Triaged
** Changed in: adcli (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bu
Started seeing this again on nvidia-396.54 with 4.18.0-16 and 4.18.0-17,
possibly 4.18.0-15 - I don't recall having hot-plugged it on -15.
It's worse now as the system never recovers any of the displays after
hot-plugging and even after removing the dock following a hot-plug the
built-in laptop di
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1823320
and then change the status of the bug to 'Confirmed'.
If, due to the nature
I have tested and verified that this works as expected with the package
from bionic-proposed. Note that the python-pip package change results in
the change in python-pip-whl which is used for virtualenvs.
root@aio1-utility-container-f98ba613:/# apt-cache policy python-pip-whl
python-pip-whl:
Ins
That's odd. Could you please also paste the result of "grep apache
/var/log/syslog"? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823313
Title:
Apache update to 2.4.18-2ubuntu3.10 stopped
301 - 400 of 590 matches
Mail list logo