[Desktop-packages] [Bug 2036647] Re: gnome-terminal-server crashed with SIGSEGV in g_utf8_pointer_to_offset()

[Daniel van Vugt]

** Information type changed from Private to Public

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

Title:
  gnome-terminal-server crashed with SIGSEGV in
  g_utf8_pointer_to_offset()

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Gnome terminal just crashed, was moving pointer across window.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-terminal 3.49.92-2ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 22:39:00 2023
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2023-09-18 (1 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918)
  ProcCmdline: /usr/libexec/gnome-terminal-server
  SegvAnalysis:
   Segfault happened at: 0x7f58c3c30180 :  movzbl 
(%rsi),%ecx
   PC (0x7f58c3c30180) ok
   source "(%rsi)" (0x5646400b2000) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_utf8_pointer_to_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ??? () at /lib/x86_64-linux-gnu/libvte-2.91.so.0
   ??? () at /lib/x86_64-linux-gnu/libvte-2.91.so.0
   ??? () at /lib/x86_64-linux-gnu/libvte-2.91.so.0
   ??? () at /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-terminal-server crashed with SIGSEGV in 
g_utf8_pointer_to_offset()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2036647/+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

[Daniel van Vugt]

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** No longer affects: nvidia-graphics-drivers-525 (Ubuntu)

** Changed in: mutter (Ubuntu)
   Status: Triaged => In Progress

** Changed in: mutter (Ubuntu)
   Importance: High => Medium

-- 
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 1962327]

[Buzea-bogdan]

Created attachment 189723
screenshot

This is how LibreOffice render now this document.
Seems ok to me.

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: a34dcd03254480927c403d904c0e754802d97b90
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

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

Title:
  [Upstream] Vertical fraction feature present in font not applied by
  Writer

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

Bug description:
  
  ~ $ lsb_release -rd 
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
   ~$ apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:6.4.7-0ubuntu0.20.04.2
Candidate: 1:6.4.7-0ubuntu0.20.04.2
Version table:
   *** 1:6.4.7-0ubuntu0.20.04.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:6.4.2-0ubuntu3 500
  500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  ~$ apt-show-versions -r libreoffice* 
  liblibreofficekitgtk:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-gtk:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-gtk2:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-java-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-l10n-bn:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-math:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-style-colibre:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-style-elementary:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 
uptodate
  libreoffice-style-tango:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreoffice-writer:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate
  libreofficekit-data:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate

  What is expected to happen in Writer is

  My font has vertical fraction look up for Bengali script. On selecting
  Format > Characters > CTL Font > Features Alternate (vertical)
  Fraction Feature is visible in options. Selecting the option should
  apply the feature on selected fraction

  see screenshot http://cloud.atipra.in/index.php/s/YosGiyFSoTQeW8i 
  What happened instead is..

  The feature is not applied, and the selected text is unchanged

  It should change as happens in firefox on selecting alternate (Vertical) 
fraction lookup in css
  see screenshot http://cloud.atipra.in/index.php/s/MxYbEisyFT3KnKT 

  Extension installed : None

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.7-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 25 20:33:24 2022
  InstallationDate: Installed on 2020-01-03 (783 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2021-09-16 (162 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1962327/+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 2036817] Re: soffice.bin crashed with SIGSEGV in com::sun::star::uno::Reference::operator->()

[Launchpad Bug Tracker]

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

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

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

Title:
  soffice.bin crashed with SIGSEGV in
  
com::sun::star::uno::Reference::operator->()

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

Bug description:
  Occurred when exiting Calc/

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 13:44:57 2023
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2023-09-17 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcAttrCurrent: libreoffice-soffice (complain)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi
   PC (0x7f4aee4abf8e) ok
   source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned 
int, com::sun::star::uno::Reference const&) () 
from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::OAccessibleContextWrapper::disposing() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   cppu::WeakComponentImplHelperBase::dispose() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
   cppu::WeakComponentImplHelperBase::release() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
  Title: soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/2036817/+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 2035016] Re: one of 3 monitors "frozen" when a window moves there

[Daniel van Vugt]

Everyone please also try this in /etc/environment by itself:

  MUTTER_DEBUG_KMS_THREAD_TYPE=user

and then reboot.

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

Title:
  one of 3 monitors "frozen" when a window moves there

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I move a window to one of my 3 monitors (not the main display),
  the monitor freezes. That means that moving the mouse there doesn't
  work and the picture is frozen on that monitor (including the mouse
  pointer which is visible there).

  The journal has those logs:

  Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
  Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:2

[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[Daniel van Vugt]

Although I might be assuming too much because if the bug happened 2
seconds before the log in comment #26 then there's nothing about it
being logged. That's normal for freezes. In that case we need to enable
full debug mode in /etc/environment:

  MUTTER_DEBUG=kms

reboot and then next time a freeze happens run:

  journalctl -b0 > journal.txt

and compress the resulting text file before attaching it here.

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

Title:
  one of 3 monitors "frozen" when a window moves there

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I move a window to one of my 3 monitors (not the main display),
  the monitor freezes. That means that moving the mouse there doesn't
  work and the picture is frozen on that monitor (including the mouse
  pointer which is visible there).

  The journal has those logs:

  Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
  Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)

[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[Daniel van Vugt]

Both of those logs contain the same warning from the kernel graphics
code:

WARNING: CPU: 12 PID: 148 at drivers/gpu/drm/drm_mode_object.c:45
drm_mode_object_add+0x99/0xa0 [drm]

whose call trace seems to be related to DisplayPort, MST (multi-stream
transport) and hotplugging.

We should assume until proven otherwise that Thomas' issue is
originating in the kernel. Everyone else please report new bugs of your
own so they can be investigated without confusion.

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

Title:
  one of 3 monitors "frozen" when a window moves there

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I move a window to one of my 3 monitors (not the main display),
  the monitor freezes. That means that moving the mouse there doesn't
  work and the picture is frozen on that monitor (including the mouse
  pointer which is visible there).

  The journal has those logs:

  Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
  Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789daf0 i   
resource:///

[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[Thomas Bechtold]

And it happened again after I unplugged and plugged my usb-c->display
port cable . looks like this time there's more useful information in the
logs.

** Attachment added: "journal.txt after unplug/plug the display port cable with 
mutter (45.0-1ubuntu1)"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702554/+files/journal.txt

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

Title:
  one of 3 monitors "frozen" when a window moves there

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I move a window to one of my 3 monitors (not the main display),
  the monitor freezes. That means that moving the mouse there doesn't
  work and the picture is frozen on that monitor (including the mouse
  pointer which is visible there).

  The journal has those logs:

  Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
  Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7

[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[Thomas Bechtold]

with latest mutter+gnome-shell (single GPU), this still happens. log
attached.

** Attachment added: "journal.txt from current boot 2 seconds after the problem 
occured with mutter (45.0-1ubuntu1)"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702553/+files/journal.txt

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

Title:
  one of 3 monitors "frozen" when a window moves there

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When I move a window to one of my 3 monitors (not the main display),
  the monitor freezes. That means that moving the mouse there doesn't
  work and the picture is frozen on that monitor (including the mouse
  pointer which is visible there).

  The journal has those logs:

  Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
  Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
  Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, 
use Mtk.Rectangle instead
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
  Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789da70 i   
resource:///org/gnome/shell/ui/overv

[Desktop-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~mwhudson/ubuntu-seeds/+git/ubuntu/+merge/451769

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

Title:
  autoinstall ssh:install-server:false is misleading in 22.04

Status in subiquity:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Jammy:
  Confirmed

Bug description:
  With 22.04, openssh-server is baked into the image curtin copies to
  the target.  The ssh:install-server key no longer controls whether
  openssh-server gets installed.  It should be easy enough to have the
  bit of code that installs openssh-server when the key is true also
  remove it when the key is false.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1974483/+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 2036746] Re: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard

[Daniel van Vugt]

gnome-shell (44.3-0ubuntu2) lunar-security; urgency=medium

  * SECURITY UPDATE: Avoid exposing window previews on lock screen
via keyboard shortcuts (CVE-2023-43090, LP: #2036746, gnome-shell#6990)

 -- Jeremy Bícha   Wed, 20 Sep 2023 08:32:31 -0400


** Tags added: fixed-in-gnome-shell-43.9 fixed-in-gnome-shell-44.5
fixed-upstream

** Also affects: gnome-shell (Ubuntu Mantic)
   Importance: Undecided
   Status: Fix Released

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

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

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

** Changed in: gnome-shell (Ubuntu Lunar)
 Assignee: Marc Deslauriers (mdeslaur) => Jeremy Bícha (jbicha)

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

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

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

Title:
  CVE-2023-43090: avoid exposing window previews on lock screen via
  keyboard

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Invalid
Status in gnome-shell source package in Lunar:
  Fix Committed
Status in gnome-shell source package in Mantic:
  Fix Released

Bug description:
  Security Impact
  ---
  Open windows can be viewed from the lock screen without unlocking the screen.

  Test Case
  -
  From upstream

  This is the broken case and should not happen:

  - Lock screen (e.g. Super+L)
  - Press PrtScn to open screenshot tool
  - Press V twice to toggle the screenshot tool from picture mode to video mode 
and then back to picture mode. (First bug: it should not be possible to enter 
video mode when the UI element is insensitive.)
  - Enter the window selection mode by clicking or pressing W
  - Now all of the user's windows may be viewed despite the session being 
locked.

  Initial Testing Done
  
  I built the package locally. I installed the updated packages on Ubuntu 23.04 
and was no longer able to reproduce the failure case.

  Other Info
  --
  I was unable to duplicate the failure with Ubuntu 22.04 LTS.

  GNOME Shell 42 (included in 22.04 LTS) was the first GNOME release
  with an embedded screenshot tool; previously it used gnome-screenshot.
  So older versions are definitely not affected. GNOME Shell 42 reached
  End of Life earlier this year, but it does not appear to be affected
  by this issue.

  This issue has been fixed for Ubuntu 23.10 with GNOME Shell 45.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2036746/+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 2036802] Re: HDMI not detected on HP Zbook Power 15 G9

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (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/2036802

Title:
  HDMI not detected on HP Zbook Power 15 G9

Status in linux-hwe-6.2 package in Ubuntu:
  Incomplete

Bug description:
  As discussed in this thread:
  https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811

  On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected.

  According to the discussion a fix has been implemented in kernel
  v6.6-rc1.

  If it's possible for Ubuntu to implement some fix in the current LTS
  version that would be MUCH helpful and appreciated for me and all
  other ubuntu users on the same laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.104.05  Sat Aug 19 
01:15:15 UTC 2023
   GCC version:  gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 19:25:44 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   evdi/1.14.1, 6.2.0-32-generic, x86_64: installed
   evdi/1.14.1, 6.2.0-33-generic, x86_64: installed
   nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed
   nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:89c0]
 Subsystem: Hewlett-Packard Company Device [103c:89c1]
  InstallationDate: Installed on 2023-08-21 (29 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic 
root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2023
  dmi.bios.release: 8.0
  dmi.bios.vendor: HP
  dmi.bios.version: U97 Ver. 01.08.00
  dmi.board.name: 89C0
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.63.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 17.99
  dmi.modalias: 
dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC
  dmi.product.sku: 6B867EA#UUW
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/linux-hwe-6.2/+bug/2036802/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Brian Murray]

I think we'd want to put it in a "quirk" and those are found in
DistUpgradeQuirks.py:

https://git.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/tree/DistUpgrade/DistUpgradeQuirks.py?h=ubuntu/mantic

I think a "StartUpgrade" quirk is likely the best time for this but
there should be a check to ensure that we are using the gtk frontend or
some other check to ensure that we really need to modify the font.

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

The attached script is an attempt to express my idea in python code. I
don't know where exactly I'd put those commands, though, so that's why I
abstain from a merge request.

** Attachment added: "proposed_commands.py"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5702529/+files/proposed_commands.py

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 1959747]

[Frank Winklmeier]

I just tried the latest 118.0b4. The lag on the mouse-over effect as
well as the high CPU usage is still reproducible for me. First I thought
the new "cards view" is better, but that's just because fewer messages
are visible in the message pane at a given time. As has been pointed out
before, reducing the TB window size to show fewer messages also reduces
the effect in the classic table view.

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

Title:
  [upstream] Very high CPU and slow responsiveness in Thunderbird 91-102

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Very high CPU and slow responsiveness in Thunderbird 91.5.0 and later.
  Just moving the mouse cursor over a message list results in 365% CPU
  for me.

  I had to set this in the config editor to fix it:

    gfx.webrender.force-disabled = TRUE

  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1959747/+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 2036845] Re: /usr/share/hplip/plugin.py:NameError:/usr/bin/hp-plugin@363:download:__init__:__init__:__readAuthType

[Brian Murray]

The traceback follows:

Traceback (most recent call last):
  File "/usr/bin/hp-plugin", line 363, in 
status, plugin_path, error_str = pluginObj.download(plugin_path, 
plugin_download_callback)
 
^
  File "/usr/share/hplip/installer/pluginhandler.py", line 257, in download
core = core_install.CoreInstall()
   ^^
  File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
self.passwordObj = password.Password(ui_mode)
   ^^
  File "/usr/share/hplip/base/password.py", line 94, in __init__
self.__readAuthType()  # self.__authType
^
  File "/usr/share/hplip/base/password.py", line 119, in __readAuthType
distro_name = get_distro_std_name(os_name)
  ^^^
NameError: name 'get_distro_std_name' is not defined

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

Title:
  /usr/share/hplip/plugin.py:NameError:/usr/bin/hp-
  plugin@363:download:__init__:__init__:__readAuthType

Status in hplip package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
hplip.  This problem was most recently seen with package version 
3.22.10+dfsg0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/9aeb29248dd23b07b16a95abf8494d24f4b3e551 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2036845/+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 2036845] [NEW] /usr/share/hplip/plugin.py:NameError:/usr/bin/hp-plugin@363:download:__init__:__init__:__readAuthType

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
hplip.  This problem was most recently seen with package version 
3.22.10+dfsg0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/9aeb29248dd23b07b16a95abf8494d24f4b3e551 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: mantic

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

