[Bug 2076164] ProcEnviron.txt

2024-08-06 Thread prafulla chandra kota
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2076164/+attachment/5803155/+files/ProcEnviron.txt

-- 
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/2076164

Title:
  fingerprint mismatch and disconnect with name

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


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

[Bug 2076164] ProcCpuinfoMinimal.txt

2024-08-06 Thread prafulla chandra kota
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2076164/+attachment/5803154/+files/ProcCpuinfoMinimal.txt

-- 
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/2076164

Title:
  fingerprint mismatch and disconnect with name

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


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

[Bug 2076164] Re: fingerprint mismatch and disconnect with name

2024-08-06 Thread prafulla chandra kota
apport information

** Tags added: apport-collected noble third-party-packages

** Description changed:

  In Ubuntu 24.04 OS, we are unable to enroll 10 fingerprints for a user 
through the GUI. Generally, the GUI displays the names of all 10 fingers, such 
as left little finger, left index finger, etc.
  Before enrolling any fingerprint, it correctly shows all 10 finger names. 
However, once a fingerprint is enrolled, the order becomes clumsy.
  
  For example, if we select 'left little finger' for fingerprint enrollment, 
the enrollment is successful, and the enrolled finger name is shown as 'left 
little finger' (same as selected).
  However, in the remaining list of fingers, a different finger name (like 
'right index finger') is removed, and 'left little finger' still appears in the 
list.
  If we select 'left little finger' again from the list, the existing enrolled 
fingerprint gets overwritten with the new one.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.28.1-0ubuntu3
+ Architecture: amd64
+ CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz 
./casper/minimal.standard.live.hotfix.squashfs 
./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs 
./boot/grub/grub.cfg
+ CasperMD5CheckResult: fail
+ CurrentDesktop: ubuntu:GNOME
+ DistributionChannelDescriptor:
+  # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-noble-oem-24.04b-edge-20240621-8
+ DistroRelease: Ubuntu 24.04
+ InstallationDate: Installed on 2024-08-01 (5 days ago)
+ InstallationMedia: Ubuntu OEM 24.04 LTS "Noble Numbat" - Release amd64 
(20240621)
+ Package: gnome-control-center 1:46.0.1-1ubuntu7
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 6.10.0-1005.5-oem 6.10.0-rc4
+ Tags: noble third-party-packages
+ Uname: Linux 6.10.0-1005-oem x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2076164/+attachment/5803153/+files/Dependencies.txt

-- 
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/2076164

Title:
  fingerprint mismatch and disconnect with name

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


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

[Bug 2076164] [NEW] fingerprint mismatch and disconnect with name

2024-08-06 Thread prafulla chandra kota
Public bug reported:

In Ubuntu 24.04 OS, we are unable to enroll 10 fingerprints for a user through 
the GUI. Generally, the GUI displays the names of all 10 fingers, such as left 
little finger, left index finger, etc.
Before enrolling any fingerprint, it correctly shows all 10 finger names. 
However, once a fingerprint is enrolled, the order becomes clumsy.

For example, if we select 'left little finger' for fingerprint enrollment, the 
enrollment is successful, and the enrolled finger name is shown as 'left little 
finger' (same as selected).
However, in the remaining list of fingers, a different finger name (like 'right 
index finger') is removed, and 'left little finger' still appears in the list.
If we select 'left little finger' again from the list, the existing enrolled 
fingerprint gets overwritten with the new one.
--- 
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz 
./casper/minimal.standard.live.hotfix.squashfs 
./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs 
./boot/grub/grub.cfg
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-noble-oem-24.04b-edge-20240621-8
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-08-01 (5 days ago)
InstallationMedia: Ubuntu OEM 24.04 LTS "Noble Numbat" - Release amd64 
(20240621)
Package: gnome-control-center 1:46.0.1-1ubuntu7
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.10.0-1005.5-oem 6.10.0-rc4
Tags: noble third-party-packages
Uname: Linux 6.10.0-1005-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True

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


** Tags: apport-collected noble third-party-packages

** Attachment added: "fingerprint enrollment issue"
   
https://bugs.launchpad.net/bugs/2076164/+attachment/5803132/+files/Ubuntu%2024.04%20FP%20enroll%20issue%20%281%29.jpg

-- 
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/2076164

Title:
  fingerprint mismatch and disconnect with name

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


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

[Bug 2069565] Re: gnome-shell crashed with SIGSEGV in meta_drm_buffer_get_width() from meta_onscreen_native_flip_crtc() from try_post_latest_swap() from meta_onscreen_native_swap_buffers_with_damage()

2024-08-06 Thread Daniel van Vugt
Not fully fixed. We found a new way it can still crash in 47.beta:
https://gitlab.gnome.org/GNOME/mutter/-/issues/3606#note_2188342

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

** Changed in: mutter (Ubuntu Oracular)
   Status: Fix Committed => In Progress

** Tags removed: fixed-in-mutter-47.beta fixed-upstream

-- 
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/2069565

Title:
  gnome-shell crashed with SIGSEGV in meta_drm_buffer_get_width() from
  meta_onscreen_native_flip_crtc() from try_post_latest_swap() from
  meta_onscreen_native_swap_buffers_with_damage() from
  cogl_onscreen_swap_buffers_with_damage()

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


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

[Bug 2076159] [NEW] HEIC failed to load 200Mpx images

2024-08-06 Thread Kirill Shustov
Public bug reported:


I have an issue with viewing large HEIC files from my phone s24 ultra.

50 MPx filex are showing, not so fast as jpeg, but it works fine, 200
MPx files cause blinking eog and broken UI, program can be closed only
by killing process (xkill or kill -9 pid)

I have added 3 files in 12 50 200 MPx and eog screenshot.
https://www.dropbox.com/scl/fo/e9mp4wb2akr578da8zyuu/ADT2ieu-
DThdStTtCfSRIdc?rlkey=dsmru7cs6y3lbeduqsspqk9lp=0

list of installled libraries:

➜  ~ apt list | grep heif  
heif-gdk-pixbuf/noble,now 1.17.6-1ubuntu4 amd64 [installed]
heif-gdk-pixbuf/noble 1.17.6-1ubuntu4 i386
heif-thumbnailer/noble,now 1.17.6-1ubuntu4 amd64 [installed]
heif-thumbnailer/noble 1.17.6-1ubuntu4 i386
kodi-imagedecoder-heif/noble 20.1.0+ds1-3build1 amd64
libheif-dev/noble 1.17.6-1ubuntu4 amd64
libheif-dev/noble 1.17.6-1ubuntu4 i386
libheif-examples/noble,now 1.17.6-1ubuntu4 amd64 [installed]
libheif-examples/noble 1.17.6-1ubuntu4 i386
libheif-plugin-aomdec/noble,now 1.17.6-1ubuntu4 amd64 [installed,automatic]
libheif-plugin-aomdec/noble 1.17.6-1ubuntu4 i386
libheif-plugin-aomenc/noble,now 1.17.6-1ubuntu4 amd64 [installed]
libheif-plugin-aomenc/noble 1.17.6-1ubuntu4 i386
libheif-plugin-dav1d/noble 1.17.6-1ubuntu4 amd64
libheif-plugin-dav1d/noble 1.17.6-1ubuntu4 i386
libheif-plugin-ffmpegdec/noble 1.17.6-1ubuntu4 amd64
libheif-plugin-ffmpegdec/noble 1.17.6-1ubuntu4 i386
libheif-plugin-j2kdec/noble 1.17.6-1ubuntu4 amd64
libheif-plugin-j2kdec/noble 1.17.6-1ubuntu4 i386
libheif-plugin-j2kenc/noble 1.17.6-1ubuntu4 amd64
libheif-plugin-j2kenc/noble 1.17.6-1ubuntu4 i386
libheif-plugin-jpegdec/noble 1.17.6-1ubuntu4 amd64
libheif-plugin-jpegdec/noble 1.17.6-1ubuntu4 i386
libheif-plugin-jpegenc/noble 1.17.6-1ubuntu4 amd64
libheif-plugin-jpegenc/noble 1.17.6-1ubuntu4 i386
libheif-plugin-libde265/noble,now 1.17.6-1ubuntu4 amd64 [installed,automatic]
libheif-plugin-libde265/noble 1.17.6-1ubuntu4 i386
libheif-plugin-rav1e/noble 1.17.6-1ubuntu4 amd64
libheif-plugin-svtenc/noble 1.17.6-1ubuntu4 amd64
libheif-plugin-svtenc/noble 1.17.6-1ubuntu4 i386
libheif-plugin-x265/noble 1.17.6-1ubuntu4 amd64
libheif-plugin-x265/noble 1.17.6-1ubuntu4 i386
libheif1/noble,now 1.17.6-1ubuntu4 amd64 [installed]
libheif1/noble 1.17.6-1ubuntu4 i386
librust-libheif-rs-dev/noble 0.20.0-5 amd64
librust-libheif-sys-dev/noble 1.16.2-5 amd64

I also tried gThumb and have same issue, looks like problem not directly
related to HEIC format, but to too huge file resolution.

my mashine

Ubuntu 24.04 LTS x86_64 
6.9.12-060912-generic
GNOME 46.0
Metacity

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: eog 45.3-1ubuntu2
Uname: Linux 6.9.12-060912-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME-Flashback:GNOME
Date: Tue Aug  6 10:55:33 2024
ExecutablePath: /usr/bin/eog
SourcePackage: eog
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble

** Attachment added: "file examples"
   https://bugs.launchpad.net/bugs/2076159/+attachment/5803119/+files/heif.zip

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

Title:
  HEIC failed to load 200Mpx images

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


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

[Bug 2069565] Re: gnome-shell crashed with SIGSEGV in meta_drm_buffer_get_width() from meta_onscreen_native_flip_crtc() from try_post_latest_swap() from meta_onscreen_native_swap_buffers_with_damage()

2024-08-05 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu Oracular)
   Status: In Progress => Fix Committed

