[Bug 1763232] [NEW] Width and Update Interval Optons do not Save

[Michael Roy]

Public bug reported:

Package: mate-applets 1.20.1-0ubuntu1
Release: 18.04 Ubuntu Bionic Beaver (development branch)
Version: 1.20.1-0ubuntu1

Expected:
Changes to System Monitor applet width and System monitor update interval save 
and are persistent following a reboot.

Actual:
Changes to System Monitor applet width and System Monitor update interval do 
not save and return to default states following a reboot.

Steps to Reproduce:

1. In Ubuntu Mate, right-click on a panel and click "Add to Panel..." 
2. Add System Monitor applet to Panel
3. Right click on System Monitor applet in Panel
4. Click Preferences
5. In "System Monitor Preferences" window, go to "Options" section and change 
the values for "System monitor width:" and "System monitor update interval" (I 
changed to 80 pixels and 1 milliseconds, respectively)
6. Click "Close" to close (and save) changed width and update interval options
7. System monitor width and System monitor update interval appears to change as 
expected, HOWEVER now try the following:

8. Right click on System Monitor applet in Panel
9.  Click Preferences
10. In "System Monitor Preferences" window, under "Options" section, the values 
shown for "System monitor width:" and "System monitor update interval" have 
reverted to default values ***even though the applet itself remains at user-set 
values***  The values displayed in the System Monitor Preferences dialog are 
now inconsistent with the appearance of the applet, which is incorrect behavior.

11. Change the values for "System monitor width:" and "System monitor update 
interval" to match the appearance of the applet (I changed to 80 pixels and 
1 milliseconds, respectively)
12. Click "Close" to close (and save) changed pixels and milliseconds settings
13. Right click on System Monitor applet in Panel
14. Click "Lock To Panel
15. Reboot computer
16. Upon reboot and login, system monitor applet width and update interval have 
reverted to default values, ignoring user-set values. This is incorrect 
behavior.

** Affects: mate-desktop
 Importance: Unknown
 Status: New

** Affects: mate-applets (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: applet monitor system

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

Title:
  Width and Update Interval Optons do not Save

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

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

[Bug 1763232] Re: Width and Update Interval Optons do not Save

[Michael Roy]

Small edit: millisecond setting in the above step-by-step should be
1,000, not 10,000.

** Package changed: mate-system-monitor (Ubuntu) => mate-applets
(Ubuntu)

** Bug watch added: github.com/mate-desktop/mate-applets/issues #291
   https://github.com/mate-desktop/mate-applets/issues/291

** Also affects: mate-desktop via
   https://github.com/mate-desktop/mate-applets/issues/291
   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/1763232

Title:
  Width and Update Interval Optons do not Save

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

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

[Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion

[Michael Roy]

Hi there, VMware here...
We're able to repro this and have the following temporary workaround while we 
figure out who's code needs adjusting:

We are able to boot by adding:
acpi=force 

to: GRUB_CMDLINE_LINUX_DEFAULT 
in: /etc/default/grub
Such that the full line reads:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"

Remember to also disable Wayland (which is not presently supported in
this Fusion tech preview) in /etc/gdm3/custom.conf by uncommenting
WaylandEnable=false.

When it's in the unresponsive state it still boots so ssh works... you
can check /proc/iomem and it seems like the PCI memory is already
reserved for BOOTFB..

Not working state:
5000-7fff : pcie@0x4000
  7800-7fff : :00:0f.0
7800-782f : BOOTFB

Working state: (i.e. with acpi=force)

5000-7fff : PCI Bus :00
  5000-501f : PCI Bus :20
  5020-503f : PCI Bus :21
  5040-505f : PCI Bus :21
  7800-782f : BOOTFB

We have an internal bug filed so I'll update if we have more we can
share.

Thanks,
-Michael

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

Title:
  5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion

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


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