[Bug 1824721] Re: g++-8 in disco is broken with libstdc++6 from gcc9 and libstdc++fs

[Roger Leigh]

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 thing, when the link order isn't right.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824721

Title:
  g++-8 in disco is broken with libstdc++6 from gcc9 and libstdc++fs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-8/+bug/1824721/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824870] [NEW] Ubuntu crashed regularly after the 1st installation and is impossible to reinstall

[Charles]

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 the disk.

I have made those installations from a USB stick

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
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: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 15 20:38:01 2019
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=fr_FR.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824870

Title:
  Ubuntu crashed regularly after the 1st installation and is impossible
  to reinstall

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1824870/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824809] Re: Videoresolution 640 x 480 since latest update. can't be changed

[Timo Aaltonen]

*** 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.
https://bugs.launchpad.net/bugs/1824809

Title:
  Videoresolution 640 x 480 since latest update. can't be changed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1824809/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824574] Re: "Authentication Failure"

[Khurshid Alam]

** 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:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1824574/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822886] Update Released

[Steve Langasek]

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 that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822886

Title:
  universe missing after bionic->cosmic do-release-upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1822886/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823410] Update Released

[Steve Langasek]

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 that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823410

Title:
  utils.py's url_downloadable doesn't support https

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823410/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823410] Re: utils.py's url_downloadable doesn't support https

[Launchpad Bug Tracker]

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 once per
uri thereby preventing situations where entries for the same server are
enabled and disabled. (LP: #1822886)
  * debian/control: build depend on the new version of update-manager which
supports checking to see if an https url is downloadable. (LP: #1823410)
  * tests/test_sources.list.py: add a test for https support.

 -- Brian Murray   Tue, 09 Apr 2019 17:10:21 -0700

** Changed in: ubuntu-release-upgrader (Ubuntu Cosmic)
   Status: Fix Committed => 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/1823410

Title:
  utils.py's url_downloadable doesn't support https

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823410/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824687] ProcModules.txt

[Dirk]

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

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822886] Re: universe missing after bionic->cosmic do-release-upgrade

[Launchpad Bug Tracker]

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 once per
uri thereby preventing situations where entries for the same server are
enabled and disabled. (LP: #1822886)
  * debian/control: build depend on the new version of update-manager which
supports checking to see if an https url is downloadable. (LP: #1823410)
  * tests/test_sources.list.py: add a test for https support.

 -- Brian Murray   Tue, 09 Apr 2019 17:10:21 -0700

** Changed in: ubuntu-release-upgrader (Ubuntu Cosmic)
   Status: Fix Committed => 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/1822886

Title:
  universe missing after bionic->cosmic do-release-upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1822886/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824687] WifiSyslog.txt

[Dirk]

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

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824687] UdevDb.txt

[Dirk]

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:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824687] Lspci.txt

[Dirk]

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:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824687] CurrentDmesg.txt

[Dirk]

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.
https://bugs.launchpad.net/bugs/1824687

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824687] ProcCpuinfo.txt

[Dirk]

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

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824687] ProcCpuinfoMinimal.txt

[Dirk]

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.
https://bugs.launchpad.net/bugs/1824687

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824687] ProcInterrupts.txt

[Dirk]

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.
https://bugs.launchpad.net/bugs/1824687

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824687] Re: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue

[Dirk]

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 Mbits/s 
  The Panics are around the area of ip6_expire_frag_queue.
  
__pskb_pull_tail
ip6_dst_lookup_tail
_decode_session6
__xfrm_decode_session
icmpv6_route_lookup
icmp6_send
  
  
  It seems similar to Bug Report in Debian.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488
  
  According to the bug finder of above bug it also occurred after using a 
Kernel with the change of
  rewrite ip6_expire_frag_queue()
  
  Intermediate solution. We disabled IPv6 on this machine to avoid further 
Panics.
  Please let me know what information is missing. The ubuntu-bug linux was 
send. And I hope it is attached to this report.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-145-generic 4.4.0-145.171
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Apr 14 11:40:11 2019
  InstallationDate: Installed on 2018-03-18 (391 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to xenial on 2018-10-21 (174 days ago)
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Apr 12 21:04 seq
+  crw-rw 1 root audio 116, 33 Apr 12 21:04 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.18
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=/dev/mapper/tor3--vg-swap_1
+ InstallationDate: Installed on 2018-03-18 (393 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb:
+  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
+  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  LANGUAGE=en_GB:en
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-145-generic 
root=/dev/mapper/hostname--vg-root ro
+ ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-145-generic N/A
+  linux-backports-modules-4.4.0-145-generic  N/A
+  linux-firmware 1.157.21
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial xenial
+ Uname: Linux 4.4.0-145-generic x86_64
+ UpgradeStatus: Upgraded to xenial on 2018-10-21 (176 days ago)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 10/08/2012
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1.0c
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
+ dmi.board.vendor: Supermicro
+ dmi.board.version: 1.2
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Supermicro
+ dmi.chassis.version: 0123456789
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd10/08/2012:svnSupermicro:pnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:pvr0123456789:rvnSupermicro:rnX9SRE/X9SRE-3F/X9SRi/X9SRi-3F:rvr1.2:cvnSupermicro:ct3:cvr0123456789:
+ dmi.product.name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F
+ dmi.product.version: 0123456789
+ dmi.sys.vendor: Supermicro

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1824687/+attachment/5256026/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824687

Title:
  4.4.0-145-generic Kernel Panic  ip6_expire_frag_queue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824685] Message after booting

[Wilfried Müller]

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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824685

Title:
  after booting "a problem occured" on the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1824685/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770502] Re: Brasero hangs when burning cds

[Rob Cannell]

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:
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1770502/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824867] [NEW] package open-iscsi 2.0.874-5ubuntu2 failed to install/upgrade: Unterprozess installed open-iscsi package post-installation script gab den Fehler-Ausgangsstatus 1 zurück

[Eberhard Guhl]

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 (2.0.874-5ubuntu2) ...
Trigger für initramfs-tools (0.130ubuntu3) werden verarbeitet ...
open-iscsi (2.0.874-5ubuntu2) wird eingerichtet ...
Created symlink /etc/systemd/system/sysinit.target.wants/iscsid.service → 
/lib/systemd/system/iscsid.service.
Created symlink /etc/systemd/system/iscsi.service → 
/lib/systemd/system/open-iscsi.service.
Created symlink /etc/systemd/system/sysinit.target.wants/open-iscsi.service → 
/lib/systemd/system/open-iscsi.service.
Job for iscsid.service failed because a timeout was exceeded.
See "systemctl status iscsid.service" and "journalctl -xe" for details.
invoke-rc.d: initscript iscsid, action "start" 
failed.###...] 
● iscsid.service - iSCSI initiator daemon 
(iscsid)]
 
   Loaded: loaded (/lib/systemd/system/iscsid.service; enabled; vendor preset: 
enabled)
   Active: failed (Result: timeout) since Mon 2019-04-15 20:02:17 CEST; 25ms ago
 Docs: 
man:iscsid(8)##]
 
  Process: 6763 ExecStart=/sbin/iscsid (code=exited, status=0/SUCCESS)
  Process: 6760 ExecStartPre=/lib/open-iscsi/startup-checks.sh (code=exited, 
status=0/SUCCESS)
Fortschritt: [ 67%] 
[#]
 
Apr 15 20:00:46 guhl004 systemd[1]: Starting iSCSI initiator daemon 
(iscsid)...###] 
Apr 15 20:00:46 guhl004 iscsid[6763]: iSCSI logger with pid=6764 started!
Apr 15 20:00:46 guhl004 systemd[1]: iscsid.service: Failed to parse PID from 
file /run/iscsid.pid: Invalid argument
Apr 15 20:00:46 guhl004 iscsid[6764]: iSCSI daemon with pid=6765 
started!#] 
Apr 15 20:00:46 guhl004 iscsid[6764]: can not create NETLINK_ISCSI 
socket#] 
Apr 15 20:02:17 guhl004 systemd[1]: iscsid.service: Start operation timed out. 
Terminating.
Apr 15 20:02:17 guhl004 systemd[1]: iscsid.service: Failed with result 
'timeout'.
Apr 15 20:02:17 guhl004 systemd[1]: Failed to start iSCSI initiator daemon 
(iscsid).##] 
dpkg: Fehler beim Bearbeiten des Paketes open-iscsi 
(--configure):] 
 Unterprozess installed open-iscsi package post-installation script gab den 
Fehler-Ausgangsstatus 1 zurück
Trigger für systemd (237-3ubuntu10) werden verarbeitet ...
Trigger für man-db (2.8.3-2) werden verarbeitet ...
Trigger für initramfs-tools (0.130ubuntu3) werden verarbeitet 
...#] 
Fehler traten auf beim Bearbeiten 
von:]
 
 open-iscsi
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: open-iscsi 2.0.874-5ubuntu2
Uname: Linux 4.4.103-ELAR-Systems armv7l
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
 libisns0:armhf: Install
 open-iscsi:armhf: Install
 NULL: ConfigurePending
Architecture: armhf
Date: Mon Apr 15 10:00:17 2019
DpkgHistoryLog:
 Start-Date: 2019-04-15  09:58:40
 Commandline: apt install open-iscsi
 Requested-By: guhl (1001)
 Install: open-iscsi:armhf (2.0.874-5ubuntu2), libisns0:armhf (0.97-2build1, 
automatic)
ErrorMessage: Unterprozess installed open-iscsi package post-installation 
script gab den Fehler-Ausgangsstatus 1 zurück
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: open-iscsi
Title: package open-iscsi 2.0.874-5ubuntu2 failed to install/upgrade: 
Unterprozess installed open-iscsi package post-installation script gab den 
Fehler-Ausgangsstatus 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: open-iscsi (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package armhf bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824867

Title:
  package open-iscsi 2.0.874-5ubuntu2 failed to install/upgrade:
  Unterprozess installed open-iscsi package post-installation script gab
  den Fehler-Ausgangsstatus 1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1824867/+subscriptions

-- 

[Bug 1824864] Missing required logs.

[Ubuntu Kernel Bot]

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 nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

** Changed in: linux (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Incomplete

** Changed in: linux (Ubuntu Xenial)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824864

Title:
  CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824864/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824863] Missing required logs.

[Ubuntu Kernel Bot]

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 nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824863

Title:
  CONFIG_LOG_BUF_SHIFT is too low on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824863/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824667] Re: Flash in Chrome does not work