Title:
  /usr/share/hplip/plugin.py:NameError:/usr/bin/hp-
  plugin@363:download:__init__:__init__:__readAuthType

Status in hplip package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
hplip.  This problem was most recently seen with package version 
3.22.10+dfsg0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/9aeb29248dd23b07b16a95abf8494d24f4b3e551 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2036845/+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 1970921] Re: Drag and drop does not work

[Nope]

Second post, as I can only upload one file per comment.  A quick screen
recording to further demonstrate the reproducible issues.  Worth noting
that beyond the appended/suffixed text issue, drag and drop seems to
struggle with location context too.  Drag and drop fails multiple times
through standard user permissions, but succeeds 100% of the time through
root permissions.

** Attachment added: "Nautilus_Bug_Video.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970921/+attachment/5702483/+files/Nautilus_Bug_Video.mp4

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

Title:
  Drag and drop does not work

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

Bug description:
  After upgrading Ubuntu to 22.04 drag and dropping files from nautilus
  to web browser (chromium, google chrome / apps like seafile, etc.) do
  not work. Also drag & drop from nautilus to slack desktop app does not
  work. If making several attempts, it might suddenly work with nth
  attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 13:32:48 2022
  InstallationDate: Installed on 2016-11-22 (1983 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago)
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1970921/+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 2036333] Re: signon-ui no longer works for Google authentication

[Launchpad Bug Tracker]

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

** Changed in: signon-ui (Ubuntu)
   Status: New => Confirmed

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

Title:
  signon-ui no longer works for Google authentication

Status in kio-gdrive package in Ubuntu:
  Confirmed
Status in signon-ui package in Ubuntu:
  Confirmed
Status in signon-ui package in Fedora:
  Unknown

Bug description:
  The version of signon-ui from Launchpad no longer works for adding
  Google services in Kubuntu. The login hangs indefinitely after
  entering an email address.

  Apparently, a slightly newer version from its current home on git
  reportedly works, and is what others have been using:

  https://gitlab.com/accounts-sso/signon-ui

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kio-gdrive/+bug/2036333/+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 2036333] Re: signon-ui no longer works for Google authentication

[Launchpad Bug Tracker]

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

** Changed in: kio-gdrive (Ubuntu)
   Status: New => Confirmed

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

Title:
  signon-ui no longer works for Google authentication

Status in kio-gdrive package in Ubuntu:
  Confirmed
Status in signon-ui package in Ubuntu:
  Confirmed
Status in signon-ui package in Fedora:
  Unknown

Bug description:
  The version of signon-ui from Launchpad no longer works for adding
  Google services in Kubuntu. The login hangs indefinitely after
  entering an email address.

  Apparently, a slightly newer version from its current home on git
  reportedly works, and is what others have been using:

  https://gitlab.com/accounts-sso/signon-ui

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kio-gdrive/+bug/2036333/+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 2036817] Re: soffice.bin crashed with SIGSEGV in com::sun::star::uno::Reference::operator->()

[Bug Watch Updater]

Launchpad has imported 26 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=156683.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-08-08T22:03:37+00:00 Stephane-guillou-i wrote:

Created attachment 188856
backtrace without debug symbols

This bug was filed from the crash reporting server and is 
br-5dddbbb0-0ccd-4622-b1e4-8632bf974151.
=

Steps:
1. Open Calc
2. Write some text in cell A1
3. Select all text in formula bar, Ctrl + C
4. Paste into cell B1
5. Close LO, don't save
6. Reopen: crash reporter dialog

Repro in:

Version: 7.6.0.2 (X86_64) / LibreOffice Community
Build ID: 41d6f628ba3f046f16b5fa9fa8db8d4c2ab3b582
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

But not in a recent master build.

7.6 crash report:
https://crashreport.libreoffice.org/stats/crash_details/5dddbbb0-0ccd-4622-b1e4-8632bf974151

No crash with gen VCL. No crash with bibisect repo or debug build, so no
bibisect nor debug symbols in backtrace.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/comments/0


On 2023-08-08T22:04:13+00:00 Stephane-guillou-i wrote:

(no repro in 7.5.5.2)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/comments/1


On 2023-08-09T03:25:01+00:00 Miguelangelrv wrote:

I can't repro
Version: 7.6.0.2 (X86_64) / LibreOffice Community
Build ID: 41d6f628ba3f046f16b5fa9fa8db8d4c2ab3b582
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/comments/2


On 2023-08-09T08:05:51+00:00 Caolan-mcnamara wrote:

That's an accessibility thing that is crashing at exit. I wonder if it
is the same root as the recently fixed bug #156463 which is also an a11y
crash on exit

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/comments/3


On 2023-08-09T08:38:12+00:00 Xiscofauli wrote:

Since this is not reproducible with the bisect repos, I guess we have to wait 
until 7.6.0.3 builds are available ( in 1-2 days ) and retest.
I also believe this is related to bug 156463

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/comments/4


On 2023-08-10T16:18:00+00:00 julien2412 wrote:

On pc Debian x86-64 with master sources updated today + gtk3, I don't
reproduce this.

Remark: I just noticed that the pasted text in cell B1 was in 17.6 pt whereas 
initial A1 is 10 pt.
To have this, I must copy the test from formula bar, if I just copy A1, I don't 
have this bug.
Anyway, that's another story than this bugtracker.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/comments/5


On 2023-08-10T18:31:23+00:00 Stephane-guillou-i wrote:

(In reply to Julien Nabet from comment #5)
> Remark: I just noticed that the pasted text in cell B1 was in 17.6 pt
> whereas initial A1 is 10 pt.

This is tracked in bug 156209

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/comments/6


On 2023-08-18T18:11:47+00:00 Michael Weghorn wrote:

(In reply to Stéphane Guillou (stragu) from comment #0)
> No crash with gen VCL. No crash with bibisect repo or debug build, so no
> bibisect nor debug symbols in backtrace.

I've encountered a crash on exit w/ gtk3 with a similar backtrace with a
master debug build, see pending Gerrit change
https://gerrit.libreoffice.org/c/core/+/155848 with a full backtrace in
the commit message.

It probably doesn't fix the problem described here, though - if that one
still exists - but the underlying problem might be similar.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/comments/7


On 2023-08-18T20:21:19+00:00 Libreoffice-commits wrote:

Michael Weghorn committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/79cc574270582d03408286544d99227881f13bb8

related tdf#156683 a11y: Dispose FrameSelectorImpl a11y children

It will be available in 24.2.0.

The patch should be i

[Desktop-packages] [Bug 2033688] Re: [mantic] gnome-shell fails to follow accent colours

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2033688

** Tags added: iso-testing

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

Title:
  [mantic] gnome-shell fails to follow accent colours

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  When accent colors are selected in gnome-control-center, gnome-shell
  fails to follow with the exception of blue and orange. Screenshots
  attached.

  Test Case
  -
  1. Open the Settings app
  2. Switch to the Appearance page
  3. Choose the Purple color
  4. Click the quick settings area in the far right side of GNOME Shell's top 
bar
  5. The highlights should be purple

  What Happens Instead
  
  The highlights are still orange

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 13:50:24 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-03-04 (180 days ago)
  InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 
(20230304)
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033688/+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 2032812] Re: [FFe] libreoffice 7.6.x for mantic

[Rico Tzschichholz]

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

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

Title:
  [FFe] libreoffice 7.6.x for mantic

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Libreoffice releases are quite in sync with the Ubuntu release
  schedule and every Ubuntu release receives its new "major" update.

  This cycle there are a few issues. As precaution to prevent breaking
  the archive and blocking transitions the upload is delayed until
  further notice.

  Hereby I am asking for permission to upload libreoffice 7.6.x for
  23.10/mantic when it is ready.

  The package will be prepared at
  https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-
  
prereleases/+packages?field.name_filter=&field.status_filter=published&field.series_filter=mantic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2032812/+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 1970921] Re: Drag and drop does not work

[Nope]

As no fix has been released yet...  Echoing Alejandro's #10 comment, when 
attempting to drag and drop images from "Files" to Google Chrome or Slack, the 
following (seemingly random) garbage text is appended / suffixed to the file 
extension:
.jpg0:~28:478:44
.png0:~22:478:44
.png0:~7:460:44

As a result of the appended text, the destination app returns an error 
indicating the file path/type is invalid:
Google Chrome:
Your file couldn't be accessed
It may have been moved, edited, or deleted.
ERR_FILE_NOT_FOUND

Slack:
File unsupported
Sorry,  is a type of file not supported by Slack
Try uploading a .zip version of this file instead.
[OK]

In the case of Google Chrome, where the file path can be edited in the
address bar, removing the characters improperly suffixed onto the file
extension and attempting the navigation again by hitting Enter, the file
renders as expected.

A fresh installation of Ubuntu on a beefy Dell Precision 5680 laptop:
OS Name: Ubuntu 22.04.3 LTS
OS Type: 64-bit
GNOME Version: 42.9
Windows System: Wayland

Standard app installs, two different methods:
Google Chrome:
$ sudo apt install ./google-chrome-stable_current_amd64.deb
Google Chrome Version 117.0.5938.88 (Official Build) (64-bit)

