[Bug 1956408] Re: Ubuntu 21.10 very slow after kernel update to 5.13.0-23-generic

[Lucas Sandery]

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

A similar issue occurred on 5.6.x kernels:
https://askubuntu.com/questions/1240879/rx-5500-xt-ubuntu-20-10-instability-crashing-drmamdgpu-dm-commit-planes-cons

Looks like it's been known since last October:
https://lore.kernel.org/lkml/YYAandieODqdEuXe@llamedos.localdomain/T/

I am seeing it on an AMD Picasso.

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

Title:
  Ubuntu 21.10 very slow after kernel update to 5.13.0-23-generic

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


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

[Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop

[Lucas Sandery]

@seb128 I'm not sure it's upstream.
 has been around
forever and was marked as duplicate of the still open
 where it appears
Mozilla doesn't want to do anything about it. The earliest ancestor of
that file I can find in the source is from 2010
.

** Bug watch added: Mozilla Bugzilla #371734
   https://bugzilla.mozilla.org/show_bug.cgi?id=371734

** Bug watch added: Mozilla Bugzilla #296568
   https://bugzilla.mozilla.org/show_bug.cgi?id=296568

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

Title:
  Add message/rfc822 to thunderbird.desktop

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

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

[Bug 661829] Re: Cannot set up a trigger for the Calculator key

[Lucas Sandery]

Apologies for the noise. It did work after a reboot/relogin; the
assignment was not immediate as with other global shortcuts I've set.

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

Title:
  Cannot set up a trigger for the Calculator key

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-runtime/+bug/661829/+subscriptions

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

[Bug 661829] Re: Cannot set up a trigger for the Calculator key

[Lucas Sandery]

Has there been a regression? I'm seeing the same behaviour.

=== system ===

Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.7.11-050711-generic
OS Type: 64-bit

=== xev output ===

KeyPress event, serial 40, synthetic NO, window 0x761,
root 0x6cb, subw 0x0, time 20275320, (600,670), root:(600,699),
state 0x10, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen 
YES,
XLookupString gives 0 bytes: 
XmbLookupString gives 0 bytes: 
XFilterEvent returns: False

KeyRelease event, serial 41, synthetic NO, window 0x761,
root 0x6cb, subw 0x0, time 20275432, (600,670), root:(600,699),
state 0x10, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen 
YES,
XLookupString gives 0 bytes: 
XFilterEvent returns: False

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

Title:
  Cannot set up a trigger for the Calculator key

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-runtime/+bug/661829/+subscriptions

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

[Bug 372588] Re: sudo crontab -e uses wrong vi version

[Lucas Sandery]

In this case, when update-alternatives does not work, try select-editor
instead.

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

Title:
   sudo crontab -e uses wrong vi version

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

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

[Bug 1694891] Re: All btrfs-tools commands need a quiet option for scripting

[Lucas Sandery]

Looks like it's on the horizon upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=111421#c1

Maybe a prod from distro devs can help things along?

** Bug watch added: Linux Kernel Bug Tracker #111421
   https://bugzilla.kernel.org/show_bug.cgi?id=111421

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

Title:
  All btrfs-tools commands need a quiet option for scripting

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

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

[Bug 1694891] [NEW] All btrfs-tools commands need a quiet option for scripting

[Lucas Sandery]

Public bug reported:

Btrfs send and receive are noisy on stderr by default (messages like "At
subvol foo"). It'd be great to get an option to only print there if
there is an error condition. I assume there are other commands which do
the same.

See the patched version that quiets send but not receive. (I didn't realise 
receive was also noisy when requesting the backport.)
https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2017-May/017455.html
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+packages

Many scripts/cron wrappers check for output on stderr in order to notify
when warnings/errors occur. There should be a way to avoid triggering
such notifications when btrfs commands are successful.

** Affects: btrfs-tools (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/1694891

Title:
  All btrfs-tools commands need a quiet option for scripting

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

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

[Bug 1634572] Re: APCUPSD does not send killpower command to UPS (only happens on Ubuntu 16.04)

[Lucas Sandery]

I got around this by creating (and of course doing chmod +x on) a script
at /lib/systemd/system-shutdown/apcups-killpower

#!/bin/sh
if [ "$1" = "poweroff" -a -f /etc/apcupsd/powerfail ]; then
/etc/apcupsd/apccontrol killpower
fi

Idea from 
https://wiki.archlinux.org/index.php/APC_UPS#Make_apcupsd_kill_UPS_power_once_the_hibernate_is_done
(with credit to djgera 
https://bbs.archlinux.org/viewtopic.php?pid=1354737#p1354737 and fsateler 
https://github.com/systemd/systemd/issues/4894#issuecomment-267372354)

** Bug watch added: github.com/systemd/systemd/issues #4894
   https://github.com/systemd/systemd/issues/4894

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

Title:
  APCUPSD does not send killpower command to UPS (only happens on Ubuntu
  16.04)

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

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