[Paul White]

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:

https://support.google.com/chrome/answer/95315?co=GENIE.Platform%3DDesktop=en

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Invalid

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1824667/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824650] Re: Ubuntu freezes when AC 430 WiFi Dongle is plugged in

[Rico Heartstrings]

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 are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824650

Title:
  Ubuntu freezes when AC 430 WiFi Dongle is plugged in

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824650/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111

[C de-Avillez]

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 .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.


18.04:

root@bionic:~# date +%-Y -d '- 2010 years'
9
root@bionic:~# date --version
date (GNU coreutils) 8.28
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.

18.10:

root@u1810:~# date +%-Y -d '- 2010 years'   

 
9
root@u1810:~# date --version
date (GNU coreutils) 8.28
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.

19.04:

cerdea@piatam:/data/buildd/coreutils$ date +%-Y -d '- 2010 years'
date: invalid date ‘- 2010 years’
1 cerdea@piatam:/data/buildd/coreutils$ date --version
date (GNU coreutils) 8.30
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.

Interestingly, it is also failing on git head:

130 cerdea@piatam:/data/buildd/coreutils$ src/date +%-Y -d '- 2010 years'
src/date: invalid date ‘- 2010 years’
1 cerdea@piatam:/data/buildd/coreutils$ src/date --version
date (GNU coreutils) 8.31.12-6d78a
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824688

Title:
  date+%-Y -d "- N years" errors when N > 111

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1824688/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1447978] Re: After update from 14.10 to 15.04 boot stops at black screen displaying "Starting version 219"

[Colin Watson]

** 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.
https://bugs.launchpad.net/bugs/1447978

Title:
  After update from 14.10 to 15.04 boot stops at black screen displaying
  "Starting version 219"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1447978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824866] [NEW] python3-distupgrade missing a dep on python3-distro-info

[Brian Murray]

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'
extracting 'cosmic.tar.gz'


A fatal error occurred

Please report this as a bug and include the files
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
your report. The upgrade has aborted.
Your original sources.list was saved in
/etc/apt/sources.list.distUpgrade.

Traceback (most recent call last):

File "/tmp/ubuntu-release-upgrader-wvzfz5ou/cosmic", line 8, in

sys.exit(main())

File
"/tmp/ubuntu-release-upgrader-wvzfz5ou/DistUpgrade/DistUpgradeMain.py",
line 224, in main
from .DistUpgradeController import DistUpgradeController

File
"/tmp/ubuntu-release-upgrader-wvzfz5ou/DistUpgrade/DistUpgradeController.py",
line 25, in 
import distro_info

ModuleNotFoundError: No module named 'distro_info'

This a result of the SRU of the fix for bug 1799310 while the new
dependency was added to the cosmic version of u-r-u that doesn't help
because the dist-upgrader tarball doesn't reflect that dependency.

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: ubuntu-release-upgrader (Ubuntu Bionic)
 Importance: Medium
 Status: Triaged

** Also affects: ubuntu-release-upgrader (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: ubuntu-release-upgrader (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/1824866

Title:
  python3-distupgrade missing a dep on python3-distro-info

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1824866/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1785626] Re: Plasma shell crahses after login and stays crashed

[Launchpad Bug Tracker]

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

Title:
  Plasma shell crahses after login and stays crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1785626/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824205] Re: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem

[Florian Richer]

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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1824205/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823315] Re: header files not included

[Thadeu Lima de Souza Cascardo]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-edge/+bug/1823315/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824864] [NEW] CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64

[Dimitri John Ledkov]

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 set 18 on arm64 s390x ppc64el.

I have a systemd autopkgtest test that asserts that we see Linux kernel
command line in the dmesg (journalctl -k -b). And it is consistently
failing on arm64 scalingstack KVM EFI machines with messages of "missing
81 kernel messages".

config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
  Select the minimal kernel log buffer size as a power of 2.
  The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
  parameter, see below. Any higher size also might be forced
  by "log_buf_len" boot parameter.

  Examples:
 17 => 128 KB
 16 => 64 KB
 15 => 32 KB
 14 => 16 KB
 13 =>  8 KB
 12 =>  4 KB

14 sounds like redictiously low for arm64. given that 17 is default
across 32-bit arches, and 18 is default on amd64.

Please backport this to xenial and up.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Cosmic)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Ee-series)
 Importance: Undecided
 Status: New


** Tags: bot-stop-nagging

** Tags added: bot-stop-nagging

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Ee-series)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Summary changed:

- CONFIG_LOG_BUF_SHIFT is too low on arm64
+ CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824864

Title:
  CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824864/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820868] Re: bionic: fork out linux-snapdragon into its own topic kernel

[Thadeu Lima de Souza Cascardo]

** 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.
https://bugs.launchpad.net/bugs/1820868

Title:
  bionic: fork out linux-snapdragon into its own topic kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820868/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824861] [NEW] dogtag-pki tests fail with resteasy3.0 3.0.26 (pki-tps)

[Steve Langasek]

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 possibly a runtime regression, but is being allowed (for both
bionic and cosmic) due to the much more severe security impact of not
updating to openjdk11.

** Affects: dogtag-pki (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: dogtag-pki (Ubuntu Bionic)
 Importance: High
 Status: New

** Affects: dogtag-pki (Ubuntu Cosmic)
 Importance: High
 Status: New

** Also affects: dogtag-pki (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: dogtag-pki (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: dogtag-pki (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: dogtag-pki (Ubuntu Cosmic)
   Importance: Undecided => High

** Changed in: dogtag-pki (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/1824861

Title:
  dogtag-pki tests fail with resteasy3.0 3.0.26 (pki-tps)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dogtag-pki/+bug/1824861/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823994] Re: arm64: not able to install linux-generic-hwe-18.04-edge/bionic-proposed

[Thadeu Lima de Souza Cascardo]

** 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 (Ubuntu Bionic)
   Status: New => 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/1823994

Title:
  arm64: not able to install linux-generic-hwe-18.04-edge/bionic-
  proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823994/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824827] Re: tasks doing write()/fsync() hit deadlock in write_cache_pages()

[Mauricio Faria de Oliveira]

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 = 3293!
[ 695.281210] kp1_pre_handler():070 :: state 1  :: pid = 1165, mapping = 
0x962333263730, comm = 'kworker/u4:2'
[ 695.299026] kp1_pre_handler():101 :: state 1 -> 2 :: pid = 1165, mapping = 
0x962333263730, comm ('kworker/u4:2') is kworker AND wbc->range_cyclic 
(0x1) is true AND mapping->writeback_index (0x2) is 0x2.
[ 695.314808] kp2_pre_handler():119 :: state 2  :: pid = 1165, page index = 
2
[ 695.322822] kp3_pre_handler():144 :: state 2  :: pid = 1165, page index = 
2, calling writepage()
  << ... HERE ... >>
[ 695.330308] kp2_pre_handler():119 :: state 2  :: pid = 1165, page index = 
1
[ 695.334355] kp2_pre_handler():123 :: state 2 -> 3 :: pid = 1165, page index = 
1, spin 5 seconds before lock_page()...

Test kernel:

[ 170.194880] Thread 0 running, TID = 2498!
[ 170.200011] kp1_pre_handler():070 :: state 1  :: pid = 7, mapping = 
0x993df9136fb0, comm = 'kworker/u4:0'
[ 170.217616] kp1_pre_handler():101 :: state 1 -> 2 :: pid = 7, mapping = 
0x993df9136fb0, comm ('kworker/u4:0') is kworker AND wbc->range_cyclic 
(0x1) is true AND mapping->writeback_index (0x2) is 0x2.
[ 170.238633] kp2_pre_handler():119 :: state 2  :: pid = 7, page index = 2
[ 170.248024] kp3_pre_handler():144 :: state 2  :: pid = 7, page index = 2, 
calling writepage()
[ 170.261141] kp1_pre_handler():070 :: state 2  :: pid = 7, mapping = 
0x993df9136fb0, comm = 'kworker/u4:0'
[ 170.272150] kp2_pre_handler():119 :: state 2  :: pid = 7, page index = 1
[ 170.279860] kp2_pre_handler():123 :: state 2 -> 3 :: pid = 7, page index = 1, 
spin 5 seconds before lock_page()...

** Changed in: linux (Ubuntu Cosmic)
   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/1824827

Title:
  tasks doing write()/fsync() hit deadlock in write_cache_pages()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824863] [NEW] CONFIG_LOG_BUF_SHIFT is too low on arm64

[Dimitri John Ledkov]

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 set 18 on arm64 s390x ppc64el.

I have a systemd autopkgtest test that asserts that we see Linux kernel
command line in the dmesg (journalctl -k -b). And it is consistently
failing on arm64 scalingstack KVM EFI machines with messages of "missing
81 kernel messages".

config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
  Select the minimal kernel log buffer size as a power of 2.
  The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
  parameter, see below. Any higher size also might be forced
  by "log_buf_len" boot parameter.

  Examples:
 17 => 128 KB
 16 => 64 KB
 15 => 32 KB
 14 => 16 KB
 13 =>  8 KB
 12 =>  4 KB

14 sounds like redictiously low for arm64. given that 17 is default
across 32-bit arches, and 18 is default on amd64.

Please backport this to xenial and up.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824863

Title:
  CONFIG_LOG_BUF_SHIFT is too low on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824863/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824862] [NEW] Test Precise ESM to Trusty ESM

[Joshua Powers]

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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824862

Title:
  Test Precise ESM to Trusty ESM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1824862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts

[Fmstrat]

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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824703/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824860] [NEW] unable to upgrade 16.04LTS to 18.04LTS

