The link order does seem to be significant as you suggested. However,
both the linker and run-time linker succeed without error. The failure
is inside the path dtor. While --as-needed may well be at fault, it
looks like there may be problems with either not reporting errors, or
doing the wrong
Public bug reported:
I have installed Ubuntu on a virgin SSD with an AMD Athlon, the OS
bugged regularly, it was frozen then impossible to shut down. I also had
lines of error messages
I have made a second attempt for installation wich failed (see this
related bug report. It seems to come from
*** This bug is a duplicate of bug 1824677 ***
https://bugs.launchpad.net/bugs/1824677
** This bug has been marked a duplicate of bug 1824677
Display only has 640x480
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: unity (Ubuntu)
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/1824574
Title:
"Authentication Failure"
To manage notifications about this bug go to:
The verification of the Stable Release Update for ubuntu-release-
upgrader 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
The verification of the Stable Release Update for ubuntu-release-
upgrader 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
This bug was fixed in the package ubuntu-release-upgrader - 1:18.10.11.6
---
ubuntu-release-upgrader (1:18.10.11.6) cosmic; urgency=medium
* DistUpgradeController.py: Instead of checking every sources.list entry to
see if they are accessible keep track of the uris and only test
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1824687/+attachment/5256032/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824687
This bug was fixed in the package ubuntu-release-upgrader - 1:18.10.11.6
---
ubuntu-release-upgrader (1:18.10.11.6) cosmic; urgency=medium
* DistUpgradeController.py: Instead of checking every sources.list entry to
see if they are accessible keep track of the uris and only test
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1824687/+attachment/5256034/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824687
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1824687/+attachment/5256033/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824687
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1824687/+attachment/5256028/+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/1824687
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1824687/+attachment/5256027/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1824687/+attachment/5256029/+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/1824687
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1824687/+attachment/5256030/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1824687/+attachment/5256031/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Description: Ubuntu 16.04.6 LTS
Release: 16.04
After upgrading our server to this Kernel we experience frequent Kernel
panics (Attachment).
Every 3 hours.
Our machine has a throuput of about 600
Hi Brian,
below is the message i have received frequently.
And therefore I wrote:
don't know whats behind the message
Thank you for taking care.
Kind regards
Wilfried
Screenshot von Ubuntu-Fehler: Es wurde ein Problem mit einer
Systemanwendung festgestellt
--
You received this bug
Mike's fix worked for me as well - Ubuntu 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770502
Title:
Brasero hangs when burning cds
To manage notifications about this bug go to:
Public bug reported:
Timeout on configuration
Vormals nicht ausgewähltes Paket open-iscsi wird gewählt.
(Lese Datenbank ... 125242 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../open-iscsi_2.0.874-5ubuntu2_armhf.deb ...
Entpacken von open-iscsi
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 1824864
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1824863
and then change the status of the bug to 'Confirmed'.
If, due to the
Google Chrome is not a software package that is provided by the official
Ubuntu repositories so the Ubuntu project can not support, help with or
fix your problem.
Please report this bug to the provider of the software package:
I've modified the /etc/sysctl.conf with
mt76x0u.disable_usb_sg=1
but the error still appears.
** Attachment added: "Modified sysctl.conf"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824650/+attachment/5256019/+files/sysctl.conf
--
You received this bug notification because you
I have ran a few tests on 16.04, 18.04, 18.10, and 19.04 (all X86_64):
16.04:
root@u1604:~# date +%-Y -d '- 2010 years'
9
root@u1604:~# date --version
date (GNU coreutils) 8.25
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
** Summary changed:
- Best Place To Buy Tramadol Online Overnight
+ After update from 14.10 to 15.04 boot stops at black screen displaying
"Starting version 219"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
(bionic-amd64)root@impulse:/home/bdmurray/Documents/canonical/admin#
do-release-upgrade
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1250 kB]
Fetched 1251 kB in 0s (0 B/s)
authenticate 'cosmic.tar.gz' against 'cosmic.tar.gz.gpg'
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plasma-workspace (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/1785626
Only Line Out works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824205
Title:
[MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front]
Playback problem
To manage notifications
** Changed in: linux-hwe-edge (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/1823315
Title:
header files not included
To manage
Public bug reported:
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on
amd64, meaning
** Also affects: linux-hwe-edge (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-edge (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
dogtag-pki fails its autopkgtests with resteasy3.0 3.0.26, which is
currently being SRUed as part of the openjdk11 transition.
http://autopkgtest.ubuntu.com/packages/d/dogtag-pki/cosmic/amd64
It appears that certutil is failing, and this impacts pki-tps usage.
This is
** Also affects: linux-hwe-edge (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-hwe-edge (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-hwe-edge
The change introduced by the patch is evident in the kernel message log for
Thread 0:
between page indexes 2 and 1 there's now another function call to
write_cache_pages()
instead of just another iteration of the for-loop inside one call.
Original kernel:
[ 695.276320] Thread 0 running, TID =
Public bug reported:
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on
amd64, meaning
Public bug reported:
We now have an LTS to LTS where both have ESM. Therefore we should be
testing a system with ESM installed on Precise and then upgrade to
Trusty ESM.
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Ignore that, typo. Blacklisting correctly didn't help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824703
Title:
Intel 8260 Bluetooth non-functioning, command timeouts
To manage notifications
Public bug reported:
An unresolvable problem occurred while calculating the upgrade.
This was likely caused by:
* Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-purge
package to remove software from a Launchpad PPA and
try the upgrade again.
Can i try it via lubuntu-18.04 virtualized with VirtualBox?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790595
Title:
Line 6 POD HD500 driver fault
To manage notifications about this bug go to:
Nope, glib fix is enough for nautilus.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760569
Title:
Nautilus crashes in g_free -> g_bookmark_file_move_item ->
gtk_recent_manager_move_item ->
Since I see that fix for budgie landed in disco and the SRU package is
in queue, I think we can mark this as verified.
** Tags removed: verification-failed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** 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/1824859
Title:
package libc-bin 2.27-3ubuntu1 failed to install/upgrade: installed
libc-bin package
Patch posted for SRU:
[C][PATCH 0/1] Fix write()/fsync() deadlock in write_cache_pages()
https://lists.ubuntu.com/archives/kernel-team/2019-April/100084.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm, blacklisting iwlwifi didn't do anything, but I still see this in my
lsmod:
iwlmvm364544 0
mac80211 778240 1 iwlmvm
iwlwifi 286720 1 iwlmvm
cfg80211 622592 3 iwlmvm,iwlwifi,mac80211
Should I be blacklisting more?
--
You received
Public bug reported:
Ubuntu is failing to update itself for a while.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libc-bin 2.27-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture:
I followed the steps in the test case when upgrading from bionic to
cosmic and it passed. In the main.log file of the upgrade using 'do-
release-upgrade -p' we can see url_downloadable is called only once and
that the universe entry is still enabled.
2019-04-15 10:13:22,505 INFO Using config
I'm using Discover in Lubuntu 18.10 and I don't see a way to "select all" nor
"deselect all." Currently, the most efficient way to deselect many is to
- click on a check mark in front of an update thereby deselecting it
- arrow down to move to the next update
- [Enter] to deselect that update
-
Public bug reported:
1) Ubuntu Release Version
:~$ lsb_release -rd
Description:Ubuntu 16.04.6 LTS
Release:16.04
2) Affected Packages
:~$ apt-cache policy xserver-xorg-core-hwe-16.04
xserver-xorg-core-hwe-16.04:
Installed: 2:1.19.6-1ubuntu4.1~16.04.2
Candidate:
Attempted fix: Installing the xserver-xorg-core
Result: X11 server freezes after login. Non-responsive and requires a forced
shutdown.
Any other information: Installing xserver-xorg-core results in the
following terminal output.
:~$ sudo apt-get install xserver-xorg-core
Reading package
Public bug reported:
When waking my laptop screen up at the lock screen, it takes a very long
time to display the password prompt (definitely longer than 30s,
possibly longer than 1m - I didn't time it). I notice that while
waiting for the password prompt, the screen is showing a full list of
** 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
** Description changed:
[Impact]
This is breaking Ceph cluster https service.
# logs:
2019-04-02 16:40:14.846313 7ff8c1736000 0 starting handler: civetweb
2019-04-02 16:40:14.846397 7ff8c1736000 0 civetweb: 0x56114520d620: load_dll:
libcrypto.so.1.1: cannot find CRYPTO_num_locks
** 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/1822808
Title:
linux-gcp: 4.15.0-1030.32 -proposed tracker
To manage notifications about this bug go to:
Google chrome
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824667
Title:
Flash in Chrome does not work
To manage notifications about this bug go to:
I got a reply to my bug report on gnu.org which says:
"
From:
Paul Eggert
It works for me with coreutils 8.31 on RHEL 7 x86-64:
$ date +%-Y -d "- 2010 years"
9
Most likely you are running on a 32-bit machine, and dates in the year 9
cannot be represented in a 32-bit timestamp. So a simple fix
I followed the test when upgrading a system from xenial to bionic and it
passed. Here we can see that url_downloadable is called only once with
the version of the release upgrader in -proposed and that the universe
entry is still enabled:
2019-04-15 09:53:30,259 INFO Using config files
** Summary changed:
- apparmor no more starting in Disco LXD containers
+ apparmor does not start in Disco LXD containers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824812
Title:
apparmor does
Public bug reported:
I downloaded the latest Ubuntu 18.04 LTS Server image from the website,
verified the image and wrote it using Startup Disk Creator to a USB
drive. Everything worked just fine up until the Network Configuration
section.
It auto-detected both Broadcom NetXtreme II 5708
It's worse than that. Developers who use nodejs in their apps, and have
to use libssl-dev, are simply screwed. Even moving to a container won't
help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested a release upgrade from Xenial to Bionic with https entries in
my sources.list file. With the version of the release upgrader in the
-updates pocket I was not allowed to upgrade however when I tried to
upgrade using 'do-release-upgrade -p' the upgrade was successfully
calculated. Here's an
** Changed in: stress-ng
Status: In Progress => 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/1815123
Title:
Hardware test stress-ng-cpu-long bind failed
To manage
This bug was fixed in the package snapd - 2.38+18.10
---
snapd (2.38+18.10) cosmic; urgency=medium
* New upstream release, LP: #1818648
- overlord/snapstate,: retry less for auto-stuff
- cmd/snap: fix regression of snap saved command
- interfaces/builtin: add
This bug was fixed in the package openconnect - 7.08-3ubuntu0.18.04.1
---
openconnect (7.08-3ubuntu0.18.04.1) bionic; urgency=medium
* debian/patches/git-juniper-realm.patch:
- Fix issue causing front-ends/GUIs to be insensitive to changes
in the Juniper realm dropdown
This bug was fixed in the package snapd - 2.38~14.04
---
snapd (2.38~14.04) trusty; urgency=medium
* New upstream release, LP: #1818648
- overlord/snapstate,: retry less for auto-stuff
- cmd/snap: fix regression of snap saved command
- interfaces/builtin: add
This bug was fixed in the package snapd - 2.38
---
snapd (2.38) xenial; urgency=medium
* New upstream release, LP: #1818648
- overlord/snapstate,: retry less for auto-stuff
- cmd/snap: fix regression of snap saved command
- interfaces/builtin: add dev/pts/ptmx access to
do you notice similar (problematic) behavior when just restarting
networkd, e.g.:
$ sudo systemctl restart systemd-networkd
or, stopping systemd-networkd, e.g.:
$ sudo systemctl stop systemd-networkd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package snapd - 2.38+18.04
---
snapd (2.38+18.04) bionic; urgency=medium
* New upstream release, LP: #1818648
- overlord/snapstate,: retry less for auto-stuff
- cmd/snap: fix regression of snap saved command
- interfaces/builtin: add
The verification of the Stable Release Update for snapd 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
testcase, kernel part.
** Attachment added: "kprobe-test.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+attachment/5255994/+files/kprobe-test.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
testcase
test kernel :: latest cosmic version + patch:
$ uname -rv
4.18.0-18-generic #19+test20190415b1 SMP Mon Apr 15 15:43:20 UTC 2019
[ 169.145212] kprobe_test: loading out-of-tree module taints kernel.
[ 169.149144] kprobe_test: module
testcase
original kernel :: latest cosmic version:
$ uname -rv
4.18.0-18-generic #19-Ubuntu SMP Tue Apr 2 18:13:16 UTC 2019
[ 654.491029] kprobe_test: loading out-of-tree module taints kernel.
[ 654.493322] kprobe_test: module verification
testcase, userspace part.
** Attachment added: "test.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+attachment/5255995/+files/test.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The verification of the Stable Release Update for stress-ng 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
The verification of the Stable Release Update for openconnect 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
** Changed in: parted (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: parted (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The verification of the Stable Release Update for im-config 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 stress-ng - 0.09.25-1ubuntu2
---
stress-ng (0.09.25-1ubuntu2) bionic; urgency=medium
[Alfonso Sanchez-Beato]
* stress-numa: fix calculation of max nodes (LP: #1823208)
- use the count of bits in "Mems_allowed" to calculate the
maximum
This bug was fixed in the package stress-ng - 0.09.25-1ubuntu2
---
stress-ng (0.09.25-1ubuntu2) bionic; urgency=medium
[Alfonso Sanchez-Beato]
* stress-numa: fix calculation of max nodes (LP: #1823208)
- use the count of bits in "Mems_allowed" to calculate the
maximum
This bug was fixed in the package ubuntu-meta - 1.361.3
---
ubuntu-meta (1.361.3) xenial; urgency=medium
* Added ubuntu-wsl metapackage from the wsl seed (LP: #1822341)
* Added wslu and ubuntu-minimal's dependencies and recommends to ubuntu-wsl
-- Balint Reczey Sat, 30 Mar
The verification of the Stable Release Update for shim-signed 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 shim-signed - 1.33.1~14.04.5
---
shim-signed (1.33.1~14.04.5) trusty; urgency=medium
* debian/control: make the sbsigntool dependency versioned to ensure updates
include getting the new sbsigntool so DKMS modules can be correctly signed.
This bug was fixed in the package im-config - 0.34-1ubuntu1.3
---
im-config (0.34-1ubuntu1.3) bionic-proposed; urgency=medium
* debian/patches/dont-set-GTK_IM_MODULE-on-wayland.patch:
- Don't set GTK_IM_MODULE if IBus on Wayland session
(LP: #1816808). (The regression,
This bug was fixed in the package shim-signed - 1.33.1~16.04.5
---
shim-signed (1.33.1~16.04.5) xenial; urgency=medium
* debian/control: make the sbsigntool dependency versioned to ensure updates
include getting the new sbsigntool so DKMS modules can be correctly signed.
This bug was fixed in the package ubuntu-meta - 1.417.1
---
ubuntu-meta (1.417.1) bionic; urgency=medium
* Added ubuntu-wsl metapackage from the wsl seed (LP: #1822341)
* Added wslu to ubuntu-wsl
-- Balint Reczey Sat, 30 Mar 2019 15:59:08 +0100
** Changed in: ubuntu-meta
I tested a release upgrade from Bionic to Cosmic with https entries in
my sources.list file. With the version of the release upgrader in the
-updates pocket I was not allowed to upgrade however when I tried to
upgrade using 'do-release-upgrade -p' the upgrade was successfully
calculated. Here's an
Public bug reported:
It seems to randomly lockup.
Often, I am able to scroll the mouse pointer without being able to
interact with the desktop itself.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname:
Does blacklist iwlwifi help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824703
Title:
Intel 8260 Bluetooth non-functioning, command timeouts
To manage notifications about this bug go to:
This bug was fixed in the package vaultlocker - 1.0.3-0ubuntu1.18.10.1
---
vaultlocker (1.0.3-0ubuntu1.18.10.1) cosmic; urgency=medium
* d/p/unblock-network.online.target.patch: Cherry pick fix to ensure
that vaultlocker-decrypt@ systemd units don't block the network-online
nodejs 8.x series uses libssl1.0-dev (OpenSSL 1.0.2) across all linux
distributions and upstream.
nodejs 10.x series uses libssl-dev (OpenSSL 1.1.0+) across all linux
distributions and upstream.
libssl1.0-dev and libssl-dev are intentionally non-coinstallable, as
they both own the same include
** 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
-- swm properties --
I see that people who use nodeenv potentially can get trapped, because
of:
$ apt show nodeenv | grep -e Package -e Depends
Package: nodeenv
Depends: python3-pkg-resources, python3, python3:any (>= 3.3.2-2~), make, gcc
(>= 4:4.9.1) | nodejs, g++ (>= 4:4.9.1) | nodejs, libssl-dev | nodejs,
** Summary changed:
- linux-gcp: -proposed tracker
+ linux-gcp: 5.0.0-1004.4 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) =>
Please clarify what you are reporting this problem against:
1) Google Chrome
2) Chromium, as provided by the official Ubuntu repositories
3) Or both Google's Chrome and Ubuntu's Chromium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
# IRC Discussion on freenode (#ubuntu-devel)
[11:46:46] slashd, jamespage - what am i missing about
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1822872 ? =)
[11:46:47] Launchpad bug 1822872 in ceph (Ubuntu Bionic) "Bionic:
Luminous radosgw incompatible with libssl1.1"
There are only a couple of reports in the Error Tracker bucket about
this happening with version 2.20.10-0ubuntu13.3 and those are likely
showing that version due to apport's late package version collection.
Setting to verification-done.
** Tags removed: verification-needed-cosmic
** Tags added:
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1544471.
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
No, it does not crash unless there is no disk space left. Closing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737012
Title:
Chromium random segfaults: error 4 in libnspr4.so
To manage
All of the update-manager autopkgtests were run (none were skipped) on
both bionic and cosmic and they all passed. Subsequently, the update-
manager parts of this SRU are verified.
Cosmic:
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1824177
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
301 - 400 of 731 matches
Mail list logo
