[Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

[Treviño]

Some gdb debugging is

#1  0x7f3abc9a1bc8 in st_label_set_text (label=0x555b3f768d10, 
text=0x555b5369d360 "...")
at ../../gnome-shell/src/st/st-label.c:331
331   ctext = CLUTTER_TEXT (priv->label);
(gdb) list
326 
327   g_return_if_fail (ST_IS_LABEL (label));
328   g_return_if_fail (text != NULL);
329 
330   priv = label->priv;
331   ctext = CLUTTER_TEXT (priv->label);
332 
333   if (clutter_text_get_editable (ctext) ||
334   g_strcmp0 (clutter_text_get_text (ctext), text) != 0)
335 {
(gdb) print label
$1 = (StLabel *) 0x555b3f768d10
(gdb) print *label
$2 = {parent_instance = {parent_instance = {parent_instance = {g_type_instance 
= {g_class = 0x555b3e5ea510}, 
ref_count = 1, qdata = 0x555b3f759800}, flags = 0, private_flags = 0, 
priv = 0x555b3f7689f0}}, 
  priv = 0x555b3f7688b0}
(gdb) print *label->priv
$3 = {label = 0x555b3f712210, text_shadow_pipeline = 0x0, shadow_width = -1, 
shadow_height = -1}
(gdb) print *label->priv->labe
There is no member named labe.
(gdb) print *label->priv->label
$4 = {parent_instance = {g_type_instance = {g_class = 0x7f3abdf80be0
 }, ref_count = 
1102656128, qdata = 0x30}, flags = 113, 
  private_flags = 0, priv = 0x68733b6572616873}

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

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

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

[Bug 1771598] [NEW] package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1

[Mahesh]

Public bug reported:

Hi, I tried editing the sudoers that is located on my Ubuntu setup on
Virtual Box, it didn't allow me to update sudoers due to permission
issues. I changed the permission of sudoers to 777 and was able to add
my user name into it, however after that I was not able to run few
commands hence I got instruction from google to purge and re-install it
however it started throwing error afterwards however I noticed that I
was able to remove my username entries from it before re-installing.
Please suggest if I would need to re-install ubuntu on my virtual box or
the current setup would work as before ?

Thanks,
Mahesh Bhatia

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: sudo 1.8.21p2-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
 ubuntu-minimal:amd64: Purge
 sudo:amd64: Purge
 NULL: ConfigurePending
 NULL: PurgePending
 NULL: ConfigurePending
Architecture: amd64
Date: Wed May 16 16:17:51 2018
ErrorMessage: installed sudo package pre-removal script subprocess returned 
error exit status 1
InstallationDate: Installed on 2018-05-15 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: sudo
Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed sudo 
package pre-removal script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
 /etc/sudoers: parsed OK
 /etc/sudoers.d/README: parsed OK
mtime.conffile..etc.sudoers: 2018-05-16T16:12:29.233258

** Affects: sudo (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/1771598

Title:
  package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed
  sudo package pre-removal script subprocess returned error exit status
  1

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

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

[Bug 1771598] Re: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1

[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/1771598

Title:
  package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: installed
  sudo package pre-removal script subprocess returned error exit status
  1

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

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

[Bug 1591977] Re: python3-autopep8

[Bug Watch Updater]

** Changed in: autopep8 (Debian)
   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/1591977

Title:
  python3-autopep8

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

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

[Bug 1524526] Re: Crashes with undefined symbol

[ Christian Ehrhardt ]

FYI - no more an issue in Cosmic (test build) so we will stop disabling
dovecot-lucene there.

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

Title:
  Crashes with undefined symbol

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

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

[Bug 1771524] Re: Merge newer dovecot for Cosmic

[ Christian Ehrhardt ]

I had thought of an issue of the breaks/replaces and tested with the first ppa 
build.
Indeed old mail-stack-delivery postrm being triggered would mean a restoration 
of the cofig before it's installation. This is not how we want it to be 
transitioned-out.
Therefore case 11 of https://wiki.debian.org/PackageTransition does not apply 
(as that would remove it).
Instead approach #2 would be to add an empty transitional that we will keep 
until 20.04 to catch all upgrades dropping it without modifying the 
configuration.

I tested an old install with mail-stack-delivery upgrading to the new version.
a) with breaks/replaces
   triggers the unwanted remove as expected
b) with a transitional package
   This does what we want
- turn it into an empty package
- does not rebuild the assumed old config
- the transitional can be removed without wreaking havok

Going on with B then ...

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

Title:
  Merge newer dovecot for Cosmic

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

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

[Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

[Treviño]

I got it finally with some proper JS stacktrace, in my case it was an
extension triggering it:

(gnome-shell:6754): Gjs-CRITICAL **: 12:22:44.730: Object St.BoxLayout 
(0x55950fcf1230), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x55950f5194c0 ==
#0 0x7fffe152eed0 I   resource:///org/gnome/shell/ui/environment.js:41 
(0x7f1e5c586d58 @ 20)
#1 0x7fffe152efc0 b   resource:///org/gnome/shell/ui/popupMenu.js:642 
(0x7f1e5c224de0 @ 61)
#2 0x7fffe152f060 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f1e5c5b5e68 @ 71)
#3 0x55950f8dd540 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:132
 (0x7f1e0fa86808 @ 342)
#4 0x55950f8dd480 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/utils.js:121
 (0x7f1e0fab9340 @ 458)

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.730:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.730:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Gjs-CRITICAL **: 12:22:44.731: Object St.BoxLayout 
(0x55950fcf1230), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x55950f5194c0 ==
#0 0x7fffe152eed0 I   resource:///org/gnome/shell/ui/environment.js:41 
(0x7f1e5c586d58 @ 20)
#1 0x7fffe152efc0 b   resource:///org/gnome/shell/ui/popupMenu.js:642 
(0x7f1e5c224de0 @ 61)
#2 0x7fffe152f060 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f1e5c5b5e68 @ 71)
#3 0x55950f8dd540 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:157
 (0x7f1e0fa86808 @ 585)
#4 0x55950f8dd480 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/utils.js:121
 (0x7f1e0fab9340 @ 458)

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.731:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.731:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Gjs-CRITICAL **: 12:22:44.731: Object St.BoxLayout 
(0x55950fcf1230), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x55950f5194c0 ==
#0 0x7fffe152eed0 I   resource:///org/gnome/shell/ui/environment.js:41 
(0x7f1e5c586d58 @ 20)
#1 0x7fffe152efc0 b   resource:///org/gnome/shell/ui/popupMenu.js:642 
(0x7f1e5c224de0 @ 61)
#2 0x7fffe152f060 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f1e5c5b5e68 @ 71)
#3 0x55950f8dd540 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:171
 (0x7f1e0fa86808 @ 778)
#4 0x55950f8dd480 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/utils.js:121
 (0x7f1e0fab9340 @ 458)

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.732:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.732:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.732:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.732:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.732:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): 

[Bug 1437353] Re: UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit SFI/SFP+

[Mathieu Trudel-Lapierre]

Well, the CI part confirms that there is no regression, but there is as
yet no indication that the issue is fixed aside from the cases where
firmware was updated (but then, it's not the SRU).

There's still a need to verify the fix positively on affected hardware.

Now, KingJ's comment says that testing has been done with the version of
grub in bionic, and with the version of grub being SRUed to xenial, and
neither did work. I think that qualifies as verification-failed, and
we'll need to have another look at grub's behavior. At this point, there
is no obvious patch missing, and we'll need to debug using packet
captures to try and make sense of it.

** Tags removed: verification-done verification-done-xenial
** Tags added: verification-failed-xenial

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

Title:
  UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit
  SFI/SFP+

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

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

[Bug 1771542] [NEW] Suspend to idle: Open lid didn't resume

[Woodrow Shen]

Public bug reported:

[Impact]
Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and 
then they can't resume the system from opening the lid.

[Fix]
According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, 
so we cherry pick the patch to Ubuntu 4.15 kernel.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953

[Regression Potential]
no regression could be happened

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


** Tags: originate-from-1769555 timbuktu

** Description changed:

  [Impact]
- Some platforms is set suspend-to-idle (s2idle) as default suspend mode, and 
then they can't resume the system from opening the lid.
+ Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and 
then they can't resume the system from opening the lid.
  
  [Fix]
  According a patch sent to 4.17-rc1, which was not be included before 4.15 
EOL, so we cherry pick the patch to Ubuntu 4.15 kernel.
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953
  
  [Regression Potential]
  no regression could be happened

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

Title:
  Suspend to idle: Open lid didn't resume

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

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

[Bug 1768734] Re: Restoring edge tiled windows with client-side decorations shrinks them (Wayland)

[mtvoid]

** Project changed: gtk => mutter

** Summary changed:

- Restoring edge tiled windows with client-side decorations shrinks them 
(Wayland)
+ Restoring edge tiled windows on Wayland shrinks them

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

Title:
  Restoring edge tiled windows on Wayland shrinks them

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

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

[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

[Penn Mackintosh]

I have confirmed that the above patch works by applying it and running
xev. I then pressed META+SPACE and the keyboard layout changed without
any output from xev.

** Changed in: gnome-shell (Ubuntu)
   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/1244090

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1244090/+subscriptions

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

[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

[Ubuntu Foundations Team Bug Bot]

The attachment "AMD64 .deb included, with .patch file" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1244090/+subscriptions

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

[Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Guilherme G. Piccoli]

Fixed in Debian

** Project changed: linux => initramfs-tools

** Changed in: initramfs-tools
   Status: Unknown => 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/1771557

Title:
  NVMe boot drives not supported - failing in generating initramfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+subscriptions

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

[Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Dan Streetman]

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

** Also affects: linux (Ubuntu Xenial)
   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/1771557

Title:
  NVMe boot drives not supported - failing in generating initramfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+subscriptions

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

[Bug 1771555] Re: dmesg Error seen on system booting from Ubuntu18.04

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it.  You can find some hints about determining what package your
bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit
https://bugs.launchpad.net/ubuntu/+bug/1771555/+editstatus and add the
package name in the text box next to the word Package.

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: bot-comment

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

Title:
  dmesg Error seen on system booting from Ubuntu18.04

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

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

[Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - gnome-screensaver & gnome-shell fail to start?

[Jean-Baptiste Lallement]

I cannot reproduce this issue anymore with a fresh installation of
xenial upgraded to bionic. I'm wondering if the fontconfig fix that
delayed the boot was causing this issue (bug 1749546)

Setting to incomplete.

** Changed in: gnome-shell (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/1765724

Title:
  Xenial -> Bionic - System fails to boot after upgrade - gnome-
  screensaver & gnome-shell fail to start?

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

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

[Bug 1687817] Re: Inkscape 0.92.1-1 always reverts display units to px

[Alvin Penner]

could you attach the svg file you are using, for testing purposes?

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

Title:
  Inkscape 0.92.1-1 always reverts display units to px

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

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

[Bug 1771548] Re: crashes while trying to re-install lubuntu to an older system.

[dino99]

Error:

 Building initial module for 4.15.0-20-generic
 lubuntu ubiquity: Done.
 lubuntu ubiquity: 
 lubuntu ubiquity: wl:
 lubuntu ubiquity: Running module version sanity check.
 lubuntu ubiquity:  - Original module
 lubuntu ubiquity:- No original module exists within this kernel
 lubuntu ubiquity:  - Installation
 lubuntu ubiquity:- Installing to 
/lib/modules/4.15.0-20-generic/updates/dkms/
 lubuntu ubiquity: 
 lubuntu ubiquity: depmod...
 lubuntu ubiquity: .
 lubuntu kernel: [  297.852883] depmod[5990]: segfault at 646e04 ip 0046ad3f sp 
bfe03ebc error 4 in kmod[455000+2b000]
 lubuntu kernel: [  304.145036] perf: interrupt took too long (6218 > 6211), 
lowering kernel.perf_event_max_sample_rate to 32000
 lubuntu ubiquity: message repeated 8 times: [ .]
 lubuntu ubiquity: (bad exit status: 139)
 lubuntu ubiquity: 
 lubuntu ubiquity: 
 lubuntu ubiquity:  Uninstall Beginning 
 lubuntu ubiquity: Module:  bcmwl
 lubuntu ubiquity: Version: 6.30.223.271+bdcom
 lubuntu ubiquity: Kernel:  4.15.0-20-generic (i686)
 lubuntu ubiquity: -
 lubuntu ubiquity: 
 lubuntu ubiquity: Status: Before uninstall, this module version was ACTIVE on 
this kernel.
 lubuntu ubiquity: 
 lubuntu ubiquity: wl.ko:
 lubuntu ubiquity:  - Uninstallation
 lubuntu ubiquity: 
 lubuntu ubiquity:- Deleting from: 
/lib/modules/4.15.0-20-generic/updates/dkms/
 lubuntu ubiquity:  - Original module
 lubuntu ubiquity:- No original module was found for this module on this 
kernel.
 lubuntu ubiquity:- Use the dkms install command to reinstall any previous 
module version.
 lubuntu ubiquity: 
 lubuntu ubiquity: 
 lubuntu ubiquity: depmod...
 lubuntu ubiquity: (bad exit status: 134)
 lubuntu ubiquity: 
 lubuntu ubiquity: 
 lubuntu ubiquity: DKMS: uninstall completed.
 lubuntu ubiquity: Error!
 lubuntu ubiquity: Problems with depmod detected.  Automatically uninstalling 
this module.
 lubuntu ubiquity: DKMS: Install Failed (depmod problems).  Module rolled back 
to built state.
 lubuntu ubiquity: dpkg: Fehler beim Bearbeiten des Paketes bcmwl-kernel-source 
(--configure):
 lubuntu ubiquity:  Unterprozess installed bcmwl-kernel-source package 
post-installation script gab den Fehler-Ausgangsstatus 6 zurück
 lubuntu ubiquity: Trigger für libc-bin (2.27-3ubuntu1) werden verarbeitet ...

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

Title:
  crashes while trying to re-install lubuntu to an older system.

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

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

[Bug 1713034] Re: gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"]

[Bug Watch Updater]

** Changed in: glib
   Status: Confirmed => Incomplete

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

Title:
  gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion
  failed: (wd >= 0)"]

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

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

[Bug 1717218] Re: Ubuntu 16.04: Can't install 'ubuntu-desktop' error during a partial upgrade of the system

[Hunter Murphy]

I am having this same problem. I am a newbie to Linux and to computing,
as a whole. Please refer to the most "beginner-friendly" fix/guide to
this issue.

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

Title:
  Ubuntu 16.04: Can't install 'ubuntu-desktop' error during a partial
  upgrade of the system

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

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

[Bug 1771555] [NEW] dmesg Error seen on system booting from Ubuntu18.04

[bugproxy]

Public bug reported:

Problem Description
===
dmesg Error seen on system booting from Ubuntu18.04
Is this an issue?
[2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
[2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)

user1@yob45wos:~$ sudo dmesg --level=alert
user1@yob45wos:~$ sudo dmesg --level=crit
user1@yob45wos:~$ sudo dmesg --level=err
[3.382733] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
[3.382738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
[3.531263] vio vio: uevent: failed to send synthetic uevent
[4.521383] nouveau 0004:04:00.0: unknown chipset (14a1)
[4.521889] nouveau 0035:03:00.0: unknown chipset (14a1)
[4.634336] lpfc 0030:01:00.0: 0:6101 Disabling NVME support: Not supported 
by firmware: 0 0
[4.634416] lpfc 0030:01:00.0: 0:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 
16
[5.646354] lpfc 0030:01:00.1: 1:6101 Disabling NVME support: Not supported 
by firmware: 0 0
[5.646420] lpfc 0030:01:00.1: 1:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 
16
[6.944481] lpfc 0030:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 
x80 x0 x0 x0 0
[6.944634] lpfc 0030:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 
x80 x0 x0 x0 0
[   22.109545] vio vio: uevent: failed to send synthetic uevent
user1@yob45wos:~$

> 
> Problem Description
> ===
> dmesg Error seen on system booting from Ubuntu18.04
> Is this an issue?  These messages are seen on every IPL.  Is there an issue?
> [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
> [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)

These messages should be marked as Warnings instead of Errors as they it 
supposedly a warning and not an error. 
This was fixed in LP #1656908 / Bug 150596, but seeing it with 'dmesg 
--level=err' again in 18.04. 
* In Ubuntu 17.04 : after reboot getting message in console like Unable to
open file: /etc/keys/x509_ima.der (-2) (LP: #1656908)
- SAUCE: ima: Downgrade error to warning

Mirroring this bug to distro to fix this in the latest kernel.

Thank you.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: architecture-ppc64le bugnameltc-166612 severity-high 
targetmilestone-inin---

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

Title:
  dmesg Error seen on system booting from Ubuntu18.04

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

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

[Bug 1770238] Re: [nvidia] Logging in results in a black screen for many minutes after which the login screen reappears and I am able to login fine.

[Jonathan]

*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192

I cannot view my own error reports, it just tells me I don't have
permission and am not part of the correct group. I filled out the form
to request access so we shall see.

I'm not sure if my original error is a duplicate of bug #154192. There
doesn't appear to be a crash involved. gdm-x-session just seems to shut
itself down because it couldn't find monitors.  Even though it works
after a system reload.

 May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)
Screen(s) found, but none have a usable configuration.

It definitely does seem I am being hit by a miriad of bugs.  Its getting
pretty frustrating to keep using it. And its also hard to tell the
difference between them.

Issues as far as I can tell:
* First login fails due to no usable monitors, if wayland is disabled. 
(Workaround, don't disable wayland)
* gnome-calculator and possibly other snap apps lock up the computer when 
opened if wayland is disabled. (Workaround, don't disable wayland)
* System locks up and reboots. (Unknown cause, no errors appear in logs as they 
don't get flushed to disk.)
* Gnome locks up and I am returned to login screen (Unknown cause but seems to 
generate a variety of different crash reports)

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

Title:
  [nvidia] Logging in results in a black screen for many minutes after
  which the login screen reappears and I am able to login fine.

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

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

[Bug 1758163] Re: Please remove xchat-gnome from Ubuntu (again)

[Kieran Bingham]

I find my way here after losing xchat-gnome on the bionic upgrade:

Ok - so I just tried out hexchat - and that seems to be pretty good
alternative / update.

Is there a way to get apt to suggest / recommend hexchat instead of
failing to install xchat-gnome?

"""
# sudo apt-get install xchat-gnome
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package xchat-gnome is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'xchat-gnome' has no installation candidate
"""

It would be useful for that to print the alternatives - or just install
hexchat as a replacement :D

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

Title:
  Please remove xchat-gnome from Ubuntu (again)

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

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

[Bug 1771540] Re: i am not able to install the updates

[dino99]

Reporting againg 'xorg' is unrelated to 'upgrade'; should have been reported 
against 'apt' instead.
So all the logs joined here are useless for fixing that problem.

What are the outputs of:

sudo apt-get install -f
sudo apt-get update && sudo apt-get upgrade

Usually in such a case, either some package(s) are broken due to
dependencies conflict. If you have some ppa's package(s) installed, then
downgrade via 'ppa-purge'

** Changed in: xorg (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/1771540

Title:
  i am not able to install the updates

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

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

[Bug 1771548] [NEW] crashes while trying to re-install lubuntu to an older system.

[Gregor]

Public bug reported:

I have no idea what is going on. I just tried to re-install an older
system - it used to work, until the re-install. I formatted the whole
ssd and nothing changed. I changed ISO's and the USB-Drives, but nothing
worked out.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic i686
ApportVersion: 2.20.9-0ubuntu7
Architecture: i386
CasperVersion: 1.394
Date: Wed May 16 12:37:53 2018
InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426)
ProcEnviron:
 LANGUAGE=de_AT.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_AT.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: apport-bug bionic i386 lubuntu ubiquity-18.04.14

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

Title:
  crashes while trying to re-install lubuntu to an older system.

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

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

[Bug 1769433] Re: do-release-upgrade from 32-bit 16.04 to 18.04 goes ahead, doesn't work and messes everything up

[Jean-Baptiste Lallement]

Thanks for following up. I'm closing this report then according to your
last comment but will keep an eye on 32bit upgrades.

Don't hesitate to file any bug you may find.

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

Title:
  do-release-upgrade from 32-bit 16.04 to 18.04 goes ahead, doesn't work
  and messes everything up

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

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

[Bug 1771513] Re: package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk:amd64 is not ready for configuration cannot configure (current status 'half-installed')

[Olivier Tilloy]

Can you run the following command in a terminal and share the output?

sudo apt -f install

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

Title:
  package ibus-gtk:amd64 1.5.11-1ubuntu2 failed to install/upgrade:
  package ibus-gtk:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

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

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

[Bug 1771546] 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 1771546

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

** Tags added: vivid

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

Title:
  WARNING: setup_local_APIC+0x27f/0x340

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

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

[Bug 1771028] Re: Apparmor profile for chronyd needs to allow creation of /var/run/chrony.tty*.sock

[Bug Watch Updater]

** Changed in: chrony (Debian)
   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/1771028

Title:
  Apparmor profile for chronyd needs to allow creation of
  /var/run/chrony.tty*.sock

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

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

[Bug 1771524] Re: Merge newer dovecot for Cosmic

[ Christian Ehrhardt ]

Since 2.3.1 is still in experimental (see Debian bug) I moved the
lp1771524/new/debian tag to that manually.

passed all Dovecot bugs of the last 2 years to clear out or consider on
the merge.

Reconstruct, Deconstruct and Logical prepared in git merge workflow.

Checked CVE patches to exist in 2.3.1
- CVE-2017-15132 is already included
- CVE-2017-15130 is already included
- CVE-2017-14461 is already included

There were some conf-breaking changes in 2.3, so I consider it even more
important to make it available early on Cosmic cycle as well as in the
long run towards 20.04.

Note for mail-stack delivery:
- only a few breaks replaces will remain according to case #11 on 
https://wiki.debian.org/PackageTransition until after 20.04
- we will not rm-conffile the modifications it had made since it did modify 
"its own" but dovecots config, therefore removing would be an unwanted 
modification of a users configuration

All that said ready to rebase and drop a lot this time ...

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-14461

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15130

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15132

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

Title:
  Merge newer dovecot for Cosmic

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

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

[Bug 1768756] Re: Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

[Olivier Tilloy]

Indeed, when doing a minimal install a normal install is performed and
then a selected list of packages is removed (casper/filesystem.manifest-
minimal-remove on the iso).

How did you initially install libreoffice after doing the minimal
install? Was it with a graphical package manager, or with apt in a
terminal?

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

Title:
  Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

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

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

[Bug 1769613] Re: ubuntu-release-upgrader crashed

[Jean-Baptiste Lallement]

Right but they are both official versions and shouldn't block the
upgrade.

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  ubuntu-release-upgrader crashed

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

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

[Bug 1770579] Re: Failure to quote variable containing secureboot password (errors out with whitespace) package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package

[Francis Ginther]

** Tags added: id-5af999195fa3c7cd33a518db

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

Title:
  Failure to quote variable containing secureboot password (errors out
  with whitespace) package shim-signed 1.34.9+13-0ubuntu2 failed to
  install/upgrade: installed shim-signed package post-installation
  script subprocess returned error exit status 2

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

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

[Bug 1768632] Re: configuring DHCPv6 wipes out any nameservers set while configuring IPv4

[Francis Ginther]

** Tags added: id-5af9fc09f44d168618294a3a

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

Title:
  configuring DHCPv6 wipes out any nameservers set while configuring
  IPv4

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

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

[Bug 1758163] Re: Please remove xchat-gnome from Ubuntu (again)

[Jeremy Bicha]

Just installing hexchat would mean adding a "transitional" package in
the hexchat source.

One way to have a suggestion about hexchat would be having command-not-
found handle it. To get an idea of how that works, if you uninstall
hexchat and run hexchat in a terminal, you'll get this output on Ubuntu
18.04 LTS:

$ hexchat

Command 'hexchat' not found, but can be installed with:

sudo snap install hexchat
sudo apt  install hexchat

See 'snap info hexchat' for additional versions.

===
So I suggest filing a separate bug against hexchat or command-not-found for 
your suggestion.

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

Title:
  Please remove xchat-gnome from Ubuntu (again)

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

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

[Bug 1770909] Re: reorder keybindings to show upstream defaults in gnome-control-center

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-gnome-default-settings -
18.10.1

---
ubuntu-gnome-default-settings (18.10.1) cosmic; urgency=medium

  * Drop some gsettings overrides that are no longer needed
  * Reorder some keybinding overrides so upstream defaults are
shown in gnome-control-center (LP: #1770909)
  * Switch mouse modifier button to  in line with upstream GNOME
and also Ubuntu, as  conflicts with various apps (LP: #1704580)

 -- Tim Lunn   Wed, 16 May 2018 19:35:54 +1000

** Changed in: ubuntu-gnome-default-settings (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/1770909

Title:
  reorder keybindings to show upstream defaults in gnome-control-center

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

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

[Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Guilherme G. Piccoli]

** Changed in: initramfs-tools (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: initramfs-tools (Ubuntu)
   Importance: High => Medium

** Changed in: initramfs-tools (Ubuntu)
Milestone: trusty-updates => None

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+subscriptions

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

[Bug 1771561] Re: I am unable to upgrade my system

[Jean-Baptiste Lallement]

Thanks for your report.

Please revert Xorg packages from oibaf repository to official Ubuntu
versions and try the upgrade again.

I'm closing this report because it is not a bug with Ubuntu. Don't
hesitate to submit any bug you may find.

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

Title:
  I am unable to upgrade my system

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

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

[Bug 1769346] Re: Unable to install 18.04 server AMD64 with targeted kernel: initramfs-tools

[Manny Flores]

I fixed this error by updating my BIOS. Weird - I didn't have this issue
with prior versions including 16.04.4 but when I also tried 16.04.4, I
got the same problem. I might have been using an earlier 16.04.x where
this wasn't an issue. But again, in the end, the BIOS did the trick.

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

Title:
  Unable to install 18.04 server AMD64 with targeted kernel: initramfs-
  tools

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

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

[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

[Timo Jyrinki]

It seems there is no update since 2015 to qca subdir of linux-firmware,
so those newer blobs will need to be submitted by Qualcomm, maybe ytkim
specifically who did that 3 years ago if he's still at Qualcomm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/log/qca

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

Title:
  Bluetooth issues with Dell XPS 13 (9370)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+subscriptions

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

[Bug 1769433] Re: do-release-upgrade from 32-bit 16.04 to 18.04 goes ahead, doesn't work and messes everything up

[Alvaro Carballo Garcia]

OK. Sorry but I have no logs. Additionally, if it is only a problem with
my machine (quite old and crappy anyway), I wouldn't have bothered at
all. The only reason for having started this thread was thinking that
this might be useful for someone else. So, we can stop it here. Thanks.

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

Title:
  do-release-upgrade from 32-bit 16.04 to 18.04 goes ahead, doesn't work
  and messes everything up

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

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

[Bug 1771389] Re: Add Wayland support to GNOME Flashback session

[Alberts Muktupāvels]

First I would like to hear why do you want Wayland with GNOME Flashback?

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

Title:
  Add Wayland support to GNOME Flashback session

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

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

[Bug 1771389] Re: Add Wayland support to GNOME Flashback session

[Livio Calvo]

The main reason is that Wayland is tearing-free by design. XOrg needs a
window manager with compositing to avoid tearing.

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

Title:
  Add Wayland support to GNOME Flashback session

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

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

[Bug 1751278] Re: dbgsym packages are generated iff DH_BUILD_DDEBS is set

[Niels Thykier]

Michael Prokop:
> Public bug reported:
> 
> A user trying to rebuild a Debian package of us ran into the problem
> that he didn't get debug packages any longer. (The original bug report
> and discussion around it is available at
> https://github.com/sipwise/rtpengine/issues/459 )
> 
> In Ubuntu's debhelper changelog I found:
> 
> debhelper (9.20160115ubuntu2) xenial; urgency=medium
> 
>   * dh-strip: Adjust reversion of commit f1a803456 to account for the recent
> ENABLE_DDEBS → ENABLE_DBGSYM rename. This actually disables -dbgsym
> generation by dh_strip by default again. (LP: #1535949)
> 
> This matches what's documented under the "Ubuntu" section at 
> https://wiki.debian.org/AutomaticDebugPackages
> This doesn't seem to really match what's documented in Ubuntu's dh_strip 
> manpage though:
> 
>--automatic-dbgsym, --no-automatic-dbgsym
>Control whether dh_strip should be creating debug symbol packages 
> when possible.
> 
>The default is to create debug symbol packages.
> 
> In Ubuntu's dh_strip implementation I stumbled upon:
> 
>   $dh{ENABLE_DBGSYM} = 0 if not $ENV{'DH_BUILD_DDEBS'};
> 
> So only if DH_BUILD_DDEBS is set then dbgsym packages are generated, and
> indeed this has been verified by the original bug reporter on Ubuntu
> Server 16.04.3 LTS.
> 
> So the documentation seems to be wrong/incomplete. Probably it would
> also make sense to switch the default around, to by default
> automatically generate the dbgsym packages, so that users get a more
> consistent behavior. You could then force it to off on Ubuntu's build
> daemons instead, if that's relevant.
> 
> ** Affects: debhelper (Ubuntu)
>  Importance: Undecided
>  Status: New
> 

Side-note: I believe this has been fixed in Artful or Bionic as Ubuntu
has migrated to use the debhelper based dbgsym packages (with only a
minor difference in the filename extension).  I remember it as Artful
(but the reference eludes me at the moment and I am too lazy to check).

Thanks,
~Niels



** Bug watch added: github.com/sipwise/rtpengine/issues #459
   https://github.com/sipwise/rtpengine/issues/459

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

Title:
  dbgsym packages are generated iff DH_BUILD_DDEBS is set

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

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

[Bug 1744710] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From ppaid...@in.ibm.com 2018-05-16 07:17 EDT---
Verified this issue and also ran opal-prd related tests, they are working fine.

root@ltc-boston125:~# dpkg -l | grep -i opal-prd
ii  opal-prd   5.10~rc4-1ubuntu1 
ppc64el  OPAL Processor Recovery Diagnostics daemon
root@ltc-boston125:~# service opal-prd status
* opal-prd.service - OPAL PRD daemon
Loaded: loaded (/lib/systemd/system/opal-prd.service; enabled; vendor preset: 
enabled)
Active: active (running) since Wed 2018-05-16 07:11:24 EDT; 56s ago
Docs: man:opal-prd(8)
Main PID: 3166 (opal-prd)
Tasks: 1 (limit: 19660)
CGroup: /system.slice/opal-prd.service
`-3166 /usr/sbin/opal-prd

May 16 07:11:25 ltc-boston125 opal-prd[3166]: HBRT: PRDF:<Service::enableAttns() enter
May 16 07:11:25 ltc-boston125 opal-prd[3166]: HBRT: TARG:[TARG] I> 
getNextTarget: Using next node 1
May 16 07:11:25 ltc-boston125 opal-prd[3166]: HBRT: TARG:[TARG] E> 
getNextTarget: Node 0 targets: first 0x7d4763affc1c, current 0x7d4763b04b00, 
last 0x7d4763b04b00
May 16 07:11:25 ltc-boston125 opal-prd[3166]: HBRT: TARG:[TARG] E> 
getNextTarget: Target not found
May 16 07:11:25 ltc-boston125 opal-prd[3166]: HBRT: 
ATTN_SLOW:I>Service::enableAttns() exit
May 16 07:11:25 ltc-boston125 opal-prd[3166]: HBRT: 
ATTN_SLOW:I> 
getNextTarget: Using next node 1
May 16 07:11:25 ltc-boston125 opal-prd[3166]: HBRT: TARG:[TARG] E> 
getNextTarget: Node 0 targets: first 0x7d4763affc1c, current 0x7d4763b04b00, 
last 0x7d4763b04b00
May 16 07:11:25 ltc-boston125 opal-prd[3166]: HBRT: TARG:[TARG] E> 
getNextTarget: Target not found
May 16 07:11:25 ltc-boston125 opal-prd[3166]: HBRT: 
ATTN_SLOW:I>Service::enableAttns() exit
May 16 07:11:25 ltc-boston125 opal-prd[3166]: HBRT: 
ATTN_SLOW:I>

[Bug 1738164] Re: [snap] U2F doesn't work with yubikey

[Olivier Tilloy]

It looks like the raw-usb interface might help here. I'll rebuild the
snap with it and will post instructions on how to test.

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

Title:
  [snap] U2F doesn't work with yubikey

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

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

[Bug 1771555] Re: dmesg Error seen on system booting from Ubuntu18.04

[bugproxy]

--- Comment From cdead...@us.ibm.com 2018-05-16 07:43 EDT---
cde00 (cdead...@us.ibm.com) added native attachment 
/tmp/AIXOS07269201/file_166612.txt on 2018-05-16 06:43:46

** Tags added: architecture-ppc64le bugnameltc-166612 severity-high
targetmilestone-inin---

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

Title:
  dmesg Error seen on system booting from Ubuntu18.04

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

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

[Bug 1769613] Re: ubuntu-release-upgrader crashed

[ben_31]

The problem was solved by removing some conflicting packages: 
- libavfilter6,
- libopencv-highgui3.1,

and then "apt autoremove".

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

Title:
  ubuntu-release-upgrader crashed

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

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

[Bug 1771555] dmesg

[bugproxy]

Default Comment by Bridge

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/bugs/1771555/+attachment/5140330/+files/file_166612.txt

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

Title:
  dmesg Error seen on system booting from Ubuntu18.04

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

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

[Bug 1771557] [NEW] NVMe boot drives not supported - failing in generating initramfs

[Guilherme G. Piccoli]

Public bug reported:

[Impact] 
The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to nvmeXnY 
block device, so it's failing and not building the initram disk.

Upstream solution is composed for at least 2 patches (it's a series, but
the 2 below are really the needed ones):

commit 3cb744c9
Author: Ben Hutchings 
hook-functions: Rewrite block device sysfs lookup to be generic

commit 8ac52dc0
Author: Ben Hutchings 
hook-functions: Include modules for all components of a multi-disk device

Instead of doing the backport, which is huge, we added another sed 
substitution: currently the script has substitutions for sdX and hdX, in order 
to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to 
nvmeXnY.
It's less intrusive than the full backport, since this is a SRU to Trusty only.


[Test Case]
To be added.


[Regression Potential] 
If the sed expression was somewhat broken, we could have an issue generating 
initiramfs for generic block devices, like regular HDDs.


[Other Info]
This issue is based on Debian bug #785147: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

** Affects: initramfs-tools
 Importance: Unknown
 Status: Fix Released

** Affects: initramfs-tools (Ubuntu)
 Importance: High
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: In Progress

** Affects: initramfs-tools (Ubuntu Trusty)
 Importance: High
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: In Progress

** Affects: initramfs-tools (Ubuntu Xenial)
 Importance: Medium
 Status: Fix Released


** Tags: sts trusty

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

** Changed in: linux (Ubuntu)
Milestone: None => trusty-updates

** Bug watch added: Debian Bug tracker #785147
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

** Also affects: linux via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147
   Importance: Unknown
   Status: Unknown

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+subscriptions

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

[Bug 1771304] Re: host don't use search domain for service record

[Sven Sternberger]

I've added "options ndots:2" and indeed it works now.

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

Title:
  host don't use search domain for service record

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

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

[Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Guilherme G. Piccoli]

** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu)

** Changed in: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: initramfs-tools (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: initramfs-tools (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: initramfs-tools (Ubuntu Trusty)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: initramfs-tools (Ubuntu Trusty)
Milestone: None => trusty-updates

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+subscriptions

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

Re: [Bug 1771540] Re: i am not able to install the updates

[pawan naresh chandiramani]

I am getting failed to connect to a server and then it's saying check your
internet connection, but I am able to browse the net via my internet
connection

On Wed 16 May, 2018, 4:20 PM dino99, <1771...@bugs.launchpad.net> wrote:

> Reporting againg 'xorg' is unrelated to 'upgrade'; should have been
> reported against 'apt' instead.
> So all the logs joined here are useless for fixing that problem.
>
> What are the outputs of:
>
> sudo apt-get install -f
> sudo apt-get update && sudo apt-get upgrade
>
> Usually in such a case, either some package(s) are broken due to
> dependencies conflict. If you have some ppa's package(s) installed, then
> downgrade via 'ppa-purge'
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1771540
>
> Title:
>   i am not able to install the updates
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>i am not able to install the updates
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
>   Uname: Linux 4.4.0-98-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.10
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   Date: Wed May 16 15:19:58 2018
>   DistUpgraded: 2017-09-01 00:53:53,943 WARNING no activity on terminal
> for 300 seconds (Installed python3-renderpm (amd64))
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   DpkgLog:
>
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07)
> (prog-if 00 [VGA controller])
>  Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
>   InstallationDate: Installed on 2017-08-01 (287 days ago)
>   InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64
> (20160803)
>   MachineType: Dell Inc. Inspiron 5559
>   ProcEnviron:
>LANGUAGE=en_IN:en
>PATH=(custom, no user)
>LANG=en_IN
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed
> root=UUID=1cde99c2-2259-44dd-a873-b302c0633c92 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to xenial on 2017-08-31 (257 days ago)
>   dmi.bios.date: 09/16/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.0.6
>   dmi.board.name: 04D1V1
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.0.6:bd09/16/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Inspiron 5559
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160325-1ubuntu1.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>   xserver.bootTime: Wed May 16 13:57:14 2018
>   xserver.configfile: default
>   xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id1557
>vendor BOE
>   xserver.version: 2:1.18.4-0ubuntu0.7
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771540/+subscriptions
>

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

Title:
  i am not able to install the updates

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

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

[Bug 1771524] Re: Merge newer dovecot for Cosmic

[ Christian Ehrhardt ]

Dropped (by dropping mail stack delivery):
 276a97d3 2.2.22-1ubuntu Add mail-stack-delivery package 
 d95bbb9a * Use ssl key paths set up by Debian as default - adapt 
mail-stack-delivery default config - move old mail-stack-deliver
 086f95d2 - for the ssl transition to work we need to ensure dovecot-core is 
complete before upgrading mail-stack-delivery
 fcfab6ea d/mail-stack-delivery.postinst: add SSL_CERT/SSL_KEY detection to 
postconf
 746601a4 fix SSL_CERT/SSL_KEY detection 
 8f8a7d17 - debian/99-mail-stack-delivery.conf: drop explicit ssl_cipher_list, 
recent upstream has sane defaults now
 1e33020a - d/mail-stack-delivery.postinst: stop modifying mandatory tls 
config, recent upstream has sane defaults now
 07c4a590 d/mail-stack-delivery.preinst: improve moving of old 
mail-stack-delivery conf (merge with '* Use ssl key paths set up by Debian 
 49d2e29e d/mail-stack-delivery.postinst: fix minor shell programming issues 
 3078196f d/mail-stack-delivery.postinst: postfix conf to follow key changes 
 bf4f82fc fix dput lint warnings in regard to dependencies   

Droped (now upstream)
 d9dcfdf4 debian/patches/CVE-2017-15132.patch
 b971a03e debian/patches/CVE-2017-15132-additional.patch 
 b468f56c debian/patches/CVE-2017-14461/*.patch: upstream parsing fixes  
 572b4ec8 debian/patches/CVE-2017-15130/*.patch: upstream config filtering fix

Dropped (transition no more needed >18.04)
  4 pick 614a88a3 handle conffile removal of /etc/init/dovecot.conf

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

Title:
  Merge newer dovecot for Cosmic

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

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

[Bug 1771278] Re: search in gnome is not working

[Jeremy Bicha]

** Changed in: gnome-shell (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/1771278

Title:
  search in gnome is not working

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

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

[Bug 1704580] Re: mouse-button-modifier should default to Super

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-gnome-default-settings -
18.10.1

---
ubuntu-gnome-default-settings (18.10.1) cosmic; urgency=medium

  * Drop some gsettings overrides that are no longer needed
  * Reorder some keybinding overrides so upstream defaults are
shown in gnome-control-center (LP: #1770909)
  * Switch mouse modifier button to  in line with upstream GNOME
and also Ubuntu, as  conflicts with various apps (LP: #1704580)

 -- Tim Lunn   Wed, 16 May 2018 19:35:54 +1000

** Changed in: ubuntu-gnome-default-settings (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/1704580

Title:
  mouse-button-modifier should default to Super

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

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

[Bug 1771542] Re: Suspend to idle: Open lid didn't resume

[Woodrow Shen]

** Description changed:

  [Impact]
  Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and 
then they can't resume the system from opening the lid.
  
  [Fix]
- According a patch sent to 4.17-rc1, which was not be included before 4.15 
EOL, so we cherry pick the patch to Ubuntu 4.15 kernel.
+ According a patch sent to 4.17-rc1, which was not be included before 4.15 
EOL, so we cherry pick the patch to Ubuntu 4.13 / 4.15 kernel.
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953
  
  [Regression Potential]
  no regression could be happened

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

Title:
  Suspend to idle: Open lid didn't resume

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

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

[Bug 1768734] Re: Restoring edge tiled windows on Wayland shrinks them

[mtvoid]

I've found a recent bug report for this issue on the GitLab site for mutter:
https://gitlab.gnome.org/GNOME/mutter/issues/140

This also requires me to correct my initial bug report. The issue is
unrelated to client-side decorated windows, but affects all native
Wayland windows, while XWayland windows are unaffected.

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

Title:
  Restoring edge tiled windows on Wayland shrinks them

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

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

[Bug 1767263] Re: 16.04 to 18.04

[Jean-Baptiste Lallement]

*** This bug is a duplicate of bug 1768620 ***
https://bugs.launchpad.net/bugs/1768620

** This bug has been marked a duplicate of bug 1768620
   removal_blacklist.cfg updates

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

Title:
  16.04 to 18.04

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

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

[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[Bug Watch Updater]

** Changed in: network-manager
   Status: Confirmed => 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/1754671

Title:
  Full-tunnel VPN DNS leakage regression

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

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

[Bug 1771546] [NEW] WARNING: setup_local_APIC+0x27f/0x340

[LovelyLich]

Public bug reported:

when load kernel with kexec:
   /sbin/kexec -p 
--command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 
console=tty0 irqpoll maxcpus=1 nousb" 
--initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic

and then, triggers a panic:
 echo c > /proc/sysrq-trigger

and now we got reboot into secondary kernel, but at this process, we
will got this call trace with 100% reproducible:

[14257.863168] Initializing cgroup subsys net_prio
[14257.864506] Initializing cgroup subsys hugetlb
[14257.865898] CPU: Physical Processor ID: 0
[14257.867035] CPU: Processor Core ID: 0
[14257.869296] mce: CPU supports 0 MCE banks
[14257.870495] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
[14257.870495] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
[14257.901734] ftrace: allocating 30063 entries in 118 pages

[14258.976524] [ cut here ]
[14258.983143] WARNING: CPU: 0 PID: 1 at 
/build/linux-lts-vivid-PmeBs4/linux-lts-vivid-3.19.0/arch/x86/kernel/apic/apic.c:1400
 setup_local_APIC+0x27f/0x340()
[14259.005863] Modules linked in:
[14259.009221] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-80-generic 
#88~14.04.1-Ubuntu
[14259.015315] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS 
VirtualBox 12/01/2006
[14259.021134]   88003191fe18 817b63c3 

[14259.036605]  81a8b9d0 88003191fe58 81075d6a 
88003191fdfc
[14259.055284]  0001  00f0 

[14259.061414] Call Trace:
[14259.063414]  [] dump_stack+0x63/0x81
[14259.067742]  [] warn_slowpath_common+0x8a/0xc0
[14259.076934]  [] warn_slowpath_null+0x1a/0x20
[14259.085878]  [] setup_local_APIC+0x27f/0x340
[14259.101292]  [] native_smp_prepare_cpus+0x2f2/0x3af
[14259.111873]  [] kernel_init_freeable+0xaf/0x1f9
[14259.114495]  [] ? rest_init+0x80/0x80
[14259.116783]  [] kernel_init+0xe/0xf0
[14259.118990]  [] ret_from_fork+0x58/0x90
[14259.121292]  [] ? rest_init+0x80/0x80
[14259.123341] ---[ end trace 7384fc8d5897e3f0 ]---
[14259.130738] Spurious LAPIC timer interrupt on cpu 0
[14259.153429] do_IRQ: 0.145 No irq handler for vector (irq -1)
[14259.157634] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[14259.161002] smpboot: CPU0: Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz (fam: 
06, model: 4e, stepping: 03)

** 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/1771546

Title:
  WARNING: setup_local_APIC+0x27f/0x340

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

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

[Bug 1738164] Re: [snap] U2F doesn't work with yubikey

[Chris Cowling]

It appears that apparmor is blocking u2f requests :


[ 5955.568022] audit: type=1400 audit(1526465659.599:92): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:045E:07B2.0001/report_descriptor"
 pid=19386 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[ 5955.568379] audit: type=1400 audit(1526465659.599:93): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.1/0003:045E:07B2.0002/report_descriptor"
 pid=19386 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[ 5955.568667] audit: type=1400 audit(1526465659.599:94): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.2/0003:045E:07B2.0003/report_descriptor"
 pid=19386 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[ 5955.569840] audit: type=1400 audit(1526465659.599:95): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:1050:0407.002D/report_descriptor"
 pid=19386 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[ 5955.570337] audit: type=1400 audit(1526465659.603:96): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" 
name="/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:1050:0407.002E/report_descriptor"
 pid=19386 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0

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

Title:
  [snap] U2F doesn't work with yubikey

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

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

[Bug 1659604] Re: root disk flavor constraints not applied to nova-lxd instances when config-drive is used

[Alex Kavanagh]

It sounds like this is probably fixed.  Just need to schedule a test to
check if it has been.

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

Title:
  root disk flavor constraints not applied to nova-lxd instances when
  config-drive is used

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova-lxd/+bug/1659604/+subscriptions

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

[Bug 1759723] Re: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation.

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: Fix Released => 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/1759723

Title:
  ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle
  hangs after hotplug CPU add operation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1759723/+subscriptions

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

[Bug 1771542] 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 1771542

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/1771542

Title:
  Suspend to idle: Open lid didn't resume

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

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

[Bug 1771545] [NEW] root.key might be missing

[Alexander Traud]

Public bug reported:

Not the underlying package libunbound2 but only the big DNS resolver
package unbound contains a script to install/copy the root.key. If you
install just unbound-anchor, unbound-host, or -dev, this does not happen
and all tools which rely on libunbound.so might not work.

Steps to Reproduce
1) install Ubuntu 18.04 LTS for Desktop (in my case, Minimal)
2) $ sudo apt remove unbound
3) $ sudo apt install unbound-anchor
4) $ sudo unbound-anchor

Expected Result
This should install a root.key at /var/lib/unbound/, because that is the 
default location, given unbound-anchor at compile time.

Actual Result
libunbound error: unable to open /var/lib/unbound/root.key for reading: No such 
file or directory
libunbound error: error reading auto-trust-anchor-file: 
/var/lib/unbound/root.key
libunbound error: validator: error in trustanchors config
libunbound error: validator: could not apply configuration settings.
libunbound error: module init for module validator failed

Notes
This happens *even* after changing the file
/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf
and its "auto-trust-anchor-file" to "/usr/share/dns/root.key" (package 
dns-root-data). The same issue happens with $ unbound-host -D example.com
I am not sure how to solve this. My first guess would be that not the package 
unbound but the package libunbound2 should install that key file (script 
root_trust_anchor_update). This affects not only -anchor and -host but all apps 
which rely on libunbound.so, because those tools expect that 
"/var/lib/unbound/root.key" exists.

Workarounds
A) create the file yourself:
sudo mkdir /var/lib/unbound
sudo cp /usr/share/dns/root.key /var/lib/unbound/
B) specify the key of the package dns-root-data as command-line option:
sudo unbound-anchor -a "/usr/share/dns/root.key"
   I was not able to use this approach for unbound-host.
C) install the whole DNS resolver:
sudo apt install unbound
D) in your own app, instead of one, try two files:
if (0 == access("/var/lib/unbound/root.key", R_OK)) {
status_unbound = ub_ctx_add_ta_file(ub_context, 
"/var/lib/unbound/root.key");
} else {
status_unbound = ub_ctx_add_ta_file(ub_context, 
"/usr/share/dns/root.key");
}

** Affects: unbound (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/1771545

Title:
  root.key might be missing

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

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

[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

[Penn Mackintosh]

I have a patch, taken from SO.

Patch is attached for package xorg-server.
After building with it, you need to install xserver-xorg-core-*.deb package 
generated.
I have attached the .deb too.

** Attachment added: "AMD64 .deb included"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1244090/+attachment/5140329/+files/patches.zip

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1244090/+subscriptions

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

[Bug 159356] Re: System freeze on high memory usage

[mostafa741 via ubuntu-bugs]

still happens with Fedora 28

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

Title:
  System freeze on high memory usage

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

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

[Bug 1767091] Re: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 30

[Francis Ginther]

** Tags added: id-5af997fc3ad8c3a41ba1538e

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

Title:
  package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade:
  installed shim-signed package post-installation script subprocess
  returned error exit status 30

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

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

[Bug 1770770] Re: Switch Build-Depends: transfig to fig2dev

[Kleber Sacilotto de Souza]

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

** Changed in: linux (Ubuntu Bionic)
   Status: New => 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/1770770

Title:
  Switch Build-Depends: transfig to fig2dev

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

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

[Bug 1295267] Re: Windows change Monitor/Desktop after screen lock

[Jeff Van Epps]

Similar but maybe not. This is the closest match I've been able to find.
Screens sleep (not lock), when I hit a key to wake it up one window has
moved from one monitor to the other. Always VirtualBox Manager and only
that, not Thunderbird or Chrome or empathy or terminal or anything else
I've found. Ubuntu 18.04 GNOME on Wayland. Nvidia GTX590 using two DVI
ports, one has an adapter to connect to VGA monitor.

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

Title:
  Windows change Monitor/Desktop after screen lock

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

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

[Bug 1743637] Re: QEMU vhost-user shutdown suffers from use after free (missing clean shutdown)

[Launchpad Bug Tracker]

This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.28

---
qemu (1:2.5+dfsg-5ubuntu10.28) xenial-security; urgency=medium

  * SECURITY UPDATE: arbitrary code execution via load_multiboot
- debian/patches/CVE-2018-7550.patch: handle bss_end_addr being zero in
  hw/i386/multiboot.c.
- CVE-2018-7550

 -- Marc Deslauriers   Fri, 11 May 2018
13:34:24 -0400

** Changed in: qemu (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-7550

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

Title:
  QEMU vhost-user shutdown suffers from use after free (missing clean
  shutdown)

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

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

[Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

[Peridot]

I tested with 4.17 rc4 and the problem persists

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

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

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

[Bug 1768823] Re: netplan ip leases traceback when interface not managed by netplan or set to DHCP

[Eric Desrochers]

** Changed in: netplan
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: netplan
   Status: New => 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/1768823

Title:
  netplan ip leases  traceback when interface not managed by
  netplan or set to DHCP

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

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

[Bug 1769613] Re: ubuntu-release-upgrader crashed

[dino99]

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

Title:
  ubuntu-release-upgrader crashed

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

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

[Bug 1761751] Re: Black screen on 18.04 + AMD RX460

[semreh]

Problem still exists in 4.16.9 kernel from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.9/
(#uname -r output is 4.16.9-041609-generic )

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

Title:
  Black screen on 18.04 + AMD RX460

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

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

[Bug 1771524] Re: Merge newer dovecot for Cosmic

[ Christian Ehrhardt ]

Also libstemmer-dev is now in main
$ apt-cache policy libstemmer-dev
libstemmer-dev:
  Installed: (none)
  Candidate: 0+svn585-1build1
  Version table:
 0+svn585-1build1 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

So we can depend on that as well now.

Lets try to re-submit the tests to Debian?
TODO - ensure they work with the latest dovecot first

And also Lucene - maybe the old issue is fixed now.
TODO - recheck #1524526

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

Title:
  Merge newer dovecot for Cosmic

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

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

[Bug 1771561] Re: I am unable to upgrade my system

[Raghvendra Mishra]

Getting this error message,

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

 This can be caused by:
 * Upgrading to a pre-release version of Ubuntu
 * Running the current pre-release version of Ubuntu
 * Unofficial software packages not provided by Ubuntu

If none of this applies, then please report this bug using the command
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.

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

Title:
  I am unable to upgrade my system

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

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

[Bug 1738164] Re: [snap] U2F doesn't work with yubikey

[Olivier Tilloy]

@Chris: can you try the following, and report whether this addresses the
issue:

snap refresh chromium --channel=candidate/raw-usb-test
snap connect chromium:raw-usb

Thanks!

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [snap] U2F doesn't work with yubikey

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

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

[Bug 1771561] [NEW] I am unable to upgrade my system

[Raghvendra Mishra]

Public bug reported:

Unable to upgrade, getting third-party package issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.25
ProcVersionSignature: Ubuntu 4.4.0-125.150-generic 4.4.128
Uname: Linux 4.4.0-125-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: X-Cinnamon
Date: Wed May 16 18:18:21 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20130203-1
InstallationDate: Installed on 2016-05-15 (730 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to xenial on 2018-05-16 (0 days ago)
VarLogDistupgradeTermlog:

** 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/1771561

Title:
  I am unable to upgrade my system

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

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

[Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

[Mathieu Trudel-Lapierre]

This is fixed in cosmic; there a new version of initramfs-tools
(0.130ubuntu6).

** Changed in: initramfs-tools (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/1769682

Title:
  NFS-based remote root hangs when running 'netplan apply'

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

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

[Bug 1760104] Re: Xorg crashed with SIGSEGV

[Alan Pope  濾]

I've added a task for snapd, because this only happens when I'm doing
"snap install" something. Usually at the point when it connects the
opengl interface.

** Information type changed from Private to Public

** Also affects: snapd
   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/1760104

Title:
  Xorg crashed with SIGSEGV

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

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

[Bug 1771628] [NEW] Grpahic Drivers

[Gurjeet]

Public bug reported:

Hi,

I'm getting a purple blank screen after putting my creadentials when the
computer is starting.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 16 19:05:08 2018
DistUpgraded: 2018-05-16 16:54:13,314 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704]
InstallationDate: Installed on 2016-11-01 (560 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:670c Microdia 
 Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
 Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=247af43d-40d7-48c1-8502-e54796f36b07 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-16 (0 days ago)
dmi.bios.date: 06/14/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.4
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
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 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/1771628

Title:
  Grpahic Drivers

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

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

[Bug 1763096] Re: Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1)

[Matthias Klose]

** Also affects: binutils (Ubuntu Bionic)
   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/1763096

Title:
  Multiple memory corruption in as-new (binuitils-2.30-15ubuntu1)

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

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

[Bug 1771630] [NEW] package mysql-server-5.7 (not installed) failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127

[Houmed AHMED]

Public bug reported:

n/a

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mysql-server-5.7 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May  9 01:14:31 2018
DuplicateSignature:
 package:mysql-server-5.7:(not installed)
 Setting up mysql-server-5.7 (5.7.22-0ubuntu18.04.1) ...
 /var/lib/dpkg/info/mysql-server-5.7.postinst: line 191: 
/usr/share/mysql-common/configure-symlinks: No such file or directory
 dpkg: error processing package mysql-server-5.7 (--configure):
  installed mysql-server-5.7 package post-installation script subprocess 
returned error exit status 127
ErrorMessage: installed mysql-server-5.7 package post-installation script 
subprocess returned error exit status 127
InstallationDate: Installed on 2018-05-07 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
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: mysql-5.7
Title: package mysql-server-5.7 (not installed) failed to install/upgrade: 
installed mysql-server-5.7 package post-installation script subprocess returned 
error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mysql-5.7 (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/1771630

Title:
  package mysql-server-5.7 (not installed) failed to install/upgrade:
  installed mysql-server-5.7 package post-installation script subprocess
  returned error exit status 127

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

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

[Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

[Joseph Salisbury]

@Peridot, 
Request from Upstream:

For the original 4.13 kernel, I don't
see any attachments that have the AMD-Vi messages in question.  Were they
completion timeouts (like in the later mainline kernel test, which I'll
get to in a bit) or I/O page fault messages?  Without that information it
is hard to determine what the issue really is.

(Just as an FYI, if the IOMMU is disabled in BIOS, then iommu=soft is not
 necessary on the kernel command line).

For the upstream kernel test, since this is a Ryzen system, it's possible
that the BIOS does not have a requisite fix for SME and IOMMU (see [1]).
On the upstream kernel, if memory encryption is active by default without
this BIOS fix, then the result is AMD-Vi completion-wait timeout messages.
Try booting with mem_encrypt=off on the kernel command line or build a
kernel with CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=n and see if that
allows the kernel to boot.

Thanks,
Tom

[1] https://bugzilla.kernel.org/show_bug.cgi?id=199513

** Bug watch added: Linux Kernel Bug Tracker #199513
   https://bugzilla.kernel.org/show_bug.cgi?id=199513

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

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

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

[Bug 1768620] Re: removal_blacklist.cfg updates

[Brian Murray]

Yes, they are intentional. The last upload of ubuntu-release-upgrader
was on April 18th, I guess the archive admins were busy in the week
before release and a lot of packages were demoted thereby causing the
set of demoted packages to be updated.

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

Title:
  removal_blacklist.cfg updates

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

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

[Bug 1771630] Re: package mysql-server-5.7 (not installed) failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 127

[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/1771630

Title:
  package mysql-server-5.7 (not installed) failed to install/upgrade:
  installed mysql-server-5.7 package post-installation script subprocess
  returned error exit status 127

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

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

[Bug 1664737] Re: [ARM] : Unable to use Cinder volumes on ARM

[Sean Feole]

Wanted to update this bug with my findings so far, I have found the
linaro commit that fixed this issue here:
https://www.redhat.com/archives/libvir-list/2016-October/msg00396.html

I was in the process of testing bionic, however was blocked due to a few
juju bugs last week,(See: https://launchpad.net/juju/2.4/2.4-beta2 )
those bugs have since been repaired.  My test hardware was temporarily
removed last week and waiting until resources are back to continue with
testing.

Steps moving forward are to deploy Queens + Bionic on arm64, test cinder
volume hotplug. If the same symptoms remain , then recreate the process
manually without using openstack. as Christian mentioned in one of the
above comments.

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

Title:
  [ARM]  : Unable to use Cinder volumes on ARM

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

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

[Bug 1769737] Re: clang-format has no default symlink without version (has only clang-format-6.0)

[Matthias Klose]

** Also affects: llvm-defaults (Ubuntu Bionic)
   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/1769737

Title:
  clang-format has no default symlink without version (has only clang-
  format-6.0)

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

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

[Bug 1768756] Re: Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

[Olivier Tilloy]

So, just to confirm (and try to reproduce the issue here): "sudo apt
install libreoffice" ?

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

Title:
  Libreoffice 6 does not start on Kubuntu 18.04 (clean install)

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

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

[Bug 1765105] Re: HP Smart Array driver fails to load, kernel panics boot process

[Roberto]

*** This bug is a duplicate of bug 1765232 ***
https://bugs.launchpad.net/bugs/1765232

I have same problem on HP Proliant ML350 G5 on P400 smart array board,
it's a kernel issue, last working kernel from ubuntu ppa or kernel.org
is 4.13.16

>From kernel 4.14.1, no boot

Tested also other live distrobutions with kernel 4.15 or 4.14 same
issue, I opened a bug on bugzilla.kernel

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

Title:
  HP Smart Array driver fails to load, kernel panics boot process

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

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

[Bug 1771364] Re: wireless headset not detecting 16.04

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc5


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  wireless headset not detecting 16.04

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

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

[Bug 1771446] Re: package linux-headers-4.4.0-96-generic 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package linux-headers-4.4.0-96-generic 4.4.0-96.119 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

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

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

[Bug 1771431] Re: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer)

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics
  manufacturer)

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

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

[Bug 1771309] Re: linux-libc-dev: linux/errno.h referrs to non-existing asm/errno.h

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

** Tags added: kernel-da-key

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

Title:
  linux-libc-dev: linux/errno.h referrs to non-existing asm/errno.h

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

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

[Bug 1771301] Re: Setting ipv6.disable=1 prevents both IPv4 and IPv6 socket opening for VXLAN tunnels

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

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

** Tags added: kernel-da-key

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

Title:
  Setting ipv6.disable=1 prevents both IPv4 and IPv6 socket opening for
  VXLAN tunnels

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

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

[Bug 1771344] Re: Fix enabling bridge MMIO windows

[Joseph Salisbury]

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

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Bionic)
   Status: New => 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/1771344

Title:
  Fix enabling bridge MMIO windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771344/+subscriptions

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

[Bug 1771344] Re: Fix enabling bridge MMIO windows

[Joseph Salisbury]

I built a test kernel with commit 13a83eac373c49c0a081cbcd137e79210fe78acd.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1771344

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-image-unsigned, linux-modules and linux-modules-extra .deb packages.

Thanks in advance!

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

Title:
  Fix enabling bridge MMIO windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771344/+subscriptions

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

[Bug 1771557] Re: NVMe boot drives not supported - failing in generating initramfs

[Guilherme G. Piccoli]

** Description changed:

- [Impact] 
- The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to 
nvmeXnY block device, so it's failing and not building the initram disk.
+ [Impact]
  
- Upstream solution is composed for at least 2 patches (it's a series, but
+ When creating the initramfs image, mkinitramfs has multiple options on
+ how to include modules. The default (and most common) one is the
+ "MODULES=most", which includes the majority of filesystem modules and
+ all the block device drivers. One other option is "MODULES=dep", which
+ tries to descend in the sysfs hierarchy and guess modules to add, with
+ the goal of reduce the size of initramfs.
+ 
+ For the MODULES=dep case, the initramfs-tools hook-functions script
+ cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing in
+ the sysfs lookup, so it does not build the initram disk.
+ 
+ Upstream solution is composed of at least 2 patches (it's a series, but
  the 2 below are really the needed ones):
  
  commit 3cb744c9
  Author: Ben Hutchings 
  hook-functions: Rewrite block device sysfs lookup to be generic
  
  commit 8ac52dc0
  Author: Ben Hutchings 
  hook-functions: Include modules for all components of a multi-disk device
  
- Instead of doing the backport, which is huge, we added another sed 
substitution: currently the script has substitutions for sdX and hdX, in order 
to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to 
nvmeXnY.
- It's less intrusive than the full backport, since this is a SRU to Trusty 
only.
+ Instead of doing the huge backport, we added another sed substitution: 
currently the script has substitutions for sdX and hdX, in order to convert 
sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY.
+ It's less intrusive than the full backport, since this is a minimal SRU to 
Trusty only.
  
  
  [Test Case]
- To be added.
+ 1. Install Trusty with rootfs in a multi-disk(md) array composed of two nvme 
partitions - in my tests, I've used a RAID1.
+ 
+ (lsblk output of my test env:
+ 
+ nvme0n1 259:0010G  0 disk  
+ └─nvme0n1p1 259:1010G  0 part  
+   └─md0   9:0010G  0 raid1 /
+ nvme1n1 259:2010G  0 disk  
+ └─nvme1n1p1 259:3010G  0 part  
+   └─md0   9:0010G  0 raid1 /
+ )
  
  
- [Regression Potential] 
- If the sed expression was somewhat broken, we could have an issue generating 
initiramfs for generic block devices, like regular HDDs.
+ 2. Once system is booted, modify the "/etc/initramfs-tools/initramfs.conf", 
replacing "MODULES=most" to "MODULES=dep".
+ 
+ 3. Update your initramfs by running something like:
+ "update-initramfs -u -k "
+ 
+ The initramfs creating procedure will fail, unless the patch from this
+ LP is present.
+ 
+ 
+ [Regression Potential]
+ If the sed expression was somewhat broken, we could have an issue generating 
initiramfs when MODULES is set to "dep", even for generic block devices (like 
regular HDDs).
  
  
  [Other Info]
  This issue is based on Debian bug #785147: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147

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

Title:
  NVMe boot drives not supported - failing in generating initramfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+subscriptions

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