[Jeremy Crowley]

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.

I cannot find the Launchpad package responsible for the problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.26
ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Mon Apr 15 11:29:13 2019
InstallationDate: Installed on 2018-02-02 (436 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to xenial on 2019-04-15 (0 days ago)
VarLogDistupgradeTermlog:
 
mtime.conffile..etc.update-manager.release-upgrades: 2018-12-03T15:28:09.383275

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade third-party-packages xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824860

Title:
  unable to upgrade 16.04LTS to 18.04LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1824860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1790595] Re: Line 6 POD HD500 driver fault

[Губанов Сергей]

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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790595/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

[Treviño]

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 -> nautilus_recent_update_file_moved

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811900] Re: SRU 3.28 latest git to bionic

[Treviño]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811900

Title:
  SRU 3.28 latest git to bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824859] Re: package libc-bin 2.27-3ubuntu1 failed to install/upgrade: installed libc-bin package post-installation script subprocess returned error exit status 139

[Apport retracing service]

** 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 post-installation script subprocess returned error
  exit status 139

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1824859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824827] Re: tasks doing write()/fsync() hit deadlock in write_cache_pages()

[Mauricio Faria de Oliveira]

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.
https://bugs.launchpad.net/bugs/1824827

Title:
  tasks doing write()/fsync() hit deadlock in write_cache_pages()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts

[Fmstrat]

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 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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824703/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824859] [NEW] package libc-bin 2.27-3ubuntu1 failed to install/upgrade: installed libc-bin package post-installation script subprocess returned error exit status 139

[sergio]

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: amd64
Date: Sun Apr  7 11:32:52 2019
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
ErrorMessage: installed libc-bin package post-installation script subprocess 
returned error exit status 139
InstallationDate: Installed on 2018-03-30 (380 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: glibc
Title: package libc-bin 2.27-3ubuntu1 failed to install/upgrade: installed 
libc-bin package post-installation script subprocess returned error exit status 
139
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glibc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
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 post-installation script subprocess returned error
  exit status 139

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1824859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822886] Re: universe missing after bionic->cosmic do-release-upgrade

[Brian Murray]

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 files '['./DistUpgrade.cfg']'
2019-04-15 10:13:22,505 INFO uname information: 'Linux clean-bionic-amd64 
4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64'
2019-04-15 10:13:22,517 INFO apt version: '1.6.10'
2019-04-15 10:13:22,517 INFO python version: '3.6.7 (default, Oct 22 2018, 
11:32:17)
[GCC 8.2.0]'
2019-04-15 10:13:22,517 INFO release-upgrader version '18.10.11.6' started
...
2019-04-15 10:13:47,165 DEBUG examining: 'deb http://ubuntu.osuosl.org/ubuntu 
bionic main restricted multiverse'
2019-04-15 10:13:47,165 DEBUG verifySourcesListEntry: deb 
http://ubuntu.osuosl.org/ubuntu cosmic main restricted multiverse
2019-04-15 10:13:47,166 DEBUG url_downloadable: 
http://ubuntu.osuosl.org/ubuntu/dists/cosmic/Release
2019-04-15 10:13:47,166 DEBUG s='http' n='ubuntu.osuosl.org' 
p='/ubuntu/dists/cosmic/Release' q='' f=''
2019-04-15 10:13:47,330 DEBUG entry 'deb http://ubuntu.osuosl.org/ubuntu cosmic 
main restricted multiverse' updated to new dist
2019-04-15 10:13:47,331 DEBUG examining: 'deb http://ubuntu.osuosl.org/ubuntu 
bionic-updates main restricted multiverse'
2019-04-15 10:13:47,331 DEBUG entry 'deb http://ubuntu.osuosl.org/ubuntu 
cosmic-updates main restricted multiverse' updated to new dist
2019-04-15 10:13:47,331 DEBUG examining: 'deb http://ubuntu.osuosl.org/ubuntu 
bionic-security main restricted multiverse'
2019-04-15 10:13:47,332 DEBUG entry 'deb http://ubuntu.osuosl.org/ubuntu 
cosmic-security main restricted multiverse' updated to new dist
2019-04-15 10:13:47,332 DEBUG examining: 'deb http://ubuntu.osuosl.org/ubuntu 
bionic universe'
2019-04-15 10:13:47,332 DEBUG entry 'deb http://ubuntu.osuosl.org/ubuntu cosmic 
universe' updated to new dist

Setting to verification-done for bionic and cosmic.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic 
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/bugs/1822886

Title:
  universe missing after bionic->cosmic do-release-upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1822886/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 289931] Re: There is no Select All Deselect All icon; takes forever to check and uncheck everythiing

[Geoffrey Wheeler]

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
- arrow down / [Enter] repeatedly

I wanted to deselect all because I had just installed Lubuntu and there
were many updates. When I tried to update all (the default), it was very
slow and many updates were begun at the same time. When my weak and
unstable connection lost the connection, I ended up with apparently no
updates completed.  I was most successful when I did a group of about 10
or 20 MB of updates.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/289931

Title:
  There is no Select All Deselect All icon; takes forever to check and
  uncheck everythiing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-cleaner/+bug/289931/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824854] [NEW] xserver-xorg-core-hwe-16.04 does not provide xserver-xorg-core

[Claire Farron]

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: 2:1.19.6-1ubuntu4.1~16.04.2
  Version table:
 *** 2:1.19.6-1ubuntu4.1~16.04.2 500
500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status

:~$ apt-cache policy virtualbox-guest-x11
virtualbox-guest-x11:
  Installed: (none)
  Candidate: 5.1.38-dfsg-0ubuntu1.16.04.3
  Version table:
 5.1.38-dfsg-0ubuntu1.16.04.3 500
500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 
Packages
 5.1.38-dfsg-0ubuntu1.16.04.2 500
500 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 
Packages
 5.0.18-dfsg-2build1 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages

3) What I expected to happen:

I expected to be able to run sudo apt-get install virtualbox-guest-x11
and the package would install without any problems.

4) What happened instead:

:~$ sudo apt-get install virtualbox-guest-dkms virtualbox-guest-x11
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 virtualbox-guest-x11 : Depends: xorg-video-abi-20
Depends: xserver-xorg-core (>= 2:1.17.99.902)
E: Unable to correct problems, you have held broken packages.

The only conclusion that I can draw from this is that the xserver-xorg-
core-hwe-16.04 does not provide xserver-xorg-core.

This is repeatable on Ubuntu 18.04 against the xserver-xorg-core-
hwe-18.04 package.

** Affects: xorg-server-hwe-16.04 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824854

Title:
  xserver-xorg-core-hwe-16.04 does not provide xserver-xorg-core

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1824854/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824854] Re: xserver-xorg-core-hwe-16.04 does not provide xserver-xorg-core

[Claire Farron]

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 lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libxfont2 snapd-login-service xserver-xorg-legacy-hwe-16.04
Use 'sudo apt autoremove' to remove them.
Suggested packages:
  xfonts-100dpi | xfonts-75dpi
The following packages will be REMOVED
  ubuntu-desktop xorg xserver-xorg-core-hwe-16.04 xserver-xorg-hwe-16.04 
xserver-xorg-input-all-hwe-16.04 xserver-xorg-input-evdev-hwe-16.04 
xserver-xorg-input-synaptics-hwe-16.04
  xserver-xorg-input-wacom-hwe-16.04 xserver-xorg-video-all-hwe-16.04 
xserver-xorg-video-amdgpu-hwe-16.04 xserver-xorg-video-ati-hwe-16.04 
xserver-xorg-video-fbdev-hwe-16.04
  xserver-xorg-video-intel-hwe-16.04 xserver-xorg-video-nouveau-hwe-16.04 
xserver-xorg-video-qxl-hwe-16.04 xserver-xorg-video-radeon-hwe-16.04 
xserver-xorg-video-vesa-hwe-16.04
  xserver-xorg-video-vmware-hwe-16.04
The following NEW packages will be installed
  xserver-xorg-core
0 to upgrade, 1 to newly install, 18 to remove and 3 not to upgrade.
Need to get 1,344 kB of archives.
After this operation, 5,702 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824854

Title:
  xserver-xorg-core-hwe-16.04 does not provide xserver-xorg-core

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1824854/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824855] [NEW] very long delay to display login prompt if there are a large number of uncleared desktop notifications

[Steve Langasek]

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
(obfuscated) desktop notifications.  After logging in, I used the gnome-
shell interface to clear the notifications; then I locked my screen
again, at which point hitting the space bar caused the password prompt
to show up immediately.

So it looks like the time to display the password prompt might scale
linearly with the number of notifications; which is not useful, because
there is a finite number of (obfuscated!) notifications that will be
displayed on the lock screen, and AFAIK you can't interact with them
through the lock screen at all.  So we shouldn't be wasting time
processing (and presumably rendering) notifications that will never be
visible.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gdm3 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 15 09:58:23 2019
InstallationDate: Installed on 2010-09-24 (3125 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
SourcePackage: gdm3
UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824855

Title:
  very long delay to display login prompt if there are a large number of
  uncleared desktop notifications

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824855/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker

[Ubuntu Kernel Bot]

** 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 see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1822807 (xenial/linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Testing
  phase-changed: Friday, 12. April 2019 01:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030
-   regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing 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/1822808

Title:
  linux-gcp: 4.15.0-1030.32 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822808/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822872] Re: Bionic: Luminous radosgw incompatible with libssl1.1

[Eric Desrochers]

** 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
  2019-04-02 16:40:14.846424 7ff8c1736000 -1 ERROR: failed run
  
  [Test Case]
  
  1) Generate a self-signed certificate or use whatever existing SSL
  certificate already in place.
  
  2) From the radosgw node, modify "/etc/ceph/ceph.conf" as follow:
  rgw_frontends = civetweb ssl_port=443 ssl_certificate=/etc/ssl/
  
  3) Restart the daemon:
  systemctl restart ceph-radosgw@rgw.`hostname -s`
  
  4) Look logs:
  2019-04-10 12:02:53.535133 7fcd20c4e000 0 civetweb: 0x562d710ed620: load_dll: 
