[Bug 1852857] Re: Use more modern Raven Ridge firmware in linux-firmware package
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 to crash, etc) Does anyone know if: service lightdm stop rmmod amdgpu modprobe amdgpu service lightdm start will reupload the firmware blob? That would speed up the testing process tremendously. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852857 Title: Use more modern Raven Ridge firmware in linux-firmware package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852857] Re: Use more modern Raven Ridge firmware in linux-firmware package
** 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 Title: Use more modern Raven Ridge firmware in linux-firmware package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852857] [NEW] Use more modern Raven Ridge firmware in linux-firmware package
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 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 100 /var/lib/dpkg/status 1.173 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The firmware provided by Ubuntu 18.04 is too old and causes frequent system freezes, particularly when using the web browser. When it freezes, the mouse is the only thing that works, but the GPU gets completely locked up. Keyboard also gets locked up (even Num Lock doesn't respond). There are no crash reports automatically generated. The logs get corrupted so it's impossible to know what happened. Updating it to a new firmware version fixes all freezes and system stability becomes rock solid. I'm not sure which exactly is the relevant firmware file, but I'm using these: fe5ec673b44d95c686a240a8d138f499 raven2_asd.bin a671f876b7ea6ff9f93dc56e0e147157 raven2_ce.bin be6c5c565ec341ee69f6d99a0ecb109d raven2_gpu_info.bin 5d7b9b404c424c692342cc1408553025 raven2_me.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec2.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec.bin 4d7651ab7fc4dba1abcfaf4a88f40686 raven2_pfp.bin 4ac07f88b9c4aa4fe026be87cb16ceda raven2_rlc.bin ac3a488f651921bc5a21b5a443ee7c23 raven2_sdma.bin 2372175130589c169afc4bc0e0435705 raven2_vcn.bin fe5ec673b44d95c686a240a8d138f499 raven_asd.bin 3e4aeb199a9e1c56a398d5b4ff6a7166 raven_ce.bin b5387b400b0ee4b04565a5179aebb9cd raven_dmcu.bin 052cdc264b228656dff12b95def55c54 raven_gpu_info.bin b16a081785f2f75a6f326ca5ca92113d raven_me.bin 4390c8485f4d4583ae878aa227968a48 raven_mec2.bin 4390c8485f4d4583ae878aa227968a48 raven_mec.bin f69ef2e297e66eb68eecb02540780f4c raven_pfp.bin 0e5fff019103b4cdc5a0366e29411fdd raven_rlc.bin df5f1ef96feade475a9c83451d840bb3 raven_sdma.bin 7e22527c2ef5e9b6e4e871d6ec546848 raven_vcn.bin There's the possibility that I'm wrong and the actually firmware file is not related to Raven Ridge (I doubt it, my usage when it freezes points to being a GPU problem) More specifically I'm using these https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tag/?h=20190815 I have been working with these new firmware files for months and no crashes. Yesterday linux-firmware was updated reverting my changes, and it started locking up again. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1852857/+attachment/5305899/+files/lspci.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 Title: Use more modern Raven Ridge firmware in linux-firmware package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827302] Re: 18.10 → 19.04 Alt-Tab cycling no longer includes Slack window
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",
"_NET_WM_WINDOW_TYPE_SPLASH",
"_NET_WM_WINDOW_TYPE_TOOLBAR",
"_NET_WM_WINDOW_TYPE_UTILITY",
But Slack doesn't set them.
I compiled xfwm4 from source, debugged remotely (it is nearly impossible
to halt the window manager in the host machine...) and the problem boils
down to:
1. clientCycleCreateList in cycle.c calls:
if (!clientSelectMask (c2, NULL, search_range, WINDOW_REGULAR_FOCUSABLE))
{
TRACE ("%s not in select mask", c2->name);
continue;
}
2. Inside clientSelectMask in focus.c, c2->type = 0; thus "return
c2->type & mask" returns 0 regardless of the mask and thinks the window
should not be alt-tabbed
3. I believe (not 100% sure) this happens because in clientWindowType in
netwm.c, c->type_atom == None. I don't know whether this should be
treated as a client bug or a window manager bug. I'm not an X11 expert
so I don't know if it is possible to know if a window is the root one,
but root windows should definitely be alt-tabbeable.
If I change the line to:
if (!clientSelectMask (c2, NULL, search_range,
WINDOW_REGULAR_FOCUSABLE) && c2->type != UNSET)
Then Slack works with alt+tab and my computer hasn't blown up yet. I
don't know if it's the proper fix though, but it may be
I fixed this problem by rebuilding xfwm4 with the attached patch:
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 -i xfwm4_slack_fix.diff #Point it where the patch is located!!!
debuild -b -uc -us
sudo dpkg -i ../xfwm4_4.12.5-1ubuntu0.18.04.1_amd64.deb
** Patch added: "Alt + Tab fix for xfwm4 and Slack"
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1827302/+attachment/5261320/+files/xfwm4_slack_fix.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827302
Title:
18.10 → 19.04 Alt-Tab cycling no longer includes Slack window
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1827302/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767560] Re: Battery graph in tray icon is inaccurate
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 themes are misleading. In /usr/share/icons/elementary- xfce/status/symbolic, battery-good-symbolic takes over at 30-59%, however the icon displayed looks more like 70% full or so. Relevant files: battery-caution-charging-symbolic.svg battery-caution-symbolic.svg battery-empty-charging-symbolic.svg battery-empty-symbolic.svg battery-full-charged-symbolic.svg battery-full-charging-symbolic.svg battery-full-symbolic.svg battery-good-charging-symbolic.svg battery-good-symbolic.svg battery-low-charging-symbolic.svg battery-low-symbolic.svg GNOME icons are consistent with this scheme (it shows 3 bars). -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1767560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767560] Re: Battery graph in tray icon is inaccurate
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1767560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767560] Re: Battery graph in tray icon is inaccurate
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767560 Title: Battery graph in tray icon is inaccurate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1767560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791452] Re: screen tearing in some games (fullscreen and windowed)
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791452 Title: screen tearing in some games (fullscreen and windowed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767560] Re: Battery graph in tray icon is inaccurate
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 the range [30; 59] an icon that indicates around 60% battery level is
displayed.
In the range [10; 30] an icon that indicates around 30-40% battery level is
displayed
In the range [0; 9] an orange bar is displayed
Judging from the themes in 17.xx at /usr/share/icons/elementary-
xfce/status/48 there's a lot more battery icon variety than what is
being displayed (there's icons for 6 ranges!).
As for the fake module, apply this patch:
diff --git a/fake_battery.c b/fake_battery.c
index 2e3c04c..48da386 100644
--- a/fake_battery.c
+++ b/fake_battery.c
@@ -23,6 +23,7 @@
#include
#include
+#include
static int
fake_battery_get_property1(struct power_supply *psy,
@@ -63,7 +64,6 @@ static int ac_status = 1;
static char *fake_ac_supplies[] = {
"BAT0",
-"BAT1",
};
static enum power_supply_property fake_battery_properties[] = {
@@ -99,14 +99,6 @@ static struct power_supply_desc descriptions[] = {
.get_property = fake_battery_get_property1,
},
-{
-.name = "BAT1",
-.type = POWER_SUPPLY_TYPE_BATTERY,
-.properties = fake_battery_properties,
-.num_properties = ARRAY_SIZE(fake_battery_properties),
-.get_property = fake_battery_get_property2,
-},
-
{
.name = "AC0",
.type = POWER_SUPPLY_TYPE_MAINS,
@@ -220,7 +212,7 @@ handle_charge_changes(int ac_status, struct battery_status
*battery)
static ssize_t
control_device_write(struct file *file, const char *buffer, size_t count,
loff_t *ppos)
{
-char kbuffer[1024]; /* limited by kernel frame size, 1K should be enough */
+char kbuffer[512]; /* limited by kernel frame size, 1K should be enough */
char *buffer_cursor;
char *newline;
size_t bytes_left = count;
@@ -232,8 +224,8 @@ control_device_write(struct file *file, const char *buffer,
size_t count, loff_t
return -EINVAL;
}
-if(count > 1024) {
-printk(KERN_ERR "Too much data provided to /dev/fake_battery (limit
1024 bytes)\n");
+if(count > 512) {
+printk(KERN_ERR "Too much data provided to /dev/fake_battery (limit
512 bytes)\n");
return -EINVAL;
}
@@ -264,7 +256,7 @@ control_device_write(struct file *file, const char *buffer,
size_t count, loff_t
power_supply_changed(supplies[0]);
power_supply_changed(supplies[1]);
-power_supply_changed(supplies[2]);
+//power_supply_changed(supplies[2]);
return count;
}
This patch fixes a compilation error, a gcc warning, and disables the 2nd fake
battery (by default the git repo creates 2 fake batteries)
And then run:
make
sudo insmod ./fake_battery.ko
echo 'charging = 0' | sudo tee /dev/fake_battery
echo 'capacity0 = 50' | sudo tee /dev/fake_battery
--
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1767560/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766217] Re: software updater presents an empty panel for updating
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766217 Title: software updater presents an empty panel for updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1766217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766217] Re: software updater presents an empty panel for updating
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. https://bugs.launchpad.net/bugs/1766217 Title: software updater presents an empty panel for updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1766217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