** Tags added: fixed-in-mutter-47.beta fixed-upstream

-- 
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/2069565

Title:
  gnome-shell crashed with SIGSEGV in meta_drm_buffer_get_width() from
  meta_onscreen_native_flip_crtc() from try_post_latest_swap() from
  meta_onscreen_native_swap_buffers_with_damage() from
  cogl_onscreen_swap_buffers_with_damage()

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


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

[Bug 2076109] Re: Audio randomly cuts out via hdmi with external monitor

2024-08-05 Thread Daniel van Vugt
** Package changed: mutter (Ubuntu) => linux (Ubuntu)

** Tags added: noble

-- 
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/2076109

Title:
  Audio randomly cuts out via hdmi with external monitor

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


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

[Bug 2076142] [NEW] List of unenrolled fingerprint to add shows wrong fingers

2024-08-05 Thread Yao Wei
Public bug reported:

On gnome-control-center 1:46.0.1-1ubuntu7 in Ubuntu 24.04, the list of
unenrolled fingers are wrong due to a filtering bug

Reproducible steps:
Enroll "Left ring finger" in a fingerprint-enabled system.

Expected:
The list in "Scan new fingerprint" hides "Left ring finger".

Actual:
The list in "Scan new fingerprint" shows "Left ring finger", instead "Left 
index finger" is hidden.

A known patch exists to fix this issue:
https://gitlab.gnome.org/GNOME/gnome-control-
center/-/commit/3b7ea05d43c0dce4201279d5945488795b66bce7

** Affects: oem-priority
 Importance: Undecided
 Status: New

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


** Tags: oem-priority

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Tags added: oem-priority

-- 
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/2076142

Title:
  List of unenrolled fingerprint to add shows wrong fingers

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2076142/+subscriptions


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

[Bug 2075983] Re: Strange behaviors with external displays over Displaylink

2024-08-05 Thread Daniel van Vugt
Was the dock still connected when you tested HDMI? If so then it might
be keeping the machine awake like a USB mouse would. You can tune that
in:

  sudo apt install powertop
  sudo powertop

under the 'WakeUp' tab.

As for changing the defaults, I've just looked upstream and found 'lid-
close-suspend-with-external-monitor' does not exist. So I looked in the
Ubuntu source code and found 'lid-close-suspend-support.patch' which
adds that setting to the schema, but doesn't seem to implement it in
code. So I think it's dead code :(



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

-- 
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/2075983

Title:
  Strange behaviors with external displays over Displaylink

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


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

[Bug 2070082] Re: Ubuntu freezes and logs out

2024-08-05 Thread Daniel van Vugt
egrsite, please open a new bug at:
https://bugs.launchpad.net/ubuntu/+source/kwin/+filebug

-- 
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/2070082

Title:
  Ubuntu freezes and logs out

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


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

[Bug 2072761] Re: Stuck arrow keys after switching workspaces

2024-08-05 Thread Daniel van Vugt
No problem. It looks like I added "arrow" just to clarify for duplicate
bug reports that this was the first one to report the issue, which most
people associate with arrow keys. So it helps them to find this bug and
avoid logging more duplicates.

-- 
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/2072761

Title:
  Stuck arrow keys after switching workspaces

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


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

[Bug 2068539] Re: tiling operation triggers assertion in gnome-shell [meta_window_get_workspaces: code should not be reached]

2024-08-05 Thread Daniel van Vugt
In progress here:
https://github.com/Leleat/Tiling-Assistant/issues/329#issuecomment-2269802471

** Changed in: gnome-shell-extension-tiling-assistant (Ubuntu)
   Status: Confirmed => In Progress

-- 
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/2068539

Title:
  tiling operation triggers assertion in gnome-shell
  [meta_window_get_workspaces: code should not be reached]

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


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

[Bug 2020249] Re: Missing Wayland login option on NVIDIA desktops

2024-08-05 Thread Daniel van Vugt
This should be fixed already in 24.04 for example(?)

** Changed in: gdm3 (Ubuntu)
   Status: Opinion => Incomplete

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

Title:
  Missing Wayland login option on NVIDIA desktops

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


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