libcrypto.so.1.1: cannot find CRYPTO_num_locks
  
  5) Look radosgw which should FAILED to start.
  
  [Potential Regression]
  
+ * Same downgrade approach has been made for 'nodejs' via LP: #1798367
+ 
+ * Seems like civetweb is all that does SSL there, so it should be fine.
+ 
+ * Nothing can be worst than current situation, considering that civetweb
+ is non-functionnal when SSL is in used due to the incompatibility with
+ 1.1 and make radosgw daemon to fail.
+ 
  [Other Information]
  
+ * Adding the OpenSSL 1.1 support has been explore, and reveal to be 
non-trivial :
  https://github.com/civetweb/civetweb/pull/384/commits
  
https://github.com/civetweb/civetweb/commit/adac9c916fa892ec5edce7b565803f1e62d304a2
  
https://github.com/civetweb/civetweb/commit/5d83900fd29fb6fa1cd604676cb0562dc984dcc9
  
  http://docs.ceph.com/docs/bobtail/radosgw/troubleshooting/
  
  [Original Description]
  
  Bionic's radosgw package (Version 12.2.11-0ubuntu0.18.04.1 ) can't run
  on Bionic, because the version of civetweb in Luminous is incompatible
  with libssl1.1, but it's built against libssl1.1.
  
  This has been known about upstream for a while now, and as noted in the
  bug-tracker (https://tracker.ceph.com/issues/20696), it can be fixed by
  building Luminous in an environment that has only libssl1.0 available
  (or, in a more invasive manner, by incorporating a newer civetweb). A
  patch is in the tracker.ceph.com issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822872

Title:
  Bionic: Luminous radosgw incompatible with libssl1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1822872/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822808] Re: linux-gcp: 4.15.0-1030.32 -proposed tracker

[Sean Feole]

** 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:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822808/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824667] Re: Flash in Chrome does not work

[olo81]

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:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1824667/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111

[O. Emmerson]

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 would be
for you to switch to a 64-bit machine.
"

I am using 64bit Ubuntu though.

I have downloaded and compiled coreutils 8.31 to see if the command
worked for me in the upgraded version but the error remains the same.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824688

Title:
  date+%-Y -d "- N years" errors when N > 111

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1824688/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822886] Re: universe missing after bionic->cosmic do-release-upgrade

[Brian Murray]

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 '['./DistUpgrade.cfg.xenial']'
2019-04-15 09:53:30,260 INFO uname information: 'Linux clean-xenial-amd64 
4.15.0-47-generic #50~16.04.1-Ubuntu SMP Fri Mar 15 16:06:21 UTC 2019 x86_64'
2019-04-15 09:53:30,527 INFO apt version: '1.2.31'
2019-04-15 09:53:30,527 INFO python version: '3.5.2 (default, Nov 12 2018, 
13:43:14)
[GCC 5.4.0 20160609]'
2019-04-15 09:53:30,530 INFO release-upgrader version '18.04.31' started
...
2019-04-15 09:53:41,478 DEBUG examining: 'deb http://ubuntu.osuosl.org/ubuntu 
xenial main restricted multiverse'
2019-04-15 09:53:41,478 DEBUG verifySourcesListEntry: deb 
http://ubuntu.osuosl.org/ubuntu bionic main restricted multiverse
2019-04-15 09:53:41,478 DEBUG url_downloadable: 
http://ubuntu.osuosl.org/ubuntu/dists/bionic/Release
2019-04-15 09:53:41,478 DEBUG s='http' n='ubuntu.osuosl.org' 
p='/ubuntu/dists/bionic/Release' q='' f=''
2019-04-15 09:53:41,556 DEBUG entry 'deb http://ubuntu.osuosl.org/ubuntu bionic 
main restricted multiverse' updated to new dist
2019-04-15 09:53:41,556 DEBUG examining: 'deb http://ubuntu.osuosl.org/ubuntu 
xenial-updates main restricted multiverse'
2019-04-15 09:53:41,557 DEBUG entry 'deb http://ubuntu.osuosl.org/ubuntu 
bionic-updates main restricted multiverse' updated to new dist
2019-04-15 09:53:41,557 DEBUG examining: 'deb http://ubuntu.osuosl.org/ubuntu 
xenial-security main restricted multiverse'
2019-04-15 09:53:41,558 DEBUG entry 'deb http://ubuntu.osuosl.org/ubuntu 
bionic-security main restricted multiverse' updated to new dist
2019-04-15 09:53:41,558 DEBUG examining: 'deb http://ubuntu.osuosl.org/ubuntu 
xenial universe'
2019-04-15 09:53:41,558 DEBUG entry 'deb http://ubuntu.osuosl.org/ubuntu bionic 
universe' updated to new dist

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822886

Title:
  universe missing after bionic->cosmic do-release-upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1822886/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824812] Re: apparmor does not start in Disco LXD containers

[Jamie Strandboge]

** 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 not start in Disco LXD containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1824812/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824852] [NEW] linux-firmware package not available in server installer

[Matt]

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 network adapters and I
am given the option to configure the IPv4/6 networking, Create a Bond,
etc.  No matter which option I try to choose there is no way to move
forward from this screen.

Upon checking the dmesg output on tty2, I see the installer failing to
find the firmware file bnx2-mips-06-6.2.3.fw which is required for the
network adapters.  And upon looking further into the issue I discovered
this file should be in the linux-firmware package.

Now here is where it gets weird, to bypass the issue of the stuck
installer, I simply entered my BIOS and disabled my network adapters and
the installer was able to continue and I was able to get the OS
installed.  After the installer completed I entered the BIOS again and
re-enabled the network adapters to begin troubleshooting the issue, and
to my surprise on first boot of the freshly installed OS, the network
adapters worked without an apt update, upgrade or anything.  dpkg shows
linux-firmware installed.

Is the linux-firmware package simply missing from the installer image
itself?

Also I should note this issue affects the latest daily server image as
well, which I also tried.

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824852

Title:
  linux-firmware package not available in server installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1824852/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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.
https://bugs.launchpad.net/bugs/1794589

Title:
  libssl1.0-dev conflicts libssl-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823410] Re: utils.py's url_downloadable doesn't support https

[Brian Murray]

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 excerpt from /var/log/dist-upgrade/main.log:

2019-04-15 09:39:47,429 DEBUG examining: 'deb https://ubuntu.osuosl.org/ubuntu 
xenial main restricted universe multiverse'
2019-04-15 09:39:47,429 DEBUG found apt-cacher/apt-torrent style uri 
https://ubuntu.osuosl.org/ubuntu
2019-04-15 09:39:47,429 DEBUG verifySourcesListEntry: deb 
https://ubuntu.osuosl.org/ubuntu bionic main restricted universe multiverse
2019-04-15 09:39:47,429 DEBUG url_downloadable: 
https://ubuntu.osuosl.org/ubuntu/dists/bionic/Release
2019-04-15 09:39:47,429 DEBUG s='https' n='ubuntu.osuosl.org' 
p='/ubuntu/dists/bionic/Release' q='' f=''
2019-04-15 09:39:47,613 DEBUG entry 'deb https://ubuntu.osuosl.org/ubuntu 
bionic main restricted universe multiverse' updated to new dist

Setting to verification-done.

** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic 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/bugs/1823410

Title:
  utils.py's url_downloadable doesn't support https

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823410/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1815123] Re: Hardware test stress-ng-cpu-long bind failed

[Colin Ian King]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1815123/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818648] Re: [SRU] 2.38

[Launchpad Bug Tracker]

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 dev/pts/ptmx access to docker_support
- overlord/snapstate, store: set a header when auto-refreshing
- interfaces/builtin: add add exec "/" to docker-support
- cmd/snap, client, daemon, ifacestate: show a leading attribute of
  a connection
- interface: avahi-observe: Fixing socket permissions on 4.15
  kernels
- tests: check that apt works before using it
- apparmor: support AppArmor 2.13
- snapstate: restart into the snapd snap on classic
- overlord/snapstate: during refresh, re-refresh on epoch bump
- cmd, daemon: split out the common bits of mapLocal and mapRemote
- cmd/snap-confine: chown private /tmp to root.root
- cmd/snap-confine: drop uid from random /tmp name
- overlord/hookstate: apply pending transaction changes onto
  temporary configuration for snapctl get
- cmd/snap: `snap connections` command
- interfaces/greengrass_support: update accesses for GGC 1.8
- cmd/snap, daemon: make the connectivity check use GET
- interfaces/builtin,/udev: add spec support to disable udev +
  device cgroup and use it for greengrass
- interfaces/intel-mei: small follow up tweaks
- ifacestate/tests: fix/improve udev mon test
- interfaces: add multipass-support interface
- tests/main/high-user-handling: fix the test for Go 1.12
- interfaces: add new intel-mei interface
- systemd: decrease the checker counter before unlocking otherwise
  we can get spurious panics
- daemon/tests: fix race in the disconnect conflict test
- cmd/snap-confine: allow moving tasks to pids cgroup
- tests: enable opensuse tumbleweed on spread
- cmd/snap: fix `snap services` completion
- ifacestate/hotplug: integration with udev monitor
- packaging: build snapctl as a static binary
- packaging/opensuse: move most logic to snapd.mk
- overlord: fix ensure before slowness on Retry
- overlord/ifacestate: fix migration of connections on upgrade from
  ubuntu-core