Slack:
$ sudo snap install slack
Snap 4.34.115 64-bit

StackExchange got me over to this bug filing:
https://unix.stackexchange.com/questions/714305/unable-to-drag-and-drop-files-into-other-applications-on-ubuntu-22-04

And as "0xheartcode" posted there, it does seem to be a permissions issue:
"It is a permission issue/feature with Ubuntu 22.04.
Opening folders with sudo nautilus /home/user/ or sudo xdg-open /home/user/ 
fixes this."

When executing "$ sudo nautilus /home/" from Terminal,
supplying my password, and using the newly launched "Files" window to
perform drag and drop into Slack, I can no longer reproduce the issue.
With standard permissions, I encounter the improperly suffixed
characters and upload error within one to three drag and drop attempts.
As root, I can drag and drop upload 25+ images to Slack (10 at a time,
per Slack's file upload limitations) without encountering the
bug/permissions issue once.

** Attachment added: "Screenshot_References.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970921/+attachment/5702482/+files/Screenshot_References.png

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

Title:
  Drag and drop does not work

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

Bug description:
  After upgrading Ubuntu to 22.04 drag and dropping files from nautilus
  to web browser (chromium, google chrome / apps like seafile, etc.) do
  not work. Also drag & drop from nautilus to slack desktop app does not
  work. If making several attempts, it might suddenly work with nth
  attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 13:32:48 2022
  InstallationDate: Installed on 2016-11-22 (1983 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago)
  usr_lib_nautilus:
   evince42.1-3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1970921/+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 2036817] Re: soffice.bin crashed with SIGSEGV in com::sun::star::uno::Reference::operator->()

[Rico Tzschichholz]

** Bug watch added: Document Foundation Bugzilla #156683
   https://bugs.documentfoundation.org/show_bug.cgi?id=156683

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=156683
   Importance: Unknown
   Status: Unknown

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

Title:
  soffice.bin crashed with SIGSEGV in
  
com::sun::star::uno::Reference::operator->()

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  New

Bug description:
  Occurred when exiting Calc/

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 13:44:57 2023
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2023-09-17 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcAttrCurrent: libreoffice-soffice (complain)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi
   PC (0x7f4aee4abf8e) ok
   source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned 
int, com::sun::star::uno::Reference const&) () 
from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::OAccessibleContextWrapper::disposing() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   cppu::WeakComponentImplHelperBase::dispose() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
   cppu::WeakComponentImplHelperBase::release() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
  Title: soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/2036817/+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 2036333] Re: signon-ui no longer works for Google authentication

[Clay Weber]

** Tags added: kubuntu

** Also affects: kio-gdrive (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  signon-ui no longer works for Google authentication

Status in kio-gdrive package in Ubuntu:
  New
Status in signon-ui package in Ubuntu:
  New
Status in signon-ui package in Fedora:
  Unknown

Bug description:
  The version of signon-ui from Launchpad no longer works for adding
  Google services in Kubuntu. The login hangs indefinitely after
  entering an email address.

  Apparently, a slightly newer version from its current home on git
  reportedly works, and is what others have been using:

  https://gitlab.com/accounts-sso/signon-ui

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kio-gdrive/+bug/2036333/+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 2036805] Re: system crashes while running this command "sudo ubuntu-drivers autoinstall"

[Paul White]

** Package changed: ubiquity (Ubuntu) => ubuntu-drivers-common (Ubuntu)

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

Title:
  system crashes while running this command "sudo ubuntu-drivers
  autoinstall"

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  While trying to install the Nvidia driver with this command "sudo
  ubuntu-drivers autoinstall" system crushes.I'm finding difficult to
  install CUDA on my laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
  Uname: Linux 5.15.0-84-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 23:58:19 2023
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2023-09-19 (1 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2036805/+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 2036805] [NEW] system crashes while running this command "sudo ubuntu-drivers autoinstall"

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

While trying to install the Nvidia driver with this command "sudo
ubuntu-drivers autoinstall" system crushes.I'm finding difficult to
install CUDA on my laptop.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
Uname: Linux 5.15.0-84-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 20 23:58:19 2023
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2023-09-19 (1 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubiquity-20.04.15.19
-- 
system crashes while running this command "sudo ubuntu-drivers autoinstall"
https://bugs.launchpad.net/bugs/2036805
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to ubuntu-drivers-common 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 2033688] Re: [mantic] gnome-shell fails to follow accent colours

[Erich Eickmeyer]

Hi Aptivi, the screenshot was just an example, I'm seeing the same.

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

Title:
  [mantic] gnome-shell fails to follow accent colours

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  When accent colors are selected in gnome-control-center, gnome-shell
  fails to follow with the exception of blue and orange. Screenshots
  attached.

  Test Case
  -
  1. Open the Settings app
  2. Switch to the Appearance page
  3. Choose the Purple color
  4. Click the quick settings area in the far right side of GNOME Shell's top 
bar
  5. The highlights should be purple

  What Happens Instead
  
  The highlights are still orange

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 13:50:24 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-03-04 (180 days ago)
  InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 
(20230304)
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033688/+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 2036817] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/2036817/+attachment/5702480/+files/ThreadStacktrace.txt

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

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
+ soffice.bin crashed with SIGSEGV in 
com::sun::star::uno::Reference::operator->()

** Tags removed: need-amd64-retrace

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

Title:
  soffice.bin crashed with SIGSEGV in
  
com::sun::star::uno::Reference::operator->()

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Occurred when exiting Calc/

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 13:44:57 2023
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2023-09-17 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcAttrCurrent: libreoffice-soffice (complain)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi
   PC (0x7f4aee4abf8e) ok
   source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned 
int, com::sun::star::uno::Reference const&) () 
from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::OAccessibleContextWrapper::disposing() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   cppu::WeakComponentImplHelperBase::dispose() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
   cppu::WeakComponentImplHelperBase::release() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
  Title: soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/+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 2036817] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/2036817/+attachment/5702479/+files/StacktraceSource.txt

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

Title:
  soffice.bin crashed with SIGSEGV in
  
com::sun::star::uno::Reference::operator->()

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Occurred when exiting Calc/

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 13:44:57 2023
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2023-09-17 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcAttrCurrent: libreoffice-soffice (complain)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi
   PC (0x7f4aee4abf8e) ok
   source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned 
int, com::sun::star::uno::Reference const&) () 
from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::OAccessibleContextWrapper::disposing() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   cppu::WeakComponentImplHelperBase::dispose() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
   cppu::WeakComponentImplHelperBase::release() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
  Title: soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/+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 2036817] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/2036817/+attachment/5702478/+files/Stacktrace.txt

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

Title:
  soffice.bin crashed with SIGSEGV in
  
com::sun::star::uno::Reference::operator->()

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Occurred when exiting Calc/

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 13:44:57 2023
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2023-09-17 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcAttrCurrent: libreoffice-soffice (complain)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi
   PC (0x7f4aee4abf8e) ok
   source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned 
int, com::sun::star::uno::Reference const&) () 
from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::OAccessibleContextWrapper::disposing() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   cppu::WeakComponentImplHelperBase::dispose() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
   cppu::WeakComponentImplHelperBase::release() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
  Title: soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/+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 2036817] soffice.bin crashed with SIGSEGV in comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()

[Apport retracing service]

StacktraceTop:
 
com::sun::star::uno::Reference::operator->
 (this=0x558d207ac2b2) at 
/usr/src/libreoffice-4:7.6.1~rc2-0ubuntu2/include/com/sun/star/uno/Reference.h:384
 
comphelper::OInterfaceContainerHelper4::disposeAndClear
 (this=this@entry=0x7ffc92234cc0, rGuard=..., rEvt=...) at 
/usr/src/libreoffice-4:7.6.1~rc2-0ubuntu2/include/comphelper/interfacecontainer4.hxx:397
 comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing 
(_nClient=, _rxEventSource=...) at 
/usr/src/libreoffice-4:7.6.1~rc2-0ubuntu2/comphelper/source/misc/accessibleeventnotifier.cxx:204
 comphelper::OAccessibleContextWrapper::disposing (this=) at 
/usr/src/libreoffice-4:7.6.1~rc2-0ubuntu2/comphelper/source/misc/accessiblewrapper.cxx:610
 cppu::WeakComponentImplHelperBase::dispose (this=0x55887f492c50) at 
/usr/src/libreoffice-4:7.6.1~rc2-0ubuntu2/cppuhelper/source/implbase.cxx:104

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

Title:
  soffice.bin crashed with SIGSEGV in
  
com::sun::star::uno::Reference::operator->()

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Occurred when exiting Calc/

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 13:44:57 2023
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2023-09-17 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcAttrCurrent: libreoffice-soffice (complain)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi
   PC (0x7f4aee4abf8e) ok
   source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned 
int, com::sun::star::uno::Reference const&) () 
from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::OAccessibleContextWrapper::disposing() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   cppu::WeakComponentImplHelperBase::dispose() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
   cppu::WeakComponentImplHelperBase::release() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
  Title: soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/+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 2036817] [NEW] soffice.bin crashed with SIGSEGV in comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()

[Carl Godfrey]

Public bug reported:

Occurred when exiting Calc/

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 20 13:44:57 2023
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2023-09-17 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
ProcAttrCurrent: libreoffice-soffice (complain)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SegvAnalysis:
 Segfault happened at: 0x7f4aee4abf8e:  mov(%rax,%rbp,1),%rdi
 PC (0x7f4aee4abf8e) ok
 source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region 
(needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? () from /usr/lib/libreoffice/program/libmergedlo.so
 comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned int, 
com::sun::star::uno::Reference const&) () from 
/usr/lib/libreoffice/program/libmergedlo.so
 comphelper::OAccessibleContextWrapper::disposing() () from 
/usr/lib/libreoffice/program/libmergedlo.so
 cppu::WeakComponentImplHelperBase::dispose() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
 cppu::WeakComponentImplHelperBase::release() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
Title: soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

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


** Tags: amd64 apport-crash mantic need-amd64-retrace wayland-session

** Information type changed from Private to Public

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

Title:
  soffice.bin crashed with SIGSEGV in
  comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Occurred when exiting Calc/

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 20 13:44:57 2023
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2023-09-17 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2)
  ProcAttrCurrent: libreoffice-soffice (complain)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi
   PC (0x7f4aee4abf8e) ok
   source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned 
int, com::sun::star::uno::Reference const&) () 
from /usr/lib/libreoffice/program/libmergedlo.so
   comphelper::OAccessibleContextWrapper::disposing() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   cppu::WeakComponentImplHelperBase::dispose() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
   cppu::WeakComponentImplHelperBase::release() () from 
/usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3
  Title: soffice.bin crashed with SIGSEGV in 
comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2036817/+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 109943] Re: Thunderbird: high CPU usage from progress bars

[Bug Watch Updater]

** Changed in: thunderbird
   Status: Invalid => Fix Released

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

Title:
  Thunderbird: high CPU usage from progress bars

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: mozilla-thunderbird

  When sending a simple and short email with Thunderbird via SMTP the
  CPU is used intensively. This seems not to be necessary. If the
  sending failed and an corresponding error message dialog appears, the
  CPU is still being used. When pressing ok to close the error dialog
  the CPU is fine. This suggests it might be related specifically to the
  progress bar.  Such behavior is especially annoying on a laptop where
  you can hear the CPU usage because of a starting fan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/109943/+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 109943]

[Vseerror-i]

This has a checked in patch, so I think the resolution should reflect
the effort as fixed, to the best extent possible at the time.

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

