[Bug 1856485] Re: ERROR neutron.manager [-] Plugin 'calico' not found.

[Neil Jerram]

Thanks Bence.  FYI, in Neutron I believe
https://review.opendev.org/#/c/691874/ has already broken Python 2, so
the ship has now sailed for almost all new OpenStack deployments
(excepting any that are Swift-only, or still using nova-net if that is
possible).

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

Title:
  ERROR neutron.manager [-] Plugin 'calico' not found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-calico/+bug/1856485/+subscriptions

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

[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images

[iveskim]

I tested the patch in Comment #34, and it was also failed to pass 5 iterations.
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "aarch64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 3987
[New LWP 3988]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
0xbd2b3154 in __GI_ppoll (fds=0xe80ef080, nfds=187650381360708, 
timeout=, sigmask=0xc31815f0)
at ../sysdeps/unix/sysv/linux/ppoll.c:39
39  ../sysdeps/unix/sysv/linux/ppoll.c: No such file or directory.
(gdb)

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

Title:
  qemu-img hangs on rcu_call_ready_event logic in Aarch64 when
  converting images

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

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

[Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Juan Carlos Carvajal Bermúdez]

For anyone struggling with this hideous bug, try the following:

add "nvme_core.default_ps_max_latency_us=250" in /etc/default/grub, for
example:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=off
nvme_core.default_ps_max_latency_us=250"

then run "update-grub"

My laptop has been running smoothly for a week now. (/dev/nvme0n1
S444NY0K600040 SAMSUNG MZVLB256HAHQ-0 1 81.09 GB / 256.06 GB 512 B +
0 B EXD7101Q)

see more infos here:
https://wiki.archlinux.org/index.php/Solid_state_drive/NVMe

@kernel developers, would it not be great to detect such disks and lower
automatically the nvme_core.default_ps_max_latency_us? Thi bug is really
hard to detect and solve because there are NO logs whatsoever. Disk goes
read-only ya know?

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

Title:
  Samsung SSD corruption (fsck needed)

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

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

[Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic

[Ivan]

Hi all, 
I have Dell Vostro 15 and i have the same problem, can some one give me step by 
step how to fix it?

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

Title:
  Synaptics s3203 touchpad not working after update to kernel
  4.15.0-72-generic

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

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

[Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[trong luu]

I think other SSD type is last option. But, i really want find out root
cause of the problem. As my understanding, system booted up with Opts:
errors=remount-ro. Then something went wrong, system switched to ro mode
to protect file system. Do you have checked system log, have any
abnormal log? NVME is becoming more and more popular. This is the big
problem with linux user.

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

Title:
  Samsung SSD corruption (fsck needed)

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

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

[Bug 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1854744
  packages:
main: linux-raspi2-5.3
meta: linux-meta-raspi2-5.3
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 18. December 2019 00:28 UTC
+ phase: Promote to Proposed
+ phase-changed: Wednesday, 18. December 2019 09:13 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- review in progress
  variant: debs

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

Title:
  bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

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

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

[Bug 1849859] Re: smb printing fails

[Xu Xiaopeng]

problem reproduced on my Ubuntu 19.10

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

Title:
  smb printing fails

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

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

[Bug 1856811] Re: Systemd warning

[Paul White]

** Package changed: ubuntu => systemd (Ubuntu)

** Tags added: focal

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

Title:
  Systemd warning

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

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

[Bug 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

Title:
  bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker

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

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

[Bug 1851380] Re: root can lift kernel lockdown

[Niklas Sombert]

Yes, there are solutions to this that don't expose the whole kernel to
root.

 * This project's kernel module could use DKMS. This could make use of the MOK 
workflow already present in Ubuntu.
 * This project's kernel module could be included in the upstream kernel.

The last option would be more secure, but more difficult to achieve.

I don't think this can be solved in Ubuntu, so let's continue this
discussion in the first upstream issue you linked. (Although I'd
probably need to take a look at the source code and I don't know any
C#.)

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

Title:
  root can lift kernel lockdown

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

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

[Bug 1856604] Re: First char appears twice when searching in "Save as..." dialog in every application

[Marcus Tomlinson]

** Package changed: libreoffice (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  First char appears twice when searching in "Save as..." dialog in
  every application

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1856604/+subscriptions

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

[Bug 1557215] Re: "The update information is outdated" warning won't go away. No information given about how to fix

[Koen Roggemans via ubuntu-bugs]

I see this same behaviour regularly on systems running 18.04 as well.
Running sudo apt update makes the update process resume - no errors shown.

Without doing that the system reports that it is up to date and it
isn't, making it unsafe.

Non techy users freak out on using a command line command. I think this
could and should be self healing, eg by running an apt update on resume
after network up.

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

Title:
  "The update information is outdated" warning won't go away. No
  information given about how to fix

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

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

[Bug 1856749] Re: bionic/linux: 4.15.0-74.83 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Wednesday, 18. December 2019 04:06 UTC
  reason:
prepare-package: Ongoing -- {} package not yet fully built
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,meta:depwait,signed:depwait
  replaces: bug 1854819
  trackers:
bionic/linux/pc-kernel: bug 1856747
bionic/linux/pc-lowlatency-kernel: bug 1856748
xenial/linux-hwe: bug 1856804
  variant: debs

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

Title:
  bionic/linux: 4.15.0-74.83 -proposed tracker

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

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

[Bug 1854661] Re: If an app is active, instead of displaying a red dot next to the dash icon, why not display a green dot?

[Daniel van Vugt]

If it's a desktop monitor then you should also have some controls on
that to adjust the colour. Remember the dots should look like a well
saturated orange, not red.

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

Title:
  If an app is active, instead of displaying a red dot next to the dash
  icon, why not display a green dot?

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

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

[Bug 1854817] Re: xenial/linux-deeplens: 4.15.0-1014.14 -proposed tracker

[Gavin Lin]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   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/1854817

Title:
  xenial/linux-deeplens: 4.15.0-1014.14 -proposed tracker

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

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

[Bug 1854661] Re: If an app is active, instead of displaying a red dot next to the dash icon, why not display a green dot?

[Daniel van Vugt]

Attaching a picture would be problematic unless photographed next to an
accurate colour swatch. It's a function of the model of display you use,
its current colour profile, the model of camera you use and the
configuration of the display that we then view the final picture on. So
it's the kind of thing you should just take the reporter's word for.
We're not going to be able to see the same problem...

I think generally if those dots look too red then you should try playing
with:

  Settings > Devices > Colour

Try adding other profiles to make the dots look orange instead of red.
If that fails then you might want to try a different monitor, or
calibrating the one you have by getting a colorimeter such as
https://hughski.com/colorhug2.html

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

Title:
  If an app is active, instead of displaying a red dot next to the dash
  icon, why not display a green dot?

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

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

[Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Wednesday, 18. December 2019 05:08 UTC
  reason:
prepare-package: Ongoing -- {} package not yet fully built
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Pending -- builds not complete in ppa 
lrm:depwait,main:building,meta:failed,signed:depwait
  replaces: bug 1854762
  trackers:
eoan/linux/pc-kernel: bug 1856805
eoan/linux/pc-lowlatency-kernel: bug 1856806
  variant: debs

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

Title:
  eoan/linux: 5.3.0-26.28 -proposed tracker

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

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

[Bug 1856702] Re: LibreOffice window behind Firefox was flickering when Firefox asked me for a passsword to access the CUPS logs.

[Daniel van Vugt]

Can you please attach a video of the problem?

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

** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mutter (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/1856702

Title:
  LibreOffice window behind Firefox was flickering when Firefox asked me
  for a passsword to access the CUPS logs.

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

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

[Bug 1856811] Re: Systemd warning

[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/1856811/+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/1856811

Title:
  Systemd warning

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

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

[Bug 1854661] Re: If an app is active, instead of displaying a red dot next to the dash icon, why not display a green dot?

[Carlo Lobrano]

** Changed in: yaru-theme (Ubuntu)
   Status: New => Opinion

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

Title:
  If an app is active, instead of displaying a red dot next to the dash
  icon, why not display a green dot?

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

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

[Bug 1846199] Re: package yaru-theme-icon 19.10.4 failed to install/upgrade: unable to open '/usr/share/icons/Yaru/256x256@2x/mimetypes/presentation.png.dpkg-new': Operation not permitted

[Carlo Lobrano]

Indeed, file 256x256@2x/mimetypes/presentation.png.dpkg-new does not
exist.

In Yaru's icons folder we have a "256x256@2x/mimetypes/presentation.png"
but nothing with "dpkg-new" in the name. Could it be a script error,
maybe merging the name of the file with a dpkg command?

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

Title:
  package yaru-theme-icon 19.10.4 failed to install/upgrade: unable to
  open '/usr/share/icons/Yaru/256x256@2x/mimetypes/presentation.png
  .dpkg-new': Operation not permitted

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

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

[Bug 1848953] Re: Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working properly in Ubuntu 19.10

[florin]

@Kai-Heng Feng
I get nothing on that command ("dkms status"). I did lots of the things above, 
including installing kernels, dkms, removing dkms, etc.  They might have been 
contradictory, but either way, in my case, nothing happened, the driver was 
always grayed and cound not connect to the 2.4GHz (5 GHz works even with the 
card grayed in that list of proprietary drivers).

uname -r
5.4.0-050400rc6-generic

uname -a
Linux florin-SATELLITE-P50-C 5.4.0-050400rc6-generic #201911031940 SMP Mon Nov 
4 00:43:05 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working
  properly in Ubuntu 19.10

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

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