[Bug 1968451] Re: GNOME launcher folder icons and labels very small

2022-04-11 Thread Daniel van Vugt
Upstream bugs:

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5097
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3450

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5097
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5097

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3450
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3450

** Tags added: quality visual

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  GNOME launcher folder icons and labels very small

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968451/+subscriptions


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

[Bug 1968663] [NEW] Screen freeze when unsuspending and entering password

2022-04-11 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Sometimes after unsuspending and entering the login screen password, the
right spinning icon stops and the whole system hangs.  I am able to SSH
into the machine and look at the logs, but everything seems pretty
normal and I can't find relevant errors.  Do note that my internal
webcam connection is kinda wonky but I don't know if that's related.
Pressing Alt+F# to switch to a TTY doesn't work.  I have to force power
down every time by holding the power button.  This happens once in a
while.  I'm using Wayland and Gnome.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.54  Tue Feb  8 04:42:21 
UTC 2022
 GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2)
ApportVersion: 2.20.11-0ubuntu71.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 11 20:05:34 2022
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Once a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 
[VGA controller])
   Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
   Subsystem: Hewlett-Packard Company TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[103c:8601]
InstallationDate: Installed on 2021-10-15 (178 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: Dell Inc. XPS 15 7590
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic 
root=/dev/mapper/vgroot-lvroot--ubuntu--21.10 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 018W12
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn018W12:rvrA02:cvnDellInc.:ct10:cvr:sku0905:
dmi.product.family: XPS
dmi.product.name: XPS 15 7590
dmi.product.sku: 0905
dmi.sys.vendor: Dell Inc.
nvidia-settings:
 ERROR: Unable to find display on any available system
 
 
 ERROR: Unable to find display on any available system
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug freeze impish ubuntu wayland-session
-- 
Screen freeze when unsuspending and entering password
https://bugs.launchpad.net/bugs/1968663
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-shell in Ubuntu.

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

[Bug 1968428] Re: AMD HD7970 Error: no ums support in radeon modual

2022-04-11 Thread Daniel van Vugt
It sounds like "nomodeset" is actually causing the newest error:

  no UMS support in Radeon module

That's expected with nomodeset and probably not a bug. So we should
instead find out why you had a hang with only a cursor at the top left
of the screen.

Please:

 1. Remove "nomodeset".

 2. Reboot (expecting it to fail).

 3. Reboot again with "nomodeset" and run:

journalctl -b-1 > prevboot.txt

 4. Attach the resulting text file here.


 

** Summary changed:

- AMD HD7970 Error: no ums support in radeon modual
+ After installation it just hangs with a cursor at the top left of the screen

** Package changed: gnome-shell (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  After installation it just hangs with a cursor at the top left of the
  screen

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


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

[Bug 1968425] Re: Workspace switching interruptible with trackpad overview gesture

2022-04-11 Thread Daniel van Vugt
I wonder if this is related to an old bug 1878408 (different GNOME
version).

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Workspace switching interruptible with trackpad overview gesture

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968425/+subscriptions


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

[Bug 1968518] Re: FFe: Backport new RDP settings

2022-04-11 Thread Jonas Ådahl
Some more upstream reasoning for switching from VNC to RDP:

Some releases ago an RDP backend was added to gnome-remote-desktop,
using the FreeRDP's RDP implementation, while the VNC backend uses the
LibVNCServer project's implementation. Over time, the RDP backend
significantly surpassed the abilities of the VNC backend, both in terms
of features and performance, and we had contemplated switching the
default backend in the past already. It's also worth noting that the RDP
protocol doesn't have awkward limitations on password length in the
commonly used authentication mechanism. Also, from an "outsiders" point
of view, FreeRDP feels like a much more active project than
LibVNCServer, and RDP is simply a more capable protocol.

A side note about security of the VNC backend: the original intention
with the VNC backend was to more or less mimic the functionality of
vino, which had an out-dated fork of LibVNCServer bundled with it.
Having a fork of a library that tends to get its fair share of CVE's
didn't feel like a good idea, so the upstream library was used directly.
However, to get the same level of encryption (anon-tls), LibVNCServer
still needed to be patched. Patches were originally contributed in 2018,
but has not landed yet, thus to get anon-tls encryption, distributions
needs downstream patching. With the RDP backend, we both moved away from
non-verifiable anon-tls as well as downstream patching.

One thing that has stopped us from switching the backend in the past has
been the need to re-design the settings dialog. It had been planned to
change the design of said dialog for some time already, but it was a
non-trivial task, since it involved more complicated steps, such as TLS
key/cert generation, management and verification. For GNOME 42, however,
we managed to both get designs as well as implement them in Settings,
thus it made us feel like it was a good opportunity to make the switch.

Originally we intended to have a "blue bar" with a note about the VNC
backend being enabled, with the option of disabling it. This blue bar
was disabled, after dropping the plan to try to automatically enable the
VNC backend on upgrade. The primary reason for dropping this was that
any risk of enabling the VNC backend by accident was too big of a risk,
given the security implications of unknowingly running a VNC remote
desktop server. It was also discussed whether it should be possible to
configure the VNC backend as well as the RDP backend, but the design
team decided against it; instead we added the command line utility
'grdctl' that allows configuration the VNC backend.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1968518

Title:
  FFe: Backport new RDP settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions


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

[Bug 1968390] Re: JS ERROR: TypeError: this.window_container is null

2022-04-11 Thread Daniel van Vugt
Looks similar to https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4324 but that was fixed in GNOME 41.

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

Title:
  JS ERROR: TypeError: this.window_container is null

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968390/+subscriptions


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

[Bug 1968390] Re: JS ERROR: TypeError: this.window_container is null

2022-04-11 Thread Daniel van Vugt
Thanks for the bug report. I have removed most of the log messages
because they are already covered by bug 1968383. So now this bug is only
about:

  JS ERROR: TypeError: this.window_container is null

** Description changed:

  Ubuntu 22.04 Development
  
  A 3 finger touchpad swipe up/down gesture with 1 application open
  outputs a lot of JS errors and stacks to the journal. This issue may be
  the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1968383 but the output is somewhat different when you have
  more than 1 app open.
  
  This also happens with all extensions disabled, does not happen in
  Fedora 36.
  
  To reproduce
  
  1. login and open terminal and watch the journal
  2. perform the 3 finger swipe up gesture until the app grid displays then 
swipe down to go back to the desktop.
  3. See journal
  4. If nothing happens try opening an app, closing it and try again.
  
- Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Button (0x56219f5b8060), 
has been already disposed — impossible to get any property from it. This might 
be caused by the object having been destroyed from C code using something such 
as destroy(), dispose(), or remove() vfuncs.
- Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
- Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:566 (4ce0bb0ac40 @ 10)
- Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
- Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:567 (4ce0bb0ac40 @ 36)
- Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
- Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:570 (4ce0bb0ac40 @ 77)
- Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
- Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7257f0 i   
resource:///org/gnome/shell/ui/windowPreview.js:638 (4ce0bb0ae20 @ 23)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #1   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:353 (4ce0bb0a5b0 @ 62)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #2   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
- Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
- Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:357 (4ce0bb0a5b0 @ 87)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #1   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
- Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
- Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7257f0 i   
resource:///org/gnome/shell/ui/windowPreview.js:364 (4ce0bb0a600 @ 8)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #1   7ffc4c0aa640 I   self-hosted:205 
(330c4e3bed80 @ 272)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #2   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #3   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
- Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
- Apr 08 21:18:49 x1c gnome-shell[21675]: #0   7ffc4c0a99a0 b   
resource:///org/gnome/shell/ui/environment.js:160 (330c4e3cc560 @ 43)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #1   7ffc4c0a9a70 b   
resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #2   56219e7257f0 i   
resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #3   7ffc4c0aa640 I   self-hosted:205 
(330c4e3bed80 @ 272)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #4   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #5   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
- Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
- Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Label (0x56219f5a8440), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
- Apr 08 21:18:49 x1c gnome-shell[21675]: #0   7ffc4c0a98b0 b   
resource:///org/gnome/shell/ui/environment.js:361 (330c4e3ccc90 @ 43)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #1   7ffc4c0a99a0 b   
resource:///org/gnome/shell/ui/environment.js:163 (330c4e3cc560 @ 91)
- Apr 08 21:18:49 x1c gnome-shell[21675]: #2   7ffc4c0a9a70 b   
resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23)
- Apr 08 2

[Bug 1968357] Re: While logginto unity session the message that'the system has crashed and cannot be recovered. the extentions have been disabled"

2022-04-11 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: gnome-session (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  While logginto unity session the message that'the system has crashed
  and cannot be recovered. the extentions have been disabled"

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


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

[Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having b

2022-04-11 Thread Daniel van Vugt
** Summary changed:

- Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
+ Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs. [windowPreview.js:566]

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

Title:
  Touchpad gesture animations trigger Object St.Button (0x56439bd53160),
  has been already disposed — impossible to get any property from it.
  This might be caused by the object having been destroyed from C code
  using something such as destroy(), dispose(), or remove() vfuncs.
  [windowPreview.js:566]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383/+subscriptions


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

[Bug 1964458] Re: [jammy] gnome-shell live session crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl

2022-04-11 Thread Daniel van Vugt
https://salsa.debian.org/gnome-team/gnome-
shell/-/commit/0fb70b0603817614d8612f1a289cd9ceb369616e

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: gnome-shell (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  [jammy] gnome-shell live session crashes with SIGSEGV in
  js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1964458/+subscriptions


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

[Bug 1960436] Re: Touchpad setting toggles don't work

2022-04-11 Thread Launchpad Bug Tracker
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1960436

Title:
  Touchpad setting toggles don't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1960436/+subscriptions


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

[Bug 1968660] Re: gvfsd-google assert failure: munmap_chunk(): invalid pointer

2022-04-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1959714 ***
https://bugs.launchpad.net/bugs/1959714

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1959714, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1968660/+attachment/5579661/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1968660/+attachment/5579663/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1968660/+attachment/5579666/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1968660/+attachment/5579667/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1968660/+attachment/5579668/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1968660/+attachment/5579669/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1968660/+attachment/5579670/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1959714
   gvfsd-google assert failure: munmap_chunk(): invalid pointer

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-google assert failure: munmap_chunk(): invalid pointer

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


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

[Bug 1945760] Re: Window manager warning: WM_TRANSIENT_FOR window 0x56994b0 for 0x572b45a window override-redirect is an override-redirect window and this is not correct according to the standard, so

2022-04-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  Window manager warning: WM_TRANSIENT_FOR window 0x56994b0 for
  0x572b45a window override-redirect is an override-redirect window and
  this is not correct according to the standard, so we'll fallback to
  the first non-override-redirect window 0x560003f.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945760/+subscriptions


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

[Bug 1968660] [NEW] gvfsd-google assert failure: munmap_chunk(): invalid pointer

2022-04-11 Thread Fabian Aguilar
Public bug reported:

Google Drive files will not open from Nautilus. However, if the files
are dragged out to the desktop or another folder, they will open.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gvfs-backends 1.48.1-4
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
AssertionMessage: munmap_chunk(): invalid pointer
CasperMD5CheckResult: pass
CrashCounter: 1
Date: Mon Apr 11 20:31:37 2022
ExecutablePath: /usr/libexec/gvfsd-google
InstallationDate: Installed on 2022-04-10 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
ProcCmdline: /usr/libexec/gvfsd-google --spawner :1.3 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa7607beb8c 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
 malloc_printerr (str=str@entry=0x7fa7607c1230 "munmap_chunk(): invalid 
pointer") at ./malloc/malloc.c:5664
 munmap_chunk (p=) at ./malloc/malloc.c:3060
 __GI___libc_free (mem=) at ./malloc/malloc.c:3381
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gvfsd-google assert failure: munmap_chunk(): invalid pointer
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

** Affects: gvfs (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash jammy need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gvfsd-google assert failure: munmap_chunk(): invalid pointer

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


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

[Bug 1968654] Re: gnome-control-center crashed with SIGSEGV Gnome settings crash when I attempt to open the pane to configure my Google Account.

2022-04-11 Thread Apport retracing service
*** This bug is a duplicate of bug 1965702 ***
https://bugs.launchpad.net/bugs/1965702

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1965702, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1968654/+attachment/5579639/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1968654/+attachment/5579641/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1968654/+attachment/5579644/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1968654/+attachment/5579645/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1968654/+attachment/5579646/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1968654/+attachment/5579647/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1968654/+attachment/5579648/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1965702

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1968654

Title:
  gnome-control-center crashed with SIGSEGV  Gnome settings crash when I
  attempt to open the pane to configure my Google Account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968654/+subscriptions


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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking

2022-04-11 Thread Daniel van Vugt
In case the 'rotation' and 'GAMMA_LUT' properties are relevant, please
try:

 * Regular landscape orientation for a while

 * Disabling night light for a while

Please also run:

  sudo drm_info > drminfo.txt

and attach the resulting text file here.

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

Title:
  Blanked screen doesn't wake up after locking

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


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

[Bug 1968518] Re: FFe: Backport new RDP settings

2022-04-11 Thread Robert Ancell
Łukasz - PPA here https://launchpad.net/~robert-
ancell/+archive/ubuntu/gnome-control-center

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1968518

Title:
  FFe: Backport new RDP settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions


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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking

2022-04-11 Thread Daniel van Vugt
Thanks. Unfortunately MUTTER_DEBUG=kms can't tell us which is the
invalid argument and I can't see a consistent pattern in the log.

Please try these in /etc/environment in separate sessions:

  MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1

  MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

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

Title:
  Blanked screen doesn't wake up after locking

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


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

[Bug 1968395] Re: [impish] Wayland is with the black screen when I share it

2022-04-11 Thread Daniel van Vugt
Ubuntu 22.04 will be out in a couple of weeks so I would recommend
trying that instead after it is released.

** Summary changed:

- Wayland
+ [impish] Wayland is with the black screen when I share it

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

Title:
  [impish] Wayland is with the black screen when I share it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968395/+subscriptions


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

[Bug 1968255] Re: Sudden, unexpected restart of the whole system. Reporting after automatic restart

2022-04-11 Thread Daniel van Vugt
A whole system restart is likely a kernel bug. Next time it happens,
please run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  Sudden, unexpected restart of the whole system. Reporting after
  automatic restart

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


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

[Bug 1968614] Re: gnome-shell crashed with SIGSEGV in meta_input_device_x11_reset_scroll_info()

2022-04-11 Thread Daniel van Vugt
** Summary changed:

- gnome-shell crashed with SIGSEGV in g_main_context_dispatch()
+ gnome-shell crashed with SIGSEGV in meta_input_device_x11_reset_scroll_info()

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968614/+attachment/5579439/+files/CoreDump.gz

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV in
  meta_input_device_x11_reset_scroll_info()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968614/+subscriptions


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

[Bug 1968005] Re: Extensions app crashes on startup

2022-04-11 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563

Thanks. That is definitely bug 1965563.

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

Title:
  Extensions app crashes on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968005/+subscriptions


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

[Bug 1968590] Re: Gnome-shell memory at 682MB

2022-04-11 Thread Daniel van Vugt
Thanks for the bug report. Please try:

gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false

and then log in again.

** Tags added: gnome-shell-leak

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  Gnome-shell memory at 682MB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968590/+subscriptions


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

[Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]

2022-04-11 Thread Kai-Chuan Hsieh
** Tags added: originate-from-1968244 somerville

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

Title:
  Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
  KMS update: CRTC property (GAMMA_LUT) not found]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions


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

[Bug 1965662] Re: gnome-shell: Unhandled promise rejection in checkInvocation@resource:///org/gnome/shell/misc/util.js:544:26

2022-04-11 Thread Treviño
Fixed in 42.0-1ubuntu1

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-shell: Unhandled promise rejection in
  checkInvocation@resource:///org/gnome/shell/misc/util.js:544:26

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965662/+subscriptions


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

[Bug 1732450] Re: Lock screen doesn't respect gnome shell theme choice

2022-04-11 Thread Treviño
** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Lock screen doesn't respect gnome shell theme choice

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1732450/+subscriptions


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

[Bug 1943857] Re: use downstream pop!_os patch for global theme switching

2022-04-11 Thread Treviño
** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  use downstream pop!_os patch for global theme switching

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943857/+subscriptions


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

[Bug 1968518] Re: FFe: Backport new RDP settings

2022-04-11 Thread Gunnar Hjalmarsson
@Jeremy: Wow, that hadn't been pushed when I looked this morning. But we
should probably use it in jammy then. I think I'll simply use a gnome-
user-docs patch. Better untranslated than incorrect.

To the release team: I added a gnome-user-docs task to this bug, since
the just mentioned measure would be a clear UIF break. Please take a
stand on that too when making your decision.

** Also affects: gnome-user-docs (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1968518

Title:
  FFe: Backport new RDP settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions


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

[Bug 1967011] Re: Unable to Share Screen via PipeWire in OBS Studio

2022-04-11 Thread Treviño
This has been fixed on previous upload.

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Unable to Share Screen via PipeWire in OBS Studio

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967011/+subscriptions


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

[Bug 1968518] Re: FFe: Backport new RDP settings

2022-04-11 Thread Jeremy Bicha
Gunnar, it looks like the GNOME did update their sharing-desktop.page
for the bullet points I mentioned. Maybe you can use their version for
jammy if this FFe is approved?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1968518

Title:
  FFe: Backport new RDP settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions


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

[Bug 1968518] Re: FFe: Backport new RDP settings

2022-04-11 Thread Treviño
More rationale from upstream.

00:03:00 <_pnowack> Trevinho: Assuming the backported UI works here, I think 
this change is good: It aligns with the state in GNOME 42 upstream and the RDP 
should be more stable than the VNC one. At least, when I found crashes I was 
able to fix them for the RDP backend and when I found bugs in FreeRDP upstream, 
then they were adressed pretty fast. The same cannot be said about libvncserver 
upstream
00:03:53  _pnowack: also jadahl mentioned a security aspect of it, 
like keeping vnc enabled was a security concern per se
00:04:14  can elaborate more on that?
00:05:18 <_pnowack> Trevinho: jadahl introduced for both the RDP and VNC 
backend an 'enabled' setting (which defaults to off). The reason is that the 
VNC server won't be silently enabled, when enabling RDP in g-c-c
00:05:30 <_pnowack> (VNC can still be used via grdctl though)
00:06:44 <_pnowack> Trevinho: Regaring security: VNC connections are not 
encrypted. Fedora uses some additional patches for this, but only a few clients 
support encrypted connections. For RDP, TLS is the default and g-r-d enforces 
that.
00:08:07 <_pnowack> which is also the reason why the new Remote Desktop panel 
has the 'Verify Encryption' button, allowing users to check the server 
certificate fingerprint (which should be the same, when connecting with an RDP 
client)
_pnowack> Also: The clipboard integration in the RDP backend is more advanced 
(as the protocol allows it to be): Not just text, can be copied, but also 
images and files. Also, the RDP protocol uses delayed clipboard data rendering, 
meaning the clipboard content is only transferred when requested (VNC sets the 
clipboard content, meaning it is directly requested and transferred)
00:11:37 <_pnowack> Of course, the used RDP client needs to support clipboard 
integration too, to make use of that
00:12:25 <_pnowack> (Remmina, for example, only implements the clipboard 
support for text and images, but not files.)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1968518

Title:
  FFe: Backport new RDP settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions


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

[Bug 1968518] Re: FFe: Backport new RDP settings

2022-04-11 Thread Gunnar Hjalmarsson
Thanks for your input, Jeremy.

We seem to be agreed that the insufficient documentation is the most
important aspect of this. Somebody who really knows the topic needs to
improve it. As far as I know the needed resources are not available in
the docs team. Neither in the GNOME Help team.

Right, a discourse page could be published instantly. There is also the
option that somebody updates sharing-desktop.page soon after the
release. Maybe also for GNOME Help. Then we could add it to the desktop
guide before the 22.04.1 point release.

Please note that the docs team or the translators team does not have a
veto as regards freeze breaks. The decision lies with the release team.
I merely wanted to express my frustration over the poor documentation of
this rather advanced area.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1968518

Title:
  FFe: Backport new RDP settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions


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

[Bug 1968627] [NEW] file saving dialog grows and grows with each additional file dialog

2022-04-11 Thread Ryan Reamsbottom
Public bug reported:

This might be an issue with xdg-desktop-portal-gnome as well, I am using
the Brave Browser and noticed this.  I *think* it uses xdg-desktop-
portal-gtk for the time being though.  This is 22.04 Daily Build from
April 9th updated.

What happens:  If you decide to save an image, the file save dialog pops
up, provided by either xdg-desktop-portal-gtk or -gnome, this is fine.
However, multiple instances of calling the file save dialog such as
saving multiple images from a website will cause the dialog box to grow
and grow every time it is called, leading to it stretching off the main
screen onto my secondary (which is a portrait 1080x1920 monitor to the
right of the main 2560x1440 monitor).  This is super annoying because
you never know where the window is going to appear, and at what size
(well, I guess you do know that it is going to grow each time, but it is
VERY inconsistent).

I've attached a scaled down webm, in it I am downloading cat pictures
from Google Image Search.  For the first image, it shows how large it
tends to get, and I resize it to a smaller size.  Then, with each image
that the dialog is brought up for, it grows and grows.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xdg-desktop-portal-gtk 1.14.0-1build1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 11 15:39:25 2022
InstallationDate: Installed on 2022-04-09 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
SourcePackage: xdg-desktop-portal-gtk
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xdg-desktop-portal-gtk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "screen recording of the file save dialog bug"
   
https://bugs.launchpad.net/bugs/1968627/+attachment/5579502/+files/output.webm

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xdg-desktop-portal-gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1968627

Title:
  file saving dialog grows and grows with each additional file dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1968627/+subscriptions


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

[Bug 1968518] Re: FFe: Backport new RDP settings

2022-04-11 Thread Jeremy Bicha
Gunnar, on Friday, Seb fixed gnome-control-center to work with the new
gnome-remote-desktop using VNC like was done in previous Ubuntu/GNOME
releases.

However, we think that our users will be more comfortable using RDP.

The documentation you pointed to doesn't document VNC well.

The GNOME feature we are backporting would make that page out of date.
- Screen Sharing is now Remote Desktop
- For #7, there is now a Remote Control on/off switch
- There is no require a password or ask for access.

We also could document remote desktop using Discourse. Except for the
translation problem, that is a faster way to provide Ubuntu-specific
docs.

Marco was looking today at also allowing users to switch to VNC with
this dialog as an Ubuntu patch. If we are able to do that, we think that
fixes the main regression risk here.

If we don't provide this dialog, there really isn't a user-friendly for
people to be able to share their desktop using RDP at all. That is a
requested feature.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1968518

Title:
  FFe: Backport new RDP settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions


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

[Bug 1965219] Re: gnome lock screen does not permit reentering password

2022-04-11 Thread Jeff Burdges
This one seemed like it refused to wake even enough to draw a black
scree, just stayed asleep.  I've no idea if this is hlepful

** Attachment added: "refuses_to_wake.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5579458/+files/refuses_to_wake.txt

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

Title:
  gnome lock screen does not permit reentering password

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions


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

[Bug 1967025] Re: Double login screen

2022-04-11 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1966786 ***
https://bugs.launchpad.net/bugs/1966786

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  Double login screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967025/+subscriptions


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

[Bug 1968513] Re: GNOME login fails to stay in the overview if DING is enabled

2022-04-11 Thread Burque Computers
Hi Daniel,

I guess I just didn't realize that showing activities overview window
was "a feature, not a bug."

After removing gnome-shell-extension-desktop-icons-ng, I completely
agree with your analysis. Thanks for also correcting the incorrect tags
I used.

What I ended up doing to achieve my desired result was to install this
extension: https://github.com/fthx/no-overview

It would be cool if that could one day be included in Ubuntu's repo.
It's pretty short and easy to read.

Thanks for your help!

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

Title:
  GNOME login fails to stay in the overview if DING is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968513/+subscriptions


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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking

2022-04-11 Thread Olivier Tilloy
I reverted to stock mutter (42.0-1ubuntu1), enabled KMS debug in mutter,
and observed that the problem persists. Attaching the corresponding
journal.

** Attachment added: "journal-with-kms-debug.log"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5579395/+files/journal-with-kms-debug.log

** Changed in: mutter (Ubuntu)
   Status: Incomplete => New

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

Title:
  Blanked screen doesn't wake up after locking

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


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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking

2022-04-11 Thread Olivier Tilloy
mutter 42.0-1ubuntu2~ppa1 is a locally-patched version with a work-
around for https://gitlab.gnome.org/GNOME/mutter/-/issues/2216, as not
being able to re-order my tabs in firefox was bothering me.

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2216
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2216

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

Title:
  Blanked screen doesn't wake up after locking

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


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

[Bug 1968590] [NEW] Gnome-shell memory at 682MB

2022-04-11 Thread Liad Solenko
Public bug reported:

Memory leak - 680-685Mb use

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 11 18:05:02 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-04-01 (10 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
RelatedPackageVersions: mutter-common 42.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Gnome-shell memory at 682MB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968590/+subscriptions


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

[Bug 1968005] Re: Extensions app crashes on startup

2022-04-11 Thread Vidvranjek
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563

Sounds like  bug 1965563 but not quite. When I try to run Extensions app
from the terminal I get a different error, although related to display.

Output:
$gnome-extensions-app
Gdk-Message: 14:19:32.489: Error flushing display: Protocol error


** Description changed:

  When trying to open the 'Extensions' app nothing happens, crashes on
  startup. Ubuntu 22.04
+ 
+ 
+ Output from terminal:
+ $gnome-extensions-app
+ Gdk-Message: 14:19:32.489: Error flushing display: Protocol error
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 10:13:39 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-21 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Extensions app crashes on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968005/+subscriptions


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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking

2022-04-11 Thread Daniel van Vugt
Also what is mutter 42.0-1ubuntu2~ppa1 ? Does reverting to the archive
version work?

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

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

Title:
  Blanked screen doesn't wake up after locking

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


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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking

2022-04-11 Thread Daniel van Vugt
Not a crash, apparently. The screen is failing to update in Wayland
sessions:

abr 06 13:55:43 dantian gnome-shell[37489]: Failed to post KMS update: 
drmModeAtomicCommit: Argument invalide
abr 06 13:55:43 dantian gnome-shell[37489]: Page flip discarded: 
drmModeAtomicCommit: Argument invalide

To debug it further please add MUTTER_DEBUG=kms to /etc/environment and
then attach a new journal log.

Alternatively, as a workaround try adding
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment.

** Package changed: gdm3 (Ubuntu) => mutter (Ubuntu)

** No longer affects: gnome-shell (Ubuntu)

** No longer affects: gnome-session (Ubuntu)

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

Title:
  Blanked screen doesn't wake up after locking

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


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

[Bug 1968513] Re: GNOME login fails to stay in the overview if DING is enabled

2022-04-11 Thread Daniel van Vugt
** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  GNOME login fails to stay in the overview if DING is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968513/+subscriptions


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

[Bug 1968513] Re: Disabling or removing ubuntu-dock makes Activites window to appear for a few seconds on login

2022-04-11 Thread Daniel van Vugt
Oh you're right, sorry. Correct behaviour without extensions is for
GNOME to stay in the overview upon login. That's the upstream designed
behaviour.

This bug appears to be caused by the desktop-icons-ng extension
starting. I think because that is a full desktop window and maybe GNOME
is designed to leave the overview when any startup application launches.

** Summary changed:

- Disabling or removing ubuntu-dock makes Activites window to appear for a few 
seconds on login
+ GNOME login fails to stay in the overview if DING is enabled

** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome-
shell-extension-desktop-icons-ng (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock
in Ubuntu.
https://bugs.launchpad.net/bugs/1968513

Title:
  GNOME login fails to stay in the overview if DING is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968513/+subscriptions


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

[Bug 1968552] [NEW] Opening web link from evince doesn't work, "env: ‘/snap/bin/firefox’: Permission denied"

2022-04-11 Thread Valentijn Sessink
Public bug reported:

Jammy Jellyfish 22.04. When opening a PDF document with an external link
in it, clicking the link doesn't do anything. However, stderr says "env:
‘/snap/bin/firefox’: Permission denied"

How to reproduce:

Open example PDF file. Click link.
Expected: firefox opens link.
Actual result: nothing; stderr says:

env: ‘/snap/bin/firefox’: Permission denied

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "example PDF"
   https://bugs.launchpad.net/bugs/1968552/+attachment/5579289/+files/link.pdf

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

Title:
  Opening web link from evince doesn't work, "env: ‘/snap/bin/firefox’:
  Permission denied"

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


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

[Bug 1968005] Re: Extensions app crashes on startup

2022-04-11 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563

Sounds like bug 1965563. Please let us know if it's any different.

** This bug has been marked a duplicate of bug 1965563
   gnome-extensions-app fails to start (Protocol error)

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

Title:
  Extensions app crashes on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968005/+subscriptions


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

[Bug 1968026] Re: right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo does work. All works with a PS2 keyboard

2022-04-11 Thread Daniel van Vugt
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)

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

Title:
  right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
  does work. All works with a PS2 keyboard

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


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

[Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]

2022-04-11 Thread Daniel van Vugt
Indeed it's mostly a mutter bug. And even then mutter won't try to use
the missing GAMMA_LUT feature most of the time.

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

Title:
  Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
  KMS update: CRTC property (GAMMA_LUT) not found]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions


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

[Bug 1967885] Re: blanking locks screen although screen lock is disabled

2022-04-11 Thread Daniel van Vugt
> I can add a photo, as your requested, but I wonder whether that would
add anything. The lock screen is simply the log-in screen that
traditionally comes up when the system is booted.

The lock screen and login screen are different, which is why I asked. If
you see the login screen instead of the lock screen then gnome-shell has
crashed. So maybe this is just bug 1968208 (which is bug 1965897).

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

Title:
  blanking locks screen although screen lock is disabled

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


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

[Bug 1964442] Re: Key repeats forever if a shell popover steals focus during a keypress

2022-04-11 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Invalid

** Changed in: gnome-shell (Ubuntu Jammy)
   Status: Won't Fix => Invalid

** No longer affects: gnome-shell (Ubuntu)

** No longer affects: gnome-shell (Ubuntu Jammy)

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

Title:
  Key repeats forever if a shell popover steals focus during a keypress

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1964442/+subscriptions


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

[Bug 1961508] Re: Dock displaying over program after resuming from blank screen

2022-04-11 Thread Daniel van Vugt
Maybe we were too optimistic:

https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/+bug/1917939/comments/18

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

Title:
  Dock displaying over program after resuming from blank screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961508/+subscriptions


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

[Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

2022-04-11 Thread Daniel van Vugt
The fix should be in jammy, but is known to not be in impish. Since you
are the first person to report that it doesn't seem to be working in
jammy, please open a new bug by running:

  ubuntu-bug thunderbird

or

  ubuntu-bug gnome-shell

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

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1932328/+subscriptions


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

[Bug 1968518] Re: FFe: Backport new RDP settings

2022-04-11 Thread Gunnar Hjalmarsson
My first question would be: Can the changes to gnome-remote-desktop be
reverted?

If that's not considered possible/desirable, I'd say that while this is
awfully late for new translatable strings, I think the importance of the
proposed change overweighs that we will see the new strings untranslated
in many languages. Translators will have the opportunity to repair It in
22.04.1.

So from a translators POV I would prefer it to be uploaded ASAP, so the
translators at least are given a chance to get at it (the deadline is on
Thursday 21:00 UTC).

As regards docs, the related GNOME 41 docs (which will shipped with
Ubuntu 22.04) is already not excellent:

https://help.ubuntu.com/stable/ubuntu-help/sharing-desktop.html

All they did so far for GNOME 42 is an additional comment (not visible
to users):

https://gitlab.gnome.org/GNOME/gnome-user-docs/-/commit/b02a44c6

There is also a discussion about improving the docs:

https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues/135

So from a docs POV, the documentation/communication aspect of the change
will result in confusion, which brings me back to the first question:
Can the changes to gnome-remote-desktop be reverted?

** Bug watch added: gitlab.gnome.org/GNOME/gnome-user-docs/-/issues #135
   https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues/135

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1968518

Title:
  FFe: Backport new RDP settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions


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

[Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

2022-04-11 Thread Yves Roggeman
But it is not solved at all! Think to disappointed users, please.

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

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1932328/+subscriptions


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

[Bug 1968518] Re: FFe: Backport new RDP settings

2022-04-11 Thread Łukasz Zemczak
Hey Robert! Can you provide some build logs of the new gnome-control-
center changes (like, maybe a link to a PPA)? It's super late for such
changes, but I'm less worried of regressions than of translators and
documentation people not having enough time to handle these UI changes.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1968518

Title:
  FFe: Backport new RDP settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions


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