[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

2024-08-05 Thread Martin Paulo
This was driving me dilly after I upgraded to 24.04. It took me a lot of
searching and trial to work out that this was happening because I was
using my fingerprint to unlock my machine on power up. The Gnome
Fingerprint subsystem does *not* unlock the keyring, for reasons
explained here: https://mjg59.dreamwidth.org/68537.html

So: on a power on, use a password to login, and from then on, you can
use your fingerprint to unlock the machine.

I'm placing this comment here, as this page was my top search result
when I was trying to solve this issue: and I'd like to save others who
made my foolish mistake time.

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

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


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

[Bug 2049923] Re: gnome-terminal freezing, then crashing

2024-08-05 Thread Alfonso Muñoz-Pomer Fuentes
This bug also happens when you create a new tab and try to detach right after. 
I reported it to the Gnome Terminal team, but they’re aware of it:
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/8086

In the meantime I’ll disable the Show scroll bar option.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #8086
   https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/8086

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

Title:
  gnome-terminal freezing, then crashing

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


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

[Bug 2064698] Re: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get [### Promise created here: ### getProperty@file:///usr/share/gnome-shell/extensions/ubuntu-appindi

2024-08-05 Thread Alessandro Astone
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
 Assignee: (unassigned) => Alessandro Astone (aleasto)

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

Title:
  Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error
  occurred in Get [### Promise created here: ###
  getProperty@file:///usr/share/gnome-shell/extensions/ubuntu-
  appindicat...@ubuntu.com/dbusProxy.js:89:33]

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


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

[Bug 2070082] Re: Ubuntu freezes and logs out

2024-08-05 Thread egrsite
Audio randomly cuts out via hdmi with external monitor...

Background audio coming from browsers (firefox, opera, etc...) or vlc,
the audio cuts out randomly as if there was a lag. This only happens
with audio via hdmi, the integrated audio of the laptop (ASUS K550J)
works very smoothly and correctly.

The error persists with any desktop, X11, Waydland
 My Setup:


-Equipo-
Procesador  : Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz
Memoria : 11681MB (4514MB usados)
Tipo de equipo  : Mini portatil
Sistema operativo   : Ubuntu 24.04 LTS
-Pantalla-
Resolución  : 1360x768 pixels
Renderizador OpenGL : Mesa Intel(R) Iris(R) Pro Graphics P5200 (HSW 
GT3)
Proveedor X11   : The X.Org Foundation
-Dispositivos de audio-
Adaptador de audio  : HDA-Intel - HDA Intel PCH
Adaptador de audio  : HDA-Intel - HDA Intel HDMI
-Dispositivos de entrada-
 Lid Switch
 Sleep Button
 Power Button
 AT Translated Set 2 keyboard
 FocalTechPS/2 FocalTech Touchpad
 SIGMACHIP USB Keyboard
 SIGMACHIP USB Keyboard Consumer Control
 SIGMACHIP USB Keyboard System Control
 Asus Wireless Radio Control
 Asus WMI hotkeys
 HDA Intel PCH Mic
 HDA Intel PCH Headphone
 Video Bus
 Video Bus
 USB2.0 VGA UVC WebCam: USB2.0 V
 HDA Intel HDMI HDMI/DP,pcm:3
 HDA Intel HDMI HDMI/DP,pcm:7
 HDA Intel HDMI HDMI/DP,pcm:8
 Telink Wireless Receiver Mouse
 Telink Wireless Receiver Consumer Control
 Telink Wireless Receiver System Control
 Telink Wireless Receiver
-Discos SCSI-
HL-DT-ST DVDRAM GUE1N
ATA KINGSTON SA400S3


** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2070082/+attachment/5802966/+files/journal.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/2070082

Title:
  Ubuntu freezes and logs out

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


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

[Bug 2076109] [NEW] Audio randomly cuts out via hdmi with external monitor

2024-08-05 Thread egrsite
Public bug reported:

Background audio coming from browsers (firefox, opera, etc...) or vlc,
the audio cuts out randomly as if there was a lag. This only happens
with audio via hdmi, the integrated audio of the laptop (ASUS K550J)
works very smoothly and correctly.

The error persists with any desktop, X11, Waydland
 My Setup:


-Equipo-
Procesador  : Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz
Memoria : 11681MB (4514MB usados)
Tipo de equipo  : Mini portatil
Sistema operativo   : Ubuntu 24.04 LTS
-Pantalla-
Resolución  : 1360x768 pixels
Renderizador OpenGL : Mesa Intel(R) Iris(R) Pro Graphics P5200 (HSW 
GT3)
Proveedor X11   : The X.Org Foundation
-Dispositivos de audio-
Adaptador de audio  : HDA-Intel - HDA Intel PCH
Adaptador de audio  : HDA-Intel - HDA Intel HDMI
-Dispositivos de entrada-
 Lid Switch
 Sleep Button
 Power Button
 AT Translated Set 2 keyboard
 FocalTechPS/2 FocalTech Touchpad
 SIGMACHIP USB Keyboard
 SIGMACHIP USB Keyboard Consumer Control
 SIGMACHIP USB Keyboard System Control
 Asus Wireless Radio Control
 Asus WMI hotkeys
 HDA Intel PCH Mic
 HDA Intel PCH Headphone
 Video Bus
 Video Bus
 USB2.0 VGA UVC WebCam: USB2.0 V
 HDA Intel HDMI HDMI/DP,pcm:3
 HDA Intel HDMI HDMI/DP,pcm:7
 HDA Intel HDMI HDMI/DP,pcm:8
 Telink Wireless Receiver Mouse
 Telink Wireless Receiver Consumer Control
 Telink Wireless Receiver System Control
 Telink Wireless Receiver
-Discos SCSI-
HL-DT-ST DVDRAM GUE1N
ATA KINGSTON SA400S3

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

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/bugs/2076109/+attachment/5802965/+files/journal.txt

-- 
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/2076109

Title:
  Audio randomly cuts out via hdmi with external monitor

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


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

[Bug 2072761] Re: Stuck arrow keys after switching workspaces

2024-08-05 Thread Magnus Johansson
As the summary was changed from "Stuck keys ..." to "Stuck arrow
keys..." I just want to stress that even if maybe is that the arrow keys
are more likely to get "stuck", I have on several occasions got a
"stuck" Ctrl or Alt key as well.

E.g. shifting to a workplace with an chrome browser just to realize that
scrolling down using the mouse scroll wheel instead zooms the page (as
if Ctrl is still pressed).

-- 
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/2072761

Title:
  Stuck arrow keys after switching workspaces

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


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

[Bug 2075983] Re: Strange behaviors with external displays over Displaylink

2024-08-05 Thread Jesse M Darnley
I'll test the scaling issue again, as I'm now unable to replicate the
same scenario I had last week when opening this report.

To focus on the suspend issue, I would echo the case that was made to
me: when it comes to what many users will define as expected behavior
they're going to be looking at Windows and macOS as well.

On Windows the default behavior for lid close is to put the laptop into
suspend, even if it is connected to external displays. This behavior has
to be manually overridden. Similarly, on macOS the default behavior on
lid close is also to enter suspend as well. The one notable change is
that for a brief window of time, keyboard and mouse movements will wake
the laptop on the connected displays. All of that said, I think if we
just exposed that setting in the GUI somewhere as you mentioned, that
would be a perfect compromise.

Unfortunately in my case changing that setting has not changed the
behavior I'm seeing. I still get the behavior of the internal display
shutting off but the laptop remaining active. This is happening with the
laptop directly connected via on-board HDMI as well, so my assumption
that it was DisplayLink related may be a red herring.

-- 
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/2075983

Title:
  Strange behaviors with external displays over Displaylink

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


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

[Bug 2076101] [NEW] Gnome openvpn saves authenticator code as password

2024-08-05 Thread Douglas Moura
Public bug reported:

I added a VPN connection through Gnome settings. I configured the user
and password. Once I try to connect, as I've already set the user and
password, I'm only asked to inform the authentication code, as the VPN
has MFA enabled. After I inform the authentication code, I'm able to
connect to the VPN. If I disconnect and try to connect again, the
authentication code was saved as if it was the password, so my
authentication fails and I have to inform my password first, then after
that I'm asked for the authentication code. The authentication code is
being saved as the password, which shouldn't happen. Everything works
but it's pretty annoying having to do that every time. I have another
machine running Debian Trixie, which used to have the network-manager-
openvpn in the same version and it used to happen the same thing. Now
that it's updated to network-manager-openvpn (1.12.0-1) this issue is
gone, probably fixed.

doug@bolado:~$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04

doug@bolado:~$ apt-cache policy network-manager-openvpn-gnome
network-manager-openvpn-gnome:
  Installed: 1.10.2-4build2
  Candidate: 1.10.2-4build2
  Version table:
 *** 1.10.2-4build2 500
500 http://br.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: network-manager-openvpn-gnome 1.10.2-4build2
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug  5 10:23:18 2024
InstallationDate: Installed on 2024-07-17 (19 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

** Description changed:

  I added a VPN connection through Gnome settings. I configured the user
- and passwords. Once I try to connect, as I've already set the user and
+ and password. Once I try to connect, as I've already set the user and
  password, I'm only asked to inform the authentication code, as the VPN
  has MFA enabled. After I inform the authentication code, I'm able to
  connect to the VPN. If I disconnect and try to connect again, the
  authentication code was saved as if it was the password, so my
  authentication fails and I have to inform my password first, then after
- that I'm asked for the authentication code. Everything works but it's
- pretty annoying having to do that every time. I have another machine
- running Debian Trixie, which used to have the network-manager-openvpn in
- the same version and it used to happen the same thing. Now that it's
- updated to network-manager-openvpn (1.12.0-1) this issue is gone,
- probably fixed.
+ that I'm asked for the authentication code. The authentication code is
+ being saved as the password, which shouldn't happen. Everything works
+ but it's pretty annoying having to do that every time. I have another
+ machine running Debian Trixie, which used to have the network-manager-
+ openvpn in the same version and it used to happen the same thing. Now
+ that it's updated to network-manager-openvpn (1.12.0-1) this issue is
+ gone, probably fixed.
  
  doug@bolado:~$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 24.04 LTS
  Release:  24.04
  
- 
  doug@bolado:~$ apt-cache policy network-manager-openvpn-gnome
  network-manager-openvpn-gnome:
-   Installed: 1.10.2-4build2
-   Candidate: 1.10.2-4build2
-   Version table:
-  *** 1.10.2-4build2 500
- 500 http://br.archive.ubuntu.com/ubuntu noble/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.10.2-4build2
+   Candidate: 1.10.2-4build2
+   Version table:
+  *** 1.10.2-4build2 500
+ 500 http://br.archive.ubuntu.com/ubuntu noble/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager-openvpn-gnome 1.10.2-4build2
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  5 10:23:18 2024
  InstallationDate: Installed on 2024-07-17 (19 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  

[Bug 1199267] Re: Evolution is in offline mode when VPN is used

2024-08-05 Thread sennoriaas
Their process is simple and efficient: customers can call or text a picture of 
the items they want removed, and Junk Ryde provides a free estimate. They pride 
themselves on offering affordable prices and a hassle-free experience. 
https://junkryde.com/

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

Title:
  Evolution is in offline mode when VPN is used

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


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

[Bug 1969198] Re: 42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card

2024-08-05 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1968929 ***
https://bugs.launchpad.net/bugs/1968929

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

** Changed in: gdm3 (Ubuntu)
   Status: New => Confirmed

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

Title:
  42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card

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


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

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-08-05 Thread Raffaele Rialdi
I already did it few days ago after reading the links, thank you for confirming 
that.
If it happens again, I'll send you the log.
Thanks!

-- 
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/2075525

Title:
  After screen blank, the displays configuration gets lost

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


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

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-08-05 Thread Daniel van Vugt
Please try:

  gnome-extensions disable tiling-assist...@ubuntu.com

and log in again. If that doesn't fix the problem then next time it
happens please run:

  journalctl -b0 > journal.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/2075525

Title:
  After screen blank, the displays configuration gets lost

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


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

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-08-05 Thread Raffaele Rialdi
I agree it would make sense.
Basically you are saying that the fixes I applied resolve the bug of resetting 
to the default configuration which leads to (let's assume) the mirror 
configuration.
If this is correct, why the configuration in the display at this point still 
shows me the "Extended" configuration instead of the current mirror 
configuration?
It looks like the config and shown in the display window is out of sync with 
the currently applied settings.

-- 
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/2075525

Title:
  After screen blank, the displays configuration gets lost

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


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

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-08-05 Thread Daniel van Vugt
I can't remember if mirror mode is the expected default for when the
system doesn't recognise a set of monitors. If it's not the default then
it would be harder to explain...

Did you try comment #3?

-- 
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/2075525

Title:
  After screen blank, the displays configuration gets lost

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


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

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-08-05 Thread Raffaele Rialdi
Thank you Daniel. I verified that this morning the installed updates
also contained the list of updates you pointed to me.

What about the configuration swithching to mirror?
Is there any workaround for this?

Thanks!

-- 
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/2075525

Title:
  After screen blank, the displays configuration gets lost

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


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

[Bug 2076030] Re: Apps are working slowly

2024-08-05 Thread Daniel van Vugt
Thanks for the bug report. Please run:

  ps auxw > ps.txt
  journalctl -b0 > journal.txt

and attach the resulting text files here.


** 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/2076030

Title:
  Apps are working slowly

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


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

[Bug 2075983] Re: Strange behaviors with external displays over Displaylink

2024-08-05 Thread Daniel van Vugt
By the way, DisplayLink has a significant performance penalty. For the
best performance I recommend either:

 * A Thunderbolt dock that doesn't require DisplayLink drivers (but does 
require a Thunderbolt port); or
 * A USB-C to whatever adapter cable so your GPU can talk directly to the 
monitor.

-- 
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/2075983

Title:
  Strange behaviors with external displays over Displaylink

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


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

[Bug 2074559] Re: [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered with black flickering rectangle

2024-08-04 Thread Daniel van Vugt
I'm wondering if it keeps reverting to a less than ideal display mode.
Xrandr.txt says the preferred mode is 59.85Hz, but monitors.xml has
stored 59.883. Does the monitor have a menu in which you
can find out the current refresh rate?

Also please look in Settings > Displays and check if you get an 'Adjust
for TV' option. If so then try enabling it.

-- 
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/2074559

Title:
  [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered
  with black flickering rectangle

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


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

[Bug 2074559] Re: [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered with black flickering rectangle

2024-08-04 Thread Daniel van Vugt
** Summary changed:

- [nouveau] Top margin of secondary monitor covered with black flickering 
rectangle
+ [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered with 
black flickering rectangle

-- 
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/2074559

Title:
  [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered
  with black flickering rectangle

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


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

[Bug 2074099] Re: [ThinkPad T495s] Screen Brightness goes to 0 waking from sleep

2024-08-04 Thread Daniel van Vugt
** Summary changed:

- Screen Brightness goes to 0 waking from sleep
+ [ThinkPad T495s] Screen Brightness goes to 0 waking from sleep

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

Title:
  [ThinkPad T495s] Screen Brightness goes to 0 waking from sleep

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


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

[Bug 2068117] Re: Gnome desktop didn't process HID events

2024-08-04 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

-- 
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/2068117

Title:
  Gnome desktop didn't process HID events

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


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

[Bug 2068121] Re: My system lagging, become slow after installing ubuntu 22.04

2024-08-04 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

-- 
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/2068121

Title:
  My system lagging, become slow after installing ubuntu 22.04

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


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

[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)

2024-08-04 Thread Daniel van Vugt
** Description changed:

  [ Impact ]
  
  GNOME Wayland session crashes with
  
libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor:
  assertion failed: (logical_monitor)
  
  Upstream Mutter release 46.1 resolved ONE cause of this assertion
  failure, but apparently not all causes. So we are separating the two
  scenarios of Tiling Assistant active and disabled. The Mutter fix only
  addresses the crash when Tiling Assistant is disabled.
  
- [ Test Plan ]
+ [ Test Plan for the Mutter fix ]
  
  This needs more detail and community help...
  
  On a machine that was previously affected by the crash...
  1. gnome-extensions disable tiling-assist...@ubuntu.com
  2. Disconnect the HDMI cable
  
  Expect: The shell has not crashed and continues to function.
+ 
+ [ Test Plan for the Tiling Assistant fix ]
+ 
+ TODO
  
  [ Where problems could occur ]
  
  Potentially anywhere in Gnome Shell. Judging by the fix it relates to
  automatic window placement when monitors are added and removed.
  
  [ Original description ]
  
  I am observing multiple issues with external monitor in a hybrid system
  (laptop) with Intel GPU and NVIDIA GPU in a Gnome session:
  
  - Disconnecting HDMI cable crashes the desktop to login screen
  
  The HDMI port is connected to NVIDIA. I use the latest updates and
  drivers of 22.04 LTS.
  
  I am not sure how to auto-report this with ubuntu-bug. The system is
  similar to this report:
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291

-- 
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/2050865

Title:
  GNOME Wayland session crashes with
  
libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor:
  assertion failed: (logical_monitor)

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


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

[Bug 2075983] Re: Strange behaviors with external displays over Displaylink

2024-08-04 Thread Daniel van Vugt
Thanks for the bug report but that's two separate issues. It's likely
the scale issue is just from using a Xorg session when you need to be
using Wayland to scale displays independently.

Please confirm which issue you would like this bug to be about and also
run:

  apport-collect 2075983

on the affected machine.


** Tags added: evdi noble

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

** Tags added: displaylink multimonitor

-- 
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/2075983

Title:
  Strange behaviors with external displays over Displaylink

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


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

[Bug 2075983] Re: Strange behaviors with external displays over Displaylink

2024-08-04 Thread Daniel van Vugt
Come to think of it, closing the lid should NOT invoke suspend. A lot of
people like to plug in an external monitor, close the laptop lid and
keep using the laptop as a desktop. So it shouldn't suspend by default
when an external monitor is connected.

And now I've found the setting. Just run:

  gsettings set org.gnome.settings-daemon.plugins.power lid-close-
suspend-with-external-monitor true

I wonder why this isn't configurable in the Settings app...

-- 
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/2075983

Title:
  Strange behaviors with external displays over Displaylink

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


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

[Bug 2076038] [NEW] pop up

2024-08-04 Thread Hans Sagner
Public bug reported:




```
Das GNU-Bildbearbeitungsprogramm version 2.10.30
git-describe: GIMP_2_10_30
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
11.4.0-1ubuntu1~22.04' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-11 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-11-XeT9lY/gcc-11-11.4.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-XeT9lY/gcc-11-11.4.0/debian/tmp-gcn/usr
 --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu 
--with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) 

# Libraries #
using babl version 0.1.92 (compiled against version 0.1.92)
using GEGL version 0.4.34 (compiled against version 0.4.34)
using GLib version 2.72.4 (compiled against version 2.72.4)
using GdkPixbuf version 2.42.8 (compiled against version 2.42.8)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.6 (compiled against version 1.50.6)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> GIMP-KRITISCH: gimp_tool_button_release: assertion 'GIMP_IS_DISPLAY 
> (display)' failed

Stack trace:
```

# Stack traces obtained from PID 16614 - Thread 16614 #

[New LWP 16617]
[New LWP 16618]
[New LWP 16619]
[New LWP 16620]
[New LWP 16621]
[New LWP 16622]
[New LWP 16624]
[New LWP 16625]
[New LWP 16628]
[New LWP 16694]
[New LWP 37812]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=256, buf=0x7ffe8cadcb40, fd=18) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id  Frame 
* 1Thread 0x718a5f4b6e80 (LWP 16614) "gimp-2.10"  __GI___libc_read 
(nbytes=256, buf=0x7ffe8cadcb40, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x718a5cbe8640 (LWP 16617) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x718a5c3e7640 (LWP 16618) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x718a5bbe6640 (LWP 16619) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x718a5b3e5640 (LWP 16620) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x718a5abe4640 (LWP 16621) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x718a5a3e3640 (LWP 16622) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x718a58ee0640 (LWP 16624) "gmain"  0x718a5e318bcf in 
__GI___poll (fds=0x59e62ab4a190, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  9Thread 0x718a4bfff640 (LWP 16625) "gdbus"  0x718a5e318bcf in 
__GI___poll (fds=0x59e62ab64850, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  10   Thread 0x718a59be2640 (LWP 16628) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x718a237fe640 (LWP 16694) "swap writer"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7189fcbe9640 (LWP 37812) "pool-gimp-2.10" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 12 (Thread 0x7189fcbe9640 (LWP 37812) "pool-gimp-2.10"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x718a5e5ee0ac in g_cond_wait_until () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x718a5e56e3e1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x718a5e56e566 in g_async_queue_timeout_pop () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x718a5e5d07b9 in  () at 

[Bug 2074099] Re: Screen Brightness goes to 0 waking from sleep

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

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

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

Title:
  Screen Brightness goes to 0 waking from sleep

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


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

[Bug 2076030] [NEW] Apps are working slowly

2024-08-04 Thread Anastasia Shestipalova
Public bug reported:

Apps such as Chrome are working slowly and stop responding after 5
minutes of use

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2.1
ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug  4 14:17:09 2024
DisplayManager: gdm3
InstallationDate: Installed on 2024-02-10 (175 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
RelatedPackageVersions: mutter-common 42.9-0ubuntu8
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/2076030

Title:
  Apps are working slowly

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


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

[Bug 2065646] Re: 1- Snap grid bug 2- file manager always shows "1"

2024-08-03 Thread Launchpad Bug Tracker
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Incomplete => Expired

-- 
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/2065646

Title:
  1- Snap grid bug 2- file manager always shows "1"

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


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

[Bug 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind

2024-08-03 Thread Timur Shaidulin
Noble user here.
I never tried any beta packages and updated mutter packages to 46.2 yesterday 
and now I have the following situation: 
1) bug with edge detect when trying to resize the window — can reproduce
2) any click-through bugs — can't reproduce

But now even autologin disabled doesn't help, only killing
mutter-x11-fram helps.

-- 
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/2026194

Title:
  When clicking on some maximized or tiled windows, focus on roughly the
  lower quarter falls to the window behind

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


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

[Bug 2072761] Re: Stuck arrow keys after switching workspaces

2024-08-03 Thread Vlad Arialin
Hi Daniel, thanks for you suggestion. I tried disabling all the
extensions and re-logging, but to no success - the stuck key is still
there, infinitely scrolling after a workspace switch.

-- 
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/2072761

Title:
  Stuck arrow keys after switching workspaces

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


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

[Bug 2075983] [NEW] Strange behaviors with external displays over Displaylink

2024-08-02 Thread Jesse M Darnley
Public bug reported:

Release: Ubuntu 24.04 LTS
gnome-shell:
  Installed: 46.0-0ubuntu6~24.04.1

Expected behavior (As seen on Windows/macOS):
  * When plugging in external displays, they should be able to scale 
independently of the internal display
  * When external displays are active through a display link dock, closing the 
laptop lid should invoke suspend

The above behavior would match the behavior seen when displays are
connected directly to the laptop.

Actual behavior:
  * External displays connected through a DisplayLink dock are forced to the 
same scaling ratio
  * Closing the laptop lid when external displays are connected through a 
display link dock results in the internal display turning off but no sleep 
behavior
* This happens regardless of config changes with dconf, upower, or logind

This is primarily a usability issue for laptops with limited ports for
IO and extremely high resolution internal panels.

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

-- 
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/2075983

Title:
  Strange behaviors with external displays over Displaylink

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


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

[Bug 2075975] [NEW] Can't use arrow keys to navigate directory with just 1 file

2024-08-02 Thread Rolf
Public bug reported:

If you use keyboard navigation to open a directory that has just a
single file, the arrow keys do nothing.

For example, if you have 2 files, when the directory is opened, nothing
is highlighted, and you can press  to highlight the 2nd file, and
then  to highlight the first file.

If you try that when there is only a single file, nothing happens.

I'm aware that you can press  to highlight the first file
regardless of the number of files in the directory.

So, I have 2 issues:

(1) I would have expected  to highlight the first file in a directory 
with just 1 file.
(2) I would have expected the first file to be highlighted automatically if 
keyboard navigation was used to open the directory.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug  2 14:50:53 2024
GsettingsChanges:
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'extra-large'"
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2024-07-31 (2 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=screen-256color
 XDG_RUNTIME_DIR=
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


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

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

Title:
  Can't use arrow keys to navigate directory with just 1 file

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


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

[Bug 1740279] Re: Two keyring login prompts "access prompt want to inhibit shortcuts"

2024-08-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Two keyring login prompts "access prompt want to inhibit shortcuts"

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


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

[Bug 1587154] Re: --working-directory does not work anymore

2024-08-02 Thread Benjamin La Madrid
The --help command isn't very clear about this, but the feature does
work when you put the "--working-directory" option BEFORE AN EXPLICIT "
--window" option.

However, the tilde "~" symbol may or may not work, depending on the
environment where the terminal is launched from. For example, I wanted
to open a terminal at my home's desktop folder using a keyboard
shortcut. I found that my window manager's keyboard shortcuts settings
does not parse the tilde correctly, so my workaround was this:

gnome-terminal --working-directory=/home/USERNAME/desktop --window

Replacing USERNAME with the username of my own.

I hope this clears the confusion for all gnome-terminal users hereon. It
does work, it just has some quirks to it.

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

Title:
  --working-directory does not work anymore

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


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

[Bug 2065294] Re: Diagnostics settings flips to Never without any user action

2024-08-02 Thread Benjamin Drung
The fix: https://salsa.debian.org/gnome-team/gnome-control-
center/-/merge_requests/36

-- 
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/2065294

Title:
  Diagnostics settings flips to Never without any user action

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


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

[Bug 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind

2024-08-02 Thread Nibl
I am unsure now. I received updates to a bunch of Mutter-related
packages along with Mutter itself either last night or the night before,
upgrading it from 6.0 to 6.2. I had tried the 'beta' packages earlier on
which did the same but did not fix the issue, so I reverted them back to
their originals. This upgrade, however, seems to have resolved the
issue. I tried to click through several applications that I can normally
reproduce the issue with immediately and the bug is refusing to show
itself. Even the bugs where a single click on empty space minimizes the
windows of certain applications and hovering over the edges refuses to
detect that I'm trying to resize them are gone. I'll report back if
clicks fall through again at any point in the future, but for now I
can't reproduce it anymore.

-- 
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/2026194

Title:
  When clicking on some maximized or tiled windows, focus on roughly the
  lower quarter falls to the window behind

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-08-02 Thread Jackson Smith
Sorry, you'd asked about that, before.

My secondary monitor shows no signal if the resolution is anything but
the maximum, native resolution of the screen.

Changing the refresh rate may temporarily restore drawing to the full
screen. However, locking the screen and then allowing it to sleep will
trigger another black region at the top of the screen. The effect of
different refresh rates is to change the width of the screen. For
example, the secondary monitor can run at 120Hz, in which case the black
region fills half of the screen, rather than a small slice, as it does
at around 60Hz.

-- 
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/2074559

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2075526] Re: Ubuntu 24.04 LTS - Monitor freeze in multi-monitor setup

2024-08-02 Thread francesco
Thanks, Daniel, I'll do it!

-- 
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/2075526

Title:
  Ubuntu 24.04 LTS - Monitor freeze in multi-monitor setup

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


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

[Bug 2065294] Re: Diagnostics settings flips to Never without any user action

2024-08-02 Thread Alessandro Astone
** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Fix Committed

** Also affects: gnome-control-center (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: gnome-control-center (Ubuntu Noble)
   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/2065294

Title:
  Diagnostics settings flips to Never without any user action

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


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

[Bug 2075350] Re: gnome-shell seems to hang on monitor disconnect, killing gnome-shell process helps to bring system to life

2024-08-02 Thread Daniel van Vugt
Please try the fix to bug 2050865. If you don't already have the update, please 
follow:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2050865/comments/44

-- 
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/2075350

Title:
  gnome-shell seems to hang on monitor disconnect, killing gnome-shell
  process helps to bring system to life

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


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

[Bug 2075526] Re: Ubuntu 24.04 LTS - Monitor freeze in multi-monitor setup

2024-08-02 Thread Daniel van Vugt
Thanks for the bug report. Next time the problem happens, immediately
after rebooting run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

** Tags added: multimonitor

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

** 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/2075526

Title:
  Ubuntu 24.04 LTS - Monitor freeze in multi-monitor setup

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


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

[Bug 2018158] Re: [Multi Monitor] Built-in screen gets enabled changing the entire layout after resuming from the lockscreen

2024-08-02 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.

Ubuntu 23.04 (lunar) reached end-of-life on January 25, 2024.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: mutter (Ubuntu)
   Status: New => Won't Fix

-- 
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/2018158

Title:
  [Multi Monitor] Built-in screen gets enabled changing the entire
  layout after resuming from the lockscreen

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


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

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-08-02 Thread Daniel van Vugt
If the problem still happens after that then try:

  gnome-extensions disable tiling-assist...@ubuntu.com

and log in again.

-- 
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/2075525

Title:
  After screen blank, the displays configuration gets lost

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


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

[Bug 2075525] Re: After screen blank, the displays configuration gets lost

2024-08-02 Thread Daniel van Vugt
The crash is probably bug 2050865 which is rolling out in automatic updates 
this week. And since you're using Xorg it's possible that crash is happening 
even more often than you know, because gnome-shell will just automatically 
restart on Xorg with apps still running. So if you don't already have the 
update, please follow:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2050865/comments/44


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

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

** Tags added: multimonitor suspend-resume

-- 
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/2075525

Title:
  After screen blank, the displays configuration gets lost

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


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

[Bug 2075526] [NEW] Ubuntu 24.04 LTS - Monitor freeze in multi-monitor setup

2024-08-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hi everyone,
I want to highlight a problem I've been encountering for a few months.
I'm running the latest 24.04 LTS version with Wayland as a windowing system. My 
current setup is to use the laptop display with a second monitor attached.

Sometimes (thus, I'm not able to reproduce this issue), let's say once a
week, the non-primary monitor (thus, the laptop one) completely freezes.

When it happens, I'm unable to enter this monitor with the cursor, plus
I'm unable to use the apps on it. Moreover, other parts of the system
seem to become unresponsive, such as the menu in the top-right part of
the display.

When this happens, the only solution that I've found is a hard reboot.

Note: I'm unable to reproduce this "crash". However, I found that it
happens more frequently when I'm creating new windows and bringing them
to the second monitor.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-compute-525_525.105.17-0ubuntu1_amd64.deb
 ./casper/minimal.standard.live.squashfs
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  1 16:47:19 2024
DistUpgraded: 2024-04-27 11:04:00,044 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Once a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0] (rev 04) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:3c82]
InstallationDate: Installed on 2023-09-07 (329 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: LENOVO 82Y7
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-39-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to noble on 2024-04-27 (96 days ago)
dmi.bios.date: 02/07/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: LWCN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76461 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Yoga Pro 7 14IRH8
dmi.ec.firmware.release: 1.21
dmi.modalias: 
dmi:bvnLENOVO:bvrLWCN21WW:bd02/07/2023:br1.21:efr1.21:svnLENOVO:pn82Y7:pvrYogaPro714IRH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrYogaPro714IRH8:skuLENOVO_MT_82Y7_BU_idea_FM_YogaPro714IRH8:
dmi.product.family: Yoga Pro 7 14IRH8
dmi.product.name: 82Y7
dmi.product.sku: LENOVO_MT_82Y7_BU_idea_FM_Yoga Pro 7 14IRH8
dmi.product.version: Yoga Pro 7 14IRH8
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug freeze multimonitor noble ubuntu wayland-session
-- 
Ubuntu 24.04 LTS - Monitor freeze in multi-monitor setup
https://bugs.launchpad.net/bugs/2075526
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to mutter in Ubuntu.

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

[Bug 2075525] [NEW] After screen blank, the displays configuration gets lost

2024-08-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have configured the host screen with two monitors extending the desktop.
They are both configured at 3840x2160, scale 150%, fractional scaling: yes.

After a period of inactivity, the screens get blanked as configured.
When I move the mouse and the screens unblank, sometimes (not always) the 
configuration is changed by mirroring the same content on the two displays. 
Anyway, the display are still configured as extended in the applet.
Trying to change some settings to restore the desired configuration never work.
I have to unbplug and re-plug the second monitor.

But sometimes, after unplugging and replugging the secondary monitor,
the session crashes, all the apps are terminated and I get just the
logon screen.

In other words, gnome is not able to manage reliably the blank/unblank cycle in 
a multi-monitor configuration.
I also tried with the AMD built-in graphics card and the behavior is exactly 
the same. Therefore I don´t think that the NVidia driver has anything to do 
with it.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.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  535.183.01  Sun May 12 
19:39:15 UTC 2024
 GCC version:
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug  1 16:41:52 2024
DistUpgraded: 2024-05-30 18:43:55,152 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP106 [GeForce GTX 1060 3GB] 
[1458:3722]
 Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c9) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Raphael [1043:8877]
InstallationDate: Installed on 2023-12-11 (234 days ago)
InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 
(20230415)
MachineType: ASUS System Product Name
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=445b6419-9578-4846-99e2-eb90362e1711 ro amd_iommu=on pcie_port_pm=off 
kvm.ignore_msrs=1 iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 
vfio-pci.ids=10de:2805,10de:22bd
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-05-30 (63 days ago)
dmi.bios.date: 04/12/2024
dmi.bios.release: 20.7
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2007
dmi.board.asset.tag: Default string
dmi.board.name: ProArt X670E-CREATOR WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2007:bd04/12/2024:br20.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProArtX670E-CREATORWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-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:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug noble possible-manual-nvidia-install ubuntu
-- 
After screen blank, the displays configuration gets lost
https://bugs.launchpad.net/bugs/2075525
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to mutter in Ubuntu.

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

[Bug 2072761] Re: Stuck arrow keys after switching workspaces

2024-08-01 Thread Daniel van Vugt
I would start by trying to disable extensions like:

  gnome-extensions list --enabled
  gnome-extensions disable tiling-assist...@ubuntu.com

and log in again. See if disabling any of them makes a difference.

-- 
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/2072761

Title:
  Stuck arrow keys after switching workspaces

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


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

[Bug 2072761] Re: Stuck arrow keys after switching workspaces

2024-08-01 Thread flatmax
Does anyone have any temporary fixes for this bug ?

-- 
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/2072761

Title:
  Stuck arrow keys after switching workspaces

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-08-01 Thread Daniel van Vugt
If you set the monitor to a lower resolution or a different refresh
rate, does it prevent the bug?

-- 
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/2074559

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-08-01 Thread Jackson Smith
ps - I don't know whether this information was preserved in the original
bug report, but it may be important.

First, the secondary monitor is positioned to the left hand side,
relative to the primary monitor. This was set by moving the small icon
of the secondary monitor in Settings>Displays to the left of the primary
monitor's icon.

Second, the Dock is on the left edge of the primary monitor, and the
Dock's auto-hide behaviour is active. Therefore, to move the mouse
cursor from the primary monitor to the secondary monitor, I must push
the cursor through the Dock and onto the secondary monitor.

-- 
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/2074559

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2023572] Re: SRU gjs 1.72.4 to jammy

2024-08-01 Thread Andreas Hasenack
Please clarify the testing that was done, and *with which version
exactly* (as requested in comment #12). This package had to go through a
revert in the previous attempt to update to 1.72.4 (see version
1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2), and we need more
confidence.

** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy

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

Title:
  SRU gjs 1.72.4 to jammy

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-08-01 Thread Jackson Smith
Just to be clear, I associate restarting gnome with logging out then
logging in again. Not with unplugging the monitor and reconnecting.

Concerning the present bug report, I'm becoming confident that the
flickering black bar appears at the top of the secondary monitor after
the following steps:

1 - Lock the screen, either manually or waiting for the timeout.
2 - Wait for screen to sleep.
3 - Unlock the screen

Logging out/in eliminates the black bar, and restores normal behaviour
until the next time the screen locks and sleeps.

-- 
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/2074559

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2061744] Re: Evolution does not handle RSS feeds anymore: libevolution-rss-common.so: cannot open shared object file

2024-08-01 Thread Launchpad Bug Tracker
This bug was fixed in the package evolution - 3.52.3-0ubuntu1

---
evolution (3.52.3-0ubuntu1) noble; urgency=medium

  [ Alessandro Astone ]
  * New upstream release (LP: #2072547)

  [ Jeremy Bícha ]
  * debian/control: Bump e-d-s dependencies and build-dependencies to 3.52.3
  * Move libevolution-rss-common.so to libevolution package (Closes: #1070833)
(LP: #2061744)

 -- Alessandro Astone   Tue, 09 Jul
2024 09:23:58 -0400

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

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

Title:
  Evolution does not handle RSS feeds anymore: libevolution-rss-
  common.so: cannot open shared object file

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


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

[Bug 2072547] Re: [SRU] Update evolution to 3.52.3

2024-08-01 Thread Launchpad Bug Tracker
This bug was fixed in the package evolution - 3.52.3-0ubuntu1

---
evolution (3.52.3-0ubuntu1) noble; urgency=medium

  [ Alessandro Astone ]
  * New upstream release (LP: #2072547)

  [ Jeremy Bícha ]
  * debian/control: Bump e-d-s dependencies and build-dependencies to 3.52.3
  * Move libevolution-rss-common.so to libevolution package (Closes: #1070833)
(LP: #2061744)

 -- Alessandro Astone   Tue, 09 Jul
2024 09:23:58 -0400

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

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

Title:
  [SRU] Update evolution to 3.52.3

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


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

[Bug 2061744] Update Released

2024-08-01 Thread Andreas Hasenack
The verification of the Stable Release Update for evolution has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Evolution does not handle RSS feeds anymore: libevolution-rss-
  common.so: cannot open shared object file

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


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

[Bug 2072547] Update Released

2024-08-01 Thread Andreas Hasenack
The verification of the Stable Release Update for evolution has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Update evolution to 3.52.3

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


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

[Bug 2075350] Re: gnome-shell seems to hang on monitor disconnect, killing gnome-shell process helps to bring system to life

2024-07-31 Thread Daniel van Vugt
Thanks for the bug report.

I don't think the above log messages are relevant to the main problem
here. Please start by removing all local extensions:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again. If the problem continues to happen then next time
it does, after bringing the machine back to life (without rebooting),
please run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.


** 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/2075350

Title:
  gnome-shell seems to hang on monitor disconnect, killing gnome-shell
  process helps to bring system to life

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-07-31 Thread Daniel van Vugt
GNOME restarting when you unplug the monitor is a bug. Likely bug
2050865.

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

** 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/2074559

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2075247] Re: gvfs-fused not running on noble, mounts not available

2024-07-31 Thread Jeremy Bícha
$ systemctl status --user gvfs-daemon.service 
● gvfs-daemon.service - Virtual filesystem service
 Loaded: loaded (/usr/lib/systemd/user/gvfs-daemon.service; static)
 Active: active (running)
   Main PID: 3721 (gvfsd)
 CGroup: 
/user.slice/user-1000.slice/user@1000.service/session.slice/gvfs-daemon.service
 ├─  3721 /usr/libexec/gvfsd
 ├─  3729 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f
 ├─  4981 /usr/libexec/gvfsd-trash --spawner :1.3 
/org/gtk/gvfs/exec_spaw/0
 ├─ 11896 /usr/libexec/gvfsd-http --spawner :1.3 
/org/gtk/gvfs/exec_spaw/1
 ├─209952 /usr/libexec/gvfsd-network --spawner :1.3 
/org/gtk/gvfs/exec_spaw/2
 ├─209961 /usr/libexec/gvfsd-dnssd --spawner :1.3 
/org/gtk/gvfs/exec_spaw/3
 └─367232 /usr/libexec/gvfsd-recent --spawner :1.3 
/org/gtk/gvfs/exec_spaw/6

-- 
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/2075247

Title:
  gvfs-fused not running on noble, mounts not available

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


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

[Bug 2074559] Re: [nouveau] Top margin of secondary monitor covered with black flickering rectangle

2024-07-31 Thread Jackson Smith
The trigger may be when a) the screen is locked, and b) the screen
blacks out. Logging back in after this leads to the flickering black
rectangle at the top of the secondary monitor. This occurs without any
use of SDL.

Switching the monitor off and on does not fix the problem. Disconnecting
and reconnecting the monitor causes the second monitor to loose signal.
At this point, it is possible to logout and then login again. I guess
that this restarts gnome. In any case, signal to both monitors is
restored, and the black bar at the top of the second monitor has
disappeared.

-- 
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/2074559

Title:
  [nouveau] Top margin of secondary monitor covered with black
  flickering rectangle

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


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

[Bug 2075247] Re: gvfs-fused not running on noble, mounts not available

2024-07-31 Thread Steve Langasek
I'll try to reproduce with a clean profile when I have a moment.

In the meantime, could you tell me what systemd user unit the process is
part of on your system? I don't see anything in the gvfs-fuse package
itself that would start it as part of a user session.

-- 
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/2075247

Title:
  gvfs-fused not running on noble, mounts not available

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


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

[Bug 2075365] [NEW] nautilus random crash

2024-07-31 Thread Christians
Public bug reported:

crash on startup of nautilus

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 31 17:45:28 2024
InstallationDate: Installed on 2023-06-06 (421 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apport.crashdb.conf: 2024-03-06T17:35:57.237100
usr_lib_nautilus:
 file-roller   44.1-1
 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2
 nautilus-image-converter  0.4.0-2build2
 nautilus-wipe 0.4.alpha2-0.1ubuntu2
 python3-nautilus  4.0-1build4

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


** Tags: amd64 apport-bug noble third-party-packages

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

Title:
  nautilus random crash

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


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

[Bug 1721049] Re: "Got unknown content type text/html" error viewing flatpack packages

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gnome-software (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  "Got unknown content type text/html" error viewing flatpack packages

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


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

[Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: mutter (Ubuntu Artful)
   Status: Confirmed => Won't Fix

-- 
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/1686081

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions


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

[Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gnome-control-center (Ubuntu Artful)
   Status: Confirmed => Won't Fix

-- 
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/1686081

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions


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

[Bug 1716409] Re: Unable to install flatpakref on Ubuntu artful

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gnome-software (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  Unable to install flatpakref on Ubuntu artful

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


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

[Bug 1721833] Re: Can't type numbers in the evolution search box

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: evolution (Ubuntu Artful)
   Status: In Progress => Won't Fix

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

Title:
  Can't type numbers in the evolution search box

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


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

[Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: snapd-glib (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  gnome-software spams error messages to journald and causes 100% CPU
  usage

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


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

[Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gnome-software (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  gnome-software spams error messages to journald and causes 100% CPU
  usage

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


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

[Bug 1725821] Re: mutter 3.26 doesn't properly unredirect windows

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: mutter (Ubuntu Artful)
   Status: Incomplete => Won't Fix

-- 
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/1725821

Title:
  mutter 3.26 doesn't properly unredirect windows

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


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

[Bug 1728617] Re: Scrolled window broken when containing an eventbox

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  Scrolled window broken when containing an eventbox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1728617/+subscriptions


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

[Bug 1729713] Re: Update gdm3 to 3.26.2.1

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gdm3 (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  Update gdm3 to 3.26.2.1

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


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

[Bug 1740345] Re: Upgrade epiphany-browser to 3.26.5.1

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: epiphany-browser (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  Upgrade epiphany-browser to 3.26.5.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1740345/+subscriptions


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

[Bug 1746773] Re: Search for Skype in GNOME Software doesn't list Skype as the first match

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gnome-software (Ubuntu Artful)
   Status: Fix Committed => Won't Fix

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

Title:
  Search for Skype in GNOME Software doesn't list Skype as the first
  match

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


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

[Bug 1760758] Re: /usr/lib/ibus/ibus-engine-libpinyin:ibus-engine-libpinyin: pinyin.cpp:991\357\274\232bool pinyin_set_zhuyin_scheme(pinyin_context_t*, ZhuyinScheme): \345\201\207\350\256\276 \342\200

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: ibus-libpinyin (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  /usr/lib/ibus/ibus-engine-libpinyin:ibus-engine-libpinyin:
  pinyin.cpp:991\357\274\232bool
  pinyin_set_zhuyin_scheme(pinyin_context_t*, ZhuyinScheme):
  \345\201\207\350\256\276 \342\200\230(0)\342\200\231
  \345\244\261\350\264\245\343\200\202

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1760758/+subscriptions


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

[Bug 1629600] Re: Installed application from .deb does not appear unless Ubuntu is restarted

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gnome-software (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  Installed application from .deb does not appear unless Ubuntu is
  restarted

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


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

[Bug 1700319] Re: GTK3 menus don't work over SSH forwarding

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: In Progress => Won't Fix

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

Title:
  GTK3 menus don't work over SSH forwarding

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


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

[Bug 1716579] Re: gnome-software uses a very high cpu amount

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gnome-software (Ubuntu Artful)
   Status: In Progress => Won't Fix

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

Title:
  gnome-software uses a very high cpu amount

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


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

[Bug 1721762] Re: Cancelled installation of snap continues

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: snapd-glib (Ubuntu Artful)
   Status: Fix Committed => Won't Fix

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

Title:
  Cancelled installation of snap continues

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1721762/+subscriptions


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

[Bug 1723874] Re: First installation of a snap reports an error "Connection reset by peer"

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: snapd-glib (Ubuntu Artful)
   Status: Fix Committed => Won't Fix

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

Title:
  First installation of a snap reports an error "Connection reset by
  peer"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1723874/+subscriptions


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

[Bug 1728653] Re: Update evolution-data-server to 3.26.3

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: evolution-data-server (Ubuntu Artful)
   Status: In Progress => Won't Fix

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

Title:
  Update evolution-data-server to 3.26.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1728653/+subscriptions


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

[Bug 1728655] Re: Update evolution to 3.26.3

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: evolution (Ubuntu Artful)
   Status: In Progress => Won't Fix

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

Title:
  Update evolution to 3.26.3

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


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

[Bug 1752197] Re: Videos won't resume after being paused

2024-07-31 Thread Brian Murray
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: webkit2gtk (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  Videos won't resume after being paused

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit-open-source/+bug/1752197/+subscriptions


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

[Bug 2075247] Re: gvfs-fused not running on noble, mounts not available

2024-07-31 Thread Jeremy Bícha
I do have a user process running on Ubuntu 24.04 LTS and 24.10

/usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f

Perhaps try if you can reproduce this issue on a clean Ubuntu install or
on a clean system upgraded from previous Ubuntu releases.

On my Android phone, I do see a popup "Allow access to phone data", I
have to click Allow on to be able to mount the phone storage on my
Ubuntu computer.

You could also check your systemd journal.

I'm setting to Incomplete because there is not enough information here
and I was unable to reproduce the issue as described.

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

-- 
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/2075247

Title:
  gvfs-fused not running on noble, mounts not available

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


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

[Bug 2075350] [NEW] gnome-shell seems to hang on monitor disconnect, killing gnome-shell process helps to bring system to life

2024-07-31 Thread Dmitry Lapshin
Public bug reported:

As title says: sometimes when I disconnect my laptop from DisplayPort-
over-USBC monitor desktop goes to black screen (sometimes with cursor
available, but only the cursor!), and over the time I've found out that
opening a tty session and executing a `killall gnome-shell` brings
system back to life! It looks very glitchy but it helps.

The only relevant part I've found out is this part of the log. It's an
extremely long thread of similar but mixed messages like:

```
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context 
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was 
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was 
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was 
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was 
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was 
window-entered-monitor on 

  1   2   3   4   5   6   7   8   9   10   >