[Bug 1900722] Re: Reinstall Ubuntu fails with an existing ESP

2020-10-25 Thread Thomas Szymczak
Here is the workaround I employed:
1. Open the Disks app to determine which partition is the EFI partition. It 
will be labeled "EFI System" under "Partition type."
1. Instead of selecting "reinstall" and getting an error, select "something 
else" to get manual partitioning.
2. Make sure the partition that previously had Ubuntu on it is used, will be 
mounted at /, and will not be formatted.
3. Select that partition, click the "Change..." button and set "Use as" to "EFI 
System Partition" in the dialog box that pops up.
4. Click "Install Now." There should not be any error about the EFI partition 
not being found.

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

Title:
  Reinstall Ubuntu fails with an existing ESP

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

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

[Bug 1900722] Re: Reinstall Ubuntu fails with an existing ESP

2020-10-23 Thread Thomas Szymczak
I am also affected on 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/1900722

Title:
  Reinstall Ubuntu fails with an existing ESP

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

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

[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

2020-07-25 Thread Thomas Szymczak
I've discovered some useful info about this bug. First, there's a forum
thread about it with lots of good info: https://ubuntu-
mate.community/t/20-04-display-issues-with-amd-gpu/21648/37

Second, a new workaround. To recap, the first workaround I found was
booting with nomodeset, but that disables all hardware acceleration. The
new workaround, as detailed in the forum thread, is to open MATE Tweak,
and in the Windows tab, change the window manager to Marco (no
compositor).

Third, we found the upstream bug in xf86-video-amdgpu:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10
. I believe this is packaged as xserver-xorg-video-amdgpu in Ubuntu.
It's been fixed upstream and the Ubuntu Mate devs will include it in
20.04.1 is possible.

Fourth, bug #1873895 appears to be the same bug, but originally reported
as manifesting in Xubuntu. Maybe this is a duplicate.

** Bug watch added: 
gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues #10
   https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10

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

Title:
  [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

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

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

[Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

2020-06-15 Thread Thomas Szymczak
Today I had some more time to play around with my computer so I tried
testing your hypothesis. I rebooted into my current software
configuration with no workarounds as a control, and reproduced the bug
as expected. Then I downgraded my system to the Marco version from 19.10
(1.22.3) by downloading it from the Ubuntu packages site, along with the
necessary versions of libmarco-private2 and marco-common. Then I
installed the .deb's with dpkg, and rebooted. The bug was still
triggered so perhaps that suggests it's not a bug in Marco? Anything
else I could try testing to narrow it down? Obviously it's confusing
because GNOME doesn't trigger it, but Marco seems to regardless of
version.

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

Title:
  [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

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

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

[Bug 1882525] Re: [amdgpu] Display is corrupted upon login on Ryzen APU

2020-06-09 Thread Thomas Szymczak
Now this is where it gets weird. Since I have Ubuntu MATE, I installed
the ubuntu-desktop package to get the default GNOME environment. I kept
my display manager as LightDM in case that's relevant.

Then I rebooted and tested all 3 desktop modes with default kernel
options. As expected, MATE is still broken. I rebooted and tried "Ubuntu
(Default)" and there were no issues whatsoever. I opened a few apps and
all of them displayed OK, and used inxi -G to verify that the display
server was indeed X. I rebooted again to test "Ubuntu on Wayland" and it
behaved as expected too. Whatever's going wrong, it's limited to MATE,
as even GNOME on X is fine.

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

Title:
  [amdgpu] Display is corrupted upon login on Ryzen APU

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

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

[Bug 1882525] Re: Display is corrupted upon login on Ryzen APU

2020-06-08 Thread Thomas Szymczak
A quick update. I tested to see if kernel version affects this bug, and
it appears not to. I booted up the previous installed kernel on my
system (5.3.0-55) without the default options and got the exact same
issue. Likewise, using the old kernel with nomodeset eliminates the
corruption at the expense of hardware acceleration (inxi -G says my
renderer is llvmpipe). As I didn't have this issue using that kernel on
19.10, I believe this points to something in the userspace that was
updated when I went to 20.04.

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

Title:
  Display is corrupted upon login on Ryzen APU

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

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

[Bug 1882525] [NEW] Display is corrupted upon login on Ryzen APU

2020-06-08 Thread Thomas Szymczak
Public bug reported:

Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu boots 
normally to the display manager (login screen) as expected. But once I log in, 
everything on the screen is cut up into horizontal slices, with each slice 
offset farther right than the slice above, and squares of random colors running 
diagonally across the screen. I've attached a picture of my monitor showing the 
issue for reference.
My hardware is a home-built PC with an ASUS Prime B450M motherboard, a Ryzen 3 
2200G APU, and using that APU's integrated graphics.
In terms of software I'm running Ubuntu 20.04, which I just upgraded to and did 
a software update on. I have Linux 5.4.0-33-generic, X.Org 1.20.8, and Mesa 
20.0.4. Before I upgraded Ubuntu, I was affected by Bug #1880041 but it seems 
fixed in the new kernel. I don't believe they're related but I figure it's 
worth mentioning.
I tried adding the nomodeset kernel option at boot, and it's an effective 
workaround. Also, I tried booting from an Ubuntu Mate 20.04 live USB to see if 
this was caused by some quirk of my particular software setup, and successfully 
reproduced the bug, proving it wasn't.
If you'd like me to, I can provide log files, system information, etc. or help 
narrow it down by testing workarounds.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-core 2:1.20.8-2ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Mon Jun  8 06:41:47 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon 
Vega Mobile Series] [1043:876b]
InstallationDate: Installed on 2019-10-20 (231 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: System manufacturer System Product Name
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=43189257-cc94-4e98-ac1d-e16336dd152e ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2006
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B450M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
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 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
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-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "Photo of screen corruption"
   
https://bugs.launchpad.net/bugs/1882525/+attachment/5381613/+files/display-issue.jpg

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

Title:
  Display is corrupted upon login on Ryzen APU

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

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