from:"Jackson"

Public bug reported:

Install chrome stable version, start it and the window just flicker.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.8
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CrashReports:
 600:117:124:37:2022-04-02 17:38:51.386440684 -0700:2022-04-02 
17:38:51.386440684 -0700:/var/crash/_usr_bin_gnome-shell.1000.uploaded
 664:1000:124:0:2022-04-02 17:38:31.017534533 -0700:2022-04-02 
17:38:31.017534533 -0700:/var/crash/_usr_bin_gnome-shell.1000.upload
 640:1000:124:33478431:2022-04-02 17:38:19.075793266 -0700:2022-04-02 
17:38:20.075793266 -0700:/var/crash/_usr_bin_gnome-shell.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  2 19:32:46 2022
InstallationDate: Installed on 2022-04-02 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade jammy wayland-session

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

Title:
  chrome browser not displaying correctly on 22.04 beta

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


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

[Bug 1967634] [NEW] matplotlib python not working in beta 22.04

Public bug reported:

after upgrading to beta 22.04 matplot no longer display from a pythom3
program. A window opens but it just flickers.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  2 13:40:21 2022
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2022-04-02 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
Symptom: installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy ubiquity-22.04.10 wayland-session

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

Title:
  matplotlib python not working in beta 22.04

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


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

[Bug 1967633] [NEW] matplotlib python not working in beta 22.04

Public bug reported:

After upgrading to the 22.04 beta matplot does not display correctly
python3

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.8
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  2 13:37:57 2022
InstallationDate: Installed on 2022-04-02 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade jammy wayland-session

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

Title:
  matplotlib python not working in beta 22.04

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


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

[Bug 1967635] [NEW] matplotlib python not working in beta 22.04

Public bug reported:

Even the sample python code from matploy doesn't display in a window
correctly.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.8
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  2 13:42:16 2022
InstallationDate: Installed on 2022-04-02 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade jammy wayland-session

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

Title:
  matplotlib python not working in beta 22.04

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


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

[Bug 1964746] [NEW] ubiquity crash on launch

2022-03-13 Thread Jackson Doak

Public bug reported:

Ubiquity crashes before showing any screen on 22.04 LTS. This bug has
happened since at least 09/03/2022's ISO. Exact same error lanching the
installer from the Kubuntu live session

Lenovo P14s with nVidia graphics

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.7
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.467
CurrentDesktop: KDE
Date: Mon Mar 14 04:55:55 2022
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220312)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy kubuntu ubiquity-22.04.7

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

Title:
  ubiquity crash on launch

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


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

[Bug 1959448] [NEW] Ubuntu installation fatal error on grub-installer

2022-01-28 Thread Jackson Renato Faquineti Rampazzo

Public bug reported:

I tried several times to install Ubuntu on my PC, but it does a fatal
error on grub-installer, I tried to repair with grub-repair but it
couldn't fix it

System: Ubuntu 20.04.3 LTS (64 bit)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CasperVersion: 1.445.1
Date: Fri Jan 28 17:04:02 2022
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash acpi=off nomodeset ---
LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu

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

Title:
  Ubuntu installation fatal error on grub-installer

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


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

[Bug 1949502] [NEW] package grub-common 2.04-1ubuntu26.13 failed to install/upgrade: o subprocesso instalado, do pacote grub-common, o script post-installation retornou erro do status de saída 1

2021-11-02 Thread Denilson Jackson

Public bug reported:

o sistema acusou esse erro, estou apenas enviando eles a vocês, porém n
sei de que forma pode afetar meu sistema, mas quero garantir que eu não
tenha defeitos futuros.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-common 2.04-1ubuntu26.13
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Nov  2 14:30:00 2021
ErrorMessage: o subprocesso instalado, do pacote grub-common, o script 
post-installation retornou erro do status de saída 1
InstallationDate: Installed on 2021-07-09 (116 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=a10a38c0-4504-4e3b-a057-c1ff2d904f88 ro quiet splash
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: grub2
Title: package grub-common 2.04-1ubuntu26.13 failed to install/upgrade: o 
subprocesso instalado, do pacote grub-common, o script post-installation 
retornou erro do status de saída 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package grub-common 2.04-1ubuntu26.13 failed to install/upgrade: o
  subprocesso instalado, do pacote grub-common, o script post-
  installation retornou erro do status de saída 1

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


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

[Bug 1946667] Re: resolved reports Failed to send hostname reply: Invalid argument

2021-10-15 Thread Clay Jackson

Why is this marked invalid?

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

Title:
  resolved reports Failed to send hostname reply: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-identity-provider/+bug/1946667/+subscriptions


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

[Bug 1946667] [NEW] resolved reports Failed to send hostname reply: Invalid argument

2021-10-11 Thread Clay Jackson

Public bug reported:

According to https://github.com/systemd/systemd/issues/11626 this is
fixed in version 248 of systemd.

Please make that version available to LTS 20.04.3

Thanks!

** Affects: canonical-identity-provider
 Importance: Undecided
 Status: New

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

** Also affects: systemd (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/1946667

Title:
  resolved reports Failed to send hostname reply: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-identity-provider/+bug/1946667/+subscriptions


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

[Bug 1944381] [NEW] package wx3.0-i18n (not installed) failed to install/upgrade: trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/wxstd.mo', which is also in package wx3.1-i18n 3.1.3-1.bionic

2021-09-20 Thread Will Jackson

Public bug reported:

Trying to install Opencpn 5.2.4
Description:Ubuntu 20.04.3 LTS
Release:20.04

"Preparing to unpack .../3-wx3.0-i18n_3.0.4+dfsg-15build1_all.deb ...
Unpacking wx3.0-i18n (3.0.4+dfsg-15build1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-Ed0Xdp/3-wx3.0-i18n_3.0.4+dfsg-15build1_all.deb 
(--unpack):
 trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/wxstd.mo', which is also 
in package wx3.1-i18n 3.1.3-1.bionic
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package opencpn-data.
Errors were encountered while processing:
 /tmp/apt-dpkg-install-Ed0Xdp/3-wx3.0-i18n_3.0.4+dfsg-15build1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
"

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: wx3.0-i18n (not installed)
ProcVersionSignature: Ubuntu 5.4.0-84.94-lowlatency 5.4.133
Uname: Linux 5.4.0-84-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Sep 20 18:30:03 2021
ErrorMessage: trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/wxstd.mo', 
which is also in package wx3.1-i18n 3.1.3-1.bionic
InstallationDate: Installed on 2018-09-01 (1115 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: wxwidgets3.0
Title: package wx3.0-i18n (not installed) failed to install/upgrade: trying to 
overwrite '/usr/share/locale/ca/LC_MESSAGES/wxstd.mo', which is also in package 
wx3.1-i18n 3.1.3-1.bionic
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: wxwidgets3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package wx3.0-i18n (not installed) failed to install/upgrade: trying
  to overwrite '/usr/share/locale/ca/LC_MESSAGES/wxstd.mo', which is
  also in package wx3.1-i18n 3.1.3-1.bionic

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


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

[Bug 1940981] Re: Value in glitchpeg.desktop, "Comment", divided into two lines

2021-08-24 Thread Anders Jackson

The issue are also reported in Debian:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990007#5

/Jackson

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

** Description changed:

  The value of the key "Comment" in
  /usr/share/applications/screensavers/glitchpeg.desktop is divided into
- to lines, like this:
+ two lines, like this:
  
  Comment=Loads an image, corrupts it, and then displays the corrupted version,
  several times a second.  After a while, finds a new image to corrupt. Written 
by Jamie Zawinski; 2018.
  
  It should be one single line, without a line break after "version,", or
  there will be an error report when installing the desktop file.

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

Title:
  Value in glitchpeg.desktop, "Comment", divided into two lines

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


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

[Bug 1940981] [NEW] Value in glitchpeg.desktop, "Comment", divided into two lines

2021-08-24 Thread Anders Jackson

Public bug reported:

The value of the key "Comment" in
/usr/share/applications/screensavers/glitchpeg.desktop is divided into
to lines, like this:

Comment=Loads an image, corrupts it, and then displays the corrupted version,
several times a second.  After a while, finds a new image to corrupt. Written 
by Jamie Zawinski; 2018.

It should be one single line, without a line break after "version,", or
there will be an error report when installing the desktop file.

** Affects: xscreensaver (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/1940981

Title:
  Value in glitchpeg.desktop, "Comment", divided into two lines

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


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

Re: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

2021-07-21 Thread Keith Jackson

Excellent. I'll use the SSH option as I've got a working Ubuntu laptop
of that's more useful. Thanks for the info.

Get Outlook for Android

From: nore...@launchpad.net  on behalf of Daniel Dadap 
<1930...@bugs.launchpad.net>
Sent: Wednesday, July 21, 2021 10:01:06 PM
To: temporal-...@live.co.uk 
Subject: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when 
using DP, but not with HDMI

> should it fail how can I get the log when my system completely locks
up and dies?

My understanding of the bug is that it occurs when the NVIDIA driver
tries to bring up the DisplayPort link on certain DisplayPort monitors.
You should be able to drive the system in text mode with a failing
driver, to capture the log. One way to do that would be to add
"systemd.unit=multi-user.target" to the kernel command line. (When the
bootloader menu comes up, edit the boot options and add this argument to
the line that starts with 'linux'.) If you happen to have another system
on the same network you can even try SSHing into the system that
reproduces the problem, then start the graphical session manually with
`sudo systemctl isolate graphical`, and if the crash doesn't take down
the SSH session, you ought to be able to generate the log file while the
problem is occurring. (Log files taken while a bug is actively being
reproduced tend to be the most useful.) Depending on the exact nature of
the crash, you may even be able to SSH into a system which has already
crashed, without having to go to the effort of starting it in text mode
first.

> In that eventuality I've only been able to recover by booting an older
kernel with the older drivers. Will that not invalidate the log content
on restart?

It may, or may not. nvidia-bug-report.sh attempts to capture logs from
the previous boot, if they have been retained. If you do find that you
are unable to capture a log file using a driver version which reproduces
the problem, just make sure to note that you captured the log file after
rebooting to a known good driver.

--
You received this bug notification because you are subscribed to the bug
report.
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1930733data=04%7C01%7C%7Ccefaf8b686a044088e3d08d94c8c0036%7C84df9e7fe9f640afb435%7C1%7C0%7C637624986447380869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=eO8jfN5MbevXRAqp0irMe22IyOABsKE3YlvBENkoYH8%3Dreserved=0

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv022829rm+0xed/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv023065rm+0x30/0x60 [nvidia]
  Jun 03

Re: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

2021-07-21 Thread Keith Jackson

I'll be attempting an upgrade next week if the drivers are now in the
canonical repositories but, should it fail how can I get the log when my
system completely locks up and dies?

In that eventuality I've only been able to recover by booting an older
kernel with the older drivers. Will that not invalidate the log content
on restart?

If there's a way I can stop at a terminal and dump the files to a stick
before I restore can you provide instructions on how that can be done
then if all is in vain, then at least I can get you useful info.

I'm a fairly noobish user but happy to help as much as I can.

Get Outlook for Android


From: nore...@launchpad.net  on behalf of Daniel Dadap 
<1930...@bugs.launchpad.net>
Sent: Wednesday, July 21, 2021 5:56:48 PM
To: temporal-...@live.co.uk 
Subject: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when 
using DP, but not with HDMI

Hello, NVIDIA employee here.

Can those who are still experiencing problems please provide the
following information?

* NVIDIA driver version installed
* NVIDIA GPU model
* Exact model of affected monitor

An nvidia-bug-report.log will capture the driver version and GPU model,
along with some other useful information, though possibly not the
monitor model since the system may be crashing before the EDID can be
read. You can generate an nvidia-bug-report.log file by running `nvidia-
bug-report.sh` as root. This will create a new file named nvidia-bug-
report.log.gz in your current directory.

As for the fix being absent from the release notes, that was an
accidental omission. The fix should be present in 460.91.03 and later,
as well as all publicly released 470 drivers. Unfortunately, the fix did
not make it into 465 before support for the 465 series was discontinued.
We will want to collect the relevant information for anybody still
experiencing problems with DP monitors so that any remaining issues can
be addressed as well.

--
You received this bug notification because you are subscribed to the bug
report.
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1930733data=04%7C01%7C%7C50e47dc149644e6a68ec08d94c69c870%7C84df9e7fe9f640afb435%7C1%7C0%7C637624839480958737%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=489S6ZVdRRW7P6PbuM6zRIKofoHn5s%2FaL4oCti18y9s%3Dreserved=0

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv022829rm+0xed/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv023065rm+0x30/0x60 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv000704rm+0x16da/0x22b0 [nvidia]
  Jun 03 16:26:57 willow

Re: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

2021-07-14 Thread Keith Jackson

The server driver doesn't work for my setup. I could try the beta
package but at the moment it's working as it is, updates aside. I'm just
after an idea of timescale for a proper fix with 470, not in a mad rush.

I'm not inclined to experiment at the moment due to other priorities and
I can't afford to be without my PC for an extended period.

As long as we get a post on here keeping us up to date with when the
fixed packages are in the Ubuntu upgrade repositories that's good enough
for me. Then I can just unlock everything, upgrade, cross all my fingers
and hope all is well!

Get Outlook for Android


From: boun...@canonical.com  on behalf of S?nke Lorenzen 
<1930...@bugs.launchpad.net>
Sent: Wednesday, July 14, 2021 7:15:35 PM
To: temporal-...@live.co.uk 
Subject: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when 
using DP, but not with HDMI

You have to install another driver than nvidia-driver-460 in order to
update all your packages again. This is because nvidia-driver-460 does
have the version 460.80 in the repositories now.

Easiest is to change to nvidia-driver-460-server if that works for you,
next easiest is to enable the PPA I mentioned above to install the 470
beta driver.

--
You received this bug notification because you are subscribed to the bug
report.
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1930733data=04%7C01%7C%7Ca554b67baec7490041ec08d946f41882%7C84df9e7fe9f640afb435%7C1%7C0%7C637618836455319573%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=s3aOcRT0weNNtu723VwqY7uELxuEopJBSoxp14eX4zI%3Dreserved=0

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv022829rm+0xed/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv023065rm+0x30/0x60 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv000704rm+0x16da/0x22b0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? rm_init_adapter+0xc5/0xe0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nv_open_device+0x122/0x8e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_open+0x2b7/0x560 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_frontend_open+0x58/0xa0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? chrdev_open+0xf7/0x220
  Jun 03 16:26:57 willow kernel:  ? cdev_device_add+0x90/0x90
  Jun 03 16:26:57 willow kernel:  ? do_dentry_open+0x156/0x370
  Jun 03 16:26:57 willow kernel:  ? vfs_open+0x2d/0x30
  Jun 03 16:26:57 willow kernel:  ? do_open+0x1c3/0x340
  Jun 03 16:26:57 willow kernel:  ? path_openat+0x10a/0x1d0
  Jun 03 16:26:57 willow kernel:  ? do_filp_open+0x8c/0x130
  Jun 03 16:26:57 willow kernel:  ?

Re: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

2021-07-14 Thread Keith Jackson

It was only kernel related in that the update from .53 to .55 also
updated my NVidia drivers at the same time - I assume due to being a
dependency. I was unable to boot my PC in that kernel at all in order to
fix it or downgrade any driver packages so I've been locked on .53 ever
since effectively, with 460.73. I noticed today that a new kernel is out
(.58?) but if that also updates my graphics drivers then I'm still up
creek without a paddle.

Just after some info as to when I can safely unblock my updates and
upgrade safely again.

Get Outlook for Android

From: boun...@canonical.com  on behalf of S?nke Lorenzen 
<1930...@bugs.launchpad.net>
Sent: Wednesday, July 14, 2021 5:35:19 PM
To: temporal-...@live.co.uk 
Subject: [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when 
using DP, but not with HDMI

@Keith
This does not seem to be kernel related, when I upgraded to  460.80 and 465.27 
and got hit by this bug, I first tried to boot with older kernels I had 
installed with the same problem then. And look at 
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fforums.developer.nvidia.com%2Ft%2F465-24-02-page-fault%2F175782data=04%7C01%7C%7Cd40c289b7ac7494ecf2108d946e62a60%7C84df9e7fe9f640afb435%7C1%7C0%7C637618776640052404%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=yCd5zPkJLnn2aaO0LO7XjVtmZ8KQOYcDBhRRED9vdr0%3Dreserved=0
 there users have tried a lot of different kernels without it helping.

You can either install the nvidia-driver-460-server which is at
460.73.01, or install it manually if it gives other problems, see above.
Or use the 470 beta from
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flaunchpad.net%2F~albertomilone%2F%2Barchive%2Fubuntu%2Fnvidia-testingdata=04%7C01%7C%7Cd40c289b7ac7494ecf2108d946e62a60%7C84df9e7fe9f640afb435%7C1%7C0%7C637618776640052404%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=pVGDfRT2eLoO3SULG6sXT3n0hRVt5PU41mneHXzxUds%3Dreserved=0

And then just update all other packages including kernels.

--
You received this bug notification because you are subscribed to the bug
report.
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1930733data=04%7C01%7C%7Cd40c289b7ac7494ecf2108d946e62a60%7C84df9e7fe9f640afb435%7C1%7C0%7C637618776640062360%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=dSSz4TkfyQz2sCFnbas%2BmEd66JJXQoAFfJA4sj%2F9OXQ%3Dreserved=0

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvidia]
  Jun 03 16:26:57

[Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

2021-07-14 Thread Keith Jackson

Do we have an ETA for this? I've had to essentially block any system
upgrades on my desktop since this began after having to roll back a
kernel update that forced this bug on me.

I noticed a new kernel update has just been posted and doesn't seem to
have rolled out this issue yet again.

This isn't a minor annoyance, this is a complete system fail type bug.

This NVidia forum thread has been really useful here:
https://forums.developer.nvidia.com/t/465-24-

It's looking like the bug on NVidia's side seems to have been rectified
in 470.42 - Manjaro have put that to their stable branch, yet I'm not
seeing anything in Ubuntu even in pre-release beyond 460.84.

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

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1930733/+subscriptions


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

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2021-06-18 Thread Reuben Jackson

I moved back to using X11 instead of wayland and have not had the issue
since if this helps anyone else out.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

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

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2021-06-08 Thread Reuben Jackson

I too have been having this issue in Ubuntu 21.04, Gnome-shell 3.38.4.

My system has a touchpad and touchscreen, the closest i have gotten to
consistently re-create it is to use the touch screen to click on the
same launcher icon multiple times.


It is quite an annoying bug as i get it 4-5 time a session, it seems a little 
beyond a 'first bug' or id have taken a shot at looking into it.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

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

[Bug 1931295] Re: After kernel upgrade to 5.8.0.58 my system would no longer boot.

2021-06-08 Thread Keith Jackson

Apologies - It was 5.8.0.55 (Not 5.8.0.58) that's recently been
installed - sorry working from memory!

I can't seem to edit the title...

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

Title:
  After kernel upgrade to 5.8.0.58 my system would no longer boot.

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

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

[Bug 1931295] [NEW] After kernel upgrade to 5.8.0.58 my system would no longer boot.

2021-06-08 Thread Keith Jackson

Public bug reported:

I have generic Ubuntu kernels 5.8.0.53 and 5.8.0.58 on my system.

After starting up following the latest update my system would not boot.
Managed to get back in via Grub manually loading the earlier kernel.

I'm running a custom Quiet PC system with SSD primary drive and data
HDDs.

I'm a bit of a noob here but happy to track down any desired logs etc.
if possible.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun  8 19:11:19 2021
InstallationDate: Installed on 2021-04-23 (46 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
SourcePackage: linux-signed-hwe-5.8
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  After kernel upgrade to 5.8.0.58 my system would no longer boot.

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

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

[Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display

2021-06-02 Thread Eric Jackson

I believe I have the same behavior with different hardware, and no
docking station: I have a Dell Latitude 7480 which I typically use with
an external monitor (via HDMI), USB mouse, and USB keyboard, while the
laptop sits behind a desk with its lid closed.

Up until April 2021, I was running Ubuntu 16.04 on this machine with the
(standard for 16.04) Unity desktop, with the same physical configuration
--that is, while working at home, I kept the laptop itself closed behind
my desk, and used it via the external mouse, keyboard, and display.
Prior to upgrading, I was able to log in without any problems associated
with the lid being closed.

On April 22, 2021, since 16.04 would no longer be getting updates, I
finally upgraded through 18.04 to 20.04, still using the Unity desktop.
Now, from a cold start, I get the user log-in screen, and immediately
after entering my password, the system suspends. If I open the lid a few
centimeters, the system resumes without prompting for a password.

If my problem is really the same problem that @twetzel21 is seeing--and
in terms of the behavior he describes, it appears that it is--this
suggests to me that it's neither related to a dock, nor to anything with
Nvidia drivers (since I have only Intel integrated graphics and do not
have any Nvidia drivers installed), nor related to a hardware issue.
Although I use my laptop with an external screen, mouse, and keyboard,
they're not connected through any dock, but just using the normal ports
on the machine. Moreover, this behavior didn't happen for me with the
same hardware in 16.04, but began only when I moved through 18.04 to
20.04.

Moreover, when I upgraded to 20.04, I installed gnome-tweak-tool, and
under General I have "Suspend when laptop lid is closed" *un*checked.
Moreover, in the system settings > Power options, the dropdowns are set
to "Do nothing" when the laptop lid is closed, both on battery or on
outlet power.

I *do* have the Dropbox client installed and set to start up on login,
which I see was one issue that was raised as potentially related. I know
that, since my system doesn't represent a clean install of 20.04, it's
going to have a bit more cruft than normal, but I'm happy to make any
system information or syslog portions available.

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

Title:
Going to sleep instead of logging in while lid closed & external
display

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

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

[Bug 1926367] [NEW] Unable to update from 18.04 to 20.04

2021-04-27 Thread Mark Jackson

Public bug reported:

Trying to update an old 18.04 VM and it fails.

$ lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04

$ do-release-upgrade
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [1,554 B]  
   
Get:2 Upgrade tool [1,340 kB]   
   
Fetched 1,342 kB in 0s (0 B/s)  
   
authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg' 
extracting 'focal.tar.gz'
[sudo] password for mpfj: 

Reading cache

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://us.archive.ubuntu.com/ubuntu bionic InRelease
   
Hit http://security.ubuntu.com/ubuntu bionic-security InRelease 
   
Hit http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
   
Hit http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease  
   
Fetched 0 B in 0s (0 B/s)   
   
Reading package lists... Done
Building dependency tree  
Reading state information... Done

Checking for installed snaps

Calculating snap size requirements

Updating repository information
Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [109 kB]   
   
Hit http://us.archive.ubuntu.com/ubuntu focal InRelease 
   
Get:2 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [623 
kB]
Hit http://us.archive.ubuntu.com/ubuntu focal-updates InRelease 
   
Hit http://us.archive.ubuntu.com/ubuntu focal-backports InRelease   
   
Get:3 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages [220 
kB] 
Get:4 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 
[555 kB]
Get:5 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages 
[438 kB] 
Fetched 1,945 kB in 0s (0 B/s)  
   

Checking package manager
Reading package lists... Done
Building dependency tree  
Reading state information... Done

Calculating the changes

Calculating the changes

Could not determine the upgrade

An unresolvable problem occurred while calculating the upgrade.

If none of this applies, then please report this bug using the 
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If 
you want to investigate this yourself the log files in 
'/var/log/dist-upgrade' will contain details about the upgrade. 
Specifically, look at 'main.log' and 'apt.log'. 


Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree  
Reading state information... Done

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.44
ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18
Uname: Linux 4.15.0-142-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Apr 27 22:25:14 2021
InstallationDate: Installed on 2012-06-08 (3245 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-04-27 (0 days ago)
mtime.conffile..etc.update-manager.release-upgrades: 2021-04-27T20:27:01.492636

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


** Tags: amd64 apport-bug bionic dist-upgrade

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

Title:
  Unable to update from 18.04 to 20.04

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

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

[Bug 1782709] Re: Updating systemd kills network on bionic

2021-03-14 Thread Brandon Jackson

Having the exact same issue with ubuntu 20.04. Has anyone found a work
around for this rather annoying issue?

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

Title:
  Updating systemd kills network on bionic

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

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

[Bug 1913342] Re: zfs.8 man page snapshot listing instructions are confusing

2021-02-02 Thread Paul Jackson

Filed upstream, as you suggested:

https://github.com/openzfs/zfs/issues/11562

It's been a couple of years since I've pushed a pull request on github,
so I'll probably remain lazy and not get around to it in this case, to
avoid the extra time it would take me to recall just how to do it.  A
few minutes work for someone actively familiar with the process is
likely a couple hours work for a (relapsed back to) clueless git such as
myself.

Thanks for your spot on initial response to this here bug.  Keep up the
good zfs work.

** Bug watch added: github.com/openzfs/zfs/issues #11562
   https://github.com/openzfs/zfs/issues/11562

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

Title:
  zfs.8 man page snapshot listing instructions are confusing

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

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

[Bug 1913342] [NEW] zfs.8 man page snapshot listing instructions are confusing

2021-01-26 Thread Paul Jackson

Public bug reported:

The zfs.8 man page describes in 3 places how to include snapshots in
"zfs list":

1) Snapshots are displayed if the listsnaps property is on (the default is off).
2) Snapshots are displayed if the listsnaps property is on.  The default is 
off.  See zpool(8) for more information on pool properties.
3) For example, specifying -t snapshot displays only snapshots.

The first of these has twice now (I'm just learning zfs) sent me down a
rabbit hole, looking for a zfs dataset property "listsnaps".  There is
no such property (of datasets).

I'm on version 0.8.3 of zfsutils-linux that has this man page, but when
I look at https://zfsonlinux.org/manpages/0.8.6/man8/zfs.8.html it seems
that the above is still true in 0.8.6

Suggestion, to help us newbies reduce our learning time to list
snapshots:

Change both of the first 2 of the above 3 places in zfs.8 to:
"
"zfs list" displays snapshots only if either the "listsnapshots" property of 
the underlying zpool is on, or if the "zfs list -t snapshot" option is 
specified.

Extra Credit:

Just now it seems to me that the following command does _NOT_ list
snapshots, on a dataset that has some snapshots ... so the zfs.8
documentation that the "zfs list -t type" can be a "comma-separated list
of types to display" seems incorrect:

zfs list -t filesystem,snapshot myzfsdataset

Whether this "Extra Credit" discrepancy is a bug in the documentation,
or in the zfs command code, or newbie operator error, I'll leave as an
exercise to the reader .

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: zfsutils-linux 0.8.3-1ubuntu12.5
ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
Uname: Linux 5.4.0-64-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Jan 26 13:41:16 2021
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  zfs.8 man page snapshot listing instructions are confusing

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

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

[Bug 1906442] [NEW] Trying to install and it crashed

2020-12-01 Thread Alex Jackson

Public bug reported:

Trying to install and it crashed

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec  1 11:28:35 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
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 focal ubiquity-20.04.15.2 ubuntu

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

Title:
  Trying to install and it crashed

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

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

[Bug 1504642] Re: Muon Discover launches wrong app for KInfoCenter

Working in 20.10, can you please mark if you can still reproduce the bug
in any supported kubuntu?

** Changed in: muon (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/1504642

Title:
  Muon Discover launches wrong app for KInfoCenter

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

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

[Bug 1744554] Re: Muon search matches only beginning of package names

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

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

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

Title:
  Muon search matches only beginning of package names

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

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

[Bug 1412970] Re: package libmuon (not installed) failed to install/upgrade: trying to overwrite '/usr/share/locale/pt_BR/LC_MESSAGES/libmuon.mo', which is also in package libmuonprivate2 2.2.0-0ubunt

This was fixed in 2015


muon (4:5.1.95+git20150120-0ubuntu2) vivid; urgency=medium

  * Make libmuon replace and break libmuonprivate2, they clash on
the translation files.
 -- Harald SitterThu, 22 Jan 2015 09:22:23 +0100

** Changed in: muon (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  package libmuon (not installed) failed to install/upgrade: trying to
  overwrite '/usr/share/locale/pt_BR/LC_MESSAGES/libmuon.mo', which is
  also in package libmuonprivate2 2.2.0-0ubuntu7

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

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

[Bug 1716120] Re: Unable to sort package list in Muon by "Installed Size", "Installed Version", "Available Version" (as in Synaptic)

Fixed in upstream git, waiting on new release or someone to add the
patch to ubuntu

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

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

Title:
  Unable to sort package list in Muon by "Installed Size", "Installed
  Version", "Available Version" (as in Synaptic)

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

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

[Bug 1579585] Re: muon freezes when we enter wrong password

I cannot reproduce this in 20.10, can someone reproduce in any remaining
supported releases?

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

Title:
  muon freezes when we enter wrong password

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

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

[Bug 927216] Re: missing column for installed size (as in synaptic)

** Changed in: muon (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  missing column for installed size (as in synaptic)

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

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

[Bug 1540830] Re: After Plasma 5.5.3 - apt-check causes massive load / creates 100's of processes

I cant reproduce this on kubuntu 20.10 and all supported releases either
are from before the bug was introduced or well after it was fixed,
marking as fixed unless someone reproduces this on a current version

** Changed in: muon (Ubuntu)
   Status: Triaged => 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/1540830

Title:
  After Plasma 5.5.3 - apt-check causes massive load / creates 100's of
  processes

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

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

[Bug 1125452] Re: [Lenovo T530]: Volume Mute key LED is not responding correctly

2020-09-21 Thread Jackson Doak

This is working fine in Ubuntu 20.10

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1125452

Title:
  [Lenovo T530]: Volume Mute key LED is not responding correctly

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

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

[Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'

2020-09-21 Thread Jackson Doak

A crash has redirected me to this bug using today's xubuntu 20.10 image.
Attached is /var/log. This is on a Thinkpad T530 with nvidia graphics

** Attachment added: "20200922.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1871268/+attachment/5413076/+files/20200922.tar.gz

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

Title:
  Installation fails with Could not configure 'libc6:i386'. , E:Could
  not perform immediate configuration on 'libgcc-s1:i386'

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

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

[Bug 1887671] [NEW] package cairo-dock-plug-in-data (not installed) failed to install/upgrade: trying to overwrite '/usr/share/cairo-dock/plug-ins/shared-files/images/expose-desktops.svg', which is al

2020-07-15 Thread Mike Jackson

Public bug reported:

trying to upgrade from 17.04 to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: cairo-dock-plug-in-data (not installed)
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.10
Architecture: amd64
Date: Wed Jul 15 08:46:29 2020
DpkgTerminalLog:
 Preparing to unpack .../00-cairo-dock-plug-in-data_3.4.1-2build1_all.deb ...
 Unpacking cairo-dock-plug-in-data (3.4.1-2build1) ...
 [1mdpkg:[0m error processing archive 
/tmp/apt-dpkg-install-uCEojd/00-cairo-dock-plug-in-data_3.4.1-2build1_all.deb 
(--unpack):
  trying to overwrite 
'/usr/share/cairo-dock/plug-ins/shared-files/images/expose-desktops.svg', which 
is also in package cairo-dock-plug-ins-data 3.4.1-0ubuntu8
ErrorMessage: trying to overwrite 
'/usr/share/cairo-dock/plug-ins/shared-files/images/expose-desktops.svg', which 
is also in package cairo-dock-plug-ins-data 3.4.1-0ubuntu8
InstallationDate: Installed on 2015-04-06 (1927 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.4.6~17.04.1
SourcePackage: cairo-dock-plug-ins
Title: package cairo-dock-plug-in-data (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/cairo-dock/plug-ins/shared-files/images/expose-desktops.svg', which 
is also in package cairo-dock-plug-ins-data 3.4.1-0ubuntu8
UpgradeStatus: Upgraded to bionic on 2020-07-15 (0 days ago)

** Affects: cairo-dock-plug-ins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package cairo-dock-plug-in-data (not installed) failed to
  install/upgrade: trying to overwrite '/usr/share/cairo-dock/plug-ins
  /shared-files/images/expose-desktops.svg', which is also in package
  cairo-dock-plug-ins-data 3.4.1-0ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1887671/+subscriptions

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

[Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

2020-05-14 Thread John Jackson

Hi Aki and Linux Community, I was able to get the camera and Yes it does
produce the issue reported above with an ASMedia 3142. I have captured a
lecroy trace that I can share, I hope this helps someone.  You can
observe the enumeration and timing between packets, as well as see where
the flow control error occurs.

** Attachment added: "FlowControlErrorWithCamera.zip"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+attachment/5371545/+files/FlowControlErrorWithCamera.zip

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

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

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

[Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

2020-05-06 Thread John Jackson

Thanks Lior, and Aki. I fear the Razer core X chroma may require
extensive setup and a graphics card that I do not have handy or am
prepared to take on right now.  And I cannot get the IMX291 CMOS Camera
overnight. Aki, do you mind looking at the Camera and trying decipher
which device side usb controller or mcu is on the board, maybe I can
find something similar that I can get over night.

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

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

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

[Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

2020-05-06 Thread John Jackson

Hi Ubuntu Community,

I would like to find one of the COTS products that is reproducing this
issue. From reading the thread above it looks like it is a camera and a
usb ethernet adapter. Does anyone have more specifics or a product link
where I can purchase these. I currently havent seen the issue with a Usb
block device such as a JMicron nvme to usb device type c, but I will
continue testing.

Where can i find this camera?
Camera 1080p60 USB3 webcam
idVendor=15aa, idProduct=1555


Thanks,
John

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

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

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

[Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller

2020-05-01 Thread John Jackson

Hi Ubuntu and Linux Team, I have been observing the attached dmesg
output with several different ASMedia 3142 Cards whilst doing usb bulk
transfers using the linux read and write api's to a usb device. This
tends to break the software invoking said API's.  I am using Ubuntu
server 18.04.3 with kernel 4.15.0-55-generic. I see this issue with both
Intel and AMD based computers.

Has there been an update or patch or change in priory that might resolve
this bug?

[155247.078810] xhci_hcd :07:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_in
dex 2 comp_code 1
[155247.083037] xhci_hcd :07:00.0: Looking for event-dma 000892c11000 
trb-start 000892c0
8fe0 trb-end 000892c08fe0 seg-start 000892c08000 seg-end 
000892c08ff0
[155247.091767] xhci_hcd :07:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_in
dex 2 comp_code 1
[155247.096313] xhci_hcd :07:00.0: Looking for event-dma 000892c11010 
trb-start 000892c0
8fe0 trb-end 000892c08fe0 seg-start 000892c08000 seg-end 
000892c08ff0
[155247.106027] xhci_hcd :07:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_in
dex 2 comp_code 1
[155247.110869] xhci_hcd :07:00.0: Looking for event-dma 000890436000 
trb-start 000893b7
3fe0 trb-end 000893b73fe0 seg-start 000893b73000 seg-end 
000893b73ff0
[155247.120830] xhci_hcd :07:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_in
dex 2 comp_code 1
[155247.125985] xhci_hcd :07:00.0: Looking for event-dma 000890436010 
trb-start 000893b7
3fe0 trb-end 000893b73fe0 seg-start 000893b73000 seg-end 
000893b73ff0

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

Title:
  xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1
  Controller

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

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

[Bug 1862879] [NEW] Is there any way to turn on Notification when battery is charged Full?

2020-02-11 Thread jackson

Public bug reported:

for all laptop users when the laptop is changed like 100% then a pop up
is needed to ensure that the battery had been charged completely which
actually can increase the battery life

** Affects: 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/1862879

Title:
  Is there any way to turn on Notification when battery is charged Full?

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

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

[Bug 1859521] [NEW] BUG: Bad page map in process ThreadPoolForeg pte:00000018 pmd:29337e067

2020-01-13 Thread MARCUS T JACKSON

Public bug reported:

showed up after using ubuntustudio package installer.

ProblemType: KernelOops
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-9-lowlatency 5.4.0-9.12
ProcVersionSignature: Ubuntu 5.4.0-9.12-lowlatency 5.4.3
Uname: Linux 5.4.0-9-lowlatency x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vizionary357   2570 F pulseaudio
 /dev/snd/controlC0:  vizionary357   2570 F pulseaudio
Date: Mon Jan 13 13:08:36 2020
Failure: oops
MachineType: LENOVO 81SS
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-lowlatency 
root=UUID=d48b9241-4b03-4652-b3de-9c81a2c11c7c ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: BUG: Bad page map in process ThreadPoolForeg  pte:0018 pmd:29337e067
UpgradeStatus: Upgraded to focal on 2020-01-12 (1 days ago)
dmi.bios.date: 09/16/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: AGCN24WW(V1.07)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad FLEX-14API
dmi.modalias: 
dmi:bvnLENOVO:bvrAGCN24WW(V1.07):bd09/16/2019:svnLENOVO:pn81SS:pvrLenovoIdeaPadFLEX-14API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadFLEX-14API:
dmi.product.family: IdeaPad FLEX-14API
dmi.product.name: 81SS
dmi.product.sku: LENOVO_MT_81SS_BU_idea_FM_IdeaPad FLEX-14API
dmi.product.version: Lenovo IdeaPad FLEX-14API
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-kerneloops focal kernel-oops

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

Title:
  BUG: Bad page map in process ThreadPoolForeg  pte:0018
  pmd:29337e067

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

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

[Bug 1844844] [NEW] Disco Dingo 19.04 crash upon installing

2019-09-20 Thread Jude Jackson

Public bug reported:

"Disco Dingo" 19.04 failed to install while upgrading

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-release-upgrader-core 1:18.10.11.5
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CrashDB: ubuntu
Date: Fri Sep 20 20:00:17 2019
InstallationDate: Installed on 2017-12-20 (639 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to cosmic on 2019-09-21 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2019-09-20 19:56:53.483033
 Log time: 2019-09-20 19:57:59.023806
 Log time: 2019-09-20 20:00:03.133957
 Log time: 2019-09-20 20:00:19.302107
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug cosmic dist-upgrade

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

Title:
  Disco Dingo 19.04 crash upon installing

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

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

[Bug 1844845] [NEW] Disco Dingo 19.04 crash upon installing

2019-09-20 Thread Jude Jackson

Public bug reported:

"Disco Dingo" 19.04 failed to install while upgrading

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-release-upgrader-core 1:18.10.11.5
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CrashDB: ubuntu
Date: Fri Sep 20 20:00:17 2019
InstallationDate: Installed on 2017-12-20 (639 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to cosmic on 2019-09-21 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2019-09-20 19:56:53.483033
 Log time: 2019-09-20 19:57:59.023806
 Log time: 2019-09-20 20:00:03.133957
 Log time: 2019-09-20 20:00:19.302107
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug cosmic dist-upgrade

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

Title:
  Disco Dingo 19.04 crash upon installing

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

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

[Bug 1830705] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all

2019-05-28 Thread Jack Jackson

Public bug reported:

I have dual-booted Ubuntu and Windows and I don't have sound at all.
Before when restart laptop sound back shortly but if I boot it again
there is no sound anymore. Interesting, when type alsamixer I get cannot
open mixer: No such file or directory. I'm noticing that I have
installed driver. Sound sometimes works sometimes not

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
Uname: Linux 4.4.0-146-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lukab  1862 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 28 11:35:56 2019
InstallationDate: Installed on 2019-05-09 (18 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lukab  1862 F pulseaudio
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
UpgradeStatus: Upgraded to xenial on 2019-05-09 (18 days ago)
dmi.bios.date: 09/08/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.17
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81EE
dmi.board.vendor: HP
dmi.board.version: 62.29
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.17:bd09/08/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EE:rvr62.29:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-20T21:39:20.719208

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

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

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

[Bug 1245473]

2019-05-22 Thread Olivia-jackson

An extensive yet tactical take on your Career Episodes can help represent 
everything that makes you an asset to the Engineers Australia. Career Episodes 
can open those closed doors comfortably. They demonstrate the key skills, the 
experience, and the expertise you bring along in your engineering domain. Every 
one of the three episodes is required to touch base on unique projects and 
experiences, and your role, and strategies. At CDRReport, we have that 
expertise to make your Career Episodes sound valid and convincing.
https://www.cdrreport.org/cpd-examples-samples/
https://www.cdrreport.org/how-to-create-a-perfect-resume-for-engineers-australia/

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

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

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

[Bug 1683383]

2019-05-22 Thread Olivia-jackson

An extensive yet tactical take on your Career Episodes can help represent 
everything that makes you an asset to the Engineers Australia. Career Episodes 
can open those closed doors comfortably. They demonstrate the key skills, the 
experience, and the expertise you bring along in your engineering domain. Every 
one of the three episodes is required to touch base on unique projects and 
experiences, and your role, and strategies. At CDRReport, we have that 
expertise to make your Career Episodes sound valid and convincing.
https://www.cdrreport.org/cpd-examples-samples/
https://www.cdrreport.org/how-to-create-a-perfect-resume-for-engineers-australia/

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts (reopen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions

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

[Bug 36812]

2019-05-22 Thread Olivia-jackson

An extensive yet tactical take on your Career Episodes can help represent 
everything that makes you an asset to the Engineers Australia. Career Episodes 
can open those closed doors comfortably. They demonstrate the key skills, the 
experience, and the expertise you bring along in your engineering domain. Every 
one of the three episodes is required to touch base on unique projects and 
experiences, and your role, and strategies. At CDRReport, we have that 
expertise to make your Career Episodes sound valid and convincing.
https://www.cdrreport.org/cpd-examples-samples/
https://www.cdrreport.org/how-to-create-a-perfect-resume-for-engineers-australia/

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions

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

[Bug 1820821] [NEW] Buy Adderall online with norx

2019-03-19 Thread amma jackson

Public bug reported:

Click here : http://mexicanpharmacyonline.org/product-category/buy-
adderall-online/

Adderall is a drug mainly prescribed to tackle ADHD (Attention Deficit 
Hyperactivity Disorder) and narcolepsy. Usually, the symptoms of ADHD are 
present all the time, but they are only important when a person is involved in 
doing something important. The important things could be the things a person 
usually does like learning/studying, engaging in complex tasks, or doing a job 
that requires a lot of focus and dedication. That’s why it is suggested before 
ordering Adderall online that the drug should be taken only when the person is 
involved in doing some activity. Therefore, it is advisable that a prescribed 
dose of the drug should be taken while following the prescription provided to 
you and only when you’re busy in doing some work.
buy adderall onlline
adderall online in USA
Order adderall online
adderall overnight
adderall 30mg online
adderall online in miami
buy adderall online cheap

** Affects: 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/1820821

Title:
  Buy Adderall online with norx

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

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

[Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

2018-12-19 Thread craig jackson

Kernel version 4.19.10 has the fix.

To install run:

ukuu --install  v4.19.10

And reboot.

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

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

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

[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

2018-12-19 Thread craig jackson

I can confirm the following fixed the no-sound issue on my UX533 per
buchovagabond's post above:

sudo ukuu --install  v4.19.10

Cheers,
Craig

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

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

[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Don't forget to 'sudo apt update' after making those changes.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

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

[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Just uncomment the deb-src lines in /etc/apt/sources.list.

For example, replace:

# deb-src http://au.archive.ubuntu.com/ubuntu/ cosmic main
restricted

With:

deb-src http://au.archive.ubuntu.com/ubuntu/ cosmic main restricted

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

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

[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

The above worked for (k)ubuntu 18.10.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

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

[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

For those following https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel, I
had to do some extra things to get kernel compilation working.

The workaround steps are described here:
https://askubuntu.com/questions/1085411/unable-to-follow-kernel-
buildyourownkernel/1099988. Substitute the kernel version relevant to
you wherever you see "4.18.0"...

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

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

[Bug 1807365] [NEW] Amd 7300 apu bad graphics 18.04

2018-12-07 Thread MR S T JACKSON

Public bug reported:

Bad graphics on start up on 18.04 just before desktop weird colors  did not 
happen on 16.04 because
of proprietary driver from Amd in use  18.04 can only use opensource driver  
plus can this be looked
at been around 8 months now  no fix 
inxi -G out put
Graphics:
Device-1: AMD Kaveri [Radeon R6 Graphics] driver: radeon v: kernel
Display: x11 server: X.Org 1.19.6 driver: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz
OpenGL: renderer: AMD KAVERI (DRM 2.50.0 / 4.15.0-20-generic LLVM 6.0.0)
v: 4.5 Mesa 18.0.5

** Affects: gstreamer-vaapi (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Bad graphics on start up on 18.04 just befor desktop weird colors  did  
happen on 16.04 because
  of proprietary from Amd in use  18.04 can only use opensource driver  plus 
can this be looked
  at been around 8 months now  no fix if below
- inxi -G out put 
+ inxi -G out put
  Graphics:
  Device-1: AMD Kaveri [Radeon R6 Graphics] driver: radeon v: kernel
  Display: x11 server: X.Org 1.19.6 driver: ati,radeon
  unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz
  OpenGL: renderer: AMD KAVERI (DRM 2.50.0 / 4.15.0-20-generic LLVM 6.0.0)
  v: 4.5 Mesa 18.0.5

** Description changed:

- Bad graphics on start up on 18.04 just befor desktop weird colors  did  
happen on 16.04 because
- of proprietary from Amd in use  18.04 can only use opensource driver  plus 
can this be looked
- at been around 8 months now  no fix if below
+ Bad graphics on start up on 18.04 just before desktop weird colors  did not 
happen on 16.04 because
+ of proprietary driver from Amd in use  18.04 can only use opensource driver  
plus can this be looked
+ at been around 8 months now  no fix 
  inxi -G out put
  Graphics:
  Device-1: AMD Kaveri [Radeon R6 Graphics] driver: radeon v: kernel
  Display: x11 server: X.Org 1.19.6 driver: ati,radeon
  unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz
  OpenGL: renderer: AMD KAVERI (DRM 2.50.0 / 4.15.0-20-generic LLVM 6.0.0)
  v: 4.5 Mesa 18.0.5

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

Title:
  Amd 7300 apu bad graphics 18.04

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

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

[Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

2018-11-23 Thread craig jackson

Re above comment, the UX533 also has the ALC294. I should have made this
clear in that comment.

Thanks,
Craig

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

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

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

[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Hi Pawel,

You may be right, but I think the common thread in all the laptops
exhibiting this problem is the ALC294. Does the power save trick
mentioned in my comment work for you at all?

Cheers,
Craig

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

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

[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1742852

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

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

[Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1784485, as I'm seeing the same symptoms, with the same
temporary improvement enabling the power save as described above.

Asus UX533 Kubuntu 18.10 (4.18.0-11-generic) fresh install (dual boot
with Windows 10).

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

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

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

[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all