- daemon, client, cmd/snap: debug GETs ask aspects, not actions
- tests/main/desktop-portal-*: fix handling of python dependencies
- interfaces/wayland: allow wayland server snaps function on classic
  too
- daemon, client, cmd/snap: snap debug base-declaration
- tests: run tests on opensuse leap 15.0 instead of 42.3
- cmd/snap: fix error messages for snapshots commands if ID is not
  uint
- interfaces/seccomp: increase filter precision
- interfaces/network-manager: no peer label check for hostname1
- tests: add a tests for xdg-desktop-portal integration
- tests: not checking 'tracking channel' after refresh core on
  nested execution
- tests: remove snapweb from tests
- snap, wrappers: support StartTimeout
- wrappers: Add an X-SnapInstanceName field to desktop files
- cmd/snap: produce better output for help on subcommands
- tests/main/nfs-support: use archive mode for creating fstab backup
- many: collect time each task runs and display it with `snap debug
  timings `
- tests: add attribution to helper script
- daemon: make ucrednetGet not loop
- squashfs: unset SOURCE_DATE_EPOCH in the TestBuildDate test
- features,cmd/libsnap: add new feature "refresh-app-awareness"
- overlord: fix random typos
- interfaces/seccomp: generate global seccomp profile
- daemon/api: fix error case for disconnect conflict
- overlord/snapstate: add some randomness to the catalog refresh
- tests: disable trusty-proposed for now
- tests: fix upgrade-from-2.15 with kernel 4.15
- interfaces/apparmor: allow sending and receiving signals from
  ourselves
- tests: split the test interfaces-many in 2 and remove snaps on
  restore
- tests: use snap which takes 15 seconds to install on retryable-
  error test
- packaging: avoid race in snapd.postinst
- overlord/snapstate: discard mount namespace when undoing 1st link
  snap