Title:
  Thunderbird: high CPU usage from progress bars

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: mozilla-thunderbird

  When sending a simple and short email with Thunderbird via SMTP the
  CPU is used intensively. This seems not to be necessary. If the
  sending failed and an corresponding error message dialog appears, the
  CPU is still being used. When pressing ok to close the error dialog
  the CPU is fine. This suggests it might be related specifically to the
  progress bar.  Such behavior is especially annoying on a laptop where
  you can hear the CPU usage because of a starting fan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/109943/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

Without my workaround, I didn't even get that far, but it hanged before
the "Cleaning up" phase. I could reboot manually, though.

With the workaround, the upgrade completed including "Cleaning up".

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Jeremy Bícha]

Here's a screenshot from today, upgrading Ubuntu Desktop 23.04 to 23.10.
This is the screen where the upgrader asks to remove no longer needed
packages. It makes me very uncomfortable to have this screen be
unreadable.

** Attachment added: "upgrade-to-mantic-2023-09-20_14-17-15.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2034986/+attachment/5702440/+files/upgrade-to-mantic-2023-09-20_14-17-15.png

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2036746] Re: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard

[Marc Deslauriers]

** Changed in: gnome-shell (Ubuntu Lunar)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

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

Title:
  CVE-2023-43090: avoid exposing window previews on lock screen via
  keyboard

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Lunar:
  Confirmed

Bug description:
  Security Impact
  ---
  Open windows can be viewed from the lock screen without unlocking the screen.

  Test Case
  -
  From upstream

  This is the broken case and should not happen:

  - Lock screen (e.g. Super+L)
  - Press PrtScn to open screenshot tool
  - Press V twice to toggle the screenshot tool from picture mode to video mode 
and then back to picture mode. (First bug: it should not be possible to enter 
video mode when the UI element is insensitive.)
  - Enter the window selection mode by clicking or pressing W
  - Now all of the user's windows may be viewed despite the session being 
locked.

  Initial Testing Done
  
  I built the package locally. I installed the updated packages on Ubuntu 23.04 
and was no longer able to reproduce the failure case.

  Other Info
  --
  I was unable to duplicate the failure with Ubuntu 22.04 LTS.

  GNOME Shell 42 (included in 22.04 LTS) was the first GNOME release
  with an embedded screenshot tool; previously it used gnome-screenshot.
  So older versions are definitely not affected. GNOME Shell 42 reached
  End of Life earlier this year, but it does not appear to be affected
  by this issue.

  This issue has been fixed for Ubuntu 23.10 with GNOME Shell 45.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2036746/+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 2030951] Re: geoclue.service fails to start

[Julian Andres Klode]

Oh that's possible but for me it's denying geoclue from accessing my LTE
modem for GPS data, I don't have a test to check if it can provide other
data.

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

Title:
  geoclue.service fails to start

Status in geoclue-2.0 package in Ubuntu:
  Triaged

Bug description:
  The geoclue service doesn't start anymore in mantic, failing with

  (geoclue:8550): Geoclue-CRITICAL **: 10:56:36.151: Failed to acquire
  name 'org.freedesktop.GeoClue2' on system bus or lost it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: geoclue-2.0 2.7.0-3
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Aug 10 10:57:41 2023
  InstallationDate: Installed on 2022-11-26 (256 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  SourcePackage: geoclue-2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/2030951/+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 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds

[Julian Andres Klode]

ppa-purge is a pretty dangerous script to run due to the downgrade
functionality that we should be discouraging use of.

It can create systems that look like they have supported components only
but had everything messed up by downgrading from some PPA.

If the PPA added packages not available in other sources, removing them
is fine. But if downgrades are involved it should come with reasonably
strong warnings.

Generally speaking people should probably reinstall from scratch if they
added a PPA that replaced important system packages.

** Also affects: software-properties (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [mantic] ppa-purge no longer purges what add-apt-repository adds

Status in ppa-purge package in Ubuntu:
  Triaged
Status in software-properties package in Ubuntu:
  New

Bug description:
  Test Case
  -
  From Ubuntu 23.10:

  sudo apt install hello
  sudo add-apt-repository ppa:jbicha/temp
  sudo apt upgrade

  apt policy hello

  sudo ppa-purge ppa:jbicha/temp

  apt policy hello
  reveals that the PPA version of hello is still installed

  Also /etc/apt/sources.list.d/jbicha-ubuntu-temp-mantic.sources
  is still present and active

  What Should Happen
  --
  ppa-purge should disable the PPA and reinstall any PPA packages with the 
version apt currently sees.

  Background
  --
  add-apt-repository creates deb822 sources lists, starting in Ubuntu 23.10

  https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by-
  default/29333

  Other Info
  --
  add-apt-repository has a --remove option

  But it does not do the reinstall part which is important
  Honestly, that feature is so important, I suggest that add-apt-repository 
take over the functionality of ppa-purge so that we always get the ppa-purge 
behavior

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761/+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 2030951] Re: geoclue.service fails to start

[Jeremy Bícha]

Julian, I think you're saying the same as Seb. The service can start but
the new apparmor profile in Ubuntu 23.10 is preventing geoclue from
providing location info to apps and services that use geoclue.

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

Title:
  geoclue.service fails to start

Status in geoclue-2.0 package in Ubuntu:
  Triaged

Bug description:
  The geoclue service doesn't start anymore in mantic, failing with

  (geoclue:8550): Geoclue-CRITICAL **: 10:56:36.151: Failed to acquire
  name 'org.freedesktop.GeoClue2' on system bus or lost it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: geoclue-2.0 2.7.0-3
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Aug 10 10:57:41 2023
  InstallationDate: Installed on 2022-11-26 (256 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  SourcePackage: geoclue-2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/2030951/+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 2036764] Re: indicator keyboard crashes when upgrading from lunar->mantic on ubuntu cinnamon

[Erich Eickmeyer]

Upon investigation, we have determined the rdepends in question:

cinnamon-core
 +-- Depends: lightdm
 ..+-- Depends: unity-greeter
 +-- Depends: indicator-applet
 ..+-- Recommends: indicator-keyboard

Unfortunately, this means it cannot be removed from the seed/meta, and
therefore, the meta is not a factor. The problem lies in the indicator,
which appears abandoned upstream and needs to be patched for this to
work without crashing. This is, of course, assuming the autopkgtests are
correct because, as you said, Tim, you couldn't reproduce in a lxd vm.

** Changed in: ubuntucinnamon-meta (Ubuntu)
   Status: New => Invalid

** Changed in: ubuntucinnamon-meta (Ubuntu)
 Assignee: Joshua Peisach (itzswirlz) => (unassigned)

** Changed in: indicator-keyboard (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  indicator keyboard crashes when upgrading from lunar->mantic on ubuntu
  cinnamon

Status in indicator-keyboard package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  Invalid

Bug description:
  Log snippet:

  JournalErrors:
   Sep 20 14:52:28 autopkgtest kernel: kauditd_printk_skb: 164 callbacks 
suppressed
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest systemd[1]: multipathd.socket: Socket service 
multipathd.service already active, refusing.
   Sep 20 14:52:32 autopkgtest systemd[1]: Failed to listen on 
multipathd.socket - multipathd control socket.
   Sep 20 14:52:34 autopkgtest kernel: kauditd_printk_skb: 205 callbacks 
suppressed
   Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:35 autopkgtest indicator-keybo[747]: g_variant_ref: assertion 
'value != NULL' failed
   Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv4: There 
appears to be another mDNS responder running, or previously systemd-resolved 
crashed with some outstanding transfers.
   Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv6: There 
appears to be another mDNS responder running, or previously systemd-resolved 
crashed with some outstanding transfers.
   Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Main 
process exited, code=dumped, status=11/SEGV
   Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Failed 
with result 'core-dump'.
   Sep 20 14:52:38 autopkgtest indicator-keybo[27565]: 
gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
   Sep 20 14:52:42 autopkgtest kernel: kauditd_printk_skb: 193 callbacks 
suppressed
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
  Package: indicator-keyboard 0.0.0+19.10.20220803-0ubuntu1

  I'll attach the full upgrade log.

  This bug was discovered by using autopkgtest. You can reproduce by
  installing autopkgtest, auto-upgrade-testing and cloning auto-upgrade-
  testing-specifications and running this from the parent directory:

  sudo --preserve-env=AUTOPKGTEST_APT_SOURCES_FILE python3 -m
  upgrade_testing.command_line -c auto-upgrade-testing-
  specifications/profiles/ubuntu-lunar-mantic-ubuntucinnamon-
  amd64_qemu.yaml --provision --results-dir /home/$USER/upgrade_cinnamon
  --adt-args=--timeout-factor=10

  I'll attach the full logs below. I'm also trying to recreate using an
  lxd container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/2036764/+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 2036802] [NEW] HDMI not detected on HP Zbook Power 15 G9

[Tim Lachmann]

Public bug reported:

As discussed in this thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811

On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected.

According to the discussion a fix has been implemented in kernel
v6.6-rc1.

If it's possible for Ubuntu to implement some fix in the current LTS
version that would be MUCH helpful and appreciated for me and all other
ubuntu users on the same laptop.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.104.05  Sat Aug 19 
01:15:15 UTC 2023
 GCC version:  gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 20 19:25:44 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 evdi/1.14.1, 6.2.0-32-generic, x86_64: installed
 evdi/1.14.1, 6.2.0-33-generic, x86_64: installed
 nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed
 nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 
0c) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:89c0]
   Subsystem: Hewlett-Packard Company Device [103c:89c1]
