[Bug 1839317] Re: Grub fails to chainload the Windows Boot Manager

[AArch64]

I should add that I experienced this on an AArch64 platform.

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

Title:
  Grub fails to chainload the Windows Boot Manager

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

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

[Bug 1839099] Re: bionic/linux-hwe: 5.0.0-25.26~18.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1839106
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
- phase: Testing
- phase-changed: Tuesday, 06. August 2019 19:45 UTC
+ phase: Ready for Testing
+ phase-changed: Monday, 12. August 2019 05:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing 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/1839099

Title:
  bionic/linux-hwe: 5.0.0-25.26~18.04.1 -proposed tracker

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

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

[Bug 1839264] Re: xenial/linux-aws-hwe: 4.15.0-1045.47~16.04.1 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1839266
  packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
- phase: Testing
- phase-changed: Wednesday, 07. August 2019 14:22 UTC
+ phase: Ready for Testing
+ phase-changed: Monday, 12. August 2019 05:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing 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/1839264

Title:
  xenial/linux-aws-hwe: 4.15.0-1045.47~16.04.1 -proposed tracker

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

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

[Bug 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures

[Daniel van Vugt]

** Tags added: eoan

** Tags added: bionic

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

Title:
  Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel
  scrolling with touchpad and touch gestures

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

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

[Bug 1839693] Re: p54usb module in linux-modules-extra-5.0.0-23-generic does not work

[Po-Hsu Lin]

** Changed in: linux-hwe (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

Title:
  p54usb module in linux-modules-extra-5.0.0-23-generic does not work

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

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

[Bug 1839758] Re: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.

[Oleh Dmytrychenko]

Tested with latest mainline kernel and gnome is failing to start with
similar issue.

kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled 
seq=1, emitted seq=3
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 2210 thread gnome-shel:cs0 pid 2239
kernel: [drm] GPU recovery disabled.

** Attachment added: "syslog-5.3-rc4.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839758/+attachment/5282123/+files/syslog-5.3-rc4.log

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

Title:
  [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE
  kernel 5.0.

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

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

[Bug 1837788] Re: bcache kernel warning when attaching device

[Khaled El Mously]

** Changed in: linux (Ubuntu Disco)
   Status: In Progress => Fix Committed

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

Title:
  bcache kernel warning when attaching device

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

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

[Bug 1279226] Re: "map untrusted to domain = Yes" has no effect

[Launchpad Bug Tracker]

[Expired for samba (Ubuntu) because there has been no activity for 60
days.]

** Changed in: samba (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  "map untrusted to domain = Yes" has no effect

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

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

[Bug 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad

[Launchpad Bug Tracker]

[Expired for lvm2 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: lvm2 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Ubuntu 18.04 won't boot - failed to connect to lvmetad

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

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

[Bug 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu 18.04 won't boot - failed to connect to lvmetad

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

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

[Bug 1804183] Re: netronome firmware symlinks are overwritten by package upgrade

[Launchpad Bug Tracker]

[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  netronome firmware symlinks are overwritten by package upgrade

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

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

[Bug 1813463] Re: no bluetooth intel ac 9260

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  no bluetooth intel ac 9260

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

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

[Bug 1823725] Re: packet: reset network header if packet shorter than ll reserved space

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  packet: reset network header if packet shorter than ll reserved space

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

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

[Bug 1832041] Re: The mouse stops working

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  The mouse stops working

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

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

[Bug 1832609] Re: i don't know speak EL

[Launchpad Bug Tracker]

[Expired for Ubuntu because there has been no activity for 60 days.]

** Changed in: ubuntu
   Status: Incomplete => Expired

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

Title:
  i don't know speak EL

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

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

[Bug 1839798] Re: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 failed to install/upgrade: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 cannot be configured because libdrm-radeon1:amd64 i

[Chris Guiver]

Just an [off-topic] support note, but I would check your sources for
issues with your two architectures (ie. is something missing that has
held back your x86_64 and led to this?)

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

Title:
  package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 failed to
  install/upgrade: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1
  cannot be configured because libdrm-radeon1:amd64 is at a different
  version (2.4.91-2)

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

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

[Bug 1839758] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE
  kernel 5.0.

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

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

[Bug 1559391] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7: bcmwl kernel module failed to build [gcc: error: unrecognized command line option ‘-fstack-protector-strong’]

[Daniel van Vugt]

** Tags removed: wily
** Tags added: xenial

** Tags added: trusty

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7: bcmwl kernel module
  failed to build [gcc: error: unrecognized command line option
  ‘-fstack-protector-strong’]

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

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

[Bug 1839664] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module failed to build [gcc: error: unrecognized command line option ‘-fstack-protector-strong’]

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1559391, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module 
failed to build
+ bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel module 
failed to build [gcc: error: unrecognized command line option 
‘-fstack-protector-strong’]

** This bug has been marked a duplicate of bug 1559391
   bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7: bcmwl kernel module failed 
to build [gcc: error: unrecognized command line option 
‘-fstack-protector-strong’]

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.3: bcmwl kernel
  module failed to build [gcc: error: unrecognized command line option
  ‘-fstack-protector-strong’]

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

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

[Bug 1839777] Re: PC frezzes under NO heavy workload and gnome-shell.crash is created

[Daniel van Vugt]

I'm not sure any crash file ending in "122.crash" would be related
because 122 means it was probably the login screen, not your actual
session. Also that crash report seems to be unusable:

 https://errors.ubuntu.com/oops/406f2e9c-bc5b-11e9-a5ca-fa163e6cac46

Please:

1. Run:

   lspci -k > pci.txt

   and attach the file 'pci.txt'.

2. Reproduce the freeze again, then reboot and run:

   journalctl -b-1 > prevboot.txt

   and attach the file 'prevboot.txt'.



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

Title:
  PC frezzes under NO heavy workload and gnome-shell.crash is created

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

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

[Bug 1839687] Re: GDM displays black screen for a few seconds after resuming from suspend while using Nvidia proprietary drivers

[Daniel van Vugt]

** Tags added: nvidia

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

** Also affects: nvidia-graphics-drivers-430 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  GDM displays black screen for a few seconds after resuming from
  suspend while using Nvidia proprietary drivers

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

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

[Bug 1839758] Re: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.

[Kai-Heng Feng]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc4/

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

Title:
  [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE
  kernel 5.0.

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

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

[Bug 1839758] Re: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.

[Daniel van Vugt]

** Summary changed:

- System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.
+ [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 
5.0.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Tags added: regression-update

** Tags added: amdgpu

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

Title:
  [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE
  kernel 5.0.

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

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

[Bug 1839759] Re: Gdm3 asks password randomly when automatic login is enabled

[Daniel van Vugt]

Maybe related to bug 1740792.

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

Title:
  Gdm3 asks password randomly when automatic login is enabled

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

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

[Bug 1837598] Re: xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker

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

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

[Bug 1837598] Re: xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/snapdragon/4.4.0-1122.128/snapdragon-4.4-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker

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

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

[Bug 1837638] Re: Add the EFA driver into linux-aws

[Khaled El Mously]

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Disco)
   Status: In Progress => Fix Committed

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

Title:
  Add the EFA driver into linux-aws

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

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

[Bug 1839637] Re: Display driver missing

[Daniel van Vugt]

This sounds like a regression of bug 1727356. And it appears the patch
for that bug was dropped in mutter version:

  3.28.3+git20190124-0ubuntu18.04.1

because it was upstreamed and is in mutter version 3.28.4. And still is.

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

Title:
  Display driver missing

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

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

[Bug 1839260] Re: bionic/linux-snapdragon: 4.15.0-1060.66 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  bionic/linux-snapdragon: 4.15.0-1060.66 -proposed tracker

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

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

[Bug 1837598] Re: xenial/linux-snapdragon: 4.4.0-1122.128 -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
  
  derivatives: bug 1837596 (dragonboard-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839119
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Testing
  phase-changed: Thursday, 08. August 2019 07:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1837596
  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/1837598

Title:
  xenial/linux-snapdragon: 4.4.0-1122.128 -proposed tracker

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

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

[Bug 1839260] Re: bionic/linux-snapdragon: 4.15.0-1060.66 -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
  
  derivatives: bug 1839259 (dragonboard-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839293
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Ready for Testing
- phase-changed: Friday, 09. August 2019 19:45 UTC
+ phase: Testing
+ phase-changed: Monday, 12. August 2019 02:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1839259
  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/1839260

Title:
  bionic/linux-snapdragon: 4.15.0-1060.66 -proposed tracker

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

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

[Bug 1839637] Re: Display driver missing

[Daniel van Vugt]

Please:

1. Switch out of recovery mode and boot normally so as to reproduce the
bug.

2. Reboot again into recovery mode and then run:

   journalctl -b-1 > preboot.txt

   and then attach the file 'prevboot.txt' here.

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

Title:
  Display driver missing

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

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

[Bug 1833118] Re: featherpad does not syntax highlight with printer dialog open

[Tsu Jan]

Yes, that's the commit. V0.11.1 will be released soon. Apart from this
change, it contains a few minor fixes.

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

Title:
  featherpad does not syntax highlight with printer dialog open

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

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

[Bug 1839258] Re: bionic/linux-raspi2: 4.15.0-1043.46 -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
  
  derivatives: bug 1839257 (pi-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839293
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Friday, 09. August 2019 19:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-raspi2/pi-kernel: bug 1839257
  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/1839258

Title:
  bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker

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

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

[Bug 1837594] Re: xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.4.0-1118.127/raspi2-4.4-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker

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

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

[Bug 1837594] Re: xenial/linux-raspi2: 4.4.0-1118.127 -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
  
  derivatives: bug 1837592 (pi2-kernel)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839119
  packages:
main: linux-raspi2
meta: linux-meta-raspi2
  phase: Ready for Testing
  phase-changed: Tuesday, 06. August 2019 21:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-raspi2/pi2-kernel: bug 1837592
  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/1837594

Title:
  xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker

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

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

[Bug 1837594] Re: xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  xenial/linux-raspi2: 4.4.0-1118.127 -proposed tracker

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

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

[Bug 1839258] Re: bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker

[Taihsiang Ho]

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.15.0-1043.46/raspi2-4.15-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => Fix Released

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

Title:
  bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker

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

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

[Bug 1839258] Re: bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker

[Taihsiang Ho]

Hardware Certification have begun testing this -proposed kernel.

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => 
Taihsiang Ho (taihsiangho)

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

Title:
  bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker

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

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

[Bug 1839637] Re: Display driver missing

[Daniel van Vugt]

Can you please attach a photo or other evidence explaining how the
display driver is "missing"?

It's meant to be missing in recovery mode, so ignore that part.

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

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

Title:
  Display driver missing

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

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

[Bug 1839637] Re: [Intel Conroe] (EE) modeset(0): drmSetMaster failed: Permission denied

[Daniel van Vugt]

Oh, it's not a bug. Your machine is just stuck in recovery mode:

[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic
root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset


** Summary changed:

- [Intel Conroe] (EE) modeset(0): drmSetMaster failed: Permission denied
+ Display driver missing

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

Title:
  Display driver missing

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

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

[Bug 1839637] Re: Display driver missing

[Daniel van Vugt]

It appears you have an Intel CPU/GPU (Core 2 Duo E4500) and the Xorg
modesetting driver is failing to talk to the kernel driver properly:

[63.574] (EE) modeset(0): drmSetMaster failed: Permission denied


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- Display driver missing
+ [Intel Conroe] (EE) modeset(0): drmSetMaster failed: Permission denied

** Also 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/1839637

Title:
  Display driver missing

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

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

[Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

[Khaled El Mously]

** Changed in: mesa (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

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

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

[Bug 1839253] Re: Excessive screen tearing and flickering

[Daniel van Vugt]

If nothing gets added to the output when the flickering happens then
that answers my question, thanks.

This still feels like a kernel bug if not a hardware problem.

Do you notice any change if you wiggle the laptop screen? Try moving it
forward and backward. We next need to check if it's related to a loose
connection either in the screen or relating to the screen hinge.

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

Title:
  Excessive screen tearing and flickering

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

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

[Bug 1839798] Re: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 failed to install/upgrade: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 cannot be configured because libdrm-radeon1:amd64 i

[nader]

..

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

Title:
  package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 failed to
  install/upgrade: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1
  cannot be configured because libdrm-radeon1:amd64 is at a different
  version (2.4.91-2)

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

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

[Bug 1839798] [NEW] package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 failed to install/upgrade: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 cannot be configured because libdrm-radeon1:amd64

[nader]

Public bug reported:

..

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompositorRunning: None
Date: Mon Aug 12 06:32:03 2019
Dependencies:
 gcc-8-base 8.3.0-6ubuntu1~18.04.1
 libc6 2.27-3ubuntu1
 libdrm-common 2.4.97-1ubuntu1~18.04.1
 libdrm2 2.4.97-1ubuntu1~18.04.1
 libgcc1 1:8.3.0-6ubuntu1~18.04.1
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-55-generic, x86_64: installed
 nvidia, 390.116, 4.15.0-20-generic, x86_64: installed
DuplicateSignature:
 package:libdrm-radeon1:i386:2.4.97-1ubuntu1~18.04.1
 Setting up libffi6:i386 (3.2.1-8) ...
 dpkg: error processing package libdrm-radeon1:amd64 (--configure):
  package libdrm-radeon1:amd64 2.4.91-2 cannot be configured because 
libdrm-radeon1:i386 is at a different version (2.4.97-1ubuntu1~18.04.1)
ErrorMessage: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 cannot be 
configured because libdrm-radeon1:amd64 is at a different version (2.4.91-2)
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04ca]
 NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GF108M [GeForce GT 525M] [1028:04ca]
InstallationDate: Installed on 2019-08-11 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Inspiron N5110
PackageArchitecture: i386
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=9f2d3a5c-c2dc-43fd-948a-a62c676212f0 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.5-3
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: libdrm
Title: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 failed to 
install/upgrade: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 cannot be 
configured because libdrm-radeon1:amd64 is at a different version (2.4.91-2)
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/18/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0FXK2Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd07/18/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FXK2Y:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron N5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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: libdrm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package bionic i386 ubuntu

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

Title:
  package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 failed to
  install/upgrade: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1
  cannot be configured because libdrm-radeon1:amd64 is at a different
  version (2.4.91-2)

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

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

[Bug 1839253] Re: Excessive screen tearing and flickering

[Daniel van Vugt]

Also, did you verify that kernel 5.3 was running successfully?

  uname -a

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

Title:
  Excessive screen tearing and flickering

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

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

[Bug 1839798] Re: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 failed to install/upgrade: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 cannot be configured because libdrm-radeon1:amd64 i

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

Title:
  package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 failed to
  install/upgrade: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1
  cannot be configured because libdrm-radeon1:amd64 is at a different
  version (2.4.91-2)

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

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

[Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it

[Daniel van Vugt]

** Summary changed:

- Bluetooth mouse sleeps after 5 seconds of inactivity
+ Bluetooth mouse sleeps after 5 seconds of inactivity, but 
btusb.enable_autosuspend=0 fixes it

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

Title:
  Bluetooth mouse sleeps after 5 seconds of inactivity, but
  btusb.enable_autosuspend=0 fixes it

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

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

[Bug 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C

[Daniel van Vugt]

It's difficult because it seems only certain laptop models will be
affected very often. And while no developers are affected by the bug
then it's unlikely to get fixed. Because nobody with the ability to fix
the bug has the hardware to reproduce the bug.

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe A/B/C

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

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

[Bug 1839376] Re: Bionic update: upstream stable patchset 2019-08-07

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  Bionic update: upstream stable patchset 2019-08-07

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

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

[Bug 1501049] Re: totem crashed with assertion failure [Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached]

[Daniel van Vugt]

** Tags removed: wily

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

Title:
  totem crashed with assertion failure [Totem:ERROR:totem-
  grilo.c:729:browse_cb: code should not be reached]

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

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

[Bug 1076499] Re: DVD AC-3 Audio is played in stereo in passthrough mode

[Daniel van Vugt]

Can you state which current Ubuntu versions are still affected by this
bug?

** Changed in: totem (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/1076499

Title:
  DVD AC-3 Audio is played in stereo in passthrough mode

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

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

[Bug 1837087] Re: gnome-shell/cinnamon crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bo

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashed with assertion failure 
../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: 
Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed.
+ gnome-shell/cinnamon crashed with assertion failure 
../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: 
Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed.

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

Title:
  gnome-shell/cinnamon crashed with assertion failure
  ../src/gallium/drivers/radeonsi/si_state_viewport.c:239:
  si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 &&
  bottom >= 1' failed.

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

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

[Bug 1837661] Re: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours

[Khaled El Mously]

** Changed in: linux-azure (Ubuntu Disco)
   Status: In Progress => Fix Committed

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

Title:
  [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the
  VM was unavailable for 2 hours

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

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

[Bug 1579205] Re: CONFIG_NR_CPUS=256 is too low

[Po-Hsu Lin]

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

Title:
  CONFIG_NR_CPUS=256 is too low

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

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

[Bug 1819881] Re: [CONFIG] please enable highdpi font FONT_TER16x32

[Po-Hsu Lin]

For those who would like to benefit from this fix, please:
1. For fonts in early boot stage:
  Add "fbcon=font:TER16x32" to the GRUB_CMDLINE_LINUX in
  /etc/default/grub and run "sudo update-grub" and reboot
2. For fonts after boot (not related to this fix, but you might
need this as well):
  Run "sudo dpkg-reconfigure console-setup" to choose a bigger
  font. (if you need a non-interactive solution, please check
  https://askubuntu.com/questions/1105052

Thanks

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

Title:
  [CONFIG] please enable highdpi font FONT_TER16x32

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

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

[Bug 1726545] Re: Gparted not working in Wayland Ubuntu

[Bob Hyman]

And in Ubuntu 19.04.  This is getting old.  Maybe wayland should relent from 
their purist stance (after all Unix always allowed root to do absolutely 
anything to the file system, and that's the keys to the kingdom).  Maybe Ubuntu 
should accept the workaround GParted implements.  
But neither side wants to compromise their principals, resulting in a system 
that's not self-consistent.

Meantime, I've implemented a SUDO wrapper that works for Gparted and
other GUI apps, as advised by
https://wiki.archlinux.org/index.php/Running_GUI_applications_as_root#Using_xhost

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

Title:
  Gparted not working in Wayland Ubuntu

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

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

[Bug 1820760] Re: Teclast F6 Pro touchpad not recognized Ubuntu 18.04.2

[Po-Hsu Lin]

That's a good news, thank you for your patience.

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

Title:
  Teclast F6 Pro touchpad not recognized Ubuntu 18.04.2

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

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

[Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

[Hui Wang]

To check, please upload the output of the command as below:

ls /lib/modules/`uname -r`/updates/dkms

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

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

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

[Bug 1837087] Re: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cinnamon (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-shell crashed with assertion failure
  ../src/gallium/drivers/radeonsi/si_state_viewport.c:239:
  si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 &&
  bottom >= 1' failed.

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

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

[Bug 1837087] Re: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mesa (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-shell crashed with assertion failure
  ../src/gallium/drivers/radeonsi/si_state_viewport.c:239:
  si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 &&
  bottom >= 1' failed.

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

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

[Bug 1839786] Re: upgrade from 16.04 LTS to 18.04 Bionic Beaver fails - report says it is impossible to install a required package.

[Ubuntu Foundations Team Bug Bot]

** Tags added: xenial2bionic

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

Title:
  upgrade from 16.04 LTS to 18.04 Bionic Beaver fails - report says  it
  is impossible to install a required package.

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

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

[Bug 1839793] [NEW] Crash during install.

[Barbara Harris-Pruitt]

Public bug reported:

I was installing Ubuntu Mate 19.04 on a Dell XPS17 which has 16 GB RAM
and 2 1TB SHDD drives.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
Date: Sun Aug 11 19:49:52 2019
InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu-mate

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

Title:
  Crash during install.

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

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

[Bug 1839792] [NEW] package virtualbox-ext-pack 5.1.38-0ubuntu1.16.04.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2

[Ponciano Guevara perez]

Public bug reported:

Simply Virtualbox stopped working

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: virtualbox-ext-pack 5.1.38-0ubuntu1.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-157.185-generic 4.4.181
Uname: Linux 4.4.0-157-generic i686
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: i386
Date: Sun Aug 11 18:42:48 2019
DpkgHistoryLog:
 Start-Date: 2019-08-11  18:42:32
 Commandline: /usr/sbin/synaptic
 Requested-By: pgp (1000)
 Install: virtualbox-guest-utils:i386 (5.1.38-dfsg-0ubuntu1.16.04.3, 
automatic), virtualbox-guest-x11:i386 (5.1.38-dfsg-0ubuntu1.16.04.3)
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 2
InstallationDate: Installed on 2019-03-15 (149 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.32
SourcePackage: virtualbox-ext-pack
Title: package virtualbox-ext-pack 5.1.38-0ubuntu1.16.04.1 failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: virtualbox-ext-pack (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package virtualbox-ext-pack 5.1.38-0ubuntu1.16.04.1 failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1839792/+subscriptions

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

[Bug 1839790] Re: kglobalaccel5 crashed with SIGABRT in QMessageLogger::fatal()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1832701, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1839790/+attachment/5282076/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1839790/+attachment/5282078/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1839790/+attachment/5282081/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1839790/+attachment/5282082/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1839790/+attachment/5282083/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1839790/+attachment/5282084/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1839790/+attachment/5282085/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1832701
   kglobalaccel5 crashed with SIGABRT in raise()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  kglobalaccel5 crashed with SIGABRT in QMessageLogger::fatal()

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

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

[Bug 1790861] Re: amdgpu.dc dual monitor issues when trying to sleep / power off the monitors

[oh]

With amdgpu.dc=0 I get random mouse lag after moving my mouse quickly.
The cursor will just stop moving. I turned amdgpu.dc=1 and it went away.

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

Title:
  amdgpu.dc dual monitor issues when trying to sleep / power off the
  monitors

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

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

[Bug 1838919] Re: Slow and lost keyboard and mouse events

[Traumflug]

If you're running on Wayland it might be related to this:

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510

It looks like a busy gnome-shell (or -extension) can eat mouse movement
events, so it might eat keystrokes as well. Second way to reproduce the
issue (for testing whether you experience the same issue) is in

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510#note_577952

All this doesn't happen on X11, though.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1510
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510

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

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1332847] Re: Switching from russian to chinese does not work

[A.M. via ubuntu-bugs]

just note the default alphabet for pinyin is latin, not anything else.
We want it just work right out of the box, correct? Well, in 99.9% of
usecases. So user (any user, nub, advanced, etc) installs it and uses
it. With currently used 'default' approach, switching to the method does
not yields right layout. How many languages are there? How many of them
use pure latin alphabet (and thus compatible 'default' layout)? diving
latter by former you will get the percentage when it works (I suppose it
will be something around 50%. an exact figure can be taken by reviewing
all the languages with their respective layouts in conjunction with
available input methods. Hard to do, no doubt).

Using 'en' layout resolves the issue, by forcing an environment to
switch to this layout, and anyone can type hanzi seamless. Thus we have
uniformity. If you want to reuse dvorak layout (just for example), then
you have a choice to fix it by supplying an exact layout using either
available means (e.g. ibus-anthy, and such). It is for advanced users.

"but it would make it harder for users who prefer some other underlying
layout when using respective input method. It seems that they preferred
the flexibilty which "default" offers."

Could you estimate how many there is such an users? I think just a units
of percents, and it seems they are a kind of 'advanced' users, who is
able to make fine tuning of their software on their own.

Usually (99.9%?) latin alphabet is engraved on keyboards using plain
QWERTY, right? It is why "en-us", for example, is right candidate to the
'right' input method for pinyin.

just IMHO))

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

Title:
  Switching from russian to chinese does not work

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

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

[Bug 1837087] Re: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1

[Theo Shaw]

For what it's worth I'm getting a very similar issue on Linux Mint
Cinnamon after the update from 19.1 to 19.2. The error is:

 cinnamon: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239:
si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 &&
bottom >= 1' failed.

I've found that the positions of monitors in a dual monitor setup
dictates whether or not the DE crashes on startup. See this thread:
https://github.com/linuxmint/cinnamon/issues/8754 Hopefully the problem
is identical for you guys and a patch can fix both issues at once.

** Bug watch added: github.com/linuxmint/cinnamon/issues #8754
   https://github.com/linuxmint/cinnamon/issues/8754

** Also affects: cinnamon (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/1837087

Title:
  gnome-shell crashed with assertion failure
  ../src/gallium/drivers/radeonsi/si_state_viewport.c:239:
  si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 &&
  bottom >= 1' failed.

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

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

[Bug 1839782] Re: totem crashed with SIGABRT

[El jinete sin cabeza]

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

** Description changed:

  $ LANGUAGE=C totem
  Click 'Channels'
- Click 'MyCloudEX2Ultra'
+ Click 'ServerDLNA'
  Click 'Photos'
  Click 'All Photos'
  
  In console:
  **
  Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached
  Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be 
reached
  Abortado (`core' generado)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: totem 3.33.90-2ubuntu1
  Uname: Linux 5.2.8-050208-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 11 16:06:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (252 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: totem
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
-  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/libtotem.so.0
-  () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0
-  g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libtotem.so.0
+  () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0
+  g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: totem crashed with SIGABRT
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (252 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  totem crashed with SIGABRT

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

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

[Bug 1332847] Re: Switching from russian to chinese does not work

[Gunnar Hjalmarsson]

Just to clarify: When saying that there is no "right" or "wrong" I meant
the configuration of respective input method, i.e. "default" vs. some
specific layout. We are of course agreed on the fact that e.g. a Russian
layout is not compatible with an input method, which - as you say -
expects latin letters.

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

Title:
  Switching from russian to chinese does not work

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

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

[Bug 1839786] [NEW] upgrade from 16.04 LTS to 18.04 Bionic Beaver fails - report says it is impossible to install a required package.

[paul]

Public bug reported:

upgrade from 16.04 LTS to 18.04 Bionic Beaver fails - report says  it is
impossible to install a required package.

Currently installed:  16.04 LTS

Tried to upgrade to: 18.04 Bionic Beaver

Upgrade message said to report this problem as a bug.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.25
ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Sun Aug 11 14:27:15 2019
InstallationDate: Installed on 2018-02-14 (543 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to xenial on 2019-08-11 (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/1839786

Title:
  upgrade from 16.04 LTS to 18.04 Bionic Beaver fails - report says  it
  is impossible to install a required package.

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

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

[Bug 1332847] Re: Switching from russian to chinese does not work

[A.M. via ubuntu-bugs]

@gunnarhj
you are right, this is upstream issue.

And you are wrong about "right" and "wrong" layouts for this input
method. Pinyin implies latin letters input only. So, for example,
neither of languages of ex-USSR is suited for pinyin. Maybe some/many
others as well. When we switching to pinyin we expect just to start
typing and get hanzi, not anything else. En us is common input method,
any keyboard has it, so it seems reasonable to the method to have it as
standard (right) input method.

Just IMHO ))

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

Title:
  Switching from russian to chinese does not work

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

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

[Bug 1836176] Re: Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th

[Andrej Friesen]

Trying to use the fix in arch wiki does not work:

```
sudo rtcwake -m freeze -s 1
rtcwake: wakeup from "freeze" using /dev/rtc0 at Sun Aug 11 22:42:06 2019


rtcwake: write error
```

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

Title:
  Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th

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

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

[Bug 1836176] Re: Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th

[Andrej Friesen]

Also using this machine and tried the fix on the arch wiki.

I am using bios 1.35 and fedora 30:

uname -a
Linux x1-yoga 5.2.6-200.fc30.x86_64 #1 SMP Mon Aug 5 13:20:47 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

Can we do something to get better debugging information?

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

Title:
  Touchscreen stops working after S3 suspend on Lenovo X1 Yoga 3th

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

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

[Bug 1825544] Re: Switch User menu item gone after upgrade to Ubuntu 19.04

[peterzay]

When I log in to my (regular user) account early morning, the Switch
User menu item is not present.

When I log out late in the evening, the Switch User menu item is
present.

This is reproducible day in, day out.

This is the case even on days when there are no system updates or
upgrades at all.

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

Title:
  Switch User menu item gone after upgrade to Ubuntu 19.04

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

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

[Bug 1501049] Re: totem crashed with assertion failure [Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached]

[Apport retracing service]

** Tags added: eoan

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

Title:
  totem crashed with assertion failure [Totem:ERROR:totem-
  grilo.c:729:browse_cb: code should not be reached]

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

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

[Bug 1839782] Re: totem crashed with SIGABRT

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1501049, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1839782/+attachment/5282053/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1839782/+attachment/5282055/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1839782/+attachment/5282061/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1839782/+attachment/5282062/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1839782/+attachment/5282063/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1839782/+attachment/5282064/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1839782/+attachment/5282065/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1501049
   totem crashed with assertion failure 
[Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  totem crashed with SIGABRT

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

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

[Bug 1839771] Re: Install of 19.04 failed on Lenovo Thinkpad W520

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the instructions at
https://help.ubuntu.com/community/HowToMD5SUM.  You might also retry
your installation with new media.  In the event that is is not in fact
an error with your installation media please set the bug's status back
to New.  Thanks and good luck!

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

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

** Tags added: ident-mismatch

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

Title:
  Install of 19.04 failed on Lenovo Thinkpad W520

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

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

[Bug 1825544] Re: Switch User menu item gone after upgrade to Ubuntu 19.04

[John Ladasky]

Following up to my remarks from yesterday: when I logged out of my
primary account, I DID see a Switch User menu option from my secondary
account.  When I returned to the primary account, Switch User was not
present.  But that was yesterday.  On reboot today, Switch User has
reappeared in my primary account.  Perhaps a patch has fixed the
problem?

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

Title:
  Switch User menu item gone after upgrade to Ubuntu 19.04

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

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

[Bug 1839756] Re: Nvidia driver options are not easy to understand

[mark johnson]

Thanks for the response and the explanation Matthew,
the new design is a big improvement, good to know that it's already in the 
works!

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

Title:
  Nvidia driver options are not easy to understand

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

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

[Bug 1839777] Re: PC frezzes under NO heavy workload and gnome-shell.crash is created

[ProfWoland]

** Description changed:

  When I am in any program, mostly happen in Blender since I spend most time in 
it, PC freezes and becomes unresponsive and I need to hold down Power button to 
shut it down.
- After booting I get send report pop up but it doesn't work. Anyway I found 
_usr_bin_gnome-shell.122.crash so I figured that maybe gnome is problem and not 
blender which I thought at firts (I reported to them but got ignore because of 
hardware) 
- This happens when I don't have any complex object in Blender or other 
software (browsing etc) it just happens randomly withouth any specific steps 
and I am not 100% sure but I think it only happens if laptop was in sleep mode 
(lid closed). 
+ After booting I get send report pop up but it doesn't work it doesn't give me 
additional dialog window with information to finalize report. Anyway I found 
_usr_bin_gnome-shell.122.crash so I figured that maybe gnome is problem and not 
blender which I thought at first (I reported to them but got ignore because of 
hardware)
+ This happens when I don't have any complex object in Blender or other 
software (browsing etc) it just happens randomly withouth any specific steps 
and I am not 100% sure but I think it only happens if laptop was in sleep mode 
(lid closed).
  If you need any more info let me know.
+ 
+ I am running Ubuntu 18.04.04 up to date and problem stated a couple weeks 
ago. 
+ Here is whoopsie ID just in case.. 
https://errors.ubuntu.com/user/0d254e4708548044d7ec6883f56c6d626d435d58691f41caf0655b328c68de981013915470172d6e37fac6ba0d9310a56a5ebe5a4c8b3fe1d37fa69cfa697ef1
+ I'd upload .crash but I think it has sensitive data so I won't do that if 
there is a way to deliver safely let me know.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sun Aug 11 19:49:05 2019
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  PC frezzes under NO heavy workload and gnome-shell.crash is created

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

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

[Bug 1839777] [NEW] PC frezzes under NO heavy workload and gnome-shell.crash is created

[ProfWoland]

Public bug reported:

When I am in any program, mostly happen in Blender since I spend most time in 
it, PC freezes and becomes unresponsive and I need to hold down Power button to 
shut it down.
After booting I get send report pop up but it doesn't work it doesn't give me 
additional dialog window with information to finalize report. Anyway I found 
_usr_bin_gnome-shell.122.crash so I figured that maybe gnome is problem and not 
blender which I thought at first (I reported to them but got ignore because of 
hardware)
This happens when I don't have any complex object in Blender or other software 
(browsing etc) it just happens randomly withouth any specific steps and I am 
not 100% sure but I think it only happens if laptop was in sleep mode (lid 
closed).
If you need any more info let me know.

I am running Ubuntu 18.04.04 up to date and problem stated a couple weeks ago. 
Here is whoopsie ID just in case.. 
https://errors.ubuntu.com/user/0d254e4708548044d7ec6883f56c6d626d435d58691f41caf0655b328c68de981013915470172d6e37fac6ba0d9310a56a5ebe5a4c8b3fe1d37fa69cfa697ef1
I'd upload .crash but I think it has sensitive data so I won't do that if there 
is a way to deliver safely let me know.


ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.1
ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
Uname: Linux 4.15.0-55-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Sun Aug 11 19:49:05 2019
DisplayManager: gdm3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  PC frezzes under NO heavy workload and gnome-shell.crash is created

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

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

[Bug 982526] Re: remmina crashed with Segmentation fault (core dumped)

[Laurent Destailleur]

Unfortunately, i removed the file before reporting the turnaround to
check the theory was good. I forgot to make a backup. But you can see in
the strace into the "read" line that the content of the file si not a
content of a .remmina file compared to other files that start with
"[remmina]\nssh_..."

This track is for me enough to say that the file was corrupted (it has a
binary content of \0 instead of text content).

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

Title:
  remmina crashed with Segmentation fault (core dumped)

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

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

[Bug 1839770] Re: NVMe. Crash during installation

[TJ]

Please ensure the installer media image is not corrupt. In this case
UbiquitySyslog.txt reports:

Aug 11 16:12:44 ubuntu kernel: [ 3438.661203] SQUASHFS error: zlib 
decompression failed, data probably corrupt
Aug 11 16:12:44 ubuntu kernel: [ 3438.661208] SQUASHFS error: 
squashfs_read_data failed to read block 0x81e4e
Aug 11 16:12:44 ubuntu kernel: [ 3438.661875] SQUASHFS error: zlib 
decompression failed, data probably corrupt
Aug 11 16:12:44 ubuntu kernel: [ 3438.661877] SQUASHFS error: 
squashfs_read_data failed to read block 0x81e4e

** Changed in: ubiquity (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/1839770

Title:
  NVMe. Crash during installation

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

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

[Bug 1839756] Re: Nvidia driver options are not easy to understand

[Matthew Paul Thomas]

Hi mark, thanks for your report. We plan to improve this interface for
Ubuntu 19.10, as part of the inclusion of Nvidia drivers in the official
Ubuntu repositories.

I think the issue you are seeing, with a newer driver showing as
“tested” while an older one is not, is that the older one is what Nvidia
calls the “Long Lived” driver and the newer one the “Short Lived”, which
people choose depending on whether they want stability, compatibility
with the latest game updates, etc. So it’s not simply a case of “newer ×
tested” >> “older × untested”. When I designed the current UI, in
January 2012, that distinction had existed for only four months and I
wasn’t aware of it. Now, we’ll show Nvidia’s “Long Lived” and “Short
Lived” terminology in the GUI.

At the same time, as you suggested, we’ll drop technical wording that
doesn’t help you make a choice, like “metapackage” and “X.org X server”.

Here’s the new design:


** Changed in: software-properties (Ubuntu)
   Status: Invalid => Triaged

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

Title:
  Nvidia driver options are not easy to understand

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

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

[Bug 1838070] Re: Unable to add dyndbg to command line

[TJ]

The reason your "dyndbg=module e1000" does not work is because
dyndbg=... is only processed at boot time and therefore only affects
*built-in* modules. e1000 is a dynamically loaded module not a built-in.

What you need is the module.dyndbg=... form as in:

"e1000.dyndbg=+p"

See especially line 259, 291 of:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation
/admin-guide/dynamic-debug-howto.rst

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

Title:
  Unable to add dyndbg to command line

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

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

[Bug 1833118] Re: featherpad does not syntax highlight with printer dialog open

[Walter Lapchynski]

Looks like that fix is here:
https://github.com/tsujan/FeatherPad/commit/510d740aa556358555dc2ebccd84b8876ef908ba

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

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

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

Title:
  featherpad does not syntax highlight with printer dialog open

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

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

[Bug 1839773] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  MicroSD not mounted when inserted, used to work correctly

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

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

[Bug 1839773] Re: MicroSD not mounted when inserted, used to work correctly

[fcole90]

04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader [10ec:5287] (rev 01)
Subsystem: ASUSTeK Computer Inc. RTL8411B PCI Express Card Reader 
[1043:202f]
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at f7815000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at f780 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable- Count=1 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [170] Latency Tolerance Reporting
Capabilities: [178] L1 PM Substates
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci

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

Title:
  MicroSD not mounted when inserted, used to work correctly

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

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

[Bug 1838070] Re: Unable to add dyndbg to command line

[TJ]

This is correct. The essential thing to understand is the kernel's
command-line uses space as the separator between options so:

option1=1 option2=2 option3=3
option1=1 option2="2" option3="3 or 4"
option1=1 "option2=2" "option3=3 or 4"

are all identical.

What you are seeing in /proc/cmdline is the *kernel* writing out each
option and, when an option contains a space, it surrounds the option
with double-quotes.

Consider that the "=" symbol has no special meaning in the context of
the command line although individual modules *may* use it to separate
key=value options themselves.

** Changed in: grub2 (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/1838070

Title:
  Unable to add dyndbg to command line

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

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

[Bug 1839773] Re: MicroSD not mounted when inserted, used to work correctly

[fcole90]

I could now make it work, reinserting it again after removing it..

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

Title:
  MicroSD not mounted when inserted, used to work correctly

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

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

[Bug 1839773] [NEW] MicroSD not mounted when inserted, used to work correctly

[fcole90]

Public bug reported:

Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an
adaptor in my laptop's SD slot, but it was not mounted nor apparently
detected. I'm certain that until few weeks ago it was working correctly,
so I suppose the cause to be an update regression.

I tested the same card on another laptop using Ubuntu 18.04 LTS and it
works correctly. Also, I have tested another card (16GB) on the 19.10
laptop, and it's detected and mounted correctly.

Summary:
- 16GB SD card, FAT32 - Works with all Ubuntu versions
- 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 
19.10, at least 2 weeks ago was still working.

I'd be happy to help debugging this issue.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.2.0-10-generic 5.2.0-10.11
ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
Uname: Linux 5.2.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  fabio  2086 F pulseaudio
 /dev/snd/controlC0:  fabio  2086 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 11 19:50:53 2019
GvfsMonitorError:
 This tool has been deprecated, use 'gio mount' instead.
 See 'gio help mount' for more info.
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=0e34c56e-8605-499f-9588-f09829ff1e81
HotplugNewDevices:

HotplugNewMounts:

InstallationDate: Installed on 2019-02-03 (188 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp. USB Camera
 Bus 001 Device 006: ID 13d3:3408 IMC Networks
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X550JK
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic 
root=UUID=3eab3ace-7b67-4e6a-aea7-d31b73cc4819 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.2.0-10-generic N/A
 linux-backports-modules-5.2.0-10-generic  N/A
 linux-firmware1.181
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 19:51:12.078: The udisks-daemon is running (name-owner :1.10).
UpgradeStatus: Upgraded to eoan on 2019-07-21 (21 days ago)
dmi.bios.date: 10/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550JK.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550JK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550JK
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug eoan

** Description changed:

  Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an
  adaptor in my laptop's SD slot, but it was not mounted nor apparently
  detected. I'm certain that until few weeks ago it was working correctly,
  so I suppose the cause to be an update regression.
  
  I tested the same card on another laptop using Ubuntu 18.04 LTS and it
  works correctly. Also, I have tested another card (16GB) on the 19.10
  laptop, and it's detected and mounted correctly.
  
  Summary:
  - 16GB SD card, FAT32 - Works with all Ubuntu versions
- - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 
19.04, at least 2 weeks ago was still working.
+ - 32GB microSD with adaptor, FAT32 - Works in 18.04, stopped working with 
19.10, at least 2 weeks ago was still working.
  
  I'd be happy to help debugging this issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-10-generic 5.2.0-10.11
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  fabio  2086 F pulseaudio
-  /dev/snd/controlC0:  fabio  2086 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  fabio  2086 F pulseaudio
+  /dev/snd/controlC0:  fabio  2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 11 19:50:53 2019
  GvfsMonitorError:
-  This tool has been deprecated, use 'gio mount' instead.
-  See 'gio help mount' for more info.
+  This tool has been 

[Bug 1839764] Re: Video cuts out after 3 seconds

[bwallum]

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779]
Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1043:03da]
Kernel driver in use: radeon
Kernel modules: radeon
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI 
Audio [Radeon HD 6450 / 7450/8450/8490 OEM / R5 230/235/235X OEM] [1002:a...
Subsystem: ASUSTeK Computer Inc. Caicos HDMI Audio [Radeon HD 6450 / 
7450/8450/8490 OEM / R5 230/235/235X OEM] [1043:aa98]
Linux bob-desktop 5.0.0-25-generic #26-Ubuntu SMP Thu Aug 1 12:04:58 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
/usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server
[sudo] password for bob: 
Hit:1 http://archive.ubuntu.com/ubuntu disco InRelease
Hit:2 http://archive.canonical.com/ubuntu disco InRelease
Get:3 http://archive.ubuntu.com/ubuntu disco-updates InRelease [97.5 kB]
Get:4 http://archive.ubuntu.com/ubuntu disco-backports InRelease [88.8 kB]
Get:5 http://archive.ubuntu.com/ubuntu disco-security InRelease [97.5 kB]
Get:6 http://archive.ubuntu.com/ubuntu disco-proposed InRelease [255 kB]
Fetched 539 kB in 1s (410 kB/s)   
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
fbset is already the newest version (2.1-30).
hardinfo is already the newest version (0.5.1+git20180227-2).
inxi is already the newest version (3.0.33-1-0ubuntu1).
mesa-utils is already the newest version (8.4.0-1build1).
nux-tools is already the newest version (4.0.8+18.10.20180623-0ubuntu1).
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
System:
  Host: bob-desktop Kernel: 5.0.0-25-generic x86_64 bits: 64 
  Desktop: Gnome 3.32.2 Distro: Ubuntu 19.04 (Disco Dingo) 
Machine:
  Type: Desktop Mobo: ASUSTeK model: M5A97 R2.0 v: Rev 1.xx 
  serial:  BIOS: American Megatrends v: 1903 date: 07/11/2013 
CPU:
  Topology: 6-Core model: AMD FX-6300 bits: 64 type: MCP L2 cache: 2048 KiB 
  Speed: 1401 MHz min/max: 1400/3500 MHz Core speeds (MHz): 1: 1400 2: 1395 
  3: 1404 4: 1404 5: 1404 6: 1395 
Graphics:
  Device-1: AMD Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 
  driver: radeon v: kernel 
  Display: x11 server: X.Org 1.20.4 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1440x900~60Hz 
  OpenGL: renderer: AMD CAICOS (DRM 2.50.0 / 5.0.0-25-generic LLVM 8.0.0) 
  v: 3.3 Mesa 19.0.8 
Audio:
  Device-1: AMD SBx00 Azalia driver: snd_hda_intel 
  Device-2: Dynex 1.3MP Webcam type: USB driver: snd-usb-audio,uvcvideo 
  Sound Server: ALSA v: k5.0.0-25-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  driver: r8169 
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: 60:a4:4c:59:78:1c 
Drives:
  Local Storage: total: 968.80 GiB used: 93.94 GiB (9.7%) 
  ID-1: /dev/sda vendor: OCZ model: VERTEX460 size: 111.79 GiB 
  ID-2: /dev/sdb vendor: OCZ model: VERTEX460 size: 111.79 GiB 
  ID-3: /dev/sdc vendor: Seagate model: ST3160815AS size: 149.05 GiB 
  ID-4: /dev/sdd vendor: Hitachi model: HDT721064SLA360 size: 596.17 GiB 
Partition:
  ID-1: / size: 105.17 GiB used: 32.75 GiB (31.1%) fs: ext4 dev: /dev/sda1 
  ID-2: /home size: 109.91 GiB used: 61.19 GiB (55.7%) fs: ext4 
  dev: /dev/sdb 
  ID-3: swap-1 size: 4.81 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 21.2 C mobo: N/A gpu: radeon temp: 36 C 
  Fan Speeds (RPM): cpu: 0 
Info:
  Processes: 251 Uptime: 30m Memory: 7.69 GiB used: 1.59 GiB (20.7%) 
  Shell: bash inxi: 3.0.33 

mode "1440x900"
geometry 1440 900 1440 900 32
timings 0 0 0 0 0 0 0
accel true
rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
Name: radeondrmfb
Address : 0
Size: 5324800
Type: PACKED PIXELS
Visual  : TRUECOLOR
XPanStep: 1
YPanStep: 1
YWrapStep   : 0
LineLength  : 5888
Accelerator : No
Version: 1:7.7+19ubuntu12
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 16384 x 16384
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-0 disconnected (normal left inverted right x axis y axis)
VGA-0 connected primary 1440x900+0+0 (normal left inverted right x axis y axis) 
410mm x 256mm
   1440x900  59.90*+  74.98  
   1280x1024 75.0260.02  
   1280x960  75.0460.00  
   1024x768  75.0370.0760.00  
   800x600   72.1975.0060.3256.25  
   640x480   75.0072.8159.94  
   720x400   70.08  
fglrxinfo: command not found

Command 'nvidia-settings' not found, but can be installed with:

sudo apt install nvidia-settings

H/W path Device  Class   Description

 system  To be filled by O.E.M. (SKU)
/0   bus M5A97 R2.0
/0/0   

[Bug 1839764] Re: Video cuts out after 3 seconds

[bwallum]

I have recovered my system by going into recovery mode from grub.

I then reset the graphics to generic. It took a few attempts to do the
same thing before the graphics held up on the monitor as per normal
usage. I then booted into Ubuntu Desktop, shut down, restarted and all
was well.

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

Title:
  Video cuts out after 3 seconds

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

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

[Bug 1839767] Re: apparmor DENIED freshclam and clamd access to openssl.cnf

[hambling]

I can confirm that adding 
   /etc/ssl/openssl.cnf r,

to /etc/apparmor.d/usr.bin.freshclam and /etc/apparmor.d/usr.sbin.clamd

then run:
apparmor_parser -r /etc/apparmor.d/usr.bin.freshclam
apparmor_parser -r /etc/apparmor.d/usr.sbin.clamd

Makes the apparmor="DENIED" go away.
Also gets rid of the syslog warning -  kernel: [   11.240463] 
kauditd_printk_skb: 16 callbacks suppressed

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

Title:
  apparmor DENIED freshclam and clamd access to openssl.cnf

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

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

[Bug 1839771] [NEW] Install of 19.04 failed on Lenovo Thinkpad W520

[volleyer01]

Public bug reported:

Pls see log sent

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
Date: Sun Aug 11 09:12:52 2019
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd quiet splash ---
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu

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

Title:
  Install of 19.04 failed on Lenovo Thinkpad W520

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

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

[Bug 1839770] [NEW] NVMe. Crash during installation

[Nikolay V. Belyakov]

Public bug reported:

Crash after disks partitioning.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 11 19:12:52 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  NVMe. Crash during installation

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

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

[Bug 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*

[daniel CURTIS]

Hello.

Sorry for writing post by post, but there still are problems with
Mousepad and 'connecting to accessibility bus' during editing any file.
Here is an example:

,[ $ mousepad /usr/bin/example ]
| ** (mousepad:14099): WARNING **: Couldn't connect to accessibility bus: 
| Failed to connect to socket /tmp/dbus-Z3dGTATnQK: Connection refused
`

Note: the same WARNING message is displayed no matter if 'sudo(8)'
command is being used. (However, it seems it is not a rule - if I
remember correctly, there wasn't such a message earlier. I mean a couple
months ago etc. But I could be wrong.) If it's about release, Mousepad
and Xfce4 version informations, everything is the same as above - in my
previous post.

By the way: because there is not any reaction on this issue/bug, maybe
it should be reported once again, but this time, choosing different
'Affects'? What do you think?

Thanks.

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

Title:
  Mousepad show the warning Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus -*

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+subscriptions

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