date:20240115

Those issues are unrelated so please log a separate bug report for each
one.

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

Title:
  [nvidia] Secondary monitor performance is slow on an Nvidia hybrid
  system in Wayland sessions

Status in GNOME Shell:
  New
Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  In session with Wayland the Nvidia driver settings do not load. And
  there is a sluggishness when opening apps, show applications menu,
  maximize, changing workspace, resize, changing monitor windows etc.
  When in an Xorg session the Nvidia settings load correctly and the
  performance is satisfactory.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 21:18:08 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 
[8086:2086]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] 
[8086:2086]
  InstallationDate: Installed on 2022-04-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: Avell High Performance A60 MUV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QCCFL357.0122.2020.0911.1520
  dmi.board.name: Avell High Performance
  dmi.board.vendor: Avell High Performance
  dmi.chassis.type: 10
  dmi.chassis.vendor: Avell High Performance
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV:
  dmi.product.family: A60 MUV
  dmi.product.name: A60 MUV
  dmi.product.sku: A60 MUV
  dmi.sys.vendor: Avell High Performance
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  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.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions

2024-01-15 Thread Zingam

I am observing multiple issues with external monitor NVIDIA GPU in a
Gnome session:

- Disconnecting HDMI cable crashes the desktop to login screen
- Desktop freezes for prolonged time when using VSCode and Firefox (the only 
opened applications), maybe also playing YouTube in the background or on the 
primary display.Sometimes the freez is complete sometimes it recovers.

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

Title:
  [nvidia] Secondary monitor performance is slow on an Nvidia hybrid
  system in Wayland sessions

Status in GNOME Shell:
  New
Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  In session with Wayland the Nvidia driver settings do not load. And
  there is a sluggishness when opening apps, show applications menu,
  maximize, changing workspace, resize, changing monitor windows etc.
  When in an Xorg session the Nvidia settings load correctly and the
  performance is satisfactory.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 21:18:08 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 
[8086:2086]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] 
[8086:2086]
  InstallationDate: Installed on 2022-04-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: Avell High Performance A60 MUV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QCCFL357.0122.2020.0911.1520
  dmi.board.name: Avell High Performance
  dmi.board.vendor: Avell High Performance
  dmi.chassis.type: 10
  dmi.chassis.vendor: Avell High Performance
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV:
  dmi.product.family: A60 MUV
  dmi.product.name: A60 MUV
  dmi.product.sku: A60 MUV
  dmi.sys.vendor: Avell High Performance
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  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.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1779432] Re: [upstream] Libre Writer doesn't do duplex printing

** Changed in: df-libreoffice
   Status: Confirmed => Invalid

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

Title:
  [upstream] Libre Writer doesn't do duplex printing

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The Libre Writer print settings are set to two side printing, but
  program only prints single side. Is not HP Linux driver because both
  FireFox and Chrome print both sides.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: ufsd
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jun 29 22:17:38 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-06-15 (14 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1779432/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1779432]

2024-01-15 Thread klinge

I have a new printer, so I'm not certain, but as I remember it did work
after one of the updates.

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

Title:
  [upstream] Libre Writer doesn't do duplex printing

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The Libre Writer print settings are set to two side printing, but
  program only prints single side. Is not HP Linux driver because both
  FireFox and Chrome print both sides.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: ufsd
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jun 29 22:17:38 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-06-15 (14 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1779432/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049368] Re: gnome-shell crashed with X error 161 (major 152, minor 23)

Thanks. The only crash similar to that I can find is
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5651

Using Wayland instead of Xorg will avoid it.

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

** Summary changed:

- gnome-shell crashed with X error 161 (major 152, minor 23)
+ gnome-shell crashed with X error 161 (major 152, minor 23) in 
free_glx_pixmap()

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

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

Title:
  gnome-shell crashed with X error 161 (major 152, minor 23) in
  free_glx_pixmap()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Casual browsing, and then boom "Oh no! Something has gone wrong"
  screen. Ubuntu 23.10, Lenovo ThinkPad P14s gen4 amd, AMDGPU open
  source drivers, also I switched to X Server from the default Wayland
  because of Wayland bugs.

  A stack trace frame I got manually, but I didn't persist much:

  ```
  ─── Stack 
───(138
 results) [2033/2675]
  [12] from 0x7f62b1f63adb in __glXSendError+155 at ../src/GLX/libglx.c:805 


  arg dpy = 0x562471d040d0, errorCode = , resourceID = 0, 
minorCode = , coreX11error = 0   
   
  [13] from 0x7f62b5f0962f  


  (no arguments)


  [14] from 0x7f62b5f09d29  


  (no arguments)


  [15] from 0x7f62b5f0734e  


  (no arguments)


  [16] from 0x7f62b5ee347b  


  (no arguments)


  [+]   


  ─── Source 
───
  789 if (dpyInfo == NULL || !dpyInfo->glxSupported) {  


  790 return;   


  791 } 


  792   


  793 LockDisplay(dpy); 


  794   


  795 error.type = X_Error;

[Desktop-packages] [Bug 1779432]

2024-01-15 Thread Qa-admin-q

Dear rosgnilk,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  [upstream] Libre Writer doesn't do duplex printing

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  The Libre Writer print settings are set to two side printing, but
  program only prints single side. Is not HP Linux driver because both
  FireFox and Chrome print both sides.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: ufsd
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jun 29 22:17:38 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-06-15 (14 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1779432/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen

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

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

Title:
  Booting into live session results in try/install page white screen

Status in ubuntu-desktop-installer:
  New
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into
  live session results in try/install page white screen.Selecting
  install from the dash results in same white screen.

  see the attached screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.487
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 07:02:48 2023
  LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049368] Re: gnome-shell crashed with X error 161 (major 152, minor 23)

Also I managed to install mutter debug symbols now, a better stack trace
showing that the error may come from free_glx_pixmap:

#0  __pthread_kill_implementation (no_tid=0, signo=5, threadid=) 
at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=5, threadid=) at 
./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=, signo=signo@entry=5) at 
./nptl/pthread_kill.c:89
#3  0x7f62b5842866 in __GI_raise (sig=5) at ../sysdeps/posix/raise.c:26
#4  0x562470b03bda in ??? ()
#5  0x7f62b5842910 in  () at 
/lib/x86_64-linux-gnu/libc.so.6
#6  0x7f62b62e5867 in g_log_structured_array () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f62b62e5b52 in g_log_default_handler () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f62b62e69e2 in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f62b62e6ca3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f62b68ab59e in display_error_event (error=0x7ffdc2b64df0, 
xdisplay=0x562471d040d0) at ../mtk/mtk/mtk-x11-errors.c:116
#11 mtk_x_error (xdisplay=0x562471d040d0, error=0x7ffdc2b64df0) at 
../mtk/mtk/mtk-x11-errors.c:139
#12 0x7f62b5704a5b in _XError (dpy=dpy@entry=0x562471d040d0, 
rep=rep@entry=0x7ffdc2b64ef0) at ../../src/XlibInt.c:1503
#13 0x7f62b1f63adb in __glXSendError (dpy=0x562471d040d0, 
errorCode=, resourceID=0, minorCode=, 
coreX11error=0) at ../src/GLX/libglx.c:805
#14 0x7f62b5f0962f in free_glx_pixmap (glx_tex_pixmap=0x562474714500, 
context=) at ../cogl/cogl/winsys/cogl-winsys-glx.c:1203
#15 0x7f62b5f09d29 in _cogl_winsys_texture_pixmap_x11_free 
(tex_pixmap=0x390) at ../cogl/cogl/winsys/cogl-winsys-glx.c:1224
#16 0x7f62b5f0734e in _cogl_texture_pixmap_x11_free 
(tex_pixmap=0x56247509abf0) at 
../cogl/cogl/winsys/cogl-texture-pixmap-x11.c:1067
#17 _cogl_object_texture_pixmap_x11_indirect_free (obj=0x56247509abf0) at 
../cogl/cogl/winsys/cogl-texture-pixmap-x11.c:71
#18 0x7f62b5ee347b in _cogl_pipeline_layer_free (layer=0x562475744090) at 
../cogl/cogl/cogl-pipeline-layer.c:706
#19 _cogl_object_pipeline_layer_indirect_free (obj=0x562475744090) at 
../cogl/cogl/cogl-pipeline-layer.c:57
#20 0x7f62b5ee29d5 in _cogl_pipeline_node_unparent_real 
(node=0x562475765340) at ../cogl/cogl/cogl-node.c:92
#21 0x7f62b5ee3460 in _cogl_pipeline_layer_unparent (layer=0x562475765340) 
at ../cogl/cogl/cogl-pipeline-layer.c:443
#22 _cogl_pipeline_layer_free (layer=0x562475765340) at 
../cogl/cogl/cogl-pipeline-layer.c:702
#23 _cogl_object_pipeline_layer_indirect_free (obj=0x562475765340) at 
../cogl/cogl/cogl-pipeline-layer.c:57
#24 0x7f62b5ee29d5 in _cogl_pipeline_node_unparent_real 
(node=0x562471bef190) at ../cogl/cogl/cogl-node.c:92
#25 0x7f62b5ee3460 in _cogl_pipeline_layer_unparent (layer=0x562471bef190) 
at ../cogl/cogl/cogl-pipeline-layer.c:443
#26 _cogl_pipeline_layer_free (layer=0x562471bef190) at 
../cogl/cogl/cogl-pipeline-layer.c:702
#27 _cogl_object_pipeline_layer_indirect_free (obj=0x562471bef190) at 
../cogl/cogl/cogl-pipeline-layer.c:57
#28 0x7f62b62d99a0 in g_list_foreach () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7f62b62d9f9f in g_list_free_full () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7f62b5ee9c0a in _cogl_pipeline_free (pipeline=0x56247444fc60) at 
../cogl/cogl/cogl-pipeline.c:386
#31 _cogl_object_pipeline_indirect_free (obj=0x56247444fc60) at 
../cogl/cogl/cogl-pipeline.c:69
#32 0x7f62b5ed00e2 in _cogl_pipeline_flush_gl_state
(ctx=ctx@entry=0x562472024690, pipeline=pipeline@entry=0x5624779ecc80, 
framebuffer=framebuffer@entry=0x5624720b97b0, with_color_attrib=1, 
unknown_color_alpha=)
at ../cogl/cogl/driver/gl/cogl-pipeline-opengl.c:1099
#33 0x7f62b5ed0723 in _cogl_gl_flush_attributes_state
(framebuffer=0x5624720b97b0, pipeline=0x5624779ecc80, 
layers_state=0x7ffdc2b65220, flags=, attributes=0x562475ef9970, 
n_attributes=4)
at ../cogl/cogl/driver/gl/cogl-attribute-gl.c:256
#34 0x7f62b5ee99eb in _cogl_flush_attributes_state
(framebuffer=0x5624720b97b0, pipeline=0x5624779ecc80, 
flags=(COGL_DRAW_SKIP_JOURNAL_FLUSH | COGL_DRAW_SKIP_PIPELINE_VALIDATION | 
COGL_DRAW_SKIP_FRAMEBUFFER_FLUSH), attributes=0x562475ef9970, n_attributes=4) 
at ../cogl/cogl/cogl-attribute.c:626
#35 0x7f62b5ec9ea4 in cogl_gl_framebuffer_draw_attributes
(driver=, pipeline=, 
mode=COGL_VERTICES_MODE_TRIANGLE_FAN, first_vertex=0, n_vertices=4, 
attributes=, n_attributes=4, flags=(COGL_DRAW_SKIP_JOURNAL_FLUSH 
| COGL_DRAW_SKIP_PIPELINE_VALIDATION | COGL_DRAW_SKIP_FRAMEBUFFER_FLUSH)) at 
../cogl/cogl/driver/gl/cogl-framebuffer-gl.c:332
#36 0x7f62b5f012c2 in cogl_framebuffer_driver_draw_attributes
(flags=(COGL_DRAW_SKIP_JOURNAL_FLUSH | COGL_DRAW_SKIP_PIPELINE_VALIDATION | 
COGL_DRAW_SKIP_FRAMEBUFFER_FLUSH), n_attributes=, 
attributes=0x562475ef9970, n_vertices=4, first_vertex=, 
mode=COGL_VERTICES_MODE_TRIANGLE_FAN, pipeline=, 
driver=) at ../cogl/cogl/cogl-framebuffer-driver.c:113
#37

[Desktop-packages] [Bug 404363] Re: desktop icons aren't aligned automatically in RTL languages (Hebrew, Arabic, Persian)

2024-01-15 Thread Khalid Abu Shawarib

Obsolete bug; Nautilus doesn't provide desktop icons anymore.

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

Title:
  desktop icons aren't aligned automatically in RTL languages (Hebrew,
  Arabic, Persian)

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Hi all,

  In my Mom's computer the localization is in Hebrew, meaning that all menus, 
folders, and Desktop icons are RTL.
  As an End-User, every time my Mom downloads something, or drags a 
file/shortcut to the desktop, the icon doesn't align itself to the grid of the 
other icons automatically, but instead "lands" in one area (usually the top 
right).

  Yet, the bug doesn't stop there. If that icon is left there, the upcoming 
icons that will be added to the desktop will land right on top of it, creating 
a lovely stack as shown in the pic:
  http://img146.imageshack.us/img146/5637/bug1p.jpg
  http://img91.imageshack.us/img91/9945/bug2d.jpg
  (credits to Shezif for posting the pics..)

  Considering that many users prefer the localize system language, and
  not plain English, i hope this is solvable quickly..

  In any case, thanks in advance..

  Regards,

  Uri

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049368] Re: gnome-shell crashed with X error 161 (major 152, minor 23)

I don't know how to reproduce and it doesn't happen often, but I've
added MUTTER_SYNC=1 and will update when/if it happens.

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

Title:
  gnome-shell crashed with X error 161 (major 152, minor 23)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Casual browsing, and then boom "Oh no! Something has gone wrong"
  screen. Ubuntu 23.10, Lenovo ThinkPad P14s gen4 amd, AMDGPU open
  source drivers, also I switched to X Server from the default Wayland
  because of Wayland bugs.

  A stack trace frame I got manually, but I didn't persist much:

  ```
  ─── Stack 