InstallationDate: Installed on 2023-08-21 (29 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic 
root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2023
dmi.bios.release: 8.0
dmi.bios.vendor: HP
dmi.bios.version: U97 Ver. 01.08.00
dmi.board.name: 89C0
dmi.board.vendor: HP
dmi.board.version: KBC Version 11.63.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 17.99
dmi.modalias: 
dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC
dmi.product.sku: 6B867EA#UUW
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
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 jammy ubuntu

** Summary changed:

- HDMI not detected
+ HDMI not detected on HP Zbook Power 15 G9

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

Title:
  HDMI not detected on HP Zbook Power 15 G9

Status in xorg package in Ubuntu:
  New

Bug description:
  As discussed in this thread:
  https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811

  On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected.

  According to the discussion a fix has been implemented in kernel
  v6.6-rc1.

  If it's possible for Ubuntu to implement some fix in the current LTS
  version that would be MUCH helpful and appreciated for me and all
  other ubuntu users on the same laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .pro

[Desktop-packages] [Bug 2030951] Re: geoclue.service fails to start

[Julian Andres Klode]

Starts here afaict, gps blocked by apparmor though.

What do you see, seb?

● geoclue.service - Location Lookup Service
 Loaded: loaded (/lib/systemd/system/geoclue.service; static)
 Active: active (running) since Wed 2023-09-20 18:53:28 CEST; 35s ago
   Main PID: 1594438 (geoclue)
  Tasks: 4 (limit: 37482)
 Memory: 2.4M
CPU: 153ms
 CGroup: /system.slice/geoclue.service
 └─1594438 /usr/libexec/geoclue

Sep 20 18:53:28 jak-t14-g3 systemd[1]: Starting geoclue.service - Location 
Lookup Service...
Sep 20 18:53:28 jak-t14-g3 systemd[1]: Started geoclue.service - Location 
Lookup Service.
Sep 20 18:53:28 jak-t14-g3 geoclue[1594438]: Failed to set GPS refresh rate: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy 
prevents this sender from sending this message to this recipient; 
type="method_call", sender=":1.2613" (uid=123 pid=1594438 
comm="/usr/libexec/geoclue" label="/usr/libexec/geoclue (enforce)") 
interface="org.freedesktop.ModemManager1.Modem.Location" 
member="SetGpsRefreshRate" error name="(unset)" requested_reply="0" 
destination=":1.17" (uid=0 pid=2021 comm="/usr/sbin/ModemManager" 
label="unconfined")

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

Title:
  geoclue.service fails to start

Status in geoclue-2.0 package in Ubuntu:
  Triaged

Bug description:
  The geoclue service doesn't start anymore in mantic, failing with

  (geoclue:8550): Geoclue-CRITICAL **: 10:56:36.151: Failed to acquire
  name 'org.freedesktop.GeoClue2' on system bus or lost it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: geoclue-2.0 2.7.0-3
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Aug 10 10:57:41 2023
  InstallationDate: Installed on 2022-11-26 (256 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  SourcePackage: geoclue-2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/2030951/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

Gunnar Hjalmarsson wrote:
> Maybe it would be sufficient to drop the Ubuntu font as the first choice and
> simply let fontconfig deal with it for everyone.

I tested that approach. On an updated lunar I run this command:

gsettings set org.gnome.desktop.interface font-name 'Sans 11'

before doing "update-manager -d". The upgrade completed successfully
without font rendering issues.

So as a workaround I'm thinking that an equivalent of that command could
be added to the beginning of the main function in DistUpgradeViewGtk3.py
file (before the first "Gtk.main()" call), while the equivalent of this
command:

gsettings reset org.gnome.desktop.interface font-name

could be executed right before the computer is restarted.

Or maybe just a wrapper.

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2036764] Re: indicator keyboard crashes when upgrading from lunar->mantic on ubuntu cinnamon

[Tim Andersson]

** Also affects: ubuntucinnamon-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  indicator keyboard crashes when upgrading from lunar->mantic on ubuntu
  cinnamon

Status in indicator-keyboard package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New

Bug description:
  Log snippet:

  JournalErrors:
   Sep 20 14:52:28 autopkgtest kernel: kauditd_printk_skb: 164 callbacks 
suppressed
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest systemd[1]: multipathd.socket: Socket service 
multipathd.service already active, refusing.
   Sep 20 14:52:32 autopkgtest systemd[1]: Failed to listen on 
multipathd.socket - multipathd control socket.
   Sep 20 14:52:34 autopkgtest kernel: kauditd_printk_skb: 205 callbacks 
suppressed
   Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:35 autopkgtest indicator-keybo[747]: g_variant_ref: assertion 
'value != NULL' failed
   Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv4: There 
appears to be another mDNS responder running, or previously systemd-resolved 
crashed with some outstanding transfers.
   Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv6: There 
appears to be another mDNS responder running, or previously systemd-resolved 
crashed with some outstanding transfers.
   Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Main 
process exited, code=dumped, status=11/SEGV
   Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Failed 
with result 'core-dump'.
   Sep 20 14:52:38 autopkgtest indicator-keybo[27565]: 
gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
   Sep 20 14:52:42 autopkgtest kernel: kauditd_printk_skb: 193 callbacks 
suppressed
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
  Package: indicator-keyboard 0.0.0+19.10.20220803-0ubuntu1

  I'll attach the full upgrade log.

  This bug was discovered by using autopkgtest. You can reproduce by
  installing autopkgtest, auto-upgrade-testing and cloning auto-upgrade-
  testing-specifications and running this from the parent directory:

  sudo --preserve-env=AUTOPKGTEST_APT_SOURCES_FILE python3 -m
  upgrade_testing.command_line -c auto-upgrade-testing-
  specifications/profiles/ubuntu-lunar-mantic-ubuntucinnamon-
  amd64_qemu.yaml --provision --results-dir /home/$USER/upgrade_cinnamon
  --adt-args=--timeout-factor=10

  I'll attach the full logs below. I'm also trying to recreate using an
  lxd container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/2036764/+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 2030951] Re: geoclue.service fails to start

[Sebastien Bacher]

Reopening, it owns the dbus name fine now but is still not working

** Summary changed:

- geoclue.service fails to start: (geoclue:8550): Geoclue-CRITICAL **: 
10:56:36.151: Failed to acquire name 'org.freedesktop.GeoClue2' on system bus 
or lost it.
+ geoclue.service fails to start

** Changed in: geoclue-2.0 (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  geoclue.service fails to start

Status in geoclue-2.0 package in Ubuntu:
  Triaged

Bug description:
  The geoclue service doesn't start anymore in mantic, failing with

  (geoclue:8550): Geoclue-CRITICAL **: 10:56:36.151: Failed to acquire
  name 'org.freedesktop.GeoClue2' on system bus or lost it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: geoclue-2.0 2.7.0-3
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Aug 10 10:57:41 2023
  InstallationDate: Installed on 2022-11-26 (256 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  SourcePackage: geoclue-2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/2030951/+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 2036764] [NEW] indicator keyboard crashes when upgrading from lunar->mantic on ubuntu cinnamon

[Tim Andersson]

Public bug reported:

Log snippet:

JournalErrors:
 Sep 20 14:52:28 autopkgtest kernel: kauditd_printk_skb: 164 callbacks 
suppressed
 Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
 Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
 Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:32 autopkgtest systemd[1]: multipathd.socket: Socket service 
multipathd.service already active, refusing.
 Sep 20 14:52:32 autopkgtest systemd[1]: Failed to listen on multipathd.socket 
- multipathd control socket.
 Sep 20 14:52:34 autopkgtest kernel: kauditd_printk_skb: 205 callbacks 
suppressed
 Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:35 autopkgtest indicator-keybo[747]: g_variant_ref: assertion 
'value != NULL' failed
 Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv4: There appears 
to be another mDNS responder running, or previously systemd-resolved crashed 
with some outstanding transfers.
 Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv6: There appears 
to be another mDNS responder running, or previously systemd-resolved crashed 
with some outstanding transfers.
 Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Main 
process exited, code=dumped, status=11/SEGV
 Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Failed 
with result 'core-dump'.
 Sep 20 14:52:38 autopkgtest indicator-keybo[27565]: 
gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
 Sep 20 14:52:42 autopkgtest kernel: kauditd_printk_skb: 193 callbacks 
suppressed
 Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
Package: indicator-keyboard 0.0.0+19.10.20220803-0ubuntu1

I'll attach the full upgrade log.

This bug was discovered by using autopkgtest. You can reproduce by
installing autopkgtest, auto-upgrade-testing and cloning auto-upgrade-
testing-specifications and running this from the parent directory:

sudo --preserve-env=AUTOPKGTEST_APT_SOURCES_FILE python3 -m
upgrade_testing.command_line -c auto-upgrade-testing-
specifications/profiles/ubuntu-lunar-mantic-ubuntucinnamon-
amd64_qemu.yaml --provision --results-dir /home/$USER/upgrade_cinnamon
--adt-args=--timeout-factor=10

I'll attach the full logs below. I'm also trying to recreate using an
lxd container

** Affects: indicator-keyboard (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Log snippet:
  
  JournalErrors:
-  Sep 20 14:52:28 autopkgtest kernel: kauditd_printk_skb: 164 callbacks 
suppressed
-  Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
-  Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
-  Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
-  Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
-  Sep 20 14:52:32 autopkgtest systemd[1]: multipathd.socket: Socket service 
multipathd.service already active, refusing.
-  Sep 20 14:52:32 autopkgtest systemd[1]: Failed to listen on 
multipathd.socket - multipathd control socket.
-  Sep 20 14:52:34 autopkgtest kernel: kauditd_printk_skb: 205 callbacks 
suppressed
-  Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
-  Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
-  Sep 20 14:52:35 autopkgtest indicator-keybo[747]: g_variant_ref: assertion 
'value != NULL' failed
-  Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv4: There 
appears to be another mDNS responder running, or previously systemd-resolved 
crashed with some outstanding transfers.
-  Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv6: There 
appears to be another mDNS responder running, or previously systemd-resolved 
crashed with some outstanding transfers.
-  Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Main 
process exited, code=dumped, status=11/SEGV
-  Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Failed 
with result 'core-dump'.
-  Sep 

[Desktop-packages] [Bug 1983010]

[Timalsinasagar4512]

I am getting this bug on manjaro on watching videos on coursera. I am using 
Mozilla Firefox 117.0.1 . 
.[18813] Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index2/size
[18813] Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index3/size
[18813] Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present
[18813] Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/possible

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

Title:
  Sandbox: attempt to open unexpected file
  /sys/devices/system/cpu/cpu0/cache/index2/size

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I use Firefox Beta and launch it from the terminal. While watching
  Netflix on Firefox, I get the following messages on my terminal:

  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index2/size
  Sandbox: attempt to open unexpected file 
/sys/devices/system/cpu/cpu0/cache/index3/size
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present
  Sandbox: attempt to open unexpected file /sys/devices/system/cpu
  Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox (not installed)
  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: KDE
  Date: Thu Jul 28 15:01:35 2022
  InstallationDate: Installed on 2022-06-21 (36 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1983010/+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 2033643] Re: [SRU] libreoffice 7.5.6 for lunar

[Rico Tzschichholz]

Upgraded libreoffice from 4:7.5.5-0ubuntu0.23.04.1 to
4:7.5.6-0ubuntu0.23.04.1 from lunar-proposed in a clean and up-to-date
lunar amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

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

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

Title:
  [SRU] libreoffice 7.5.6 for lunar

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release

   * Version 7.5.5 is currently released in lunar. For a list of fixed bugs 
compared to 7.5.5 see the list of bugs fixed in the release candidates of 7.5.6 
(that's a total of 53 bugs):
   https://wiki.documentfoundation.org/Releases/7.5.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.5.6/RC2#List_of_fixed_bugs

   7.5.6 RC2 is identical to the 7.5.6 release

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_75/1671/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  Tested build can be found at 
https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135055/+listing-archive-extra
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230901_205756_d4783@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230902_020105_e2774@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230901_185845_d6d5b@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230901_174418_b7c30@/log.gz
  * [riscv64] not available
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230901_201014_90e5e@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 53 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033643/+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 2036746] Re: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard

[Jeremy Bícha]

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

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

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

Title:
  CVE-2023-43090: avoid exposing window previews on lock screen via
  keyboard

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Lunar:
  Confirmed

Bug description:
  Security Impact
  ---
  Open windows can be viewed from the lock screen without unlocking the screen.

  Test Case
  -
  From upstream

  This is the broken case and should not happen:

  - Lock screen (e.g. Super+L)
  - Press PrtScn to open screenshot tool
  - Press V twice to toggle the screenshot tool from picture mode to video mode 
and then back to picture mode. (First bug: it should not be possible to enter 
video mode when the UI element is insensitive.)
  - Enter the window selection mode by clicking or pressing W
  - Now all of the user's windows may be viewed despite the session being 
locked.

  Initial Testing Done
  
  I built the package locally. I installed the updated packages on Ubuntu 23.04 
and was no longer able to reproduce the failure case.

  Other Info
  --
  I was unable to duplicate the failure with Ubuntu 22.04 LTS.

  GNOME Shell 42 (included in 22.04 LTS) was the first GNOME release
  with an embedded screenshot tool; previously it used gnome-screenshot.
  So older versions are definitely not affected. GNOME Shell 42 reached
  End of Life earlier this year, but it does not appear to be affected
  by this issue.

  This issue has been fixed for Ubuntu 23.10 with GNOME Shell 45.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2036746/+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 2036611] Re: FFe: Mesa 23.2.0

[Timo Aaltonen]

** Description changed:

  Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
  almost seven weeks past it's original release date. But at least we have
  an rc3 which is "only" two weeks old. Yes, we are getting close to
  mantic release but this series is something we want for Intel Meteor
  Lake support.
  
  This is now fresh in Debian unstable, and has been in Fedora 39 for a
  month already without any apparent drama.
+ 
+ Build available at the x-staging ppa
+ https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages
+ (status: i386/riscv64 build failed due to an upstream bug, but should be 
fixed by latest upload)

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

Title:
  FFe: Mesa 23.2.0

Status in mesa package in Ubuntu:
  New

Bug description:
  Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
  almost seven weeks past it's original release date. But at least we
  have an rc3 which is "only" two weeks old. Yes, we are getting close
  to mantic release but this series is something we want for Intel
  Meteor Lake support.

  This is now fresh in Debian unstable, and has been in Fedora 39 for a
  month already without any apparent drama.

  Build available at the x-staging ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages
  (status: i386/riscv64 build failed due to an upstream bug, but should be 
fixed by latest upload)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2036611/+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 2036746] [NEW] CVE-2023-43090: avoid exposing window previews on lock screen via keyboard

[Jeremy Bícha]

*** This bug is a security vulnerability ***

Public security bug reported:

Security Impact
---
Open windows can be viewed from the lock screen without unlocking the screen.

Test Case
-
>From upstream

This is the broken case and should not happen:

- Lock screen (e.g. Super+L)
- Press PrtScn to open screenshot tool
- Press V twice to toggle the screenshot tool from picture mode to video mode 
and then back to picture mode. (First bug: it should not be possible to enter 
video mode when the UI element is insensitive.)
- Enter the window selection mode by clicking or pressing W
- Now all of the user's windows may be viewed despite the session being locked.

Initial Testing Done

I built the package locally. I installed the updated packages on Ubuntu 23.04 
and was no longer able to reproduce the failure case.

Other Info
--
I was unable to duplicate the failure with Ubuntu 22.04 LTS.

GNOME Shell 42 (included in 22.04 LTS) was the first GNOME release with
an embedded screenshot tool; previously it used gnome-screenshot. So
older versions are definitely not affected. GNOME Shell 42 reached End
of Life earlier this year, but it does not appear to be affected by this
issue.

This issue has been fixed for Ubuntu 23.10 with GNOME Shell 45.0

** Affects: gnome-shell
 Importance: Unknown
 Status: Unknown

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

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


** Tags: lunar

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

** Also affects: gnome-shell (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

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

Title:
  CVE-2023-43090: avoid exposing window previews on lock screen via
  keyboard

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Lunar:
  Confirmed

Bug description:
  Security Impact
  ---
  Open windows can be viewed from the lock screen without unlocking the screen.

  Test Case
  -
  From upstream

  This is the broken case and should not happen:

  - Lock screen (e.g. Super+L)
  - Press PrtScn to open screenshot tool
  - Press V twice to toggle the screenshot tool from picture mode to video mode 
and then back to picture mode. (First bug: it should not be possible to enter 
video mode when the UI element is insensitive.)
  - Enter the window selection mode by clicking or pressing W
  - Now all of the user's windows may be viewed despite the session being 
locked.

  Initial Testing Done
  
  I built the package locally. I installed the updated packages on Ubuntu 23.04 
and was no longer able to reproduce the failure case.

  Other Info
  --
  I was unable to duplicate the failure with Ubuntu 22.04 LTS.

  GNOME Shell 42 (included in 22.04 LTS) was the first GNOME release
  with an embedded screenshot tool; previously it used gnome-screenshot.
  So older versions are definitely not affected. GNOME Shell 42 reached
  End of Life earlier this year, but it does not appear to be affected
  by this issue.

  This issue has been fixed for Ubuntu 23.10 with GNOME Shell 45.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2036746/+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 2036746] Re: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard

[Jeremy Bícha]

** Patch added: "gnome-shell-lp2036746.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036746/+attachment/5702363/+files/gnome-shell-lp2036746.debdiff

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-43090

** Information type changed from Public to Public Security

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

Title:
  CVE-2023-43090: avoid exposing window previews on lock screen via
  keyboard

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Lunar:
  Confirmed

Bug description:
  Security Impact
  ---
  Open windows can be viewed from the lock screen without unlocking the screen.

  Test Case
  -
  From upstream

  This is the broken case and should not happen:

  - Lock screen (e.g. Super+L)
  - Press PrtScn to open screenshot tool
  - Press V twice to toggle the screenshot tool from picture mode to video mode 
and then back to picture mode. (First bug: it should not be possible to enter 
video mode when the UI element is insensitive.)
  - Enter the window selection mode by clicking or pressing W
  - Now all of the user's windows may be viewed despite the session being 
locked.

  Initial Testing Done
  
  I built the package locally. I installed the updated packages on Ubuntu 23.04 
and was no longer able to reproduce the failure case.

  Other Info
  --
  I was unable to duplicate the failure with Ubuntu 22.04 LTS.

  GNOME Shell 42 (included in 22.04 LTS) was the first GNOME release
  with an embedded screenshot tool; previously it used gnome-screenshot.
  So older versions are definitely not affected. GNOME Shell 42 reached
  End of Life earlier this year, but it does not appear to be affected
  by this issue.

  This issue has been fixed for Ubuntu 23.10 with GNOME Shell 45.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2036746/+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 2036749] [NEW] Sudo gnome-terminal fails

[Rob Peters]

Public bug reported:


Can't launch a sudo version of gnome-terminal

sudo gnome-terminal
# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: 
Failed to execute child process “dbus-launch” (No such file or directory)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-terminal 3.44.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Wed Sep 20 08:48:31 2023
InstallationDate: Installed on 2023-09-01 (19 days ago)
InstallationMedia: Ubuntu-Budgie 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2023-09-02T06:36:32.926571

** Affects: gnome-terminal (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 gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2036749

Title:
  Sudo gnome-terminal fails

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  
  Can't launch a sudo version of gnome-terminal

  sudo gnome-terminal
  # Error constructing proxy for 
org.gnome.Terminal:/org/gnome/Terminal/Factory0: Failed to execute child 
process “dbus-launch” (No such file or directory)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 20 08:48:31 2023
  InstallationDate: Installed on 2023-09-01 (19 days ago)
  InstallationMedia: Ubuntu-Budgie 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230807)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-09-02T06:36:32.926571

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2036749/+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 2036751] [NEW] file-roller's show files doesn't go to file directory

[wontfix]

Public bug reported:

Clicking show files doesn't pull up the directory the files were
extracted to. It opens home.

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  file-roller's show files doesn't go to file directory

Status in file-roller package in Ubuntu:
  New

Bug description:
  Clicking show files doesn't pull up the directory the files were
  extracted to. It opens home.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2036751/+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 1574586] Re: Not able to rate/review snaps

[Michael Vogt]

** Project changed: snappy => snapd

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

Title:
  Not able to rate/review snaps

Status in Ratings and Reviews server:
  New
Status in snapd:
  Confirmed
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Snaps are not able to be rated/reviewed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/rnr-server/+bug/1574586/+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 1593407] Re: Guest session cannot run snaps

[Michael Vogt]

** Project changed: snappy => snapd

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

Title:
  Guest session cannot run snaps

Status in Light Display Manager:
  Confirmed
Status in snapd:
  Confirmed
Status in Ubuntu MATE:
  Confirmed
Status in Desktop:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in firefox source package in Xenial:
  Confirmed
Status in lightdm source package in Xenial:
  Confirmed
Status in snapd source package in Xenial:
  Confirmed

Bug description:
  I'm using Ubuntu 16.04.

  The guest session cannot execute snaps, because of a permission error.
  The LightDM's guest session AppArmor profile is not allowing access to /snap 
and other needed files and folders.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1593407/+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 1598667] Re: No snapd API for account registration / password reset

[Michael Vogt]

** Project changed: snappy => snapd

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

Title:
  No snapd API for account registration / password reset

Status in snapd:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  There is no mechanism for registering an account using snapd or
  resetting your password. This is currently done by knowing the
  appropriate URLs to visit (https://login.ubuntu.com/+forgot_password
  etc).

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1598667/+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 2036743] [NEW] WiFi roaming causes disconnection

[Kian Cross]

Public bug reported:

My device is connected to a university wireless network. There are
numerous beacons, and my device regularly roams between them. However,
when this happens, I experience a wireless disconnect.

Upon further investigation (see attached log), it appears that this is
because the DHCP lease is being refreshed, resulting in a new IP which
breaks existing connections.

I think the following bug on the NetworkManager repository describes the
same issue:

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

I am on Ubuntu 22.04.3 LTS, with NM version 1.36.6-0ubuntu2. This issue
is not fixed until later versions of NM, which are not available in the
Ubuntu package repositories.

Can this fix be backported? I'm surprised that I haven't seen others
reporting this issue, given that I imagine many others are on similar
corporate networks.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager 1.36.6-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
Uname: Linux 5.15.0-83-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: i3
Date: Wed Sep 20 14:03:18 2023
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-09-30 (1450 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 10.255.255.254 dev wlp0s20f3 proto dhcp metric 600 
 10.252.0.0/14 dev wlp0s20f3 proto kernel scope link src 10.253.101.252 metric 
600
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: network-manager
UpgradeStatus: Upgraded to jammy on 2023-08-16 (34 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN 
 running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  disabled

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


** Tags: amd64 apport-bug jammy

** Attachment added: "NetworkManager log"
   https://bugs.launchpad.net/bugs/2036743/+attachment/5702346/+files/log.txt

** Attachment removed: "nmcli-con.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2036743/+attachment/5702360/+files/nmcli-con.txt

** Attachment removed: "NetworkManager log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2036743/+attachment/5702346/+files/log.txt

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

Title:
  WiFi roaming causes disconnection

Status in network-manager package in Ubuntu:
  New

Bug description:
  My device is connected to a university wireless network. There are
  numerous beacons, and my device regularly roams between them. However,
  when this happens, I experience a wireless disconnect.

  Upon further investigation (see attached log), it appears that this is
  because the DHCP lease is being refreshed, resulting in a new IP which
  breaks existing connections.

  I think the following bug on the NetworkManager repository describes
  the same issue:

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

  I am on Ubuntu 22.04.3 LTS, with NM version 1.36.6-0ubuntu2. This
  issue is not fixed until later versions of NM, which are not available
  in the Ubuntu package repositories.

  Can this fix be backported? I'm surprised that I haven't seen others
  reporting this issue, given that I imagine many others are on similar
  corporate networks.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  Uname: Linux 5.15.0-83-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: i3
  Date: Wed Sep 20 14:03:18 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-30 (1450 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 10.255.255.254 dev wlp0s20f3 proto dhcp metric 600 
   10.252.0.0/14 dev wlp0s20f3 proto kernel scope link src 10.253.101.252 
metric 600
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to jammy on 2023-08-16 (34 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2036743/+subscriptions


-- 
Mailing list: https://launchpad.net/~desk

[Desktop-packages] [Bug 2036743] Re: WiFi roaming causes disconnection

[Kian Cross]

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2036743/+attachment/5702362/+files/WifiSyslog.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2036743/+attachment/5702359/+files/WifiSyslog.txt

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

Title:
  WiFi roaming causes disconnection

Status in network-manager package in Ubuntu:
  New

Bug description:
  My device is connected to a university wireless network. There are
  numerous beacons, and my device regularly roams between them. However,
  when this happens, I experience a wireless disconnect.

  Upon further investigation (see attached log), it appears that this is
  because the DHCP lease is being refreshed, resulting in a new IP which
  breaks existing connections.

  I think the following bug on the NetworkManager repository describes
  the same issue:

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

  I am on Ubuntu 22.04.3 LTS, with NM version 1.36.6-0ubuntu2. This
  issue is not fixed until later versions of NM, which are not available
  in the Ubuntu package repositories.

  Can this fix be backported? I'm surprised that I haven't seen others
  reporting this issue, given that I imagine many others are on similar
  corporate networks.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-83.92-generic 5.15.116
  Uname: Linux 5.15.0-83-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: i3
  Date: Wed Sep 20 14:03:18 2023
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-30 (1450 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 10.255.255.254 dev wlp0s20f3 proto dhcp metric 600 
   10.252.0.0/14 dev wlp0s20f3 proto kernel scope link src 10.253.101.252 
metric 600
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to jammy on 2023-08-16 (34 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2036743/+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 2036611] Re: FFe: Mesa 23.2.0

[Timo Aaltonen]

** Description changed:

  Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
  almost seven weeks past it's original release date. But at least we have
  an rc3 which is "only" two weeks old. Yes, we are getting close to
  mantic release but this series is something we want for Intel Meteor
  Lake support.
  
- This is now fresh in Debian unstable, and has been in Fedora 39/40 for a
+ This is now fresh in Debian unstable, and has been in Fedora 39 for a
  month already without any apparent drama.

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

Title:
  FFe: Mesa 23.2.0

Status in mesa package in Ubuntu:
  New

Bug description:
  Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
  almost seven weeks past it's original release date. But at least we
  have an rc3 which is "only" two weeks old. Yes, we are getting close
  to mantic release but this series is something we want for Intel
  Meteor Lake support.

  This is now fresh in Debian unstable, and has been in Fedora 39 for a
  month already without any apparent drama.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2036611/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

> What about this idea for a workaround: have the upgrader temporarily
switch the UI font to a font that hasn't been changed since Jammy?

That sounds as a reasonable idea. Maybe it would be sufficient to drop
the Ubuntu font as the first choice and simply let fontconfig deal with
it for everyone.

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

[Bug Watch Updater]

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

** Changed in: xorg-server
   Status: New => 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/2034619

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

Status in Linux:
  New
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034619/+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 1555567] Re: [snaps] License information from the store not available

[Michael Vogt]

** Project changed: snappy => snapd

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

Title:
  [snaps] License information from the store not available

Status in snapd:
  Confirmed
Status in snapd-glib:
  Confirmed
Status in Software Center Agent:
  New
Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  While the store (and its API) has a field to specify the app's
  license, it seems to be ignored somewhere on its way to the client.

  As an example, ubuntu-calculator-app.ubuntucoredev has GPL3 set as its
  license in the store, yet in GNOME Software it is tagged as "non-free"
  when listed in a search. Clicking on the package details in GNOME
  Software, the license type is shown as "Unknown".

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/167/+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 1643910] Re: BAMF_DESKTOP_FILE_HINT not set in correct place for unity7

[Michael Vogt]

** Project changed: snappy => snapd

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

Title:
  BAMF_DESKTOP_FILE_HINT not set in correct place for unity7

Status in snapd:
  Triaged
Status in bamf package in Ubuntu:
  Fix Released

Bug description:
  Occasionally when I pin items to the Unity7 launcher, the BAMF code
  (as I'm told) incorrectly matches to /snap/app/revision/ This is a
  security issue because the Exec= line points to /snap/app/revision/...
  which bypasses snap run (/snap/bin/...) and therefore snap-confine.

  I'm told by Marcus (aka, 3v1n0 aka Trevinho) that this is because
  BAMF_DESKTOP_FILE_HINT is not exported by snap env and instead only
  injected in the desktop file that is created in
  /var/lib/snapd/desktop/applications upon snap install. This means that
  the wrong Exec= (ie, where it points to the binary) may occur in two
  places:

  1. when launching /snap/bin/... from the command line
  2. when something in /var/lib/snapd/desktop/applications/*.desktop doesn't 
match properly

  In both cases, the initial launch is fine, but pinning the icon to the
  launcher results in the wrong entry in the Exec= line and launching
  from this pinned launcher entry after is unconfined. You can check by
  doing:

  1. launch application from the dash
  2. run sudo aa-status and see if it is launched under confinement
  3. pin the icon that is in the launcher
  4. close the application, then launch from the pinned icon
  5. run sudo aa-status and see if it is launched under confinement

  This doesn't happen all the time. For example, vlc seems to work fine
  both from the command line and from launching via a pinned launcher
  entry. chrome-test on the other hand doesn't seem to work with either.

  Related https://github.com/snapcore/snapd/pull/1580 -- puts
  BAMF_DESKTOP_FILE_HINT in the desktop file instead of in the
  environment, but Marco requested that this change
  (https://github.com/snapcore/snapd/pull/1580#issuecomment-234546220).

  https://trello.com/c/xP1hN3BF/152-improve-desktop-file-support-by-
  adding-a-new-bamf-desktop-file-hint-environment-hint also discussed
  this issue, but the card is archived and therefore it won't be worked
  on.

  I'm having trouble finding a simple reproducer (other than chrome-
  test) but am told by Marco that the BAMF matching will always work if
  BAMF_DESKTOP_FILE_HINT in the process' environment always points to
  the desktop file in /var/lib/snapd/desktop/applications. I will
  continue to look for a simple reproducer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1643910/+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 2036597] Re: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos))

[Martin Randau]

No, the laptop had been up and running for some time there. Here's
journalctl from 11:32:

Sep 20 11:31:49 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:31:49 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:31:51 ThinkPad-P14s-Gen-3 kernel: audit: type=1400 
audit(1695202311.035:244): apparmor="DENIED" operation="open" class="file" 
profile="snap.firefox.firefox" name="/etc/fstab" pid=6542 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Sep 20 11:31:51 ThinkPad-P14s-Gen-3 dbus-daemon[1487]: [system] Activating via 
systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.172' (uid=1000 
pid=6542 comm="/snap/firefox/3145/usr/lib/firefox/firefox" 
label="snap.firefox.firefox (enforce)")
Sep 20 11:31:51 ThinkPad-P14s-Gen-3 systemd[1]: Starting 
systemd-hostnamed.service - Hostname Service...
Sep 20 11:31:51 ThinkPad-P14s-Gen-3 dbus-daemon[1487]: [system] Successfully 
activated service 'org.freedesktop.hostname1'
Sep 20 11:31:51 ThinkPad-P14s-Gen-3 systemd[1]: Started 
systemd-hostnamed.service - Hostname Service.
Sep 20 11:31:51 ThinkPad-P14s-Gen-3 kernel: audit: type=1107 
audit(1695202311.383:245): pid=1487 uid=101 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/hostname1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.173" pid=6542 label="snap.firefox.firefox" peer_pid=7747 
peer_label="unconfined"
 exe="/usr/bin/dbus-daemon" 
sauid=101 hostname=? addr=? terminal=?'
Sep 20 11:31:51 ThinkPad-P14s-Gen-3 kernel: audit: type=1107 
audit(1695202311.383:246): pid=1487 uid=101 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/org/freedesktop/hostname1" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name=":1.173" pid=6542 label="snap.firefox.firefox" peer_pid=7747 
peer_label="unconfined"
 exe="/usr/bin/dbus-daemon" 
sauid=101 hostname=? addr=? terminal=?'
Sep 20 11:31:51 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:31:58 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:31:58 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:32:07 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:32:07 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:32:07 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:32:07 ThinkPad-P14s-Gen-3 gnome-shell[3636]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
Sep 20 11:32:08 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:32:08 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:32:15 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:32:15 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:32:15 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:32:15 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:32:15 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is 
deprecated, use Mtk.Rectangle instead
Sep 20 11:32:21 ThinkPad-P14s-Gen-3 dbus-daemon[3346]: [session uid=1000 
pid=3346] Activating service name='org.gnome.Nautilus' requested by ':1.90' 
(uid=1000 pid=4310 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" 
label="unconfined")
Sep 20 11:32:21 ThinkPad-P14s-Gen-3 systemd[1]: anacron.service - Run anacron 
jobs was skipped because of an unmet condition check (ConditionACPower=true).
Sep 20 11:32:21 ThinkPad-P14s-Gen-3 nautilus[7855]: Connecting to 
org.freedesktop.Tracker3.Miner.Files
Sep 20 11:32:21 ThinkPad-P14s-Gen-3 dbus-daemon[3346]: [session uid=1000 
pid=3346] Successfully activated service 'org.gnome.Nautilus'
Sep 20 11:32:21 ThinkPad-P14s-Gen-3 systemd[1]: systemd-hostnamed.service: 
Deactivated successfully.
Sep 20 11:32:21 ThinkPad-P14s-Gen-3 org.gnome.Nautilus[7855]: Initializing 
nautilus-dropbox 2019.02.14
Sep 20 11:32:21 ThinkPad-P14s-Gen-3 dbus-daemon[1487]: [system] Activating via 
systemd: service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.175' (uid=1000 
pid=7855 comm="/usr/bin/nautilus --gapplication-

[Desktop-packages] [Bug 2036597] Re: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos))

[Sebastien Bacher]

The timestamp indicates those were created at 11:32, do you know what
you did on the system around that time? is that when you turned the
computer on/started the session?

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

Title:
  Strange permissions and/or links to default directories in home folder
  (Music, Pictures, Public, Templates and Videos))

Status in xdg-user-dirs package in Ubuntu:
  Incomplete

Bug description:
  Can't enter these folders. This is on an almost fresh install of
  Mantic.

  martin@ThinkPad-P14s-Gen-3:~$ cd Music
  bash: cd: Music: Too many levels of symbolic links


  martin@ThinkPad-P14s-Gen-3:~$ ls -l
  total 2988
  drwxrwxr-x  3 martin martin4096 Sep 18 12:44 bin
  drwxr-xr-x  2 martin martin4096 Sep 19 13:48 Desktop
  drwxr-xr-x 19 martin martin4096 Sep 18 12:42 Documents
  drwxr-xr-x  4 martin martin4096 Sep 19 13:48 Downloads
  drwx--  5 martin martin4096 Sep 18 16:24 Dropbox
  lrwxrwxrwx  1 martin martin  18 Sep 19 13:56 Music -> /home/martin/Music
  lrwxrwxrwx  1 martin martin  21 Sep 19 13:56 Pictures -> 
/home/martin/Pictures
  lrwxrwxrwx  1 martin martin  19 Sep 19 13:56 Public -> /home/martin/Public
  drwxrwxr-x  3 martin martin4096 Sep 18 16:25 R
  -rw---  1 martin martin 3029503 Sep 19 14:08 references.bib
  drwx-- 13 martin martin4096 Sep 19 13:56 snap
  lrwxrwxrwx  1 martin martin  22 Sep 19 13:56 Templates -> 
/home/martin/Templates
  lrwxrwxrwx  1 martin martin  19 Sep 19 13:56 Videos -> /home/martin/Videos

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 14:19:32 2023
  InstallationDate: Installed on 2023-09-18 (1 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   nautilus-dropbox  2019.02.14-1.2
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/2036597/+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 2036597] Re: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos))

[Martin Randau]

It happened again:

martin@ThinkPad-P14s-Gen-3:~$ ls -l
total 2992
drwxrwxr-x  3 martin martin4096 Sep 18 12:44 bin
drwxr-xr-x  2 martin martin4096 Sep 19 13:48 Desktop
drwxr-xr-x 19 martin martin4096 Sep 18 12:42 Documents
drwxr-xr-x  4 martin martin4096 Sep 20 11:31 Downloads
drwx--  5 martin martin4096 Sep 19 14:56 Dropbox
lrwxrwxrwx  1 martin martin  18 Sep 20 11:32 Music -> /home/martin/Music
drwxrwxr-x  3 martin martin4096 Sep 19 15:10 Pictures
lrwxrwxrwx  1 martin martin  19 Sep 20 11:32 Public -> /home/martin/Public
drwxrwxr-x  3 martin martin4096 Sep 18 16:25 R
-rw---  1 martin martin 3027062 Sep 19 14:37 references.bib
drwx-- 13 martin martin4096 Sep 19 13:56 snap
lrwxrwxrwx  1 martin martin  22 Sep 20 11:32 Templates -> 
/home/martin/Templates
lrwxrwxrwx  1 martin martin  19 Sep 20 11:32 Videos -> /home/martin/Videos

but this time, .config/user-dirs.dirs is not changed, or the changes to
correct I made before are still there, e.g.,
XDG_VIDEOS_DIR="$HOME/Videos".

In fact, even though I changed the locale to en_DK, Settings still show
the default en_US and locale seems to be a mix?

martin@ThinkPad-P14s-Gen-3:~$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_DK.UTF-8
LC_TIME=en_DK.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=en_DK.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=en_DK.UTF-8
LC_NAME=en_DK.UTF-8
LC_ADDRESS=en_DK.UTF-8
LC_TELEPHONE=en_DK.UTF-8
LC_MEASUREMENT=en_DK.UTF-8
LC_IDENTIFICATION=en_DK.UTF-8
LC_ALL=


** Attachment added: "Screenshot from 2023-09-20 12-11-42.png"
   
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/2036597/+attachment/5702323/+files/Screenshot%20from%202023-09-20%2012-11-42.png

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

Title:
  Strange permissions and/or links to default directories in home folder
  (Music, Pictures, Public, Templates and Videos))

Status in xdg-user-dirs package in Ubuntu:
  Incomplete

Bug description:
  Can't enter these folders. This is on an almost fresh install of
  Mantic.

  martin@ThinkPad-P14s-Gen-3:~$ cd Music
  bash: cd: Music: Too many levels of symbolic links


  martin@ThinkPad-P14s-Gen-3:~$ ls -l
  total 2988
  drwxrwxr-x  3 martin martin4096 Sep 18 12:44 bin
  drwxr-xr-x  2 martin martin4096 Sep 19 13:48 Desktop
  drwxr-xr-x 19 martin martin4096 Sep 18 12:42 Documents
  drwxr-xr-x  4 martin martin4096 Sep 19 13:48 Downloads
  drwx--  5 martin martin4096 Sep 18 16:24 Dropbox
  lrwxrwxrwx  1 martin martin  18 Sep 19 13:56 Music -> /home/martin/Music
  lrwxrwxrwx  1 martin martin  21 Sep 19 13:56 Pictures -> 
/home/martin/Pictures
  lrwxrwxrwx  1 martin martin  19 Sep 19 13:56 Public -> /home/martin/Public
  drwxrwxr-x  3 martin martin4096 Sep 18 16:25 R
  -rw---  1 martin martin 3029503 Sep 19 14:08 references.bib
  drwx-- 13 martin martin4096 Sep 19 13:56 snap
  lrwxrwxrwx  1 martin martin  22 Sep 19 13:56 Templates -> 
/home/martin/Templates
  lrwxrwxrwx  1 martin martin  19 Sep 19 13:56 Videos -> /home/martin/Videos

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 14:19:32 2023
  InstallationDate: Installed on 2023-09-18 (1 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   nautilus-dropbox  2019.02.14-1.2
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/2036597/+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 1429584] Re: gnome-terminal doesn't set $COLORTERM from 3.14 onwards

[Egmont Koblinger]

I've just found a link to this ancient bugreport in
https://en.wikipedia.org/wiki/ANSI_escape_code.

Unfortunately this discussion here contains two confusing mistakes. I'd
like to correct them for future reference purposes. No action necessary,
other than perhaps closing this bug, and fixing the Wiki page (I might
do the latter).

In comment #1 I was mistakenly talking about the COLOR*FGBG* variable,
not about COLOR*TERM*. This can be seen by the link pointing to an issue
that actually (correctly) talks about COLORFGBG, and from my words over
here not making any sense. I probably made the same mistake in #4 too
(but I'm not sure). I must have had that other environment variable in
mind and talked about that, incorrectly typing the name of the one this
bugreport was talking about, not realizing the difference. My bad,
apologies for this mistake. (I'm not editing the earlier posts here
because then the thread will make even less sense.)

COLORTERM used to be set to the terminal emulator's name, "gnome-
terminal" in our case. This was removed from GNOME Terminal version
3.14, released in 2014, the commit is linked from comment #2 here. This
version of GNOME Terminal (or rather, the corresponding VTE version)
also implemented truecolor support. Around this time the de facto use of
this environment variable across various terminal emulators shifted for
it to contain the "truecolor" string if the emulator supported this
feature. So VTE 0.44, corresponding to GNOME Terminal 3.20, released in
2016 brought back this environment variable with the new value in
https://github.com/GNOME/vte/commit/1dea919b9aa4b55e2c5c07bf2022769cbac365b5.
Since the setting now occurs in VTE rather than GNOME Terminal, it is
set in all VTE-based emulators. It has stayed ever since and is likely
to stay as long as this variable is in widespread use.

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

Title:
  gnome-terminal doesn't set $COLORTERM from 3.14 onwards

Status in gnome-terminal package in Ubuntu:
  Opinion

Bug description:
  Gnome terminal has dropped the $COLORTERM workaround for invalid
  terminfo/termcap.

  References:
  
https://github.com/GNOME/gnome-terminal/commit/1d5c1b6ca6373c1301494edbc9e43c3e6a9c9aaf
  https://bugzilla.redhat.com/show_bug.cgi?id=1165439
  https://bugzilla.redhat.com/show_bug.cgi?id=1173688
  https://bugzilla.redhat.com/show_bug.cgi?id=1166428

  This affects release: Vivid Vervet

  Workaround I currently use is `.bashrc`:
   if [ -z "$COLORTERM" ] && cat /proc/$PPID/exe 2> /dev/null | grep -q 
gnome-terminal; then
    export COLORTERM=gnome-terminal
   fi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1429584/+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 2036719] [NEW] Start of audio cut off after upgrade to 23.10

[Alistair Cunningham]

Public bug reported:

After upgrading from Ubuntu 23.04 to 23.10, my Sony WH-1000XM5
headphones have Bluetooth audio problems that didn't happen on 23.04.

Initially, they connected in mono mode only, and audio was completely
corrupt. I unpaired them and re-paired them, and this problem appears to
be fixed.

Now they give good audio quality, but the first second or so of audio is
cut off when starting playing. The audio test in the Ubuntu sound
settings plays "t left" rather than "front left". If I then click on
right, it says "front right" correctly. If I close the audio test and
open it again, the same problem happens again.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pipewire 0.3.79-2
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Sep 20 10:52:56 2023
InstallationDate: Installed on 2020-07-14 (1163 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pipewire
UpgradeStatus: Upgraded to mantic on 2023-09-16 (4 days ago)

** Affects: pipewire (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 pipewire in Ubuntu.
https://bugs.launchpad.net/bugs/2036719

Title:
  Start of audio cut off after upgrade to 23.10

Status in pipewire package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10, my Sony WH-1000XM5
  headphones have Bluetooth audio problems that didn't happen on 23.04.

  Initially, they connected in mono mode only, and audio was completely
  corrupt. I unpaired them and re-paired them, and this problem appears
  to be fixed.

  Now they give good audio quality, but the first second or so of audio
  is cut off when starting playing. The audio test in the Ubuntu sound
  settings plays "t left" rather than "front left". If I then click on
  right, it says "front right" correctly. If I close the audio test and
  open it again, the same problem happens again.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pipewire 0.3.79-2
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Sep 20 10:52:56 2023
  InstallationDate: Installed on 2020-07-14 (1163 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to mantic on 2023-09-16 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2036719/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

[Daniel van Vugt]

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2861
   https://gitlab.freedesktop.org/drm/amd/-/issues/2861

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/amd/-/issues/2861
   Importance: Unknown
   Status: Unknown

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

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

Status in Linux:
  Unknown
Status in X.Org X server:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034619/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash

[Daniel van Vugt]

I have more questions than answers now...

* It looks like source_gnome-shell.py already attaches journalctl
output, so why didn't it here?

* data/general-hooks/generic.py also attaches journal errors, so why
didn't it here?

* Do we really want all Ubuntu bug reports to have journal data that
might be sensitive?

* Can we compress system logs before attaching them?

* Why is ubuntu.py source maintained in debian/patches/Add-general-
hooks.patch instead of a standalone file?

* What's the criteria for going in ubuntu.py vs upstream
https://github.com/canonical/apport ?

It all seems a little too hard right now. I have other things I need to
be doing instead of learning apport and Python.

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

Title:
  Choosing "Try Ubuntu" on daily-legacy image produced a crash

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I was booting up a daily-legacy image from 20230918 and received a
  crash report after choosing "Try Ubuntu".

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu3
  Uname: Linux 6.5.0-5-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 15:20:58 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694375959
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2034105] Update Released

[Chris Halse Rogers]

The verification of the Stable Release Update for xserver-xorg-video-
amdgpu 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 xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/2034105

Title:
  Cursor didn't show up in X session when output from amd dgpu

Status in OEM Priority Project:
  Fix Committed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

   * There is no cursor in Xorg session when output from AMD Navi3.x
  dgpu

  [ Test Plan ]

   * Test on the DT with AMD Navi3.x dgpu

   * Attach external monitor to AMD Navi3.x dgpu

   * Switch to Xorg session when login

   * Check if cursor is appeared and works properly

  [ Where problems could occur ]

   * The implementation checks DRM_CAP_CURSOR_WIDTH and
  DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if
  kernel can't report the caps.

   * The user might see different cursor size after the patch applied,
  since the driver will ask kernel for it but not the hard coded one.

  [ Other Info ]

   * Upstream commit: 
https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614
   * The patch has been included in mantic and lunar already

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2034105/+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 2034105] Re: Cursor didn't show up in X session when output from amd dgpu

[Launchpad Bug Tracker]

This bug was fixed in the package xserver-xorg-video-amdgpu -
22.0.0-1ubuntu0.2

---
xserver-xorg-video-amdgpu (22.0.0-1ubuntu0.2) jammy; urgency=medium

  * Use DRM_CAP_CURSOR_WIDTH/HEIGHT if possible (LP: #2034105)

 -- Kai-Chuan Hsieh   Wed, 06 Sep 2023
14:43:28 +0800

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Cursor didn't show up in X session when output from amd dgpu

Status in OEM Priority Project:
  Fix Committed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

   * There is no cursor in Xorg session when output from AMD Navi3.x
  dgpu

  [ Test Plan ]

   * Test on the DT with AMD Navi3.x dgpu

   * Attach external monitor to AMD Navi3.x dgpu

   * Switch to Xorg session when login

   * Check if cursor is appeared and works properly

  [ Where problems could occur ]

   * The implementation checks DRM_CAP_CURSOR_WIDTH and
  DRM_CAP_CURSOR_HEIGHT and fallback to original implementation if
  kernel can't report the caps.

   * The user might see different cursor size after the patch applied,
  since the driver will ask kernel for it but not the hard coded one.

  [ Other Info ]

   * Upstream commit: 
https://cgit.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/?id=9c959fac3af28d191105f63236096ad456dca614
   * The patch has been included in mantic and lunar already

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2034105/+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