- cmd/snap-confine: allow writes to /var/lib/**
- tests: stop catalog-update test for now
- tests/main/auto-refresh-private: make sure to actually download
  with the expired macaroon
- many: save media info when installing, show it when listing
- userd: handle help urls which requires prepending XDG_DATA_DIRS
- tests: fix NFS home mocking
- tests: improve snaps-system-env test
- tests: pre-cache core on core18 systems
- interfaces/hotplug: renamed RequestedSlotSpec to ProposedSlot,
  removed Specification
- debian: ensure leftover usr.lib.snapd.snap-confine is gone
- image,cmd/snap,tests: introduce support for modern prepare-image
  --snap [=]
- 

[Bug 1764047] Re: Unable to switch realm on authentication dialog

[Launchpad Bug Tracker]

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 (lp: #1764047)

 -- Sebastien Bacher   Fri, 15 Mar 2019 00:23:01
+0100

** Changed in: openconnect (Ubuntu Bionic)
   Status: Fix Committed => 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/1764047

Title:
  Unable to switch realm on authentication dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openconnect/+bug/1764047/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818648] Re: [SRU] 2.38

[Launchpad Bug Tracker]

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 dev/pts/ptmx access to docker_support
- overlord/snapstate, store: set a header when auto-refreshing
- interfaces/builtin: add add exec "/" to docker-support
- cmd/snap, client, daemon, ifacestate: show a leading attribute of
  a connection
- interface: avahi-observe: Fixing socket permissions on 4.15
  kernels
- tests: check that apt works before using it
- apparmor: support AppArmor 2.13
- snapstate: restart into the snapd snap on classic
- overlord/snapstate: during refresh, re-refresh on epoch bump
- cmd, daemon: split out the common bits of mapLocal and mapRemote
- cmd/snap-confine: chown private /tmp to root.root
- cmd/snap-confine: drop uid from random /tmp name
- overlord/hookstate: apply pending transaction changes onto
  temporary configuration for snapctl get
- cmd/snap: `snap connections` command
- interfaces/greengrass_support: update accesses for GGC 1.8
- cmd/snap, daemon: make the connectivity check use GET
- interfaces/builtin,/udev: add spec support to disable udev +
  device cgroup and use it for greengrass
- interfaces/intel-mei: small follow up tweaks
- ifacestate/tests: fix/improve udev mon test
- interfaces: add multipass-support interface
- tests/main/high-user-handling: fix the test for Go 1.12
- interfaces: add new intel-mei interface
- systemd: decrease the checker counter before unlocking otherwise
  we can get spurious panics
- daemon/tests: fix race in the disconnect conflict test
- cmd/snap-confine: allow moving tasks to pids cgroup
- tests: enable opensuse tumbleweed on spread
- cmd/snap: fix `snap services` completion
- ifacestate/hotplug: integration with udev monitor
- packaging: build snapctl as a static binary
- packaging/opensuse: move most logic to snapd.mk
- overlord: fix ensure before slowness on Retry
- overlord/ifacestate: fix migration of connections on upgrade from
  ubuntu-core
- daemon, client, cmd/snap: debug GETs ask aspects, not actions
- tests/main/desktop-portal-*: fix handling of python dependencies
- interfaces/wayland: allow wayland server snaps function on classic
  too
- daemon, client, cmd/snap: snap debug base-declaration
- tests: run tests on opensuse leap 15.0 instead of 42.3
- cmd/snap: fix error messages for snapshots commands if ID is not
  uint
- interfaces/seccomp: increase filter precision
- interfaces/network-manager: no peer label check for hostname1
- tests: add a tests for xdg-desktop-portal integration
- tests: not checking 'tracking channel' after refresh core on
  nested execution
- tests: remove snapweb from tests
- snap, wrappers: support StartTimeout
- wrappers: Add an X-SnapInstanceName field to desktop files
- cmd/snap: produce better output for help on subcommands
- tests/main/nfs-support: use archive mode for creating fstab backup
- many: collect time each task runs and display it with `snap debug
  timings `
- tests: add attribution to helper script
- daemon: make ucrednetGet not loop
- squashfs: unset SOURCE_DATE_EPOCH in the TestBuildDate test
- features,cmd/libsnap: add new feature "refresh-app-awareness"
- overlord: fix random typos
- interfaces/seccomp: generate global seccomp profile
- daemon/api: fix error case for disconnect conflict
- overlord/snapstate: add some randomness to the catalog refresh
- tests: disable trusty-proposed for now
- tests: fix upgrade-from-2.15 with kernel 4.15
- interfaces/apparmor: allow sending and receiving signals from
  ourselves
- tests: split the test interfaces-many in 2 and remove snaps on
  restore
- tests: use snap which takes 15 seconds to install on retryable-
  error test
- packaging: avoid race in snapd.postinst
- overlord/snapstate: discard mount namespace when undoing 1st link
  snap
- cmd/snap-confine: allow writes to /var/lib/**
- tests: stop catalog-update test for now
- tests/main/auto-refresh-private: make sure to actually download
  with the expired macaroon
- many: save media info when installing, show it when listing
- userd: handle help urls which requires prepending XDG_DATA_DIRS
- tests: fix NFS home mocking
- tests: improve snaps-system-env test
- tests: pre-cache core on core18 systems
- interfaces/hotplug: renamed RequestedSlotSpec to ProposedSlot,
  removed Specification
- debian: ensure leftover usr.lib.snapd.snap-confine is gone
- image,cmd/snap,tests: introduce support for modern prepare-image
  --snap [=]
- 

[Bug 1818648] Re: [SRU] 2.38

[Launchpad Bug Tracker]

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 docker_support
- overlord/snapstate, store: set a header when auto-refreshing
- interfaces/builtin: add add exec "/" to docker-support
- cmd/snap, client, daemon, ifacestate: show a leading attribute of
  a connection
- interface: avahi-observe: Fixing socket permissions on 4.15
  kernels
- tests: check that apt works before using it
- apparmor: support AppArmor 2.13
- snapstate: restart into the snapd snap on classic
- overlord/snapstate: during refresh, re-refresh on epoch bump
- cmd, daemon: split out the common bits of mapLocal and mapRemote
- cmd/snap-confine: chown private /tmp to root.root
- cmd/snap-confine: drop uid from random /tmp name
- overlord/hookstate: apply pending transaction changes onto
  temporary configuration for snapctl get
- cmd/snap: `snap connections` command
- interfaces/greengrass_support: update accesses for GGC 1.8
- cmd/snap, daemon: make the connectivity check use GET
- interfaces/builtin,/udev: add spec support to disable udev +
  device cgroup and use it for greengrass
- interfaces/intel-mei: small follow up tweaks
- ifacestate/tests: fix/improve udev mon test
- interfaces: add multipass-support interface
- tests/main/high-user-handling: fix the test for Go 1.12
- interfaces: add new intel-mei interface
- systemd: decrease the checker counter before unlocking otherwise
  we can get spurious panics
- daemon/tests: fix race in the disconnect conflict test
- cmd/snap-confine: allow moving tasks to pids cgroup
- tests: enable opensuse tumbleweed on spread
- cmd/snap: fix `snap services` completion
- ifacestate/hotplug: integration with udev monitor
- packaging: build snapctl as a static binary
- packaging/opensuse: move most logic to snapd.mk
- overlord: fix ensure before slowness on Retry
- overlord/ifacestate: fix migration of connections on upgrade from
  ubuntu-core
- daemon, client, cmd/snap: debug GETs ask aspects, not actions
- tests/main/desktop-portal-*: fix handling of python dependencies
- interfaces/wayland: allow wayland server snaps function on classic
  too
- daemon, client, cmd/snap: snap debug base-declaration
- tests: run tests on opensuse leap 15.0 instead of 42.3
- cmd/snap: fix error messages for snapshots commands if ID is not
  uint
- interfaces/seccomp: increase filter precision
- interfaces/network-manager: no peer label check for hostname1
- tests: add a tests for xdg-desktop-portal integration
- tests: not checking 'tracking channel' after refresh core on
  nested execution
- tests: remove snapweb from tests
- snap, wrappers: support StartTimeout
- wrappers: Add an X-SnapInstanceName field to desktop files
- cmd/snap: produce better output for help on subcommands
- tests/main/nfs-support: use archive mode for creating fstab backup
- many: collect time each task runs and display it with `snap debug
  timings `
- tests: add attribution to helper script
- daemon: make ucrednetGet not loop
- squashfs: unset SOURCE_DATE_EPOCH in the TestBuildDate test
- features,cmd/libsnap: add new feature "refresh-app-awareness"
- overlord: fix random typos
- interfaces/seccomp: generate global seccomp profile
- daemon/api: fix error case for disconnect conflict
- overlord/snapstate: add some randomness to the catalog refresh
- tests: disable trusty-proposed for now
- tests: fix upgrade-from-2.15 with kernel 4.15
- interfaces/apparmor: allow sending and receiving signals from
  ourselves
- tests: split the test interfaces-many in 2 and remove snaps on
  restore
- tests: use snap which takes 15 seconds to install on retryable-
  error test
- packaging: avoid race in snapd.postinst
- overlord/snapstate: discard mount namespace when undoing 1st link
  snap
- cmd/snap-confine: allow writes to /var/lib/**
- tests: stop catalog-update test for now
- tests/main/auto-refresh-private: make sure to actually download
  with the expired macaroon
- many: save media info when installing, show it when listing
- userd: handle help urls which requires prepending XDG_DATA_DIRS
- tests: fix NFS home mocking
- tests: improve snaps-system-env test
- tests: pre-cache core on core18 systems
- interfaces/hotplug: renamed RequestedSlotSpec to ProposedSlot,
  removed Specification
- debian: ensure leftover usr.lib.snapd.snap-confine is gone
- image,cmd/snap,tests: introduce support for modern prepare-image
  --snap [=]
- overlord/ifacestate: 

[Bug 1824806] Re: Network stops working after systemd update

[Dan Streetman]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824806

Title:
  Network stops working after systemd update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824806/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818648] Re: [SRU] 2.38

[Launchpad Bug Tracker]

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 dev/pts/ptmx access to docker_support
- overlord/snapstate, store: set a header when auto-refreshing
- interfaces/builtin: add add exec "/" to docker-support
- cmd/snap, client, daemon, ifacestate: show a leading attribute of
  a connection
- interface: avahi-observe: Fixing socket permissions on 4.15
  kernels
- tests: check that apt works before using it
- apparmor: support AppArmor 2.13
- snapstate: restart into the snapd snap on classic
- overlord/snapstate: during refresh, re-refresh on epoch bump
- cmd, daemon: split out the common bits of mapLocal and mapRemote
- cmd/snap-confine: chown private /tmp to root.root
- cmd/snap-confine: drop uid from random /tmp name
- overlord/hookstate: apply pending transaction changes onto
  temporary configuration for snapctl get
- cmd/snap: `snap connections` command
- interfaces/greengrass_support: update accesses for GGC 1.8
- cmd/snap, daemon: make the connectivity check use GET
- interfaces/builtin,/udev: add spec support to disable udev +
  device cgroup and use it for greengrass
- interfaces/intel-mei: small follow up tweaks
- ifacestate/tests: fix/improve udev mon test
- interfaces: add multipass-support interface
- tests/main/high-user-handling: fix the test for Go 1.12
- interfaces: add new intel-mei interface
- systemd: decrease the checker counter before unlocking otherwise
  we can get spurious panics
- daemon/tests: fix race in the disconnect conflict test
- cmd/snap-confine: allow moving tasks to pids cgroup
- tests: enable opensuse tumbleweed on spread
- cmd/snap: fix `snap services` completion
- ifacestate/hotplug: integration with udev monitor
- packaging: build snapctl as a static binary
- packaging/opensuse: move most logic to snapd.mk
- overlord: fix ensure before slowness on Retry
- overlord/ifacestate: fix migration of connections on upgrade from
  ubuntu-core
- daemon, client, cmd/snap: debug GETs ask aspects, not actions
- tests/main/desktop-portal-*: fix handling of python dependencies
- interfaces/wayland: allow wayland server snaps function on classic
  too
- daemon, client, cmd/snap: snap debug base-declaration
- tests: run tests on opensuse leap 15.0 instead of 42.3
- cmd/snap: fix error messages for snapshots commands if ID is not
  uint
- interfaces/seccomp: increase filter precision
- interfaces/network-manager: no peer label check for hostname1
- tests: add a tests for xdg-desktop-portal integration
- tests: not checking 'tracking channel' after refresh core on
  nested execution
- tests: remove snapweb from tests
- snap, wrappers: support StartTimeout
- wrappers: Add an X-SnapInstanceName field to desktop files
- cmd/snap: produce better output for help on subcommands
- tests/main/nfs-support: use archive mode for creating fstab backup
- many: collect time each task runs and display it with `snap debug
  timings `
- tests: add attribution to helper script
- daemon: make ucrednetGet not loop
- squashfs: unset SOURCE_DATE_EPOCH in the TestBuildDate test
- features,cmd/libsnap: add new feature "refresh-app-awareness"
- overlord: fix random typos
- interfaces/seccomp: generate global seccomp profile
- daemon/api: fix error case for disconnect conflict
- overlord/snapstate: add some randomness to the catalog refresh
- tests: disable trusty-proposed for now
- tests: fix upgrade-from-2.15 with kernel 4.15
- interfaces/apparmor: allow sending and receiving signals from
  ourselves
- tests: split the test interfaces-many in 2 and remove snaps on
  restore
- tests: use snap which takes 15 seconds to install on retryable-
  error test
- packaging: avoid race in snapd.postinst
- overlord/snapstate: discard mount namespace when undoing 1st link
  snap
- cmd/snap-confine: allow writes to /var/lib/**
- tests: stop catalog-update test for now
- tests/main/auto-refresh-private: make sure to actually download
  with the expired macaroon
- many: save media info when installing, show it when listing
- userd: handle help urls which requires prepending XDG_DATA_DIRS
- tests: fix NFS home mocking
- tests: improve snaps-system-env test
- tests: pre-cache core on core18 systems
- interfaces/hotplug: renamed RequestedSlotSpec to ProposedSlot,
  removed Specification
- debian: ensure leftover usr.lib.snapd.snap-confine is gone
- image,cmd/snap,tests: introduce support for modern prepare-image
  --snap [=]
- 

[Bug 1818648] Update Released

[Łukasz Zemczak]

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 regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818648

Title:
  [SRU] 2.38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1818648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824827] Re: tasks doing write()/fsync() hit deadlock in write_cache_pages()

[Mauricio Faria de Oliveira]

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.
https://bugs.launchpad.net/bugs/1824827

Title:
  tasks doing write()/fsync() hit deadlock in write_cache_pages()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824827] Re: tasks doing write()/fsync() hit deadlock in write_cache_pages()

[Mauricio Faria de Oliveira]

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 verification failed: signature and/or 
required key missing - tainting kernel

[  169.153539] mod_init():158 :: hello
[  169.154744] mod_init():190 :: kernel version: test/-18/cosmic

[  169.177027] Program running, TID = 2497
[  169.177978] kp1_pre_handler():070 :: state 0  :: pid =   2497, mapping = 
0x993df9136fb0, comm = 'test'
[  169.181080] kp1_pre_handler():079 :: state 0 -> 1 :: pid =   2497, mapping = 
0x993df9136fb0
[  169.183355] kp2_pre_handler():119 :: state 1  :: pid =   2497, page 
index = 1
[  169.185616] kp3_pre_handler():144 :: state 1  :: pid =   2497, page 
index = 1, calling writepage()
[  169.187779] kp2_pre_handler():119 :: state 1  :: pid =   2497, page 
index = 2
[  169.189186] kp3_pre_handler():144 :: state 1  :: pid =   2497, page 
index = 2, calling writepage()

[  170.194880] Thread 0 running, TID = 2498!
[  170.200011] kp1_pre_handler():070 :: state 1  :: pid =  7, mapping = 
0x993df9136fb0, comm = 'kworker/u4:0'
[  170.217616] kp1_pre_handler():101 :: state 1 -> 2 :: pid =  7, mapping = 
0x993df9136fb0, comm ('kworker/u4:0') is kworker AND wbc->range_cyclic 
(0x1) is true AND mapping->writeback_index (0x2) is 0x2.
[  170.238633] kp2_pre_handler():119 :: state 2  :: pid =  7, page 
index = 2
[  170.248024] kp3_pre_handler():144 :: state 2  :: pid =  7, page 
index = 2, calling writepage()
[  170.261141] kp1_pre_handler():070 :: state 2  :: pid =  7, mapping = 
0x993df9136fb0, comm = 'kworker/u4:0'
[  170.272150] kp2_pre_handler():119 :: state 2  :: pid =  7, page 
index = 1
[  170.279860] kp2_pre_handler():123 :: state 2 -> 3 :: pid =  7, page 
index = 1, spin 5 seconds before lock_page()...

[  171.195090] Thread 1 running, TID = 2499!
[  171.196182] kp1_pre_handler():070 :: state 3  :: pid =   2499, mapping = 
0x993df9136fb0, comm = 'test'
[  171.198609] kp2_pre_handler():119 :: state 3  :: pid =   2499, page 
index = 1
[  171.200358] kp3_pre_handler():144 :: state 3  :: pid =   2499, page 
index = 1, calling writepage()
[  171.203717] kp2_pre_handler():119 :: state 3  :: pid =   2499, page 
index = 2

[  172.195297] Thread 2 running, TID = 2500!
[  172.196387] kp1_pre_handler():070 :: state 3  :: pid =   2500, mapping = 
0x993df9136fb0, comm = 'test'
[  172.198673] kp2_pre_handler():119 :: state 3  :: pid =   2500, page 
index = 1
[  175.252161] kp2_pre_handler():127 :: state 3 -> 4 :: pid =  7, page 
index = 1, spun 5 seconds before lock_page().

[  175.254922] kp3_pre_handler():144 :: state 4  :: pid =   2499, page 
index = 2, calling writepage()
[  175.256849] kp3_pre_handler():144 :: state 4  :: pid =   2500, page 
index = 1, calling writepage()
[  175.259166] kp2_pre_handler():119 :: state 4  :: pid =   2500, page 
index = 2
[  175.273178] mod_exit():213 :: bye

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824827

Title:
  tasks doing write()/fsync() hit deadlock in write_cache_pages()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824827] Re: tasks doing write()/fsync() hit deadlock in write_cache_pages()

[Mauricio Faria de Oliveira]

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 failed: signature and/or 
required key missing - tainting kernel

[  654.497033] mod_init():158 :: hello
[  654.497976] mod_init():183 :: kernel version: orig/-18/cosmic

[  694.254271] Program running, TID = 3292
[  694.256600] kp1_pre_handler():070 :: state 0  :: pid =   3292, mapping = 
0x962333263730, comm = 'test'
[  694.260870] kp1_pre_handler():079 :: state 0 -> 1 :: pid =   3292, mapping = 
0x962333263730
[  694.262710] kp2_pre_handler():119 :: state 1  :: pid =   3292, page 
index = 1
[  694.264264] kp3_pre_handler():144 :: state 1  :: pid =   3292, page 
index = 1, calling writepage()
[  694.266641] kp2_pre_handler():119 :: state 1  :: pid =   3292, page 
index = 2
[  694.268456] kp3_pre_handler():144 :: state 1  :: pid =   3292, page 
index = 2, calling writepage()

[  695.276320] Thread 0 running, TID = 3293!
[  695.281210] kp1_pre_handler():070 :: state 1  :: pid =   1165, mapping = 
0x962333263730, comm = 'kworker/u4:2'
[  695.299026] kp1_pre_handler():101 :: state 1 -> 2 :: pid =   1165, mapping = 
0x962333263730, comm ('kworker/u4:2') is kworker AND wbc->range_cyclic 
(0x1) is true AND mapping->writeback_index (0x2) is 0x2.
[  695.314808] kp2_pre_handler():119 :: state 2  :: pid =   1165, page 
index = 2
[  695.322822] kp3_pre_handler():144 :: state 2  :: pid =   1165, page 
index = 2, calling writepage()

[  695.330308] kp2_pre_handler():119 :: state 2  :: pid =   1165, page 
index = 1
[  695.334355] kp2_pre_handler():123 :: state 2 -> 3 :: pid =   1165, page 
index = 1, spin 5 seconds before lock_page()...

[  696.283747] Thread 1 running, TID = 3295!
[  696.284623] kp1_pre_handler():070 :: state 3  :: pid =   3295, mapping = 
0x962333263730, comm = 'test'
[  696.286726] kp2_pre_handler():119 :: state 3  :: pid =   3295, page 
index = 1
[  696.288392] kp3_pre_handler():144 :: state 3  :: pid =   3295, page 
index = 1, calling writepage()
[  696.290018] kp2_pre_handler():119 :: state 3  :: pid =   3295, page 
index = 2

[  697.283941] Thread 2 running, TID = 3296!
[  697.284859] kp1_pre_handler():070 :: state 3  :: pid =   3296, mapping = 
0x962333263730, comm = 'test'
[  697.287246] kp2_pre_handler():119 :: state 3  :: pid =   3296, page 
index = 1
[  700.302756] kp2_pre_handler():127 :: state 3 -> 4 :: pid =   1165, page 
index = 1, spun 5 seconds before lock_page().

[  715.716717] INFO: task kworker/u4:2:1165 blocked for more than 10 seconds.
[  715.725486]   Tainted: G   OE 4.18.0-18-generic #19-Ubuntu
[  715.732832] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  715.740500] kworker/u4:2D0  1165  2 0x8000
[  715.745615] Workqueue: writeback wb_workfn (flush-7:1)
[  715.750736] Call Trace:
[  715.753270]  __schedule+0x29e/0x840
[  715.756493]  schedule+0x2c/0x80
[  715.759369]  io_schedule+0x16/0x40
[  715.762044]  __lock_page+0x101/0x150
[  715.764729]  ? page_cache_tree_insert+0xe0/0xe0
[  715.773625]  write_cache_pages+0x283/0x4e0
[  715.782547]  ? xfs_vm_readpage+0x80/0x80 [xfs]
[  715.792525]  ? xfs_vm_readpage+0x80/0x80 [xfs]
[  715.798175]  ? write_cache_pages+0x5/0x4e0
[  715.803180]  xfs_vm_writepages+0x6b/0xa0 [xfs]
[  715.807087]  do_writepages+0x41/0xd0
[  715.810416]  __writeback_single_inode+0x40/0x360
[  715.813588]  ? fprop_fraction_percpu+0x26/0x80
[  715.816686]  writeback_sb_inodes+0x211/0x520
[  715.819584]  __writeback_inodes_wb+0x67/0xb0
[  715.822661]  wb_writeback+0x25f/0x2f0
[  715.824963]  ? get_nr_dirty_inodes+0x46/0x70
[  715.827180]  wb_workfn+0x175/0x3f0
[  715.829225]  process_one_work+0x20f/0x410
[  715.830964]  worker_thread+0x34/0x400
[  715.832646]  kthread+0x120/0x140
[  715.834551]  ? pwq_unbound_release_workfn+0xd0/0xd0
[  715.836902]  ? kthread_bind+0x40/0x40
[  715.838772]  ret_from_fork+0x35/0x40
[  715.840579] INFO: task test:3293 blocked for more than 10 seconds.
[  715.842927]   Tainted: G   OE 4.18.0-18-generic #19-Ubuntu
[  715.845279] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  715.847771] testD0  3293   3291 0x
[  715.849826] Call Trace:
[  715.851266]  __schedule+0x29e/0x840
[  715.853289]  schedule+0x2c/0x80
[  715.855069]  wb_wait_for_completion+0x64/0x90
[  715.857179]  ? wait_woken+0x80/0x80
[  715.858973]  sync_inodes_sb+0xc7/0x290
[  715.860754]  sync_inodes_one_sb+0x15/0x20
[  715.862383]  iterate_supers+0xaa/0x100
[  715.863938]  ? default_file_splice_write+0x30/0x30
[  715.865666]  ksys_sync+0x42/0xb0
[  715.867082]  __ia32_sys_sync+0xe/0x20
[  715.869122]  do_syscall_64+0x5a/0x110
[  715.871041]  

[Bug 1824827] Re: tasks doing write()/fsync() hit deadlock in write_cache_pages()

[Mauricio Faria de Oliveira]

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.
https://bugs.launchpad.net/bugs/1824827

Title:
  tasks doing write()/fsync() hit deadlock in write_cache_pages()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1815123] Update Released

[Łukasz Zemczak]

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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1815123/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1764047] Update Released

[Łukasz Zemczak]

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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764047

Title:
  Unable to switch realm on authentication dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openconnect/+bug/1764047/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1641308] Re: Partitions display wrong in gnome -disks - ok in gparted

[Colin Watson]

** 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.
https://bugs.launchpad.net/bugs/1641308

Title:
  Partitions display wrong in gnome -disks - ok in gparted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1641308/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816808] Update Released

[Łukasz Zemczak]

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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816808

Title:
  [disco] OSK does not appear under wayland when a text-entry is focused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1816808/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1815123] Re: Hardware test stress-ng-cpu-long bind failed

[Launchpad Bug Tracker]

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 number of NUMA nodes
  [Colin Ian King]
  * stress-af-alg: check for EBUSY bind failures (LP: #1815123)
- backport of upstream prerequisits and the fix:
  13c4c58d0150 expand error message to capture more information
  39184c74f1e0 forgot to add in \n
  aed180cb7b2f make ENOKEY a non-critical failure
  7f1a617adcd6 skip over ciphers that may not exist
  88cbe87a3cc1 fix errno = ENOENT assignment, should be == comparison
  3ec28f2f5438 return EXIT_NOT_IMPLEMENTED if protocol is not supported
  a5c2cb02e8ed stress-af-alg: check for EBUSY bind failures

 -- Colin King   Thu, 4 Apr 2019 17:47:11
+0100

** Changed in: stress-ng (Ubuntu Bionic)
   Status: Fix Committed => 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 notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1815123/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823208] Re: NUMA stress test fails, requires upstream fix stress-numa: fix calculation of max nodes

[Launchpad Bug Tracker]

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 number of NUMA nodes
  [Colin Ian King]
  * stress-af-alg: check for EBUSY bind failures (LP: #1815123)
- backport of upstream prerequisits and the fix:
  13c4c58d0150 expand error message to capture more information
  39184c74f1e0 forgot to add in \n
  aed180cb7b2f make ENOKEY a non-critical failure
  7f1a617adcd6 skip over ciphers that may not exist
  88cbe87a3cc1 fix errno = ENOENT assignment, should be == comparison
  3ec28f2f5438 return EXIT_NOT_IMPLEMENTED if protocol is not supported
  a5c2cb02e8ed stress-af-alg: check for EBUSY bind failures

 -- Colin King   Thu, 4 Apr 2019 17:47:11
+0100

** Changed in: stress-ng (Ubuntu Bionic)
   Status: Fix Committed => 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/1823208

Title:
  NUMA stress test fails, requires upstream fix stress-numa: fix
  calculation of max nodes

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1823208/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

[Launchpad Bug Tracker]

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 2019 15:59:08 +0100

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822341

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818929] Update Released

[Łukasz Zemczak]

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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818929

Title:
  shim-signed: missing versioned dep on sbsigntool (>= 0.6-0ubuntu10.1)
  package shim-signed 1.33.1~16.04.4+15+1533136590.3beb971-0ubuntu1
  failed to install/upgrade: sub-processo script post-installation
  instalado retornou estado de saída de erro 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1818929/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818929] Re: shim-signed: missing versioned dep on sbsigntool (>= 0.6-0ubuntu10.1) package shim-signed 1.33.1~16.04.4+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: sub-processo script

[Launchpad Bug Tracker]

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.
(LP: #1818929)

 -- Mathieu Trudel-Lapierre   Mon, 01 Apr 2019
12:20:03 -0400

** Changed in: shim-signed (Ubuntu Trusty)
   Status: Fix Committed => 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/1818929

Title:
  shim-signed: missing versioned dep on sbsigntool (>= 0.6-0ubuntu10.1)
  package shim-signed 1.33.1~16.04.4+15+1533136590.3beb971-0ubuntu1
  failed to install/upgrade: sub-processo script post-installation
  instalado retornou estado de saída de erro 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1818929/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816808] Re: [disco] OSK does not appear under wayland when a text-entry is focused

[Launchpad Bug Tracker]

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, which caused the reversal of
  this same patch in version 0.34-1ubuntu1.2, has now been fixed.)

 -- Gunnar Hjalmarsson   Wed, 03 Apr 2019 19:07:00
+0200

** Changed in: im-config (Ubuntu Bionic)
   Status: Fix Committed => 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/1816808

Title:
  [disco] OSK does not appear under wayland when a text-entry is focused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1816808/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818929] Re: shim-signed: missing versioned dep on sbsigntool (>= 0.6-0ubuntu10.1) package shim-signed 1.33.1~16.04.4+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: sub-processo script

[Launchpad Bug Tracker]

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.
(LP: #1818929)

 -- Mathieu Trudel-Lapierre   Mon, 01 Apr 2019
12:15:21 -0400

** Changed in: shim-signed (Ubuntu Xenial)
   Status: Fix Committed => 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/1818929

Title:
  shim-signed: missing versioned dep on sbsigntool (>= 0.6-0ubuntu10.1)
  package shim-signed 1.33.1~16.04.4+15+1533136590.3beb971-0ubuntu1
  failed to install/upgrade: sub-processo script post-installation
  instalado retornou estado de saída de erro 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1818929/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

[Launchpad Bug Tracker]

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 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-meta (Ubuntu Xenial)
   Status: Fix Committed => 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/1822341

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823410] Re: utils.py's url_downloadable doesn't support https

[Brian Murray]

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 excerpt from /var/log/dist-upgrade/main.log:


2019-04-15 09:15:10,252 DEBUG examining: 'deb https://ubuntu.osuosl.org/ubuntu 
bionic main restricted universe multiverse'
2019-04-15 09:15:10,253 DEBUG found apt-cacher/apt-torrent style uri 
https://ubuntu.osuosl.org/ubuntu
2019-04-15 09:15:10,253 DEBUG verifySourcesListEntry: deb 
https://ubuntu.osuosl.org/ubuntu cosmic main restricted universe multiverse
2019-04-15 09:15:10,253 DEBUG url_downloadable: 
https://ubuntu.osuosl.org/ubuntu/dists/cosmic/Release
2019-04-15 09:15:10,253 DEBUG s='https' n='ubuntu.osuosl.org' 
p='/ubuntu/dists/cosmic/Release' q='' f=''
2019-04-15 09:15:10,623 DEBUG entry 'deb https://ubuntu.osuosl.org/ubuntu 
cosmic main restricted universe multiverse' updated to new dist

The "apt-cacher/apt-torrent" message is a bit strange but it worked.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823410

Title:
  utils.py's url_downloadable doesn't support https

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823410/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824849] [NEW] Xorg freeze

[Joris]

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: Linux 4.15.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Apr 15 11:53:04 2019
DistUpgraded: 2019-03-04 16:15:30,619 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.15.0-47-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-48-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation GK107 [NVS 510] [10de:0967]
InstallationDate: Installed on 2016-08-18 (970 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 
1576)
 Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
 Bus 001 Device 002: ID 1050:0116 Yubico.com Yubikey NEO(-N) OTP+U2F+CCID
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision Tower 3620
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=UUID=9dad6725-3b16-46e0-806f-31fdb2d56121 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to bionic on 2019-03-04 (41 days ago)
dmi.bios.date: 05/26/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.6
dmi.board.name: 09WH54
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA01:cvnDellInc.:ct6:cvr:
dmi.product.name: Precision Tower 3620
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic freeze third-party-packages ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824849

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1824849/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824703] Re: Intel 8260 Bluetooth non-functioning, command timeouts

[Kai-Heng Feng]

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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824703/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818680] Re: booting should succeed even if vault is unavailable

[Launchpad Bug Tracker]

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
target which blocks server boot in the event that the Vault deployment
being used is not accessible (LP: #1818680).

 -- James Page   Thu, 07 Mar 2019 07:44:58 +

** Changed in: vaultlocker (Ubuntu Cosmic)
   Status: Fix Committed => 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/1818680

Title:
  booting should succeed even if vault is unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1818680/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dimitri John Ledkov]

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 headers and the libssl.so/libcrypto.so
symlink.

If you are using nodejs 8.x you do want to build with libssl1.0-dev,
ideally in a chroot / container.

If you are using nodejs 10.x you do want to build with libssl-dev (>=
1.1.0), ideally in a chroot / container.

Thus everything is setup, intentially, correct to enforce correct
openssl ABIs.

** Changed in: nodejs (Ubuntu Bionic)
   Status: Confirmed => Invalid

** Changed in: nodejs (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: openssl1.0 (Ubuntu)
   Status: Won't Fix => Invalid

** Changed in: openssl1.0 (Ubuntu Bionic)
   Status: Won't Fix => Invalid

** Changed in: openssl1.0 (Ubuntu Cosmic)
   Status: Won't Fix => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589

Title:
  libssl1.0-dev conflicts libssl-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824835] Re: linux-gcp: 5.0.0-1004.4 -proposed tracker

[Ubuntu Kernel Bot]

** 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 --
  kernel-stable-master-bug: 1824819
- phase: Holding before Packaging
- phase-changed: Monday, 15. April 2019 15:41 UTC
+ phase: Packaging
+ phase-changed: Monday, 15. April 2019 16:09 UTC
  reason:
-   prepare-package: Stalled -- waiting for master bug
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824835

Title:
  linux-gcp: 5.0.0-1004.4 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824835/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dimitri John Ledkov]

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, 
python2.7 | nodejs

note the bogus "libssl-dev | nodejs" which is quite bad.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589

Title:
  libssl1.0-dev conflicts libssl-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824835] Re: linux-gcp: 5.0.0-1004.4 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** 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) => Thadeu Lima de 
Souza Cascardo (cascardo)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824835

Title:
  linux-gcp: 5.0.0-1004.4 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824835/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824667] Re: Flash in Chrome does not work

[Paul White]

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 Ubuntu.
https://bugs.launchpad.net/bugs/1824667

Title:
  Flash in Chrome does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1824667/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822872] Re: Bionic: Luminous radosgw incompatible with libssl1.1

[Eric Desrochers]

# 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" [Medium,Confirmed]
[11:47:10]  slashd, jamespage - libssl/libcrypto 1.0 and 1.1 are 
coinstallable and both are support in bionic, in main from now and until 
forever.
[11:47:13]  so what's broken?
[11:48:41]  slashd, jamespage - sound slike load_dll should be dll 
opening libcrypto.so.1.0 if that's what it expects?
[11:50:30]  slashd, jamespage - imho we should builddepend on libssl1.0 
and set CIVETWEB_SSL_SSL_LIB and CIVETWEB_SSL_CRYPTO_LIB to versioned sonames 
of libssl.so.1.0 and libcrypto.so.1.0
[11:52:38]  xnox, slashd: tbh I think that's fine
[11:52:57]  I'm easy either way - slashd are you ok to SRU that?
[11:53:21]  jamespage, yeah I can SRU the libssl-dev downgrade to 1.0
[11:53:31] jamespage, well reading the code, it sounds slightly harder. 
cause WITH_RADOSGW tries to build with SSL_INCLUDE_DIR
[11:54:35] slashd, if it works. cause it does look that radosgw, rgw, 
civetweb all need to use libssl1.0-dev then.
[11:55:11] slashd, ah, and that's all that does ssl there, so it's fine.
[12:04:48]  slashd, and we reverted and forced to use libssl1.0-dev with 
nodejs 8 in bionic
[12:05:01]  slashd, and one should use libssl-dev (aka 1.1) with nodejs 
in disco.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822872

Title:
  Bionic: Luminous radosgw incompatible with libssl1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1822872/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

[Brian Murray]

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: 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/bugs/1658188

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1658188/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823363] Re: Running "Junk Mail Controls" does not appear in Activity Manager

[Bug Watch Updater]

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
https://help.launchpad.net/InterBugTracking.


On 2019-04-15T15:49:32+00:00 Paul White wrote:

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Ubuntu Chromium/73.0.3683.86 Chrome/73.0.3683.86
Safari/537.36

Steps to reproduce:

>From the 'Tools' menu, run "Junk Mail Controls"

Originally reported at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1823363


Actual results:

Process does not appear in Activity Manager



Expected results:

Process should appear in Activity Manager

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1823363/comments/4


** Changed in: thunderbird
   Status: Unknown => Confirmed

** Changed in: thunderbird
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823363

Title:
  Running "Junk Mail Controls" does not appear in Activity Manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1823363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1737012] Re: Chromium random segfaults: error 4 in libnspr4.so

[Mikhail Novosyolov]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1737012/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823410] Re: utils.py's url_downloadable doesn't support https

[Brian Murray]

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:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/u/update-manager/20190410_183044_9a12d@/log.gz

Bionic:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/update-manager/20190410_183008_84ba1@/log.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823410

Title:
  utils.py's url_downloadable doesn't support https

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823410/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824177] Re: dmesg spammed with nvidia-nvlink messages during install

[Ubuntu QA Website]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824177

Title:
  dmesg spammed with nvidia-nvlink messages during install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1824177/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs