Public bug reported:
Very simple to repro.
Starting Xubuntu 20.04 (bug still present in 22.04):
1. Open rhythmbox
2. Hit Ctrl+Q (Quit) or Ctrl+W (Close window)
3. Nothing happens
This was working fine in Xubuntu 18.04
This bug can be reproduced in the Live USB version (i.e. "Try Xubuntu")
Public bug reported:
After upgrading to Ubuntu 20.04 apt-cacher-ng started to behave
erratically.
Trying to do `apt update` would randomly throw errors such as:
Err:20 https://repo.skype.com/deb stable InRelease
This bug is related to
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1928244
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811
Kernel 5.13 can be compiled in one of the two ways:
1. Use dwarves 1.21, which needs Ubuntu 21.04 and breaks installation for
older
As a workaround you can try booting with "amdgpu.dc=0"
Although I don't know if Vega supports disabling DC.
With DC disabled, the GPU cannot know if your monitor has been turned off.
Another possible solution is to use an SSH session to try to restore
your monitor, typing:
DISPLAY=:0.0 xrandr
This bug should be marked as CRITICAL and be fixed ASAP. It's preventing
automatic security upgrades.
Hopefully this was a mistake by a packager, but investigation should be made in
order to check this isn't a Supply Chain Attack
More info on apt output:
Reading package lists... Done
Public bug reported:
Description:Ubuntu 18.04.5 LTS
In kernel 5.4.0-51 (known good: 5.4.0-48), resuming from suspend results
in the monitors not turning up and the keyboard locked up. However the
system still responds to SSH sessions.
- The bug sometimes also triggers when plugging or
I can also confirm 5.3.0-59 fixed the bug on my HW as well.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux-meta-hwe (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi,
I'm just passing by.
Regarding amdgpu issues related with Ryzen / Vega iGPU, there are a
couple steps you can try:
1. Try a newer firmware blob. Download e.g.
1a. Download the latest firmware and unpack it
*** This bug is a duplicate of bug 1880041 ***
https://bugs.launchpad.net/bugs/1880041
** This bug is no longer a duplicate of bug 1879807
5.3.0-53 Kernel system falis to reboot after install
** This bug has been marked a duplicate of bug 1880041
Failing to shutdown/power off or reboot
*** This bug is a duplicate of bug 1880041 ***
https://bugs.launchpad.net/bugs/1880041
** This bug has been marked a duplicate of bug 1880041
Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions
5.3.0-52 and later
--
You received this bug notification because you
*** This bug is a duplicate of bug 1880041 ***
https://bugs.launchpad.net/bugs/1880041
** This bug is no longer a duplicate of bug 1879807
5.3.0-53 Kernel system falis to reboot after install
** This bug has been marked a duplicate of bug 1880041
Failing to shutdown/power off or reboot
*** This bug is a duplicate of bug 1880041 ***
https://bugs.launchpad.net/bugs/1880041
** This bug is no longer a duplicate of bug 1879807
5.3.0-53 Kernel system falis to reboot after install
** This bug has been marked a duplicate of bug 1880041
Failing to shutdown/power off or reboot
*** This bug is a duplicate of bug 1880041 ***
https://bugs.launchpad.net/bugs/1880041
** This bug is no longer a duplicate of bug 1879807
5.3.0-53 Kernel system falis to reboot after install
** This bug has been marked a duplicate of bug 1880041
Failing to shutdown/power off or reboot
** Also affects: libdrm (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/1880041
Title:
Failing to shutdown/power off or reboot on AMD Ryzen CPUs
** Also affects: dri via
https://gitlab.freedesktop.org/drm/amd/-/issues/1094
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880041
Title:
Failing
*** This bug is a duplicate of bug 1880041 ***
https://bugs.launchpad.net/bugs/1880041
** This bug has been marked a duplicate of bug 1880041
Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions
5.3.0-52 and later
--
You received this bug notification because you
This series of patches broke:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-
hwe/+bug/1880041/comments/19
Commit
drm/amdgpu: fix gfx hang during suspend with video playback (v2)
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=6ad2b975986441870a9a67051f9571b5c09c2569
[BISECTED], FOUND
After bisecting, I found the troublesome commit:
drm/amdgpu: fix gfx hang during suspend with video playback (v2)
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=6ad2b975986441870a9a67051f9571b5c09c2569
This problem is known and already has a bugfix in
Try installing the latest firmware from git:
1. Make a backup of /lib/firmware
2. Download the latest firmware package e.g.
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20200519.tar.gz
3. Unzip it
4. sudo make install
5. Reboot your system
*** This bug is a duplicate of bug 1880041 ***
https://bugs.launchpad.net/bugs/1880041
** This bug has been marked a duplicate of bug 1880041
Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions
5.3.0-52 and later
--
You received this bug notification because you
*** This bug is a duplicate of bug 1880041 ***
https://bugs.launchpad.net/bugs/1880041
** This bug has been marked a duplicate of bug 1880041
Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions
5.3.0-52 and later
--
You received this bug notification because you
*** This bug is a duplicate of bug 1880041 ***
https://bugs.launchpad.net/bugs/1880041
** This bug has been marked a duplicate of bug 1880041
Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions
5.3.0-52 and later
--
You received this bug notification because you
*** This bug is a duplicate of bug 1880041 ***
https://bugs.launchpad.net/bugs/1880041
** This bug has been marked a duplicate of bug 1880041
Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions
5.3.0-52 and later
--
You received this bug notification because you
Duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-meta-
hwe/+bug/1880041
Please pass there by and select that you're affected too so it gets more
attention.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
But is still present as of package linux-meta-hwe (5.3.0.53.110) bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880041
Title:
Failing to shutdown/power off or reboot on AMD Ryzen CPUs on
Duplicate tickets:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1880425
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041
Possibly duplicate (unsure):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185
--
You received this bug notification
Duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-meta-
hwe/+bug/1880041
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880041
Title:
Failing to shutdown/power off or reboot on AMD Ryzen
Same. I reported it as https://bugs.launchpad.net/ubuntu/+source/linux-
signed-hwe/+bug/1880425
and I just noticed this bug report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880041
Title:
Please marks this as duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041
I only just found it after reporting
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880425
Public bug reported:
Last known good: 5.3.0-51
Last known bad: 5.3.0-53
System:
Laptop
Ryzen 2500U 8GB RAM
Lenovo ideapad 330-15 ARR
Description:Ubuntu 18.04.4 LTS
Release:18.04
apt-cache policy linux-image-5.3.0-53
linux-image-5.3.0-53-generic:
Installed: 5.3.0-53.47~18.04.1
You mean bisecting the git commits from mainline linux-firmware; compare
it against https://kernel.ubuntu.com/git/ubuntu/linux-
firmware.git/log/?h=bionic until I isolate the culprit(s)?
Yes I can do that. It will take a while though (laptop needs to reboot
with every attempt, it may take a while
** Attachment added: "uname.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+attachment/5305900/+files/uname.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852857
Public bug reported:
I own a:
CPU: AMD Ryzen 5 2500U
GPU: AMD Raven Ridge (Vega 8)
Laptop model: Lenovo IdeaPad 330S (330S-15ARR)
Description:Ubuntu 18.04.3 LTS
Release:18.04
linux-firmware:
Installed: 1.173.12
Candidate: 1.173.12
Version table:
*** 1.173.12 500
500
This bug started in Slack 3.4.0 and affects Xubuntu 18.04.2 LTS too.
The problem happens because xfwm4 looks for any of the following:
"_NET_WM_WINDOW_TYPE_DESKTOP",
"_NET_WM_WINDOW_TYPE_DIALOG",
"_NET_WM_WINDOW_TYPE_DOCK",
"_NET_WM_WINDOW_TYPE_MENU",
"_NET_WM_WINDOW_TYPE_NORMAL",
I'm attaching .deb and .ddeb (debug symbols) files I built myself if
someone's too lazy or too busy to rebuild the patched xfwm4 him/herself.
It has been working fine for me so far.
USE THEM AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR WHAT HAPPENS IF YOU
TRY THEM.
** Attachment added: "Built deb
Sorry my bad, the diff is reversed. Use the following commands instead:
mkdir tmp
cd tmp
sudo apt install devscripts build-essential fakeroot dpkg-dev
sudo apt-get build-dep xfwm4
apt-get source xfwm4
cd xfwm4-4.12.5
patch -R -p1 -i xfwm4_slack_fix.diff # !!! Point it
Found upstream discussion: https://forum.xfce.org/viewtopic.php?id=12138
Apparently the problem is caused because xfce4-power-manager migrated to
upower, which has only empty, caution, low, good, and full icon themes.
That's 3 states + a caution + empty. IMO that's too few.
And yes, the icon
More related discussion:
https://bbs.archlinux.org/viewtopic.php?pid=1651514#p1651514
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767560
Title:
Battery graph in tray icon is inaccurate
To
I'm not fully certain. It appears like a theme specific bug, but it
doesn't seem like the new xfce4-power-manager icon is using the theme's
icons, but rather its own internal, or perhaps I'm looking at the wrong
place.
--
You received this bug notification because you are a member of Ubuntu
Try the following:
xrandr --output DVI-D-0 --set TearFree 1
You may need a different output e.g. HDMI-A-0
You can list your outputs by just running "xrandr"
Apply the TearFree option to all of your monitors and try again
--
You received this bug notification because you are a member of Ubuntu
This bug affects Xubuntu 18.04 but not 17.xx or earlier
It can be easily be reproduced on any desktop machine using
https://github.com/hoelzro/linux-fake-battery-module (patch to compile
on Xubuntu 18.04 is at the end)
I can see that:
In the range [60; 100] the full battery icon is displayed
In
I forgot. If after executing those commands now update-manager gets
permanently stuck on "waiting for other software managers to quit"
(which is kept stuck even after removing the locks in all apt places and
closing all software managers), then run:
sudo apt install --reinstall update-manager
--
I was having this same bug and I managed to "fix" it by deleting
everything under /var/lib/apt
i.e. sudo apt rm -rf /var/lib/apt/
Then run "sudo apt update" and reboot the system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug affects yakkety yak but I don't see an update for that
platform.
Am I wrong or this was missed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661842
Title:
gstreamer 1.8.3 incorrectly
I can confirm this bug still persists in latest package 304.134 on
XUbuntu 16.04 LTS.
The card is nForce 6150SE
OpenGL does not work, but I can login to xfce because it does not need a
compositor.
Version 304.131 works OK. It was listed in aptitude for some reason, so
I could just downgrade.
I
+1 to ask for a backport to 14.04. It's getting pretty annoying.
It happens every time I plug my iPad Mini 3 to the USB; it gets worst if
the system boots with the iPad already plugged ("System problem
detected" will show up as soon as I'm logged in, my screen resolution
will be wrong, then goes
Same problem here.
Intel Quad Core QX9650 @3Ghz
Motherboard ASUS P5Q-E
4GB RAM
CPU Scaling works in Windows.
Tried acpi-cpufreq powernow-k8 speedstep-centrino all of them just in case,
with same result
uname -r
2.6.26-2-amd64
lsmod:
Module Size Used by
nvidia
Ooops. I'm a bit ashamed.
I'm still wondering how it works in Windows though.
After more researching I had C1E (Enhanced Halt State) enabled BUT Intel
SpeedStep disabled in the BIOS. After enabling it, cpu freq scaling started
working and the modprobe was done automatically on boot (using
48 matches
Mail list logo