[Bug 2063470] [NEW] 6.8.0-1004-raspi "The futex facility returned an unexpected error code."

[Luke-Jr]

Public bug reported:

Upgrading my Raspberry Pi 5 to 6.8.0-1004-raspi broke the CI that runs
on it.

https://cirrus-ci.com/task/6254679959535616

All the attempts were after upgrading, except the very last re-run that
succeeded after downgrading to 6.8.0-1001-raspi.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-1004-raspi 6.8.0-1004.4
ProcVersionSignature: Ubuntu 6.8.0-1001.1-raspi 6.8.0-rc4
Uname: Linux 6.8.0-1001-raspi aarch64
ApportVersion: 2.28.1-0ubuntu2
Architecture: arm64
CasperMD5CheckResult: unknown
CloudArchitecture: aarch64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Apr 25 18:54:42 2024
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: linux-raspi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 noble

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

Title:
  6.8.0-1004-raspi "The futex facility returned an unexpected error
  code."

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


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

[Bug 2058255] [NEW] GNU Image Manipulation Program version 2.10.36

[Jack Pogorelsky Jr.]

Public bug reported:




```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-7ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-p2aSDx/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-p2aSDx/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu 
--with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-7ubuntu1) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.106)
using GEGL version 0.4.48 (compiled against version 0.4.44)
using GLib version 2.79.2 (compiled against version 2.78.1)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.51.0 (compiled against version 1.51.0)
using Fontconfig version 2.15.0 (compiled against version 2.14.2)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Falha de segmentação

Stack trace:
```

# Stack traces obtained from PID 10414 - Thread 10414 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 10871]
[New LWP 10467]
[New LWP 10421]
[New LWP 10420]
[New LWP 10419]
[New LWP 10418]
[New LWP 10417]
[New LWP 10416]
[New LWP 10415]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
unlink_chunk (p=0x5dfa3e591980, av=) at ./malloc/malloc.c:1619
  Id   Target Id  Frame 
* 1Thread 0x7621634a33c0 (LWP 10414) "gimp-2.10"  unlink_chunk 
(p=0x5dfa3e591980, av=) at ./malloc/malloc.c:1619
  2Thread 0x762147e006c0 (LWP 10871) "pool-gimp-2.10" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7621466006c0 (LWP 10467) "swap writer"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7621514006c0 (LWP 10421) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x76215b4006c0 (LWP 10420) "gdbus"  0x762163f1b4bd in 
__GI___poll (fds=0x76213c000b90, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x76215be006c0 (LWP 10419) "gmain"  0x762163f1b4bd in 
__GI___poll (fds=0x5dfa39d3ac30, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7621616006c0 (LWP 10418) "pool-spawner"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7621596006c0 (LWP 10417) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7621620006c0 (LWP 10416) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x762162a006c0 (LWP 10415) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 10 (Thread 0x762162a006c0 (LWP 10415) "worker"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7621641c741d in g_cond_wait () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x762164709083 in ?? () from /lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3  0x76216419cc92 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x762163e9ca94 in 

[Bug 1967165] Re: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Weymeth Eugene Hatley Jr]

In my case the error message was "could not write compressed host" /boot
partition as per installed default may be a bit small-ish. Tried running
update-upgrade command again, same result. ran "sudo apt autoremove
--purge" to remove old kernels; update-upgrade worked fine after that.

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

Title:
  package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

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


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

[Bug 1967165] Re: package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Weymeth Eugene Hatley Jr]

In my case the error message was "could not write compressed host" /boot
partition as per installed default may be a bit small-ish. Tried running
update-upgrade command again, same result. ran "sudo apt autoremove
--purge" to remove old kernels; update-upgrade worked fine after that.

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

Title:
  package linux-image-5.13.0-39-generic 5.13.0-39.44~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

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


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

[Bug 1961517] [NEW] package base-files 11ubuntu5.5 failed to install/upgrade: end of file on stdin at conffile prompt

[Kenneth Boyd Jr.]

Public bug reported:

package base-files 11ubuntu5.5 failed to install/upgrade: end of file on
stdin at conffile prompt

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: base-files 11ubuntu5.5
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
AptOrdering:
 base-files:amd64: Install
 base-files:amd64: Configure
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Feb 20 01:05:04 2022
ErrorMessage: end of file on stdin at conffile prompt
InstallationDate: Installed on 2022-02-05 (14 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: base-files
Title: package base-files 11ubuntu5.5 failed to install/upgrade: end of file on 
stdin at conffile prompt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.issue:
 I've read & consent to terms in IS user agreem't. \n
 
 Ubuntu 20.04.3 LTS \n \l
mtime.conffile..etc.issue: 2022-02-18T21:37:57.039602

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  package base-files 11ubuntu5.5 failed to install/upgrade: end of file
  on stdin at conffile prompt

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


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

[Bug 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8

[Javier Diaz Jr]

Note that this is for the latest focal debian-installer. Since there is
no hwe-netboot image the current focal installer is affected. I think an
hwe-netboot image for focal would resolve this issue for the installer.

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

Title:
  Mellanox NIC interface names change between 5.4 and 5.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/debian-installer/+bug/1940860/+subscriptions


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

[Bug 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8

[Javier Diaz Jr]

** Also affects: linux
   Importance: Undecided
   Status: New

** Project changed: linux => debian-installer

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

Title:
  Mellanox NIC interface names change between 5.4 and 5.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/debian-installer/+bug/1940860/+subscriptions


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

[Bug 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8

[Javier Diaz Jr]

This also affects the ubuntu-installer when the `d-i base-
installer/kernel/override-image  string linux-generic-hwe-20.04`
flag is added to preseed. The installer loads 5.4 kernel and configure
NICs using the 5.4 naming convention, then once the 5.11 kernel is
loaded and the host reboots the network config fails.

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

Title:
  Mellanox NIC interface names change between 5.4 and 5.8

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


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

[Bug 1948732] Re: I cant use the touch pat in my laptop tried it all, ideapad 3 14iil05 / LNVNB161216 lenovo,

[Tomas M Elicanal Jr]

Tried to search for the touchpad, i cant find it and i tried to check if
i could install the synaptics

///not letting me

sudo apt install synaptics
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package synaptics
 
I am using Ubuntu 20.04.3 LTS

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

Title:
  I cant use the touch pat in my laptop tried it all, ideapad 3 14iil05
  / LNVNB161216 lenovo,

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


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

[Bug 1948732] [NEW] I cant use the touch pat in my laptop tried it all, ideapad 3 14iil05 / LNVNB161216 lenovo,

[Tomas M Elicanal Jr]

Public bug reported:

Note: I can only use my laptop because i have a wired keyboard and mouse
which is a Lenovo 300 USB Combo Keyboard

Laptop: ideapad 3 14iil05 / LNVNB161216 lenovo,

Note: This is what i was able to get from my laptop

xinput list

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ PixArt Lenovo USB Optical Mouse   id=9[slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ LiteOn Lenovo Essential Wired Combo   id=10   [slave  keyboard (3)]
↳ LiteOn Lenovo Essential Wired Combo System Controlid=11   [slave  
keyboard (3)]
↳ Integrated Camera: Integrated C   id=13   [slave  keyboard (3)]
↳ Ideapad extra buttons id=14   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=15   [slave  keyboard (3)]
↳ LiteOn Lenovo Essential Wired Combo Consumer Control  id=12   [slave  
keyboard (3)]


cat /proc/bus/input/devices

I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=17ef Product=608d Version=0111
N: Name="PixArt Lenovo USB Optical Mouse"
P: Phys=usb-:00:14.0-1/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:17EF:608D.0001/input/input4
U: Uniq=
H: Handlers=mouse0 event4 
B: PROP=0
B: EV=17
B: KEY=7 0 0 0 0
B: REL=903
B: MSC=10

I: Bus=0003 Vendor=17ef Product=60a1 Version=0111
N: Name="LiteOn Lenovo Essential Wired Combo"
P: Phys=usb-:00:14.0-2/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:17EF:60A1.0002/input/input5
U: Uniq=
H: Handlers=sysrq kbd event5 leds 
B: PROP=0
B: EV=120013
B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=17ef Product=60a1 Version=0111
N: Name="LiteOn Lenovo Essential Wired Combo System Control"
P: Phys=usb-:00:14.0-2/input1
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1/0003:17EF:60A1.0003/input/input6
U: Uniq=
H: Handlers=kbd event6 
B: PROP=0
B: EV=13
B: KEY=c000 10 0
B: MSC=10

I: Bus=0003 Vendor=17ef Product=60a1 Version=0111
N: Name="LiteOn Lenovo Essential Wired Combo Consumer Control"
P: Phys=usb-:00:14.0-2/input1
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.1/0003:17EF:60A1.0003/input/input7
U: Uniq=
H: Handlers=kbd event7 js0 
B: PROP=0
B: EV=13
B: KEY=710001 0 7800011000 e 0
B: MSC=10

I: Bus=0019 Vendor= Product= Version=
N: Name="Ideapad extra buttons"
P: Phys=ideapad/input0
S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input8
U: Uniq=
H: Handlers=rfkill kbd event8 
B: PROP=0
B: EV=13
B: KEY=81000800100c03 4430 0 2
B: MSC=10

I: Bus=0003 Vendor=5986 Product=1135 Version=5408
N: Name="Integrated Camera: Integrated C"
P: Phys=usb-:00:14.0-5/button
S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input9
U: Uniq=
H: Handlers=kbd event9 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus=0019 Vendor= Product=0006 Version=
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10
U: Uniq=
H: Handlers=kbd event10 
B: PROP=0
B: EV=3
B: KEY=3e000b 0 0 0

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
U: Uniq=
H: Handlers=event11 
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: 

[Bug 1948619] ZSYSJournal.txt

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "ZSYSJournal.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535739/+files/ZSYSJournal.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] ZFSPoolsStatus.txt

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "ZFSPoolsStatus.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535738/+files/ZFSPoolsStatus.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] ZFSPoolCache.gz

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "ZFSPoolCache.gz"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535737/+files/ZFSPoolCache.gz

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] ZFSMounts.txt

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "ZFSMounts.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535736/+files/ZFSMounts.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] ZFSModules.txt

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "ZFSModules.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535735/+files/ZFSModules.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] ZFSListcache-rpool.txt

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "ZFSListcache-rpool.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535734/+files/ZFSListcache-rpool.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] SystemdFailedUnits.txt

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "SystemdFailedUnits.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535732/+files/SystemdFailedUnits.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] ProcCpuinfoMinimal.txt

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535730/+files/ProcCpuinfoMinimal.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] ZFSDatasets.txt

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "ZFSDatasets.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535733/+files/ZFSDatasets.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] SystemdDefaultUnitsState.txt

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "SystemdDefaultUnitsState.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535731/+files/SystemdDefaultUnitsState.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] MountsGenerated.txt

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "MountsGenerated.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535729/+files/MountsGenerated.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] Grub.cfg.txt

[Robert A. Schaefer Jr.]

apport information

** Attachment added: "Grub.cfg.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535728/+files/Grub.cfg.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] Re: Failed to start zsys daemon service

[Robert A. Schaefer Jr.]

apport information

** Tags added: apport-collected impish

** Description changed:

  Frequently when running apt upgrade as well as other times the system
  seems to hang.  Afterwards with either a message is printed to the
  screen or an entry is made in the log statusing that zsysd.service timed
  out and Failed to start ZSYS daemon service.
  
  This started I think back in September on 21.04.  It has continued now
  that I've upgraded to 21.10.
  
  lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10
  
  
  apt-cache policy zsys
  zsys:
Installed: 0.5.8
Candidate: 0.5.8
Version table:
   *** 0.5.8 500
  500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages
  100 /var/lib/dpkg/status
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu70
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2021-01-11 (286 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ Mounts: Error: [Errno 40] Too many levels of symbolic links: '/proc/mounts'
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
+ Package: zsys 0.5.8
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pbfhvd@/vmlinuz-5.13.0-20-generic 
root=ZFS=rpool/ROOT/ubuntu_pbfhvd ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
+ RelatedPackageVersions:
+  zfs-initramfs  2.0.6-1ubuntu2
+  zfsutils-linux 2.0.6-1ubuntu2
+ Tags:  impish
+ Uname: Linux 5.13.0-20-generic x86_64
+ UpgradeStatus: Upgraded to impish on 2021-10-19 (5 days ago)
+ UserGroups: docker sudo
+ ZFSImportedPools:
+  NAMESIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHEALTH 
 ALTROOT
+  bpool  1.88G  1.05G   841M- -21%56%  1.00xONLINE 
 -
+  rpool   920G   356G   564G- -34%38%  1.00xONLINE 
 -
+ ZFSListcache-bpool:
+  bpool/boot   off on  on  off on  off on  
off -   none-   -   -   -   -   -   -   
-
+  bpool/BOOT   noneoff on  on  off on  off on  
off -   none-   -   -   -   -   -   -   
-
+  bpool/BOOT/ubuntu_pbfhvd /boot   on  on  on  off on  
off on  off -   none-   -   -   -   -   
-   -   -
+ ZSYSDump: Error: command ['zsysctl', 'service', 'dump'] failed with exit code 
1: level=error msg="couldn't connect to zsys daemon: timed out waiting for 
server handshake"
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1948619/+attachment/5535727/+files/Dependencies.txt

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

Title:
  Failed to start zsys daemon service

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


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

[Bug 1948619] [NEW] Failed to start zsys daemon service

[Robert A. Schaefer Jr.]

Public bug reported:

Frequently when running apt upgrade as well as other times the system
seems to hang.  Afterwards with either a message is printed to the
screen or an entry is made in the log statusing that zsysd.service timed
out and Failed to start ZSYS daemon service.

This started I think back in September on 21.04.  It has continued now
that I've upgraded to 21.10.

lsb_release -rd
Description:Ubuntu 21.10
Release:21.10


apt-cache policy zsys
zsys:
  Installed: 0.5.8
  Candidate: 0.5.8
  Version table:
 *** 0.5.8 500
500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status

** Affects: zsys (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/1948619

Title:
  Failed to start zsys daemon service

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


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

[Bug 1937296] Re: Kernel Hang During "Loading initial ramdisk..."

[Boyd Stephen Smith Jr.]

On a personal note, I'm unable to be productive at work because I can no
longer find a kernel that will boot with networking in a non-line
environment.  Never had this happen with the Debian installation I have
on System76 (but not-Serval) hardware I have at home.

5.11.0-7620-generic never booted.

5.11.0-7633-generic never booted.

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

Title:
  Kernel Hang During "Loading initial ramdisk..."

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


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

[Bug 1937296] Re: Kernel Hang During "Loading initial ramdisk..."

[Boyd Stephen Smith Jr.]

5.11.0-7614-generic was updated last week, and no longer boots.

5.13.0-7614-generic had never booted.

5.8.0-43-generic boots, but comes up without audio devices or network
devices (neither wired nor wireless).  This is particularly weird since
the Ubuntu Live environment I'm writing this update from is using
5.8.0-43, and has both audio and networking working fine.

5.4.0-84-generic boots, but comes up without audio devices or network
devices.

I still need to try 5.4.0-26, but I'm not hopeful.

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

Title:
  Kernel Hang During "Loading initial ramdisk..."

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


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

[Bug 1937296] Re: Kernel Hang During "Loading initial ramdisk..."

[Boyd Stephen Smith Jr.]

I was wanting to assign to https://launchpad.net/~system76 but I
couldn't figure out how to do that.  Says I can only assign to myself
when I try. :(

** Also affects: system76
   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/1937296

Title:
  Kernel Hang During "Loading initial ramdisk..."

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


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

[Bug 1937296] [NEW] Kernel Hang During "Loading initial ramdisk..."

[Boyd Stephen Smith Jr.]

Public bug reported:

This is specific to the System 76 PPA.

linux-image-5.11.0-7614-generic boots with no problems.

```
% uname -a
Linux system76-pc 5.11.0-7614-generic #15~1622578982~20.04~383c0a9~dev-Ubuntu 
SMP Wed Jun 2 00:50:47 U x86_64 x86_64 x86_64 GNU/Linux
```

linux-image-5.11.0-7620-generic hangs at "Loading initial ramdisk...".
This is true in recovery mode as well.

/etc/os-release:
```
NAME="Ubuntu"
VERSION="20.04.2 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.2 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
```

Hardware is Serval:
```
System Information
Manufacturer: System76
Product Name: Serval
Version: serw11-b
UUID: 6c5bfa80-9b7c---
Wake-up Type: Power Switch
```

All packages / firmware is up-to-date, and EFI was updated a couple of
months ago.

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


** Tags: system76

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

Title:
  Kernel Hang During "Loading initial ramdisk..."

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


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

[Bug 1875459] Re: System hangs when loading google maps on chrome with navi AMD GPU

[Mike Gleason jr Couturier]

Same thing here. Radeon 5700 XT, Ubuntu 20.04, Chromium 91.0.4449.6,
Google Maps freezes.

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

Title:
  System hangs when loading google maps on chrome with navi AMD GPU

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

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

[Bug 1915566] [NEW] package linux-image-4.4.0-174-generic 4.4.0-174.204 failed to install/upgrade: package linux-image-4.4.0-174-generic is not ready for configuration cannot configure (current status

[Robert N Hubby Jr]

Public bug reported:

I think that ever since the HDMI audio driver failed; my system has been
unable to update properly. I think that If it is possible to either re-
install the HDMI audio driver or both the HDMI audio driver and the HDMI
video driver, the Turks version for the AMD Radeon HD 6570 to correct
the problem. This is because AMD does not give support for Ubuntu 16.04.
They give support for Ubuntu 14.04 and lower. In other words, there are
not any proprietary AMD HDMI drivers to correct the problems and
therefore the end result is that the system does not update properly and
there are many errors related directly to this problem. Often I get
system error messages because of these faulty drivers which create this
insane endless loop of code which prevent me from properly updating my
programs. The generic Ubuntu HDMI drivers are clearly failing on the
Turks version of the AMD Radeon HD 6570. There is not any catalyst
control center to tweak the video and audio. If AMD does finally give
Ubuntu 16.04 support then this insanity will end. Otherwise, I am
dependent on Ubuntu to create a better Turks driver for my AMD Radeon HD
6570. Thank you very much for all of your help!! I hope that this driver
problem can be resolved and Ubuntu 16.04 can be restored to sanity. Feel
free to keep me posted on it. Have a wonderful day!!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-174-generic 4.4.0-174.204
ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
Uname: Linux 4.4.0-173-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: amd64
Date: Fri Feb 12 13:44:33 2021
DuplicateSignature:
 package:linux-image-4.4.0-174-generic:4.4.0-174.204
 Setting up grub-pc (2.02~beta2-36ubuntu3.29) ...
 /var/lib/dpkg/info/grub-pc.config: 1: /etc/default/grub: radeon.audio=1#: not 
found
 dpkg: error processing package grub-pc (--configure):
  subprocess installed post-installation script returned error exit status 127
ErrorMessage: package linux-image-4.4.0-174-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
InstallationDate: Installed on 2019-04-17 (667 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32ubuntu0.2
SourcePackage: linux-signed
Title: package linux-image-4.4.0-174-generic 4.4.0-174.204 failed to 
install/upgrade: package linux-image-4.4.0-174-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-4.4.0-174-generic 4.4.0-174.204 failed to
  install/upgrade: package linux-image-4.4.0-174-generic is not ready
  for configuration  cannot configure (current status 'half-installed')

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

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

[Bug 1910995] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build

[Carlos Tavares Jr]

Confirmed on my HP Laptop as my wifi isn't being detected after this
upgrade. Whats weird is my wifi switch on the keyboard is now the
airplane mode and causing issues. Currently tethering off my phone to
write this message. Please fix as this bricked my wifi card built into
this HP 8640P workbook.

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module
  failed to build

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

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

[Bug 1908299] [NEW] Selecting area to grab puts gnome-screenshot into a 100% CPU busy loop

[jr]

Public bug reported:

Save dialog never appears.

I have used gnome-screenshot many times daily for years.
This started happening yesterday.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-screenshot 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 15 15:05:15 2020
InstallationDate: Installed on 2018-05-05 (955 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screenshot
UpgradeStatus: Upgraded to focal on 2020-07-27 (141 days ago)

** Affects: gnome-screenshot (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/1908299

Title:
  Selecting area to grab puts gnome-screenshot into a 100% CPU busy loop

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

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

[Bug 1906774] [NEW] Crashed during INstall on the new PI 400 Keyboard PC.

[michael robert zubas jr]

Public bug reported:

I tried to INstall the new Ubuntu MATE onto the new Raspberry Pi 400
Keyboard PC that was recently Released, and gave me an Error.

Tehre is the BUg Report.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-1015.15-raspi 5.4.44
Uname: Linux 5.4.0-1015-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: arm64
CasperMD5CheckResult: skip
Date: Fri Dec  4 01:49:55 2020
ImageMediaBuild: 20200812
SourcePackage: ubiquity
UbiquityDebug:
 
UbiquitySyslog:
 
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug arm64 focal oem-config uec-images

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

Title:
  Crashed during INstall on the new PI 400 Keyboard PC.

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

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

[Bug 1906774] Re: Crashed during INstall on the new PI 400 Keyboard PC.

[michael robert zubas jr]

Please look into this so others who buy this new Product can have Ease
Of Use.

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

Title:
  Crashed during INstall on the new PI 400 Keyboard PC.

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

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

Re: [Bug 1903408] Re: Raspberry Pi 4 Issue with Blueman

[michael robert zubas jr]

I updated the Blue man Program without the Driver's as an Experiment, It
works fine until you Update the "Raspberry Pi 3 Bluetooth Driver"

It's a Driver Issue, someone needs to Separate the Raspberry Pi 3, and 4
Driver's..

Be Safe.

Z.

On Mon, Nov 30, 2020, 11:26 avdzm <1903...@bugs.launchpad.net> wrote:

> i think the problem might be with bluez...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1903408
>
> Title:
>   Raspberry Pi 4 Issue with Blueman
>
> Status in Ubuntu MATE:
>   New
> Status in blueman package in Ubuntu:
>   New
>
> Bug description:
>   So when I do the Initial Install of Ubuntu MATE 20.whatever, the
>   Bluetooth works fine, but Ubuntu forces an Update of Raspberry Pi 3
>   onto my Raspberry Pi 4, which Breaks it, every time I try to connect
>   to a Device after, I get a "No Host to Connect" error Repeatedly, and
>   I am forced to Reinstall.
>
>   Please either take out the Update for Blue-man, or ask them to make an
>   Update for the Raspberry Pi 4, thank you for your time.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-mate/+bug/1903408/+subscriptions
>

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

Title:
  Raspberry Pi 4 Issue with Blueman

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

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

Re: [Bug 1903408] Re: Raspberry Pi 4 Issue with Blueman

[michael robert zubas jr]

I found that installing the Blue man Update is OK, Just do Not allow MATE
to update the Bluetooth Raspberry Pi Drivers themselves, That's the Issue.
I've had to Reinstall Multiple times, And I have concluded that Ensuring
the Bluetooth Driver's it the only Solution, at least until the MATE Team
either takes out the Update, Or the Raspberry Pi people make a new update.

Be Safe.

Z.

On Mon, Nov 30, 2020, 10:51 avdzm <1903...@bugs.launchpad.net> wrote:

> Hello again,
> The mouse has stopped working
>
> tried again to re-pair, no luck.
>
> I tried in terminal as well, no luck...
>
>
> Below are the attempts...
> pi@umatepi:~$ bluetoothctl devices
> pi@umatepi:~$ bluetoothctl scan on
> Discovery started
> [CHG] Controller AA:AA:AA:AA:AA:AA Discovering: yes
> [NEW] Device CA:62:5B:42:2F:57 BluetoothMouse3600
> ^Cpi@umatepi:~$ bluetoothctl pair CA:62:5B:42:2F:57
> Attempting to pair with CA:62:5B:42:2F:57
> [CHG] Device CA:62:5B:42:2F:57 Connected: yes
> [CHG] Device CA:62:5B:42:2F:57 Connected: no
> ^Cpi@umatepi:~$ bluetoothctl pair CA:62:5B:42:2F:57
> Attempting to pair with CA:62:5B:42:2F:57
> ^Cpi@umatepi:~$ bluetoothctl pair CA:62:5B:42:2F:57
> Attempting to pair with CA:62:5B:42:2F:57
> Failed to pair: org.bluez.Error.InProgress
> pi@umatepi:~$ bluetoothctl pair CA:62:5B:42:2F:57
> Attempting to pair with CA:62:5B:42:2F:57
> Failed to pair: org.bluez.Error.InProgress
> pi@umatepi:~$ bluetoothctl connect CA:62:5B:42:2F:57
> Attempting to connect to CA:62:5B:42:2F:57
> Failed to connect: org.bluez.Error.Failed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1903408
>
> Title:
>   Raspberry Pi 4 Issue with Blueman
>
> Status in Ubuntu MATE:
>   New
> Status in blueman package in Ubuntu:
>   New
>
> Bug description:
>   So when I do the Initial Install of Ubuntu MATE 20.whatever, the
>   Bluetooth works fine, but Ubuntu forces an Update of Raspberry Pi 3
>   onto my Raspberry Pi 4, which Breaks it, every time I try to connect
>   to a Device after, I get a "No Host to Connect" error Repeatedly, and
>   I am forced to Reinstall.
>
>   Please either take out the Update for Blue-man, or ask them to make an
>   Update for the Raspberry Pi 4, thank you for your time.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-mate/+bug/1903408/+subscriptions
>

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

Title:
  Raspberry Pi 4 Issue with Blueman

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

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

[Bug 1901365] [NEW] package grub-pc 2.02~beta2-36ubuntu3.28 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Robert N Hubby Jr]

Public bug reported:

I have this error and other errors as a result of the loss of my HDMI
audio driver from my AMD HD Radeon 6570 video card on Ubuntu 16.04 LTS.
There are a number of kernels that can't update. I'm stuck with a
partial upgrade with many errors all because the HDMI audio driver would
not load after unplugging my Cakewalk UA25-EX Sound Card from the USB
port.It seems that I have not been able to restore the HDMI audio driver
which shows up in constant error messages and is affecting any updates.
It also affects the way the video driver loads the desktop. I am curious
about how to resolve this problem so that updates can be normal not
partials with errors. The name of the video driver that shares the audio
driver name is AMD TURKS (DRM 2.43.0 / 4.4.0-173-generic, LLVM 6.0.0). I
presume that the HDMI audio is similar Turks/Whistler HDMI Audio [Radeon
HD 6000 Series]. The Cakewalk UA25-EX USB Audio drivers work perfectly.
It is the HDMI Audio driver that is the problem. I was thinking about
taking out the video card and booting from on board graphics to reset
the hard drive and then putting the video card back in and maybe the
HDMI audio will be recognized again but because of all these kernel
errors, I'm scared that it might make things worse than before and
possibly not boot-able. Does anyone have any suggestions to resolve this
problem, restoring the HDMI audio and correcting the broken kernels
which are constantly evident any time I try to update the system. I have
a Gateway DX4300 computer with 8GB of RAM and a AMD Phenom(tm) 9750
Quad-Core Processor × 4 . The video driver is the AMD TURKS (DRM 2.43.0
/ 4.4.0-173-generic, LLVM 6.0.0). The video card is a AMD HD Radeon 6570
video card.I think that the package name is package grub-pc
2.02~beta2-36ubuntu3.28. I don't know the version number.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: grub-pc 2.02~beta2-36ubuntu3.28
ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
Uname: Linux 4.4.0-173-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.25
Architecture: amd64
Date: Sat Oct 24 19:26:34 2020
DuplicateSignature:
 package:grub-pc:2.02~beta2-36ubuntu3.28
 Setting up grub-pc (2.02~beta2-36ubuntu3.28) ...
 /var/lib/dpkg/info/grub-pc.config: 1: /etc/default/grub: radeon.audio=1#: not 
found
 dpkg: error processing package grub-pc (--configure):
  subprocess installed post-installation script returned error exit status 127
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
InstallationDate: Installed on 2019-04-17 (556 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
InvalidGrubScript: /etc/default/grub
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-173-generic 
root=UUID=d095aa3f-96d5-4645-be23-2a273fda157f ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32ubuntu0.1
SourcePackage: grub2
Title: package grub-pc 2.02~beta2-36ubuntu3.28 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package grub-pc 2.02~beta2-36ubuntu3.28 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

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

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

Re: [Bug 1899682] Re: package postfix-doc 3.4.13-0ubuntu1 failed to install/upgrade: installed postfix-doc package pre-removal script subprocess returned error exit status 1

[Ken Huffman, Jr.]

I've rebooted/shutdown several times and no more errors.  No apparent
problems in what I'm doing with the OS either. My report was just the
standard "send report" button submission in case it helped anyone.

Thanks for the look. I'm happy with operations at this time. If I can
provide any other info or data please let me know.

Thanks!
Ken (khuffmanjr)

On Wed, Oct 14, 2020, 14:00 Sergio Durigan Junior <
1899...@bugs.launchpad.net> wrote:

> Thank you for taking the time to file a bug report.
>
> I tried reproducing the upgrade path here inside a lxd container.  Of
> course, since some of the versions you mentioned above are EOL'ed, I
> started with bionic and upgraded to focal.  Everything worked.  I made
> sure to have postfix, postfix-doc and all the other postfix-* packages
> installed.  I also tried purging/removing some postfix-* packages, and
> then postfix, and then postfix-doc, but everything worked.  Your logs
> tell me that the prerm script of postfix-doc could not locate the
> /etc/postfix/main.cf file.  This is what the script does:
>
> case "$1" in
> remove|upgrade|deconfigure)
> if [ -x /usr/sbin/postconf ]; then
> postconf -e readme_directory=no html_directory=no
> fi
> ;;
> ...
>
> The only way I could reproduce the failure you've seen was if I manually
> removed/renamed /etc/postfix/main.cf, and the "apt remove postfix-doc":
>
> Removing postfix-doc (3.4.13-0ubuntu1) ...
> postconf: fatal: open /etc/postfix/main.cf for reading: No such file or
> directory
> dpkg: error processing package postfix-doc (--remove):
>  installed postfix-doc package pre-removal script subprocess returned
> error exit status 1
> dpkg: too many errors, stopping
> Errors were encountered while processing:
>  postfix-doc
> Processing was halted because there were too many errors.
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> I could not think of a way to remove postfix and still have
> /usr/sbin/postconf available.  From your logs (especifically the
> DpkgTerminalLog.txt), it is not clear whether postfix was removed before
> the other postfix-* packages, but I very much doubt this was the case.
>
> Since it seems likely to me that this is a local configuration problem,
> rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.
>
> However, if you believe that this is really a bug in Ubuntu, then we would
> be grateful if you would provide a more complete description of the problem
> with steps to reproduce, explain why you believe this is a bug in Ubuntu
> rather than a problem specific to your system, and then change the bug
> status back to "New".
>
> For local configuration issues, you can find assistance here:
> http://www.ubuntu.com/support/community
>
> ** Changed in: postfix (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1899682
>
> Title:
>   package postfix-doc 3.4.13-0ubuntu1 failed to install/upgrade:
>   installed postfix-doc package pre-removal script subprocess returned
>   error exit status 1
>
> Status in postfix package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Received this prior to, and following, a reboot at end of upgrade from
>   19.10 to 20.04 on Oct 13, 2020.  This machine has been upgraded from
>   18.10 to 19.04 to 19.10 to 20.04 over the last two days.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 20.04
>   Package: postfix-doc 3.4.13-0ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
>   Uname: Linux 5.4.0-48-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.9
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   Date: Tue Oct 13 13:00:56 2020
>   Dependencies:
>
>   DuplicateSignature:
>package:postfix-doc:3.4.13-0ubuntu1
>Removing postfix-doc (3.4.13-0ubuntu1) ...
>postconf: fatal: open /etc/postfix/main.cf for reading: No such file
> or directory
>dpkg: error processing package postfix-doc (--remove):
> installed postfix-doc package pre-removal script subprocess returned
> error exit status 1
>   ErrorMessage: installed postfix-doc package pre-removal script
> subprocess returned error exit status 1
>   InstallationDate: Installed on 2018-11-14 (698 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
>   PackageArchitecture: all
>   Python3Details: /usr/bin/python3.8, Python 3.8.5, 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.2ubuntu0.1
>   SourcePackage: postfix
>   Title: package postfix-doc 3.4.13-0ubuntu1 failed to install/upgrade:
> installed postfix-doc package pre-removal script subprocess returned error
> exit status 1
>   UpgradeStatus: Upgraded to focal on 2020-10-13 (0 days ago)
>
> To manage notifications about this bug go to:
>
> 

[Bug 1899682] [NEW] package postfix-doc 3.4.13-0ubuntu1 failed to install/upgrade: installed postfix-doc package pre-removal script subprocess returned error exit status 1

[Ken Huffman, Jr.]

Public bug reported:

Received this prior to, and following, a reboot at end of upgrade from
19.10 to 20.04 on Oct 13, 2020.  This machine has been upgraded from
18.10 to 19.04 to 19.10 to 20.04 over the last two days.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: postfix-doc 3.4.13-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Oct 13 13:00:56 2020
Dependencies:
 
DuplicateSignature:
 package:postfix-doc:3.4.13-0ubuntu1
 Removing postfix-doc (3.4.13-0ubuntu1) ...
 postconf: fatal: open /etc/postfix/main.cf for reading: No such file or 
directory
 dpkg: error processing package postfix-doc (--remove):
  installed postfix-doc package pre-removal script subprocess returned error 
exit status 1
ErrorMessage: installed postfix-doc package pre-removal script subprocess 
returned error exit status 1
InstallationDate: Installed on 2018-11-14 (698 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, 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.2ubuntu0.1
SourcePackage: postfix
Title: package postfix-doc 3.4.13-0ubuntu1 failed to install/upgrade: installed 
postfix-doc package pre-removal script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-10-13 (0 days ago)

** Affects: postfix (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/1899682

Title:
  package postfix-doc 3.4.13-0ubuntu1 failed to install/upgrade:
  installed postfix-doc package pre-removal script subprocess returned
  error exit status 1

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

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

[Bug 1898958] [NEW] Error importing google caldendar from Online Accounts

[Robert A. Schaefer Jr.]

Public bug reported:

When I upgraded to 20.10 beta evolution wouldn't connect to the google
calendars of any of the accounts that I setup in the settings online
accounts.  I was able to add them through the evolution accounts mail
accounts options and that worked.  I tried removing the accounts in the
main accounts settings for ubuntu and putting them back again.  That
didn't correct the problem.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: evolution 3.38.0-1
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct  7 19:42:15 2020
ExecutablePath: /usr/bin/evolution
InstallationDate: Installed on 2020-05-21 (139 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: Upgraded to groovy on 2020-10-07 (1 days ago)

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


** Tags: amd64 apport-bug groovy

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

Title:
  Error importing google caldendar from Online Accounts

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

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

[Bug 1898910] [NEW] gnome-shell crashes when in Wayland and you try to change the Resolution

[Sean Miller Jr]

Public bug reported:

Ubuntu on Wayland crashes when you try to change the resolution even if your 
display supports the 
Version: 3.38.0-1ubuntu2
Release: 20.10 Groovy Gorilla (development branch)
What I expected to happen
1. Login to Wayland 
2. Change the resolution 
3. Go on with my day

What actually happened
1. Login to Wayland
2. Change the resolution
3. Wait a minute to get kicked to the gdm login screen
4. Now I am here.

ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct  7 12:55:35 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2020-10-07 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/gnome-shell/libst-1.0.so
 g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

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


** Tags: amd64 apport-crash groovy need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gnome-shell crashes when in Wayland and you try to change the
  Resolution

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

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

[Bug 1898383] [NEW] tcsh filename pattern matching fails

[Harry G McGavran Jr]

Public bug reported:

TCSH filename pattern matching bug --

To reproduce:

1) Make a subdirectory

2) cd to that subdirectory

3) create or touch the files x1 x2 x3 x4 x5 x6 x7 x8 and x9

4) execute the command:
  "echo x[7-9]"

You will see all the files echo, NOT just x7 x8 and x9...

/bin/sh and /bin/bash still do this correctly... but tcsh seems broken!

Description:Ubuntu 20.04.1 LTS
Release:20.04

tcsh:
  Installed: 6.21.00-1
  Candidate: 6.21.00-1
  Version table:
 *** 6.21.00-1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

** Affects: tcsh (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/1898383

Title:
  tcsh filename pattern matching fails

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

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

[Bug 1898362] [NEW] bluetooth not connecting to bluetooth headset

[Dominador A. Nobleza Jr.]

Public bug reported:

FAILED TO APPLY NETWORK SETTINGS
You might not be able to connect to the Bluetooth network via this machine

\/ Exception
g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.Failed: Traceback 
(most recent call last):
  File "/usr/lib/python3/dist-packages/blueman/main/DbusService.py", line 124, 
in _handle_method_call
    ok(method(*args))
  File "/usr/lib/python3/dist-packages/blueman/plugins/mechanism/Network.py", 
line 56, in _reload_network
    nc.apply_settings()
  File "/usr/lib/python3/dist-packages/blueman/main/NetConf.py", line 384, in 
apply_settings
    self.del_ipt_rules()
  File "/usr/lib/python3/dist-packages/blueman/main/NetConf.py", line 329, in 
del_ipt_rules
    call(["/sbin/iptables", "-t", table, "-D", chain] + rule.split(" "))
  File "/usr/lib/python3.8/subprocess.py", line 340, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/sbin/iptables'
 (0)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: MATE
Date: Sat Oct  3 21:05:42 2020
InstallationDate: Installed on 2020-09-17 (16 days ago)
InstallationMedia: Ubuntu-MATE 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_PH:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-10-01 (2 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu
 Importance: Undecided
 Status: New


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

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

Title:
  bluetooth not connecting to bluetooth headset

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

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

[Bug 1888073] [NEW] ubunt 20.4 lts desktop intaller crashed

[Allen L Malsbary Jr]

Public bug reported:

I was installing Ubuntu from usb stick and it crashed

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/efi.img
CasperMD5CheckResult: fail
CasperVersion: 1.445
Date: Sat Jul 18 11:27:48 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
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 ubuntu

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

Title:
  ubunt 20.4 lts desktop intaller crashed

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

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

[Bug 1885400] Re: [ 0.613555] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [CPB3] at bit offset/length 64/32 exceeds size of target Buffer (64 bits) (20190816/dsopcode-198) [ 0.615101] ACPI Error

[JR@Protheus]

Please help me. The first boot does not complete the ubuntu boot, but
after restarting, error messages appear but complete the boot

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

Title:
  [0.613555] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field
  [CPB3] at bit offset/length 64/32 exceeds size of target Buffer (64
  bits) (20190816/dsopcode-198) [0.615101] ACPI Error: Aborting
  method \_SB._OSC due to previous error (AE_AML_BUFFER_LIMIT)
  (20190816/psparse-529)

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

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

[Bug 1885400] [NEW] [ 0.613555] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [CPB3] at bit offset/length 64/32 exceeds size of target Buffer (64 bits) (20190816/dsopcode-198) [ 0.615101] ACPI Err

[JR@Protheus]

Public bug reported:

[0.613555] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [CPB3] at bit 
offset/length 64/32 exceeds size of target Buffer (64 bits) 
(20190816/dsopcode-198)
[0.615101] ACPI Error: Aborting method \_SB._OSC due to previous error 
(AE_AML_BUFFER_LIMIT) (20190816/psparse-529)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: acpi (not installed)
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Sat Jun 27 20:56:14 2020
SourcePackage: acpi
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: acpi (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/1885400

Title:
  [0.613555] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field
  [CPB3] at bit offset/length 64/32 exceeds size of target Buffer (64
  bits) (20190816/dsopcode-198) [0.615101] ACPI Error: Aborting
  method \_SB._OSC due to previous error (AE_AML_BUFFER_LIMIT)
  (20190816/psparse-529)

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

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

Re: [Bug 1880728] Re: [amdgpu] Gnome Shell freeze

[David Landis Jr]

another crash yesterday no new error links, ran another prevboot.

On Thu, Jun 18, 2020 at 7:57 AM DavidJr. 
wrote:

> Crashed again overnight.  No response from mouse, keyboard, or power
> button.  Hard rebooted.  Dont see any new error links.  I have reinstalled
> TeamViewer and disabled dash to dock to see if that does anything
> different.
>
> On Wed, Jun 17, 2020 at 9:50 PM Daniel van Vugt <
> 1880...@bugs.launchpad.net> wrote:
>
>> Oh those are much better links, thanks. There you have:
>>
>> Bug 1877075: A fix for 20.04 is on the way (you will need libmutter
>> version 3.36.3).
>>
>> Bug 1843982: A fix for 20.04 was released to updates yesterday.
>>
>> Bug 1878775: Not sure but maybe fixed with bug 1843982 yesterday?
>>
>> But that doesn't help us to choose a single issue for this bug to be
>> about. I guess this bug doesn't need to stay open unless we can identify
>> some new issue that doesn't already have a bug ID. Please continue
>> reporting your crashes here so we can find some pattern.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1880728
>>
>> Title:
>>   [amdgpu] Gnome Shell freeze
>>
>> Status in gnome-shell package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   was logged in through team viewer and got kicked out.  when i was able
>>   to physically access the machine the screens were on, but was not able
>>   to move the mouse or interact with the computer.  performed hard
>>   reboot to get it back on.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 20.04
>>   Package: xorg 1:7.7+19ubuntu14
>>   ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
>>   Uname: Linux 5.4.0-31-generic x86_64
>>   ApportVersion: 2.20.11-0ubuntu27
>>   Architecture: amd64
>>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>>   CasperMD5CheckResult: skip
>>   CompositorRunning: None
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Tue May 26 11:24:02 2020
>>   DistUpgraded: Fresh install
>>   DistroCodename: focal
>>   DistroVariant: ubuntu
>>   ExtraDebuggingInterest: Yes
>>   GpuHangFrequency: Several times a week
>>   GpuHangReproducibility: Seems to happen randomly
>>   GpuHangStarted: Immediately after installing this version of Ubuntu
>>   GraphicsCard:
>>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX
>> 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA
>> controller])
>>  Subsystem: PC Partner Limited / Sapphire Technology Radeon RX
>> 470/480 [174b:e347]
>>   InstallationDate: Installed on 2020-05-09 (16 days ago)
>>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>> (20200423)
>>   MachineType: Micro-Star International Co., Ltd. MS-7A34
>>   ProcEnviron:
>>PATH=(custom, no user)
>>XDG_RUNTIME_DIR=
>>LANG=en_US.UTF-8
>>SHELL=/bin/bash
>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic
>> root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7
>>   SourcePackage: xorg
>>   Symptom: display
>>   Title: Xorg freeze
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 07/08/2019
>>   dmi.bios.vendor: American Megatrends Inc.
>>   dmi.bios.version: A.LM
>>   dmi.board.asset.tag: To be filled by O.E.M.
>>   dmi.board.name: B350 PC MATE(MS-7A34)
>>   dmi.board.vendor: Micro-Star International Co., Ltd
>>   dmi.board.version: 2.0
>>   dmi.chassis.asset.tag: To be filled by O.E.M.
>>   dmi.chassis.type: 3
>>   dmi.chassis.vendor: Micro-Star International Co., Ltd.
>>   dmi.chassis.version: 2.0
>>   dmi.modalias:
>> dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
>>   dmi.product.family: To be filled by O.E.M.
>>   dmi.product.name: MS-7A34
>>   dmi.product.sku: To be filled by O.E.M.
>>   dmi.product.version: 2.0
>>   dmi.sys.vendor: Micro-Star International Co., Ltd.
>>   version.compiz: compiz N/A
>>   version.libdrm2: libdrm2 2.4.101-2
>>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
>>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
>>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
>> 2:2.99.917+git20200226-1
>>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
>> 1:1.0.16-1
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880728/+subscriptions
>>
>


** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/bugs/1880728/+attachment/5385615/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 

Re: [Bug 1880728] Re: [amdgpu] Gnome Shell freeze

[David Landis Jr]

Crashed again overnight.  No response from mouse, keyboard, or power
button.  Hard rebooted.  Dont see any new error links.  I have reinstalled
TeamViewer and disabled dash to dock to see if that does anything
different.

On Wed, Jun 17, 2020 at 9:50 PM Daniel van Vugt <1880...@bugs.launchpad.net>
wrote:

> Oh those are much better links, thanks. There you have:
>
> Bug 1877075: A fix for 20.04 is on the way (you will need libmutter
> version 3.36.3).
>
> Bug 1843982: A fix for 20.04 was released to updates yesterday.
>
> Bug 1878775: Not sure but maybe fixed with bug 1843982 yesterday?
>
> But that doesn't help us to choose a single issue for this bug to be
> about. I guess this bug doesn't need to stay open unless we can identify
> some new issue that doesn't already have a bug ID. Please continue
> reporting your crashes here so we can find some pattern.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1880728
>
> Title:
>   [amdgpu] Gnome Shell freeze
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   was logged in through team viewer and got kicked out.  when i was able
>   to physically access the machine the screens were on, but was not able
>   to move the mouse or interact with the computer.  performed hard
>   reboot to get it back on.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
>   Uname: Linux 5.4.0-31-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue May 26 11:24:02 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a week
>   GpuHangReproducibility: Seems to happen randomly
>   GpuHangStarted: Immediately after installing this version of Ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX
> 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA
> controller])
>  Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480
> [174b:e347]
>   InstallationDate: Installed on 2020-05-09 (16 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: Micro-Star International Co., Ltd. MS-7A34
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic
> root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/08/2019
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: A.LM
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: B350 PC MATE(MS-7A34)
>   dmi.board.vendor: Micro-Star International Co., Ltd
>   dmi.board.version: 2.0
>   dmi.chassis.asset.tag: To be filled by O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Micro-Star International Co., Ltd.
>   dmi.chassis.version: 2.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
>   dmi.product.family: To be filled by O.E.M.
>   dmi.product.name: MS-7A34
>   dmi.product.sku: To be filled by O.E.M.
>   dmi.product.version: 2.0
>   dmi.sys.vendor: Micro-Star International Co., Ltd.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880728/+subscriptions
>

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

Title:
  [amdgpu] Gnome Shell freeze

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

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

Re: [Bug 1880728] Re: [amdgpu] Gnome Shell freeze

[David Landis Jr]

Here are a couple other links from errors.ubuntu.com today.  There were
three from temviewer as well, but i did not list those here.

https://errors.ubuntu.com/oops/5f1c4638-b0a5-11ea-af49-fa163e983629
https://errors.ubuntu.com/oops/69a6aac2-b0a4-11ea-9cf2-fa163e102db1
https://errors.ubuntu.com/oops/3fa61456-b0a4-11ea-a652-fa163e6cac46
https://errors.ubuntu.com/oops/3a454040-b0a4-11ea-9cf2-fa163e102db1

I actually just uninstalled teamviewer to see if that resolves anything.  I
am going to be using a different program called anydesk for right now.


On Wed, Jun 17, 2020 at 8:55 PM Daniel van Vugt <1880...@bugs.launchpad.net>
wrote:

> The crash in comment #9 is
>
>   /opt/teamviewer/tv_bin/TeamViewer_Desktop
>
> While that doesn't appear to be a supported component of Ubuntu, if that
> is the main crash you experience then it would account for this bug. But
> still, we can't help with crashes of TeamViewer itself. So let's ignore
> any crashes in TeamViewer binaries here. We're only interested in
> crashes of 'gnome-shell' or 'Xorg'. Because those are provided by
> Ubuntu.
>
> Please continue repeating the steps from comment #2 as we still need to
> figure out the signature of a recurring problem in gnome-shell, if any.
>
> You also seem to have the extension 'dash-to-dock' loaded so please try
> removing that.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1880728
>
> Title:
>   [amdgpu] Gnome Shell freeze
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   was logged in through team viewer and got kicked out.  when i was able
>   to physically access the machine the screens were on, but was not able
>   to move the mouse or interact with the computer.  performed hard
>   reboot to get it back on.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
>   Uname: Linux 5.4.0-31-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue May 26 11:24:02 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a week
>   GpuHangReproducibility: Seems to happen randomly
>   GpuHangStarted: Immediately after installing this version of Ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX
> 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA
> controller])
>  Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480
> [174b:e347]
>   InstallationDate: Installed on 2020-05-09 (16 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: Micro-Star International Co., Ltd. MS-7A34
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic
> root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/08/2019
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: A.LM
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: B350 PC MATE(MS-7A34)
>   dmi.board.vendor: Micro-Star International Co., Ltd
>   dmi.board.version: 2.0
>   dmi.chassis.asset.tag: To be filled by O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Micro-Star International Co., Ltd.
>   dmi.chassis.version: 2.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
>   dmi.product.family: To be filled by O.E.M.
>   dmi.product.name: MS-7A34
>   dmi.product.sku: To be filled by O.E.M.
>   dmi.product.version: 2.0
>   dmi.sys.vendor: Micro-Star International Co., Ltd.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880728/+subscriptions
>

-- 
You 

Re: [Bug 1880728] Re: [amdgpu] Xorg freeze

[David Landis Jr]

crashed again this afternoon.  attached is another prevboot file.

On Wed, Jun 17, 2020 at 8:11 AM DavidJr. 
wrote:

> Crashed again overnight.  Went to wake the screen (the computer doesnt
> sleep, just turns off the screen) and got no response from the mouse or
> keyboard.  When i pressed the power buttonit woke the screen, but it was
> just a black screen with the mouse cursor displayed, but not able to be
> moved.  There is a new error on errors.ubuntu.com, but it was in the
> afternoon and i used it in the evening just fine. Here is the link:
> https://errors.ubuntu.com/oops/1abba6b4-b09b-11ea-aba8-fa163ee63de6
>
> i also am attaching another prevboot file that i ran after it powered up
> this morning.
>
> On Mon, Jun 15, 2020 at 9:29 PM DavidJr.  wrote:
>
>> attached is the file requested.  I have unplugged the viewsonic monitor
>> from the GPU and will run for a while to see if it still has issues.
>>
>> On Mon, Jun 15, 2020 at 9:00 PM Daniel van Vugt <
>> 1880...@bugs.launchpad.net> wrote:
>>
>>> Thanks. Certainly gnome-shell is crashing so we should focus on those:
>>>
>>> https://errors.ubuntu.com/oops/f1dcc3fa-988e-11ea-ad8b-fa163e983629
>>> https://errors.ubuntu.com/oops/f3279c74-95fc-11ea-a45e-fa163e6cac46
>>> https://errors.ubuntu.com/oops/53690272-9516-11ea-a9c3-fa163ee63de6
>>>
>>> Unfortunately there isn't any debugging information available in those.
>>>
>>> What I can see is a recurring problem with your ViewSonic monitor being
>>> redetected/reconnected on DVI regularly. So it looks like there's a
>>> connection problem there which might be triggering this. Please try
>>> replacing the DVI cable, or leaving the ViewSonic unplugged for a while
>>> to see if the problem goes away.
>>>
>>> Please also run this command:
>>>
>>>   gsettings list-recursively org.gnome.shell > settings.txt
>>>
>>> and then attach the resulting text file here.
>>>
>>>
>>> ** Summary changed:
>>>
>>> - [amdgpu] Xorg freeze
>>> + [amdgpu] Gnome Shell freeze
>>>
>>> ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu)
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1880728
>>>
>>> Title:
>>>   [amdgpu] Gnome Shell freeze
>>>
>>> Status in gnome-shell package in Ubuntu:
>>>   Incomplete
>>>
>>> Bug description:
>>>   was logged in through team viewer and got kicked out.  when i was able
>>>   to physically access the machine the screens were on, but was not able
>>>   to move the mouse or interact with the computer.  performed hard
>>>   reboot to get it back on.
>>>
>>>   ProblemType: Bug
>>>   DistroRelease: Ubuntu 20.04
>>>   Package: xorg 1:7.7+19ubuntu14
>>>   ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
>>>   Uname: Linux 5.4.0-31-generic x86_64
>>>   ApportVersion: 2.20.11-0ubuntu27
>>>   Architecture: amd64
>>>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>>>   CasperMD5CheckResult: skip
>>>   CompositorRunning: None
>>>   CurrentDesktop: ubuntu:GNOME
>>>   Date: Tue May 26 11:24:02 2020
>>>   DistUpgraded: Fresh install
>>>   DistroCodename: focal
>>>   DistroVariant: ubuntu
>>>   ExtraDebuggingInterest: Yes
>>>   GpuHangFrequency: Several times a week
>>>   GpuHangReproducibility: Seems to happen randomly
>>>   GpuHangStarted: Immediately after installing this version of Ubuntu
>>>   GraphicsCard:
>>>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX
>>> 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA
>>> controller])
>>>  Subsystem: PC Partner Limited / Sapphire Technology Radeon RX
>>> 470/480 [174b:e347]
>>>   InstallationDate: Installed on 2020-05-09 (16 days ago)
>>>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>>> (20200423)
>>>   MachineType: Micro-Star International Co., Ltd. MS-7A34
>>>   ProcEnviron:
>>>PATH=(custom, no user)
>>>XDG_RUNTIME_DIR=
>>>LANG=en_US.UTF-8
>>>SHELL=/bin/bash
>>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic
>>> root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7
>>>   SourcePackage: xorg
>>>   Symptom: display
>>>   Title: Xorg freeze
>>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>>   dmi.bios.date: 07/08/2019
>>>   dmi.bios.vendor: American Megatrends Inc.
>>>   dmi.bios.version: A.LM
>>>   dmi.board.asset.tag: To be filled by O.E.M.
>>>   dmi.board.name: B350 PC MATE(MS-7A34)
>>>   dmi.board.vendor: Micro-Star International Co., Ltd
>>>   dmi.board.version: 2.0
>>>   dmi.chassis.asset.tag: To be filled by O.E.M.
>>>   dmi.chassis.type: 3
>>>   dmi.chassis.vendor: Micro-Star International Co., Ltd.
>>>   dmi.chassis.version: 2.0
>>>   dmi.modalias:
>>> dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
>>>   dmi.product.family: To be 

Re: [Bug 1880728] Re: [amdgpu] Xorg freeze

[David Landis Jr]

Crashed again overnight.  Went to wake the screen (the computer doesnt
sleep, just turns off the screen) and got no response from the mouse or
keyboard.  When i pressed the power buttonit woke the screen, but it was
just a black screen with the mouse cursor displayed, but not able to be
moved.  There is a new error on errors.ubuntu.com, but it was in the
afternoon and i used it in the evening just fine. Here is the link:
https://errors.ubuntu.com/oops/1abba6b4-b09b-11ea-aba8-fa163ee63de6

i also am attaching another prevboot file that i ran after it powered up
this morning.

On Mon, Jun 15, 2020 at 9:29 PM DavidJr. 
wrote:

> attached is the file requested.  I have unplugged the viewsonic monitor
> from the GPU and will run for a while to see if it still has issues.
>
> On Mon, Jun 15, 2020 at 9:00 PM Daniel van Vugt <
> 1880...@bugs.launchpad.net> wrote:
>
>> Thanks. Certainly gnome-shell is crashing so we should focus on those:
>>
>> https://errors.ubuntu.com/oops/f1dcc3fa-988e-11ea-ad8b-fa163e983629
>> https://errors.ubuntu.com/oops/f3279c74-95fc-11ea-a45e-fa163e6cac46
>> https://errors.ubuntu.com/oops/53690272-9516-11ea-a9c3-fa163ee63de6
>>
>> Unfortunately there isn't any debugging information available in those.
>>
>> What I can see is a recurring problem with your ViewSonic monitor being
>> redetected/reconnected on DVI regularly. So it looks like there's a
>> connection problem there which might be triggering this. Please try
>> replacing the DVI cable, or leaving the ViewSonic unplugged for a while
>> to see if the problem goes away.
>>
>> Please also run this command:
>>
>>   gsettings list-recursively org.gnome.shell > settings.txt
>>
>> and then attach the resulting text file here.
>>
>>
>> ** Summary changed:
>>
>> - [amdgpu] Xorg freeze
>> + [amdgpu] Gnome Shell freeze
>>
>> ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu)
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1880728
>>
>> Title:
>>   [amdgpu] Gnome Shell freeze
>>
>> Status in gnome-shell package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   was logged in through team viewer and got kicked out.  when i was able
>>   to physically access the machine the screens were on, but was not able
>>   to move the mouse or interact with the computer.  performed hard
>>   reboot to get it back on.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 20.04
>>   Package: xorg 1:7.7+19ubuntu14
>>   ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
>>   Uname: Linux 5.4.0-31-generic x86_64
>>   ApportVersion: 2.20.11-0ubuntu27
>>   Architecture: amd64
>>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>>   CasperMD5CheckResult: skip
>>   CompositorRunning: None
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Tue May 26 11:24:02 2020
>>   DistUpgraded: Fresh install
>>   DistroCodename: focal
>>   DistroVariant: ubuntu
>>   ExtraDebuggingInterest: Yes
>>   GpuHangFrequency: Several times a week
>>   GpuHangReproducibility: Seems to happen randomly
>>   GpuHangStarted: Immediately after installing this version of Ubuntu
>>   GraphicsCard:
>>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX
>> 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA
>> controller])
>>  Subsystem: PC Partner Limited / Sapphire Technology Radeon RX
>> 470/480 [174b:e347]
>>   InstallationDate: Installed on 2020-05-09 (16 days ago)
>>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
>> (20200423)
>>   MachineType: Micro-Star International Co., Ltd. MS-7A34
>>   ProcEnviron:
>>PATH=(custom, no user)
>>XDG_RUNTIME_DIR=
>>LANG=en_US.UTF-8
>>SHELL=/bin/bash
>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic
>> root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7
>>   SourcePackage: xorg
>>   Symptom: display
>>   Title: Xorg freeze
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 07/08/2019
>>   dmi.bios.vendor: American Megatrends Inc.
>>   dmi.bios.version: A.LM
>>   dmi.board.asset.tag: To be filled by O.E.M.
>>   dmi.board.name: B350 PC MATE(MS-7A34)
>>   dmi.board.vendor: Micro-Star International Co., Ltd
>>   dmi.board.version: 2.0
>>   dmi.chassis.asset.tag: To be filled by O.E.M.
>>   dmi.chassis.type: 3
>>   dmi.chassis.vendor: Micro-Star International Co., Ltd.
>>   dmi.chassis.version: 2.0
>>   dmi.modalias:
>> dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
>>   dmi.product.family: To be filled by O.E.M.
>>   dmi.product.name: MS-7A34
>>   dmi.product.sku: To be filled by O.E.M.
>>   dmi.product.version: 2.0
>>   dmi.sys.vendor: Micro-Star International Co., Ltd.
>>   version.compiz: compiz N/A
>>   version.libdrm2: libdrm2 

Re: [Bug 1880728] Re: [amdgpu] Xorg freeze

[David Landis Jr]

attached is the file requested.  I have unplugged the viewsonic monitor
from the GPU and will run for a while to see if it still has issues.

On Mon, Jun 15, 2020 at 9:00 PM Daniel van Vugt <1880...@bugs.launchpad.net>
wrote:

> Thanks. Certainly gnome-shell is crashing so we should focus on those:
>
> https://errors.ubuntu.com/oops/f1dcc3fa-988e-11ea-ad8b-fa163e983629
> https://errors.ubuntu.com/oops/f3279c74-95fc-11ea-a45e-fa163e6cac46
> https://errors.ubuntu.com/oops/53690272-9516-11ea-a9c3-fa163ee63de6
>
> Unfortunately there isn't any debugging information available in those.
>
> What I can see is a recurring problem with your ViewSonic monitor being
> redetected/reconnected on DVI regularly. So it looks like there's a
> connection problem there which might be triggering this. Please try
> replacing the DVI cable, or leaving the ViewSonic unplugged for a while
> to see if the problem goes away.
>
> Please also run this command:
>
>   gsettings list-recursively org.gnome.shell > settings.txt
>
> and then attach the resulting text file here.
>
>
> ** Summary changed:
>
> - [amdgpu] Xorg freeze
> + [amdgpu] Gnome Shell freeze
>
> ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1880728
>
> Title:
>   [amdgpu] Gnome Shell freeze
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   was logged in through team viewer and got kicked out.  when i was able
>   to physically access the machine the screens were on, but was not able
>   to move the mouse or interact with the computer.  performed hard
>   reboot to get it back on.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
>   Uname: Linux 5.4.0-31-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue May 26 11:24:02 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a week
>   GpuHangReproducibility: Seems to happen randomly
>   GpuHangStarted: Immediately after installing this version of Ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX
> 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA
> controller])
>  Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480
> [174b:e347]
>   InstallationDate: Installed on 2020-05-09 (16 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: Micro-Star International Co., Ltd. MS-7A34
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic
> root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/08/2019
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: A.LM
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: B350 PC MATE(MS-7A34)
>   dmi.board.vendor: Micro-Star International Co., Ltd
>   dmi.board.version: 2.0
>   dmi.chassis.asset.tag: To be filled by O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Micro-Star International Co., Ltd.
>   dmi.chassis.version: 2.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
>   dmi.product.family: To be filled by O.E.M.
>   dmi.product.name: MS-7A34
>   dmi.product.sku: To be filled by O.E.M.
>   dmi.product.version: 2.0
>   dmi.sys.vendor: Micro-Star International Co., Ltd.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880728/+subscriptions
>


** Attachment added: "settings.txt"
   
https://bugs.launchpad.net/bugs/1880728/+attachment/5384228/+files/settings.txt

-- 

Re: [Bug 1880728] Re: [amdgpu] Xorg freeze

[David Landis Jr]

Here are the links to the errors from step #2(I did it wrong the first time
so these may have been there then as well):

https://errors.ubuntu.com/oops/f1dcc3fa-988e-11ea-ad8b-fa163e983629
https://errors.ubuntu.com/oops/f3279c74-95fc-11ea-a45e-fa163e6cac46
https://errors.ubuntu.com/oops/53690272-9516-11ea-a9c3-fa163ee63de6
https://errors.ubuntu.com/oops/474d8534-9477-11ea-9ada-fa163e102db1
https://errors.ubuntu.com/oops/9d7f349c-92d9-11ea-a412-fa163e6cac46
https://errors.ubuntu.com/oops/97142398-926f-11ea-a40c-fa163e6cac46

And i attached another prevboot file.

On Sun, Jun 14, 2020 at 9:41 PM Daniel van Vugt <1880...@bugs.launchpad.net>
wrote:

> Thanks. Unfortunately I can't see any evidence of the freeze in comment
> #4. Please repeat the steps in comments #2 and #3 next time it happens.
>
>
> ** Summary changed:
>
> - Xorg freeze
> + [amdgpu] Xorg freeze
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1880728
>
> Title:
>   [amdgpu] Xorg freeze
>
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   was logged in through team viewer and got kicked out.  when i was able
>   to physically access the machine the screens were on, but was not able
>   to move the mouse or interact with the computer.  performed hard
>   reboot to get it back on.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
>   Uname: Linux 5.4.0-31-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue May 26 11:24:02 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a week
>   GpuHangReproducibility: Seems to happen randomly
>   GpuHangStarted: Immediately after installing this version of Ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX
> 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA
> controller])
>  Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480
> [174b:e347]
>   InstallationDate: Installed on 2020-05-09 (16 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: Micro-Star International Co., Ltd. MS-7A34
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic
> root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/08/2019
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: A.LM
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: B350 PC MATE(MS-7A34)
>   dmi.board.vendor: Micro-Star International Co., Ltd
>   dmi.board.version: 2.0
>   dmi.chassis.asset.tag: To be filled by O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Micro-Star International Co., Ltd.
>   dmi.chassis.version: 2.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
>   dmi.product.family: To be filled by O.E.M.
>   dmi.product.name: MS-7A34
>   dmi.product.sku: To be filled by O.E.M.
>   dmi.product.version: 2.0
>   dmi.sys.vendor: Micro-Star International Co., Ltd.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1880728/+subscriptions
>


** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/bugs/1880728/+attachment/5384219/+files/prevboot.txt

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

Title:
  [amdgpu] Xorg freeze

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

-- 
ubuntu-bugs mailing list

Re: [Bug 1880728] Re: Xorg freeze

[David Landis Jr]

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
**NO LOG**

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
**NO LINKS**

I have actually reinstalled ubuntu since I reported this bug, but I started
having the issue again.  It just crashed this morning while i was
physically working on it.  Screens stayed on, mouse and keyboard were
unresponsive.  I performed a hard reboot and ran the command you asked.
Attached is the result.

On Tue, May 26, 2020 at 9:55 PM Daniel van Vugt <1880...@bugs.launchpad.net>
wrote:

> Also if the freeze happens again then immediately after rebooting please
> run:
>
>   journalctl -b-1 > prevboot.txt
>
> and attach the resulting text file here.
>
>
> ** Tags added: amdgpu
>
> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
>
> ** Changed in: xorg-server (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1880728
>
> Title:
>   Xorg freeze
>
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   was logged in through team viewer and got kicked out.  when i was able
>   to physically access the machine the screens were on, but was not able
>   to move the mouse or interact with the computer.  performed hard
>   reboot to get it back on.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
>   Uname: Linux 5.4.0-31-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue May 26 11:24:02 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a week
>   GpuHangReproducibility: Seems to happen randomly
>   GpuHangStarted: Immediately after installing this version of Ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX
> 470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA
> controller])
>  Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480
> [174b:e347]
>   InstallationDate: Installed on 2020-05-09 (16 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: Micro-Star International Co., Ltd. MS-7A34
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic
> root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg freeze
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/08/2019
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: A.LM
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: B350 PC MATE(MS-7A34)
>   dmi.board.vendor: Micro-Star International Co., Ltd
>   dmi.board.version: 2.0
>   dmi.chassis.asset.tag: To be filled by O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Micro-Star International Co., Ltd.
>   dmi.chassis.version: 2.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
>   dmi.product.family: To be filled by O.E.M.
>   dmi.product.name: MS-7A34
>   dmi.product.sku: To be filled by O.E.M.
>   dmi.product.version: 2.0
>   dmi.sys.vendor: Micro-Star International Co., Ltd.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1880728/+subscriptions
>


** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/bugs/1880728/+attachment/5383580/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

Re: [Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi

[Harry G McGavran Jr]

On 6/10/20 5:48 PM, Henrique de Moraes Holschuh wrote:
> This has been reported to be fixed on very similar processors (with the
> same microcode signature as yours) in the 20200609 microcode updates,
> could you test them?
> 

I see four versions on your webpage:

two versions of 3.20200609.0ubuntu0.16.04.1
and two versions of 3.20200609.0ubuntu0.16.04.0.

I downloaded all four and both versions of 3.20200609.0ubuntu0.16.04.1
compared without any differences AND both versions of
3.20200609.0ubuntu0.16.04.0 compared without any differences. So in
spite of the statement on the web page that each of those versions had a
different publishing time, the two versions of .1 seem to be the same
and the two versions of .0 seem to be the same.

So I tried BOTH versions and warm reboots DID work with either .0 or .1.

I left my machine with 3.20200609.0ubuntu0.16.04.1

Let me know if I missed any version you wished me to test...

Harry McGavran

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

Title:
  Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot
  with Intel(R) Xeon(R) W-2125 CPUi

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

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

[Bug 1880728] [NEW] Xorg freeze

[David Landis Jr]

Public bug reported:

was logged in through team viewer and got kicked out.  when i was able
to physically access the machine the screens were on, but was not able
to move the mouse or interact with the computer.  performed hard reboot
to get it back on.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue May 26 11:24:02 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev c7) (prog-if 00 [VGA 
controller])
   Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480 
[174b:e347]
InstallationDate: Installed on 2020-05-09 (16 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Micro-Star International Co., Ltd. MS-7A34
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=595b2c33-123b-4c4d-be9f-f87ce6ce8733 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.LM
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 PC MATE(MS-7A34)
dmi.board.vendor: Micro-Star International Co., Ltd
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.LM:bd07/08/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A34
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu

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

Title:
  Xorg freeze

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

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

[Bug 1878511] [NEW] bootloader install failed

[Sim Layne Jr]

Public bug reported:

Install on hp-17-bs0xx fails during install as the reserved boot-loader
partition failed, not happy.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445
Date: Wed May 13 20:22:36 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
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 ubuntu

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

Title:
  bootloader install failed

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

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

[Bug 1855318] Re: autofs tries to find .xdg-volume-info and autorun.inf

[John W. Brown, Jr.]

I have been trying to recreate in different permutations and I have come
to the conclusion that the 2 weird mounts aren't the primary issue.
Those are strange, but it appears to break when the autofs is started
and stopped multiple times as it would be if someone were trying to
troubleshoot there configuration.

It appears that the daemon does not clean up when it closes and can
sometimes leave open mounts That should be closed. I found that if I
stopped the daemon and restart, my configured mounts were not being
mounted automatically.

When this happens, the happy path only returns when I close the deamon
and manually release any held mounts.

To recreate the error:
1. I ran the daemon in debug mode in the foreground
2. navigated to OR did an "ls" on an automounted mount to verify that it was 
mounted
2.1 close any open file explorer windows
2.2 cd out of any mounted directories on the command line
3. After confirming the mount, I then manually close the running automount 
daemon
4. If I restart the automount daemon at this point, it does not consistently 
re-mount my configured mounts

This is where it is easy to assume that the 2 unconfigured mounts
initially reported are the symptoms of the failure. It appears that
automount does not cleanly close out in such a way that it can be
restarted without manual intervention. This may be known/inherited
bugginess of automount, and if so, maybe not a severe issue is being
reported here.

Still no explanation for the 2 unconfigured mounts though. That is still
valid unexpected behavior, whether the OS has autorun support or now.

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

Title:
  autofs tries to find .xdg-volume-info and autorun.inf

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

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

[Bug 1855318] Re: autofs tries to find .xdg-volume-info and autorun.inf

[John W. Brown, Jr.]

No, this is a real thing. The issue is valid. The explanation does not
dismiss it. Even if the assumption that the desktop is somehow looking
for these files for autorun functionality, how does that equate into an
entire mount point being generated.

Is this fallback behavior of some kind?

Just as the original example illustrated, the automount daemon
completely ignores the map file and attempts to mount these 2 mount
points instead. It didn't do that before.

** Changed in: autofs (Ubuntu)
   Status: Expired => New

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

Title:
  autofs tries to find .xdg-volume-info and autorun.inf

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

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

[Bug 1877763] [NEW] i was installing UBUNTU from bootable USB install option on screen while testing out UBUNTU. It ran well. So I tried to install it on 2nd hard drive that was empty. Old scsi drive.

[alton d davis jr]

Public bug reported:

i tested your ubuntu LTS 20.04 (focal fossa) via bootable USB stick.
testing was awesome.
I have:
Hewlett Packard 64bit
2 scsi drives internal
6gb ram
6 processors

drive 1 has windows 7 (running very slow)  1Terabyte in size
drive 2 (was) a backup of drive 1 but I changed that to being a separate drive. 
 500gb in size
BOTH DRIVES ARE SCSI DRIVES. (NEW TECHNOLOGY THEN/ I USED THAT IN WORK COMPUTER 
AT IBM AS WELL)

IN UBUNTU TEST RUN I SELECTED 2ND DRIVE AND IT SHOWED UNMOUNTED STATUS.

THEN I SELECTED FOR "INSTALLING UBUNTU" FROM THE MAIN WINDOW.

IT RAN A LITTLE AND THEN CRASHED. NOTED A POSSIBLE FAULTY DRIVE.  THERE
IS A POSSIBILITY IT MAY HAVE VERY LITTLE FEW BAD SECTORS.  BUT I HAVE
USED IT OFTEN IN THE PAST.

IF YOU THINK THE FEW BAD SECTORS WERE STOPPING INSTALLATION, DO YOU KNOW
WHERE I CAN GET ANOTHER "SCSI DRIVE"?

I WILL TRY WWW.NEWEGG.COM AND ALSO CONTACT HEWLETT PACKARD TO SEE WHO IS
THEIR SUGGESTED OLD PRODUCT VENDOR.

MOST HUMBLE REGARDS,

ALTON
(770)651-7009  I CAN CALL ANYWHERE IN USA OR CANADA FREE.  
HANDICAPPED - I DO BETTER IN CONVERSATION INSTEAD OF WRITTEN INSTRUCTIONS.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445
Date: Sat May  9 12:52:58 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
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 ubuntu

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

Title:
   i was installing UBUNTU from bootable USB install option on screen
  while testing out UBUNTU.  It ran well. So I tried to install it on
  2nd hard drive that was empty.  Old scsi drive.

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

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

[Bug 1697536] Re: nm strongswan gui doesn't have a way to enter pre-shared key

[Van Stokes, Jr.]

This problem still persist in Ubuntu 18.04

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename:   bionic

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

Title:
  nm strongswan gui doesn't have a way to enter pre-shared key

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

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

[Bug 1867470] [NEW] package linux-image-4.4.0-171-generic 4.4.0-171.200 failed to install/upgrade: package linux-image-4.4.0-171-generic is not ready for configuration cannot configure (current status

[Robert N Hubby Jr]

Public bug reported:

I noticed that on the graphics driver it says that the version on the
driver is the AMD TURKS (DRM 2.43.0 / 4.4.0-173-generic, LLVM 6.0.0). I
noticed that my HDMI audio driver got dropped from sound settings after
running my external sound card, my Cakewalk UA-25EX driver which works
but I lost my HDMI audio driver after unplugging the Cakewalk UA-25EX
sound card. I'm not sure what version of the 16.04 64 bit operating
system but I suspect that the package linux-image 4.40.170 generic but I
am not sure without booting into the recovery mode at start up. Maybe
what is happening is that the computer is trying to either upgrade from
16.04 to 18.04 or just updating programs instead. Either way, I think
that the HDMI audio driver needs to be corrected, re-installed and the
updates need to work again, maybe I need to do more work in the recovery
console like repair broken packages etc.. I will keep you posted on it.
Hopefully, the recovery console will resolve the problems, if not, I
will have to run the terminal and correct the get the updates by using
sudo apt-get update and sudo apt-install upgrade or the like. Feel free
to keep me posted on any solutions that may correct the problems. I
really want to correct the HDMI audio problem. I have a AMD HD Radeon
6570 Video card on a Gateway DX4300 Computer running Ubuntu 16.04. Thank
you very kindly and have a wonderful day!!

I have the Ubuntu Software center version 3.20.5 installed. My current
system is listed as this: 4.4.0-173-generic #203-Ubuntu SMP Wed Jan 15
02:55:01 UTC 2020 x86_64. This information is from the system log. I
wanted to update my system and maybe eventually upgrade from Ubuntu
16.04 to Ubuntu 18.04. I'm happy with Ubuntu 16.04 except there is not
any catalyst control center for my video card to tweak. I wonder why is
the package linux-image 4.4.0.171 generic 4.4.0.171.200 trying to
install if I have the 4.4.0.173 generic version already installed? Maybe
the computer is trying to correct it's self? Feel free to let me know
how to handle this and have a good day!! Also, my computer forgets that
I want to auto-login and creates this crash report each time I startup
my computer. It may be a video driver problem but I am not sure because
my computer should auto-login, instead of me typing in my password every
time I startup my computer. Maybe this startup problem is related to the
loss of the HDMI audio driver but I'm not sure about it. The startup
problem did not occur until after the loss of the HDMI audio driver. I
can try removing my video card and booting up with onboard graphics and
then clearing the improper HDMI video and audio drivers and shut down
and put my video card back in to my computer to see if it refreshes its
self. Maybe that will resolve the HDMI audio problem and resolve the
boot sign in problem as well by refreshing the drivers.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-171-generic 4.4.0-171.200
ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
Uname: Linux 4.4.0-173-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
Date: Sat Mar 14 14:19:28 2020
DpkgHistoryLog:
 Start-Date: 2020-03-14  14:18:18
 Requested-By: alice (1000)
 Upgrade: adobe-flash-properties-gtk:amd64 (1:20200211.1-0ubuntu0.16.04.1, 
1:20200311.1-0ubuntu0.16.04.1), snapd:amd64 (2.40, 2.42.1), libsqlite3-0:amd64 
(3.11.0-1ubuntu1.3, 3.11.0-1ubuntu1.4), libsqlite3-0:i386 (3.11.0-1ubuntu1.3, 
3.11.0-1ubuntu1.4), libarchive13:amd64 (3.1.2-11ubuntu0.16.04.7, 
3.1.2-11ubuntu0.16.04.8), adobe-flashplugin:amd64 
(1:20200211.1-0ubuntu0.16.04.1, 1:20200311.1-0ubuntu0.16.04.1), ppp:amd64 
(2.4.7-1+2ubuntu1.16.04.1, 2.4.7-1+2ubuntu1.16.04.2), firefox-locale-en:amd64 
(72.0.2+build1-0ubuntu0.16.04.1, 74.0+build3-0ubuntu0.16.04.1), 
ubuntu-core-launcher:amd64 (2.40, 2.42.1), unattended-upgrades:amd64 
(1.1ubuntu1.18.04.7~16.04.5, 1.1ubuntu1.18.04.7~16.04.6), firefox:amd64 
(72.0.2+build1-0ubuntu0.16.04.1, 74.0+build3-0ubuntu0.16.04.1), rsync:amd64 
(3.1.1-3ubuntu1.2, 3.1.1-3ubuntu1.3), opera-stable:amd64 (66.0.3515.103, 
67.0.3575.53), teamviewer:amd64 (15.2.2756, 15.3.2682)
DuplicateSignature:
 package:linux-image-4.4.0-171-generic:4.4.0-171.200
 Processing triggers for ureadahead (0.100.0-19.1) ...
 ureadahead will be reprofiled on next reboot
 dpkg: error processing package linux-image-4.4.0-171-generic (--configure):
  package linux-image-4.4.0-171-generic is not ready for configuration
ErrorMessage: package linux-image-4.4.0-171-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
InstallationDate: Installed on 2019-04-17 (332 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: linux-signed
Title: package linux-image-4.4.0-171-generic 4.4.0-171.200 failed to 
install/upgrade: package linux-image-4.4.0-171-generic is not ready for 

[Bug 1858959] [NEW] GRUB failed to install on /dev/sda

[Abdon Morales Jr]

Public bug reported:

grub-install failed to install on /dev/sda

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
Date: Wed Jan  8 18:18:52 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed 
boot=casper quiet splash ---
LiveMediaBuild: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  GRUB failed to install on /dev/sda

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

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

Re: [Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi

[Harry G McGavran Jr]

I finally got a little time to try to search for which package exactly
causes this problem.

I downloaded:

intel-microcode_3.20151106.1_amd64.deb
intel-microcode_3.20190618.0ubuntu0.16.04.1_amd64.deb
intel-microcode_3.20191112-0ubuntu0.16.04.2_amd64.deb
intel-microcode_3.20191115.1ubuntu0.16.04.1_amd64.deb
intel-microcode_3.20191115.1ubuntu0.16.04.2_amd64.deb

I had downgraded to 3.20151106.1, which is working.

So, I tried intel-microcode_3.20190618.0ubuntu0.16.04.1_amd64.deb,
and it worked ok.

So, next I tried intel-microcode_3.20191112-0ubuntu0.16.04.2_amd64.deb,
and it worked ok.

So, Next I tried intel-microcode_3.20191115.1ubuntu0.16.04.1_amd64.deb
and it hangs on warm reboot.

So, next I tried intel-microcode_3.20191112-0ubuntu0.16.04.2_amd64.deb,
and NOW IT hangs on warm reboot.

So, next I tried intel-microcode_3.20190618.0ubuntu0.16.04.1_amd64.deb,
and now IT TOO hangs on warm reboot.

So, Next I tried intel-microcode_3.20151106.1_amd64.deb,
and it works ok --

Unfortunately, I just don't have time to go back one by one through
all the releases between 3.20151106.1 and 3.20190618.0 to
see how far back I need to go before finding where it really would
start working ok again.

I find it very puzzling that the packages all worked until I got
to 3.20191115.1ubuntu0.16.04.1, and then none of them worked
until I backed off all the way to 3.20151106.1.  There must be a clue in
that somewhere.

Good luck, I hope you find it -- I'm staying locked on 3.20151106.1
until this gets fixed...

   Harry


On 12/17/19 12:51 PM, Harry G McGavran Jr wrote:
> 
> 
> On 12/17/19 12:13 PM, Harry G McGavran Jr wrote:
>>
>>
>> On 12/17/19 11:52 AM, Seth Arnold wrote:
>>> Hello Harry,
>>>
>>> Just to double-check, did you perform a *cold* reboot at least once
>>> after installing the 3.20191115.1ubuntu0.16.04.2?
> 
> Meant to respond to this in my first reply...
> 
> The answer to this one is yes.
> 
> The only way I could get the system to come up was with a cold boot as
> well.  This was true for each of the last two microcode releases
> in my update stream.
> 
> Harry
> 
> 
>>>
>>> Can you please provide the output of:
>>>
>>> iucode-tool -S
>>
>> iucode-tool: system has processor(s) with signature 0x00050654
>>
>>>
>>> It might also be helpful to know where exactly the failure started;
>>> previous releases can be found on
>>> https://launchpad.net/ubuntu/xenial/+source/intel-microcode
>>>
>>> (I'm guessing it's probably fastest to just work backwards up the list
>>> rather than bisecting, but that's a guess.)
>>
>> I believe it was a problem with the last two microcode releases for
>> Ubuntu 16.04 LTS.
>>
>> That would be the 3.20191115 and 3.20191112 releases.
>> The 3.20190618 releases and before were ok.
>>
>> Exactly which ones on 3.20191115 and 3.20191112, I don't
>> know without trying them, but the ones in the update stream
>> for Ubuntu 16.04 LTS are the ones where I had trouble.
>>
>>Harry
>>
>>>
>>> Here's the previous bug report for a handy link for navigating among the 
>>> bugs:
>>> https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1854764
>>>
>>> Thanks
>>>

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

Title:
  Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot
  with Intel(R) Xeon(R) W-2125 CPUi

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

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

Re: [Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi

[Harry G McGavran Jr]

On 12/17/19 12:13 PM, Harry G McGavran Jr wrote:
> 
> 
> On 12/17/19 11:52 AM, Seth Arnold wrote:
>> Hello Harry,
>>
>> Just to double-check, did you perform a *cold* reboot at least once
>> after installing the 3.20191115.1ubuntu0.16.04.2?

Meant to respond to this in my first reply...

The answer to this one is yes.

The only way I could get the system to come up was with a cold boot as
well.  This was true for each of the last two microcode releases
in my update stream.

Harry


>>
>> Can you please provide the output of:
>>
>> iucode-tool -S
> 
> iucode-tool: system has processor(s) with signature 0x00050654
> 
>>
>> It might also be helpful to know where exactly the failure started;
>> previous releases can be found on
>> https://launchpad.net/ubuntu/xenial/+source/intel-microcode
>>
>> (I'm guessing it's probably fastest to just work backwards up the list
>> rather than bisecting, but that's a guess.)
> 
> I believe it was a problem with the last two microcode releases for
> Ubuntu 16.04 LTS.
> 
> That would be the 3.20191115 and 3.20191112 releases.
> The 3.20190618 releases and before were ok.
> 
> Exactly which ones on 3.20191115 and 3.20191112, I don't
> know without trying them, but the ones in the update stream
> for Ubuntu 16.04 LTS are the ones where I had trouble.
> 
>Harry
> 
>>
>> Here's the previous bug report for a handy link for navigating among the 
>> bugs:
>> https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1854764
>>
>> Thanks
>>

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

Title:
  Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot
  with Intel(R) Xeon(R) W-2125 CPUi

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

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

Re: [Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi

[Harry G McGavran Jr]

On 12/17/19 11:52 AM, Seth Arnold wrote:
> Hello Harry,
> 
> Just to double-check, did you perform a *cold* reboot at least once
> after installing the 3.20191115.1ubuntu0.16.04.2?
> 
> Can you please provide the output of:
> 
> iucode-tool -S

iucode-tool: system has processor(s) with signature 0x00050654

> 
> It might also be helpful to know where exactly the failure started;
> previous releases can be found on
> https://launchpad.net/ubuntu/xenial/+source/intel-microcode
> 
> (I'm guessing it's probably fastest to just work backwards up the list
> rather than bisecting, but that's a guess.)

I believe it was a problem with the last two microcode releases for
Ubuntu 16.04 LTS.

That would be the 3.20191115 and 3.20191112 releases.
The 3.20190618 releases and before were ok.

Exactly which ones on 3.20191115 and 3.20191112, I don't
know without trying them, but the ones in the update stream
for Ubuntu 16.04 LTS are the ones where I had trouble.

   Harry

> 
> Here's the previous bug report for a handy link for navigating among the bugs:
> https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1854764
> 
> Thanks
>

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

Title:
  Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot
  with Intel(R) Xeon(R) W-2125 CPUi

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

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

[Bug 1855784] [NEW] Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi

[Harry G McGavran Jr]

Public bug reported:

Intel Micorocde 3.20191115.1ubuntu0.16.04.2 STILL hangs on warm reboot
with Dell T5820 and Intel(R) Xeon(R) W-2125 CPU

Reverting to 3.20151106.1 fixes the problem.

Running Ubuntu 16.04 LTS.

** Affects: intel-microcode (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/1855784

Title:
  Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot
  with Intel(R) Xeon(R) W-2125 CPUi

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

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

[Bug 1852850] [NEW] package grub-efi-amd64-signed (not installed) failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1

[Osvaldo Verussa Jr]

Public bug reported:

Don't have indicator

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: grub-efi-amd64-signed (not installed)
ProcVersionSignature: Ubuntu 5.0.0-37.40-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
Date: Wed Nov 13 04:08:23 2019
ErrorMessage: installed grub-efi-amd64-signed package post-installation script 
subprocess returned error exit status 1
Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
RelatedPackageVersions:
 dpkg 1.19.6ubuntu1.2
 apt  1.8.4
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed (not installed) failed to install/upgrade: 
installed grub-efi-amd64-signed package post-installation script subprocess 
returned error exit status 1
UpgradeStatus: Upgraded to disco on 2019-11-13 (3 days ago)

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


** Tags: amd64 apport-package disco

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

Title:
  package grub-efi-amd64-signed (not installed) failed to
  install/upgrade: installed grub-efi-amd64-signed package post-
  installation script subprocess returned error exit status 1

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

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

[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu

[Harry G McGavran Jr]

I haven't been able to find how to set a tag for my post above (#10).
It should have the "verification-done-xenial" tag.

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

Title:
  fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu

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

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

[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu

[Harry G McGavran Jr]

I just installed proposed fwupd 0.8.3 on Xenial.  The "Mismatched XML" issue
disappeared, fwupdmgr found new firmware.  I updated the firmware and everything
seems to work fine. Running fwupdmgr after this process and rebooting seems 
fine too,
no "Mismatched XML"  With the previous version, the "Mismatched XML" issue 
didn't always
happen, but it's been happening the past week or thereabouts.

If this problem returns, I'll post any issues here.

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

Title:
  fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu

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

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

[Bug 1772066] Re: Ubuntu 18.04 Network-Manager-OpenVPN won't connected, worked in 17.10, 17.04

[Carlos Tavares Jr]

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

Any update on this?

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

Title:
  Ubuntu 18.04 Network-Manager-OpenVPN won't connected, worked in 17.10,
  17.04

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

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

[Bug 1829637] [NEW] crash when attempting to install

[Fredrick Capell Jr]

Public bug reported:

Attempting a fresh install of Lubuntu 18.04 LTS on an SSD, choosing the
option "erase disk and install Lubuntu" or somesuch. The drive
previously had an installation of Lubuntu 18.10. I can give you more
complete hardware details on request.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CasperVersion: 1.394
Date: Sat May 18 20:03:33 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/lubuntu.seed 
boot=casper quiet splash ---
LiveMediaBuild: Lubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  crash when attempting to install

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

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

Re: [Bug 1820909] Re: installer crashed after downloading stuff

[Bob McClure, Jr.]

Hi Sebastien,

This is a new Acer AMD A10-based machine with Win 10 on it.  Win
already had four primary partitions on a 1 TB drive.  To make it
dual-boot, I shrunk the main partition to 200 GB, then using fdisk in
the live install DVD created a 1 GB part for /boot and the rest of the
disk for LVM.  From an xterm in the live install disk, I used the LVM
tools to create LVs for root (16 GB), swap (20 GB), home (10 GB), var
(1 GB), and ulocal (for /usr/local, 1 GB).  Then I proceeded with the
normal install.

Later I retried the install without updated packages and it reported
it failed to format the swap LV, gave me an "OK" button which did
nothing.  Had to use the power switch to get out of that.

FWIW, I have downloaded and burned to DVD the 18.04.2 desktop distro
and will try to install with it today.

On Wed, Mar 20, 2019 at 10:00:29AM -, Sebastien Bacher wrote:
> Thank you for your bug report, could you give some details on the type
> of installation/partitionning you did?
> 
> >From the log
> (Mar 19 20:42:24 ubuntu ubiquity: cannot open /target/etc/apt/sources.list: 
> No such file'
> 
> ** Changed in: ubiquity (Ubuntu)
>Importance: Undecided => High
> 
> ** Changed in: ubiquity (Ubuntu)
>Status: New => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1820909
> 
> Title:
>   installer crashed after downloading stuff
> 
> Status in ubiquity package in Ubuntu:
>   Incomplete
> 
> Bug description:
>   It had downloaded updated packages and then crashed.
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: ubiquity 18.04.14
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   Uname: Linux 4.15.0-20-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   CasperVersion: 1.394
>   Date: Tue Mar 19 15:43:51 2019
>   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
> boot=casper only-ubiquity quiet splash ---
>   LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820909/+subscriptions

Cheers,
-- 
Bob McClure, Jr. Bobcat Open Systems, Inc.
b...@bobcatos.com http://www.bobcatos.com
Finally, be strong in the Lord and in his mighty power.
Ephesians 6:10

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

Title:
  installer crashed after downloading stuff

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

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

[Bug 1820909] [NEW] installer crashed after downloading stuff

[Bob McClure, Jr.]

Public bug reported:

It had downloaded updated packages and then crashed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
Date: Tue Mar 19 15:43:51 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  installer crashed after downloading stuff

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

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

[Bug 1820909] Re: installer crashed after downloading stuff

[Bob McClure, Jr.]

will try again without getting updated packages.

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

Title:
  installer crashed after downloading stuff

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

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

[Bug 1819303] [NEW] package grub-pc 2.02-2ubuntu8.12 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1

[Tim Kennell Jr.]

Public bug reported:

upgrade from ubuntu 16.04 to 18.04, automated bug report

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-pc 2.02-2ubuntu8.12
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic i686
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
Date: Sat Mar  9 20:32:07 2019
ErrorMessage: installed grub-pc package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2016-02-09 (1125 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta i386 
(20150805)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/hostname--vg-root ro
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.8
SourcePackage: grub2
Title: package grub-pc 2.02-2ubuntu8.12 failed to install/upgrade: installed 
grub-pc package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago)

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


** Tags: apport-package bionic i386

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

Title:
  package grub-pc 2.02-2ubuntu8.12 failed to install/upgrade: installed
  grub-pc package post-installation script subprocess returned error
  exit status 1

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

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

[Bug 1819272] [NEW] no print from HP Envy 5530

[ARTHUR H WILLIAMS JR]

Public bug reported:

cannot print pdf, except first page through Libre Draw.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cups 2.2.8-5ubuntu1.2
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
CupsErrorLog:
 E [09/Mar/2019:09:19:30 -0500] Unknown directive JobPrivateAccess on line 123 
of /etc/cups/cupsd.conf.
 E [09/Mar/2019:09:19:30 -0500] Unknown directive JobPrivateValues on line 124 
of /etc/cups/cupsd.conf.
 E [09/Mar/2019:09:19:30 -0500] Unknown directive SubscriptionPrivateAccess on 
line 125 of /etc/cups/cupsd.conf.
 E [09/Mar/2019:09:19:30 -0500] Unknown directive SubscriptionPrivateValues on 
line 126 of /etc/cups/cupsd.conf.
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  9 09:43:09 2019
InstallationDate: Installed on 2019-01-07 (61 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lpstat:
 device for CUPS-BRF-Printer: cups-brf:/
 device for ENVY-5530-series: hp:/usb/ENVY_5530_series?serial=CN43I210GS05XT
 device for Generic-CUPS-BRF-Printer: cups-brf:/
MachineType: Dell Inc. Inspiron 5558
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-CUPS-BRF-Printer.ppd', 
'/etc/cups/ppd/ENVY-5530-series.ppd', '/etc/cups/ppd/CUPS-BRF-Printer.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/Generic-CUPS-BRF-Printer.ppd: 
Permission denied
 grep: /etc/cups/ppd/ENVY-5530-series.ppd: Permission denied
 grep: /etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=2916d9f1-41e2-4b63-8b0b-4a8c5fd65a11 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/22/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0FF8N0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd11/22/2016:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn0FF8N0:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5558
dmi.product.sku: Inspiron 5558
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apparmor apport-bug cosmic

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

Title:
  no print from HP Envy 5530

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

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

[Bug 1725779] Re: Gnome network manager cannot find authentication binary

[Carlos Tavares Jr]

I can confirm this is still an issue with ubuntu 18.04. I have both the
network-manager-openvpn and network-manager-openvpn-gnome. The DNS
issues are still an issue on the client side. I know this isn't my
openvpn server (running on pfsense) or config files as the same config
files on Windows and MACOS work and connect with no issues. This needs
to be fixed since, I, the IT guy use Ubuntu 18.04, lol.

Thanks,
Carlos

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

Title:
  Gnome network manager cannot find authentication binary

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

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

[Bug 1772066] Re: Ubuntu 18.04 Network-Manager-OpenVPN won't connected, worked in 17.10, 17.04

[Carlos Tavares Jr]

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

I can confirm this is still an issue with ubuntu 18.04. I have both the
network-manager-openvpn and network-manager-openvpn-gnome. The DNS
issues are still an issue on the client. I know this isn't my openvpn
server (running on pfsense) or config files as the same config files on
Windows and MACOS work and connect with no issues. This needs to be
fixed since, I, the IT guy use Ubuntu 18.04, lol.

Thanks,
Carlos

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

Title:
  Ubuntu 18.04 Network-Manager-OpenVPN won't connected, worked in 17.10,
  17.04

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

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

[Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Herb Miller Jr.]

Is there any hope of this being backported to 16.04? This is a big
problem for our customers running our digital signage players running
16.04. This is a pretty critical bug to leave unaddressed in an LTS that
still has two years of support left.

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

Title:
  Xfce resets TV mode to NULL when power cycled

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

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

[Bug 1816703] [NEW] fuck

[Nicholas J. Linden Jr.]

Public bug reported:

i dont know

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompositorRunning: None
Date: Wed Feb 20 01:03:43 2019
DistUpgraded: 2018-11-03 00:06:35,514 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:221e]
 NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GK107GLM [Quadro K1100M] [17aa:221e]
InstallationDate: Installed on 2017-06-08 (621 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20EGS2Y100
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=634836b3-fbce-46ef-a204-02830b05eb59 ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-11-03 (109 days ago)
dmi.bios.date: 09/01/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: GNET75WW (2.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EGS2Y100
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGNET75WW(2.23):bd09/01/2015:svnLENOVO:pn20EGS2Y100:pvrThinkPadW541:rvnLENOVO:rn20EGS2Y100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad W541
dmi.product.name: 20EGS2Y100
dmi.product.version: ThinkPad W541
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Fri Nov  2 22:48:29 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5571 
 vendor CMN
xserver.version: 2:1.18.4-0ubuntu0.8

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


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

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

Title:
  fuck

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

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

[Bug 1797715] Re: Libvirt kvm windows guest has no network after upgrade to 18.10

[JR]

Hi Christian,
I did some further testing with the network interfaces, and I can report:
* networking in bridged mode (macvtap) with my ethernet device works as desired
* networking in bridged mode (macvtap) with my wifi device does *not* work
* networking in nat mode does not work on any of my devices (this is what I 
always used)

still, as said earlier, ping in nat mode does work, but everything else
I tested does not.

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

Title:
  Libvirt kvm windows guest has no network after upgrade to 18.10

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

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

[Bug 1800953] [NEW] driver does not control resolution

[John Broxson Jr.]

Public bug reported:

driver does not control resolutiondriver does not control resolution

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Wed Oct 31 18:27:58 2018
DuplicateSignature:
 package:nvidia-340:(not installed)
 Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-dtgsIS/3-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb 
(--unpack):
  trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is 
also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
InstallationDate: Installed on 2018-10-30 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 (not installed) failed to install/upgrade: trying to 
overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic package-conflict

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

Title:
  driver does not control resolution

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

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

[Bug 1797715] Re: Libvirt kvm windows guest has no network after upgrade to 18.10

[JR]

As I had too much network interfaces, I uninstalled the lxc package
which I didn't use anyway. Then I removed the recently created network
to have everything as simple as possible. As this didn't help at all I
configured the IPv4 address statically (in the guest). I must have
screwed something up the last time, because after I did this, I was able
to ping the guest vm from my host (yay). I'm now also able to ping the
host from the guest vm and everything else (even hosts like 8.8.8.8 -
even tracert in windows works).

BUT: only ping seems to work. I cannot resolve names inside my guest, no
matter which DNS server I configure. I also tried opening a webpage via
IP in my local net - this doesn't work either. I have no idea what could
cause everything but ICPM working...

$ iptables -L -nv
Chain INPUT (policy ACCEPT 315 packets, 63571 bytes)
 pkts bytes target prot opt in out source   destination 

0 0 ACCEPT udp  --  virbr0 *   0.0.0.0/00.0.0.0/0   
 udp dpt:53
0 0 ACCEPT tcp  --  virbr0 *   0.0.0.0/00.0.0.0/0   
 tcp dpt:53
0 0 ACCEPT udp  --  virbr0 *   0.0.0.0/00.0.0.0/0   
 udp dpt:67
0 0 ACCEPT tcp  --  virbr0 *   0.0.0.0/00.0.0.0/0   
 tcp dpt:67

Chain FORWARD (policy ACCEPT 39 packets, 2794 bytes)
 pkts bytes target prot opt in out source   destination 

9   540 ACCEPT all  --  *  virbr0  0.0.0.0/0
192.168.122.0/24 ctstate RELATED,ESTABLISHED
  160 10888 ACCEPT all  --  virbr0 *   192.168.122.0/24 0.0.0.0/0   

0 0 ACCEPT all  --  virbr0 virbr0  0.0.0.0/00.0.0.0/0   

0 0 REJECT all  --  *  virbr0  0.0.0.0/00.0.0.0/0   
 reject-with icmp-port-unreachable
0 0 REJECT all  --  virbr0 *   0.0.0.0/00.0.0.0/0   
 reject-with icmp-port-unreachable

Chain OUTPUT (policy ACCEPT 427 packets, 58983 bytes)
 pkts bytes target prot opt in out source   destination 

0 0 ACCEPT udp  --  *  virbr0  0.0.0.0/00.0.0.0/0   
 udp dpt:68

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

Title:
  Libvirt kvm windows guest has no network after upgrade to 18.10

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

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

[Bug 1797715] Re: Libvirt kvm windows guest has no network after upgrade to 18.10

[JR]

I just created a 2nd network, and when looking at some numbers, I just
found out, that the RX packets of virbr1 and vnet1 exactly match the
number of TX packets inside the guest vm. The guest vm shows 0 RX
packets, while the vnet1 device shows 207 packets. The virbr[01]-nic
devices have no RX/TX packets at all.

not sure if this is of any help

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

Title:
  Libvirt kvm windows guest has no network after upgrade to 18.10

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

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

[Bug 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

[JR]

I just 'resolved' that issue myself by removing the package timidity -
it seems this program exclusively used the audio hardware. If there is a
issue, it is with this package.

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

Title:
  [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta

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

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

[Bug 1797715] Re: Libvirt kvm windows guest has no network after upgrade to 18.10

[JR]

the vm was started around 21:00, the log starts a minute earlier

** Attachment added: "the libvirt logfile extracted from journalctl"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1797715/+attachment/5202671/+files/libvirtd.log.gz

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

Title:
  Libvirt kvm windows guest has no network after upgrade to 18.10

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

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

[Bug 1797715] Re: Libvirt kvm windows guest has no network after upgrade to 18.10

[JR]

Hi Christian,
today I upgraded another Kubuntu to the current 18.10 - and everything worked 
as desired. The only thing I had to do on both systems was to change the 
machine type to 'pc-i144fx-cosmic' (on both systems it was a 
pc-i144fx-something' that went away)

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

Title:
  Libvirt kvm windows guest has no network after upgrade to 18.10

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

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

[Bug 1797715] Re: Libvirt kvm windows guest has no network after upgrade to 18.10

[JR]

$ ps axlf | grep dnsmasq
5   135  2533 1  20   0  27668   368 -  S?  0:00 
/usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf 
--leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
1 0  2535  2533  20   0  27640   368 -  S?  0:00  \_ 
/usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf 
--leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
5   131  2820 1  20   0  33564   388 -  S?  0:00 dnsmasq -u 
lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid 
--listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 
--dhcp-no-override --except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative


$ sudo cat /var/lib/libvirt/dnsmasq/default.conf
##WARNING:  THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
##OVERWRITTEN AND LOST.  Changes to this configuration should be made using:
##virsh net-edit default
## or other application using the libvirt API.
##
## dnsmasq conf file created by libvirt
strict-order
user=libvirt-dnsmasq
pid-file=/var/run/libvirt/network/default.pid
except-interface=lo
bind-dynamic
interface=virbr0
dhcp-range=192.168.122.2,192.168.122.254
dhcp-no-override
dhcp-authoritative
dhcp-lease-max=253
dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts


I also started the arch linux live cd, but the installer didn't get a address 
via dhcp, so it doesn't appear to be a a windows guest issue.
I also checked the iptables rules, I even removed them but it didn't help.

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

Title:
  Libvirt kvm windows guest has no network after upgrade to 18.10

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

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

[Bug 1797715] Re: Libvirt kvm windows guest has no network after upgrade to 18.10

[JR]

  
  
  
  

 

$ virsh net-info default
Name:   default
UUID:   5db32803-fd1e-4876-98d8-da194f535c17
Active: yes
Persistent: yes
Autostart:  yes
Bridge: virbr0


$ virsh net-dumpxml default

  default
  5db32803-fd1e-4876-98d8-da194f535c17
  

  

  
  
  
  

  

  



from the journal:
Okt 15 17:18:06 juergen kernel: virbr0: port 2(vnet0) entered blocking state
Okt 15 17:18:06 juergen kernel: virbr0: port 2(vnet0) entered disabled state
Okt 15 17:18:06 juergen kernel: device vnet0 entered promiscuous mode
Okt 15 17:18:06 juergen kernel: virbr0: port 2(vnet0) entered blocking state
Okt 15 17:18:06 juergen kernel: virbr0: port 2(vnet0) entered listening state
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7302] 
manager: (vnet0): new Tun device (/org/freedesktop/NetworkManager/Devices/8)
Okt 15 17:18:06 juergen systemd-udevd[7327]: link_config: autonegotiation is 
unset or enabled, the speed and duplex are not writable.
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7453] devices 
added (path: /sys/devices/virtual/net/vnet0, iface: vnet0)
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7454] device 
added (path: /sys/devices/virtual/net/vnet0, iface: vnet0): no ifupdown 
configuration found.
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7470] device 
(vnet0): state change: unmanaged -> unavailable (reason 'connection-assumed', 
sys-iface-state: 'external')
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7513] 
keyfile: add connection in-memory (697f6001-f8b1-4acc-bc69-b562c78a1372,"vnet0")
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7546] device 
(vnet0): state change: unavailable -> disconnected (reason 
'connection-assumed', sys-iface-state: 'external')
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7570] device 
(vnet0): Activation: starting connection 'vnet0' 
(697f6001-f8b1-4acc-bc69-b562c78a1372)
Okt 15 17:18:06 juergen libvirtd[1706]: 2018-10-15 15:18:06.757+: 1776: 
error : virNetDevSendEthtoolIoctl:3071 : ethtool ioctl error: No such device
Okt 15 17:18:06 juergen libvirtd[1706]: 2018-10-15 15:18:06.758+: 1776: 
error : virNetDevSendEthtoolIoctl:3071 : ethtool ioctl error: No such device
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7576] device 
(vnet0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 
'external')
Okt 15 17:18:06 juergen libvirtd[1706]: 2018-10-15 15:18:06.758+: 1776: 
error : virNetDevSendEthtoolIoctl:3071 : ethtool ioctl error: No such device
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7588] device 
(vnet0): state change: prepare -> config (reason 'none', sys-iface-state: 
'external')
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7595] device 
(vnet0): state change: config -> ip-config (reason 'none', sys-iface-state: 
'external')
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7600] device 
(virbr0): bridge port vnet0 was attached
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7600] device 
(vnet0): Activation: connection 'vnet0' enslaved, continuing activation
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7605] device 
(vnet0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 
'external')
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7622] device 
(vnet0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 
'external')
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7627] device 
(vnet0): state change: secondaries -> activated (reason 'none', 
sys-iface-state: 'external')
Okt 15 17:18:06 juergen NetworkManager[1653]:   [1539616686.7787] device 
(vnet0): Activation: successful, device activated.


the virbr0.status file stays 'empty', the virbr0.macs file contains:
[
  {
"domain": "win7",
"macs": [
  "52:54:00:41:51:b4"
]
  }
]


hth,
Jürgen

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

Title:
  Libvirt kvm windows guest has no network after upgrade to 18.10

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

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

[Bug 1797715] [NEW] Libvirt kvm windows guest has no network after upgrade to 18.10

[JR]

Public bug reported:

Today I upgraded to 18.10 beta and now my windows guest doesn't have
network. The network is configured to NAT. The network card is of course
shown in the guest, but it doesn't get an IP via dhcp. Even configuring
a static IP doesn't help - the same network IP of the host is not
reachable from the guest.

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

** Package changed: pulseaudio (Ubuntu) => libvirt (Ubuntu)

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

Title:
  Libvirt kvm windows guest has no network after upgrade to 18.10

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

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

[Bug 1797714] [NEW] No sound after upgrade to Kubuntu 18.10 beta

[JR]

Public bug reported:

I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have 
sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa 
force-reload', KDE shows the audio device.
When I execute alsamixer in a shell before executing the force-reload, the 
audio card is shown.

My hardware: (from lspci)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High 
Definition Audio (rev 05)

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: pulseaudio 1:12.2-0ubuntu4
Uname: Linux 4.19.0-041900rc6-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  juergen8924 F pulseaudio
 /dev/snd/controlC1:  juergen8924 F pulseaudio
CurrentDesktop: KDE
Date: Sat Oct 13 21:07:53 2018
InstallationDate: Installed on 2015-02-16 (1334 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago)
dmi.bios.date: 10/06/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0KM426
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A02
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02:
dmi.product.name: Studio 1557
dmi.product.version: A02
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug cosmic

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

Title:
  No sound after upgrade to Kubuntu 18.10 beta

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

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

[Bug 1796895] Re: Kernel 4.15.0-36 network performance regression

[Van Stokes, Jr.]

We had a similar issue with our MySQL server farm (seven dedicated MySQL
servers). Replication was very slow, falling behind for no apparent
reason. We were reaching 24 hours of lag! We never had that kind of lag
before. A couple of minutes at the most.

Long story short, we rebooted to 4.15.0.34 and the servers caught up
replication with in minutes!

References:
https://forums.mysql.com/read.php?26,669517
https://askubuntu.com/questions/1080911/linux-image-4-15-0-36-reduces-rsync-over-ssh-to-10-times-less/1082322#1082322

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

Title:
  Kernel 4.15.0-36 network performance regression

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

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

[Bug 1795500] [NEW] konsole crashed on shutdown

[JR]

Public bug reported:

Happened on shutdown.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: konsole 4:17.12.3-1ubuntu1
Uname: Linux 4.18.8-041808-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Oct  1 21:47:31 2018
InstallationDate: Installed on 2015-02-16 (1323 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
SourcePackage: konsole
UpgradeStatus: Upgraded to bionic on 2018-03-21 (194 days ago)

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


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

** Attachment added: "crash report"
   
https://bugs.launchpad.net/bugs/1795500/+attachment/5195450/+files/konsole-20181001-194140.kcrash.txt

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

Title:
  konsole crashed on shutdown

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

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

[Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.0

[Robert L Wilcox Jr]

This also fixed it for me.

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

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also
  in package nvidia-340 340.107-0ubuntu0~gpu18.04.1

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

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

Re: [Bug 1792802] Re: HP G7 Laptop Display rotated without input.. cannot open the display settings to rotate back to horizontal

[L R Bellmore Jr (Bob)]

Thank you Gunnar.. but the rotation occurred while I was watching a 
video streaming program.  I had not touched the keyboard.  Then 
following the instructions to change the rotation, the actual screen 
allowing me to do so would not open... never did after 5 or more tries. 
It just looped back to instructions.

Bob


*L R (Bob) Bellmore Jr*
1685 RTE 405 HWY, PO BOX 211
HUGHESVILLE, PA 17737
(cell) 570-337-7501
(email) lrbellmor...@gmail.com

On 9/16/2018 11:58 AM, Gunnar Hjalmarsson wrote:
> You have filed a bug against the desktop documentation, but what you
> write has nothing to do with that. Apparently you are seeking support,
> so I recommend you to try at e.g. <https://askubuntu.com>.
>
> Closing this bug report.
>
> ** Changed in: ubuntu-docs (Ubuntu)
> Status: New => Invalid
>

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

Title:
  HP G7 Laptop Display rotated without input.. cannot open the display
  settings to rotate back to horizontal

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

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

Re: [Bug 1792802] Re: HP G7 Laptop Display rotated without input.. cannot open the display settings to rotate back to horizontal

[L R Bellmore Jr (Bob)]

IT IS A BUG...


*L R (Bob) Bellmore Jr*
1685 RTE 405 HWY, PO BOX 211
HUGHESVILLE, PA 17737
(cell) 570-337-7501
(email) lrbellmor...@gmail.com

On 9/16/2018 11:58 AM, Gunnar Hjalmarsson wrote:
> You have filed a bug against the desktop documentation, but what you
> write has nothing to do with that. Apparently you are seeking support,
> so I recommend you to try at e.g. <https://askubuntu.com>.
>
> Closing this bug report.
>
> ** Changed in: ubuntu-docs (Ubuntu)
> Status: New => Invalid
>

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

Title:
  HP G7 Laptop Display rotated without input.. cannot open the display
  settings to rotate back to horizontal

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

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

[Bug 1792802] Re: HP G7 Laptop Display rotated without input.. cannot open the display settings to rotate back to horizontal

[L R Bellmore Jr (Bob)]

I am communicating from my W10 HP i7 laptop which is my main laptop
because we have one software program that must and only runs on Windows.
It is critical to our licensing/business.  The HP g7 laptop is a backup
running Ubuntu.  I would prefer to have all my office computer systems
on Ubuntu but I have one program that will only run on Windows.  I have
not tried it in a virtual machine yet.  That is next step for trying to
transition to Ubuntu completely.  I have 3 desktops and 1 laptop running
W10 and this laptop on W10 because of the one software program that I
need for business production.  I can't run it on the Ubuntu laptop.
There are major suppliers who run the specific software on virtual
machines but you must be a high volume user of the software to afford
their virtual systems running this sofware... so I am stuck with
Windows.

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

Title:
  HP G7 Laptop Display rotated without input.. cannot open the display
  settings to rotate back to horizontal

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

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

[Bug 1792802] Re: HP G7 Laptop Display rotated without input.. cannot open the display settings to rotate back to horizontal

[L R Bellmore Jr (Bob)]

I note importance undecided... well it is extremely important to me.. this is a 
computer used for business.  It backs up my other laptop which is running 
windows 10.. which I also detest.  I love Linux/Ubuntu except for these 
hazards.  I should never be an early adopter.
L R Bellmore Jr

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

Title:
  HP G7 Laptop Display rotated without input.. cannot open the display
  settings to rotate back to horizontal

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

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

[Bug 1792802] Re: HP G7 Laptop Display rotated without input.. cannot open the display settings to rotate back to horizontal

[L R Bellmore Jr (Bob)]

OH, and the cursor doesn't like the rotation either.. very difficult to
control it.

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

Title:
  HP G7 Laptop Display rotated without input.. cannot open the display
  settings to rotate back to horizontal

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

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