───(138
 results) [2033/2675]
  [12] from 0x7f62b1f63adb in __glXSendError+155 at ../src/GLX/libglx.c:805 


  arg dpy = 0x562471d040d0, errorCode = , resourceID = 0, 
minorCode = , coreX11error = 0   
   
  [13] from 0x7f62b5f0962f  


  (no arguments)


  [14] from 0x7f62b5f09d29  


  (no arguments)


  [15] from 0x7f62b5f0734e  


  (no arguments)


  [16] from 0x7f62b5ee347b  


  (no arguments)


  [+]   


  ─── Source 
───
  789 if (dpyInfo == NULL || !dpyInfo->glxSupported) {  


  790 return;   


  791 } 


  792   


  793 LockDisplay(dpy); 


  794   


  795 error.type = X_Error; 


  796 error.errorCode = errorCode;  


  797 error.sequenceNumber = dpy->request;

[Desktop-packages] [Bug 1236983] Re: Possible security expoit using special characters to manipulate displayed filename.

2024-01-15 Thread Khalid Abu Shawarib

This is using a Unicode Right-to-Left override. Unless you want to
disable bidirectional Unicode support, this should not change the way
it's rendered. Instead you should be managing things like whether it's
executable by double click and whether it displays a PDF icon/preview.

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

Title:
  Possible security expoit using special characters to manipulate
  displayed filename.

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Use of special characters can be used to manipulate a filename
  extension in Nautilus. We received a piece of malware with a filename
  that appears differently with Nautilus than on the command line using
  ls.

  With Nautilus we see: NO.00123Order# POrcs.pdf
  With ls in bash we see: NO.00123Order# POfdp.scr

  Using od the special characters are revealed as:
  ronp@ron:~/Desktop/virus$ ls *scr | od -c
  000   N   O   .   0   0   1   2   3   O   r   d   e   r   #   P
  020   O 342 200 256   f   d   p   .   s   c   r  \n
  034

  Before extraction from the archive, the file appears with question marks as 
follows:
  NO.00123Order# PO???fdp.scr

  Perhaps this would be a more secure way to display the file in
  Nautaulis revealing the true nature of the file; scr instead of pdf.

  This occurred with Nautilus 3.4.2 on Ubuntu 12.10 and Nautilus 3.6.3
  on Ubuntu 13.04

  We note this type of exploit has been used before:
  
https://kc.mcafee.com/resources/sites/MCAFEE/content/live/PRODUCT_DOCUMENTATION/23000/PD23930/en_US/McAfee_Labs_Threat_Advisory_XDocCrypt.pdf

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 869793] Re: Nautilus is very slow when opening folders with many files

2024-01-15 Thread Khalid Abu Shawarib

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Nautilus is very slow when opening folders with many files

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Opening folders with many files takes a long time with Nautilus, to the point 
it becomes unusable for folders with more than 5K files. 
  I've measured the time it takes for folders with different amount of files to 
open with Nautilus and Gnome Commander. It is ~6 times faster with GC on 
average. In folders with ~20K files, it takes 30s with nautilus versus 6! with 
GC. 

  With Nautilus
  ~3500 files tales 6 seconds
  ~7000 files takes 18 seconds
  ~15000 files takes 22 seconds
  ~2 files takes 30 seconds

  With Gnome Commander
  ~3500 files tales <1 second
  ~7000 files takes 1.5 seconds
  ~15000 files takes 3 seconds
  ~2 files takes 6 seconds

  These are mostly small dicom files (MRI images). I am using a 8 core 3.4Ghz 
and 16Gigs of RAM with Ubuntu 11.04 64-bits.
  Also, of course, things like selecting all files and copying them around is 
absurdly slow and makes nautilus unusable... but that would be another bug 
report (?).

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2042796] Re: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't respond to taps if they are very small

2024-01-15 Thread Kai-Chuan Hsieh

** Changed in: oem-priority
   Status: Triaged => Fix Released

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

Title:
  Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't
  respond to taps if they are very small

Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Touchscreen touches at the left or bottom edges (within 20px) of the
  screen are not treated as mouse clicks. Icons only get highlighted,
  not launched.

  [ Test Plan ]

  0. Find a touchscreen.
  1. Set Ubuntu Dock in Panel mode (the default mode) if not already.
  2. Touch as close to the edge of the screen as possible. Aim for the gap 
