Hi Daniel,
Thanks again.
Tested 42.5-0ubuntu1vv5
When I apply the 200% scale:
https://pastebin.ubuntu.com/p/MfS9vpT6KB/
When I revert it:
https://pastebin.ubuntu.com/p/SHtvrXyPkY/
And then I get this situation (possibly due to what you mentioned on the
settings app attempting to enable the 4
Although Mustafa says he's not well-versed, he's way smarter than me :)
So his comment#26 seems to be much more relevant than what I have to
say, but I'd like to reply to Daniel's comment#24/25 anyway:
I saw the details you mentioned on comment #16, and I also have
fractional scaling turned off. B
> Try logging into a non-GNOME Xorg session on Workspaces
> if you can. Then use the 'xrandr' command to set a mode
> to turn on one of the unused virtual monitors. If that
> causes the DCV client to go blank then we have proven
> it's not mutter's fault.
I did test that with a Cinnamon session a
Hi Daniel,
Thanks again, and I totally agree that we need to focus on the revert
resolution issue in this LP bug. I wasn't willing to discuss the other
issues here, but to summarize my understanding so far, so as to make
sure we are on the same page.
Also, I tested "xrandr --output VNC-output-1 -
Daniel,
A few items to make sure I'm on the same page:
1. So, IIUC, you're saying that the "final fix" should be the vv5
package, which contains the fix to the zero hz bug (loosening mutter to
accept zero-Hz, as this is the bogus refresh rate being reported by
Xdcv) + the caveat for AWS to either
Ignacio, if Xdcv ever wants to support Fractional Scaling, I believe you
will also need to look at the details shared by Daniel in his comment
#16. Otherwise, even if we fix the zero hz issue, you will be able to
change/revert scale, but will also need to make sure fractional scaling
is disabled.
Daniel,
Regarding 3 (the blank screen issue when enabling a monitor): I can
confirm that the issue happens when you're using Workspaces client
5.9.0.4129 (Windows client version) and no longer happens (even with
Xdcv + Gnome) in 5.10.0.4196.
And, by checking the client release notes [1]:
"Resolv
Thank you very much for the great job narrowing this, Daniel!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782
Title:
Xdcv: Changing display scale setting and reverting it fails
I've tested Focal and it works well with adsys from -proposed:
https://pastebin.ubuntu.com/p/6RBcBpZq2T/
And also does Jammy:
https://pastebin.ubuntu.com/p/pqvgSkkmcQ/
I'm having issues with Kinetic. When I install adsys, I'm no longer able
to login to the instance, I'm getting the following er
I've tested the mutter packages from -proposed in an AWS Workspace:
https://pastebin.ubuntu.com/p/9Yvgfs7yZr/
And I'm able to successfully change the scale to 200% and then revert
the setting.
The following messages are logged when changing to 200%:
https://pastebin.ubuntu.com/p/Y5QdXSqcsW/
An
OK, thanks for the information. The one I had tested was 42.9-0ubuntu2
with Jammy. I'll test again when 42.9-0ubuntu3 is available in
-proposed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/
Hi,
Thank you for the package in -proposed.
I just tested Ubuntu 22.04 and I can confirm it fixes the issue.
First, used 22.04 with the current mutter version available in jammy-
updates:
user0@U-2RVWD6LKXR3GE:~$ sudo apt-cache policy mutter-common libmutter-10-0
gir1.2-mutter-10
mutter-common
I just tested Ubuntu 22.04 and I can confirm it fixes the issue.
First, used 22.04 with the current mutter version available in jammy-
updates:
user1@U-20CG3JVH1ALS3:~$ sudo apt-cache policy mutter-common libmutter-10-0
gir1.2-mutter-10
[sudo] password for user1:
mutter-common:
Installed: 42.
I've tested this in Lunar and Mantic.
TL;DR: In Lunar I hit the exact same issue as in Kinetic. After
installing adsys, I'm no longer able to login using a domain user. On
Mantic, it works fine and I'm able to login even after installing adsys.
On the other hand, both Lunar and Mantic have the sa
@Daniel,
My understanding is that bug 2019751 is the same as bug 1989170, but
public. Since the fix was not released to Jammy, bug 2019751 aims to
address that (although your question might be targeted to Lunar, since I
see bug 1989170 was released to Kinetic.
--
You received this bug notificati
Public bug reported:
In Amazon Workspaces running Ubuntu 22.04, when attempting to change the
Scale in the Gnome Display settings, if you click on a different scale
(i.e. changing from 100% to 200%) and hitting apply, it will bring up a
prompt asking if you want to keep or revert the changes and t
Also tested with mutter-common 42.5-0ubuntu1 and gnome-shell
42.5-0ubuntu1:
fabiomirmar@U-1JSKZM4R9U78P:~$ sudo apt-cache policy mutter-common
[sudo] password for fabiomirmar:
mutter-common:
Installed: 42.5-0ubuntu1
Candidate: 42.5-0ubuntu1
Version table:
*** 42.5-0ubuntu1 500
500
Hi Daniel,
I'm not with the SEG team and I would need assistance from someone
building that and providing the debs or a ppa. I've also subscribed
Mustafa, from SEG, to this bug, as he's assisting me investigating this
issue.
Regards,
Fabio Martins
--
You received this bug notification because y
I also tested Daniel's mutter package with:
sudo add-apt-repository ppa:vanvugt/mutter
sudo apt update
sudo apt upgrade
And rebooted the Workspace just in case.
I know Mustafa mentioned he was still able to reproduce the issue. In my
case, I wasn't but on the other hand, I can't do the action t
Thanks for the investigation Daniel.
Indeed my inability to change the scale with the first patch was due to
low resolution in my client machine.
Interesting enough, I tried reproducing this in a Local VM with Xdcv
(with just regular mutter packages, straight from our archives, no PPA),
and I'm u
I was getting some inconsistent and confusing results on my tests, so I
decided to start from scratch with a fresh VM (qemu) and also a fresh
Workspace (AWS).
In a freshly installed Jammy VM (on qemu, not AWS), out of the box we
have factional scaling disabled, so I tried changing scale to 200% an
Public bug reported:
In an environment where /etc/krb5.conf sets "default_ccache_name =
FILE:/tmp/krb5cc_%{uid}" and you don't have the KRB5CCNAME variable set,
running "adsysctl update" with a AD domain user will fail.
If you either export the variable with the path to the kerberos ticket
OR run
Sorry for the late feedback, but sharing here:
AWS docs regarding best practices regarding cpu-starvation [1] do not
recommend disabling the irqbalance service. Quoting the doc:
> "Note: we do not recommend disabling irqbalance service. ENA driver
doesn’t provide affinity hints, and if device res
We are closing this bug report as it is related to a no longer supported
version of Ubuntu + Kernel + Nautilus and this issue has not been
observed in any recent and supported releases.
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
--
You received this bug notification because y
Thank you for filing this bug. I tried to reproduce it in Xenial, but it
seems this behavior is no longer happening and very likely is already
fixed, so I'm closing this bug as invalid. This is also a duplicate of
683725.
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
--
You rece
Thank you for filing this bug. I tried to reproduce it in Xenial, but it
seems this behavior is no longer happening and very likely is already
fixed, so I'm closing this bug as invalid. This is also a duplicate of
686780.
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
--
You rece
26 matches
Mail list logo