between the icon and the edge of the screen.

  Expect: The app launch animation occurs for each tap. Icons aren't
  just highlighted.

  [ Where problems could occur ]

  Anywhere in touchscreen gesture tracking or even regular touchscreen
  usage. As this bug demonstrates, the former is able to interfere with
  even simple touchscreen actions.

  [ Workaround ]

  Size the Ubuntu Dock adequately large so it is unlikely the user will
  touch less than 20 pixels from the edge of the screen.

  [ Original description ]

  On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance,
  adjust the dock icon-size to 24. It is hard to launch corner app like
  firefox, or trigger the launcher. The app icon gets focus but not
  clicked.

  1. Ubuntu version 20.04.6
  2. gnome-shell 3.36.9-0ubuntu0.20.04.2
  3. The app or launcher is launched after a click
  4. Only see focus but no app launched

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049424] Re: Grayscreen

Xorg itself doesn't paint anything, it will start with a black window.
So it's likely to be a Xubuntu bug. Since it can't be reproduced then
let's leave it Incomplete and it will close automatically after two
months of inactivity.

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

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

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

Title:
  Grayscreen

Status in Ubuntu:
  Incomplete

Bug description:
  Dell Precision 3660

  I upgraded BIOS to 2.11.1 which also upgraded some other things.

  When I login into Xubuntu I get a frozen gray screen

  
  jim@jim:~/Scripts$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  jim@jim:~/Scripts$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915

  jim@jim:~/Scripts$ uname -r
  6.5.0-14-generic


  I can boot into the install flashdrive under Try Xubuntu and the
  display works fine.

  Flash Drive:
  xubuntu@xubuntu:~$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
  xubuntu@xubuntu:~$ uname -r
  6.5.0-9-generic

  Please provide a workaround as this is my primary workstation.

  Let me know if you need any additional information.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Mon Jan 15 10:37:25 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA 
controller])
 Subsystem: Dell AlderLake-S GT1 [1028:0a9f]
  InstallationDate: Installed on 2023-10-14 (93 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2024
  dmi.bios.release: 2.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.11.1
  dmi.board.name: 0KM9JV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.1:bd01/03/2024:br2.11:efr1.7:svnDellInc.:pnPrecision3660:pvr:rvnDellInc.:rn0KM9JV:rvrA00:cvnDellInc.:ct3:cvr:sku0A9F:
  dmi.product.family: Precision
  dmi.product.name: Precision 3660
  dmi.product.sku: 0A9F
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049368] Re: gnome-shell crashed with X error 161 (major 152, minor 23)

Thanks for the bug report. If you are able to reproduce the crash then
please add MUTTER_SYNC=1 to /etc/environment, reboot and then find out
the new stack trace.

** Summary changed:

- gnome-shell crash while chaing Chromium browser tab
+ gnome-shell crashed with X error 161 (major 152, minor 23)

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

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

Title:
  gnome-shell crashed with X error 161 (major 152, minor 23)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Casual browsing, and then boom "Oh no! Something has gone wrong"
  screen. Ubuntu 23.10, Lenovo ThinkPad P14s gen4 amd, AMDGPU open
  source drivers, also I switched to X Server from the default Wayland
  because of Wayland bugs.

  A stack trace frame I got manually, but I didn't persist much:

  ```
  ─── Stack 
───(138
 results) [2033/2675]
  [12] from 0x7f62b1f63adb in __glXSendError+155 at ../src/GLX/libglx.c:805 


  arg dpy = 0x562471d040d0, errorCode = , resourceID = 0, 
minorCode = , coreX11error = 0   
   
  [13] from 0x7f62b5f0962f  


  (no arguments)


  [14] from 0x7f62b5f09d29  


  (no arguments)


  [15] from 0x7f62b5f0734e  


  (no arguments)


  [16] from 0x7f62b5ee347b  


  (no arguments)


  [+]   


  ─── Source 
───
  789 if (dpyInfo == NULL || !dpyInfo->glxSupported) {  


  790 return;   


  791 } 


  792   


  793 LockDisplay(dpy); 


  794   


  795 error.type = X_Error; 


  796 error.errorCode = errorCode;

[Desktop-packages] [Bug 2048931] Re: [noble] extension pref dialog turns hidden

** Changed in: gjs
   Status: Unknown => New

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

Title:
  [noble] extension pref dialog turns hidden

Status in gjs:
  New
Status in GNOME Shell:
  New
Status in gjs package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I get this after:
  1) open Extensions app
  2) open a pref
  3) prefs window after a quarter of second gets hidden
  4) no way to access this window

  JS ERROR: Gio.IOErrorEnum: GDBus.Error:org.gnome.gjs.JSError.Error: Already 
showing a prefs dialog
  asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  
_init/GLib.MainLoop.prototype.runAsync/https://bugs.launchpad.net/gjs/+bug/2048931/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1982693] Re: USB-Audio device UMC204HD disappears after suspend

2024-01-15 Thread Charly Boy

I'm facing the same problem that you describe.
Were you able to figure out a solution to your problem?

I noticed that the command "usbreset" before going to sleep would show
the USB audio interface. After coming back from sleep, the same command
doesn't show the interface anymore.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1982693

Title:
  USB-Audio device UMC204HD disappears after suspend

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Coming back from sleep, Behringer UMC204HD is not in the list of
  devices in Settings > Sound. It comes back if I unplug and plug back
  in.

  I tried with/without a USB hub in between, I tried setting
  "usbcore.autosuspend=-1". No help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 24 15:04:57 2022
  InstallationDate: Installed on 2022-04-21 (93 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U192k successful
  Symptom_Card: HD Webcam C525 - HD Webcam C525
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [USB-Audio - UMC204HD 192k, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.H0
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M PRO-VH (MS-7996)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.H0:bd06/16/2018:br5.12:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VH(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7996
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1982693/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2048931] Re: [noble] extension pref dialog turns hidden

2024-01-15 Thread Jeremy Bícha

** Also affects: gjs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gjs (Ubuntu)
   Importance: Undecided => High

** Changed in: gjs (Ubuntu)
   Status: New => Triaged

** Bug watch added: gitlab.gnome.org/GNOME/gjs/-/issues #598
   https://gitlab.gnome.org/GNOME/gjs/-/issues/598

** Also affects: gjs via
   https://gitlab.gnome.org/GNOME/gjs/-/issues/598
   Importance: Unknown
   Status: Unknown

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

Title:
  [noble] extension pref dialog turns hidden

Status in gjs:
  Unknown
Status in GNOME Shell:
  New
Status in gjs package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I get this after:
  1) open Extensions app
  2) open a pref
  3) prefs window after a quarter of second gets hidden
  4) no way to access this window

  JS ERROR: Gio.IOErrorEnum: GDBus.Error:org.gnome.gjs.JSError.Error: Already 
showing a prefs dialog
  asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  
_init/GLib.MainLoop.prototype.runAsync/https://bugs.launchpad.net/gjs/+bug/2048931/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049434] [NEW] Nautilus crashes when trying to open file options in administrator mode

2024-01-15 Thread Alexandr

Public bug reported:

Ubuntu 23.10
nautilus 1:45~rc-1ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: nautilus 1:45~rc-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 16 00:46:25 2024
InstallationDate: Installed on 2024-01-11 (4 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

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


** Tags: amd64 apport-bug mantic

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

Title:
  Nautilus crashes when trying to open file options in administrator
  mode

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 23.10
  nautilus 1:45~rc-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 16 00:46:25 2024
  InstallationDate: Installed on 2024-01-11 (4 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049433] [NEW] [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6

2024-01-15 Thread Shahbaz Youssefi

Public bug reported:

Hi, Chrome/ANGLE developer here.

We've started observing crashes on Ubuntu 20.04.6 in libvulkan_radeon.so
since December 5, 2023. So far, all crashes seem to come from that
specific Ubuntu version, and with RADV 21.2.6. Speaking with a mesa RADV
developer, that version hasn't had an update since Nov 2021.

While there's always a chance that an update in ANGLE has hit a bug, the
timing does not work out (Chrome Beta has been fine since November 1,
but the crashes started happening on Dec 5).

Has there been an update to this driver around Dec 5, 2023 in Ubuntu
specifically? I'm wondering if there has been a (security) update done
by the Ubuntu team that upstream mesa may not be aware of. I can't find
a public history of updates to ubuntu packages (with associated dates),
is it possible to look at / provide that info and see what happened
around Dec 5?

Additional context is crbug.com/1508940, but I'm afraid not much is
visible publicly. The crash stack is nonsense unfortunately.

Cheers

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

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

Title:
  [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi, Chrome/ANGLE developer here.

  We've started observing crashes on Ubuntu 20.04.6 in
  libvulkan_radeon.so since December 5, 2023. So far, all crashes seem
  to come from that specific Ubuntu version, and with RADV 21.2.6.
  Speaking with a mesa RADV developer, that version hasn't had an update
  since Nov 2021.

  While there's always a chance that an update in ANGLE has hit a bug,
  the timing does not work out (Chrome Beta has been fine since November
  1, but the crashes started happening on Dec 5).

  Has there been an update to this driver around Dec 5, 2023 in Ubuntu
  specifically? I'm wondering if there has been a (security) update done
  by the Ubuntu team that upstream mesa may not be aware of. I can't
  find a public history of updates to ubuntu packages (with associated
  dates), is it possible to look at / provide that info and see what
  happened around Dec 5?

  Additional context is crbug.com/1508940, but I'm afraid not much is
  visible publicly. The crash stack is nonsense unfortunately.

  Cheers

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2048697] Re: Saving backup server credentials

2024-01-15 Thread Luis

Hey,

if I use nautilus I can save passwords correctly.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/2048697

Title:
  Saving backup server credentials

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  If I want to run a backup, I have to enter the username and password for the 
target backup server over and over again.
  Even if I set the checkbox Remember password.

  System:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  deja-dup:
Installiert:   42.9-1ubuntu3
Installationskandidat: 42.9-1ubuntu3
Versionstabelle:
   *** 42.9-1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.9-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: deja-dup 42.9-1ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 22:34:52 2024
  InstallationDate: Installed on 2023-06-09 (213 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2048697/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2048697] Re: Saving backup server credentials

2024-01-15 Thread Michael Terry

Hmm… that means we aren’t able to store passwords in your desktop
secrets / passwords store. It looks like you’re using gnome, so that’s
very unexpected (there are known issues with KDE).

If you connect to these servers using the basic Files (nautilus) app, do
the passwords get saved?

** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/2048697

Title:
  Saving backup server credentials

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  If I want to run a backup, I have to enter the username and password for the 
target backup server over and over again.
  Even if I set the checkbox Remember password.

  System:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  deja-dup:
Installiert:   42.9-1ubuntu3
Installationskandidat: 42.9-1ubuntu3
Versionstabelle:
   *** 42.9-1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.9-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: deja-dup 42.9-1ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 22:34:52 2024
  InstallationDate: Installed on 2023-06-09 (213 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2048697/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049424] Re: Grayscreen

2024-01-15 Thread Jim Roberts

How frustrating I have spent hours researching this issue including
numerous reboots and logins.

After opening this bug I logged in to get my processes started expecting
the frozen gray screen and the display came up without an issue.

If there is anything that can be gained by further examination of this
issue please let me know how I can help.  If not, please close this bug.

Thank you

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

Title:
  Grayscreen

Status in xorg package in Ubuntu:
  New

Bug description:
  Dell Precision 3660

  I upgraded BIOS to 2.11.1 which also upgraded some other things.

  When I login into Xubuntu I get a frozen gray screen

  
  jim@jim:~/Scripts$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  jim@jim:~/Scripts$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915

  jim@jim:~/Scripts$ uname -r
  6.5.0-14-generic


  I can boot into the install flashdrive under Try Xubuntu and the
  display works fine.

  Flash Drive:
  xubuntu@xubuntu:~$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
  xubuntu@xubuntu:~$ uname -r
  6.5.0-9-generic

  Please provide a workaround as this is my primary workstation.

  Let me know if you need any additional information.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Mon Jan 15 10:37:25 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA 
controller])
 Subsystem: Dell AlderLake-S GT1 [1028:0a9f]
  InstallationDate: Installed on 2023-10-14 (93 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2024
  dmi.bios.release: 2.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.11.1
  dmi.board.name: 0KM9JV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.1:bd01/03/2024:br2.11:efr1.7:svnDellInc.:pnPrecision3660:pvr:rvnDellInc.:rn0KM9JV:rvrA00:cvnDellInc.:ct3:cvr:sku0A9F:
  dmi.product.family: Precision
  dmi.product.name: Precision 3660
  dmi.product.sku: 0A9F
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049424] [NEW] Grayscreen

2024-01-15 Thread Jim Roberts

Public bug reported:

Dell Precision 3660

I upgraded BIOS to 2.11.1 which also upgraded some other things.

When I login into Xubuntu I get a frozen gray screen


jim@jim:~/Scripts$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10

jim@jim:~/Scripts$ lspci -k | grep -EA3 'VGA|3D|Display'
:00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 
0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915

jim@jim:~/Scripts$ uname -r
6.5.0-14-generic


I can boot into the install flashdrive under Try Xubuntu and the display
works fine.

Flash Drive:
xubuntu@xubuntu:~$ lspci -k | grep -EA3 'VGA|3D|Display'
:00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 
0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
xubuntu@xubuntu:~$ uname -r
6.5.0-9-generic

Please provide a workaround as this is my primary workstation.

Let me know if you need any additional information.

Thank you

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
Date: Mon Jan 15 10:37:25 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA 
controller])
   Subsystem: Dell AlderLake-S GT1 [1028:0a9f]
InstallationDate: Installed on 2023-10-14 (93 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/03/2024
dmi.bios.release: 2.11
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.11.1
dmi.board.name: 0KM9JV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.1:bd01/03/2024:br2.11:efr1.7:svnDellInc.:pnPrecision3660:pvr:rvnDellInc.:rn0KM9JV:rvrA00:cvnDellInc.:ct3:cvr:sku0A9F:
dmi.product.family: Precision
dmi.product.name: Precision 3660
dmi.product.sku: 0A9F
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic ubuntu

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

Title:
  Grayscreen

Status in xorg package in Ubuntu:
  New

Bug description:
  Dell Precision 3660

  I upgraded BIOS to 2.11.1 which also upgraded some other things.

  When I login into Xubuntu I get a frozen gray screen

  
  jim@jim:~/Scripts$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  jim@jim:~/Scripts$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915

  jim@jim:~/Scripts$ uname -r
  6.5.0-14-generic


  I can boot into the install flashdrive under Try Xubuntu and the
  display works fine.

  Flash Drive:
  xubuntu@xubuntu:~$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
  xubuntu@xubuntu:~$ uname -r
  6.5.0-9-generic

  Please provide a workaround as this is my primary workstation.

  Let me know if you need any additional information.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied:

[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

2024-01-15 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1833322

Title:
  Consider removing irqbalance from default install on desktop images

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

2024-01-15 Thread Sebastien Bacher

Speaking from a Desktop perspective, it's difficult to have a strong
opinion without data to backup the decision but it does feel like that
in the light of what other distributions/upstream are doing we should
reverse the default and go with option A and not have it by default but
an opt-in instead.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1833322

Title:
  Consider removing irqbalance from default install on desktop images

Status in Ubuntu on IBM z Systems:
  New
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2041491] Re: Provide an option to avoid the yaml NM backend

2024-01-15 Thread Lukas Märdian

Another option/idea I'd like to provide here is the migration script
used by NetworkManager [1], to transfer NM keyfiles from
/etc/NetworkManager/system-conncetions/ into /etc/netplan. This script
is automatically run on package upgrade of NetworkManager. I understand
this does not exactly fit the usecase described by alkisg, as you'd go
from debian-box:/etc/NetworkManager/system-connections -> ubuntu-
box:/etc/NetworkManager/system-connections -> migrate.sh -> ubuntu-
box:/run/NetworkManager/system-connections

Running "./migrate.sh configure" would transfer your copied original NM
keyfiles from a different box into Netplan and re-generate them in
/run/NetworkManager/system-connections:

```bash
# Run "Netplan Everywhere" migration after debhelper (re-)started
# NetworkManager.service for us. On every package upgrade.
DIR="/etc/NetworkManager/system-connections"
if [ "$1" = "configure" ] && [ -d "$DIR" ]; then
mkdir -p /run/netplan/nm-migrate
for CON in /etc/NetworkManager/system-connections/*; do
TYPE=$(file -bi "$CON" | cut -s -d ";" -f 1)
[ "$TYPE" = "text/plain" ] || continue # skip non-keyfiles
UUID=$(grep "^uuid=" "$CON" | cut -c 6-)
if [ -n "$UUID" ]
then
# Wait for NetworkManager startup to complete,
# so we can safely use nmcli. Wait in every interation to handle
# a crashed NetworkManager in the previous migraiton step.
if ! nm-online -qs; then
echo "SKIP: NetworkManager is not ready ..." 1>&2
continue
fi
BACKUP="/run/netplan/nm-migrate/"$(basename "$CON")
ORIG_NAME=$(nmcli --get-values connection.id con show "$UUID") || \
{ echo "SKIP: $(basename "$CON") ($UUID) unknown to 
NetworkManager." 1>&2 && \
  continue; }
cp "$CON" "$BACKUP"
echo "Migrating $ORIG_NAME ($UUID) to /etc/netplan" 1>&2
# Touch the connection's ID (con-name) to trigger its migration.
# The Netplan integration will translate the original NM keyfile 
from
# /etc/NetworkManager/system-connections/* to a YAML file located in
# /etc/netplan/90-NM-*.yaml and re-generate a corresponding keyfile 
in
# /run/NetworkManager/system-connections/netplan-NM-*.nmconnection
nmcli con mod "$UUID" con-name "$ORIG_NAME" || \
(echo "FAILED. Restoring backup ..." 1>&2 && mv "$BACKUP" 
"$CON" && \
 rm -f "/etc/netplan/90-NM-$UUID"*.yaml)
rm -f "$BACKUP" # clear backup (if it still exists)
   fi
done
rm -rf /run/netplan/nm-migrate # cleanup after ourselves
(nm-online -qs && nmcli con reload) || echo "WARNING: NetworkManager could 
not reload connections ..." 1>&2
fi
```

[1] https://git.launchpad.net/network-manager/tree/debian/network-
manager.postinst#n62

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2041491

Title:
  Provide an option to avoid the yaml NM backend

Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi, recently netplan added support for a yaml NM backend:

  https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-
  settings/32420

  The rationale is that "the descriptive YAML layer is especially useful
  in cloud environments":

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/556

  It's great that you care about that user group!
  Please also care for the rest of us that do not use cloud environments!

  For example, I routinely review, clone, backup or even directly edit
  the /etc/NetworkManager/system-connections files in my desktops and
  servers, in all distributions.

  Having an Ubuntu-specific way to do things will make things harder for
  me. I will have to learn a new Ubuntu-specific syntax, develop scripts
  and methods to convert my connections between distributions, I will
  need to discover and report bugs in the netplan <=> nm mapping etc...

  I.e. Ubuntu is great for the cloud, and it's awesome that you want to provide 
a unified yaml-based experience for cloud-init etc.
  But Ubuntu is also great outside the cloud; please allow us to continue 
having a unified experience between distributions (i.e. directly using nm or 
systemd-networkd) without enforcing an Ubuntu-specific way of doing things 
(netplan) to us.

  For Ubuntu 24.04+, please provide an option to avoid the yaml NM
  backend, thank you very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041491/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   :

[Desktop-packages] [Bug 2049395] [NEW] seahorse use 100% CPU after attempt to change OpenSSH Passphrase

2024-01-15 Thread krom

Public bug reported:

Seems to be similar to bug #556349, but hidden a little deeper.


I have various OpenSSH keys credentials stored for seahorse. Those OpenSSH keys 
are displayes using a tabbed list view in seahorse. When double-clicking an 
entry, to view details (including masked / unmasked) password, then click 
"Change Passphrase", cancel or change changing and now the CPU Load goes to 
100% upon the dialog being opened.


Reproduce:

1) Run seahorse with some OpenSSH keys.
2) Click "OpenSSH keys" on the left panel.
3) Double-click on some of you SSH keys.
4) Click "Change Passphrase".
5) Click "Cancel". (or really change pass, works for me too)

Observe CPU Consumption.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: seahorse 41.0-2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 15 15:53:31 2024
InstallationDate: Installed on 2023-05-08 (252 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
SourcePackage: seahorse
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** Summary changed:

- seahorse use 100% CPU after attempt to change Passphrase
+ seahorse use 100% CPU after attempt to change OpenSSH Passphrase

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

Title:
  seahorse use 100% CPU after attempt to change OpenSSH Passphrase

Status in seahorse package in Ubuntu:
  New

Bug description:
  Seems to be similar to bug #556349, but hidden a little deeper.

  
  I have various OpenSSH keys credentials stored for seahorse. Those OpenSSH 
keys are displayes using a tabbed list view in seahorse. When double-clicking 
an entry, to view details (including masked / unmasked) password, then click 
"Change Passphrase", cancel or change changing and now the CPU Load goes to 
100% upon the dialog being opened.

  
  Reproduce:

  1) Run seahorse with some OpenSSH keys.
  2) Click "OpenSSH keys" on the left panel.
  3) Double-click on some of you SSH keys.
  4) Click "Change Passphrase".
  5) Click "Cancel". (or really change pass, works for me too)

  Observe CPU Consumption.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: seahorse 41.0-2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 15 15:53:31 2024
  InstallationDate: Installed on 2023-05-08 (252 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: seahorse
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 628293] Re: gnome-default-applications-properties does not set needs_term for mailer presets

** Changed in: control-center (Debian)
   Status: New => Fix Released

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

Title:
  gnome-default-applications-properties does not set  needs_term for
  mailer presets

Status in gnome-control-center:
  Expired
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in control-center package in Debian:
  Fix Released

Bug description:
  Binary package hint: gnome-control-center

  This bug is a duplicate of Debian's #537278.

  If you select mutt as a preferred mail reader application in gnome-
  default-application-properties, it is not automatically set to run in
  a terminal. The gconf property /desktop/gnome/url-
  handlers/mailto/needs_terminal isn't set either to the correct value,
  which is found in gnome-default-applications.xml.

  Steps to reproduce :
  1. On a default install of Ubuntu lucid, install mutt
  2. open gnome-default-application-properties
  3. select mutt as the preferred mail reader application and close
  4. in a terminal, type : gconftool-2 -a /desktop/gnome/url-handlers/mailto

  Expected result :
   command = mutt %s
   needs_terminal = true
   enabled = true

  Actual result :
   command = mutt %s
   needs_terminal = false
   enabled = true

  You will find enclosed a patch that corrects this behavior for the
  Mail Reader, but I think that the same problem concerns the Web
  Browser and the Multimedia player.

  System information :
  $ lsb_release -rd
  Description:  Ubuntu 10.04.1 LTS
  Release:  10.04

  $ apt-cache policy gnome-control-center
  gnome-control-center:
Installed: 1:2.30.1-0ubuntu1
Candidate: 1:2.30.1-0ubuntu1
Version table:
   *** 1:2.30.1-0ubuntu1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
  100 /var/lib/dpkg/status
   1:2.30.0-0ubuntu4 0
  500 http://fr.archive.ubuntu.com/ubuntu/ lucid/main Packages

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049362] Re: The latex package glossarie has a typo in the name of a dependency.

2024-01-15 Thread Christoph Scherr

The problem was a typo in my code. Didn't think of that, sorry. Have a
nice day everyone.

** Changed in: texlive-extra (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-extra in Ubuntu.
https://bugs.launchpad.net/bugs/2049362

Title:
  The latex package glossarie has a typo in the name of a dependency.

Status in texlive-extra package in Ubuntu:
  Invalid

Bug description:
  the latex package "glosssaries" needs a file called "glosssaries.sty" but the 
  system only provides a file called "glossaries.sty" (one file has 'sss', 
while 
  the other one has 'ss'). I highly suspect that the file name contains a typo, 
  resulting in users being unable to use the glossaries latex package.

  Minimal (not) working example:

  ```tex
  \documentclass{article}
  \usepackage{glosssaries}
  \makeglossaries
  \newglossaryentry{latex}
  {
  name=latex,
  description={Is a mark up language specially suited for
  scientific documents}
  }

  \begin{document}
  foo bar qux \Gls{latex}
  \end{document}
  ```

  See that the latex "compiler does not find the file (with 'sss'):
  ```bash
  $ pdflatex master.tex
  This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) 
(preloaded format=pdflatex)
   restricted \write18 enabled.
  entering extended mode
  (./master.tex
  LaTeX2e <2021-11-15> patch level 1
  L3 programming layer <2022-01-21>
  (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
  Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
  (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))

  ! LaTeX Error: File `glosssaries.sty' not found.

  Type X to quit or  to proceed,
  or enter new name. (Default extension: sty)

  Enter file name:
  ```

  For a workaround, users can manually specify the filename when being
  asked as "glossaries.tex". Clearly the glossaries package has a typo
  in the dependency. Note that "glossaries.sty" is part of the texlive-
  latex-extra package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: texlive-latex-extra 2021.20220204-1
  Uname: Linux 5.15.133.1-microsoft-standard-WSL2 x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Jan 15 09:58:48 2024
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/zsh
  SourcePackage: texlive-extra
  UpgradeStatus: Upgraded to jammy on 2023-06-26 (202 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/2049362/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1833322] Comment bridged from LTC Bugzilla

2024-01-15 Thread bugproxy

--- Comment From cborn...@de.ibm.com 2024-01-15 06:46 EDT---
Just a statement from s390x/IBM Z. For our platform irqbalance makes no sense 
as our interrupt handling works differently. So we do not need it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1833322

Title:
  Consider removing irqbalance from default install on desktop images

Status in Ubuntu on IBM z Systems:
  New
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2

This bug was fixed in the package mutter - 45.2-0ubuntu3

---
mutter (45.2-0ubuntu3) mantic; urgency=medium

[ Jeremy Bícha ]
* Revert roll back to 45.0-3ubuntu3.1

[ Daniel van Vugt ]
* Update Support-Dynamic-triple-double-buffering.patch
with a fix to the frame clock for a regression inherited from
45.1 (8f27ebf8) whereby it would enter triple buffering mode
prematurely. And because it was premature, the clock would soon
notice that triple buffering isn't required and drop back to double
buffering. But the switch from triple to double buffering stalls the
client frame queue by one frame which for some clients like Firefox
is seen as a frame skip. (LP: #2046360)

mutter (45.2-0ubuntu2~really45.0) mantic; urgency=medium

* Roll back to address regression LP: #2046360.
- Full revert to mutter 45.0-3ubuntu3.1, with revert implemented under
debian/patches to avoid having to keep around confusing version numbers
for very long.
- mutter 45.2 introduces new library symbols vs 45.0 but no packages
have picked up dependencies on these symbols yet via rebuilds, and all
binary packages built from mutter source have a strict versioned
dependency on the library package; so a straight revert of the symbols
file is possible without the need to add any additional Breaks.

mutter (45.2-0ubuntu1) mantic; urgency=medium

[ Jeremy Bícha ]
* New upstream release (LP: #2043000)
- Fix entering capital accent letters with Caps Lock (LP: #2035076)
- Fix Wacom on X11 issues (LP: #2043027)
* debian/libmutter-13-0.symbols: Add new symbols
* Drop patches applied in new release
* Rebase X11 fractional scaling patch

[ Daniel van Vugt ]
* Rebase triple buffering patch

-- Jeremy Bícha Tue, 02 Jan 2024 08:28:40 -0500

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

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

Title:
Heavy stuttering in Firefox with mutter 45.1/45.2

Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Mantic:
Fix Released

Bug description:
[ Impact ]

There is heavy stuttering visible in Firefox with mutter 45.1/45.2
when kinetic scrolling a non-animated web page with a touchpad. This
is a regression introduced upstream in mutter 45.1 (8f27ebf8).

[ Test Plan ]

0. Find a laptop with a touchpad.
1. Open a simple web page like a Wikipedia page in Firefox.
2. Use two fingers on the touchpad to fling it so it continues scrolling.

Expect: The scrolling proceeds and slows perfectly smoothly.

[ Where problems could occur ]

Anywhere in frame scheduling (visual smoothness), since that is the
code affected.

[ Other Info ]

The bug was introduced upstream in 45.1 by

https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d
but since it only hurts the triple buffering patch, that's where it
has been fixed:

https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689

https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45

[ Workaround ]

In /etc/environment:

MUTTER_DEBUG_TRIPLE_BUFFERING=always

or "never" also works. Just not "auto" because the bug is in auto mode
(the default).

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

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049372] [NEW] Libreoffice prints N^2 copies - cups-filters

2024-01-15 Thread James Murray

Public bug reported:

Whenever I print from Libreoffice I get the square of the number of
copies I requested.

I am the sole user, printing single sided to a HP LaserJet P1606DN over
ethernet.

I have listed this as 'cups-filters' as the other bug reports below
believe that's where this originates.

This is on a recently purchased Dell PC preloaded with Ubuntu 22. (I
have been using Ubuntu for many years on different hardware but was on
an older LTS release which did not have this problem.)

$ lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04

$ apt-cache policy cups-filters
cups-filters:
  Installed: 1.28.15-0ubuntu1.2
  Candidate: 1.28.15-0ubuntu1.2
  Version table:
 *** 1.28.15-0ubuntu1.2 500
500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
 1.28.15-0ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
 1.8.3-2ubuntu3.5 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages


See the same/similar issue here:
https://askubuntu.com/questions/1188154/cups-prints-n%C2%B2-copies-when-collation-is-enabled

https://unix.stackexchange.com/questions/265538/cups-prints-n%C2%B2-as-
many-copies-as-i-want

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups-filters 1.28.15-0ubuntu1.2
ProcVersionSignature: Ubuntu 6.1.0-1026.26-oem 6.1.57
Uname: Linux 6.1.0-1026-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/efi.img ./casper/initrd ./casper/vmlinuz 
./scripts/chroot-scripts/os-post/70_fix-apt-installed.sh
CasperMD5CheckResult: fail
CupsErrorLog:
 
CurrentDesktop: MATE
Date: Mon Jan 15 09:57:47 2024
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-jammy-amd64-20220504-33
InstallationDate: Installed on 2023-10-18 (88 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
Lpstat:
 device for Brother_MFC_J5910DW: implicitclass://Brother_MFC_J5910DW/
 device for HP_LaserJet_Professional_P1606dn: 
implicitclass://HP_LaserJet_Professional_P1606dn/
MachineType: Dell Inc. Precision 3660
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_Professional_P1606dn.ppd', 
'/etc/cups/ppd/Brother_MFC_J5910DW.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP_LaserJet_Professional_P1606dn.ppd: Permission denied
 grep: /etc/cups/ppd/Brother_MFC_J5910DW.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1026-oem 
root=UUID=bbe1e6aa-bb8a-4d14-939a-0e21fa783921 ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: cups-filters
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/16/2023
dmi.bios.release: 2.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.1
dmi.board.name: 0PRR48
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.3
dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd05/16/2023:br2.5:efr1.3:svnDellInc.:pnPrecision3660:pvr:rvnDellInc.:rn0PRR48:rvrA01:cvnDellInc.:ct3:cvr:sku0A9F:
dmi.product.family: Precision
dmi.product.name: Precision 3660
dmi.product.sku: 0A9F
dmi.sys.vendor: Dell Inc.

** Affects: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/2049372

Title:
  Libreoffice prints N^2 copies - cups-filters

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Whenever I print from Libreoffice I get the square of the number of
  copies I requested.

  I am the sole user, printing single sided to a HP LaserJet P1606DN
  over ethernet.

  I have listed this as 'cups-filters' as the other bug reports below
  believe that's where this originates.

  This is on a recently purchased Dell PC preloaded with Ubuntu 22. (I
  have been using Ubuntu for many years on different hardware but was on
  an older LTS release which did not have this problem.)

  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  $ apt-cache policy cups-filters
  cups-filters:
Installed: 1.28.15-0ubuntu1.2
Candidate: 1.28.15-0ubuntu1.2
Version table:
   *** 1.28.15-0ubuntu1.2 500
  500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.28.15-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu

[Desktop-packages] [Bug 2048438] ProcEnviron.txt

apport information

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

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

Title:
  Dual monitor extend (join) not working with Wayland with p14s ThinkPad
  laptop

Status in xwayland package in Ubuntu:
  New

Bug description:
  I have a Lenovo ThinkPad P14s gen4 amd laptop, which has an integrated
  GPU.

  I installed Ubuntu 23.10, and it defaults to using Wayland and
  connected it to an external Dell Dell P2720D monitor via HDMI.

  The UI under Settings > Displays then "Mirror", the default setting
  works, and I see the display duplicated as expected, with the large
  external monitor having a low resolution limited to that of the
  laptop.

  But if I switch to "Join" does not allow to Apply with message:

  > Changes Cannot be Applied. This could be due to hardware
  limitations.

  Logging off and changing to X allows "Join" to work, so it is a
  Wayland issue.

  Is there a way to make it work on Wayland? Mostly out of morbid curiosity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-11-25 (51 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  Package: xwayland 2:23.2.0-1ubuntu0.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Tags: mantic
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2048438] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  Dual monitor extend (join) not working with Wayland with p14s ThinkPad
  laptop

Status in xwayland package in Ubuntu:
  New

Bug description:
  I have a Lenovo ThinkPad P14s gen4 amd laptop, which has an integrated
  GPU.

  I installed Ubuntu 23.10, and it defaults to using Wayland and
  connected it to an external Dell Dell P2720D monitor via HDMI.

  The UI under Settings > Displays then "Mirror", the default setting
  works, and I see the display duplicated as expected, with the large
  external monitor having a low resolution limited to that of the
  laptop.

  But if I switch to "Join" does not allow to Apply with message:

  > Changes Cannot be Applied. This could be due to hardware
  limitations.

  Logging off and changing to X allows "Join" to work, so it is a
  Wayland issue.

  Is there a way to make it work on Wayland? Mostly out of morbid curiosity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-11-25 (51 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  Package: xwayland 2:23.2.0-1ubuntu0.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Tags: mantic
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2048438] Re: Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop

apport information

** Tags added: apport-collected mantic

** Description changed:

  I have a Lenovo ThinkPad P14s gen4 amd laptop, which has an integrated
  GPU.
  
  I installed Ubuntu 23.10, and it defaults to using Wayland and connected
  it to an external Dell Dell P2720D monitor via HDMI.
  
  The UI under Settings > Displays then "Mirror", the default setting
  works, and I see the display duplicated as expected, with the large
  external monitor having a low resolution limited to that of the laptop.
  
  But if I switch to "Join" does not allow to Apply with message:
  
  > Changes Cannot be Applied. This could be due to hardware limitations.
  
  Logging off and changing to X allows "Join" to work, so it is a Wayland
  issue.
  
- Is there a way to make it work on Wayland? Mostly out of morbid
- curiosity.
+ Is there a way to make it work on Wayland? Mostly out of morbid curiosity.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu5
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2023-11-25 (51 days ago)
+ InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
+ Package: xwayland 2:23.2.0-1ubuntu0.3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
+ Tags: mantic
+ Uname: Linux 6.5.0-14-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin ollama plugdev sudo users
+ _MarkForUpload: True

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

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

Title:
  Dual monitor extend (join) not working with Wayland with p14s ThinkPad
  laptop

Status in xwayland package in Ubuntu:
  New

Bug description:
  I have a Lenovo ThinkPad P14s gen4 amd laptop, which has an integrated
  GPU.

  I installed Ubuntu 23.10, and it defaults to using Wayland and
  connected it to an external Dell Dell P2720D monitor via HDMI.

  The UI under Settings > Displays then "Mirror", the default setting
  works, and I see the display duplicated as expected, with the large
  external monitor having a low resolution limited to that of the
  laptop.

  But if I switch to "Join" does not allow to Apply with message:

  > Changes Cannot be Applied. This could be due to hardware
  limitations.

  Logging off and changing to X allows "Join" to work, so it is a
  Wayland issue.

  Is there a way to make it work on Wayland? Mostly out of morbid curiosity.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-11-25 (51 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  Package: xwayland 2:23.2.0-1ubuntu0.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Tags: mantic
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin ollama plugdev sudo users
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049368] Re: gnome-shell crash while chaing Chromium browser tab

And backtrace:

#0  __pthread_kill_implementation (no_tid=0, signo=5, threadid=) 
at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=5, threadid=) at 
./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=, signo=signo@entry=5) at 
./nptl/pthread_kill.c:89
#3  0x7f62b5842866 in __GI_raise (sig=5) at ../sysdeps/posix/raise.c:26
#4  0x562470b03bda in ??? ()
#5  0x7f62b5842910 in  () at 
/lib/x86_64-linux-gnu/libc.so.6
#6  0x7f62b62e5867 in g_log_structured_array () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f62b62e5b52 in g_log_default_handler () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f62b62e69e2 in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f62b62e6ca3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f62b68ab59e in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0
#11 0x7f62b5704a5b in _XError (dpy=dpy@entry=0x562471d040d0, 
rep=rep@entry=0x7ffdc2b64ef0) at ../../src/XlibInt.c:1503
#12 0x7f62b1f63adb in __glXSendError (dpy=0x562471d040d0, 
errorCode=, resourceID=0, minorCode=, 
coreX11error=0) at ../src/GLX/libglx.c:805
#13 0x7f62b5f0962f in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#14 0x7f62b5f09d29 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#15 0x7f62b5f0734e in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#16 0x7f62b5ee347b in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#17 0x7f62b5ee29d5 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#18 0x7f62b5ee3460 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#19 0x7f62b5ee29d5 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#20 0x7f62b5ee3460 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#21 0x7f62b62d99a0 in g_list_foreach () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7f62b62d9f9f in g_list_free_full () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7f62b5ee9c0a in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#24 0x7f62b5ed00e2 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#25 0x7f62b5ed0723 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#26 0x7f62b5ee99eb in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#27 0x7f62b5ec9ea4 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#28 0x7f62b5f012c2 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#29 0x7f62b5f01716 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#30 0x7f62b5f01942 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#31 0x7f62b5f02113 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#32 0x7f62b5f02cb3 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#33 0x7f62b5f05c96 in cogl_onscreen_swap_buffers_with_damage () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
#34 0x7f62b5ca4e70 in ??? () at /lib/x86_64-linux-gnu/libmutter-13.so.0
#35 0x7f62b5ca54cb in ??? () at /lib/x86_64-linux-gnu/libmutter-13.so.0
#36 0x7f62b5cfd5f2 in ??? () at /lib/x86_64-linux-gnu/libmutter-13.so.0
#37 0x7f62b60d97d6 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0
#38 0x7f62b60a5422 in ??? () at 
/usr/lib/x86_64-linux-gnu/mutter-13/libmutter-clutter-13.so.0
#39 0x7f62b62deb2c in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#40 0x7f62b633a46f in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#41 0x7f62b62df46f in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#42 0x7f62b5ccbb19 in meta_context_run_main_loop () at 
/lib/x86_64-linux-gnu/libmutter-13.so.0
#43 0x7f62b5e528b6 in ??? () at /lib/x86_64-linux-gnu/libffi.so.8
#44 0x7f62b5e4f34d in ??? () at /lib/x86_64-linux-gnu/libffi.so.8
#45 0x7f62b5e51f33 in ffi_call () at /lib/x86_64-linux-gnu/libffi.so.8
#46 0x7f62b619292e in ??? () at /lib/x86_64-linux-gnu/libgjs.so.0
#47 0x7f62b6193a27 in ??? () at /lib/x86_64-linux-gnu/libgjs.so.0
#48 0x7f62b3363970 in ??? () at /lib/x86_64-linux-gnu/libmozjs-115.so.0
#49 0x7f62b3357cdf in ??? () at /lib/x86_64-linux-gnu/libmozjs-115.so.0
#50 0x7f62b33634db in ??? () at /lib/x86_64-linux-gnu/libmozjs-115.so.0
#51 0x7f62b3363847 in ??? () at /lib/x86_64-linux-gnu/libmozjs-115.so.0
#52 0x7f62b3363db9 in ??? () at /lib/x86_64-linux-gnu/libmozjs-115.so.0
#53 0x7f62b33d8820 in JS::Call(JSContext*, JS::Handle, 
JS::Handle, JS::HandleValueArray const&, 
JS::MutableHandle) ()
at /lib/x86_64-linux-gnu/libmozjs-115.so.0
#54 0x7f62b61c5090 in ??? () at /lib/x86_64-linux-gnu/libgjs.so.0
#55 0x7f62b61cb697 in gjs_context_eval_module () at

[Desktop-packages] [Bug 2049368] [NEW] gnome-shell crash while chaing Chromium browser tab

Public bug reported:

Casual browsing, and then boom "Oh no! Something has gone wrong" screen.
Ubuntu 23.10, Lenovo ThinkPad P14s gen4 amd, AMDGPU open source drivers,
also I switched to X Server from the default Wayland because of Wayland
bugs.

A stack trace frame I got manually, but I didn't persist much:

```
─── Stack 
───(138
 results) [2033/2675]
[12] from 0x7f62b1f63adb in __glXSendError+155 at ../src/GLX/libglx.c:805   

  
arg dpy = 0x562471d040d0, errorCode = , resourceID = 0, 
minorCode = , coreX11error = 0   
   
[13] from 0x7f62b5f0962f

  
(no arguments)  

  
[14] from 0x7f62b5f09d29

  
(no arguments)  

  
[15] from 0x7f62b5f0734e

  
(no arguments)  

  
[16] from 0x7f62b5ee347b

  
(no arguments)  

  
[+] 

  
─── Source 
───
789 if (dpyInfo == NULL || !dpyInfo->glxSupported) {

  
790 return; 

  
791 }   

  
792 

  
793 LockDisplay(dpy);   

  
794 

  
795 error.type = X_Error;   

  
796 error.errorCode = errorCode;

  
797 error.sequenceNumber = dpy->request;

  
798 error.resourceID = resourceID;  

  
799 error.minorCode = minorCode;

  
800 error.majorCode = dpyInfo->glxMajorOpcode;

[Desktop-packages] [Bug 1958019]

2024-01-15 Thread attitokes

(In reply to August Wikerfors from comment #781)
> (In reply to Christian G. Semke from comment #780)
> > Here on my Lenovo Legion 7 Slim the audio never worked and the microphone
> > worked until 6.4, now in 6.5 nothing works anymore. Does anyone know how I
> > can resolve this? I'm a bit of a beginner
> > 
> > Alsa:
> http://alsa-project.org/db/?f=24e78ce46f588c8a681c092c24e05811a4f42f77
> > Kernel: 6.5.2-arch1-1
> 
> I've submitted this patch which should fix it:
> https://lore.kernel.org/all/20230911213409.6106-1-...@augustwikerfors.se/

Hey! Looks like this acp6x-mach/yc_acp_quirk_table workaround would also
be needed for Yoga Slim 7 Pro 14ARH7 (LENOVO/82UU). I have one, and the
microphone does not works.

ALSA info:
https://alsa-project.org/db/?f=77e94edfeb14c5e3bf3ffb9524fb5d8390e1b722

>From the kernel logs looks like snd_pci_acp6x detects and enables a device:
```
[7.120140] snd_pci_acp6x :32:00.5: enabling device ( -> 0002)
```
but then there is nothing acp_yc_mach related in the logs.

I would appreciate if you could make a patch. Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049309] Re: wayland fractional scaling breaks some screenshares

I think screen sharing is instigated from gnome-shell rather than being
an underlying mutter feature so perhaps report the bug to
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues

But they will likely also want you to check the bug still exists in
GNOME 45 (Ubuntu 23.10).

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

Title:
  wayland fractional scaling breaks some screenshares

Status in mutter package in Ubuntu:
  New

Bug description:
  1) Ubuntu 22.04.3 LTS with Gnome and Wayland
  2) Unsure what package is the problem, here are the versions of a few:
  gnome-shell 42.9-0ubuntu2
  xdg-desktop-portal 1.14.4-1ubuntu2~22.04.1
  xdg-desktop-portal-gnome 42.1-0ubuntu1
  xdg-desktop-portal-gtk 1.14.0-1build1
  3) expected: with fractional scaling enabled, sharing a window to an 
application would share the full window
  4) actual: for some apps, only the top-right part of the window is shared

  Some apps are displayed correctly, like terminal and file explorer,
  but other apps only show the top-right, such as virtualbox and
  vscodium. When fractional scaling is disabled, these apps share
  properly again.

  It doesn't seem to depend on the app you are sharing to, I tested it
  on firefox, chromium, and OBS studio and it was consistent across all
  3. Attached is a screenshot of virtualbox being shared through
  chromium and only the top left part of the window is being shared.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049362] [NEW] The latex package glossarie has a typo in the name of a dependency.

2024-01-15 Thread Christoph Scherr

Public bug reported:

the latex package "glosssaries" needs a file called "glosssaries.sty" but the 
system only provides a file called "glossaries.sty" (one file has 'sss', while 
the other one has 'ss'). I highly suspect that the file name contains a typo, 
resulting in users being unable to use the glossaries latex package.

Minimal (not) working example:

```tex
\documentclass{article}
\usepackage{glosssaries}
\makeglossaries
\newglossaryentry{latex}
{
name=latex,
description={Is a mark up language specially suited for
scientific documents}
}

\begin{document}
foo bar qux \Gls{latex}
\end{document}
```

See that the latex "compiler does not find the file (with 'sss'):
```bash
$ pdflatex master.tex
This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./master.tex
LaTeX2e <2021-11-15> patch level 1
L3 programming layer <2022-01-21>
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))

! LaTeX Error: File `glosssaries.sty' not found.

Type X to quit or  to proceed,
or enter new name. (Default extension: sty)

Enter file name:
```

For a workaround, users can manually specify the filename when being
asked as "glossaries.tex". Clearly the glossaries package has a typo in
the dependency. Note that "glossaries.sty" is part of the texlive-latex-
extra package.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: texlive-latex-extra 2021.20220204-1
Uname: Linux 5.15.133.1-microsoft-standard-WSL2 x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Jan 15 09:58:48 2024
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/zsh
SourcePackage: texlive-extra
UpgradeStatus: Upgraded to jammy on 2023-06-26 (202 days ago)

** Affects: texlive-extra (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-extra in Ubuntu.
https://bugs.launchpad.net/bugs/2049362

Title:
  The latex package glossarie has a typo in the name of a dependency.

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  the latex package "glosssaries" needs a file called "glosssaries.sty" but the 
  system only provides a file called "glossaries.sty" (one file has 'sss', 
while 
  the other one has 'ss'). I highly suspect that the file name contains a typo, 
  resulting in users being unable to use the glossaries latex package.

  Minimal (not) working example:

  ```tex
  \documentclass{article}
  \usepackage{glosssaries}
  \makeglossaries
  \newglossaryentry{latex}
  {
  name=latex,
  description={Is a mark up language specially suited for
  scientific documents}
  }

  \begin{document}
  foo bar qux \Gls{latex}
  \end{document}
  ```

  See that the latex "compiler does not find the file (with 'sss'):
  ```bash
  $ pdflatex master.tex
  This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) 
(preloaded format=pdflatex)
   restricted \write18 enabled.
  entering extended mode
  (./master.tex
  LaTeX2e <2021-11-15> patch level 1
  L3 programming layer <2022-01-21>
  (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
  Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
  (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))

  ! LaTeX Error: File `glosssaries.sty' not found.

  Type X to quit or  to proceed,
  or enter new name. (Default extension: sty)

  Enter file name:
  ```

  For a workaround, users can manually specify the filename when being
  asked as "glossaries.tex". Clearly the glossaries package has a typo
  in the dependency. Note that "glossaries.sty" is part of the texlive-
  latex-extra package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: texlive-latex-extra 2021.20220204-1
  Uname: Linux 5.15.133.1-microsoft-standard-WSL2 x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Jan 15 09:58:48 2024
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/zsh
  SourcePackage: texlive-extra
  UpgradeStatus: Upgraded to jammy on 2023-06-26 (202 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/2049362/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049309] Re: wayland fractional scaling breaks some screenshares

2024-01-15 Thread Paul White

** Tags added: jammy

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

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

Title:
  wayland fractional scaling breaks some screenshares

Status in mutter package in Ubuntu:
  New

Bug description:
  1) Ubuntu 22.04.3 LTS with Gnome and Wayland
  2) Unsure what package is the problem, here are the versions of a few:
  gnome-shell 42.9-0ubuntu2
  xdg-desktop-portal 1.14.4-1ubuntu2~22.04.1
  xdg-desktop-portal-gnome 42.1-0ubuntu1
  xdg-desktop-portal-gtk 1.14.0-1build1
  3) expected: with fractional scaling enabled, sharing a window to an 
application would share the full window
  4) actual: for some apps, only the top-right part of the window is shared

  Some apps are displayed correctly, like terminal and file explorer,
  but other apps only show the top-right, such as virtualbox and
  vscodium. When fractional scaling is disabled, these apps share
  properly again.

  It doesn't seem to depend on the app you are sharing to, I tested it
  on firefox, chromium, and OBS studio and it was consistent across all
  3. Attached is a screenshot of virtualbox being shared through
  chromium and only the top left part of the window is being shared.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049353] Re: wayland XWarpPointer backwards compability

** Changed in: wayland
   Status: Unknown => New

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

Title:
  wayland XWarpPointer backwards compability

Status in wayland:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  I'm not sure how to report this really as it's not a bug but still
  quite severe. Bear with me as I'm a Unity dev mainly.

  Unity uses function calls to X11 for setting mouse cursor positions.
  Many games use this to lock the cursor to a certain position.

  With no backwards compatibility to XWarpPointer these games will be broken in 
Wayland.
  As there's little chance these games will be updated, the only possibility 
here is that Wayland supports this in some way.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2049309] [NEW] wayland fractional scaling breaks some screenshares

You have been subscribed to a public bug:

1) Ubuntu 22.04.3 LTS with Gnome and Wayland
2) Unsure what package is the problem, here are the versions of a few:
gnome-shell 42.9-0ubuntu2
xdg-desktop-portal 1.14.4-1ubuntu2~22.04.1
xdg-desktop-portal-gnome 42.1-0ubuntu1
xdg-desktop-portal-gtk 1.14.0-1build1
3) expected: with fractional scaling enabled, sharing a window to an 
application would share the full window
4) actual: for some apps, only the top-right part of the window is shared

Some apps are displayed correctly, like terminal and file explorer, but
other apps only show the top-right, such as virtualbox and vscodium.
When fractional scaling is disabled, these apps share properly again.

It doesn't seem to depend on the app you are sharing to, I tested it on
firefox, chromium, and OBS studio and it was consistent across all 3.
Attached is a screenshot of virtualbox being shared through chromium and
only the top left part of the window is being shared.

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


** Tags: bot-comment jammy
-- 
wayland fractional scaling breaks some screenshares
https://bugs.launchpad.net/bugs/2049309
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mutter in Ubuntu.

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)

This bug was fixed in the package gnome-shell - 3.36.9-0ubuntu0.20.04.3

---
gnome-shell (3.36.9-0ubuntu0.20.04.3) focal; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Cherry-pick upstream calendar-server crash fix
(LP: #1915929)
  * debian/patches: Refresh indexes

  [ Daniel van Vugt ]
  * Add edgeDragAction-Change-edge-trigger-threshold-to-AFTER.patch
(LP: #2042796)

 -- Marco Trevisan (Treviño)   Mon, 11 Dec 2023
20:08:17 +0100

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

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

Title:
  gnome-shell-calendar-server assert failure on arm64: double free or
  corruption (fasttop)

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released
Status in gnome-shell source package in Hirsute:
  Fix Released

Bug description:
  [ Impact ]

  gnome-shell-calendar-server crashes (and it seems to happen more in
  aarch64).

  https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a
  https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1

  [ Test case ]

  There's not a clear test case, but this is relevant:
   - Configure a supported calendar in your online accounts 
   - GNOME shell should show your events in the calendar (under notifications 
panel)

  [ Regression potential ]

  gnome-shell-calendar-server may leak memory.

  
  ---

  M1 Mac mini
  Parallels Ubuntu VM

  ProblemType: CrashDistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic aarch64
  ApportVersion: 2.20.11-0ubuntu58
  Architecture: arm64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 17 04:34:36 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/libexec/gnome-shell-calendar-server
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
   b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true'
  InstallationDate: Installed on 2021-02-17 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217)
  ProcCmdline: /usr/libexec/gnome-shell-calendar-server
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x81245180 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x81240c08 "double free or corruption 
(fasttop)") at malloc.c:5389
   _int_free (av=, p=0xe9eee300, have_lock=0) at 
malloc.c:4298
   g_variant_builder_clear () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
   ?? ()
  Title: gnome-shell-calendar-server assert failure: double free or corruption 
(fasttop)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2042796] Update Released

2024-01-15 Thread Łukasz Zemczak

The verification of the Stable Release Update for gnome-shell 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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2042796

Title:
  Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't
  respond to taps if they are very small

Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Triaged
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Touchscreen touches at the left or bottom edges (within 20px) of the
  screen are not treated as mouse clicks. Icons only get highlighted,
  not launched.

  [ Test Plan ]

  0. Find a touchscreen.
  1. Set Ubuntu Dock in Panel mode (the default mode) if not already.
  2. Touch as close to the edge of the screen as possible. Aim for the gap 
between the icon and the edge of the screen.

  Expect: The app launch animation occurs for each tap. Icons aren't
  just highlighted.

  [ Where problems could occur ]

  Anywhere in touchscreen gesture tracking or even regular touchscreen
  usage. As this bug demonstrates, the former is able to interfere with
  even simple touchscreen actions.

  [ Workaround ]

  Size the Ubuntu Dock adequately large so it is unlikely the user will
  touch less than 20 pixels from the edge of the screen.

  [ Original description ]

  On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance,
  adjust the dock icon-size to 24. It is hard to launch corner app like
  firefox, or trigger the launcher. The app icon gets focus but not
  clicked.

  1. Ubuntu version 20.04.6
  2. gnome-shell 3.36.9-0ubuntu0.20.04.2
  3. The app or launcher is launched after a click
  4. Only see focus but no app launched

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2042796] Re: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't respond to taps if they are very small